Bug 466036 - kded5 crash after resume from blank
Summary: kded5 crash after resume from blank
Status: RESOLVED DUPLICATE of bug 464590
Alias: None
Product: KScreen
Classification: Plasma
Component: common (show other bugs)
Version: 5.27.0
Platform: Other Linux
: NOR crash
Target Milestone: ---
Assignee: kscreen-bugs-null@kde.org
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2023-02-18 21:58 UTC by rick
Modified: 2023-02-22 00:05 UTC (History)
5 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 rick 2023-02-18 21:58:22 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***
kded5 crash after resume from blank

```
Application: kded5 (kded5), signal: Segmentation fault

[KCrash Handler]
#4  0x00007f49d62ad270 in KScreen::Output::id() const () from /lib64/libKF5Screen.so.8
#5  0x00007f49d62a01f8 in KScreen::Config::setOutputPriority(QSharedPointer<KScreen::Output> const&, unsigned int) () from /lib64/libKF5Screen.so.8
#6  0x00007f49d62a9ca2 in KScreen::SetConfigOperation::start() () from /lib64/libKF5Screen.so.8
#7  0x00007f4a11907d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#8  0x00007f4a127a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#9  0x00007f4a118dc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007f4a118df181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#11 0x00007f4a11934413 in ?? () from /lib64/libQt5Core.so.5
#12 0x00007f4a1051ba90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#13 0x00007f4a1051be48 in ?? () from /lib64/libglib-2.0.so.0
#14 0x00007f4a1051bedc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#15 0x00007f4a11933c16 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#16 0x00007f4a118dac5b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#17 0x00007f4a118e2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#18 0x000055f59658b976 in ?? ()
#19 0x00007f4a1102caf0 in __libc_start_call_main () from /lib64/libc.so.6
#20 0x00007f4a1102cbb9 in __libc_start_main_impl () from /lib64/libc.so.6
#21 0x000055f59658bb75 in ?? ()
[Inferior 1 (process 2368) detached]
```

STEPS TO REPRODUCE
1. settings -> power management -> display off after 1 minute
2. resume display after the screen black
3. get kded5 crash error, tray icon not working and maybe others

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: archlinux/opensuse tumbleweed
(available in About System)
KDE Plasma Version:plasma 5.27.0 
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8

ADDITIONAL INFORMATION
Comment 1 coherence 2023-02-20 17:36:22 UTC
I have encountered the same issue after updating to 5.27. The steps to reproduce are also the same.

Backtrace:
#0  0x00007fc0700a08ec in  () at /usr/lib/libc.so.6
#1  0x00007fc070051ea8 in raise () at /usr/lib/libc.so.6
#2  0x00007fc071ce637c in KCrash::defaultCrashHandler(int) () at /usr/lib/libKF5Crash.so.5
#3  0x00007fc070051f50 in <signal handler called> () at /usr/lib/libc.so.6
#4  0x00007fc05e36bcf4 in KScreen::Output::id() const () at /usr/lib/libKF5Screen.so.8
#5  0x00007fc05e35e71d in KScreen::Config::setOutputPriority(QSharedPointer<KScreen::Output> const&, unsigned int) () at /usr/lib/libKF5Screen.so.8
#6  0x00007fc05e36826f in KScreen::SetConfigOperation::start() () at /usr/lib/libKF5Screen.so.8
#7  0x00007fc0708b1bb0 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#8  0x00007fc071778b5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#9  0x00007fc07088df48 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#10 0x00007fc07088ea53 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#11 0x00007fc0708d4e88 in  () at /usr/lib/libQt5Core.so.5
#12 0x00007fc06f51682b in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#13 0x00007fc06f56dcc9 in  () at /usr/lib/libglib-2.0.so.0
#14 0x00007fc06f5150e2 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#15 0x00007fc0708d8c6c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#16 0x00007fc0708866ec in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#17 0x00007fc070891219 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#18 0x0000559c1e9f2040 in  ()
#19 0x00007fc07003c790 in  () at /usr/lib/libc.so.6
#20 0x00007fc07003c84a in __libc_start_main () at /usr/lib/libc.so.6
#21 0x0000559c1e9f20c5 in  ()
Comment 2 grayich 2023-02-21 06:27:21 UTC
The same thing after updating to 5.27 

additionally, there is still such:

