Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 713094 - net-im/slack-4.3.2-r2: /opt/slack/chrome-sandbox doesn't have correct permission flags
Summary: net-im/slack-4.3.2-r2: /opt/slack/chrome-sandbox doesn't have correct permiss...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: AMD64 Linux
: Normal normal (vote)
Assignee: Vladimir Pavljuchenkov (SpiderX)
URL:
Whiteboard:
Keywords: PullRequest
Depends on:
Blocks:
 
Reported: 2020-03-18 00:44 UTC by shunlir
Modified: 2020-12-04 20:48 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge-info.txt (emerge-info.txt,5.54 KB, text/plain)
2020-03-18 00:44 UTC, shunlir
Details

Note You need to log in before you can comment on or make changes to this bug.
Description shunlir 2020-03-18 00:44:53 UTC
Created attachment 621150 [details]
emerge-info.txt

After install/upgrade of net-im/slack-bin, run slack-bin as normal user, it can't launch, the following errors are printed:

[5436:0318/083721.389684:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/slack/chrome-sandbox is owned by root and has mode 4755.
Comment 1 Vladimir Pavljuchenkov (SpiderX) 2020-03-22 12:36:04 UTC
On my system slack is not used chrome-sandbox at all.
And I have never heard about any issues with it.
However, slack indeed delivers it in official packages with suid bit enabled.


shunlir, 

1. Could you try to run slack with --no-sandbox option like "slack --no-sandbox" and share results you will get?

2. Could you try to install this ebuild https://github.com/SpiderX/portage-overlay/blob/master/net-im/slack-bin/slack-bin-4.3.2-r3.ebuild into local overlay (https://wiki.gentoo.org/wiki/Custom_repository) and emerge it with USE flag suid enabled? Will it help?

Thanks.
Comment 2 Larry the Git Cow gentoo-dev 2020-04-30 12:00:18 UTC
The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=62f6390e5f3889e177464e0c0d31cc93a25c179d

commit 62f6390e5f3889e177464e0c0d31cc93a25c179d
Author:     Vladimir Pavljuchenkov (SpiderX) <spiderx@spiderx.dp.ua>
AuthorDate: 2020-04-27 08:28:38 +0000
Commit:     Joonas Niilola <juippis@gentoo.org>
CommitDate: 2020-04-30 11:59:57 +0000

    net-im/slack: rework QA_PREBUILT, version bump to 4.4.2, wrt 713094
    
    Closes: https://bugs.gentoo.org/716638
    Closes: https://bugs.gentoo.org/713094
    Package-Manager: Portage-2.3.89, Repoman-2.3.20
    Signed-off-by: Vladimir Pavljuchenkov <spiderx@spiderx.dp.ua>
    Closes: https://github.com/gentoo/gentoo/pull/15543
    Signed-off-by: Joonas Niilola <juippis@gentoo.org>

 net-im/slack/Manifest           |   1 +
 net-im/slack/slack-4.4.2.ebuild | 106 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 107 insertions(+)
Comment 3 Alex Efros 2020-11-03 00:33:17 UTC
(In reply to Vladimir Pavljuchenkov (SpiderX) from comment #1)
> 1. Could you try to run slack with --no-sandbox option like "slack
> --no-sandbox" and share results you will get?

I've the same issue:

$ qlist -Iv slack
net-im/slack-4.4.3
$ slack
[5000:1103/023148.258617:FATAL:setuid_sandbox_host.cc(157)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/slack/chrome-sandbox is owned by root and has mode 4755.
[1]    5000 trace trap  slack
$ slack --no-sandbox
Works okay.
Comment 4 Vladimir Pavljuchenkov (SpiderX) 2020-12-04 20:48:12 UTC
Alex Efros, let continue in https://bugs.gentoo.org/738232