Hide Forgot
Description of problem: This happens with kernel 4.3 and proprietary AMD drivers. I know, I know. That's not supported, but due to other (very old) bugs not yet fixed, I cannot use open-source drivers. I will explain more after bug creation. Version-Release number of selected component: lightdm-gtk-1.8.5-19.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/sbin/lightdm-gtk-greeter crash_function: rawmemchr executable: /usr/sbin/lightdm-gtk-greeter global_pid: 2248 kernel: 4.3.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 990 Truncated backtrace: Thread no. 1 (10 frames) #0 rawmemchr at ../sysdeps/x86_64/rawmemchr.S:37 #1 _IO_str_init_static_internal at strops.c:44 #2 __isoc99_vsscanf at isoc99_vsscanf.c:41 #3 __isoc99_sscanf at isoc99_sscanf.c:31 #4 epoxy_glx_version at dispatch_glx.c:60 #5 gdk_x11_screen_init_gl at gdkglcontext-x11.c:774 #6 _gdk_x11_screen_update_visuals_for_gl at gdkglcontext-x11.c:1114 #7 _gdk_x11_screen_init_visuals at gdkvisual-x11.c:334 #8 _gdk_x11_screen_new at gdkscreen-x11.c:1214 #9 _gdk_x11_display_open at gdkdisplay-x11.c:1472
Created attachment 1119715 [details] File: backtrace
Created attachment 1119716 [details] File: cgroup
Created attachment 1119717 [details] File: core_backtrace
Created attachment 1119718 [details] File: dso_list
Created attachment 1119719 [details] File: environ
Created attachment 1119720 [details] File: exploitable
Created attachment 1119721 [details] File: limits
Created attachment 1119722 [details] File: maps
Created attachment 1119723 [details] File: mountinfo
Created attachment 1119724 [details] File: namespaces
Created attachment 1119725 [details] File: open_fds
Created attachment 1119726 [details] File: proc_pid_status
Created attachment 1119727 [details] File: var_log_messages
Oops, I completely forgot the radeon audio problem did get fixed. bug 1295641. Sorry, I guess I could use that; I thought it was still broken. Well, on the off chance someone knows why lightdm breaks this way with kernel 4.3 but not kernel 4.2, I'd still like to know. Maybe I can find a workaround if someone can interpret for me.
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.