Application: kwin (4.8.4 (4.8.4)) KDE Platform Version: 4.8.4 (4.8.4) Qt Version: 4.8.2 Operating System: Linux 3.4.4-5.fc17.x86_64 x86_64 Distribution: "Fedora release 17 (Beefy Miracle)" -- Information about the crash: - What I was doing when the application crashed:When I boot in runlevel 5 (graphical mode) directly after logging on I get a white screen and a crash is reported The crash can be reproduced every time. -- Backtrace: Application: KWin (kwin), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82 T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7faaccd97880 (LWP 1617))] Thread 2 (Thread 0x7faabeb81700 (LWP 1639)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x00000035de784ac7 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x35dea919a0) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359 #2 0x00000035de784af9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464 #3 0x00000035bc807d14 in start_thread (arg=0x7faabeb81700) at pthread_create.c:309 #4 0x00000035bc0f199d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7faaccd97880 (LWP 1617)): [KCrash Handler] #6 QObject::setProperty (this=0x0, name=0x35dc712c2a "source", value=...) at kernel/qobject.cpp:3689 #7 0x00000035dc6ec80f in ?? () from /lib64/libkdeinit4_kwin.so #8 0x00000035dc6ec938 in ?? () from /lib64/libkdeinit4_kwin.so #9 0x00000035caa19ece in QWidget::event (this=0xb8c320, event=0x7fff30be67f0) at kernel/qwidget.cpp:8578 #10 0x00000035cadc3b46 in QFrame::event (this=0xb8c320, e=0x7fff30be67f0) at widgets/qframe.cpp:557 #11 0x00000035cae436fb in QAbstractScrollArea::event (this=0xb8c320, e=0x7fff30be67f0) at widgets/qabstractscrollarea.cpp:996 #12 0x00000035ca9ca37c in QApplicationPrivate::notify_helper (this=this@entry=0x85d910, receiver=receiver@entry=0xb8c320, e=e@entry=0x7fff30be67f0) at kernel/qapplication.cpp:4551 #13 0x00000035ca9ce7fa in QApplication::notify (this=0x7fff30be7680, receiver=0xb8c320, e=0x7fff30be67f0) at kernel/qapplication.cpp:4412 #14 0x00000035cb846756 in KApplication::notify (this=0x7fff30be7680, receiver=0xb8c320, event=0x7fff30be67f0) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #15 0x00000035c71763ee in QCoreApplication::notifyInternal (this=0x7fff30be7680, receiver=0xb8c320, event=0x7fff30be67f0) at kernel/qcoreapplication.cpp:915 #16 0x00000035caa1bed7 in sendEvent (event=0x7fff30be67f0, receiver=0xb8c320) at ../../src/corelib/kernel/qcoreapplication.h:231 #17 QWidgetPrivate::show_helper (this=this@entry=0x9eff80) at kernel/qwidget.cpp:7551 #18 0x00000035caa1c1c2 in QWidget::setVisible (this=0xb8c320, visible=<optimized out>) at kernel/qwidget.cpp:7773 #19 0x00000035dc6f5b45 in ?? () from /lib64/libkdeinit4_kwin.so #20 0x00000035c718cb9f in QMetaObject::activate (sender=0x9a2008, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3547 #21 0x00000035c718ab1c in QObject::event (this=0x9a2008, e=<optimized out>) at kernel/qobject.cpp:1157 #22 0x00000035ca9ca37c in QApplicationPrivate::notify_helper (this=this@entry=0x85d910, receiver=receiver@entry=0x9a2008, e=e@entry=0x7fff30be7040) at kernel/qapplication.cpp:4551 #23 0x00000035ca9ce7fa in QApplication::notify (this=0x7fff30be7680, receiver=0x9a2008, e=0x7fff30be7040) at kernel/qapplication.cpp:4412 #24 0x00000035cb846756 in KApplication::notify (this=0x7fff30be7680, receiver=0x9a2008, event=0x7fff30be7040) at /usr/src/debug/kdelibs-4.8.4/kdeui/kernel/kapplication.cpp:311 #25 0x00000035c71763ee in QCoreApplication::notifyInternal (this=0x7fff30be7680, receiver=0x9a2008, event=0x7fff30be7040) at kernel/qcoreapplication.cpp:915 #26 0x00000035c71a6d52 in sendEvent (event=0x7fff30be7040, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #27 QTimerInfoList::activateTimers (this=0x85e308) at kernel/qeventdispatcher_unix.cpp:611 #28 0x00000035c71a6db0 in QEventDispatcherUNIX::activateTimers (this=this@entry=0x80e720) at kernel/qeventdispatcher_unix.cpp:868 #29 0x00000035c71a6f08 in QEventDispatcherUNIX::processEvents (this=0x80e720, flags=...) at kernel/qeventdispatcher_unix.cpp:930 #30 0x00000035caa6b10f in QEventDispatcherX11::processEvents (this=0x80e720, flags=...) at kernel/qeventdispatcher_x11.cpp:152 #31 0x00000035c717513f in QEventLoop::processEvents (this=this@entry=0x7fff30be7390, flags=...) at kernel/qeventloop.cpp:149 #32 0x00000035c71753c8 in QEventLoop::exec (this=0x7fff30be7390, flags=...) at kernel/qeventloop.cpp:204 #33 0x00000035c717a1b8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187 #34 0x00000035dc65f4ee in kdemain () from /lib64/libkdeinit4_kwin.so #35 0x00000035bc021735 in __libc_start_main (main=0x4008c0, argc=3, ubp_av=0x7fff30be7808, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff30be77f8) at libc-start.c:226 #36 0x00000000004008f1 in _start () Possible duplicates by query: bug 299575. Reported using DrKonqi
The backtrace contains hardly usable info (except that ::setProperty() is apparently called on a NULL pointer) Please have a look here, install required packages, trigger the crash and update the but with the full backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#How_to_create_useful_crash_reports
Thomas, Thank you for the quick answer. However I already installed all the debug tools described by the link you send me. If you wish I can let it "Crash" again but I doubt it will generate more info. Kind regards, Desmond Swaab 2012/7/12 Thomas Lübking <thomas.luebking@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=303411 > > Thomas Lübking <thomas.luebking@gmail.com> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > Resolution|--- |BACKTRACE > > --- Comment #1 from Thomas Lübking <thomas.luebking@gmail.com> --- > The backtrace contains hardly usable info (except that ::setProperty() is > apparently called on a NULL pointer) > > Please have a look here, install required packages, trigger the crash and > update the but with the full backtrace: > > http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#How_to_create_useful_crash_reports > > -- > You are receiving this mail because: > You reported the bug.
It's not about tools but packages - you need the unstripped version of the libraries. Looking at their page, it doesn't mention kde-workspace-debuginfo (or similar) which you'll need for sure. Without a better backtrace one can only guess around wildly. The QAbstractScrollArea will be either the scene (disable compositing) or the decoration (do you use Aurorae resp. some theme for it?) Does the crash only occur on logging in and kwin starts up "normally" afterwards or does it fail to start ever?
I will give it another try to see if I can get some more debug info. The crash only occurs on logging in but kwin never starts afterwards (actually it keeps on crashing). I don't use any special themes (I can't really install anything with my Xwindow right now). 2012/7/12 Thomas Lübking <thomas.luebking@gmail.com> > https://bugs.kde.org/show_bug.cgi?id=303411 > > --- Comment #3 from Thomas Lübking <thomas.luebking@gmail.com> --- > It's not about tools but packages - you need the unstripped version of the > libraries. > Looking at their page, it doesn't mention kde-workspace-debuginfo (or > similar) > which you'll need for sure. > > Without a better backtrace one can only guess around wildly. > The QAbstractScrollArea will be either the scene (disable compositing) or > the > decoration (do you use Aurorae resp. some theme for it?) > > Does the crash only occur on logging in and kwin starts up "normally" > afterwards or does it fail to start ever? > > -- > You are receiving this mail because: > You reported the bug. >
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!
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!