On February 21, 2016 12:51:00 AM PST, Rodney Baker
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
On Fri, 19 Feb 2016 12:23:20 Carl Hartung wrote: 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. -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org