Add Mozilla dbus_gmain implementation
Categories
(Core :: Widget: Gtk, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox-esr115 | --- | unaffected |
firefox117 | --- | unaffected |
firefox118 | --- | unaffected |
firefox119 | + | fixed |
People
(Reporter: bbhtt.zn0i8, Assigned: stransky)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file, 2 obsolete files)
59.13 KB,
application/json
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/119.0
Steps to reproduce:
- Select Nightly as the default browser in GNOME Settings or in about:preferences and launch it
- Try to click a link from another application
- The dialogue saying another instance is running or busy pops up.
Actual results:
The link didn't open in the launched instance
Expected results:
The link should've opened in the launched instance
$ mozregression --good 2023-09-03 --bad 2023-09-04
5:36.16 INFO: Last good revision: 931ad71c21b535e0098402b172e975de27c9b4e2
5:36.16 INFO: First bad revision: 8be358911e03871f9359b2e8de91daf5a01d37ec
5:36.16 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=931ad71c21b535e0098402b172e975de27c9b4e2&tochange=8be358911e03871f9359b2e8de91daf5a01d37ec
Seems like a change from https://bugzilla.mozilla.org/show_bug.cgi?id=1532281 is at fault.
I'm running it on GNOME 45 beta (Fedora 39 beta) wayland, Nightly as native wayland but other people #nightly have reported it on XFCE too
Updated•1 year ago
|
Comment 4•1 year ago
|
||
[Tracking Requested - why for this release]: significant regression for linux users
Updated•1 year ago
|
Comment 5•1 year ago
|
||
The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.
Comment 6•1 year ago
|
||
The bug is marked as tracked for firefox119 (nightly). However, the bug still isn't assigned.
:gcp, could you please find an assignee for this tracked bug? Given that it is a regression and we know the cause, we could also simply backout the regressor. If you disagree with the tracking decision, please talk with the release managers.
For more information, please visit BugBot documentation.
Comment 7•1 year ago
|
||
:stransky while you're investigating, do you think you'll have a fix for this today or should I request back out of the regressor?
Assignee | ||
Comment 8•1 year ago
|
||
Yes, we just need to put back the dbus_connection_setup_with_g_main() calls.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 9•1 year ago
|
||
Untill all DBus code is migrated to GIO we need to provide internal dbus_connection_setup_with_g_main() implementation to get DBus messages from system.
Updated•1 year ago
|
Assignee | ||
Comment 10•1 year ago
|
||
Depends on D187453
Comment 11•1 year ago
|
||
Set release status flags based on info from the regressing bug 1532281
Updated•1 year ago
|
Comment 12•1 year ago
|
||
Setting 119 to fixed, the regressor was backed out of central https://bugzilla.mozilla.org/show_bug.cgi?id=1532281#c16
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Description
•