Crash viewer log empty
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
Please confirm there isn't an open report for this issue
- I have searched through bug reports
Summary
Crash viewer log is empty despite archives of crashes in \var\lib\systemd\coredump. Also recent crashes seem to disappear after a set amount of day. Trying to view a crash dump from a few days ago is not possible,
Steps to reproduce
Open crash viewer from Plasma menu.
Expected result
Should be able to see recent crashes in the log.
Actual result
Blank window which says No crashes matching the search
Environment
- Is system up to date?
Repo
Shannon (stable)
Desktop Environment
Plasma
System details
System:
Host: tim-solus Kernel: 6.12.21-316.current arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.3.4 Distro: Solus 4.7 endurance
Machine:
Type: Desktop Mobo: Gigabyte model: H310M S2H 2.0
serial: UEFI: American Megatrends v: F14
date: 11/10/2021
CPU:
Info: 6-core Intel Core i5-9400F [MCP] speed (MHz): avg: 4100
min/max: 800/4100
Graphics:
Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nvidia v: 570.133.07
Device-2: A4Tech FHD 1080P PC Camera driver: snd-usb-audio,uvcvideo
type: USB
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: gpu: nvidia,nvidia-nvswitch
resolution: 1920x1200~60Hz
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07
renderer: NVIDIA GeForce GT 1030/PCIe/SSE2
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
driver: r8169
Device-2: Realtek RTL88x2bu [AC1200 Techkey] driver: rtw_8822bu type: USB
Drives:
Local Storage: total: 2.24 TiB used: 937.73 GiB (40.9%)
Info:
Memory: total: 32 GiB available: 31.28 GiB used: 5 GiB (16.0%)
Processes: 318 Uptime: 25m Shell: Bash inxi: 3.3.37
Other comments
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the crash viewer opened from the Plasma menu and inspect how it discovers archives under /var/lib/systemd/coredump. Reproduce the blank “No crashes matching the search” result with a recent crash and compare it with the available archives. Done means recent crash dumps appear in the viewer and remain available for the reported period.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100