https://bugs.kde.org/show_bug.cgi?id=498427
Mark Elston changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #7 from Bug Janitor Service ---
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days.
Please provide the requested information, then set the bug status to REPORTED.
If there is no change for at least 30 days, it wi
https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #6 from Mark Elston ---
The backtrace from `coredumpctl gdb` doesn't look too promising:
(gdb) bt
#0 0x715b136780df in g_log_structured_array ()
from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x715b136783cc in g_log_default
https://bugs.kde.org/show_bug.cgi?id=498427
Sune Vuorela changed:
What|Removed |Added
CC||k...@pusling.com
--- Comment #5 from Sune Vuorel
https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #4 from Mark Elston ---
In fact, there are exactly eight amdgpu.ids files on my system, including
`/usr/share/libdrm/amdgpu.ids'.
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #3 from Mark Elston ---
Ok. I ran it from the command-line. Here is what it prints out:
/usr/share/libdrm/amdgpu.ids: No such file or directory
kf.config.core: Watching absolute paths is not supported
"/snap/okular/162/kf6/usr/share/color
https://bugs.kde.org/show_bug.cgi?id=498427
--- Comment #2 from Mark Elston ---
I never saw a backtrace anywhere, nor was there a core file generated. Is
there a process to retrieve a backtrace I can use?
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=498427
Albert Astals Cid changed:
What|Removed |Added
CC||aa...@kde.org
Status|REPORTED
