Description of problem: lightdm crashes as soon as it starts. May be related to the fact that my graphics card is not working properly. Version-Release number of selected component: lightdm-gtk-1.8.5-17.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/sbin/lightdm-gtk-greeter crash_function: set_session executable: /usr/sbin/lightdm-gtk-greeter global_pid: 791 kernel: 4.1.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 994 Truncated backtrace: Thread no. 1 (1 frames) #0 set_session at ../../src/lightdm-gtk-greeter.c:583 Potential duplicate: bug 1072193
Created attachment 1064167 [details] File: backtrace
Created attachment 1064168 [details] File: cgroup
Created attachment 1064169 [details] File: core_backtrace
Created attachment 1064170 [details] File: dso_list
Created attachment 1064171 [details] File: environ
Created attachment 1064172 [details] File: limits
Created attachment 1064173 [details] File: maps
Created attachment 1064174 [details] File: mountinfo
Created attachment 1064175 [details] File: namespaces
Created attachment 1064176 [details] File: open_fds
Created attachment 1064177 [details] File: proc_pid_status
Created attachment 1064178 [details] File: var_log_messages
Oh I just had a peek at the set_session function which was crashing. I think this is because I haven't got any valid X sessions installed on this system yet (still just trying to get X working with this graphics card). It would be nice if lightdm could handle that situation sanely -- at least starting up and showing a login prompt or error message, even if it won't let me actually log in.
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.