Hi everybody.
Having some trouble and hoping the community can offer some insight. Files have been appearing in ~/ for months with impossible file names not recognized by Dolphin or other programs. Initially, I was ignoring them but lately they have become a major nuisance since they disrupt working in ~/ in an application I have started using. Below is an example of two of these files which appeared recently:
Opening one up, below are the contents. Contents of the other file are similar.
[KCrash]
exe=/�4^D�U
appname=��1^D�U
apppath=�e�\�U
signal=6
pid=553370
sudo journalctl --no-pager -p 3 -xb returned:
May 17 16:44:02 mycomputername systemd-coredump[602067]: [🡕] Process 600452 (org_kde_powerde) of user 1000 dumped core.
Module libsystemd.so.0 from deb systemd-252.22-1~deb12u1.amd64
Module libudev.so.1 from deb systemd-252.22-1~deb12u1.amd64
Stack trace of thread 600452:
#0 0x00007fe9f24aed14 pthread_sigmask (libc.so.6 + 0x8fd14)
#1 0x00007fe9f245b239 sigprocmask (libc.so.6 + 0x3c239)
#2 0x00007fe9f36e9e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b)
#3 0x00007fe9f36eab3e _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x5b3e)
#4 0x00007fe9f245b050 n/a (libc.so.6 + 0x3c050)
#5 0x00007fe9e8fd18c6 n/a (KSC_KWayland.so + 0x148c6)
#6 0x00007fe9ed60cf7a n/a (libffi.so.8 + 0x6f7a)
#7 0x00007fe9ed60c40e n/a (libffi.so.8 + 0x640e)
#8 0x00007fe9ed60cb0d ffi_call (libffi.so.8 + 0x6b0d)
#9 0x00007fe9ecfe6761 n/a (libwayland-client.so.0 + 0xa761)
#10 0x00007fe9ecfe2aaa n/a (libwayland-client.so.0 + 0x6aaa)
#11 0x00007fe9ecfe441c wl_display_dispatch_queue_pending (libwayland-client.so.0 + 0x841c)
#12 0x00007fe9ecb2b872 _ZN15QtWaylandClient15QWaylandDisplay13flushRequestsEv (libQt5WaylandClient.so.5 + 0x76872)
#13 0x00007fe9f28dd6f0 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2dd6f0)
#14 0x00007fe9f28b16f8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b16f8)
#15 0x00007fe9f28b4681 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b4681)
#16 0x00007fe9f290a153 n/a (libQt5Core.so.5 + 0x30a153)
#17 0x00007fe9f151e7a9 g_main_context_dispatch (libglib-2.0.so.0 + 0x547a9)
#18 0x00007fe9f151ea38 n/a (libglib-2.0.so.0 + 0x54a38)
#19 0x00007fe9f151eacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
#20 0x00007fe9f2909836 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x309836)
#21 0x00007fe9f28b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b)
#22 0x00007fe9f28b82d6 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2b82d6)
#23 0x0000559c635d1c6e n/a (org_kde_powerdevil + 0x6c6e)
#24 0x00007fe9f244624a n/a (libc.so.6 + 0x2724a)
#25 0x00007fe9f2446305 __libc_start_main (libc.so.6 + 0x27305)
#26 0x0000559c635d1cd1 n/a (org_kde_powerdevil + 0x6cd1)
Stack trace of thread 600457:
#0 0x00007fe9f251b15f __poll (libc.so.6 + 0xfc15f)
#1 0x00007fe9f151e9ae n/a (libglib-2.0.so.0 + 0x549ae)
#2 0x00007fe9f151eacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
#3 0x00007fe9f290984e _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30984e)
#4 0x00007fe9f28b017b _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b017b)
#5 0x00007fe9f26cab87 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcab87)
#6 0x00007fe9f3435487 n/a (libQt5DBus.so.5 + 0x17487)
#7 0x00007fe9f26cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#8 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#9 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
Stack trace of thread 600456:
#0 0x00007fe9f251b15f __poll (libc.so.6 + 0xfc15f)
#1 0x00007fe9ecb2fcd6 n/a (libQt5WaylandClient.so.5 + 0x7acd6)
#2 0x00007fe9f26cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#3 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#4 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
Stack trace of thread 600455:
#0 0x00007fe9f24a4e96 n/a (libc.so.6 + 0x85e96)
#1 0x00007fe9f24a7558 pthread_cond_wait (libc.so.6 + 0x88558)
#2 0x00007fe9f26d1a2b _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd1a2b)
#3 0x00007fe9ecb2fc7f n/a (libQt5WaylandClient.so.5 + 0x7ac7f)
#4 0x00007fe9f26cbd43 n/a (libQt5Core.so.5 + 0xcbd43)
#5 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#6 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
Stack trace of thread 600496:
#0 0x00007fe9f251da41 pselect (libc.so.6 + 0xfea41)
#1 0x00007fe9f12b6a62 n/a (libusbmuxd-2.0.so.6 + 0x2a62)
#2 0x00007fe9f12b7e60 n/a (libusbmuxd-2.0.so.6 + 0x3e60)
#3 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#4 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
Stack trace of thread 600458:
#0 0x00007fe9f251b15f __poll (libc.so.6 + 0xfc15f)
#1 0x00007fe9f151e9ae n/a (libglib-2.0.so.0 + 0x549ae)
#2 0x00007fe9f151eacc g_main_context_iteration (libglib-2.0.so.0 + 0x54acc)
#3 0x00007fe9f151eb11 n/a (libglib-2.0.so.0 + 0x54b11)
#4 0x00007fe9f1548cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
#5 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#6 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
Stack trace of thread 600459:
#0 0x00007fe9f251b15f __poll (libc.so.6 + 0xfc15f)
#1 0x00007fe9f151e9ae n/a (libglib-2.0.so.0 + 0x549ae)
#2 0x00007fe9f151ecef g_main_loop_run (libglib-2.0.so.0 + 0x54cef)
#3 0x00007fe9eb1cd7b6 n/a (libgio-2.0.so.0 + 0x1197b6)
#4 0x00007fe9f1548cfd n/a (libglib-2.0.so.0 + 0x7ecfd)
#5 0x00007fe9f24a8134 n/a (libc.so.6 + 0x89134)
#6 0x00007fe9f25287dc n/a (libc.so.6 + 0x1097dc)
ELF object binary architecture: AMD x86-64
â–‘â–‘ Subject: Process 600452 (org_kde_powerde) dumped core
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: https://www.debian.org/support
â–‘â–‘ Documentation: man:core(5)
â–‘â–‘
â–‘â–‘ Process 600452 (org_kde_powerde) crashed and dumped core.
â–‘â–‘
â–‘â–‘ This usually indicates a programming error in the crashing program and
â–‘â–‘ should be reported to its vendor as a bug.
These are almost certainly related due to the log timestamp matching the time of the file creation in ~/. So, I believe I have identified the cause, but I am quite new to Linux/Debian/KDE and do not really know what to do to investigate the issue further and find a solution. Would really appreciate any assistance and advice to try to fix this. Thank you very much in advance.
