Open Bug 1404540 Opened 2 years ago Updated 6 months ago

"Make Default..." does nonsense, sets browser to Thunderbird and breaks xdg-open on URLs


(Firefox :: Shell Integration, defect, P2)






(Reporter: jtcode, Unassigned)




(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0
Build ID: 20170929100122

Steps to reproduce:

1. Go to about:preferences#general
2. Click "Make Default..."

Actual results:

xdg-open on URLs is now broken (terminates without anything happening, nothing opens), gnome-shell settings show that "Thunderbird" is set in "Default Applications" for "Web"

Expected results:

Nightly is correctly set as web browser for opening URLs
Firefox version is 58, which was unavailable from the Version dropdown for some reason.
I forgot to mention this, but I have seen this bug sporadically for a really long time probably going back to Firefox 35 or something. I have only now had a screen recorder installed of which I knew how to use it, so that I could record it happening live. Therefore, it's probably not a recent regression if that info helps in any way with locating the underlying issue.
Component: Untriaged → Widget: Gtk
Product: Firefox → Core
OS: Unspecified → Linux
Priority: -- → P2
Component: Widget: Gtk → Shell Integration
Product: Core → Firefox
See Also: → 1404295
not sure what gnome does or expects but "Make Default..." does work (with any WM)

not sure what gnome does or expects but "Make Default..." does work (with any WM)

No, sometimes it absolutely doesn't. That is why I filed this bug.

Just had this happen again, firefox developer edition prompted this dialog despite being the default and "Make default..." made it set thunderbird(!) as a default and then clicking a link from within thunderbird itself leads to tons of confused background idling thunderbird instances called with the URL. After launching firefox developer edition again manually the dialog came up AGAIN, and "Make default..." fixed it again.

So no, this is still broken. And it is quite annoying when it happens

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