Slack 4.7.0 sefgault ubuntu 18.04

interface · July 8, 2020, 12:56pm

Hello,

After updating slack to version slack 4.7.0 25 latest/stable slack✓ classic on ubuntu 18.04 the application is no longer able to open and terminates with the following segfault errors:

Jul 08 08:41:03 parker-XPS-13-9300 kernel: ThreadPoolForeg[8705]: segfault at 1b8 ip 00007f922fe1775c sp 00007f921d28dd70 error 4 in ld-2.23.so[7f922fe0b000+26000]
Jul 08 08:41:03 parker-XPS-13-9300 kernel: Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 
Jul 08 08:41:03 parker-XPS-13-9300 kernel: ThreadPoolForeg[8726]: segfault at 1b8 ip 00007f922fe1775c sp 00007f921d28dd70 error 4 in ld-2.23.so[7f922fe0b000+26000]
Jul 08 08:41:03 parker-XPS-13-9300 kernel: Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 
Jul 08 08:41:03 parker-XPS-13-9300 kernel: ThreadPoolForeg[8734]: segfault at 1b8 ip 00007f922fe1775c sp 00007f921d28dd70 error 4 in ld-2.23.so[7f922fe0b000+26000]
Jul 08 08:41:03 parker-XPS-13-9300 kernel: Code: 41 c1 e1 02 81 e2 ff 7f 00 00 41 09 c1 4d 89 bc 24 f8 03 00 00 48 8d 14 52 45 89 8c 24 00 04 00 00 4c 8d 04 d6 4d 85 c0 74 0f <41> 8b 40 08 85 c0 b8 00 00 00 00 4c 0f 44 c0 41 
Jul 08 08:41:03 parker-XPS-13-9300 gnome-shell[2504]: [AppIndicatorSupport-DEBUG] Registering StatusNotifierItem :1.92/org/ayatana/NotificationItem/Slack1
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8748]: segfault at caf0 ip 000000000000caf0 sp 00007f921ef61df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8774]: segfault at caf0 ip 000000000000caf0 sp 00007f921ef61df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8782]: segfault at caf0 ip 000000000000caf0 sp 00007f921ef61df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8791]: segfault at caf0 ip 000000000000caf0 sp 00007f921f2e2df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8800]: segfault at caf0 ip 000000000000caf0 sp 00007f921f2e2df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:04 parker-XPS-13-9300 pkexec[8814]: pam_unix(polkit-1:session): session opened for user root by (uid=1001)
Jul 08 08:41:04 parker-XPS-13-9300 pkexec[8814]: parker: Executing command [USER=root] [TTY=unknown] [CWD=/home/parker] [COMMAND=/usr/lib/gnome-settings-daemon/gsd-backlight-helper --set-brightness 4800]
Jul 08 08:41:04 parker-XPS-13-9300 kernel: ThreadPoolForeg[8809]: segfault at caf0 ip 000000000000caf0 sp 00007f921f2e2df8 error 14
Jul 08 08:41:04 parker-XPS-13-9300 kernel: Code: Bad RIP value.
Jul 08 08:41:05 parker-XPS-13-9300 kernel: traps: Chrome_IOThread[8668] trap int3 ip:562f367c81c4 sp:7f8b8ec217e0 error:0 in slack[562f3433c000+5caf000]
Jul 08 08:41:05 parker-XPS-13-9300 gnome-shell[2504]: Object .Gjs_AppIndicatorIconActor__1 (0x55e850120e20), has been already finalized. Impossible to set any property to it.
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: == Stack trace for context 0x55e84b916330 ==
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #0 0x7fff2785af00 I   resource:///org/gnome/gjs/modules/_legacy.js:83 (0x7f7bf6eb5de0 @ 87)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #1 0x55e84bcb13e0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/indicatorStatusIcon.js:93 (0x7f7bf40c76f8 @ 58)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #2 0x7fff2785bae0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7bf6eb5de0 @ 71)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #3 0x7fff2785bba0 b   self-hosted:916 (0x7f7bf6ef12b8 @ 367)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #4 0x7fff2785bc20 I   resource:///org/gnome/gjs/modules/signals.js:128 (0x7f7bf6ed2230 @ 386)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #5 0x55e84bcb1358 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/appIndicator.js:190 (0x7f7bf40b63c8 @ 22)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #6 0x7fff2785c800 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7bf6eb5de0 @ 71)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #7 0x55e84bcb12b0 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:176 (0x7f7bf40b1670 @ 26)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #8 0x7fff2785d3e0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7bf6eb5de0 @ 71)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #9 0x55e84bcb1210 i   /usr/share/gnome-shell/extensions/ubuntu-appindicators@ubuntu.com/statusNotifierWatcher.js:170 (0x7f7bf40b15e8 @ 68)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #10 0x7fff2785dfd0 I   resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f7bf6eb5de0 @ 71)
Jul 08 08:41:05 parker-XPS-13-9300 org.gnome.Shell.desktop[2504]: #11 0x7fff2785e0a0 b   self-hosted:918 (0x7f7bf6ef12b8 @ 394)

Cheers

ptcar2009 · July 8, 2020, 3:18pm

Same here. Ubuntu 20.04.

Installing it through the .deb in the official slack downloads page worked, if you need to use it it works.

daniel · July 8, 2020, 3:34pm

It looks like the problem is with the --no-sandbox flag that is passed by $SNAP/command-slack.wrapper. Manually running the command without that flag fixes the issue, but that’s not helpful for regular users that aren’t going to want to be messing with commandline hacking

@advocacy this might be something for you to follow-up on?

Specifically, from snap run --shell slack, this works:

$SNAP/usr/lib/slack/slack

