Description of problem: I have a three head setup with thinkpad W520 (2 monitors and LCD panel) when undocked and re-docked the gnome shell crashed Version-Release number of selected component: gnome-shell-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: crtc_assignment_assign executable: /usr/bin/gnome-shell global_pid: 3226 kernel: 4.0.4-301.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 crtc_assignment_assign at backends/meta-monitor-config.c:1716 #1 real_assign_crtcs at backends/meta-monitor-config.c:1876 #2 meta_monitor_config_assign_crtcs at backends/meta-monitor-config.c:1916 #3 apply_configuration at backends/meta-monitor-config.c:872 #4 meta_monitor_config_restore_previous at backends/meta-monitor-config.c:1453 #10 g_object_notify_by_spec_internal at gobject.c:1149 #11 g_object_notify at gobject.c:1197 #17 g_object_notify_by_spec_internal at gobject.c:1149 #18 g_object_notify at gobject.c:1197 #19 up_client_glue_proxy_g_properties_changed at up-client-glue.c:1348
Created attachment 1033337 [details] File: backtrace
Created attachment 1033338 [details] File: cgroup
Created attachment 1033340 [details] File: core_backtrace
Created attachment 1033341 [details] File: dso_list
Created attachment 1033342 [details] File: environ
Created attachment 1033343 [details] File: limits
Created attachment 1033344 [details] File: maps
Created attachment 1033345 [details] File: mountinfo
Created attachment 1033346 [details] File: namespaces
Created attachment 1033347 [details] File: open_fds
Created attachment 1033348 [details] File: proc_pid_status
Created attachment 1033349 [details] File: var_log_messages
Another user experienced a similar problem: I undocked my Notebook, it locked itself and I logged in. The crash must have happened during one of those steps. reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: crtc_assignment_assign executable: /usr/bin/gnome-shell global_pid: 2154 kernel: 4.0.6-300.fc22.x86_64 package: gnome-shell-3.16.2-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I believe this happened as I resumed from suspend, after I had docked with two monitors connected via DP reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: crtc_assignment_assign executable: /usr/bin/gnome-shell global_pid: 24038 kernel: 4.1.10-200.fc22.x86_64 package: gnome-shell-3.16.3-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Restoring my laptop from sleep. I don't know if is important to understand the bug but I but in sleep mode with an external monitor attached as secondary display and at restore time it was not longer attached. reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: crtc_assignment_assign executable: /usr/bin/gnome-shell global_pid: 4062 kernel: 4.2.3-200.fc22.x86_64 package: gnome-shell-3.16.4-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.