Bug 182765 - kwin crash at close and logout
Summary: kwin crash at close and logout
Status: RESOLVED DUPLICATE of bug 182462
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
Depends on:
Reported: 2009-02-01 19:42 UTC by BRULE Herman
Modified: 2009-02-09 15:16 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2009-02-01 19:42:44 UTC
Version:            (using KDE 4.2.0)
Installed from:    Gentoo Packages

Related maybe of:
I have save the trace, but when I have go see it the file is empty.
Comment 1 Martin Flöser 2009-02-09 11:49:06 UTC
If you are able to reproduce the crash please include the backtrace. With current information this bug is totally useless.

Please have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 BRULE Herman 2009-02-09 13:11:55 UTC
yes I know but it's random bug, then hard to reproduct it and unable to save the bug.
Comment 3 BRULE Herman 2009-02-09 14:42:17 UTC
Application: KWin (kwin), signal SIGABRT
0x00007fe18bd63870 in __nanosleep_nocancel () from /lib/libc.so.6
Current language:  auto; currently c

Thread 1 (Thread 0x7fe19159a760 (LWP 5527)):
[KCrash Handler]
#5  0x00007fe18bcf61e5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x00007fe18bcf7703 in *__GI_abort () at abort.c:88
#7  0x00007fe18bcef229 in *__GI___assert_fail (assertion=0x7fe189bb9cdb "!c->xlib.lock", file=0x7fe189bb9cd0 "xcb_xlib.c", line=73, function=0x7fe189bb9d00 "xcb_xlib_lock") at assert.c:78
#8  0x00007fe189bb9c11 in xcb_xlib_lock (c=0x247e4c0) at xcb_xlib.c:73
#9  0x00007fe18e2f3c80 in _XCBLockDisplay (dpy=0x247c9b0) at xcb_lock.c:21
#10 0x00007fe18c9c8cb6 in XRenderFreePicture (dpy=0x247c9b0, picture=20971726) at Picture.c:236
#11 0x00007fe18ec3227b in QX11PixmapData::release (this=0x2586490) at image/qpixmap_x11.cpp:1179
#12 0x00007fe18ec32ba0 in ~QX11PixmapData (this=0x1597) at image/qpixmap_x11.cpp:1155
#13 0x00007fe18ec284a3 in QPixmap::deref (this=0x25246c8) at image/qpixmap.cpp:1264
#14 0x00007fe18ec287e4 in ~QPixmap (this=0x1597) at image/qpixmap.cpp:326
#15 0x00007fe18ed1a174 in ~QX11PaintEnginePrivate (this=0x2524670) at ../../include/QtGui/private/../../../src/gui/painting/qpaintengine_x11_p.h:144
#16 0x00007fe18ed10849 in ~QX11PaintEngine (this=0x25b09a0) at painting/qpaintengine_x11.cpp:451
#17 0x00007fe18ebf6855 in ~QGlobalStaticDeleter (this=0x7fe18f529e68) at ../../include/QtCore/../../src/corelib/global/qglobal.h:1563
#18 0x00007fe18bcf8d8d in *__GI_exit (status=1) at exit.c:75
#19 0x00007fe18e2ecc3d in _XDefaultError (dpy=<value optimized out>, event=<value optimized out>) at XlibInt.c:2860
#20 0x00007fe18e2ecdac in _XError (dpy=0x247c9b0, rep=0x2608160) at XlibInt.c:2912
#21 0x00007fe18e2f45bf in process_responses (dpy=0x247c9b0, wait_for_first_event=0, current_error=0x7fff995d1278, current_request=315871) at xcb_io.c:138
#22 0x00007fe18e2f4962 in _XReply (dpy=0x247c9b0, rep=0x7fff995d12c0, extra=0, discard=1) at xcb_io.c:370
#23 0x00007fe18e2e86b2 in XSync (dpy=0x247c9b0, discard=1) at Sync.c:48
#24 0x00007fe18e2c7c1f in XCloseDisplay (dpy=0x247c9b0) at ClDisplay.c:67
#25 0x00007fe18ebcc635 in qt_cleanup () at kernel/qapplication_x11.cpp:2325
#26 0x00007fe18eb725cf in ~QApplication (this=0x7fff995d1490) at kernel/qapplication.cpp:1019
#27 0x00007fe1911301f2 in kdemain (argc=<value optimized out>, argv=0x7fff995d1968) at /var/tmp/portage/kde-base/kwin-4.2.0/work/kwin-4.2.0/kwin/main.cpp:519
#28 0x00007fe18bce25c6 in __libc_start_main (main=0x400a00 <main>, argc=3, ubp_av=0x7fff995d1968, init=0x400a30 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, 
    stack_end=0x7fff995d1958) at libc-start.c:226
#29 0x0000000000400939 in _start ()

Comment 4 Martin Flöser 2009-02-09 15:16:09 UTC
Thanks for taking the time to generate the backtrace. But we already have this one.

*** This bug has been marked as a duplicate of bug 182462 ***