Summary: | net-im/slack-4.13.0 crashes with /dev/shm related error | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alex Efros <powerman-asdf> |
Component: | Current packages | Assignee: | Vladimir Pavljuchenkov (SpiderX) <spiderx> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | contact, proxy-maint, sam |
Priority: | Normal | Keywords: | PullRequest |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://github.com/electron/electron/issues/30758 | ||
See Also: | https://github.com/gentoo/gentoo/pull/26950 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alex Efros
2021-02-22 10:27:20 UTC
Please show the following from affected system: 1. grep 'shm' /proc/mounts 2. df -h | grep shm Try to launch it with wiped ~/.config/Slack (In reply to Vladimir Pavljuchenkov (SpiderX) from comment #1) > Please show the following from affected system: > > 1. grep 'shm' /proc/mounts shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0 shm /var/lib/docker/containers/e28f114e392f08556c8d0c8c8963dd553360f30cbbd311a829472f3cbda4c81f/mounts/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=65536k 0 0 > 2. df -h | grep shm shm 12G 345M 12G 3% /dev/shm shm 64M 0 64M 0% /var/lib/docker/containers/e28f114e392f08556c8d0c8c8963dd553360f30cbbd311a829472f3cbda4c81f/mounts/shm > Try to launch it with wiped ~/.config/Slack This doesn't change anything. Try to stop your docker container where you mounted shm and try once again to launch slack. (In reply to Vladimir Pavljuchenkov (SpiderX) from comment #3) > Try to stop your docker container where you mounted shm and try once again > to launch slack. It was a swaggerapi/swagger-editor container. I can't see how it might affect slack, but I've stopped and removed it, checked no one else is using shm, and tried to run slack - no change, same error and it didn't work. I too have been having this problem and have downgraded to 4.12.2 for the time being. I can provide any output or logs that may be necessary. Running Gentoo Testing. No Docker installed. $ ls -ld /dev/shm drwxrwxrwt 2 root root 60 Mar 11 08:06 /dev/shm $ grep 'shm' /proc/mounts shm /dev/shm tmpfs rw,nosuid,nodev,noexec,relatime 0 0 $ df -h | grep shm shm 7.6G 194M 7.4G 3% /dev/shm Removing my slack configuration directory didn't change anything. How is it happens 4.13.0 is now the only version in portage without fixing this bug first? The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=16fdaa4df3c9d0e66105c6855461f9314d75caba commit 16fdaa4df3c9d0e66105c6855461f9314d75caba Author: Joonas Niilola <juippis@gentoo.org> AuthorDate: 2021-03-20 16:03:28 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2021-03-20 16:03:51 +0000 net-im/slack: restore 4.12.2 Bug: https://bugs.gentoo.org/772137 Signed-off-by: Joonas Niilola <juippis@gentoo.org> net-im/slack/Manifest | 1 + net-im/slack/slack-4.12.2.ebuild | 98 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 99 insertions(+) hello, I've bumped 4.14.0, could you check if still have this problem? as I didn't checked this bug before, and prune out the 4.12.0 version .. btw, it sounds the 4.14.0 works great here .. (In reply to Yixun Lan from comment #8) > hello, I've bumped 4.14.0, could you check if still have this problem? Yes, 4.14.0 is still crashes with same error: [16782:0323/153826.797675:FATAL:platform_shared_memory_region_posix.cc(255)] This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo chmod 1777 /dev/shm' to fix. Unexpected crash report id length Failed to get crash dump id. Report Id: I see the tray icon (and even able to use it menu to Quit), but no main window. (In reply to Alex Efros from comment #10) > (In reply to Yixun Lan from comment #8) > > hello, I've bumped 4.14.0, could you check if still have this problem? > > Yes, 4.14.0 is still crashes with same error: > > [16782:0323/153826.797675:FATAL:platform_shared_memory_region_posix.cc(255)] > This is frequently caused by incorrect permissions on /dev/shm. Try 'sudo > chmod 1777 /dev/shm' to fix. > > Unexpected crash report id length > Failed to get crash dump id. > Report Id: > > I see the tray icon (and even able to use it menu to Quit), but no main > window. I believe it's a bug if the /dev/shm permission is not 1777, as the handbook also suggest this[1] could you check why or maybe file a bug for this? [1] https://wiki.gentoo.org/wiki/Handbook:AMD64/Full/Installation#Mounting_the_necessary_filesystems (In reply to Yixun Lan from comment #11) > I believe it's a bug if the /dev/shm permission is not 1777, as the handbook > also suggest this[1] > > could you check why or maybe file a bug for this? The permissions is 1777, problem is somewhere else. Please read first comment here, I've included all such details there. The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=adba580be72f0b3613d7237954532f9f6b6d58f6 commit adba580be72f0b3613d7237954532f9f6b6d58f6 Author: Yixun Lan <dlan@gentoo.org> AuthorDate: 2021-03-24 06:28:35 +0000 Commit: Yixun Lan <dlan@gentoo.org> CommitDate: 2021-03-24 06:33:17 +0000 net-im/slack: restore 4.12.2 for now Bug: https://bugs.gentoo.org/772137 Signed-off-by: Yixun Lan <dlan@gentoo.org> net-im/slack/Manifest | 1 + net-im/slack/slack-4.12.2.ebuild | 98 ++++++++++++++++++++++++++++++++++++++++ 2 files changed, 99 insertions(+) (In reply to Alex Efros from comment #12) > The permissions is 1777, problem is somewhere else. Please read first > comment here, I've included all such details there. since it's a binary release, so please report it to upstream for now, I just restore the old 4.12.2 version Still actual in 4.19.2. :( Upstream refuse to fix this because "Gentoo is not a supported distro". Looks like this is a sandbox-related issue, which can be fixed this way: 1. Unpack /opt/slack/resources/app.asar (using `npx asar extract app.asar destfolder`). 2. Edit extracted destfolder/dist/main.bundle.js to remove string "||external_electron_.app.enableSandbox()". 3. Pack it back into app.asap (using `npx asar pack destfolder app.asar`). Running `slack --no-sandbox` has no effect, not sure is this option supported or is there any other way to disable or somehow fix sandbox. With this flag it works without modifications: slack --disable-seccomp-filter-sandbox The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9c85489fe25a2cb24ac97e52af5a9118af326c03 commit 9c85489fe25a2cb24ac97e52af5a9118af326c03 Author: Vladimir Pavljuchenkov (SpiderX) <spiderx@spiderx.dp.ua> AuthorDate: 2022-08-21 15:40:04 +0000 Commit: Joonas Niilola <juippis@gentoo.org> CommitDate: 2022-08-31 08:39:14 +0000 net-im/slack: version bump to 4.27.156, wrt #836874, #772137, #853964 Closes: https://bugs.gentoo.org/836874 Closes: https://bugs.gentoo.org/772137 Closes: https://bugs.gentoo.org/853964 Package-Manager: Portage-3.0.30, Repoman-3.0.3 Signed-off-by: Vladimir Pavljuchenkov <spiderx@spiderx.dp.ua> Closes: https://github.com/gentoo/gentoo/pull/26950 Closes: https://github.com/gentoo/gentoo/pull/26744 Signed-off-by: Joonas Niilola <juippis@gentoo.org> net-im/slack/Manifest | 1 + net-im/slack/slack-4.27.156.ebuild | 110 +++++++++++++++++++++++++++++++++++++ 2 files changed, 111 insertions(+) |