kded5 crashes
Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot and then icons from no KDE programs (like Telegram) disappears from the system tray. A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. Any ideas? Thanks in advance The last crash: 2022-12-06T13:25:45.729082+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132545.728952:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:45.729818+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132545.729669:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RED_8, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:45.731194+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132545.731029:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:45.803791+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132545.803610:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RED_8, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:45.803996+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132545.803903:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:50.847114+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132550.846702:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RED_8, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:25:50.847224+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132550.846811:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:26:05.302141+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132605.301276:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RED_8, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:26:05.303077+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132605.301531:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory 2022-12-06T13:26:22.128639+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 39487, resource id: 27263164, major code: 18 (ChangeProperty), minor code: 0 2022-12-06T13:26:22.321886+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 39750, resource id: 27263165, major code: 18 (ChangeProperty), minor code: 0 2022-12-06T13:26:54.800549+01:00 waterhole kwin_x11[1449]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 42442, resource id: 4194321, major code: 18 (ChangeProperty), minor code: 0 2022-12-06T13:27:20.532320+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132720.531753:ERROR:shared_image_factory.cc(575)] Could not find SharedImageBackingFactory with params: usage: DisplayRead|Scanout, format: YUV_420_BIPLANAR, share_between_threads: 0, gmb_type: platform 2022-12-06T13:27:20.535272+01:00 waterhole plasmashell[2298]: [2335:2335:1206/132720.531880:ERROR:shared_image_stub.cc(147)] SharedImageStub: Unable to create shared image 2022-12-06T13:27:21.810647+01:00 waterhole DiscoverNotifier[1717]: packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.64") 2022-12-06T13:27:22.924224+01:00 waterhole PackageKit: refresh-cache transaction /23315_ebeedecc from uid 1000 finished with success after 1057ms 2022-12-06T13:27:23.026302+01:00 waterhole kded5[1448]: apper.daemon: System is not ready, application should conserve resources 2022-12-06T13:27:23.029435+01:00 waterhole kded5[1448]: packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.39") 2022-12-06T13:27:23.035093+01:00 waterhole kded5[1448]: packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.39") 2022-12-06T13:27:23.223099+01:00 waterhole DiscoverNotifier[1717]: packagekitqt.transaction: Unknown Transaction property: "Sender" QVariant(QString, ":1.64") 2022-12-06T13:
Re: kded5 crashes
Il 06/12/22 13:45, Miguel A. Vallejo ha scritto: Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot I can confirm. -- Saluti, Luca Pedrielli
Re: kded5 crashes
I can also confirm. Best regards Volker Christian On 06.12.22 17:41, luca.pedrielli wrote: > [Sie erhalten nicht häufig E-Mails von ago...@gmail.com. Weitere > Informationen, warum dies wichtig ist, finden Sie unter > https://aka.ms/LearnAboutSenderIdentification ] > > Il 06/12/22 13:45, Miguel A. Vallejo ha scritto: >> Since a few days ago I've been experiencing problems with KDE in a >> fully upgraded Sid. >> >> The symptoms are always the same: kded5 crashes a few minutes after >> boot > > I can confirm. > > -- > Saluti, Luca Pedrielli >
Re: kded5 crashes
Le 06/12/2022 à 13:45, Miguel A. Vallejo a écrit : Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot and then icons from no KDE programs (like Telegram) disappears from the system tray. A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. Any ideas? Thanks in advance Hi, I am on Sid and I don't see this. I use Wayland, are all the affected users here still on X11?
Re: kded5 crashes
Il 06/12/22 20:30, tv.debian ha scritto: Le 06/12/2022 à 13:45, Miguel A. Vallejo a écrit : Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot and then icons from no KDE programs (like Telegram) disappears from the system tray. A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. Any ideas? Thanks in advance Hi, I am on Sid and I don't see this. I use Wayland, are all the affected users here still on X11? It is crashing in Wayland too. Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 924 (kded5) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Tue 2022-12-06 22:03:23 CET (2min 48s ago) Command Line: /usr/bin/kded5 Executable: /usr/bin/kded5 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kded.service Unit: user@1000.service User Unit: plasma-kded.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: b91cecf0c7f64f6abd137d6cfbe575ba Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.kded5.1000.b91cecf0c7f64f6abd137d6cfbe575ba.924.167036060300.zst (present) Size on Disk: 4.7M Message: Process 924 (kded5) of user 1000 dumped core. Module libudev.so.1 from deb systemd-252.2-1.amd64 Module libsystemd.so.0 from deb systemd-252.2-1.amd64 Stack trace of thread 924: #0 0x7fa444be6bb4 pthread_sigmask (libc.so.6 + 0x8fbb4) #1 0x7fa444b93179 sigprocmask (libc.so.6 + 0x3c179) #2 0x7fa445ce3eab _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4eab) #3 0x7fa445ce4bd9 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5bd9) #4 0x7fa444b92f90 n/a (libc.so.6 + 0x3bf90) #5 0x7fa424d77740 _ZNK10PackageKit11Transaction3tidEv (libpackagekitqt5.so.1 + 0x1a740) #6 0x7fa425233563 n/a (kded_apperd.so + 0xe563) #7 0x7fa425233b99 n/a (kded_apperd.so + 0xeb99) #8 0x7fa4448e8caf n/a (libQt5Core.so.5 + 0x2e8caf) #9 0x7fa424d6b095 _ZN10PackageKit6Daemon22transactionListChangedERK11QStringList (libpackagekitqt5.so.1 + 0xe095) #10 0x7fa4448e8cdc n/a (libQt5Core.so.5 + 0x2e8cdc) #11 0x7fa424d83b38 n/a (libpackagekitqt5.so.1 + 0x26b38) #12 0x7fa424d84d73 n/a (libpackagekitqt5.so.1 + 0x27d73) #13 0x7fa44552661b n/a (libQt5DBus.so.5 + 0x2361b) #14 0x7fa4448dd450 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd450) #15 0x7fa445762f5e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f5e) #16 0x7fa4448b1718 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1718) #17 0x7fa4448b46b1 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b46b1) #18 0x7fa444909dd3 n/a (libQt5Core.so.5 + 0x309dd3) #19 0x7fa44371f7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #20 0x7fa44371fa38 n/a (libglib-2.0.so.0 + 0x54a38) #21 0x7fa44371facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #22 0x7fa4449094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #23 0x7fa4448b019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #24 0x7fa4448b8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #25 0x55e42173c359 n/a (kded5 + 0x7359) #26 0x7fa444b7e18a n/a (libc.so.6 + 0x2718a) #27 0x7fa444b7e245 __libc_start_main (libc.so.6 + 0x27245) #28 0x55e42173c541 n/a (kded5 + 0x7541) Stack trace of thread 931: #0 0x7fa444bdcd36 n/a (libc.so.6 + 0x85d36) #1 0x7fa444bdf3f8 pthread_cond_wait (libc.so.6 + 0x883f8) #2 0x7fa4446d199b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd199b) #3 0x7fa440b2faef n/a (libQt5WaylandClient.so.5 + 0x7aaef) #4 0x7fa4446cbcd1 n/a (libQt5Core.so.5
Re: kded5 crashes
On Tuesday, 6 December 2022 13:45:40 CET Miguel A. Vallejo wrote: > Since a few days ago I've been experiencing problems with KDE in a > fully upgraded Sid. > > The symptoms are always the same: kded5 crashes a few minutes after > boot and then icons from no KDE programs (like Telegram) disappears > from the system tray. > > A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. > Any ideas? It looks like I'm not having those issues, but your report did prompt me to look in syslog ... and that looks like KDE's debug log?!? # tail -n30 /var/log/syslog 2022-12-07T01:44:35.502916+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: isCorrect : "debug" 2022-12-07T01:44:35.503214+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: result : true 2022-12-07T01:44:35.503469+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: isCorrect : "log" 2022-12-07T01:44:35.503814+01:00 prancing-pony plasmashell[9550]: kf.sonnet.clients.hunspell: result : true 2022-12-07T01:44:36.222321+01:00 prancing-pony kwin_x11[1152]: kwin_tabbox: == "Alt+Tab" or "Alt+Shift+Backtab" 2022-12-07T01:44:36.313043+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:36.581574+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:40.218135+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:41.013394+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.030635+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.063486+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.414862+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:43.511189+01:00 prancing-pony kglobalaccel5[15433]: org.kde.konsole: Undecodable sequence: CSI >4;m 2022-12-07T01:44:43.511966+01:00 prancing-pony kglobalaccel5[15433]: org.kde.konsole: Undecodable sequence: CSI >4;m 2022-12-07T01:44:43.605965+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:44.554500+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:46.121951+01:00 prancing-pony kernel: [75486.661010] rmi4_f12 rmi4-00.fn12: Failed to read object data. Code: -6. 2022-12-07T01:44:46.830757+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:47.562204+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:47.937241+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.066014+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.207457+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:48.955986+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:49.223484+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:49.510930+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:50.131426+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:50.195366+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.078386+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.250778+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event 2022-12-07T01:44:51.616006+01:00 prancing-pony kglobalaccel5[1181]: kf.globalaccel.kglobalacceld: Got XKeyRelease event I don't think that's supposed to happen? signature.asc Description: This is a digitally signed message part.
Re: kded5 crashes
On 2022-12-06, luca.pedrielli wrote: > #6 0x7fa425233563 n/a (kded_apperd.so + 0xe563) > #7 0x7fa425233b99 n/a (kded_apperd.so + 0xeb99) Can you try remove apper and see if that is the culprit ? /Sune
Re: kded5 crashes
Il 07/12/22 11:10, Sune Vuorela ha scritto: On 2022-12-06, luca.pedrielli wrote: #6 0x7fa425233563 n/a (kded_apperd.so + 0xe563) #7 0x7fa425233b99 n/a (kded_apperd.so + 0xeb99) Can you try remove apper and see if that is the culprit ? /Sune i removed apper and things seems to be better. waiting for confirmation from the other guys too. now only plasmashell crashes ;) -- Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 1019 (plasmashell) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Wed 2022-12-07 11:34:26 CET (3min 39s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: cafc24ad58f24c5489c9ffa748d8f32f Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.plasmashell.1000.cafc24ad58f24c5489c9ffa748d8f32f.1019.167040926600.zst (present) Size on Disk: 16.3M Message: Process 1019 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.2-2.amd64 Module libudev.so.1 from deb systemd-252.2-2.amd64 Stack trace of thread 1019: #0 0x7f488f6a9ccc n/a (libc.so.6 + 0x8accc) #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f4891a93be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) #13 0x7f4889964fff n/a (libqxcb-glx-integration.so + 0xafff) #14 0x7f48899621b7 n/a (libqxcb-glx-integration.so + 0x81b7) #15 0x7f488ff8262d _ZN14QOpenGLContext6createEv (libQt5Gui.so.5 + 0x18262d) #16 0x7f489160d2ce n/a (libQt5Quick.so.5 + 0x20d2ce) #17 0x7f488ff495b5 _ZN7QWindow5eventEP6QEvent (libQt5Gui.so.5 + 0x1495b5) #18 0x7f4890762f5e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x162f5e) #19 0x7f488fab1718 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b1718) #20 0x7f488ff3e73d _ZN22QGuiApplicationPrivate18processExposeEventEPN29QWindowSystemInterfacePrivate11ExposeEventE (libQt5Gui.so.5 + 0x13e73d) #21 0x7f488ff11e1c _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Gui.so.5 + 0x111e1c) #22 0x7f488a6fbc7a n/a (libQt5XcbQpa.so.5 + 0x6dc7a) #23 0x7f488d91f7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9) #24 0x7f488d91fa38 n/a (libglib-2.0.so.0 + 0x54a38) #25 0x7f488d91facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #26 0x7f488fb094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #27 0x7f488fab019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #28 0x7f488fab8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #29 0x5629241c1c6c n/a (plasmashell + 0x25c6c) #30 0x7f488f64618a n/a (libc.so.6 + 0x2718a) #31 0x7f488f646245 __libc_start_main (libc.so.6 + 0x27245) #32 0x5629241c1d81 n/a (plasmashell + 0x25d81) Stack trace of thread 1046: #0 0x7f488f71b0af __poll (libc.so.6 + 0xfc0af) #1 0x7f488d91f9ae n/a (libglib-2.0.so.0 + 0x549ae) #2 0x7f488d91facc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #3 0x7f488fb094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEve
Re: kded5 crashes
On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote: > i removed apper and things seems to be better. > waiting for confirmation from the other guys too. I didin't have apper installed to begin with, so maybe that's why I wasn't seeing it? > now only plasmashell crashes ;) > ... > #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) > #2 0x7f4891a93be1 > _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) > #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) > #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) > #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) > #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) > #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) > #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) > #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) > #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) > #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) > #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. signature.asc Description: This is a digitally signed message part.
Re: kded5 crashes
dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. Yes, sorry. Sid on a virtualbox vm, VMSVGA with 3D enabled. Intel graphics on host.
Re: kded5 crashes
Le 07/12/2022 à 12:25, Diederik de Haas a écrit : On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote: i removed apper and things seems to be better. waiting for confirmation from the other guys too. I didin't have apper installed to begin with, so maybe that's why I wasn't seeing it? now only plasmashell crashes ;) ... #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f4891a93be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. I am not seeing this either out of 6 bare metal machines on SID. Mix of AMD desktop GPU and Intel laptops. None have "Apper" installed, all are running Wayland sessions. There is some KDE noise in the logs, but nothing like what's reported here. Is there a bug report opened somewhere?
Re: kded5 crashes
Il 07/12/22 15:47, tv.debian ha scritto: Le 07/12/2022 à 12:25, Diederik de Haas a écrit : On Wednesday, 7 December 2022 11:49:21 CET luca.pedrielli wrote: i removed apper and things seems to be better. waiting for confirmation from the other guys too. I didin't have apper installed to begin with, so maybe that's why I wasn't seeing it? now only plasmashell crashes ;) ... #1 0x7f488f65aef2 raise (libc.so.6 + 0x3bef2) #2 0x7f4891a93be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f488f65af90 n/a (libc.so.6 + 0x3bf90) #4 0x7f4882a1c158 n/a (vmwgfx_dri.so + 0x61c158) #5 0x7f4882a1c343 n/a (vmwgfx_dri.so + 0x61c343) #6 0x7f4882dcbcad n/a (vmwgfx_dri.so + 0x9cbcad) #7 0x7f4882575083 n/a (vmwgfx_dri.so + 0x175083) #8 0x7f48824b0a23 n/a (vmwgfx_dri.so + 0xb0a23) #9 0x7f48824b40cc n/a (vmwgfx_dri.so + 0xb40cc) #10 0x7f48898f9104 n/a (libGLX_mesa.so.0 + 0x43104) #11 0x7f48898e2a38 n/a (libGLX_mesa.so.0 + 0x2ca38) #12 0x7f488ce49ccc n/a (libGLX.so.0 + 0x4ccc) dri, GLX and mesa all point to graphics subsystem, so it's probably useful to share the GPU that you're using. I am not seeing this either out of 6 bare metal machines on SID. Mix of AMD desktop GPU and Intel laptops. None have "Apper" installed, all are running Wayland sessions. There is some KDE noise in the logs, but nothing like what's reported here. Is there a bug report opened somewhere? Here is another example. -- Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. PID: 2597 (plasmashell) UID: 1000 (ilprof) GID: 1000 (ilprof) Signal: 11 (SEGV) Timestamp: Wed 2022-12-07 16:57:47 CET (18s ago) Command Line: /usr/bin/plasmashell --no-respawn Executable: /usr/bin/plasmashell Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-plasmashell.service Unit: user@1000.service User Unit: plasma-plasmashell.service Slice: user-1000.slice Owner UID: 1000 (ilprof) Boot ID: 305afcfdae664e7a8857639f127e51b5 Machine ID: ad6738af96e1470e8772413d7f9c5dd0 Hostname: unstable Storage: /var/lib/systemd/coredump/core.plasmashell.1000.305afcfdae664e7a8857639f127e51b5.2597.167042866700.zst (present) Size on Disk: 10.5M Message: Process 2597 (plasmashell) of user 1000 dumped core. Module libsystemd.so.0 from deb systemd-252.2-2.amd64 Module libudev.so.1 from deb systemd-252.2-2.amd64 Stack trace of thread 2597: #0 0x7f8ba10a9ccc __pthread_kill_implementation (libc.so.6 + 0x8accc) #1 0x7f8ba105aef2 __GI_raise (libc.so.6 + 0x3bef2) #2 0x7f8ba3471be1 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5be1) #3 0x7f8ba105af90 __restore_rt (libc.so.6 + 0x3bf90) #4 0x7f8b9c0fc419 _ZN19QXcbBasicConnection10internAtomEPKc (libQt5XcbQpa.so.5 + 0x6e419) #5 0x7f8b9c0dde6b _ZN8QXcbMime18mimeAtomsForFormatEP14QXcbConnectionRK7QString (libQt5XcbQpa.so.5 + 0x4fe6b) #6 0x7f8b9c0d04c5 _ZN13QXcbClipboard20sendTargetsSelectionEP9QMimeDatajj (libQt5XcbQpa.so.5 + 0x424c5) #7 0x7f8b9c0d1141 _ZN13QXcbClipboard22handleSelectionRequestEP29xcb_selection_request_event_t (libQt5XcbQpa.so.5 + 0x43141) #8 0x7f8b9c0d4616 _ZN14QXcbConnection14handleXcbEventEP19xcb_generic_event_t (libQt5XcbQpa.so.5 + 0x46616) #9 0x7f8b9c0d5946 _ZN14QXcbConnection16processXcbEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5XcbQpa.so.5 + 0x47946) #10 0x7f8b9c0fbc73 xcbSourceDispatch (libQt5XcbQpa.so.5 + 0x6dc73) #11 0x7f8b9f2667a9 g_main_dispatch (libglib-2.0.so.0 + 0x547a9) #12 0x7f8b9f266a38 g_main_context_iterate (libglib-2.0.so.0 + 0x54a38) #13 0x7f8b9f266acc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc) #14 0x7f8ba15094b6 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x3094b6) #15 0x7f8ba14b019b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b019b) #16 0x7f8ba14b8306 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b8306) #17 0x55df0e590c6c
[backtrace] kded5 crashes
On 06/12/2022 12:45, Miguel A. Vallejo wrote: Since a few days ago I've been experiencing problems with KDE in a fully upgraded Sid. The symptoms are always the same: kded5 crashes a few minutes after boot and then icons from no KDE programs (like Telegram) disappears from the system tray. A lot of errors in syslog from plasmashell, kwin_x11 and kded5 itself. Any ideas? Confirming, dozens of kwin, plasmashell, kded5 crashes, very often. I run "kwin --replace" and "plasmashell --replace" commands in Konsole terminal, as I can quickly kill and restore them when things glitch. I don't know any better solution which allows me to continue using desktop without full restart or killing X by Ctrl+Alt+Backspace combination, which I really would like to avoid. KDE desktop freezes or glitch every 24h of active desktop use, on average. I use fully updated Debian Testing, on AMD64, with Radeon 6800 XT card, X11 display, two monitors. kded5 shows Version: 5.101.0-1. Crashes today: Wed 2023-01-04 11:19:06 GMT 3813232 1000 1000 SIGSEGV present /usr/bin/kded5 6.5M Wed 2023-01-04 11:20:26 GMT 1197737 1000 1000 SIGSEGV present /usr/bin/kded5 6.3M Wed 2023-01-04 11:20:29 GMT 1209714 1000 1000 SIGSEGV present /usr/bin/kded5 4.5M Wed 2023-01-04 11:20:35 GMT 1210113 1000 1000 SIGSEGV present /usr/bin/kded5 4.5M Wed 2023-01-04 11:20:38 GMT 1211582 1000 1000 SIGSEGV present /usr/bin/kded5 4.5M Wed 2023-01-04 11:20:48 GMT 1212583 1000 1000 SIGSEGV present /usr/bin/kded5 4.5M Wed 2023-01-04 11:20:53 GMT 1217289 1000 1000 SIGSEGV present /usr/bin/kded5 4.5M Wed 2023-01-04 11:20:56 GMT 1218407 1000 1000 SIGSEGV present /usr/bin/kded5 4.2M Wed 2023-01-04 14:17:53 GMT 1219170 1000 1000 SIGSEGV present /usr/bin/kded5 4.3M Wed 2023-01-04 14:17:55 GMT 2269708 1000 1000 SIGSEGV present /usr/bin/kded5 4.2M Wed 2023-01-04 14:17:57 GMT 2269821 1000 1000 SIGSEGV present /usr/bin/kded5 4.2M Wed 2023-01-04 14:17:58 GMT 2269927 1000 1000 SIGSEGV present /usr/bin/kded5 4.2M Closer look at last four: four consecutive crashes in a few seconds. They are different, crashing on something else. Full gdb backtrace of first crash Wed 2023-01-04 14:17:53 GMT https://paste.debian.net/1266164/ And the last one: https://paste.debian.net/1266163/ Has anyone opened bug report yet? If not, against which package we can open it? kded5? -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: kded5 crashes
On 07/12/2022 00:46, Diederik de Haas wrote: It looks like I'm not having those issues, but your report did prompt me to look in syslog ... and that looks like KDE's debug log?!? 2023-01-04T20:50:31.002430+00:00 ryzen kglobalaccel5[433966]: Invalid return type in method "addAction" 2023-01-04T20:50:31.002448+00:00 ryzen kglobalaccel5[433966]: Skipped method "setDefaultShortcuts" : Pointers are not supported: QAction* 2023-01-04T20:50:31.012326+00:00 ryzen kglobalaccel5[2669877]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.012357+00:00 ryzen kglobalaccel5[2669877]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.012718+00:00 ryzen kglobalaccel5[2669877]: Invalid return type in method "addAction" 2023-01-04T20:50:31.012747+00:00 ryzen kglobalaccel5[2669877]: Skipped method "setDefaultShortcuts" : Pointers are not supported: QAction* 2023-01-04T20:50:31.025360+00:00 ryzen kglobalaccel5[3565037]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.025400+00:00 ryzen kglobalaccel5[3565037]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.025653+00:00 ryzen kglobalaccel5[3565037]: Invalid return type in method "addAction" 2023-01-04T20:50:31.025668+00:00 ryzen kglobalaccel5[3565037]: Skipped method "setDefaultShortcuts" : Pointers are not supported: QAction* 2023-01-04T20:50:31.038086+00:00 ryzen kglobalaccel5[3663985]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.038110+00:00 ryzen kglobalaccel5[3663985]: Unsupported return type 65 QPixmap in method "grab" 2023-01-04T20:50:31.038402+00:00 ryzen kglobalaccel5[3663985]: Invalid return type in method "addAction" 2023-01-04T20:50:31.038429+00:00 ryzen kglobalaccel5[3663985]: Skipped method "setDefaultShortcuts" : Pointers are not supported: QAction* 2023-01-04T20:56:34.498590+00:00 ryzen kglobalaccel5[3702650]: Omitting both --window and --windowclass arguments is not recommended 2023-01-04T20:56:34.631005+00:00 ryzen kglobalaccel5[3702659]: kf.xmlgui: Shortcut for action "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. 2023-01-04T20:56:34.631096+00:00 ryzen kglobalaccel5[3702659]: kf.xmlgui: Shortcut for action "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. 2023-01-04T21:04:34.087617+00:00 ryzen kglobalaccel5[3752214]: Omitting both --window and --windowclass arguments is not recommended 2023-01-04T21:04:34.221507+00:00 ryzen kglobalaccel5[3752838]: kf.xmlgui: Shortcut for action "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. 2023-01-04T21:04:34.221593+00:00 ryzen kglobalaccel5[3752838]: kf.xmlgui: Shortcut for action "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. 2023-01-04T21:08:36.695088+00:00 ryzen kglobalaccel5[3777855]: Omitting both --window and --windowclass arguments is not recommended 2023-01-04T21:08:36.829862+00:00 ryzen kglobalaccel5[3777864]: kf.xmlgui: Shortcut for action "" "Show Quick Commands" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. 2023-01-04T21:08:36.829961+00:00 ryzen kglobalaccel5[3777864]: kf.xmlgui: Shortcut for action "" "Show SSH Manager" set with QAction::setShortcut()! Use KActionCollection::setDefaultShortcut(s) instead. That's only last 18 minutes of the log ;) -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
Re: kded5 crashes
I'm still experiencing constant kded5 crashes, but after a few days of googling I didn't find anything relevant... Is it a Debian Unstable only issue? Greetings
Re: kded5 crashes
On Thu, 5 Jan 2023 20:11:48 +0100 "Miguel A. Vallejo" wrote: > I'm still experiencing constant kded5 crashes, but after a few days of > googling I didn't find anything relevant... Is it a Debian Unstable > only issue? > I saw it on testing, but removing apper (as mentioned earlier in the thread) seems to have improved things.
Re: kded5 crashes
Hello! Once I removed apper, plasmashell goes to 100% after login for about 30 seconds and then, everything goes ok, no extra CPU usage and everything seems to work. I guess it is ok for now. Thank you!
Re: kded5 crashes
A small update: Syslog is flooded with messages like this: 2023-01-06T00:56:11.901415+01:00 waterhole plasmashell[3567]: [3604:3604:0106/005611.901154:ERROR:shared_image_factory.cc(575)] Could not find SharedIm ageBackingFactory with params: usage: Gles2|Raster|DisplayRead|Scanout, format: RG_88, share_between_threads: 0, gmb_type: shared_memory One every few seconds
Re: kded5 crashes
Le 05/01/2023 à 20:11, Miguel A. Vallejo a écrit : I'm still experiencing constant kded5 crashes, but after a few days of googling I didn't find anything relevant... Is it a Debian Unstable only issue? Greetings On testing it crashes when apper sees upgrades are available and it's icon has to be switch on in systray. It wa s already said here, I do not know whether it is a kded5 or a apper bug.
Re: kded5 crashes
Le 06/01/2023 à 00:54, Miguel A. Vallejo a écrit : Hello! Once I removed apper, plasmashell goes to 100% after login for about 30 seconds and then, everything goes ok, no extra CPU usage and everything seems to work. I guess it is ok for now. Thank you! So a bug should be open against apper ?
Re: kded5 crashes
On 07/12/2022 14:47, tv.debian wrote: Is there a bug report opened somewhere? Bug report opened on 13th December. I added backtrace from crashes in my machine too. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1026062 -- With kindest regards, Piotr. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/ ⠈⠳⣄
