- User Since
- May 23 2018, 6:57 PM (245 w, 5 d)
Apr 4 2022
Feb 15 2022
Feb 3 2022
Jun 2 2020
So ... interestingly ... I now can't reproduce this. Here are my settings as asked anyway:
May 6 2020
Dec 22 2019
I've just retested this, and it's now working for me, including with hardware acceleration enabled in Firefox. Since I created this ticket, and no-one else seems to have the issue, I'm closing the ticket 'invalid'.
Oct 1 2019
Sep 3 2019
Thanks for the suggestion. Disabling hardware rendering in Firefox does make a subtle difference - reverts me to the original behaviour - the 1st frame is never rendered ( as opposed to *only* the 1st frame being rendered ). It also fixes that E-crash-on-resize that I mentioned in the above comment too. Current screenshot:
Sep 1 2019
Aug 26 2019
Switching back to previous priority ( as I've provided input ). Feel free to change priority if not appropriate ...
Aug 8 2019
did you run firefox and then took the logs? if so, there is still no error message. if not please run firefox before uploading dmesg and journalctl
Aug 7 2019
I've tried the default firefox and firefox-developer-edition with --g-fatal-warnings ... no errors or messages at all, unfortunately.
Aug 2 2019
Jul 29 2019
I've switched to Arch ( from Gentoo ) and can no longer reproduce this bug. I'm pretty sure it's still a bug, but I'm potentially the only one to ever encounter it, so I'm closing it. Feel free to re-open if you encounter it also ...
Jul 19 2019
I can no longer reproduce this crash. Closing 'invalid' ...
Jun 23 2019
Mar 31 2019
I haven't seen this issue for over a month, so I assume it was transitory. Closing 'Resolved' ...
I'm seeing behaviour that might be related. I'm working on a gtk3 app that renders some gtk3 menus in a menubar. When running under Wayland, the 1st time that an application window renders a menu, it appears slightly offscreen ( slightly too high ). If I close the menu and reopen it, nothing appears ( the parent menubar widget becomes highlighted, but no menu appears onscreen ). These menus, which are dynamically generated and appear in all windows, have the same issue in every window ... and we always see the same pattern of the 1st menu per window being slightly offscreen, and others completely invisible/offscreen.