1555308 - [wayland] Firefox won't start without --no-remote

Status: RESOLVED DUPLICATE of bug 1551664

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

Description

[luis.pabon]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Steps to reproduce:

On wayland, firefox nightly won't start unless --no-remote is specified.

Ubuntu 19.04
Firefox nightly (69.0a1hg20190528r475793-0ubuntu0.19.04.1~umd1) from mozilla's PPA.
Sway 1.1rc2
libdbus 1.12.12-1ubuntu1
libdbus-glib 0.110-4
dbus 1.12.12-1ubuntu1
dbus-user-session 1.12.12-1ubuntu1
dbus-x11 1.12.12-1ubuntu1

~ ps aux|grep dbus                                                                                                                                            
message+  1136  0.0  0.0   8744  5848 ?        Ss   May24   5:05 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root      1175  0.0  0.0 133796  9812 ?        Ssl  May24   0:17 /usr/sbin/thermald --no-daemon --dbus-enable
luis      1938  0.0  0.0   8076  5396 ?        Ss   May24   3:36 /usr/bin/dbus-daemon --session --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
luis      1963  0.0  0.0   7136  4340 ?        S    May24   0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
luis      4798  0.0  0.0  18748   904 pts/3    S+   12:49   0:00 grep --color=auto dbus
luis     15597  0.0  0.0   7132  3016 ?        Ss   May24   0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
luis     15896  0.0  0.0   7136  3016 ?        Ss   May24   0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session
luis     16040  0.0  0.0   7268  3192 ?        Ss   May24   0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 4 --print-address 6 --session
luis     16082  0.0  0.0   7008  3704 ?        S    May24   0:00 /usr/bin/dbus-daemon --config-file=/usr/share/defaults/at-spi2/accessibility.conf --nofork --print-address 3
luis     16448  0.0  0.0   7136  2980 ?        Ss   May24   0:00 /usr/bin/dbus-daemon --syslog --fork --print-pid 5 --print-address 7 --session

Actual results:

~ env MOZ_ENABLE_WAYLAND=1 firefox-trunk  
dbus[29338]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../../dbus/dbus-message.c line 1366.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Redirecting call to abort() to mozalloc_abort

fish: “env MOZ_ENABLE_WAYLAND=1 firefo…” terminated by signal SIGSEGV (Address boundary error)

Expected results:

Firefox should've opened and worked normally

Comment 1

[luis.pabon]

With --no-remote, firefox opens if it isn't already running.

When clicking a link outside ff (ff-trunk is set as default browser), an error dialog appears saying

Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system.

Emulating that on the command line produces no output.

Comment 2

[Martin Stránský [:stransky] (ni? me)]

Yes, it's related to profile name which is used by DBUS to identify Firefox instance on Wayland. I expect the new profile changes broke it.

Comment 3

[luis.pabon]

Thank you. I can confirm this is not an issue on current stable (v67).

Comment 4

[Martin Stránský [:stransky] (ni? me)]

Hm, I'm unable to reproduce with upstream binaries or with my custom debug build. Is that under sway compositor? Can you try Gnome for instance?

Comment 5

[luis.pabon]

I can confirm this happens when run from either Gnome 3.32 in Wayland or Sway 1.1-rc3:

 ~ env MOZ_ENABLE_WAYLAND=1 firefox-trunk  
dbus[7986]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../../dbus/dbus-message.c line 1366.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Redirecting call to abort() to mozalloc_abort

fish: “env MOZ_ENABLE_WAYLAND=1 firefo…” terminated by signal SIGSEGV (Address boundary error)
~ env|grep XDG 
XDG_CURRENT_DESKTOP=ubuntu:GNOME
XDG_DATA_DIRS=:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/local/share:/usr/share:/var/lib/snapd/desktop
XDG_MENU_PREFIX=gnome-
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=ubuntu-wayland
XDG_SESSION_ID=11
XDG_SESSION_TYPE=wayland
XDG_VTNR=2

Comment 6

[luis.pabon]

On sway:

 ~ env MOZ_ENABLE_WAYLAND=1 firefox-trunk   
dbus[9203]: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file ../../../dbus/dbus-message.c line 1366.
This is normally a bug in some application using the D-Bus library.

  D-Bus not built with -rdynamic so unable to print a backtrace
Redirecting call to abort() to mozalloc_abort

fish: “env MOZ_ENABLE_WAYLAND=1 firefo…” terminated by signal SIGSEGV (Address boundary error)
~ env|grep XDG          
XDG_DATA_DIRS=:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/local/share:/usr/share:/var/lib/snapd/desktop
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_ID=13
XDG_SESSION_TYPE=tty
XDG_VTNR=3

Comment 7

[luis.pabon]

I can also confirm the issue does not happen when running off the nightly binaries as downloaded from firefox's website. Could to be an issue with the way ff is built for the mozilla ppa perhaps?

Comment 8

[Martin Stránský [:stransky] (ni? me)]

(In reply to luis.pabon from comment #7)

I can also confirm the issue does not happen when running off the nightly
binaries as downloaded from firefox's website. Could to be an issue with the
way ff is built for the mozilla ppa perhaps?

Yes, seems to be caused by this.

Comment 9

[luis.pabon]

Martin, when using the binaries from ff's website I can start with no remote, but opening links from external apps still doesn't work. Might be related to this I also reported? https://bugzilla.mozilla.org/show_bug.cgi?id=1561878

Comment 10

[luis.pabon]

Attachment: coredump & bt

```
~

Comment 11

[Jan Alexander Steffens [:heftig]]

I think this is a duplicate of bug 1551664. Is the Ubuntu build changing the remoting name?

If you have trouble reproducing, try the upstream dev edition builds, as these are affected by the above bug.

Comment 12

[luis.pabon]

The firefox builds on the beta ppa aren't affected by this. I'm using these after they swapped to FF69 as they have more than adequate wayland support.
The main difference in those ppas from my point of view is that the beta version supersedes Ubuntu's stable versions instead of installing as a separate app (firefox vs firefox-trunk).

Comment 13

[Martin Stránský [:stransky] (ni? me)]

Dupe of Bug 1551664.