[Sway] firefox locks up 100% consistently on wayland
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: hholst80, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36 OPR/105.0.0.0
Steps to reproduce:
firefox --version
Mozilla Firefox 120.0.1
Start firefox. Right click on the canvas.
Actual results:
Firefox freezes. Check the attached logs.
[1660282.095] wl_callback@52.done(37470375)
[1660282.102] -> wl_surface@59.frame(new id wl_callback@52)
[1660282.106] -> wl_surface@59.commit()
[1660286.988] -> wl_compositor@5.create_surface(new id wl_surface@64)
[1660287.264] -> wl_surface@59.frame(new id wl_callback@48)
[1660287.272] -> wl_surface@59.commit()
Expected results:
Well, not freeze. Business as usual.
Same thing with firefox-esr (v115.5.0)
https://pasteboard.co/2yj2WkPEeaF9.png
firefox-esr --version
Mozilla Firefox 115.5.0esr
[2474017.936] wl_pointer@20.motion(38256343, 257.71875000, 838.27343750)
[2474018.673] -> wl_surface@59.set_buffer_scale(2)
[2474018.688] -> wl_compositor@34.create_surface(new id wl_surface@61)
[2474018.694] -> wl_subcompositor@35.get_subsurface(new id wl_subsurface@57, wl_surface@61, wl_surface@59)
[2474018.699] -> wl_subsurface@57.set_desync()
[2474018.704] -> wl_surface@59.frame(new id wl_callback@58)
[2474018.708] -> wl_surface@61.commit()
[2474018.717] -> wl_surface@61.attach(nil, 0, 0)
[2474018.721] -> wl_surface@61.set_buffer_scale(2)
[2474018.726] -> wl_compositor@34.create_region(new id wl_region@71)
[2474018.730] -> wl_surface@61.set_input_region(wl_region@71)
[2474018.734] -> wl_region@71.destroy()
[2474018.753] -> xdg_wm_base@27.create_positioner(new id xdg_positioner@72)
[2474018.758] -> xdg_positioner@72.set_size(219, 254)
[2474018.762] -> xdg_positioner@72.set_anchor_rect(461, 492, 1, 1)
[2474018.767] -> xdg_positioner@72.set_offset(-2, -2)
[2474018.771] -> xdg_positioner@72.set_anchor(8)
[2474018.776] -> xdg_positioner@72.set_gravity(8)
[2474018.780] -> xdg_positioner@72.set_constraint_adjustment(61)
[2474018.784] -> xdg_wm_base@27.get_xdg_surface(new id xdg_surface@73, wl_surface@59)
[2474018.789] -> xdg_surface@73.get_popup(new id xdg_popup@74, xdg_surface@54, xdg_positioner@72)
[2474018.794] -> xdg_positioner@72.destroy()
[2474018.798] -> wl_surface@59.commit()
Gdk-Message: 11:19:55.909: Lost connection to Wayland compositor.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
|
||
Comment 2•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
I was able to unblock this by pressing CTRL+ALT+F1 to switch to tty1 and back to tty2 (wayland). Interesting. After the switch it seems that the problem does not appear again in that Firefox window. knock on wood
I see you use Sway. Can you try different compositor in tested mode?
https://fedoraproject.org/wiki/How_to_debug_Firefox_problems#Testing_different_Wayland_compositor
Thanks.
As far fetched as it might sound, I was able to resolve this by uninstalling pipewire, pipewire-pulse, and wireplumber. Instead I installed the pulseaudio stack. I tried this solution on both Artix (Arch derived) and Fedora 38 and it resolved the problem on both systems. I run sway on both systems with almost identical setup including an AMD PEG. I have another laptop that I need to reinstall. I can try and use pipewire et al on that machine too and see if I run into the same problem, and if it is resolved by switching to pulseaudio. However, that system has a Nvidia GPU. On the laptop where I have not observed this problem (that run the same software) I have an Intel IGPU. If I cannot trigger this issue on Nvidia I will try the pipewire stack again on my workstation. I just want to enjoy the feeling a bit of having a working system before I ahead and break it. ;-)
I use sound over HDMI/Displayport so I guess it is possible that it could be the reason on some level. But it sounds almost crazy.
|
|
||
Comment 7•1 year ago
|
||
A needinfo is requested from the reporter, however, the reporter is inactive on Bugzilla. Given that the bug is still UNCONFIRMED, closing the bug as incomplete.
For more information, please visit BugBot documentation.
Description
•