On 02/05/2016 12:51 PM, John Andersen wrote:

On 02/05/2016 10:00 AM, Dave Smith wrote:

...

Since I updated my 13.2 installation this morning Chromium will not start. Attempting to start Chromium from the command line prompt gives a one line error message:

Check failed: NamespaceUtils::WriteToIdMapFile("/proc/self/gid_map", gid_)

I notice the kernel was updated with this update. Any ideas on how to get Chromium back?

Thanks,

Dave

Oh, and a forced re-install of chrome does not fix it either. I'm using chrome-stable.

Did find some old-ish google hits: https://code.google.com/p/chromium/issues/detail?id=480017 And getting updated with opensuse users.

Also this page has a work around: https://forums.opensuse.org/showthread.php/513348-chromium-failed-to-launch-...

...

Start chrome as: /usr/bin/google-chrome-stable %U --disable-namespace-sandbox

and start chromium as: chromium --disable-namespace-sandbox

This doesn't seem like a permanent (or wise) solution, but it did work for me.

By the way, there is a new Chrome in the repositories Version 48.0.2564.109 (64-bit) Stable, but it does not fix this, and apparently a kernel update is needed, and in testing at this time. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/05/2016 12:51 PM, John Andersen wrote:

...

On 02/05/2016 10:00 AM, Dave Smith wrote:

...

Since I updated my 13.2 installation this morning Chromium will not start. Attempting to start Chromium from the command line prompt gives a one line error message:

Check failed: NamespaceUtils::WriteToIdMapFile("/proc/self/gid_map", gid_)

I notice the kernel was updated with this update. Any ideas on how to get Chromium back?

Thanks,

Dave

Oh, and a forced re-install of chrome does not fix it either. I'm using chrome-stable.

Did find some old-ish google hits: https://code.google.com/p/chromium/issues/detail?id=480017 And getting updated with opensuse users.

Also this page has a work around: https://forums.opensuse.org/showthread.php/513348-chromium-failed-to-launc h-quot-Check-failed-NamespaceUtils-WriteToIdMapFile%28-quot-proc-self-gid_ map-quot-gid_>

...

Start chrome as: /usr/bin/google-chrome-stable %U --disable-namespace-sandbox

and start chromium as: chromium --disable-namespace-sandbox

This doesn't seem like a permanent (or wise) solution, but it did work for me. By the way, there is a new Chrome in the repositories Version 48.0.2564.109 (64-bit) Stable, but it does not fix this, and apparently a kernel update is needed, and in testing at this time. The previous kernel is always available through GRUB's Advanced options. If

Op dinsdag 9 februari 2016 18:03:21 CET schreef John Andersen: that saves you, boot that one and Chrome ( or Chromium ) should work again if the info re. kernel is correct. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/11/2016 07:55 AM, michael norman wrote:

So if I've got this right I should install the updated kernel which breaks Chrome/Chromium and then I should then reboot from Grub2 back to the older one to get Chrome/Chromium to work again ?

If you just sit tight for a couple days the problem will be solved. If you ARE seeing this problem you already have the problem kernel installed. If not, then don't allow kernel updates till people start posting on this thread that its fixed.. _Note_ that the work-arounds are NOT the the most dangerous thing in the world. Its not the total sandbox that is horked when using the work-arounds, just the dns lookups. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/11/2016 11:12 AM, John Andersen wrote:

On 02/11/2016 07:55 AM, michael norman wrote:

...

So if I've got this right I should install the updated kernel which breaks Chrome/Chromium and then I should then reboot from Grub2 back to the older one to get Chrome/Chromium to work again ?

If you just sit tight for a couple days the problem will be solved. If you ARE seeing this problem you already have the problem kernel installed. If not, then don't allow kernel updates till people start posting on this thread that its fixed..

Well they made a liar out of me. Its now been over two weeks since this regression was posted, and Chrome and chromium both got updated and still this isn't fixed. By the end of the day i have 5 or 6 zombie Chrome items running because of clicks on links in emails. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/19/2016 02:11 AM, michael norman wrote:

Does anybody know why it hasn't yet been fixed ? Is it a low priority, surely it can't be particularly difficult ?

FWIW, I have Chromium running, with 4 tabs open, 24/7. No problems here. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/19/2016 07:11 AM, michael norman wrote:

On 19/02/16 12:09, James Knott wrote:

...

On 02/19/2016 02:11 AM, michael norman wrote:

...

Does anybody know why it hasn't yet been fixed ? Is it a low priority, surely it can't be particularly difficult ?

FWIW, I have Chromium running, with 4 tabs open, 24/7. No problems here.

Is that 13.2 or Leap ? I believe the problem is with 13.2 and not Leap.

13.1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Fri, 19 Feb 2016 12:23:20 Carl Hartung wrote:

On Fri, 19 Feb 2016 07:19:41 -0500

James Knott wrote:

...

On 02/19/2016 07:11 AM, michael norman wrote:

...

On 19/02/16 12:09, James Knott wrote:

...

On 02/19/2016 02:11 AM, michael norman wrote:

...

Does anybody know why it hasn't yet been fixed ? Is it a low priority, surely it can't be particularly difficult ?

FWIW, I have Chromium running, with 4 tabs open, 24/7. No problems here.

Is that 13.2 or Leap ? I believe the problem is with 13.2 and not Leap.

13.1

It still isn't launching on 13.2 here after yesterday's updates.

What version of Chromium? Version Version 48.0.2564.109 (64-bit) is working fine here on 13.2. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 21 Feb 2016 01:01:36 John Andersen wrote:

