Description of problem: Gnome shell crashes and "shotguns" the screen when a root terminal is open, rolled up, then mouse is bumped into hot corner for overly to open a new workspace. Version-Release number of selected component (if applicable): How reproducible: Open root terminal, roll-up (this may not be a needed step) and then bump hot corner for overlay. Steps to Reproduce: 1. 2. 3. Actual results: Scattered video on screen - mouse movement capable, but nothing works. ctrl+alt+del needed to restart X, but will not return to GDM, instead stops at, "Starting waiting for Plymouth Boot Screen to Quit." Will not go past this point. Tty2 is required to reboot the machine. Expected results: Additional info: See the fedora forum here for photo of screen after failure. http://forums.fedoraforum.org/showpost.php?p=1461070&postcount=390 You will need to be logged in to see the graphic.
Additional info: The critical step seems to be the "roll-up" of the terminal. Without that step, everything works as expected.
Created attachment 494090 [details] dmesg and logs from crashed system
If you have to reboot after this, it's a bug in the graphics stack, rather than in GNOME Shell. I can't reproduce the crash here either on a more recent Intel GPU system, so I suspect the crash and the misbehavior are all the same thing. (Note: i915 is fairly marginal for running the shell but we do expect it to work.) The: [ 892.707] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error at the end of the Xorg.0.log, which (along with the need to reboot) makes me think this is a kernel issue rather than mesa or device-specific X driver. Can you reattach the screenshot here so all the information is in one place?
Created attachment 494555 [details] Photo of video-crashed condition.
Okey dokey. Working on it. BTW, I started a thread on this in the forum and to date, nobody else has been able to reproduce it either. http://forums.fedoraforum.org/showthread.php?t=261830
Update: I've been playing with this a bit and have discovered that it does not crash if the super button is used to bring up the overlay, but does if either the hot corner or clicking the Activities menu is used. Again. CLick or mouse into the hot corner = crash. using the Super key from the keyboard = no crash. Seems like that rules out a kernel driver issue.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 499145 [details] dmesg-5-16
Created attachment 499147 [details] messages-5-16
Created attachment 499148 [details] xorg-log-5-16
I have something very similiar when doing suspend/resume on DELL E4200 Xorg.log [329135.649] (II) Dell WMI hotkeys: Configuring as keyboard [329135.649] (**) Option "config_info" "udev:/sys/devices/virtual/input/input12/event12" [329135.649] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD) [329135.649] (**) Option "xkb_rules" "evdev" [329135.649] (**) Option "xkb_model" "pc105" [329135.649] (**) Option "xkb_layout" "fi" [329135.649] (**) Option "xkb_options" "terminate:ctrl_alt_bksp," [329135.697] (EE) intel(0): Detected a hung GPU, disabling acceleration. [329135.697] (EE) intel(0): When reporting this, please include i915_error_state from debugfs and the full dmesg. [329135.699] (II) intel(0): EDID vendor "SEC", prod id 21569 [329135.699] (II) intel(0): Printing DDC gathered Modelines: [329135.700] (II) intel(0): Modeline "1280x800"x0.0 70.34 1280 1328 1360 1400 800 803 809 830 +hsync -vsync (50.2 kHz) [329135.735] (EE) intel(0): failed to set cursor: Input/output error [329135.735] (WW) intel(0): intel_uxa_prepare_access: bo map failed: Input/output error [329135.856] (EE) intel(0): failed to set cursor: Input/output error [329135.976] (EE) intel(0): failed to set cursor: Input/output error [329136.096] (EE) intel(0): failed to set cursor: Input/output error chipinfo 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device 0277 Flags: bus master, fast devsel, latency 0, IRQ 46 Memory at f6c00000 (64-bit, non-prefetchable) [size=4M] Memory at e0000000 (64-bit, prefetchable) [size=256M] I/O ports at ef98 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 Kernel driver in use: i915 Kernel modules: i915
Added Info: It seems that the ripple animation is the culprit. Using the extension from mpmurphy, (listed in the forums) which removes the ripple, removes the problem.
I'm getting the crash when starting the Steel Storm game demo on a Toshiba Tecra M11 http://download3.steel-storm.com/steelstorm-ep1-v1.00.02718.tar.gz crashes in KDE as well as in Gnome lspci -v ... 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device 0003 Flags: bus master, fast devsel, latency 0, IRQ 41 Memory at d0000000 (64-bit, non-prefetchable) [size=4M] Memory at c0000000 (64-bit, prefetchable) [size=256M] I/O ports at 3058 [size=8] Expansion ROM at <unassigned> [disabled] Capabilities: <access denied> Kernel driver in use: i915 Kernel modules: i915
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping