Bug 806427

Summary: Most recent F17 updates let my VirtualBox and then the gnome-shell session crash
Product: [Fedora] Fedora Reporter: Joachim Backes <joachim.backes>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: awilliam, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-23 18:23:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Part of /var/log/messages produced by the crash none

Description Joachim Backes 2012-03-23 17:31:23 UTC
Created attachment 572346 [details]
Part of /var/log/messages produced by the crash

Description of problem:
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 has gone wrong"


Version-Release number of selected component (if applicable):
gnome-shell-3.3.92-1.fc17.x86_64


How reproducible:
Each time I start the virtual machine inside VirtualBox

Steps to Reproduce:
1.Start Virtual Box
2.Start a virtual machine
3.
  
Actual results:
see description

Expected results:


Additional info:

Comment 1 Adam Williamson 2012-03-23 18:05:37 UTC
As the log shows, abrt caught the crash. Can you use abrt-cli, or log in to another desktop and use abrt-gui, to report the crash, then close this bug as a dupe of the report? Thanks!



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Joachim Backes 2012-03-23 18:23:36 UTC

*** This bug has been marked as a duplicate of bug 806437 ***