Bug 241163 - Kwin crashes unexpectedly when opening yast2
Summary: Kwin crashes unexpectedly when opening yast2
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: triaged
: 254568 256196 257794 259155 261832 265238 267005 268642 268902 269214 269387 270873 271118 274616 275679 277271 281290 281867 301642 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-06-09 03:41 UTC by jason.mours
Modified: 2018-10-27 09:07 UTC (History)
16 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Patch to pot. fix the mysterious __cxa_rethrow bug (4.05 KB, patch)
2011-03-13 22:47 UTC, Thomas Lübking
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jason.mours 2010-06-09 03:41:42 UTC
Application: kwin (4.4.3 (KDE 4.4.3))
KDE Platform Version: 4.4.3 (KDE 4.4.3)
Qt Version: 4.6.2
Operating System: Linux 2.6.31.12-0.2-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

-- Information about the crash:
Machine was on for 5 hours. Firefox, konsole, & thunderbird were minimized. Tried to open yast2 and kwin crashes, restoring all windows with no window manager i.e. lack of borders. Kwin restarted. openSuSE 11.2-updates, KDE 4.4.X factory repo, fglrx 10.5

 -- Backtrace:
Application: KWin (kwin), signal: Aborted
[KCrash Handler]
#5  0x00007f45627c34e5 in raise () from /lib64/libc.so.6
#6  0x00007f45627c49b0 in abort () from /lib64/libc.so.6
#7  0x00007f455e1fbdc5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib64/libstdc++.so.6
#8  0x00007f455e1fa1f6 in ?? () from /usr/lib64/libstdc++.so.6
#9  0x00007f455e1fa223 in std::terminate() () from /usr/lib64/libstdc++.so.6
#10 0x00007f455e1fa2a6 in __cxa_rethrow () from /usr/lib64/libstdc++.so.6
#11 0x00007f455e7cb7cd in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#12 0x00007f455e7cf3cb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#13 0x00007f4562bafe5a in kdemain (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.4.3/kwin/main.cpp:526
#14 0x00007f45627afa7d in __libc_start_main () from /lib64/libc.so.6
#15 0x0000000000400699 in _start () at ../sysdeps/x86_64/elf/start.S:113

Possible duplicates by query: bug 241155, bug 241126, bug 240906, bug 240793, bug 240765.

Reported using DrKonqi
Comment 1 Martin Flöser 2010-06-10 19:25:11 UTC
This backtrace doesn't say anything. Looks like another issue with glibc to me. But if the duplicate searches are correct the issue might be fixed.
Comment 2 Thomas Lübking 2010-12-07 19:13:18 UTC
*** Bug 256196 has been marked as a duplicate of this bug. ***
Comment 3 Thomas Lübking 2010-12-07 19:13:43 UTC
I'm gonna merge in some other "uncatched exception in Qt eventloop" bugs i googled up... this starts to get annoying... :-\
Comment 4 Thomas Lübking 2010-12-07 19:13:59 UTC
*** Bug 257794 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Lübking 2010-12-07 19:14:07 UTC
*** Bug 259155 has been marked as a duplicate of this bug. ***
Comment 6 Thomas Lübking 2010-12-07 19:27:48 UTC
The problem about this bug is that "something" (*cough* i just blame plasma, cause it ... *cough*) throws an exception from a slot which isn't catched in the slot and enters the Qt eventloop which then - w/o any further detailed information just asserts (very smart implementation, indeed)

This so far didn't happen to me, ever.

Handling)
---------
If -> you have got a somewhat reliably way to reproduce the issue:

There a chance that info about the exception is printed to konsole when you run kwin from there ("kwin --replace &")
It can _maybe_ also be found in ~/.xsession-errors

You can run "gdb --args kwin --replace" and "catch throw" to have gdb catch throws and acquire a backtrace using "bt"

