Description of problem: Happens shortly after login to Rawhide system upgraded from F23. Version-Release number of selected component: glx-utils-8.3.0-3.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: glxinfo crash_function: pthread_barrier_destroy executable: /usr/bin/glxinfo global_pid: 1662 kernel: 4.5.0-0.rc4.git1.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 pthread_barrier_destroy at pthread_barrier_destroy.c:40 #1 pipe_barrier_destroy at ../../../../src/gallium/auxiliary/os/os_thread.h:155 #2 lp_rast_destroy at lp_rast.c:970 #3 llvmpipe_destroy_screen at lp_screen.c:528 #4 dri_destroy_screen_helper at dri_screen.c:380 #5 dri_destroy_screen at dri_screen.c:391 #6 driDestroyScreen at dri_util.c:228 #7 driswDestroyScreen at drisw_glx.c:587 #8 FreeScreenConfigs at glxext.c:217 #9 glx_display_free at glxext.c:240
Created attachment 1128376 [details] File: backtrace
Created attachment 1128377 [details] File: cgroup
Created attachment 1128378 [details] File: core_backtrace
Created attachment 1128379 [details] File: dso_list
Created attachment 1128380 [details] File: environ
Created attachment 1128381 [details] File: limits
Created attachment 1128382 [details] File: maps
Created attachment 1128383 [details] File: mountinfo
Created attachment 1128384 [details] File: namespaces
Created attachment 1128385 [details] File: open_fds
Created attachment 1128386 [details] File: proc_pid_status
Created attachment 1128387 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Similar problem has been detected: Booted the F24 Alpha 1.5 KDE x86_64 live image in a vmvga / VNC VM, then went into System Settings and changed a video setting and quit again. I'm not sure where along the line this crash happened, it had no obviously visible effects, it may have happened during startup. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: glxinfo crash_function: pthread_barrier_destroy executable: /usr/bin/glxinfo global_pid: 1446 kernel: 4.5.0-0.rc7.git0.2.fc24.x86_64 package: glx-utils-8.3.0-3.fc24 reason: glxinfo killed by SIGFPE runlevel: unknown type: CCpp uid: 1000
Similar problem has been detected: Booted Fedora 24 Alpha 1.5 Workstation x86_64 live. Crash notification appeared immediately after GNOME loaded, must have happened during boot. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: glxinfo crash_function: pthread_barrier_destroy executable: /usr/bin/glxinfo global_pid: 1448 kernel: 4.5.0-0.rc7.git0.2.fc24.x86_64 package: glx-utils-8.3.0-3.fc24 reason: glxinfo killed by SIGFPE runlevel: unknown type: CCpp uid: 1000
Nominating as a Final blocker, per criterion "There must be no SELinux denial notifications or crash notifications on boot of or during installation from a release-blocking live image, or at first login after a default install of a release-blocking desktop." - this seems to happen reliably when booting Workstation and KDE lives in a typical VM configuration (qxl/SPICE).
may be a dup of bug #1318541 (the crash ends in the same place at least)
mesa-11.2.0-0.devel.12.24ea81a.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e27c369d3
mesa-11.2.0-0.devel.12.24ea81a.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-8e27c369d3
I don't see this with the updated mesa, thanks.
mesa-11.2.0-0.devel.12.24ea81a.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.