Bug 807812 - locked on woops there was a problem message
locked on woops there was a problem message
Product: Fedora
Classification: Fedora
Component: gnome-shell (Show other bugs)
i386 Linux
unspecified Severity urgent
: ---
: ---
Assigned To: Owen Taylor
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-03-28 15:45 EDT by dario
Modified: 2012-04-19 13:41 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-04-19 13:41:35 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description dario 2012-03-28 15:45:23 EDT
Description of problem: after the new install of the F17 graphic test CD, and opening several programs in them blender, the installer, and setting the graphics to the highest resolution, if the activities overview mode is activated constantly, the woops there was a problem and gnome cannot recover log out message apears, then since the log out process starts and the message apears over and over again, no log in screen is shown, rebooting does not fix this.

How reproducible: every time I move the mouse over the hot corner while the overview is trying to show all the windows the message appears and, to fix this really fast, reinstall the system.

Steps to Reproduce:
1. log in
2. open 4 programs
3. move over to the hot corner several times while gnome-shell trys to show the windows
Actual results: you se the Woops message 

Expected results: the overview

Additional info: it never shows the log in screen ever again.
Comment 1 Owen Taylor 2012-04-19 13:41:35 EDT
Can't really proceed further here without detailed information about the crashing process. (The crashes are likely caught by ABRT which should offer to file a bug.) Various crashes are fixed in 3.4.1 in updates-testing.

Note You need to log in before you can comment on or make changes to this bug.