On Tue, Nov 25, 2014 at 12:09:10PM +1100, Peter Miller wrote: > I've had the "Oh no! Something went wrong" screen for a couple of > weeks now, since just before Testing went into freeze. > > I've looked everywhere I can and tried all sorts of things, but > nothing solves the problem. I recently upgraded to sid to see if that > helped, but still no luck. > > In the included journal file below, it seems the problem lies in the > "cannot determine display-device" entry, but I can't tell what is > causing that. > > I have a lot more diagnostic output, but I can't have attachments, apparently. > > I would file a bug report, but I am not sure which package to report under. > > One thing I have not been able to work out if is whether the memory > conflict message is an issue, and, if it is, how to solve it... > > Thanks for any assistance...
Had that as well, filed a bug several weeks ago. You might want to add your +1 as a comment to my bug report Bug#767083. Not absolutely sure that it's because of Google-Chrome, but I was using it each time received the "Oh No" from Gnome-Shell. > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141125112334.GA17097@stephen-desktop