#> kscreen-doctor -o
Output: 82 HDMI-A-0 enabled connected priority 1 HDMI Modes: 87:1920x1080@60*! 88:1920x1080@75 89:1920x1080@50 90:1920x1080@60 91:1680x1050@60 92:1280x1024@75 93:1280x1024@60 94:1440x900@60 95:1280x960@60 96:1280x800@60 97:1280x720@60 98:1280x720@50 99:1280x720@60 100:1024x768@75 101:1024x768@70 102:1024x768@60 103:832x624@75 104:800x600@72 105:800x600@75 106:800x600@60 107:800x600@56 108:720x576@50 109:720x480@60 110:720x480@60 111:640x480@75 112:640x480@73 113:640x480@67 114:640x480@60 115:640x480@60 116:720x400@70 Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 83 DVI-D-0 disabled disconnected priority 0 DVI Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 84 DisplayPort-0 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown
Output: 85 DisplayPort-1 disabled disconnected priority 0 DisplayPort Modes: Geometry: 0,0 0x0 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: unknown

#> kscreen-doctor output.HDMI-A-0.disable
Disabling output 82
zsh: segmentation fault (core dumped)  kscreen-doctor output.HDMI-A-0.disable
Comment 3 Andrew Gunnerson 2023-02-21 22:30:12 UTC
I've having the same issue as well after the Plasma 5.27.0 update. When this occurs, the screen also stays blank until I switch to another VT and then back.

Software info:

* Distro: Fedora 37
* Session type: X11
* kernel: 6.1.11-200.fc37.x86_64
* kf5: 5.103.0-1.fc37.x86_64
* plasma: 5.27.0-2.fc37.x86_64
* qt5: 5.15.8-5.fc37.x86_64
* Nvidia proprietary drivers: 525.89.02-1.fc37.x86_64

Backtrace with debuginfo:

Core was generated by `/usr/bin/kded5'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  KScreen::Output::id (this=0x0) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp:189
Downloading 0.00 MB source file /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp
189         return d->id;
[Current thread is 1 (Thread 0x7f3ae576c840 (LWP 593267))]
(gdb) bt
#0  KScreen::Output::id() const (this=0x0) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/output.cpp:189
#1  0x00007f3abc09110c in KScreen::Config::setOutputPriority(QSharedPointer<KScreen::Output> const&, unsigned int) (this=0x558343e4d3f0, output=..., priority=1) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:301
#2  0x00007f3abc09aa5e in KScreen::SetConfigOperationPrivate::fixPrimaryOutput() (this=<optimized out>) at /usr/include/qt5/QtCore/qsharedpointer_impl.h:301
#3  KScreen::SetConfigOperation::start() (this=0x558343ae4550) at /usr/src/debug/libkscreen-qt5-5.27.0-1.fc37.x86_64/src/setconfigoperation.cpp:114
#4  0x00007f3ae54c8134 in QObject::event(QEvent*) (this=0x558343ae4550, e=0x558343e21070) at kernel/qobject.cpp:1347
#5  0x00007f3ae63aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=<optimized out>, receiver=0x558343ae4550, e=0x558343e21070) at kernel/qapplication.cpp:3640
#6  0x00007f3ae549d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x558343ae4550, event=0x558343e21070) at kernel/qcoreapplication.cpp:1064
#7  0x00007f3ae54a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x5583433de340) at kernel/qcoreapplication.cpp:1821
#8  0x00007f3ae54eeb07 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x5583434bfe20) at kernel/qeventdispatcher_glib.cpp:277
#9  0x00007f3ae4264cbf in g_main_dispatch (context=0x7f3acc005010) at ../glib/gmain.c:3444
#10 g_main_context_dispatch (context=0x7f3acc005010) at ../glib/gmain.c:4162
#11 0x00007f3ae42ba598 in g_main_context_iterate.constprop.0 (context=0x7f3acc005010, block=1, dispatch=1, self=<optimized out>) at ../glib/gmain.c:4238
#12 0x00007f3ae4261f40 in g_main_context_iteration (context=0x7f3acc005010, may_block=1) at ../glib/gmain.c:4303
#13 0x00007f3ae54ee5fa in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x5583434bf6e0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#14 0x00007f3ae549bf3a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fff5b65c820, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#15 0x00007f3ae54a4002 in QCoreApplication::exec() () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#16 0x00007f3ae595fad0 in QGuiApplication::exec() () at kernel/qguiapplication.cpp:1863
#17 0x00007f3ae63aecd9 in QApplication::exec() () at kernel/qapplication.cpp:2832
#18 0x000055834213d5ab in main(int, char**) (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/kf5-kded-5.103.0-1.fc37.x86_64/src/kded.cpp:785
Comment 4 Nate Graham 2023-02-22 00:05:54 UTC

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