Bug 360931 - crash if i lock screen ,again login enter password ,click unlock button , every time crash
Summary: crash if i lock screen ,again login enter password ,click unlock button , ev...
Status: RESOLVED FIXED
Alias: None
Product: kscreenlocker
Classification: Plasma
Component: breeze-theme (show other bugs)
Version: 5.5.5
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-24 07:27 UTC by wangwei
Modified: 2020-01-12 23:26 UTC (History)
5 users (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 wangwei 2016-03-24 07:27:40 UTC
crash if i lock screen ,again login  enter password ,click unlock button , every  time crash

Reproducible: Always

Steps to Reproduce:
1.lock screen
2.enter password  login , again again ,
3.so...

Actual Results:  
crash

Expected Results:  
open desktop  kde run no bug
Comment 1 foss 2017-03-07 15:28:58 UTC
This still happens on Wayland though, if it makes a difference.
- Locking the screen and type correct password results in black screen, need to kill the session from another tty and startplasmacompositor again.
- Trying to logout either from app menu or with Ctrl+Alt+Del has no effect. Krash handler opens with the info "We are sorry, ksmserver-logout-greeter closed unexpectedly \n You cannot report this error, because ksmserver-logout-greeter does not provide a bug reporting address"

[From Developer Information Tab, not helpfull I suppose. Archlinux and the missing debug symbols dilema.]
Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fdda45c8840 (LWP 14447))]

Thread 2 (Thread 0x7fdd8df8e700 (LWP 14448)):
#0  0x00007fdd9ff6148d in poll () from /usr/lib/libc.so.6
#1  0x00007fdd98b897a6 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007fdd98b898bc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#3  0x00007fdda088506b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#4  0x00007fdda082e89a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#5  0x00007fdda0650a73 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#6  0x00007fdda13d5125 in ?? () from /usr/lib/libQt5DBus.so.5
#7  0x00007fdda06556d8 in ?? () from /usr/lib/libQt5Core.so.5
#8  0x00007fdd9aaa9454 in start_thread () from /usr/lib/libpthread.so.0
#9  0x00007fdd9ff6a7df in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7fdda45c8840 (LWP 14447)):
[KCrash Handler]
#6  0x00007fdd9b331d49 in wl_map_insert_at () from /usr/lib/libwayland-client.so.0
#7  0x00007fdd9b32df1e in wl_proxy_destroy () from /usr/lib/libwayland-client.so.0
#8  0x00007fdda3985175 in KWayland::Client::Registry::release() () from /usr/lib/libKF5WaylandClient.so.5
#9  0x00007fdda398519e in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#10 0x00007fdda3985279 in KWayland::Client::Registry::~Registry() () from /usr/lib/libKF5WaylandClient.so.5
#11 0x00007fdda085a411 in QObjectPrivate::deleteChildren() () from /usr/lib/libQt5Core.so.5
#12 0x00007fdda0863d6f in QObject::~QObject() () from /usr/lib/libQt5Core.so.5
#13 0x00007fdd84ed1393 in ?? () from /usr/lib/qt/plugins/kf5/org.kde.kwindowsystem.platforms/KF5WindowSystemKWaylandPlugin.so
#14 0x00007fdd9feb7990 in __run_exit_handlers () from /usr/lib/libc.so.6
#15 0x00007fdd9feb79ea in exit () from /usr/lib/libc.so.6
#16 0x00007fdd9fea2298 in __libc_start_main () from /usr/lib/libc.so.6
#17 0x0000000000405c4a in _start ()
Comment 2 Christoph Feck 2017-03-18 17:25:42 UTC
Comment #1 is bug 372597.
Comment 3 Alexander Mentyu 2018-07-19 09:39:22 UTC
Is the crash still reproducible?
Comment 4 wangwei 2018-07-19 09:57:55 UTC
多少年了,这个bug还活着。 系统删除了,无法复现

(In reply to Alexander Mentyu from comment #3)
> Is the crash still reproducible?
Comment 5 Nate Graham 2020-01-12 23:26:29 UTC
Not reproducible.