If you happen to compile Qt from sources, --- export QT_NO_EXCEPTIONS as CFLAG ---
This should produce a usable backtrace. ;-P
Comment 7 Thomas Lübking 2011-02-03 00:07:22 UTC
*** Bug 265238 has been marked as a duplicate of this bug. ***
Comment 8 Thomas Lübking 2011-02-23 21:42:23 UTC
*** Bug 267005 has been marked as a duplicate of this bug. ***
Comment 9 Thomas Lübking 2011-03-13 22:47:38 UTC
Created attachment 57939 [details]
Patch to pot. fix the mysterious __cxa_rethrow bug

Thanks to Michal Pekař from bug #268384 we've possibly identified the source of the bug (plasma seems off the hook ;-)

a) it seems to be caused by the lanczos filter, so set the scale method to "smooth" ("kcmshell4 kwincompositing" / "Advanced" tab)
b) attached is a patch against the 4.6 branch (will likely apply to all 4.6 versions, bt not 4.7) - it would be very helpful if someone being able to (semi)reliably reproduce the segfault could test this and report on the outcome. (because we cannot say whether all bugs derive from the same source)
Comment 10 Thomas Lübking 2011-03-16 15:41:28 UTC
*** Bug 268642 has been marked as a duplicate of this bug. ***
Comment 11 Thomas Lübking 2011-03-19 16:25:29 UTC
*** Bug 268902 has been marked as a duplicate of this bug. ***
Comment 12 Thomas Lübking 2011-03-19 17:19:43 UTC
*** Bug 261832 has been marked as a duplicate of this bug. ***
Comment 13 Thomas Lübking 2011-03-23 14:46:12 UTC
*** Bug 269214 has been marked as a duplicate of this bug. ***
Comment 14 Thomas Lübking 2011-03-25 16:54:12 UTC
*** Bug 269387 has been marked as a duplicate of this bug. ***
Comment 15 Thomas Lübking 2011-04-13 21:58:26 UTC
*** Bug 270873 has been marked as a duplicate of this bug. ***
Comment 16 Thomas Lübking 2011-04-16 21:59:43 UTC
*** Bug 271118 has been marked as a duplicate of this bug. ***
Comment 17 Thomas Lübking 2011-04-19 02:36:48 UTC
Git commit 505f7cc14a7ee9914a7d75128e28476ead34b9e0 by Thomas Lübking.
Committed on 19/04/2011 at 02:41.
Pushed by luebking into branch 'KDE/4.6'.

Validate/check logarry in lanczos filter

this will *probably* fix the mysterious __cxa_rethrow bug
we still need validation from someone encountering the bug

CCBUG: 241163

M  +64   -28   kwin/lib/kwinglutils.cpp     

http://commits.kde.org/kde-workspace/505f7cc14a7ee9914a7d75128e28476ead34b9e0
Comment 18 Martin Flöser 2011-05-07 10:19:56 UTC
*** Bug 254568 has been marked as a duplicate of this bug. ***
Comment 19 Thomas Lübking 2011-05-31 19:29:14 UTC
*** Bug 274616 has been marked as a duplicate of this bug. ***
Comment 20 Thomas Lübking 2011-06-15 09:00:03 UTC
*** Bug 275679 has been marked as a duplicate of this bug. ***
Comment 21 Thomas Lübking 2011-07-07 12:10:17 UTC
*** Bug 277271 has been marked as a duplicate of this bug. ***
Comment 22 Thomas Lübking 2011-09-03 21:52:18 UTC
*** Bug 281290 has been marked as a duplicate of this bug. ***
Comment 23 Thomas Lübking 2011-09-12 15:50:24 UTC
*** Bug 281867 has been marked as a duplicate of this bug. ***
Comment 24 Thomas Lübking 2012-06-11 12:28:41 UTC
*** Bug 301642 has been marked as a duplicate of this bug. ***
Comment 25 Andrew Crouthamel 2018-09-23 02:41:28 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 26 Andrew Crouthamel 2018-10-27 04:13:35 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!