Bug 223325 - Kscreenlocker crash on bad password
Summary: Kscreenlocker crash on bad password
Status: RESOLVED DUPLICATE of bug 217882
Alias: None
Product: kscreensaver
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-18 20:23 UTC by Michal Vyskocil
Modified: 2010-02-12 09:29 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Vyskocil 2010-01-18 20:23:53 UTC
Application: kscreenlocker (2.0)
KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1)) "release 2"
Qt Version: 4.6.1
Operating System: Linux 2.6.27.37-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"

-- Information about the crash:
Kscreenlocker crashed after insert a bad (incomplete) password. This crash also unlock the KDE session!

 -- Backtrace:
Application: KDE zámek obrazovky (kscreenlocker), signal: Segmentation fault
[KCrash Handler]
#6  QCoreApplication::postEvent (receiver=0x819b488, event=0x82235d0, priority=0) at kernel/qcoreapplication.cpp:1105
#7  0xb6db66ec in QCoreApplication::postEvent (receiver=0x819b488, event=0x82235d0) at kernel/qcoreapplication.cpp:1066
#8  0xb6dc6937 in QObject::deleteLater (this=0x819b488) at kernel/qobject.cpp:2150
#9  0x0805ef69 in PasswordDlg::reapVerify (this=0xbfa16eb0) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/lockdlg.cc:319
#10 0x0805f135 in PasswordDlg::handleVerify (this=0xbfa16eb0) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/lockdlg.cc:389
#11 0x0805f388 in PasswordDlg::qt_metacall (this=0xbfa16eb0, _c=QMetaObject::InvokeMetaMethod, _id=135902344, _a=0xbfa1664c)
    at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/build/krunner/lock/lockdlg.moc:86
#12 0xb6dbbc45 in QMetaObject::metacall (object=0x819b488, cl=QMetaObject::InvokeMetaMethod, idx=78, argv=0xbfa1664c) at kernel/qmetaobject.cpp:237
#13 0xb6dcaa79 in QMetaObject::activate (sender=0x82e0140, m=0xb6ed2550, local_signal_index=0, argv=0xbfa1664c) at kernel/qobject.cpp:3267
#14 0xb6e1de23 in QSocketNotifier::activated (this=0x82e0140, _t1=17) at .moc/release-shared/moc_qsocketnotifier.cpp:89
#15 0xb6dd1bb7 in QSocketNotifier::event (this=0x82e0140, e=0xbfa16b50) at kernel/qsocketnotifier.cpp:317
#16 0xb62ab68c in QApplicationPrivate::notify_helper (this=0x808a778, receiver=0x82e0140, e=0xbfa16b50) at kernel/qapplication.cpp:4297
#17 0xb62b2e4f in QApplication::notify (this=0xbfa179a8, receiver=0x82e0140, e=0xbfa16b50) at kernel/qapplication.cpp:3701
#18 0xb75bc37d in KApplication::notify (this=0xbfa179a8, receiver=0x82e0140, event=0xbfa16b50) at /usr/src/debug/kdelibs-4.3.87svn1070744/kdeui/kernel/kapplication.cpp:302
#19 0xb6db677b in QCoreApplication::notifyInternal (this=0xbfa179a8, receiver=0x82e0140, event=0xbfa16b50) at kernel/qcoreapplication.cpp:704
#20 0xb6de35fa in socketNotifierSourceDispatch (source=0x808d738) at kernel/qcoreapplication.h:215
#21 0xb5b429c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb5b46083 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb5b46241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb6de3231 in QEventDispatcherGlib::processEvents (this=0x808a738, flags={i = -1079939928}) at kernel/qeventdispatcher_glib.cpp:412
#25 0xb6369805 in QGuiEventDispatcherGlib::processEvents (this=0x808a738, flags={i = -1079939880}) at kernel/qguieventdispatcher_glib.cpp:204
#26 0xb6db4d8a in QEventLoop::processEvents (this=0xbfa16d4c, flags={i = -1079939816}) at kernel/qeventloop.cpp:149
#27 0xb6db51d2 in QEventLoop::exec (this=0xbfa16d4c, flags={i = -1079939756}) at kernel/qeventloop.cpp:201
#28 0xb67c7233 in QDialog::exec (this=0xbfa16eb0) at dialogs/qdialog.cpp:530
#29 0x08054a7d in LockProcess::execDialog (this=0xbfa178cc, dlg=0xbfa16eb0) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/lockprocess.cc:1239
#30 0x0805b00d in LockProcess::checkPass (this=0xbfa178cc) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/lockprocess.cc:1127
#31 0x0805bcbd in LockProcess::x11Event (this=0xbfa178cc, event=0xbfa175ec) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/lockprocess.cc:1309
#32 0xb75bb699 in KApplication::x11EventFilter (this=0xbfa179a8, _event=0xbfa175ec) at /usr/src/debug/kdelibs-4.3.87svn1070744/kdeui/kernel/kapplication.cpp:903
#33 0xb632bd3e in qt_x11EventFilter (ev=0xbfa175ec) at kernel/qapplication_x11.cpp:399
#34 0xb633c868 in QApplication::x11ProcessEvent (this=0xbfa179a8, event=0xbfa175ec) at kernel/qapplication_x11.cpp:3231
#35 0xb6369cf2 in x11EventSourceDispatch (s=0x808d828, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#36 0xb5b429c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#37 0xb5b46083 in ?? () from /usr/lib/libglib-2.0.so.0
#38 0xb5b46241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#39 0xb6de3231 in QEventDispatcherGlib::processEvents (this=0x808a738, flags={i = -1079937112}) at kernel/qeventdispatcher_glib.cpp:412
#40 0xb6369805 in QGuiEventDispatcherGlib::processEvents (this=0x808a738, flags={i = -1079937064}) at kernel/qguieventdispatcher_glib.cpp:204
#41 0xb6db4d8a in QEventLoop::processEvents (this=0xbfa17850, flags={i = -1079937000}) at kernel/qeventloop.cpp:149
#42 0xb6db51d2 in QEventLoop::exec (this=0xbfa17850, flags={i = -1079936936}) at kernel/qeventloop.cpp:201
#43 0xb6db79c9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#44 0xb62ab737 in QApplication::exec () at kernel/qapplication.cpp:3576
#45 0x08063f96 in main (argc=2, argv=0xbfa17b24) at /usr/src/debug/kdebase-workspace-4.3.87svn1070744/krunner/lock/main.cc:173

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-18 21:55:10 UTC
This looks related to bug 217882. - Did you resumed a suspended session ?
Thanks
Comment 2 Michal Vyskocil 2010-01-25 19:56:12 UTC
Yes I resumed from suspend to RAM.
Comment 3 Dario Andres 2010-01-25 22:39:40 UTC
Thanks

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