On February 21, 2016 12:51:00 AM PST, Rodney Baker wrote:

...

On Fri, 19 Feb 2016 12:23:20 Carl Hartung wrote:

...

On Fri, 19 Feb 2016 07:19:41 -0500

James Knott wrote:

...

On 02/19/2016 07:11 AM, michael norman wrote:

...

On 19/02/16 12:09, James Knott wrote:

...

On 02/19/2016 02:11 AM, michael norman wrote: > Does anybody know why it hasn't yet been fixed ? Is it a low > priority, surely it can't be particularly difficult ?

FWIW, I have Chromium running, with 4 tabs open, 24/7. No

problems

...

...

...

...

here.

Is that 13.2 or Leap ? I believe the problem is with 13.2 and

not

...

...

...

Leap.

13.1

It still isn't launching on 13.2 here after yesterday's updates.

What version of Chromium? Version Version 48.0.2564.109 (64-bit) is working fine here on 13.2.

Chrome also fails to launch on 13.2 . You have to turn off sand boxing dns requests in order to get it to launch.

A kernel fix was promised last week but that didn't happen. Some lame excuse about it building on a show machine. Then it was simply forgotten.

Ah. If it's kernel related, I'm running 4.4.1-5.g6398c2d-default - maybe that's why I'm not seeing the issue. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Am 21.02.2016 um 10:14 schrieb Rodney Baker:

Chrome also fails to launch on 13.2 . You have to turn off sand boxing dns requests in order to get it to launch.

A kernel fix was promised last week but that didn't happen. Some lame excuse about it building on a show machine. Then it was simply forgotten. Ah. If it's kernel related, I'm running 4.4.1-5.g6398c2d-default - maybe that's why I'm not seeing the issue.

Where did you get a 4.4 Kernel for 13.2? Regards, -- Aaron "Optimizer" Digulla a.k.a. Philmann Dark "It's not the universe that's limited, it's our imagination. Follow me and I'll show you something beyond the limits." http://blog.pdark.de/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On Sun, 21 Feb 2016 07:52:32 Anton Aylward wrote:

On 02/21/2016 05:24 AM, Aaron Digulla wrote:

...

Am 21.02.2016 um 10:14 schrieb Rodney Baker:

...

Chrome also fails to launch on 13.2 . You have to turn off sand boxing dns requests in order to get it to launch.

A kernel fix was promised last week but that didn't happen. Some lame excuse about it building on a show machine. Then it was simply forgotten. Ah. If it's kernel related, I'm running 4.4.1-5.g6398c2d-default - maybe that's why I'm not seeing the issue.

Where did you get a 4.4 Kernel for 13.2?

Probably the same place I've been getting the series 4 kernel and posting about it regularly, the "Kernel Stable" repository at http://download.opensuse.org/repositories/Kernel:/stable/standard/

YMMV.

The answer to most questions of this nature lie somewhere under http://download.opensuse.org/repositories/ Feel free to browse there for interesting and valuable things :-)

It's more fun than reading manual pages :-)

Yes. What he said. :) The Kernel Stable repository has various different up- to-date kernel flavours to choose from. There are a couple of caveats - the firmware for my dvb card, for instance, that is distrbuted with the >4.1 series kernels is broken (at least for my card) but I have a workaround; I keep the last working version handy ready to put back into /lib/firmware when it gets replaced (and I have the source etc in /usr/local/src/ so that I can rebuild it if necessary. Apart from that, I have zero problems. I also have dkms installed to automatically handle module rebuilds for nvidia and VirtualBox when the kernel is updated. Saves reinstalling drivers every time. Yes, I know I could use the nvidia drivers from the openSuSE repositories but I've had way more problems doing that than using the NVidia binary installer. Again, YMMV. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au ============================================================== -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

On 02/21/2016 01:14 AM, Rodney Baker wrote:

On Sun, 21 Feb 2016 01:01:36 John Andersen wrote:

...

On February 21, 2016 12:51:00 AM PST, Rodney Baker wrote:

...

On Fri, 19 Feb 2016 12:23:20 Carl Hartung wrote:

...

On Fri, 19 Feb 2016 07:19:41 -0500

James Knott wrote:

...

On 02/19/2016 07:11 AM, michael norman wrote:

...

On 19/02/16 12:09, James Knott wrote: > On 02/19/2016 02:11 AM, michael norman wrote: >> Does anybody know why it hasn't yet been fixed ? Is it a low >> priority, surely it can't be particularly difficult ? > > FWIW, I have Chromium running, with 4 tabs open, 24/7. No

problems

...

...

...

> here.

Is that 13.2 or Leap ? I believe the problem is with 13.2 and

not

...

...

...

Leap.

13.1

It still isn't launching on 13.2 here after yesterday's updates.

What version of Chromium? Version Version 48.0.2564.109 (64-bit) is working fine here on 13.2.

Chrome also fails to launch on 13.2 . You have to turn off sand boxing dns requests in order to get it to launch.

A kernel fix was promised last week but that didn't happen. Some lame excuse about it building on a show machine. Then it was simply forgotten.

Ah. If it's kernel related, I'm running 4.4.1-5.g6398c2d-default - maybe that's why I'm not seeing the issue.

13.2 official kernel is still 3.16.7-32. Given all the people posting caveats of broken hardware issues, I see nothing to gain in updating 13.2 to a later kernel, since I have no hardware issues and no performance issues. Besides, wouldn't want to incur the wrath of Mr. Brown for tainting my installation and thereby jeopardizing my support *cough*. -- After all is said and done, more is said than done. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org