Most recent F17 updates let my VirtualBox and then the gnome-shell session crash

Adam Williamson awilliam at redhat.com
Fri Mar 23 18:04:13 UTC 2012


On Fri, 2012-03-23 at 09:43 -0700, Tom London wrote:
> On Fri, Mar 23, 2012 at 9:28 AM, Joachim Backes
> <joachim.backes at rhrk.uni-kl.de> wrote:
> > Hi,
> >
> > I'm running inside F17 VirtualBox-4.1-4.1.10_76795_fedora16-1.x86_64
> > from virtualbox.org flawlessly until today morning. But after having
> > applied all F17 updates (a lot!!) and trying to start VirtualBox,
> >
> > 1. VirtualBox crashes immediately if starting the virtual machine
> > 2. Immeditately after the VirtualBox crash, the gnome-shell session
> >   crashes too with the well known message "Oh no, something went wrong"
> >
> > Anybody sees this too?
> >
> > --
> > Joachim Backes <joachim.backes at rhrk.uni-kl.de>
> >
> > http://www.rhrk.uni-kl.de/~backes
> >
> >
> > --
> > test mailing list
> > test at lists.fedoraproject.org
> > To unsubscribe:
> > https://admin.fedoraproject.org/mailman/listinfo/test
> 
> I see this on my "non VirtualBox", fully updated system, I see the "Oh
> no, something went wrong" too.
> 
> A very quick check of the logs indicates gnome-shell is
> exiting/restarting too quickly...

Somewhere else in the log should be a clue as to why it's crashing. The
crash might also have been logged by abrt, if you log into another
desktop and run abrt-gui, or use abrt-cli from the console.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net



More information about the test mailing list