• [gentoo-user] Vanishing tab bar in Firefox

    From Peter Humphrey@21:1/5 to All on Tue Aug 24 17:00:02 2021
    On Friday, 20 August 2021 17:26:15 BST Peter Humphrey wrote:
    On Saturday, 7 August 2021 10:45:26 BST Peter Humphrey wrote:
    Hello list,

    Far too often, Firefox on this box will hide the tab bar, but behave as though it were still there. In other words, I have to aim the mouse
    pointer
    2cm below the thing I want to click.

    Pressing <ALT> reveals the bar but clicking in it just hides it again. I can still cycle through the tabs with the standard <CTRL><left/right>.

    Sometimes remerging Firefox fixes it, sometimes rebooting does; mostly
    I
    just have to put up with it.

    Several versions of Firefox have suffered this, and several versions of Plasma. I might submit a bug report if I could work out which component
    is
    at fault.

    Disabling my three plugins didn't help. I fixed it in the end by removing ~/.mozilla and setting mozilla up again. At least, I hope it's fixed. It's looking good so far.

    Spoke too soon. It's back again, and it's more stubborn this time. I really don't want to keep zapping my Firefox directory and setting it up all over again, especially as I don't understand what's going wrong. Any crumbs of advice or experience, anyone?

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrew Lowe@21:1/5 to Peter Humphrey on Wed Aug 25 05:10:02 2021
    On 24/8/21 10:59 pm, Peter Humphrey wrote:
    On Friday, 20 August 2021 17:26:15 BST Peter Humphrey wrote:
    On Saturday, 7 August 2021 10:45:26 BST Peter Humphrey wrote:
    Hello list,


    [snip]


    Spoke too soon. It's back again, and it's more stubborn this time. I really don't want to keep zapping my Firefox directory and setting it up all over again, especially as I don't understand what's going wrong. Any crumbs of advice or experience, anyone?


    As the Firefox dir is all text files, I think, when you blow it away and rebuild and get the correct behaviour, grab a copy. When the dodgy behaviour returns diff the copy, with the good behaviour, against the
    current dir, with the dodgy behaviour, and see what's changed. That may
    lead to an indication of what's being naughty.

    I have a recollection of doing this in the past to track down a problem.

    Andrew

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Wed Aug 25 11:30:01 2021
    On Wednesday, 25 August 2021 04:05:12 BST Andrew Lowe wrote:
    On 24/8/21 10:59 pm, Peter Humphrey wrote:
    On Friday, 20 August 2021 17:26:15 BST Peter Humphrey wrote:
    On Saturday, 7 August 2021 10:45:26 BST Peter Humphrey wrote:
    Hello list,

    [snip]

    Spoke too soon. It's back again, and it's more stubborn this time. I
    really
    don't want to keep zapping my Firefox directory and setting it up all
    over
    again, especially as I don't understand what's going wrong. Any crumbs
    of
    advice or experience, anyone?

    As the Firefox dir is all text files, I think, when you blow it away and rebuild and get the correct behaviour, grab a copy. When the dodgy behaviour returns diff the copy, with the good behaviour, against the
    current dir, with the dodgy behaviour, and see what's changed. That may
    lead to an indication of what's being naughty.

    I have a recollection of doing this in the past to track down a
    problem.

    Good idea. Thanks Andrew.

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Wed Aug 25 12:40:01 2021
    On Wednesday, 25 August 2021 10:26:31 BST Peter Humphrey wrote:
    On Wednesday, 25 August 2021 04:05:12 BST Andrew Lowe wrote:

    As the Firefox dir is all text files, I think, when you blow it away and rebuild and get the correct behaviour, grab a copy. When the dodgy behaviour returns diff the copy, with the good behaviour, against the current dir, with the dodgy behaviour, and see what's changed. That
    may lead to an indication of what's being naughty.

    Good idea. Thanks Andrew.

    Just a small matter of 308 files to check. :)

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Neil Bothwick@21:1/5 to Peter Humphrey on Wed Aug 25 13:30:01 2021
    On Wed, 25 Aug 2021 11:35:26 +0100, Peter Humphrey wrote:

    As the Firefox dir is all text files, I think, when you
    blow it away and rebuild and get the correct behaviour, grab a
    copy. When the dodgy behaviour returns diff the copy, with the good behaviour, against the current dir, with the dodgy behaviour, and
    see what's changed. That may lead to an indication of what's being naughty.

    Good idea. Thanks Andrew.

    Just a small matter of 308 files to check. :)

    diff -r old/ new/ >lotsofstuff/txt :)


    --
    Neil Bothwick

    WinErr 004: Erroneous error - Nothing is wrong

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmEmKQwACgkQ92eFu0QS MJijDBAAnWQRxil0ZBU2xkSMZNfKQStYGo7ZyCRBreDrOeDOf3u8ju+pah3Y5e+w hpS9Faxf0BXn6rublalY1AgB6qUQN+1RBhPTaeTWk9mffYEcOkKrtpPxyPZnJwil Bm0qGk8gBVd0c7FZ/t+7Zy0OSd8qEGNl7hdOIlEg0fTZDqDDrYQO3vneAbMf8odU lHiR45QdgIpZslz4+WAUIdJD3szlaiOpyykXY1v6cbB1wUA5UGlNEjf7NO30cWoO 0f1pUr7ALtMyGMwcxzMbQqTVQT05k5wuvY/r0jMLCOJM4osqLwL8YDQIyQvENPSp gnIQ63UxWDVrzkgF0+neqMUpSXvSq+TWBm7DUhCdUEoE1mjG8uA1e+efe3brANoj nIe53hb6w7aT8gG0chjgoHhxGwRDaOj/7zfd5onVLqd5NiaKEEadcGn4lvhGEeiJ 7LW6O1zDqAz+ej/L4xpbII9dCeW5Ljli2WTiJrk1gSBzGm20S4gHZ1pG4nKwZEfl mPCmgi1vgSLPwCdHOv1TDs5dHPvpYp27qIXnJNU+1pas2yLZ2dSbnimtrgbVPHr6 lxLFWDwg8jfWKRJOGobtZa/4qAs36QLua/HX0YISSStTMXL71l85TKcqGyRkiOKX aktUVus+DD4BsWMogeNcX4JoQzqe8FuGV1ibtNa+YtGONE1S2/Q=
    =UUI5
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Wed Aug 25 15:30:02 2021
    On Wednesday, 25 August 2021 12:27:08 BST Neil Bothwick wrote:
    On Wed, 25 Aug 2021 11:35:26 +0100, Peter Humphrey wrote:
    As the Firefox dir is all text files, I think, when you

    blow it away and rebuild and get the correct behaviour, grab a
    copy. When the dodgy behaviour returns diff the copy, with the
    good
    behaviour, against the current dir, with the dodgy behaviour, and
    see what's changed. That may lead to an indication of what's being naughty.

    Good idea. Thanks Andrew.

    Just a small matter of 308 files to check. :)

    diff -r old/ new/ >lotsofstuff/txt :)

    :)

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Thu Aug 26 13:38:38 2021
    On Wednesday, 25 August 2021 14:22:39 BST Peter Humphrey wrote:
    On Wednesday, 25 August 2021 12:27:08 BST Neil Bothwick wrote:
    On Wed, 25 Aug 2021 11:35:26 +0100, Peter Humphrey wrote:
    As the Firefox dir is all text files, I think, when you

    blow it away and rebuild and get the correct behaviour, grab a
    copy. When the dodgy behaviour returns diff the copy, with the

    good

    behaviour, against the current dir, with the dodgy behaviour, and
    see what's changed. That may lead to an indication of what's being naughty.

    Good idea. Thanks Andrew.

    Just a small matter of 308 files to check. :)

    diff -r old/ new/ >lotsofstuff/txt :)
    :
    :)

    I have observed something similar in three edge use cases.

    1. When the browser is fighting against the window manager, or display environment, in the rendering of the application. I recall this being a particularly annoying problem a few years back, with Chromium on Enlightenment DE. From what I recall the problem was caused by Chromium's code taking over some window rendering functions, which conventionally was performed by the window manager. Minimising and restoring the Chromium window was a workaround to fix this problem, until Chromium improved their code.

    2. When an application window is running in a QEMU VM and the VM full desktop window itself is not maximised on the host. The mouse events are geographically misaligned with the target. After the guest desktop window is maximised the mouse becomes aligned and remains so even if the guest desktop window is resized thereafter.

    3. On a particular system I discovered Firefox tabs and scroll bar disappear, or do not respond, when running on Plasma in Wayland. Plasma in X11 plus Firefox works fine.

    I haven't found a workaround for the Firefox problem on Wayland, perhaps an update will address this.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmEni08ACgkQseqq9sKV Zxms6Q//ddhLI1rWxuwtk5zmLzRWuo8dQrUBNUgswxD5tfr7x7YZcQEPZIRUx7iv fGJtZo+RQ4EO9b0EpEcLh5MI++exRz8LJ/wZn724wjFFfj2Y0wSEropEUCrdnWRu DzNNx/No5TDnMd2UHKMv9GzN2UbV7LLEhza57NWBlXWK+ITdkwx8jePfXt7b6a8k QBruV6LPSNEbcf+JPj6GLDaRkhK+6ecWXZHHpojgNYMcxMNjG7QRkURyAO6lSBfe H+md1WOtckFUxa79dpCuH2G8jZ5aG8XuH5w9l/h4JYrLXjGNlnyndfiZiBI3A+gK PJHGfQdYllrkOcs5pq2lFf7pEsyCpxdmcGZc7cb7Yz0fbs3i2uTO7b9+Q7yrXzgO C1L8SMmZmjTm00N2yrVCQN5sbs90uLQGFI49jg48BxTxjI056AKstjtSWD5X6hvg NMbM35CYJOx/6443Eo6K4Gqmt/CTXlhOrp6qhBA4jd+x4QnzOCfK9pa0QmQrvZUi tOzdWV+2TPb7uQPWbfNEZgQZ/cJnZ/gtefNguUvZdroZaB2tqLzKIAX/mGTcpBOq uODZ3pbOEN6o66XpkzZFusoFNKwRDIbaxVzcWK/MOrGBs12Gja4aZIMhTaJtmeiH TAZXTN0EHfta1ehwfccS8BPIjDsLxGSrkTVIN9/Rrqa5TBD5ZGs=
    =O1fV
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)