Bug 182923 - random unpredictable kwin crash on boot
Summary: random unpredictable kwin crash on boot
Status: RESOLVED REMIND
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-02 22:47 UTC by zerobaba
Modified: 2009-02-19 09:55 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description zerobaba 2009-02-02 22:47:41 UTC
Version:            (using KDE 4.1.4)
OS:                Linux
Installed from:    Ubuntu Packages

How to reproduce? No idea, the crash report randomly shows up after some boots (or rather kde starts, but it is the same for me), and nothing peculiar happens at other times. I'm grateful that KDE is so great that it continues seamlessly despite the previous kwin instance's crash.

I run KDE with compositing enabled. Selected desktop effects:
Track Mouse, Blur, Dialog Parent, Dim Screen for Adm., Fade, Login, Logout, Minimize Anim., Present Windows, Scale In, Shadows, Translucency, Scaling, Wobbly, Box Switch, Cover Switch, Desktop Grid, Taskbar Thumbs. It is not easy to triage whether they influence the phenomenon, because a crash happens so randomly.

I use the 177.82 nVidia driver with a GeForce 7600 GT.


Application: KWin (kwin), signal SIGSEGV
0x00007f03ff3456b0 in __nanosleep_nocancel () from /lib/libc.so.6

Thread 1 (Thread 0x7f03f70a1730 (LWP 6130)):
[KCrash Handler]
#5  0x00007f03ff31969a in _int_malloc () from /lib/libc.so.6
#6  0x00007f03ff31ab44 in _int_realloc () from /lib/libc.so.6
#7  0x00007f03ff31bbde in realloc () from /lib/libc.so.6
#8  0x00007f03fd4445b3 in ?? () from /usr/lib/libQtGui.so.4
#9  0x00007f03fd43cd50 in ?? () from /usr/lib/libQtGui.so.4
#10 0x00007f03fd43f204 in ?? () from /usr/lib/libQtGui.so.4
#11 0x00007f03fd43f5c0 in ?? () from /usr/lib/libQtGui.so.4
#12 0x00007f03fd441383 in QRegion::operator+= () from /usr/lib/libQtGui.so.4
#13 0x00007f03ff68f04c in ?? () from /usr/lib/libkdeinit4_kwin.so
#14 0x00007f03ff6598d2 in ?? () from /usr/lib/libkdeinit4_kwin.so
#15 0x00007f03ff65da3e in ?? () from /usr/lib/libkdeinit4_kwin.so
#16 0x00007f03ff64afd8 in ?? () from /usr/lib/libkdeinit4_kwin.so
#17 0x00007f03fd35b7ef in ?? () from /usr/lib/libQtGui.so.4
#18 0x00007f03fd36ce26 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#19 0x00007f03fd3952c4 in ?? () from /usr/lib/libQtGui.so.4
#20 0x00007f03fabdbd3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0x00007f03fabdf50d in ?? () from /usr/lib/libglib-2.0.so.0
#22 0x00007f03fabdf6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0x00007f03fe74715f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#24 0x00007f03fd394a6f in ?? () from /usr/lib/libQtGui.so.4
#25 0x00007f03fe71d682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f03fe71d80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0x00007f03fe71fcbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#28 0x00007f03ff64ea01 in kdemain () from /usr/lib/libkdeinit4_kwin.so
#29 0x00007f03ff2bb466 in __libc_start_main () from /lib/libc.so.6
#30 0x0000000000400659 in _start ()
Comment 1 David Nadlinger 2009-02-02 22:54:59 UTC
The obvious reply: Could you please install the debugging symbols for KWin and Qt in order to create an useful backtrace the next time KWin crashes?

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 zerobaba 2009-02-02 23:19:27 UTC
I've already installed a bunch of kde and qt debug symbol packages for the exact same purpose. Maybe I missed some of the important ones, I'll look into it.
Comment 3 Dario Andres 2009-02-03 13:26:21 UTC
You need "libqt4-dbg", "kdebase-workspace-dbg"
:)
Comment 4 Martin Flöser 2009-02-19 09:55:02 UTC
No response for more than two weeks and by that I'm marking this bug as resolve remind. Please reopen after providing useful backtrace