Closed Bug 1416186 Opened 8 years ago Closed 8 years ago

Firefox crashes on start when wayland backend is selected

Categories

(Core :: Widget: Gtk, defect, P3)

Product:
Core
Component:
Widget: Gtk
Version:
58 Branch
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: mihailescu2m, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/604.3.5 (KHTML, like Gecko) Version/11.0.1 Safari/604.3.5 Steps to reproduce: start Firefox: GDK_BACKEND=wayland firefox Actual results: segmentation fault. trace: #0 0xb6ec5116 in __libc_do_syscall () at /lib/arm-linux-gnueabihf/libpthread.so.0 #1 0xb6ec4122 in raise () at /lib/arm-linux-gnueabihf/libpthread.so.0 #2 0xb2a13cca in nsProfileLock::FatalSignalHandler(int, siginfo_t*, void*) () at /usr/local/lib/firefox/libxul.so #3 0xb6c15890 in <signal handler called> () at /lib/arm-linux-gnueabihf/libc.so.6 #4 0xb61960f4 in XChangeProperty () at /usr/lib/arm-linux-gnueabihf/libX11.so.6 #5 0xb27fdff6 in XRemoteClient::DoSendCommandLine(unsigned long, int, char**, char const*, char**, bool*, char const*, char const*) () at /usr/local/lib/firefox/libxul.so #6 0xb27fe508 in XRemoteClient::SendCommandLine(char const*, char const*, char const*, int, char**, char const*, char**, bool*) () at /usr/local/lib/firefox/libxul.so #7 0xb2a192ae in XREMain::XRE_mainStartup(bool*) [clone .part.79] () at /usr/local/lib/firefox/libxul.so #8 0xb6f33ab8 in __stack_chk_guard () at /lib/ld-linux-armhf.so.3 Expected results: Firefox should have started
Component: Untriaged → Widget: Gtk
Product: Firefox → Core
We don't officially support Wayland, but we like to make sure it works. Martin, any ideas here?
Flags: needinfo?(stransky)
Priority: -- → P3
It might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1360566 So after these patches get in, I will check if it fixes this bug...
(In reply to Jim Mathies [:jimm] from comment #1) > We don't officially support Wayland, but we like to make sure it works. > Martin, any ideas here? Sure, we should not crash when user selects wayland backend but has wayland disabled build (which is default now). I'll post a patch for it. Firefox Wayland port is under development, tracking bug is Bug 635134
Blocks: wayland
Flags: needinfo?(stransky)
Summary: Firefox (Wayland) crashes on start → Firefox crashes on start when wayland backend is selected
Which version do you run? The "GDK_BACKEND=wayland" is silently ignored on Firefox 57 and exits on latest trunk: $ GDK_BACKEND=wayland ./firefox Error: cannot open display: :0
Flags: needinfo?(mihailescu2m)
I got it, it crashes only when there's a running X11 Firefox instance and you try to start another one under wayland backend.
Flags: needinfo?(mihailescu2m)
This crash was fixed by Bug 1409716.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED

@stransky I'm still getting:

GDK_BACKEND=wayland firefox
Error: cannot open display: :0

Same error here with "Mozilla Firefox 65.0" under "sway 1.0-RC1" using "wlroots 0.3".

You need to log in before you can comment on or make changes to this bug.