Hide Forgot
Description of problem: Hi! When "Plugable UD-160" usb docking station is connected to system then gdm login screen should appear. Instead, docking station powers up but gdm does not appear. Logs and 'loginctl' show that seat is created and X starts but gnome-session-chek-accelerated utility crashed somewhere in a process. It happens every time when docking stations are connected to computer or powered up. So far i found two workarounds. First, when docking stations (i have two) are powered on before main computer then everything works as expected. Curious that docking stations get X11 display numbers ":0" and ":1"; main computer gets :2. Second, when /usr/libexec/gnome-session-check-accelerated binary is renamed and replaced with symlink to /bin/true then docking stations work. I haven't tested wheter it affects main computers display performance after gdm login screen. Version-Release number of selected component: gnome-session-3.18.1.2-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 3 cmdline: /usr/libexec/gnome-session-check-accelerated crash_function: _XInternAtom executable: /usr/libexec/gnome-session-check-accelerated global_pid: 5872 kernel: 4.2.5-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 42 Truncated backtrace: Thread no. 1 (3 frames) #0 _XInternAtom at IntAtom.c:76 #1 XInternAtom at IntAtom.c:175 #2 gdk_x11_atom_to_xatom_for_display at gdkproperty-x11.c:115
Created attachment 1110790 [details] File: backtrace
Created attachment 1110791 [details] File: cgroup
Created attachment 1110792 [details] File: core_backtrace
Created attachment 1110793 [details] File: dso_list
Created attachment 1110794 [details] File: environ
Created attachment 1110795 [details] File: exploitable
Created attachment 1110796 [details] File: limits
Created attachment 1110797 [details] File: maps
Created attachment 1110798 [details] File: mountinfo
Created attachment 1110799 [details] File: namespaces
Created attachment 1110800 [details] File: open_fds
Created attachment 1110801 [details] File: proc_pid_status
*** Bug 1318398 has been marked as a duplicate of this bug. ***
Similar problem has been detected: Reinstalled SO and update it remaining untouched /home/[users] 2 users log in correctly but the third doesn't reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/libexec/gnome-session-check-accelerated crash_function: _XInternAtom executable: /usr/libexec/gnome-session-check-accelerated global_pid: 21197 kernel: 4.5.5-201.fc23.x86_64 package: gnome-session-3.18.1.2-2.fc23 reason: gnome-session-check-accelerated killed by SIGSEGV runlevel: N 5 type: CCpp uid: 42
Created attachment 1165481 [details] File: backtrace
*** Bug 1371918 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.