Description of problem: Installed Fedora 25 (XFCE spin) in a ASUS ROG GL551V. Hardware: * Latest updates * 4.9.8-201.fc25.x86_64 * NVIDIA Geforce GTX 960M (closed source drivers via negativo17 repo) Launched xfdashboard and the error notification came up. Restarted the app and tried again, same issue happened. Version-Release number of selected component: xfdashboard-0.7.0-1.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: xfdashboard crash_function: poll_for_event executable: /usr/bin/xfdashboard global_pid: 2534 kernel: 4.9.8-201.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 poll_for_event at xcb_io.c:256 #5 poll_for_response at xcb_io.c:274 #7 _XGetRequest at XlibInt.c:1707 #8 XCreateColormap at CrCmap.c:44 #9 create_context at winsys/cogl-winsys-glx.c:1123 #10 _cogl_winsys_display_setup at winsys/cogl-winsys-glx.c:1226 #11 cogl_display_setup at cogl-display.c:154 #12 clutter_backend_do_real_create_context at clutter-backend.c:330 #13 clutter_backend_real_create_context at clutter-backend.c:414 #14 _clutter_feature_init at clutter-feature.c:107 Potential duplicate: bug 1383858
Created attachment 1249062 [details] File: backtrace
Created attachment 1249063 [details] File: cgroup
Created attachment 1249064 [details] File: core_backtrace
Created attachment 1249065 [details] File: dso_list
Created attachment 1249066 [details] File: environ
Created attachment 1249067 [details] File: limits
Created attachment 1249068 [details] File: maps
Created attachment 1249069 [details] File: mountinfo
Created attachment 1249070 [details] File: namespaces
Created attachment 1249071 [details] File: open_fds
Created attachment 1249072 [details] File: proc_pid_status
Created attachment 1249073 [details] File: var_log_messages
Do you get any more output if you try and start it from a terminal? How about with 'xfdashboard -d' ?
*** Bug 1383858 has been marked as a duplicate of this bug. ***
Filed upstream https://github.com/gmc-holle/xfdashboard/issues/140
Can you please run xfdashboard using CLUTTER_DEBUG=backend xfdashboard and provide the output (or what happens)?
Sorry for the delay, the laptop is not mine so I had to request the info. These are the messages that appear when executed xfdashboard -d or CLUTTER_DEBUG=backend xfdashboard in a terminal. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. xfdashboard: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted Let us know if there is something else we can do/provide.
I've checked the upstream bug report (thanks Mukundan), based on the latest input we checked again and this is what we got. [user@pc ~]$ CLUTTER_DEBUG=BACKEND COGL_DEBUG=winsys xfdashboard Cogl-Message: [WINSYS] cogl-xlib-renderer.c:415 & Outputs: Cogl-Message: [WINSYS] cogl-xlib-renderer.c:454 & eDP-1-1: +0+0x1920x1080 mm=344x193 dpi=141.8x142.1 subpixel_order=horizontal_rgb refresh_rate=60.008 libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:687 & GLX Extensions: GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_create_context_robustness GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_framebuffer_sRGB GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_MESA_multithread_makecurrent GLX_SGI_make_current_read GLX_SGI_swap_control GLX_SGI_video_sync GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_EXT_texture_from_pixmap GLX_EXT_buffer_age Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:988 & Found an ARGB FBConfig [index:1] Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1076 & Creating GLX Context (display: 0x55c1ac8520c0) Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1002 & Using the first available FBConfig Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1076 & Creating GLX Context (display: 0x55c1ac8520c0) Cogl-Message: [WINSYS] cogl-xlib-renderer.c:415 & Outputs: Cogl-Message: [WINSYS] cogl-xlib-renderer.c:454 & eDP-1-1: +0+0x1920x1080 mm=344x193 dpi=141.8x142.1 subpixel_order=horizontal_rgb refresh_rate=60.008 Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:687 & GLX Extensions: GLX_ARB_create_context GLX_ARB_create_context_profile GLX_ARB_create_context_robustness GLX_ARB_fbconfig_float GLX_ARB_framebuffer_sRGB GLX_ARB_get_proc_address GLX_ARB_multisample GLX_EXT_import_context GLX_EXT_visual_info GLX_EXT_visual_rating GLX_EXT_framebuffer_sRGB GLX_EXT_create_context_es2_profile GLX_EXT_create_context_es_profile GLX_MESA_multithread_makecurrent GLX_SGI_make_current_read GLX_SGI_swap_control GLX_SGI_video_sync GLX_SGIX_fbconfig GLX_SGIX_pbuffer GLX_EXT_texture_from_pixmap GLX_EXT_buffer_age Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:988 & Found an ARGB FBConfig [index:1] Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1076 & Creating GLX Context (display: 0x55c1ac8520c0) Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1103 & Setting indirect context Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1158 & Selecting dummy 0x3400006 for the GLX context Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:988 & Found an ARGB FBConfig [index:1] Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1076 & Creating GLX Context (display: 0x55c1ac8520c0) Cogl-Message: [WINSYS] winsys/cogl-winsys-glx.c:1103 & Setting indirect context [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. xfdashboard: xcb_io.c:259: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. Aborted (core dumped) Also we checked the packages installed [user@pc ~]$ dnf list installed clutter cogl gtk* mesa* Installed Packages clutter.x86_64 1.26.0-1.fc25 @koji-override-0 cogl.x86_64 1.22.2-2.fc25 @koji-override-0 gtk-murrine-engine.x86_64 0.98.2-10.fc25 @koji-override-0 gtk-unico-engine.x86_64 1.0.3-0.7.20140109bzr152.fc24 @koji-override-0 gtk-update-icon-cache.x86_64 3.22.7-1.fc25 @updates gtk-vnc2.x86_64 0.7.0-1.fc25 @updates gtk-xfce-engine.x86_64 3.2.0-3.fc24 @koji-override-0 gtk2.x86_64 2.24.31-2.fc25 @koji-override-0 gtk2-engines.x86_64 2.20.2-11.fc24 @koji-override-0 gtk3.x86_64 3.22.7-1.fc25 @updates gtkmm24.x86_64 2.24.5-1.fc25 @koji-override-0 gtkmm30.x86_64 3.22.0-1.fc25 @koji-override-0 gtkspell.x86_64 2.0.16-11.fc24 @koji-override-0 mesa-dri-drivers.i686 13.0.3-5.fc25 @updates mesa-dri-drivers.x86_64 13.0.3-5.fc25 @updates mesa-filesystem.i686 13.0.3-5.fc25 @updates mesa-filesystem.x86_64 13.0.3-5.fc25 @updates mesa-libEGL.i686 13.0.3-5.fc25 @updates mesa-libEGL.x86_64 13.0.3-5.fc25 @updates mesa-libGL.i686 13.0.3-5.fc25 @updates mesa-libGL.x86_64 13.0.3-5.fc25 @updates mesa-libGL-devel.x86_64 13.0.3-5.fc25 @updates mesa-libGLES.x86_64 13.0.3-5.fc25 @updates mesa-libGLU.i686 9.0.0-10.fc24 @fedora mesa-libGLU.x86_64 9.0.0-10.fc24 @fedora mesa-libGLU-devel.x86_64 9.0.0-10.fc24 @fedora mesa-libOSMesa.i686 13.0.3-5.fc25 @updates mesa-libOSMesa.x86_64 13.0.3-5.fc25 @updates mesa-libgbm.i686 13.0.3-5.fc25 @updates mesa-libgbm.x86_64 13.0.3-5.fc25 @updates mesa-libglapi.i686 13.0.3-5.fc25 @updates mesa-libglapi.x86_64 13.0.3-5.fc25 @updates mesa-libwayland-egl.x86_64 13.0.3-5.fc25 @updates mesa-libxatracker.x86_64 13.0.3-5.fc25 @updates mesa-vulkan-drivers.x86_64 13.0.3-5.fc25 @updates The nvidia driver version installed is 378.13.
xfdashboard-0.7.1-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-bfd9026dac
xfdashboard-0.7.1-1.fc26 has been pushed to the Fedora 26 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-2017-bfd9026dac
xfdashboard-0.7.2-1.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-6fa0f5cf36
xfdashboard-0.7.2-1.fc25 has been submitted as an update to Fedora 25. https://bodhi.fedoraproject.org/updates/FEDORA-2017-5a9bc913ed
xfdashboard-0.7.2-1.fc26 has been pushed to the Fedora 26 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-2017-6fa0f5cf36
xfdashboard-0.7.2-1.fc25 has been pushed to the Fedora 25 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-2017-5a9bc913ed
xfdashboard-0.7.2-1.fc25 has been pushed to the Fedora 25 stable repository. If problems still persist, please make note of it in this bug report.
xfdashboard-0.7.2-1.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.