Description of problem: chromium-browser does not start, due to wronge permissions of chrome-sandbox (755 instead of 4755) Message when started in shell: [1802:1802:1118/192253:FATAL:setuid_sandbox_client.cc(282)] 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 /usr/lib64/chromium-browser/chrome-sandbox is owned by root and has mode 4755. LC_ALL=C stat /usr/lib64/chromium-browser/chrome-sandbox File: '/usr/lib64/chromium-browser/chrome-sandbox' Size: 19880 Blocks: 40 IO Block: 4096 regular file Device: 806h/2054d Inode: 919948 Links: 1 Access: (0755/-rwxr-xr-x) Uid: ( 0/ root) Gid: ( 0/ root) Changing permissions of chrome-sandbox to 4755 starts chromium as expected. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Reproducible: Steps to Reproduce:
I'll upload (needs a freeze push) chromium 39 with fixed permissions ASAP. We still don't know why this changed (rpmbuild now resets permissions while building a package).
Status: NEW => ASSIGNEDCC: (none) => cjwAssignee: bugsquad => cjw
Christiaan, just in case you hadn't noticed, I already fixed this issue in SVN. Lutz, this will be fixed when 39 is uploaded. Currently the upstream tarball is not yet available. Christiaan, you may have seen that I mentioned this on the dev list. Any thoughts? Hopefully we can find and fix any other affected packages. https://ml.mageia.org/l/arc/dev/2014-11/msg00454.html
(In reply to David Walser from comment #2) > Christiaan, just in case you hadn't noticed, I already fixed this issue in > SVN. Thanks, I had an additional space in my version which I didn't like, so pulled your change. > Christiaan, you may have seen that I mentioned this on the dev list. Any > thoughts? Hopefully we can find and fix any other affected packages. > https://ml.mageia.org/l/arc/dev/2014-11/msg00454.html I was referring to that mail. How to find such packages... I only came up with two ways so far: either do rpmdiff of autobuilder output with cauldron RPMs, or check permissions in RPMs against those specified in the spec files %files section. I don't think already broken packages packages can be detected other than by e.g. running into problems caused by the permission change. This bug should now be fixed with chromium-browser-stable 39.0.2171.65-1.mga5, closing.
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED