Bug 507670 - Applications are very slow at opening/don't open after a few hours of uptime
Summary: Applications are very slow at opening/don't open after a few hours of uptime
Status: RESOLVED DUPLICATE of bug 506892
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.4.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-30 19:06 UTC by Sagnik S.
Modified: 2025-07-31 07:35 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sagnik S. 2025-07-30 19:06:09 UTC 
SUMMARY
After some hours of uptime (around 12-16 hours), applications don't open, or open very slowly (likely after the dbus timeout is reached), and notifications stop working. The application launcher doesn't open either.

For example, this is the journalctl output when opening Brave:
Jul 31 00:29:34 SagnikS-WS-1 systemd[3377]: Started app-com.brave.Browser@4a05ab977d6a4c12ba5c4ffb11d36432.service - Brave - Web Browser.
Jul 31 00:29:34 SagnikS-WS-1 systemd[3377]: Started app-flatpak-com.brave.Browser-2277530041.scope.
Jul 31 00:29:34 SagnikS-WS-1 systemd[3377]: Started app-flatpak-com.brave.Browser-1794326370.scope.
Jul 31 00:29:34 SagnikS-WS-1 flatpak[1679996]: Opening in existing browser session.
Jul 31 00:29:59 SagnikS-WS-1 plasmashell[1306317]: kf.kio.gui: Failed to launch process as service: "app-com.brave.Browser@4a05ab977d6a4c12ba5c4ffb11d36432.service" "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

And when opening spectacle:
Jul 31 00:21:10 SagnikS-WS-1 spectacle[1675319]: Error querying plasma version "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

STEPS TO REPRODUCE
1. Have a long enough uptime
2. Try to launch any application

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit)
Graphics Platform: X11
Processors: 32 × AMD Ryzen 9 5950X 16-Core Processor
Memory: 128 GiB of RAM (125.7 GiB usable)
Graphics Processor: NVIDIA GeForce RTX 3060

ADDITIONAL INFORMATION

Running plasmashell --replace in krunner does not fix it. So far the only way I have been able to fix this, albeit temporarily, is to kill -9 the plasmashell process and then it restarts without any problems.

This problem started about 3 days back after I updated Fedora KDE, prior to that there were no problems.
Comment 1 Sagnik S. 2025-07-30 19:09:53 UTC 
I also occasionally see such errors after the update:
Jul 31 00:30:11 SagnikS-WS-1 plasmashell[1306317]: qt.network.http2: stream 3 finished with error: "HTTP/2 protocol error"
Jul 31 00:30:11 SagnikS-WS-1 plasmashell[1306317]: qt.network.http2: stream 3 error: "HEADERS on invalid stream"
Jul 31 00:30:11 SagnikS-WS-1 plasmashell[1306317]: qt.network.http2.connection: [0x7f91444a26c0] Connection error: HEADERS on invalid stream (1)


I am not sure if they are related
Comment 2 Harald Sitter 2025-07-31 06:53:27 UTC 
Sounds a lot like bug #506892
Comment 3 David Edmundson 2025-07-31 07:35:18 UTC 
>Jul 31 00:21:10 SagnikS-WS-1 spectacle[1675319]: Error querying plasma version "org.freedesktop.DBus.Error.NoReply"

That's important. It implies plasmashell is frozen.

*** This bug has been marked as a duplicate of bug 506892 ***