[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #12 from Nate Graham --- *** This bug has been marked as a duplicate of bug 461068 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 Nate Graham changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |DUPLICATE --- Comment #11 from Nate Graham --- *** This bug has been marked as a duplicate of bug 462646 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 Nate Graham changed: What|Removed |Added Component|common |OSD -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 christian.rohm...@gmx.de changed: What|Removed |Added Resolution|WORKSFORME |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #10 from christian.rohm...@gmx.de --- I observe the same issue whenever I klick onto any option of the OSD. I open it via Fn+F7 and even if I click "leave unchanged" or when pressing Esc this appears in the dmesg: --- cut --- Dec 11 18:24:38 thinkpadt14s kernel: kscreen_osd_ser[23165]: segfault at 55007669348d ip 7f4596d426ef sp 7fff7270b2a8 error 4 in libQt5Gui.so.5.15.7[7f4596cf7000+45d000] likely on CPU 2 (core 1, socket 0 ) Dec 11 18:24:38 thinkpadt14s kernel: Code: 8b 44 24 68 eb d5 90 0f 1f 40 00 f3 0f 1e fa 48 8b 47 08 89 70 58 c3 0f 1f 40 00 f3 0f 1e fa 48 8b 7f 08 40 0f b6 f6 48 8b 07 60 20 66 66 2e 0f 1f 84 00 00 00 00 0 0 0f 1f 00 f3 0f 1e fa 48 --- cut --- I can solidly reproduce the issue. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #9 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #8 from Bug Janitor Service --- 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! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #7 from tho...@zell-mbc.com --- New crash just now: System was about to show a notification, it got as far as drawing a black square in the upper right hand corner where notifications would appear, this time Plasma froze before it was able to display the text. I immediately switched over to tty2. The log below shows 3 minutes up to the creation of tty2 / me logging on. When on the console I tried "sudo systemctl restart display-manager" which restarts Plasma but things get stuck at the logon screen. Next attempt was to kill Xorg: ps -ef | grep ssdm kill -9 /usr/lib/Xorg Restarts Plasma (and all applications :-( ) Back in business Journalctl: … Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: reauthenticate: trying to refresh Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Starting OAuth2 authentication Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to retrieve authentication data Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Failed to process EWS request - HTTP code 401 Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews: requestAuthFailed - going offline Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: org.kde.pim.ews.client: Authentication succeeded Nov 03 15:50:40 hermes akonadi_ews_resource[2614]: Please register the custom scheme 'urn' via QWebEngineUrlScheme::registerScheme() before installing the custom scheme handler. Nov 03 15:50:41 hermes akonadiserver[1501]: org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_5 (0x558e98a86820) Nov 03 15:50:41 hermes akonadiserver[1501]: org.kde.pim.akonadiserver: Error while handling command FetchCollections on connection akonadi_ews_resource_5 (0x558e98a86820) Nov 03 15:50:45 hermes kwin_x11[1080]: kwin_core: XCB error: 152 (BadDamage), sequence: 20035, resource id: 15423924, major code: 143 (DAMAGE), minor code: 3 (Subtract) Nov 03 15:50:57 hermes akonadi_imap_resource[1614]: org.kde.pim.kimap: Connection to server lost QAbstractSocket::ConnectionRefusedError Nov 03 15:50:57 hermes akonadi_imap_resource[1614]: org.kde.pim.kimap: Connection to server lost QAbstractSocket::C
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #6 from tho...@zell-mbc.com --- (In reply to Nate Graham from comment #5) > > Okt 23 21:39:55 hermes kglobalaccel5[1136]: The X11 connection broke (error > > 1). Did the X11 server die? > If the X11 server died, it's going to take down everything else with it. Is > there an x11 crash? I was specifically looking for that but couldn't find anything mentioning X11 shortly before things went south. Had another crash yesterday, same story, nothing obvious in the log. But meanwhile I figured out that restarting Plasma instead of rebooting is sufficient. Still use all of my open applications though. The OS is fully updated so none of the updates which arrived between opening the bug and yesterday seem to have fixed things. I'll keep checking and will update this thread as soon as I find something to hold on. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #5 from Nate Graham --- > Okt 23 21:39:55 hermes kglobalaccel5[1136]: The X11 connection broke (error > 1). Did the X11 server die? If the X11 server died, it's going to take down everything else with it. Is there an x11 crash? -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 christian.rohm...@gmx.de changed: What|Removed |Added CC||christian.rohm...@gmx.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #4 from tho...@zell-mbc.com --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! I had two more crashes over the weekend, but unfortunately none led to a coredump. What I can find this time is lots of processes which die because something is missing. Going up the log the below is the first crash entry and all the others may fail because of sddm to go away: Okt 23 21:39:55 hermes sddm[746]: Authentication error: "Process crashed" Okt 23 21:39:55 hermes sddm[746]: Auth: sddm-helper crashed (exit code 15) Okt 23 21:39:55 hermes sddm[746]: Authentication error: "Process crashed" Okt 23 21:39:55 hermes sddm[746]: Auth: sddm-helper exited with 15 Okt 23 21:39:55 hermes sddm[746]: Display server stopping... Okt 23 21:39:55 hermes systemd[1]: Stopped target Graphical Interface. Okt 23 21:39:55 hermes kglobalaccel5[1136]: The X11 connection broke (error 1). Did the X11 server die? Next to die is akonadi: Okt 23 21:39:55 hermes akonadiserver[1516]: org.kde.pim.akonadiserver: Control process died, committing suicide! Plasma is next: Okt 23 21:39:55 hermes systemd[871]: plasma-gmenudbusmenuproxy.service: Main process exited, code=exited, status=1/FAILURE Okt 23 21:39:55 hermes systemd[871]: plasma-gmenudbusmenuproxy.service: Failed with result 'exit-code'. Okt 23 21:39:55 hermes systemd-coredump[37353]: Failed to connect to coredump service: Connection refused And lots more… -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 --- Comment #3 from tho...@zell-mbc.com --- (In reply to Nate Graham from comment #1) > If something crashed, we need a backtrace of it so we can figure out what's > going on. See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports. > > Can you please attach one? Thanks! Happy to, I read the note re. providing a crash report but was a bit hesitant to read up and install additional software not knowing if someone is going to pick this up. Anyway, I just ran coredumpctl gdb, but it looks like there's been another core dump by kioslave5, unrelated I guess, which means the the one we need is not accessible any longer. I guess I will have to wait for the crash to re-occurre. I will update this post asap, given previous experience this shouldn't take longer than 1 or 2 days before this happens again. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 Sebastian changed: What|Removed |Added CC||bugreports.nm...@aleeas.com --- Comment #2 from Sebastian --- Same happing to my kde neon (Plasma 5.26.0) installation. >From crash process viewer: PID: 4084 (kscreen_osd_ser) UID: 1000 (sebastian) GID: 1000 (sebastian) Signal: 11 (SEGV) Timestamp: Fri 2022-10-21 20:05:42 CEST (4min 9s ago) Command Line: /usr/lib/x86_64-linux-gnu/libexec/kscreen_osd_service Executable: /usr/lib/x86_64-linux-gnu/libexec/kscreen_osd_service Control Group: /user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kscreen-osd.service Unit: user@1000.service User Unit: plasma-kscreen-osd.service Slice: user-1000.slice Owner UID: 1000 (sebastian) Boot ID: a1b9e0ad37ed4583a381bec2fcc49c02 Machine ID: be93237f58a7432c8924ca44369ab72b Hostname: sebzbook Storage: /var/lib/systemd/coredump/core.kscreen_osd_ser.1000.a1b9e0ad37ed4583a381bec2fcc49c02.4084.1666375542.lz4 Message: Process 4084 (kscreen_osd_ser) of user 1000 dumped core. Stack trace of thread 4084: #0 0x7fdf7b90685f _ZN7QWindow10setVisibleEb (libQt5Gui.so.5 + 0x14685f) #1 0x7fdf7b5532f2 n/a (libQt5Core.so.5 + 0x2ec2f2) #2 0x7fdf7b54c643 _ZN7QObject9destroyedEPS_ (libQt5Core.so.5 + 0x2e5643) #3 0x7fdf7b551500 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2ea500) #4 0x7fdf7c9c2e6d _ZN7KScreen6OutputD0Ev (libKF5Screen.so.7 + 0x4ce6d) #5 0x55f97570520e n/a (kscreen_osd_service + 0xe20e) #6 0x55f97570524d n/a (kscreen_osd_service + 0xe24d) #7 0x55f9756fd6f7 n/a (kscreen_osd_service + 0x66f7) #8 0x7fdf7b5532f2 n/a (libQt5Core.so.5 + 0x2ec2f2) #9 0x7fdf7b557e8e _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2f0e8e) #10 0x7fdf7b549c25 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2c25) #11 0x7fdf7b51c03a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b503a) #12 0x7fdf7b575ed0 _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x30eed0) #13 0x7fdf7b5767bc n/a (libQt5Core.so.5 + 0x30f7bc) #14 0x7fdf7970017d g_main_context_dispatch (libglib-2.0.so.0 + 0x5217d) #15 0x7fdf79700400 n/a (libglib-2.0.so.0 + 0x52400) #16 0x7fdf797004a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #17 0x7fdf7b576b82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #18 0x7fdf7b51ab3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #19 0x7fdf7b522ce4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bbce4) #20 0x55f9756fd0b7 n/a (kscreen_osd_service + 0x60b7) #21 0x7fdf7aeb7083 __libc_start_main (libc.so.6 + 0x24083) #22 0x55f9756fd16e n/a (kscreen_osd_service + 0x616e) Stack trace of thread 4085: #0 0x7fdf7afa599f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fdf7970036e n/a (libglib-2.0.so.0 + 0x5236e) #2 0x7fdf797004a3 g_main_context_iteration (libglib-2.0.so.0 + 0x524a3) #3 0x7fdf7b576b82 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30fb82) #4 0x7fdf7b51ab3b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b3b3b) #5 0x7fdf7b334342 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcd342) #6 0x7fdf7c8e0f4b n/a (libQt5DBus.so.5 + 0x18f4b) #7 0x7fdf7b335543 n/a (libQt5Core.so.5 + 0xce543) #8 0x7fdf7a378609 start_thread (libpthread.so.0 + 0x8609) #9 0x7fdf7afb2133 __clone (libc.so.6 + 0x11f133) Stack trace of thread 4086: #0 0x7fdf7afa599f __GI___poll (libc.so.6 + 0x11299f) #1 0x7fdf7ad35c1a n/a (libxcb.so.1 + 0xbc1a) #2 0x7fdf7ad3790a xcb_wait_for_event (libxcb.so.1 + 0xd90a) #3 0x7fdf768e7e18 n/a (libQt5XcbQpa.so.5 + 0x78e18) #4 0x7fdf7b335543 n/a (libQt5Core.so.5 + 0xce543) #5 0x7fdf7a378609 start_thread (libpthread.so.0 + 0x8609) #6 0x7fdf7afb2133 __clone (libc.so.6 + 0x11f133) Stack trace of thread 4089: #0
[KScreen] [Bug 460798] systemd-coredump kscreen_osd_ser ever since upgrading to v26.0
https://bugs.kde.org/show_bug.cgi?id=460798 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||n...@kde.org Resolution|--- |BACKTRACE --- Comment #1 from Nate Graham --- If something crashed, we need a backtrace of it so we can figure out what's going on. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports. Can you please attach one? Thanks! -- You are receiving this mail because: You are watching all bug changes.
