Bug 241235

Summary: Kwin crashed after each apply to the changes
Product: [Plasma] kwin Reporter: Danial Behzadi <dani.behzi>
Component: generalAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED WORKSFORME    
Severity: crash CC: dani.behzi
Priority: NOR Keywords: investigated, triaged
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Danial Behzadi 2010-06-09 21:29:10 UTC 
Application that crashed: kwin
Version of the application: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1"
KDE Version: 4.2.86 (KDE 4.2.86 (KDE 4.3 >= 20090514)) "release 1"
Qt Version: 4.5.1
Operating System: Linux 2.6.31.5-0.1-debug x86_64
Distribution: "openSUSE 11.2 Milestone 2 (x86_64)"

What I was doing when the application crashed:
When I changes somthing related to Kwin such as Desktop Effects and I press "Apply", each time Kwin crashs

 -- Backtrace:
Application: KWin (kwin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f27bd2b60db in memcpy () from /lib64/libc.so.6
#6  0x00007f27c2c083b9 in ?? () from /usr/X11R6/lib64/libGL.so.1
#7  0x00007f27b498fa73 in ?? () from /usr/lib64/kde4/kwin4_effect_builtins.so
#8  0x00007f27c2986c43 in ?? () from /usr/lib64/libkdeinit4_kwin.so
#9  0x00007f27c2987148 in ?? () from /usr/lib64/libkdeinit4_kwin.so
#10 0x00007f27c29686a8 in ?? () from /usr/lib64/libkdeinit4_kwin.so
#11 0x00007f27c290120d in KSelectionOwner::genericReply(unsigned long, unsigned long, unsigned long) () from /usr/lib64/libkdeinit4_kwin.so
#12 0x00007f27c2908ae5 in KSelectionOwner::genericReply(unsigned long, unsigned long, unsigned long) () from /usr/lib64/libkdeinit4_kwin.so
#13 0x00007f27c0350348 in ?? () from /usr/lib64/libQtDBus.so.4
#14 0x00007f27c0357b4f in ?? () from /usr/lib64/libQtDBus.so.4
#15 0x00007f27c0046bf9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007f27c073711c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f27c073e74e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#18 0x00007f27c1c5f826 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#19 0x00007f27c00370ec in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f27c0037bda in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#21 0x00007f27c0060783 in ?? () from /usr/lib64/libQtCore.so.4
#22 0x00007f27b910aafe in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f27b910e258 in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f27b910e3cc in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f27c00603f6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f27c07cb99e in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f27c00359c2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f27c0035d94 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f27c0037e89 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#30 0x00007f27c291f464 in kdemain () from /usr/lib64/libkdeinit4_kwin.so
#31 0x00007f27bd25659d in __libc_start_main () from /lib64/libc.so.6
#32 0x0000000000400849 in _start ()
Comment 1 Danial Behzadi 2010-06-09 21:35:40 UTC 
And after crash compositing state goes disable
Comment 2 Thomas Lübking 2010-06-09 21:43:40 UTC 
unfortunately the backtrace lacks important information, so all one can see is that the segfault happens from a mesa/gl driver call.
compositing is disabled to prevent further crashes.

please read here on how to create useful backtraces and update the report, thanks. (for suse install the -debuginfo packages)

in general:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

and for openSuSE in particular:
http://en.opensuse.org/Bugs:An_application_crashed
Comment 3 Martin Flöser 2010-06-10 19:19:15 UTC 
most likely a driver bug - top most item is libGL. But without a proper backtrace we can't say anything
Comment 4 Andrew Crouthamel 2018-09-20 22:07:35 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-21 05:03:01 UTC 
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!