Summary: | [ANR] Spectacle crashed when DBus wasn't available | ||
---|---|---|---|
Product: | [Applications] Spectacle | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
Component: | General | Assignee: | Noah Davis <noahadvs> |
Status: | RESOLVED NOT A BUG | ||
Severity: | crash | CC: | kde, nate |
Priority: | NOR | Keywords: | drkonqi |
Version First Reported In: | 6.4.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
See Also: | https://bugzilla.redhat.com/show_bug.cgi?id=2391175 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | https://crash-reports.kde.org/organizations/kde/issues/241606/events/bb85740589ba4e8ba86e293146d22ba7/ |
Description
Roke Julian Lockhart Beedell
2025-08-26 22:45:29 UTC
Reported downstream, at https://bugzilla.redhat.com/show_bug.cgi?id=2391175#c0. > I had `cat /dev/random` open in a few terminals, which appeared to utterly hammer DBus
Yeah, don't do that.
What are you doing to your computer here? I'm seeing a lot of bug reports about really abnormal usage that's causing weird bugs. The system can't be expected to survive behavior that amounts to sabotage, even if unintentional.
(In reply to Nate Graham from comment #2) I was testing Konsole search, because it just had a huge upgrade. By mere chance, I realised that that method of outputting garbage prints bell characters, which the shell outputs. I've had a few other applications spam notifications before (Firefox), so all the others, except this, do seem to be decent bugs in their own rights. I did recently test Spectacle on an OS without DBus, and it coped well. It only seems to fail when it can't access DBus, despite registering its existence. The sole real-world instance of *this* bug that I've encountered was a very, very aged laptop that probably shouldn't have been using Plasma 5 at the time. (In reply to Roke Julian Lockhart Beedell from comment #3) Albeit tangential, to answer your question better, I was also testing Konsole's display output speed limits, since I once had it SIGSEGV on OSTW when outputting multiple STraces, which that command much better reproduces. I believe that https://bugs.kde.org/show_bug.cgi?id=508721#c1 should remediate *that*, though. (In reply to Nate Graham from comment #2) If of any use, by incredible coincidence, I actually encountered this DBus overload organically today (as did my brother and a stranger, to a lesser extent), as https://discuss.kde.org/t/why-cant-i-open-discover/39560/5?u=rokejulianlockhart explains. Consequently, this isn't entirely a theoretical problem, albeit rare. |