Bug 495845

Summary:	Searching application (KRunner, Plasmashell) quits for some queries while the Browser Integration plugin is enabled
Product:	[Plasma] plasma-browser-integration	Reporter:	Karcsesz <dump+kdebugs>
Component:	Firefox	Assignee:	Kai Uwe Broulik <kde>
Status:	CONFIRMED ---
Severity:	crash	CC:	bshah, mw
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	crashed-process-viewer log from plasma crash backtrace of plasmashell

Description Karcsesz 2024-11-05 15:23:04 UTC

SUMMARY
Whenever searching for a select few keywords in KRunner or through Application Launcher's search field, the given application cleanly exits without logging anything or generating a crash dump.

I have quite a lot of tabs open in Firefox (manually running a query against the extension's DBus service makes QDBusViewer lag), so my hunch is this either has to do with a message size limit or the request timing out.

Disabling "Browser Tabs" from Plasma Search works around the issue.

STEPS TO REPRODUCE
1. (probably) have a lot of open tabs in Firefox (I have a bit over 1000, no I do not have a problem >c<)
2. Install Plasma Integration 1.9.1 and have Browser Tabs enabled in Plasma Search settings
3. Experiment with KRunner while having `journalctl --user -f` running
4. On some search terms KRunner exits without a single logged error
5. Try the same with the builtin search for Application Launcher
6. plasmashell quits without any automatic recovery taking place

OBSERVED RESULT

```
nov 05 16:03:25 Littlepip systemd[1005]: Started KRunner.
nov 05 16:03:25 Littlepip krunner[7829]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
nov 05 16:03:32 Littlepip systemd[1005]: plasma-krunner.service: Consumed 844ms CPU time, 177.9M memory peak.
```

EXPECTED RESULT
Plasma Search either truncates the response and returns less precise results or scolds the user for having too many open tabs.

SOFTWARE/OS VERSIONS
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma: 6.11.6-arch1-1 (64-bit)
KDE Plasma Version: 6.2.2 (Wayland)
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0

Comment 1 Michał Walczak 2025-07-25 09:56:11 UTC

Created attachment 183505 [details]
crashed-process-viewer log from plasma crash

I'm attaching this log, as I've noticed exact same behaviour.
I'm running Fedora 42 with newest available Plasma packages, Firefox 141 (2 windows with about 700 tabs open).

The problem with crashes goes away when I disable Browser Tab integration in Krunner settings.

Comment 2 Michał Walczak 2025-07-25 09:59:04 UTC

I've just noticed the log I've attached is from few days ago. Seems unrelated, sorry for the confusion.

However, this shows up in journalctl right at the crash:

Jul 25 11:41:08 plasmashell[161602]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Jul 25 11:41:08 plasmashell[161602]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Jul 25 11:41:08 plasmashell[161602]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "org.freedesktop.DBus.Error.Disconnected" "Not connected to D-Bus server"
Jul 25 11:41:08 plasmashell[161602]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:131: TypeError: Cannot read property 'screenGeometry' of null
Jul 25 11:41:08 plasmashell[161602]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:261: TypeError: Cannot read property 'plasmoid' of undefined

Comment 3 Kai Uwe Broulik 2025-07-25 10:15:13 UTC

I’m also a tab hoarder (currently got 710 tabs open) and never noticed any issues with the tabsrunner.

Can you check whether the plasma-browser-integration-host crashes or gets killed? The "not connected" suggests the host exited.

Is there any pattern you notice? Maybe there’s a specific website whose favicon is way too huge or something?

Comment 4 Bhushan Shah 2025-07-25 10:38:02 UTC

Pretty sure it's not *just* PBI which has issues, recently I had some other runners also failing...

Jul 25 12:23:04 antlia plasmashell[1620]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "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."                                                                                                                                                                                          
Jul 25 12:23:04 antlia plasmashell[1620]: kf.runner: Error requesting matches; calling "org.kde.KWin"  : "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."                                                                                                                                                                                                                
Jul 25 12:23:04 antlia plasmashell[1620]: kf.runner: Error requesting matches; calling "org.kde.plasma.browser_integration"  : "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."                                                                                                                                                                                          
Jul 25 12:23:04 antlia plasmashell[1620]: kf.runner: Error requesting matches; calling "org.kde.runners.baloo"  : "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 eventually, even launching apps freeze

Jul 25 12:23:29 antlia plasmashell[1620]: kf.kio.gui: Failed to launch process as service: "app-org.kde.dolphin@57de9d5dfa8f458aaec999adcbf73c9b.service" "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a r
eply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Jul 25 12:31:09 antlia plasmashell[1620]: kf.kio.gui: Failed to launch process as service: "app-firefox@94bd8e8d4cf9448dbf87dea6fa03ffd2.service" "org.freedesktop.DBus.Error.NoReply" "Did not receive a reply. Possible causes include: the remote application did not send a reply, th
e message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

Comment 5 Bhushan Shah 2025-08-02 04:53:13 UTC

Created attachment 183725 [details]
backtrace of plasmashell

This is backtrace of plasmashell when it is stuck in such an state.