While this crashes:

$SNAP/usr/lib/slack/slack --no-sandbox

acrq · July 8, 2020, 6:53pm

I’m also seeing this on Ubuntu 20.04.

Can also confirm that installing via .deb file works

mr.AlexZT · July 9, 2020, 8:41am

Also crashed on Ubuntu 20.04 LTS

Distributor ID:	Ubuntu
Description:	Ubuntu 20.04 LTS
Release:	20.04
Codename:	focal

Linux is 5.4.0-40-generic #44-Ubuntu SMP Tue Jun 23 00:01:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

slack 4.7.0 25 latest/stable slack* classic

    Jul  9 11:17:30 is systemd[2264]: Started Application launched by gnome-shell.
    Jul  9 11:17:35 is dbus-daemon[711]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.181' (uid=1000 pid=17856 comm="/snap/slack/25/usr/lib/slack/slack --no-sandbox --" label="snap.slack.slack (complain)")
    Jul  9 11:17:35 is systemd[1]: Condition check resulted in Bluetooth service being skipped.
    Jul  9 11:17:37 is kernel: [ 7917.944801] ThreadPoolForeg[17934]: segfault at 34d0 ip 00000000000034d0 sp 00007efee74ace08 error 14
    Jul  9 11:17:37 is kernel: [ 7917.944807] Code: Bad RIP value.
    Jul  9 11:17:39 is kernel: [ 7919.595715] ThreadPoolForeg[17956]: segfault at 34d0 ip 00000000000034d0 sp 00007efee74ace08 error 14
    Jul  9 11:17:39 is kernel: [ 7919.595721] Code: Bad RIP value.
    Jul  9 11:17:39 is kernel: [ 7920.482820] ThreadPoolForeg[17971]: segfault at 34d0 ip 00000000000034d0 sp 00007efee74ace08 error 14
    Jul  9 11:17:39 is kernel: [ 7920.482829] Code: Bad RIP value.
    Jul  9 11:17:42 is kernel: [ 7922.904158] ThreadPoolForeg[17995]: segfault at 34d0 ip 00000000000034d0 sp 00007efee7833e08 error 14
    Jul  9 11:17:42 is kernel: [ 7922.904172] Code: Bad RIP value.
    Jul  9 11:17:42 is kernel: [ 7923.504971] ThreadPoolForeg[18005]: segfault at 34d0 ip 00000000000034d0 sp 00007efee7833e08 error 14
    Jul  9 11:17:42 is kernel: [ 7923.504979] Code: Bad RIP value.
    Jul  9 11:17:43 is kernel: [ 7924.022205] ThreadPoolForeg[18013]: segfault at 34d0 ip 00000000000034d0 sp 00007efee7833e08 error 14
    Jul  9 11:17:43 is kernel: [ 7924.022215] Code: Bad RIP value.
    Jul  9 11:17:43 is kernel: [ 7924.303063] traps: Chrome_IOThread[17866] trap int3 ip:5622f5a8e1c4 sp:7f81639937e0 error:0 in slack[5622f3602000+5caf000]
    Jul  9 11:17:44 is systemd[2264]: gnome-launched-slack_slack.desktop-17840.scope: Succeeded.

Gargoyle · July 9, 2020, 10:02am

Same here!

Was working on Tuesday.

Gargoyle · July 9, 2020, 10:07am

Its a good job this got plenty of testing on the edge channel first…

channels:
  latest/stable:    4.7.0 2020-07-07 (25) 151MB classic
  latest/candidate: ↑                           
  latest/beta:      ↑                           
  latest/edge:      3.3.1 2018-08-31  (8) 148MB classic
installed:          4.7.0            (25) 151MB classic

ogra · July 9, 2020, 12:05pm

note that if you had a working version installed last, you should theoretically be able to run:

sudo snap revert slack

to go back to the last working version (havent ever tried that with classic snaps, which is why i said "theoretically ) …

daniel · July 9, 2020, 12:07pm

seems to have worked for me yey

troyready · July 9, 2020, 4:15pm

Also affecting me on 20.04 - sudo snap revert slack'd back to v4.4.3 to get it to launch again.

lizthegrey · July 9, 2020, 10:00pm

Also affecting me on 20.04. Have reported it via slack /feedback once reverted.

odc · July 10, 2020, 7:28pm

Same here, I had to revert to the previous version for Slack to start. Also reported via /feedback and I would suggest for everyone to do the same.

tonyarnold99 · July 19, 2020, 11:40am

I’m having the same problem. Is there any way to edit the command-slack.wrapper file inside the snap without rebuilding the snap? Even as root vim says it’s a read-only file.

ogra · July 19, 2020, 1:39pm

copy the file somewhere writable … then edit it … then use

mount --bind /path/to/edited/file /original/path/where/you/copied/it/from

(this indeed only works once but it a good step for debugging or adding env vars etc)

daniel · July 19, 2020, 4:40pm

That will also only work on classic snaps because they don’t use a separate mount namespace. As this is classic you might be able to just run the command directly instead of editing the file.

ogra · July 19, 2020, 4:58pm

i use it all the time on Ubuntu Core … it works just fine with strict snaps …

daniel · July 19, 2020, 6:21pm

Odd. I thought for sure that the mount namespace would obscure this…

ogra · July 19, 2020, 6:22pm

i dont think it does for anyting in $SNAP …

Gargoyle · July 28, 2020, 1:56pm

Work-arounds are all very well and good, I’m just curious as if any progress has been made on the actual problem - which is Slack not bothering to use the development and testing channels and as far as I can tell, have still not fixed the snap! (snap info slack is telling me its stil 4.7.0 from the 7th July - I actually removed the snap and installed the deb)