Questions about drkonqi plasmashell crash reporting

Help
1

Sorry if these are answered elsewhere. If they are, I failed to find them.

Since about last Wednesday, I’ve been getting regular plasmashell crashes, sometimes 1, 2, or 3 per day. My questions are about reporting these crashes, NOT about the crashes themselves.

Just for background, I’m running:

Operating System: KaOS (2025)
KDE Plasma Version: 6.4.4
KDE Frameworks Version: 6.17.0
Qt Version: 6.9.2
Kernel Version: 6.15.7-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840HS w/ Radeon 780M Graphics
Memory: 32 GB of RAM (30.7 GB usable)
Graphics Processor: AMD Radeon 780M Graphics

Anyway, back to crash reporting

On each crash, FOUR crash windows appear. Each time, I just used one of those and closed the other three. On the one, I’ve always selected automatic reports.

Q1: Am I supposed to be doing something with all of them?

Q2: Are the four crash windows actually a drkonqi bug?

Q3: I thought the report created a bug but when I go to bugs.kde.org and search for plasmashell with “words” crash, and sort the results by ID to get the latest at the top, I see no indication of my reports creating even a single bug. What do I need to do to get a bugs (or bugs) entered?

BTW, I have also have an install of OpenSUSE Tumbleweed. That one does NOT crash. It’s running the same Plasma and Frameworks version as KaOS, BUT the Qt in TW is 6.9.1, not 6.9.2 as in KaOS.

1 Like
2

There have been some new developments, but my questions still stand.

The new developments:

  • My Tumbleweed install now has plasmashell crashes, tho it produces five crash windows instead of the four of the KaOS crashes
  • For a day and a half so far, I no longer get plasmashell crashes in KaOS, after I did a KaOS update Sunday.

The second development suggests there’s been a fix for the crashes, but my real questions here, about the crash reporting, are still in play.

3

My guess that there’s been a fix for the plasmashell crashes is wrong, because after another half-day on KaOS, the plasmashell crash was back. Submitted the single crash report from the last window as usual.

Since the problem still exists, it seems important to know if these single reports are getting to the right place, and whether all four, or five, report windows need to be responded to.

I’m avoiding the whole plasmashell crash issue right now by posting this from a Linux Mint I installed in another partition.

4

I had a similar crash on Sunday after reboot and got three windows.
Luckily no crash since so I am not sure if Plasma shell crashed three times in short succession or if this was the same crash reported three times.

I’ve only used one of them when I ran into a similar situation (see above).

That could be.
I guess we would need something other than Plasma shell to crash to see if that also triggers multiple windows.

These crash reports actually end up in a system called Sentry instead.
It can deal with duplication and similarities which makes it more viable for these kind of entries than BugZilla.

@sitter wrote a very nice blog series on how the crash reporting works

5

This morning went back to KaOS running Plasma. Got another plasmashell crash, this time with SEVENTEEN crash reports. Answered one of them.

So back to running Mint.

Also this morning during a Google Meet videochat running on my wife’s laptop with Fedora Kinoite (which uses Plasma), she had her first plasmashell crash. I think she had about four crash windows. I responded to one. These crash reports all opened full-screen so it’s possible I miscounted them.

6

kaos has no debuginfod server which means we can’t really debug what’s going on. mint is the same. opensuse has a crippled drkonqi from what I’ve heard so I wouldn’t get my hopes up there either.

kinoite works but the crashes I’ve seen were non-trivial stuff deep inside Qt

7

OK, I’ve now posted to the KaOS forum inquiring about the missing debuginfod server.

8

I have followed the advice of a KaOS dev and installed the debug packages for the following:

  • qt6-base,
  • qt6-declarative,
  • wayland,
  • libplasma,
  • kwin &
  • plasma-workspace

I await the next crash!:slightly_smiling_face:

Another poster thought this was the related (Qt 6.9.2) bug:

https://bugs.kde.org/show_bug.cgi?id=509192

and this the proposed (temporary) solution:

https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5821

tho from the overview, this solution may not be available until 2025-11-11, kind of a long time.

I’ll stay in KaOS until I get data from the next crash, but I guess then I’ll go back to Mint for safety.