Bug 348624 - Error message when viewing windows settings
Summary: Error message when viewing windows settings
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: compositing (show other bugs)
Version: 5.3.1
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2015-06-03 10:03 UTC by Piotr Belniak
Modified: 2018-10-27 02:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Step 1 (100.67 KB, image/png)
2015-06-07 13:32 UTC, Piotr Belniak
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Piotr Belniak 2015-06-03 10:03:18 UTC
Application: kdeinit5 (5.3.1)

Qt Version: 5.4.1
Operating System: Linux 3.19.0-18-generic x86_64
Distribution: Ubuntu 15.04

-- Information about the crash:
- What I was doing when the application crashed:

I was  viewing window composer settings
- In the view engine combobox there was a text OpenGL 3.1
- I clicked this cobobox and choose the OpenGL 3.1 again
- Then i clicked Cancel in the dialog
After that error message appeared.

-- Backtrace:
Application: Moduł ustawień KDE (kdeinit5), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f45e3230780 (LWP 6033))]

Thread 3 (Thread 0x7f45cd53f700 (LWP 6034)):
[KCrash Handler]
#6  0x00007f45e185d267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007f45e185eeca in __GI_abort () at abort.c:89
#8  0x00007f45e18a0c53 in __libc_message (do_abort=do_abort@entry=1, fmt=fmt@entry=0x7f45e19b91a8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#9  0x00007f45e18a8c69 in malloc_printerr (ptr=<optimized out>, str=0x7f45e19b92b8 "double free or corruption (out)", action=1) at malloc.c:4965
#10 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3834
#11 0x00007f45e18ac89c in __GI___libc_free (mem=<optimized out>) at malloc.c:2950
#12 0x00007f45ddf27af6 in _nv007tls () from /usr/lib/nvidia-346/tls/libnvidia-tls.so.346.59
#13 0x00007f45df4b1359 in __nptl_deallocate_tsd () at pthread_create.c:175
#14 0x00007f45df4b276d in __nptl_deallocate_tsd () at ../sysdeps/unix/sysv/linux/exit-thread.h:36
#15 start_thread (arg=0x7f45cd53f700) at pthread_create.c:346
#16 0x00007f45e192eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f45b3d57700 (LWP 6037)):
#0  0x00007f45e19238dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f45dea55ebc in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f45dea55fcc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f45e1f2cc6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f45e1ed13e2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f45e1c90b44 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f45d12b9f65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#7  0x00007f45e1c95b0e in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f45df4b26aa in start_thread (arg=0x7f45b3d57700) at pthread_create.c:333
#9  0x00007f45e192eeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f45e3230780 (LWP 6033)):
#0  0x00007f45e19238dd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f45dfd5eb72 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f45dfd603ff in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f45dfd60512 in xcb_wait_for_reply () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#4  0x00007f45e217169f in _XReply () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5  0x00007f45e216d28d in XSync () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#6  0x00007f45e214f5be in XCloseDisplay () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#7  0x00007f45d02cf1f4 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#8  0x00007f45d02cf619 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#9  0x00007f45d02d3d3e in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#10 0x00007f45d02d3e19 in ?? () from /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so
#11 0x00007f45e2bdc5c0 in QGuiApplicationPrivate::~QGuiApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#12 0x00007f45e02d04e9 in QApplicationPrivate::~QApplicationPrivate() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f45e1f0d83b in QObject::~QObject() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f45e02d2133 in QApplication::~QApplication() () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#15 0x00007f45d07dd480 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kcmshell5.so
#16 0x0000000000408716 in ?? ()
#17 0x000000000040a132 in ?? ()
#18 0x000000000040a6ee in ?? ()
#19 0x000000000040501b in main ()

Reported using DrKonqi
Comment 1 Christoph Feck 2015-06-07 10:27:44 UTC
Does is also crash if you uninstall nvidia binary drivers?
Comment 2 Thomas Lübking 2015-06-07 13:10:32 UTC
Did you *only* open the compositor settings ("kcmshell5 kwincompositing") or did you choose "More Actions/Window manager settings" from the titlebar rightclick menu?

In case this is reproducible, is it also reproducible with *only* the compositor kcm (run "kcmshell5 kwincompositing")?
Comment 3 Piotr Belniak 2015-06-07 13:32:48 UTC
Created attachment 93053 [details]
Step 1
Comment 4 Piotr Belniak 2015-06-07 13:38:02 UTC
Sorry  - I wanted to add screenshots :)
btw to be 100% precise - it is 100% reproducible on 2 independent PC's
 - step 1 - choose
More Actions/Window manager settings
(Rendering engine is OpenGL 3.1)
- step 2 - change Rendering engine to OpenGL 2.0 ( do not apply change)
- step 3 - go back to previous value (3.1)
- step 4 - click Cancel button
- error message will appear.
I am using Nvidia driver. Will do that test on another PC with intel graphics card later.
Comment 5 Thomas Lübking 2015-06-07 14:04:25 UTC
This has probably nothing to do with the driver or even the compositing kcm.
Please close the dialog and (from konsole or krunner) run
   kcmshell5 kwincompositing

this will open only the compositing config dialog.
Try to cause the crash there and report back.
Comment 6 Piotr Belniak 2015-06-07 14:37:28 UTC
When invoking the settings dialog by this command:
 kcmshell5 kwincompositing
issue is not appearing.
Comment 7 Thomas Lübking 2015-06-07 14:45:05 UTC
This is most likely related to bug #346748 then.
And apparently the approach to avoid it failed =(
Comment 8 Martin Flöser 2016-08-29 07:23:55 UTC
Unfortunately the backtrace is missing debug symbols. This makes it impossible to proper investigate. If you are still able to reproduce please install debug symbols and attach a new backtrace. Sorry that we forgot to ask you about this really important step in a timely manner.
Comment 9 Andrew Crouthamel 2018-09-26 22:26:07 UTC
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 set the bug status 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!
Comment 10 Andrew Crouthamel 2018-10-27 02:36:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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

Thank you for helping us make KDE software even better for everyone!