Bug 275555

Summary: whenever the system wants to lock the screen the lockscreen crashes
Product: [Unmaintained] kdelibs Reporter: Christoph Obexer <cobexer>
Component: knotifyAssignee: Olivier Goffart <ogoffart>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Christoph Obexer 2011-06-13 16:00:49 UTC 
Application: kscreenlocker (2.0)
KDE Platform Version: 4.6.00 (4.6.0) "release 6"
Qt Version: 4.7.1
Operating System: Linux 2.6.37.6-0.5-default i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:

screensaver: asciiquarium if that matters

whenever the system wants to lock the screen the lockscreen crashes.

The crash can be reproduced every time.

-- Backtrace:
Application: KDE-Bildschirmsperre (kscreenlocker), signal: Segmentation fault
[KCrash Handler]
#7  0xb7567023 in KNotificationManager::KNotificationManager (this=0x8188df8) at /usr/src/debug/kdelibs-4.6.0/kdeui/notifications/knotificationmanager.cpp:65
#8  0xb75673bf in operator-> () at /usr/src/debug/kdelibs-4.6.0/kdeui/notifications/knotificationmanager.cpp:46
#9  operator KNotificationManager* () at /usr/src/debug/kdelibs-4.6.0/kdeui/notifications/knotificationmanager.cpp:46
#10 KNotificationManager::self () at /usr/src/debug/kdelibs-4.6.0/kdeui/notifications/knotificationmanager.cpp:47
#11 0xb75f8900 in KNotification::sendEvent (this=0x81892d0) at /usr/src/debug/kdelibs-4.6.0/kdeui/notifications/knotification.cpp:372
#12 0xb75f928c in KNotification::qt_metacall (this=0x81892d0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x81895a0) at /usr/src/debug/kdelibs-4.6.0/build/kdeui/knotification.moc:109
#13 0xb6da08cd in QMetaObject::metacall (object=0x81892d0, cl=QMetaObject::InvokeMetaMethod, idx=17, argv=0x81895a0) at kernel/qmetaobject.cpp:237
#14 0xb6dab3a5 in QMetaCallEvent::placeMetaCall (this=0x8188e08, object=0x81892d0) at kernel/qobject.cpp:534
#15 0xb6daf5af in QObject::event (this=0x81892d0, e=0x8188e08) at kernel/qobject.cpp:1211
#16 0xb62a7414 in QApplicationPrivate::notify_helper (this=0x808fee8, receiver=0x81892d0, e=0x8188e08) at kernel/qapplication.cpp:4445
#17 0xb62b00c7 in QApplication::notify (this=0xbff47cf0, receiver=0x81892d0, e=0x8188e08) at kernel/qapplication.cpp:3845
#18 0xb74f31f1 in KApplication::notify (this=0xbff47cf0, receiver=0x81892d0, event=0x8188e08) at /usr/src/debug/kdelibs-4.6.0/kdeui/kernel/kapplication.cpp:311
#19 0xb6d99fde in QCoreApplication::notifyInternal (this=0xbff47cf0, receiver=0x81892d0, event=0x8188e08) at kernel/qcoreapplication.cpp:732
#20 0xb6d9dd6c in sendEvent (receiver=0x0, event_type=0, data=0x80782a0) at kernel/qcoreapplication.h:215
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x80782a0) at kernel/qcoreapplication.cpp:1373
#22 0xb6d9debc in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#23 0xb6dc85e4 in sendPostedEvents (s=0x8092368) at kernel/qcoreapplication.h:220
#24 postEventSourceDispatch (s=0x8092368) at kernel/qeventdispatcher_glib.cpp:277
#25 0xb5a62509 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0xb5a62d10 in ?? () from /lib/libglib-2.0.so.0
#27 0xb5a62fce in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0xb6dc876b in QEventDispatcherGlib::processEvents (this=0x807bcb8, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#29 0xb635d55a in QGuiEventDispatcherGlib::processEvents (this=0x807bcb8, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0xb6d992bd in QEventLoop::processEvents (this=0xbff47b34, flags=...) at kernel/qeventloop.cpp:149
#31 0xb6d994e9 in QEventLoop::exec (this=0xbff47b34, flags=...) at kernel/qeventloop.cpp:201
#32 0xb6d9df90 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#33 0xb62a5104 in QApplication::exec () at kernel/qapplication.cpp:3719
#34 0x080679a2 in main (argc=) at /usr/src/debug/kdebase-workspace-4.6.0/krunner/lock/main.cc:198

Reported using DrKonqi
Comment 1 Christoph Obexer 2011-07-28 19:09:13 UTC 
a few more things to consider:
 * there were a number of asciiquarium processes already running.
 * other KDE applications crashed identically (like Choqok)
 * this happened after a lot of suspend resume cycles
 * sometimes after a resume it seems like processes loading a random library crash (like some gtk apps, some kde apps, everything that uses libc,...)

this might well have been caused by something that can not be fixed in kde...
Comment 2 Andrew Crouthamel 2018-10-29 22:39:58 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:33:12 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
mark the bug 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 4 Bug Janitor Service 2018-11-29 04:51:50 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!