http://bugzilla.novell.com/show_bug.cgi?id=965356 http://bugzilla.novell.com/show_bug.cgi?id=965356#c45 --- Comment #45 from Simcha Lerner --- (In reply to Pedro Montes de Oca from comment #42)

Dear Friends.. I have applied the updates and reboot my system.

I sill can not open Chromium the normal way.

I only can open it as suggested with "chromium --disable-namespace-sandbox"

I'm lost, any idea why the update did not correct this issue ?

Thanks

First thing to do is see if you are actually booting the new kernel. "uname -r" should show "3.16.7-35-desktop" If it isn't, things to check include whether your grub boot menu is defaulting to another kernel version or whether you need to fix symlinks in /boot. If you are running the latest kernel, something may be bollixed with chrome. Temporarily rename ~/.config/google-chrome to something else and do a forced reinstall of chrome to see if this fixes things. (I've found that chrome's --disable-extensions option isn't a full safe mode equivalent, so I use the above brute force method instead.) Hope you manage to get things straightened out. This update, once it hit the repo, fixed the chrome problem for myself and the local users that I support. Good luck and let us know how it works out. -- You are receiving this mail because: You are on the CC list for the bug.