https://bugs.kde.org/show_bug.cgi?id=510390
Bug ID: 510390
Summary: Plasma Discover invocation is randomly blocked, until
reboot, by an EAGAIN on a FUTEX call that requires 300
s to fail
Classification: Applications
Product: Discover
Version First 6.4.5
Reported In:
Platform: Fedora RPMs
URL: https://discuss.kde.org/t/why-cant-i-open-discover/395
60/5?u=rokejulianlockhart
OS: Linux
Status: REPORTED
Severity: crash
Priority: NOR
Component: discover
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
Created attachment 185601
--> https://bugs.kde.org/attachment.cgi?id=185601&action=edit
The Output Of `time strace -Ttr plasma-discover`
# SUMMARY
Apparently randomly, I (and other users, including my brother, per
https://discuss.kde.org/t/why-cant-i-open-discover/39560/5?u=rokejulianlockhart)
become unable to invoke Discover, until we invoke `qdbus-qt6 org.kde.Shutdown
/Shutdown org.kde.Shutdown.logoutAndReboot` (`org.kde.Shutdown.logout` might
also work, but I've yet to confirm, due to how rarely this reproduces).
# STEPS TO REPRODUCE
Invoke `plasma-discover` (from `$Env:PATH`, in `bash`).
# OBSERVED RESULT
It closes with an `EAGAIN` of "Resource temporarily unavailable", but requires
an inordinate amount of time to:
> ~~~
> real 5m8.252s
> user 0m0.307s
> sys 0m0.273s
> ~~~
Most notable is:
> ~~~
> 13:15:37 (+ 0.000029) futex(0x55bcc7b568d8,
> FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL,
> FUTEX_BITSET_MATCH_ANY) = 0 <299.662141>
> 13:20:37 (+ 299.662324) futex(0x55bcc7b56890, FUTEX_WAKE_PRIVATE, 1) = 0
> <0.000085>
> ~~~
I've seen this reach 300 s, but that's a mere difference of 1 s.
# EXPECTED RESULT
It should invoke.
# SOFTWARE/OS VERSIONS
> ~~~
> Operating System: Fedora Linux 42
> KDE Plasma Version: 6.4.5
> KDE Frameworks Version: 6.18.0
> Qt Version: 6.9.2
> Kernel Version: 6.16.9-200.fc42.x86_64 (64-bit)
> Graphics Platform: Wayland
> ~~~
The hardware likely doesn't matter, due to the amount of hardware that this has
occurred on.
--
You are receiving this mail because:
You are watching all bug changes.
