[Bug 1355588] Re: On launch, failed to initialize command buffer

2018-03-09 Thread Olivier Tilloy
** Changed in: chromium-browser (Ubuntu) Assignee: Chad Miller (cmiller) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1355588 Title: On launch, failed to initialize command buf

[Bug 1355588] Re: On launch, failed to initialize command buffer

2015-07-23 Thread dino99
** Changed in: chromium-browser Importance: Unknown => Undecided ** Changed in: chromium-browser Status: Unknown => New ** Changed in: chromium-browser Remote watch: code.google.com/p/chromium/issues #415928 => None ** Changed in: chromium-browser Status: New => Invalid -- Yo

[Bug 1355588] Re: On launch, failed to initialize command buffer

2015-07-23 Thread dino99
Closing that report now , as: - utopic support has now ended - chromium version is now more recent - that issue has not been met recently ** Changed in: chromium-browser (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, whic

[Bug 1355588] Re: On launch, failed to initialize command buffer

2015-02-26 Thread dino99
Way better since chromium 40 has been upgraded on Vivid : i was having the "aw, snap!!" fatal blue screen so often on "tomshardware" site, but now that does not happen since a couple weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubunt