Bug 304703

Summary: Kwin crashes when changing the color scheme
Product: [Plasma] kwin Reporter: Daniel Añez Scott <danielscott171>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash Keywords: triaged
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Daniel Añez Scott 2012-08-07 04:01:18 UTC 
Application: kwin (4.8.4 (4.8.4))
KDE Platform Version: 4.9.00
Qt Version: 4.8.1
Operating System: Linux 3.2.0-27-generic x86_64
Distribution: Ubuntu 12.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Changing the color scheme in apperance properties
- Unusual behavior I noticed:
Kwin decorations dissapeared/bugged, and composition sometimes disabled
- Custom settings of the application:

The crash can be reproduced every time.

-- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fb0d8a0b780 (LWP 1709))]

Thread 3 (Thread 0x7fb0b7fff700 (LWP 1713)):
#0  0x00007fb0d8216823 in select () at ../sysdeps/unix/syscall-template.S:82
#1  0x00007fb0d3a63366 in qt_safe_select (nfds=20, fdread=0x7fb0ac000ac8, fdwrite=0x7fb0ac000d60, fdexcept=0x7fb0ac000ff8, orig_timeout=<optimized out>) at kernel/qcore_unix.cpp:83
#2  0x00007fb0d3a687b2 in QEventDispatcherUNIXPrivate::doSelect (this=0x7fb0ac000910, flags=..., timeout=0x0) at kernel/qeventdispatcher_unix.cpp:223
#3  0x00007fb0d3a68ca3 in QEventDispatcherUNIX::processEvents (this=0x7fb0ac0008f0, flags=...) at kernel/qeventdispatcher_unix.cpp:926
#4  0x00007fb0d3a35c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007fb0d3a35ed7 in QEventLoop::exec (this=0x7fb0b7ffedd0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007fb0d3934fa7 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007fb0d3a159ff in QInotifyFileSystemWatcherEngine::run (this=0xb1fef0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007fb0d3937fcb in QThreadPrivate::start (arg=0xb1fef0) at thread/qthread_unix.cpp:298
#9  0x00007fb0ccb5ee9a in start_thread (arg=0x7fb0b7fff700) at pthread_create.c:308
#10 0x00007fb0d821d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7fb0b77fe700 (LWP 1714)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007fb0d4ccf222 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007fb0d4ccf259 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007fb0ccb5ee9a in start_thread (arg=0x7fb0b77fe700) at pthread_create.c:308
#4  0x00007fb0d821d4bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fb0d8a0b780 (LWP 1709)):
[KCrash Handler]
#6  0x00007fb0bd655f10 in ?? () from /usr/lib/kde4/kwin3_oxygen.so
#7  0x00007fb0d65a1d52 in KDecorationPlugins::reset(unsigned long) () from /usr/lib/libkdecorations.so.4
#8  0x00007fb0d852c0a1 in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#9  0x00007fb0d852c7da in ?? () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#10 0x00007fb0d3a4b281 in QMetaObject::activate (sender=0x98dc88, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547
#11 0x00007fb0d3a50179 in QObject::event (this=0x98dc88, e=<optimized out>) at kernel/qobject.cpp:1157
#12 0x00007fb0d2db9894 in notify_helper (e=0x7fffe099af60, receiver=0x98dc88, this=0x920c90) at kernel/qapplication.cpp:4559
#13 QApplicationPrivate::notify_helper (this=0x920c90, receiver=0x98dc88, e=0x7fffe099af60) at kernel/qapplication.cpp:4531
#14 0x00007fb0d2dbe713 in QApplication::notify (this=0x7fffe099b380, receiver=0x98dc88, e=0x7fffe099af60) at kernel/qapplication.cpp:4420
#15 0x00007fb0d7cf7456 in KApplication::notify (this=0x7fffe099b380, receiver=0x98dc88, event=0x7fffe099af60) at ../../kdeui/kernel/kapplication.cpp:311
#16 0x00007fb0d3a36e9c in QCoreApplication::notifyInternal (this=0x7fffe099b380, receiver=0x98dc88, event=0x7fffe099af60) at kernel/qcoreapplication.cpp:876
#17 0x00007fb0d3a681f2 in sendEvent (event=0x7fffe099af60, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#18 QTimerInfoList::activateTimers (this=0x9217d8) at kernel/qeventdispatcher_unix.cpp:611
#19 0x00007fb0d3a68cb4 in QEventDispatcherUNIX::processEvents (this=0x8bcad0, flags=...) at kernel/qeventdispatcher_unix.cpp:930
#20 0x00007fb0d2e62bf8 in QEventDispatcherX11::processEvents (this=0x8bcad0, flags=...) at kernel/qeventdispatcher_x11.cpp:152
#21 0x00007fb0d3a35c82 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#22 0x00007fb0d3a35ed7 in QEventLoop::exec (this=0x7fffe099b2c0, flags=...) at kernel/qeventloop.cpp:204
#23 0x00007fb0d3a3af67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#24 0x00007fb0d8548c36 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_kwin.so
#25 0x00007fb0d814c76d in __libc_start_main (main=0x400640, argc=1, ubp_av=0x7fffe099baa8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffe099ba98) at libc-start.c:226
#26 0x0000000000400671 in _start ()

Possible duplicates by query: bug 268179.

Reported using DrKonqi
Comment 1 Thomas Lübking 2012-08-07 13:04:09 UTC 
The trace still lacks all relevant debug symbols.

Afaik you need esp. this package for ubuntu:
http://packages.ubuntu.com/precise/kde-workspace-dbg

resp. the matching backport.
Comment 2 Daniel Añez Scott 2012-08-08 17:10:08 UTC 
I suspect there's a bug in the bug reporting tool too... I clicked on "install debug symbols" and they're already installed, I already checked in Muon. But it still says "install debug symbols" and doesn't do anything different than before installing them. 
Is there any way to get you the data you need using the command line, or searching for a log file or something?

Thanks a lot for your patience.
Comment 3 Thomas Lübking 2012-08-08 18:39:14 UTC 
You have this Package installed?
http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu/pool/main/k/kde-workspace/kde-workspace-dbg_4.9.0-0ubuntu2~precise1~ppa1_amd64.deb

I don't know how Ubuntu invokes the debug libraries (ie. by replacing the stripped ones or invoking them only conditionally) but if you've that package installed, it's supposed to shib libraries with present debug symbols. If not, there's a bug in Ubuntu (you'll have to ask for more help there - at least i don't know anything about their linkage in this regard)

It's very likely important to at least restart kwin after installing the debug libs and before causing the crash (in doubt log out & back in)

There's no bug in the debug tool in the tracing part (there are just no debug symbols in the loaded lib)
The "install debug symbols" button seems a Ubuntu specific extension (i don't have such in the crashhandler dialog)
Comment 4 Andrew Crouthamel 2018-09-23 02:20:01 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 5 Andrew Crouthamel 2018-10-27 03:32:40 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!