Description of problem: Docked laptop into a docking station connected to an external monitor as well. Version-Release number of selected component: gnome-shell-3.10.1-1.fc20 Additional info: reporter: libreport-2.1.8 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.11.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 10327 Truncated backtrace: Thread no. 1 (8 frames) #2 _g_log_abort at gmessages.c:255 #5 meta_monitor_config_assign_crtcs at core/monitor-config.c:1806 #6 apply_configuration at core/monitor-config.c:848 #7 _g_closure_invoke_va at gclosure.c:840 #10 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c:1736 #15 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c:1789 #16 dbus_g_proxy_manager_filter at dbus-gproxy.c:1356 #23 meta_run at core/main.c:556
Created attachment 815359 [details] File: backtrace
Created attachment 815360 [details] File: cgroup
Created attachment 815361 [details] File: core_backtrace
Created attachment 815362 [details] File: dso_list
Created attachment 815363 [details] File: environ
Created attachment 815364 [details] File: limits
Created attachment 815365 [details] File: maps
Created attachment 815366 [details] File: open_fds
Created attachment 815367 [details] File: proc_pid_status
Created attachment 815368 [details] File: var_log_messages
Tried to increase laptop screen brightness when plugged into a dock tied to a secondary monitor. reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.11.6-301.fc20.x86_64 package: gnome-shell-3.10.1-2.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
Nautilus crashed while video thumnails is loading reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.11.6-301.fc20.x86_64 package: gnome-shell-3.10.1-2.fc20 reason: Process /usr/bin/gnome-shell was killed by signal 6 (SIGABRT) runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I inserted a CD and clicked on the notification button to open in rhythmbox. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.12.5-302.fc20.x86_64 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Setup: Laptop with one external monitor. How to reproduce: 1. Close the laptop lid. 2. Wait until system reconfigures the desktop to use only the external monitor. 3. Open laptop lid. Crash will occur at some point when the system reconfigures the desktop for two monitors. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.12.5-302.fc20.i686 package: gnome-shell-3.10.2.1-3.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Laptop connected to external monitor during yum update. When download finished and install started a display corruption occurred. There were small groups of pixels that flashed between black and white. I restarted gnome hoping that would fix the corruption, but it did not so I restarted. Upon reboot I was presented with the abrt notification of this bug.
Simply disabling the monitor (from settings), saving the setting and re-enabling the monitor works for me.
for me I think it happens when I suspend then connect an external screen and power up, also sometimes the other way around. Seems like there has not been much thought given these scenarios with laptop + external screen, including Intel, I use Dell Latitude 6430u regards
This issue occurred for me as well. - laptop had been disconnected from docking station which had an external monitor connected to it; - laptop was suspended; - laptop was connected to docking station which had an external monitor connected to it; - laptop was resumed by opening laptop lid; - gnome-shell killed by SIGABRT[1] [1]: https://retrace.fedoraproject.org/faf/reports/249586/
Another user experienced a similar problem: Seem to be related to resuming from suspend state on the laptop. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell kernel: 3.14.7-200.fc20.x86_64 package: gnome-shell-3.10.4-5.fc20 reason: gnome-shell killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
I plug/unplug an external monitor daily, but only have experienced this once. I have a Lenovo P580 20184 laptop.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.