Hello, I thought I had already raised this issue, but I can't see any emails. So maybe mistaken. But anyway, the problem is when I click on a pull down menu - any pull down menu - in Firefox, it previously appears, but then disappears immediately. e.g. right click on a web page (any web page). On click on the one of the Firefox plugin menus. Or the Firefox menu. Unlikely many of the reported similar problems restarting Firefox solves the problem, and it doesn't appear to be a problem with my Profile. As in I have completely rebuilt my profile from scratch several times, and eventually the problem comes back. Rather, I have found what triggers it appears to be clicking on a link within notmuch inside emacs. The page loads OK. Then the very next menu fails however. It only happens if I open a page from emacs. If I manually run "firefox-esr http://www.google.com/" or "xdg-open http://www.google.com/" it works fine. This has happened a while now on a range of different computers, running different profiles, on different versions of Debian. Just noticed running strace on the emacs process, the firefox invocation is a bit more complex then I might have noticed. I don't see any URL even on the command line. Wonder if there is something here that is killing menus. [pid 16180] execve("/usr/lib/firefox-esr/firefox-esr", ["/usr/lib/firefox-esr/firefox-esr", "-contentproc", "-childID", "13", "-isForBrowser", "-prefsLen", "7297", "-prefMapSize", "185946", "-parentBuildID", "20200720181548", "-greomni", "/usr/lib/firefox-esr/omni.ja", "-appomni", "/usr/lib/firefox-esr/browser/omni.ja", "-appdir", "/usr/lib/firefox-esr/browser", "11615", "true", "tab"], 0x7fe29880c900 /* 54 vars */) = 0 -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Subscribed. When you open a link from emacs does it become a child process to emac? Can you test with the following scenario and see if it makes any difference: 1. launch firefox from terminal by "/path/to/firefox -P" 2. create a new temp profile (for the test) 3. then click a link on emacs + Alexar On Wed, Sep 2, 2020 at 8:08 AM Brian May via luv-main <luv-main@luv.asn.au> wrote:
Hello,
I thought I had already raised this issue, but I can't see any emails. So maybe mistaken.
But anyway, the problem is when I click on a pull down menu - any pull down menu - in Firefox, it previously appears, but then disappears immediately. e.g. right click on a web page (any web page). On click on the one of the Firefox plugin menus. Or the Firefox menu.
Unlikely many of the reported similar problems restarting Firefox solves the problem, and it doesn't appear to be a problem with my Profile. As in I have completely rebuilt my profile from scratch several times, and eventually the problem comes back.
Rather, I have found what triggers it appears to be clicking on a link within notmuch inside emacs. The page loads OK. Then the very next menu fails however.
It only happens if I open a page from emacs. If I manually run "firefox-esr http://www.google.com/" or "xdg-open http://www.google.com/" it works fine.
This has happened a while now on a range of different computers, running different profiles, on different versions of Debian.
Just noticed running strace on the emacs process, the firefox invocation is a bit more complex then I might have noticed. I don't see any URL even on the command line. Wonder if there is something here that is killing menus.
[pid 16180] execve("/usr/lib/firefox-esr/firefox-esr", ["/usr/lib/firefox-esr/firefox-esr", "-contentproc", "-childID", "13", "-isForBrowser", "-prefsLen", "7297", "-prefMapSize", "185946", "-parentBuildID", "20200720181548", "-greomni", "/usr/lib/firefox-esr/omni.ja", "-appomni", "/usr/lib/firefox-esr/browser/omni.ja", "-appdir", "/usr/lib/firefox-esr/browser", "11615", "true", "tab"], 0x7fe29880c900 /* 54 vars */) = 0 -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/ _______________________________________________ luv-main mailing list luv-main@luv.asn.au https://lists.luv.asn.au/cgi-bin/mailman/listinfo/luv-main
-- [image: image.jpg] *Alexar Pendashteh* technologist / social entrepreneur https://github.com/pendashteh
Alexar Pendashteh <hi@alexar.me> writes:
When you open a link from emacs does it become a child process to emac?
Can you test with the following scenario and see if it makes any difference:
1. launch firefox from terminal by "/path/to/firefox -P" 2. create a new temp profile (for the test) 3. then click a link on emacs
Previously I thought this worked fine. For a while. But I just did a test (using above steps) and found that I can reproduce the problem immediately with Firefox running a brand new profile. Which sort of surprised me a bit actually. Sometimes this does "come good" on a particular computer for a while, and I have no idea why. -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Brian May via luv-main <luv-main@luv.asn.au> writes:
Previously I thought this worked fine. For a while. But I just did a test (using above steps) and found that I can reproduce the problem immediately with Firefox running a brand new profile.
Which sort of surprised me a bit actually.
Sometimes this does "come good" on a particular computer for a while, and I have no idea why.
I realised that a computer where this just works has the latest Firefox which I downloaded from the Firefox website (now 80.0.1). Instead of the ESR version supplied with Debian (68.11.0esr). So I installed the same version on my machine where it is not working, and encountered exactly the same issue, with a brand new profile also. So nope, looks like nothing to do with the Firefox profile or the version. -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
On Sun, Sep 6, 2020, at 7:29 PM, Brian May via luv-main wrote:
Brian May via luv-main <luv-main@luv.asn.au> writes:
So I installed the same version on my machine where it is not working, and encountered exactly the same issue, with a brand new profile also.
So nope, looks like nothing to do with the Firefox profile or the version. -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Hello Brian, Far be it for me to know what is happening, but I recall that I had trouble with Firefox menus when my window manager at the time wasn't properly configured. It was twm at the time. When I got the wm going, Firefox was fine. Just a thought that occurred to me on this issue. ben
Ben Nisenbaum via luv-main <luv-main@luv.asn.au> writes:
Far be it for me to know what is happening, but I recall that I had trouble with Firefox menus when my window manager at the time wasn't properly configured. It was twm at the time. When I got the wm going, Firefox was fine. Just a thought that occurred to me on this issue.
Good suggestion. Thanks. I am using i3. But I have the exact same config (git controlled in fact) on the working and non-working computers... -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Brian May via luv-main <luv-main@luv.asn.au> writes:
I am using i3. But I have the exact same config (git controlled in fact) on the working and non-working computers...
The "good computer" suddenly started playing up too, I have no idea why. But setting browse-url-browser-function to browse-url-firefox (instead of the default of browse-url-default-browser) seems to have solved the problem. Curious. PS: How on earth did the email address become "Russell Coker via luv-main <luv-main@luv.asn.au>"? Russell has never participated in this conversation... -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Brian May via luv-main <luv-main@luv.asn.au> writes:
But setting browse-url-browser-function to browse-url-firefox (instead of the default of browse-url-default-browser) seems to have solved the problem.
I spoke too soon. Problem has come back again. Which is partly why this is so frustrating. I repeatedly think I have solved the problem and it keeps coming back sometime later. Maybe I need to switch back to Chrome :-( -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
On 17/9/20 9:32 am, Brian May via luv-main wrote:
Which is partly why this is so frustrating. I repeatedly think I have solved the problem and it keeps coming back sometime later.
Maybe I need to switch back to Chrome :-(
or you could switch back to vim... [ducks] More seriously - if you set 'ui.popup.disable_autohide' to 'true' in firefox config (about:config), presumably the menus remain? This isn't a solution, because it means you have to escape out of firefox menus, but it would be interesting to see if there was some interaction with this autohide code. It seems at least one other person is seeing a bug here https://support.mozilla.org/en-US/questions/1273349 I'm assuming that for some reason firefox is thinking that the menu is losing focus. You could possibly use 'xev' and 'xprop -spy' to monitor the misbehaving firefox window you've opened from emacs/notmuch, see if there are any unexpected events? Glenn -- pgp: 833A 67F6 1966 EF5F 7AF1 DFF6 75B7 5621 6D65 6D65
Glenn McIntosh via luv-main <luv-main@luv.asn.au> writes:
More seriously - if you set 'ui.popup.disable_autohide' to 'true' in firefox config (about:config), presumably the menus remain?
Yes, that does help...
This isn't a solution, because it means you have to escape out of firefox menus, but it would be interesting to see if there was some interaction with this autohide code. It seems at least one other person is seeing a bug here https://support.mozilla.org/en-US/questions/1273349
Yes, that sounds familiar also. I thought maybe it was related to using i3, but he is using OSX...
I'm assuming that for some reason firefox is thinking that the menu is losing focus. You could possibly use 'xev' and 'xprop -spy' to monitor the misbehaving firefox window you've opened from emacs/notmuch, see if there are any unexpected events?
I am not making any sense of xev output. It is hard to know at what point the menu disappears. Before or after that LeaveNotify? (assume this is focus related). I am not seeing any mouse events. So wonder if I am not getting the right window id. But 0x5000003 it looks right: $ xwininfo xwininfo: Please select the window about which you would like information by clicking the mouse in that window. xwininfo: Window id: 0x5000003 "Dropdown Menus in Firefox Wont Stay Open | Firefox Support Forum | Mozilla Support - Mozilla Firefox" Absolute upper-left X: 3202 Absolute upper-left Y: 786 Relative upper-left X: 2 Relative upper-left Y: 0 Width: 1276 Height: 1560 Depth: 24 Visual: 0x2b Visual Class: TrueColor Border width: 0 Class: InputOutput Colormap: 0x5000002 (not installed) Bit Gravity State: NorthWestGravity Window Gravity State: NorthWestGravity Backing Store State: NotUseful Save Under State: no Map State: IsViewable Override Redirect State: no Corners: +3202+786 -2+786 -2-22 +3202-22 -geometry 1276x1560-0-20 On mouse down (nothing appears): PropertyNotify event, serial 22, synthetic NO, window 0x5000003, atom 0x15f (_NET_WM_USER_TIME), time 59001725, state PropertyNewValue On mouse up (menu appears and disappears): VisibilityNotify event, serial 22, synthetic NO, window 0x5000003, state VisibilityPartiallyObscured LeaveNotify event, serial 22, synthetic NO, window 0x5000003, root 0x1e4, subw 0x0, time 59008478, (1163,56), root:(4365,842), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 Expose event, serial 22, synthetic NO, window 0x5000003, (806,53), width 364, height 1, count 20 Expose event, serial 22, synthetic NO, window 0x5000003, (1172,53), width 19, height 1, count 19 Expose event, serial 22, synthetic NO, window 0x5000003, (806,54), width 363, height 1, count 18 Expose event, serial 22, synthetic NO, window 0x5000003, (1173,54), width 18, height 1, count 17 Expose event, serial 22, synthetic NO, window 0x5000003, (806,55), width 362, height 1, count 16 Expose event, serial 22, synthetic NO, window 0x5000003, (1174,55), width 17, height 1, count 15 Expose event, serial 22, synthetic NO, window 0x5000003, (806,56), width 361, height 1, count 14 Expose event, serial 22, synthetic NO, window 0x5000003, (1175,56), width 16, height 1, count 13 Expose event, serial 22, synthetic NO, window 0x5000003, (806,57), width 360, height 1, count 12 Expose event, serial 22, synthetic NO, window 0x5000003, (1176,57), width 15, height 1, count 11 Expose event, serial 22, synthetic NO, window 0x5000003, (806,58), width 359, height 1, count 10 Expose event, serial 22, synthetic NO, window 0x5000003, (1177,58), width 14, height 1, count 9 Expose event, serial 22, synthetic NO, window 0x5000003, (806,59), width 358, height 1, count 8 Expose event, serial 22, synthetic NO, window 0x5000003, (1178,59), width 13, height 1, count 7 Expose event, serial 22, synthetic NO, window 0x5000003, (806,60), width 357, height 1, count 6 Expose event, serial 22, synthetic NO, window 0x5000003, (1179,60), width 12, height 1, count 5 Expose event, serial 22, synthetic NO, window 0x5000003, (806,61), width 356, height 1, count 4 Expose event, serial 22, synthetic NO, window 0x5000003, (1180,61), width 11, height 1, count 3 Expose event, serial 22, synthetic NO, window 0x5000003, (806,62), width 4, height 602, count 2 Expose event, serial 22, synthetic NO, window 0x5000003, (1187,62), width 4, height 602, count 1 Expose event, serial 22, synthetic NO, window 0x5000003, (806,664), width 385, height 4, count 0 EnterNotify event, serial 22, synthetic NO, window 0x5000003, root 0x1e4, subw 0x0, time 59008479, (1163,56), root:(4365,842), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 KeymapNotify event, serial 22, synthetic NO, window 0x0, keys: 38 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 LeaveNotify event, serial 22, synthetic NO, window 0x5000003, root 0x1e4, subw 0x0, time 59008483, (1163,56), root:(4365,842), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 VisibilityNotify event, serial 22, synthetic NO, window 0x5000003, state VisibilityUnobscured Expose event, serial 22, synthetic NO, window 0x5000003, (806,53), width 385, height 615, count 0 EnterNotify event, serial 22, synthetic NO, window 0x5000003, root 0x1e4, subw 0x0, time 59008483, (1163,56), root:(4365,842), mode NotifyNormal, detail NotifyNonlinear, same_screen YES, focus YES, state 0 KeymapNotify event, serial 22, synthetic NO, window 0x0, keys: 4294967268 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
Brian May via luv-main <luv-main@luv.asn.au> writes:
I opened another report: https://support.mozilla.org/en-US/questions/1273349 -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
On Sun, Sep 06, 2020 at 07:29:29PM +1000, Brian May wrote:
I realised that a computer where this just works has the latest Firefox which I downloaded from the Firefox website (now 80.0.1). Instead of the ESR version supplied with Debian (68.11.0esr).
68.11.0esr is what's in testing, right? sid currently has 78.2.0esr maybe try that? or switch to firefox rather than firefox-esr. I think testing currently has 79.0. sid has 80.0.1 i used firefox-esr for a while until I had new versions of my plugins (or, at least, reasonable replacements for most of them), but i don't really see any point to firefox-esr now. It's moved past the version where xul plugins still worked, so it's just firefox but a few versions behind. craig ps: ewwww - upstream binaries. that's unhygienic. -- craig sanders <cas@taz.net.au>
Hello Craig and Brian, On 9/17/20, Craig Sanders via luv-main <luv-main@luv.asn.au> wrote:
On Sun, Sep 06, 2020 at 07:29:29PM +1000, Brian May wrote:
I realised that a computer where this just works has the latest Firefox which I downloaded from the Firefox website (now 80.0.1). Instead of the ESR version supplied with Debian (68.11.0esr).
68.11.0esr is what's in testing, right?
Current up to date Debian 10 has Firefox ESR 68.12.0 and no problems here. I have done very little customising, Also I do not invoke FF from an editor, emacs, vi, vim or otherwise. Updates are no longer through synaptic, because of Wayland, I su to root, then run apt-get update, apt-get upgrade. There are security issues with sudo, but in the right place, it can be a very valuable tool that I need to sort out enabling.
sid currently has 78.2.0esr
maybe try that?
or switch to firefox rather than firefox-esr. I think testing currently has 79.0. sid has 80.0.1
i used firefox-esr for a while until I had new versions of my plugins (or, at least, reasonable replacements for most of them), but i don't really see any point to firefox-esr now. It's moved past the version where xul plugins still worked, so it's just firefox but a few versions behind.
craig
ps: ewwww - upstream binaries. that's unhygienic.
Agreed, and it messes with the package management, which is one of the things I most appreciate about Debian and derivatives. I have lived through too much Microsoft dependency hell, and that the early RPM required manually sorting dependencies and manually adding to the command line.
-- craig sanders <cas@taz.net.au>
Regards, Mark Trickett
Craig Sanders via luv-main <luv-main@luv.asn.au> writes:
ps: ewwww - upstream binaries. that's unhygienic.
Regardless probably worth trying just in case Debian accidentally broke something. But like I said this happens with all versions of Firefox I have tried - upstream and Debian and a number of different versions. -- Brian May <brian@linuxpenguins.xyz> https://linuxpenguins.xyz/brian/
participants (6)
-
Alexar Pendashteh -
bnis＠fastmail.fm -
Brian May -
Craig Sanders -
Glenn McIntosh -
Mark Trickett