Bug 456163

Summary:	KWin error on resume from suspend after Lock screen error
Product:	[Plasma] plasmashell	Reporter:	Roman <nightcitysun>
Component:	general	Assignee:	Plasma Bugs List <plasma-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	crash	CC:	kde
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	5.24.5
Target Milestone:	1.0
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Roman 2022-06-30 10:31:39 UTC

Application: plasmashell (5.24.5)

Qt Version: 5.15.5
Frameworks Version: 5.95.0
Operating System: Linux 5.18.0-1-rt11-MANJARO x86_64
Windowing System: X11
Distribution: Manjaro Linux
DrKonqi: 5.24.5 [KCrashBackend]

-- Information about the crash:
- What I was doing when the application crashed:
-- resume from suspend - immediately got black screen with "Lock screen is broken" error
-- swiched to TTY (ctrl+al+F2) and unlocked session 2
-- returned back to TTY1 

- Unusual behavior I noticed:
-- system settings UI has orange circle marks for different menu items
-- "QDBusConnection: error: could not send signal to service" appears even after reinstalling qt and plasma packages

- Custom settings of the application:
current theme: "breath-light" (same issue on "breeze" theme). 
Reinstalling plasma5-themes-breath and sddm-breath-theme did not help.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma (plasmashell), signal: Aborted

[KCrash Handler]
#4  0x00007f509cc06117 in  () at /usr/lib/libc.so.6
#5  0x00007f509cc08920 in pthread_cond_wait () at /usr/lib/libc.so.6
#6  0x00007f509d0ab7d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5
#7  0x00007f509eafd950 in  () at /usr/lib/libQt5Quick.so.5
#8  0x00007f509eafe6c1 in  () at /usr/lib/libQt5Quick.so.5
#9  0x00007f509d637707 in QWindow::event(QEvent*) () at /usr/lib/libQt5Gui.so.5
#10 0x00007f509dea2abc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#11 0x00007f509d24cf38 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#12 0x00007f509d62a4d4 in QGuiApplicationPrivate::processExposeEvent(QWindowSystemInterfacePrivate::ExposeEvent*) () at /usr/lib/libQt5Gui.so.5
#13 0x00007f509d60c9c5 in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#14 0x00007f5097c81ce0 in  () at /usr/lib/libQt5XcbQpa.so.5
#15 0x00007f509b624c6b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#16 0x00007f509b67b001 in  () at /usr/lib/libglib-2.0.so.0
#17 0x00007f509b622392 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#18 0x00007f509d29764c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#19 0x00007f509d2456ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#20 0x00007f509d2501e9 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#21 0x000055def0df1dc2 in  ()
#22 0x00007f509cba6290 in  () at /usr/lib/libc.so.6
#23 0x00007f509cba634a in __libc_start_main () at /usr/lib/libc.so.6
#24 0x000055def0df2195 in  ()
[Inferior 1 (process 1227) detached]

Possible duplicates by query: bug 456151, bug 456062, bug 455869, bug 455543, bug 455505.

Reported using DrKonqi

Comment 1 David Edmundson 2022-06-30 12:04:11 UTC

>[KCrash Handler]
#4  0x00007f509cc06117 in  () at /usr/lib/libc.so.6
#5  0x00007f509cc08920 in pthread_cond_wait () at /usr/lib/libc.so.6
#6  0x00007f509d0ab7d4 in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /usr/lib/libQt5Core.so.5

That doesn't sound like  crash, we're just sitting about idling for events

>signal: Aborted

This isn't a crash, something external is sending us an abort signal. 
Last time I encountered this it was a user's script doing it.

Comment 2 Bug Janitor Service 2022-07-15 04:37:05 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 3 Bug Janitor Service 2022-07-30 04:35:51 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!