Bug 2230588 - firefox-x11 crashes on start in Wayland session
Summary: firefox-x11 crashes on start in Wayland session
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-09 16:50 UTC by Christian Stadelmann
Modified: 2024-11-27 21:27 UTC (History)
6 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-11-27 21:27:16 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Christian Stadelmann 2023-08-09 16:50:16 UTC
When trying to start firefox-x11 in a GNOME/Wayland session, it immediately aborts.

Reproducible: Always

Steps to Reproduce:
1. Log in to a GNOME/Wayland session
2. Open a terminal
3. execute `$ firefox-x11 --safe-mode --Profile-Manager --new-instance`
Actual Results:  
Firefox does not start. Instead, I get this output:
```
Authorization required, but no authorization protocol specified
Error: cannot open display: :0
```

Expected Results:  
Start firefox. This works fine when using `firefox` instead of `firefox-x11`, e.g. with this command line `$ firefox --safe-mode --Profile-Manager --new-instance`

Note: I have not tried this with previous versions of Firefox, I have tried this only because https://fedoraproject.org/wiki/How_to_debug_Firefox_problems refers to firefox-x11, so I expected it to work.

Installed software versions:
firefox-116.0-2.fc38.x86_64
gtk3-3.24.38-1.fc38.x86_64
gnome-shell-44.3-1.fc38.x86_64
libwayland-client-1.22.0-1.fc38.x86_64
libX11-1.8.6-1.fc38.x86_64
cairo-1.17.8-4.fc38.x86_64
libXcomposite-0.4.5-9.fc38.x86_64
libXdamage-1.1.5-9.fc38.x86_64
libXext-1.3.5-2.fc38.x86_64
libXfixes-6.0.0-5.fc38.x86_64
libXrandr-1.5.2-10.fc38.x86_64
libXtst-1.2.4-2.fc38.x86_64
libxcb-1.13.1-11.fc38.x86_64

Comment 1 Fedora Release Engineering 2023-08-16 08:14:08 UTC
This bug appears to have been reported against 'rawhide' during the Fedora Linux 39 development cycle.
Changing version to 39.

Comment 2 Martin Stransky 2023-08-17 19:08:19 UTC
Error: cannot open display: :0 means you're missing running X server. Can you try Gnome on X.org?

Comment 3 Aoife Moloney 2024-11-08 11:01:24 UTC
This message is a reminder that Fedora Linux 39 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 39 on 2024-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '39'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 39 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 4 Aoife Moloney 2024-11-27 21:27:16 UTC
Fedora Linux 39 entered end-of-life (EOL) status on 2024-11-26.

Fedora Linux 39 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


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