Summary: | Info Center crashed after unlocking screen and switching from Wayland info section to OpenGL info section | ||
---|---|---|---|
Product: | [Applications] kinfocenter | Reporter: | drloera |
Component: | OpenGL | Assignee: | David Hubner <hubn3rd> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | ekigwana, kde, notuxius, null, sitter, wuelpi |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
KInfoCenter crash info
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
Description
drloera
2016-09-23 04:52:50 UTC
I hit the same error. * open KInfoCenter * click around the various sections * Every now and then when clicking "OpenGL" section KInfoCenter crashes: I managed to make it crash twice and I clicked on it tens of times. When I'll manage to make it crash again I'll attach the report from DrKonqi. I am on OpenSUSE Tumbleweed 20160926 Created attachment 101327 [details]
KInfoCenter crash info
Valid on mageia 6 with Plasma 5.8.5 Created attachment 108249 [details]
New crash information added by DrKonqi
kinfocenter (5.11.90) using Qt 5.9.1
- What I was doing when the application crashed:
UI input: kinfocenter -> graphical Information -> OpenGL
UI input: kinfocenter -> graphical Information -> X-Server
Alternate selection of both and crash occurs within 5 clicks.
On the console I see several messages of this nature that I'm not sure are related:
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_QUERY_COUNTER_BITS)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_VERTEX_UNITS_ARB)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_PALETTE_MATRICES_ARB)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_COLOR_MATRIX_STACK_DEPTH)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_MATRIX_PALETTE_STACK_DEPTH_ARB)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_PROGRAM_ENV_PARAMETERS_ARB)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_PROGRAM_LOCAL_PARAMETERS_ARB)
Mesa: User error: GL_INVALID_ENUM in glGetIntegerv(pname=GL_MAX_PROGRAM_INSTRUCTIONS_ARB)
...
This has been around for a while I just never had debugging enabled os a bug report would have been useless. It seems like it works the first time OpenGL is selected and maybe a second time but thats all the chances you get. Yeah wierd for someone to click back and forth but with GLX and EGL in mesa it is annoying to not know what backend is selected. My panel is not rendered properly so I took it out on kinfocenter :)
-- Backtrace (Reduced):
#6 0x00007fbb5055e642 in xcb_send_request_with_fds64 (c=0x209baf0, flags=flags@entry=0, vector=vector@entry=0x7ffe3aad3290, req=req@entry=0x7fbb50570ad0 <xcb_req>, num_fds=num_fds@entry=0, fds=fds@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_out.c:274
#7 0x00007fbb5055e7cb in xcb_send_request64 (c=<optimized out>, flags=flags@entry=0, vector=vector@entry=0x7ffe3aad3290, req=req@entry=0x7fbb50570ad0 <xcb_req>) at /var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_out.c:349
#8 0x00007fbb5055e7d9 in xcb_send_request (c=<optimized out>, flags=flags@entry=0, vector=vector@entry=0x7ffe3aad3290, req=req@entry=0x7fbb50570ad0 <xcb_req>) at /var/tmp/portage/x11-libs/libxcb-1.12-r2/work/libxcb-1.12/src/xcb_out.c:355
#9 0x00007fbb50567ca5 in xcb_free_pixmap (c=<optimized out>, pixmap=<optimized out>) at xproto.c:6579
#10 0x00007fbb285b4960 in dri3_free_render_buffer (buffer=0x1f08f40, draw=<optimized out>, draw=<optimized out>) at /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/loader/loader_dri3_helper.c:219
Created attachment 111292 [details]
New crash information added by DrKonqi
kinfocenter (5.12.80) using Qt 5.10.1
- What I was doing when the application crashed:
Open kinfocenter and alternate clicks between opengl and xserver.
-- Backtrace (Reduced):
#6 0x00007f574e2f5641 in xcb_send_request_with_fds64 (c=0x56510772e7a0, flags=flags@entry=1, vector=vector@entry=0x7ffca9e25010, req=req@entry=0x7f574e309540 <xcb_req>, num_fds=num_fds@entry=0, fds=fds@entry=0x0) at /var/tmp/portage/x11-libs/libxcb-1.13/work/libxcb-1.13/src/xcb_out.c:274
#7 0x00007f574e2f57cb in xcb_send_request64 (c=<optimized out>, flags=flags@entry=1, vector=vector@entry=0x7ffca9e25010, req=req@entry=0x7f574e309540 <xcb_req>) at /var/tmp/portage/x11-libs/libxcb-1.13/work/libxcb-1.13/src/xcb_out.c:349
#8 0x00007f574e2f57d9 in xcb_send_request (c=<optimized out>, flags=flags@entry=1, vector=vector@entry=0x7ffca9e25010, req=req@entry=0x7f574e309540 <xcb_req>) at /var/tmp/portage/x11-libs/libxcb-1.13/work/libxcb-1.13/src/xcb_out.c:355
#9 0x00007f574e2fc048 in xcb_get_geometry (c=<optimized out>, drawable=<optimized out>) at xproto.c:3008
#10 0x00007f5731400cc1 in loader_dri3_drawable_init (conn=<optimized out>, drawable=drawable@entry=67108873, dri_screen=0x5651072406d0, is_different_gpu=<optimized out>, multiplanes_available=<optimized out>, dri_config=0x565108c06e40, ext=0x565107449208, vtable=0x7f5731615020 <egl_dri3_vtable>, draw=0x565107447c80) at /var/tmp/portage/media-libs/mesa-9999/work/mesa-9999/src/loader/loader_dri3_helper.c:319
Can this be related to https://bugs.kde.org/show_bug.cgi?id=391486 and https://github.com/anholt/libepoxy/issues/160 ? Created attachment 117091 [details]
New crash information added by DrKonqi
kinfocenter (5.14.4) using Qt 5.12.0
- What I was doing when the application crashed:
Switching from OpenGL to xserver or vice versa on Wayland. Tumbleweed, QT5.12, Plasma 5.14.4, Frameworks 5.53
-- Backtrace (Reduced):
#6 xcb_send_request_with_fds64 (c=0x56516c6e0ec0, flags=flags@entry=1, vector=vector@entry=0x7fffb77126b0, req=req@entry=0x7f906234ff30 <xcb_req>, num_fds=num_fds@entry=0, fds=fds@entry=0x0) at xcb_out.c:274
#7 0x00007f906233ccbb in xcb_send_request64 (c=<optimized out>, flags=flags@entry=1, vector=vector@entry=0x7fffb77126b0, req=req@entry=0x7f906234ff30 <xcb_req>) at xcb_out.c:349
#8 0x00007f906233ccc9 in xcb_send_request (c=<optimized out>, flags=flags@entry=1, vector=vector@entry=0x7fffb77126b0, req=req@entry=0x7f906234ff30 <xcb_req>) at xcb_out.c:355
#9 0x00007f9062342e58 in xcb_get_geometry (c=<optimized out>, drawable=<optimized out>) at xproto.c:3008
#10 0x00007f903b4984f6 in loader_dri3_drawable_init (conn=<optimized out>, drawable=drawable@entry=69206025, dri_screen=0x56516c4b4c30, is_different_gpu=<optimized out>, multiplanes_available=<optimized out>, dri_config=0x56516bee9390, ext=0x56516bf57ce0, vtable=0x7f903b4adee0 <egl_dri3_vtable>, draw=0x56516c714290) at loader_dri3_helper.c:368
A year ago a similar bug got fixed: https://bugs.kde.org/show_bug.cgi?id=387479 maybe this information helps with fixing the bug. Is this still reproducible on newer Plasmas? There have been a few changes in the opengl path in KDE and in QT. I can no longer reproduce the bug. But I couldn't tell you what fixed it. Plasma: 5.17.80 Frameworks: 5.67.0 Qt: 5.14 Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! |