Discussion:
oS 12.3 x86_64 Chromium update error
(too old to reply)
Carl Hartung
2014-09-27 00:19:40 UTC
Permalink
Hello All,

Here's the error:

Retrieving: chromium-desktop-kde-37.0.2062.94-1.55.3.x86_64.rpm ...
(1/2) Installing: chromium-37.0.2062.94-1.55.3 ...
Additional rpm output:
update-alternatives: using /usr/lib64/chromium/chromium-generic to provide /usr/bin/chromium (chromium) in auto mode
/usr/lib/chrome_sandbox: will not give away s-bits on an insecure path
ERROR: not all operations were successful.
setting /usr/lib/chrome_sandbox to root:root 4755. (wrong permissions 0755)
warning: %post(chromium-37.0.2062.94-1.55.3.x86_64) scriptlet failed,
exit status 1

Am I the only one?

TIA & regards,

Carl
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Patrick Shanahan
2014-09-27 00:24:20 UTC
Permalink
Post by Carl Hartung
Retrieving: chromium-desktop-kde-37.0.2062.94-1.55.3.x86_64.rpm ...
(1/2) Installing: chromium-37.0.2062.94-1.55.3 ...
update-alternatives: using /usr/lib64/chromium/chromium-generic to provide /usr/bin/chromium (chromium) in auto mode
/usr/lib/chrome_sandbox: will not give away s-bits on an insecure path
ERROR: not all operations were successful.
setting /usr/lib/chrome_sandbox to root:root 4755. (wrong permissions 0755)
warning: %post(chromium-37.0.2062.94-1.55.3.x86_64) scriptlet failed,
exit status 1
Am I the only one?
I was successful Tuesday on openSUSE-Factory
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://linuxcounter.net
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Carl Hartung
2014-09-27 01:20:08 UTC
Permalink
On Fri, 26 Sep 2014 20:24:20 -0400
Post by Patrick Shanahan
Post by Carl Hartung
Retrieving: chromium-desktop-kde-37.0.2062.94-1.55.3.x86_64.rpm ...
(1/2) Installing: chromium-37.0.2062.94-1.55.3 ...
update-alternatives: using /usr/lib64/chromium/chromium-generic to
provide /usr/bin/chromium (chromium) in auto
mode /usr/lib/chrome_sandbox: will not give away s-bits on an
insecure path ERROR: not all operations were successful.
setting /usr/lib/chrome_sandbox to root:root 4755. (wrong
%post(chromium-37.0.2062.94-1.55.3.x86_64) scriptlet failed, exit
status 1
Am I the only one?
I was successful Tuesday on openSUSE-Factory
Thanks for the feedback, Patrick. If you were to hazard an educated
guess, does this look like a packaging error, or an environment error
to you?
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Carl Hartung
2014-09-27 01:42:43 UTC
Permalink
On Fri, 26 Sep 2014 21:20:08 -0400
Post by Carl Hartung
On Fri, 26 Sep 2014 20:24:20 -0400
Post by Patrick Shanahan
chromium-desktop-kde-37.0.2062.94-1.55.3.x86_64.rpm ... (1/2)
Installing: chromium-37.0.2062.94-1.55.3 ... Additional rpm
using /usr/lib64/chromium/chromium-generic to
provide /usr/bin/chromium (chromium) in auto
mode /usr/lib/chrome_sandbox: will not give away s-bits on an
insecure path ERROR: not all operations were successful.
setting /usr/lib/chrome_sandbox to root:root 4755. (wrong
%post(chromium-37.0.2062.94-1.55.3.x86_64) scriptlet failed, exit
status 1
Am I the only one?
I was successful Tuesday on openSUSE-Factory
Thanks for the feedback, Patrick. If you were to hazard an educated
guess, does this look like a packaging error, or an environment error
to you?
More info after reinstalling w/ rpm:

carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is owned by root and has mode 4755.
Aborted
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Patrick Shanahan
2014-09-27 02:03:47 UTC
Permalink
Post by Carl Hartung
On Fri, 26 Sep 2014 21:20:08 -0400
[...]
Post by Carl Hartung
carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is owned by root and has
mode 4755.
Aborted
I have:
l /usr/lib64/chromium/chrome-sandbox
lrwxrwxrwx 1 root root 24 Sep 23 11:43
/usr/lib64/chromium/chrome-sandbox -> ../../lib/chrome_sandbox*

I believe 4755 would be -rwsr-xr-x

Your's failing and my succeeding I would not think indicates a packaging
error, but perhaps changing your perms will allow install. It would
really be simple to try:
chmod 777 /usr/lib64/chromium/chrome-sandbox

then try the update and see if the script still fails.
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://linuxcounter.net
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Patrick Shanahan
2014-09-27 02:17:50 UTC
Permalink
Post by Patrick Shanahan
Post by Carl Hartung
On Fri, 26 Sep 2014 21:20:08 -0400
[...]
Post by Carl Hartung
carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is owned by root and has
mode 4755.
Aborted
l /usr/lib64/chromium/chrome-sandbox
lrwxrwxrwx 1 root root 24 Sep 23 11:43
/usr/lib64/chromium/chrome-sandbox -> ../../lib/chrome_sandbox*
I believe 4755 would be -rwsr-xr-x
Your's failing and my succeeding I would not think indicates a packaging
error, but perhaps changing your perms will allow install. It would
chmod 777 /usr/lib64/chromium/chrome-sandbox
then try the update and see if the script still fails.
the chmod is incorrect, it should be as the error reported, I imagine. I
don't know why my link has the incorrect mode but it does work and I
didn't change it, ever. /usr/lib/chrome_sandbox which the link points is
indeed 4755.

Someone with a better understanding the me will have to advise
--
(paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri
http://en.opensuse.org openSUSE Community Member facebook/ptilopteri
http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535 @ http://linuxcounter.net
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Carl Hartung
2014-09-27 02:24:22 UTC
Permalink
On Fri, 26 Sep 2014 22:17:50 -0400
Post by Patrick Shanahan
Post by Patrick Shanahan
Post by Carl Hartung
On Fri, 26 Sep 2014 21:20:08 -0400
[...]
Post by Carl Hartung
carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is
owned by root and has mode 4755.
Aborted
l /usr/lib64/chromium/chrome-sandbox
lrwxrwxrwx 1 root root 24 Sep 23 11:43
/usr/lib64/chromium/chrome-sandbox -> ../../lib/chrome_sandbox*
I believe 4755 would be -rwsr-xr-x
Your's failing and my succeeding I would not think indicates a
packaging error, but perhaps changing your perms will allow
chmod 777 /usr/lib64/chromium/chrome-sandbox
then try the update and see if the script still fails.
the chmod is incorrect, it should be as the error reported, I
imagine. I don't know why my link has the incorrect mode but it does
work and I didn't change it, ever. /usr/lib/chrome_sandbox which the
link points is indeed 4755.
Someone with a better understanding the me will have to advise
Thanks again for the feedback, Patrick. We were thinking along the same
lines. I ultimately ran chmod 4755 on /usr/lib/chrome_sandbox and
chromium launches ... it complains about not being able to connect to
kwallet, though.
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Marcus Meissner
2014-09-27 07:31:23 UTC
Permalink
Post by Carl Hartung
On Fri, 26 Sep 2014 22:17:50 -0400
Post by Patrick Shanahan
Post by Patrick Shanahan
Post by Carl Hartung
On Fri, 26 Sep 2014 21:20:08 -0400
[...]
Post by Carl Hartung
carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is
owned by root and has mode 4755.
Aborted
l /usr/lib64/chromium/chrome-sandbox
lrwxrwxrwx 1 root root 24 Sep 23 11:43
/usr/lib64/chromium/chrome-sandbox -> ../../lib/chrome_sandbox*
I believe 4755 would be -rwsr-xr-x
Your's failing and my succeeding I would not think indicates a
packaging error, but perhaps changing your perms will allow
chmod 777 /usr/lib64/chromium/chrome-sandbox
then try the update and see if the script still fails.
the chmod is incorrect, it should be as the error reported, I
imagine. I don't know why my link has the incorrect mode but it does
work and I didn't change it, ever. /usr/lib/chrome_sandbox which the
link points is indeed 4755.
Someone with a better understanding the me will have to advise
Thanks again for the feedback, Patrick. We were thinking along the same
lines. I ultimately ran chmod 4755 on /usr/lib/chrome_sandbox and
chromium launches ... it complains about not being able to connect to
kwallet, though.
For this you should open a bugreport.

(As 12.3 gets the factory chromium it might have changes that are not
mirrored in permissions.)

Ciao, Marcus
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Carl Hartung
2014-09-27 13:32:36 UTC
Permalink
On Sat, 27 Sep 2014 09:31:23 +0200
Post by Marcus Meissner
Post by Carl Hartung
On Fri, 26 Sep 2014 22:17:50 -0400
Post by Patrick Shanahan
Post by Patrick Shanahan
Post by Carl Hartung
On Fri, 26 Sep 2014 21:20:08 -0400
[...]
Post by Carl Hartung
carlh:~/> chromium
[7257:7257:0926/213904: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/chrome-sandbox is owned by root and
has mode 4755. Aborted
l /usr/lib64/chromium/chrome-sandbox
lrwxrwxrwx 1 root root 24 Sep 23 11:43
/usr/lib64/chromium/chrome-sandbox
-> ../../lib/chrome_sandbox*
I believe 4755 would be -rwsr-xr-x
Your's failing and my succeeding I would not think indicates a
packaging error, but perhaps changing your perms will allow
chmod 777 /usr/lib64/chromium/chrome-sandbox
then try the update and see if the script still fails.
the chmod is incorrect, it should be as the error reported, I
imagine. I don't know why my link has the incorrect mode but it
does work and I didn't change it, ever. /usr/lib/chrome_sandbox
which the link points is indeed 4755.
Someone with a better understanding the me will have to advise
Thanks again for the feedback, Patrick. We were thinking along the
same lines. I ultimately ran chmod 4755 on /usr/lib/chrome_sandbox
and chromium launches ... it complains about not being able to
connect to kwallet, though.
For this you should open a bugreport.
(As 12.3 gets the factory chromium it might have changes that are not
mirrored in permissions.)
Ciao, Marcus
Thanks for the guidance, Marcus ... done:

http://bugzilla.opensuse.org/show_bug.cgi?id=898822

Carl
--
To unsubscribe, e-mail: opensuse+***@opensuse.org
To contact the owner, e-mail: opensuse+***@opensuse.org
Loading...