Bug 401651

Summary:	Plasma-browser-integration doesn't work with 'export QT_QPA_PLATFORMTHEME="qt5ct"'
Product:	[Plasma] plasma-browser-integration	Reporter:	zjeffer <vanhouttetuur>
Component:	general	Assignee:	Kai Uwe Broulik <kde>
Status:	RESOLVED DUPLICATE
Severity:	major
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description zjeffer 2018-12-02 14:38:21 UTC

Not using KDE.

Normally I can use plasma-browser-integration fine, but only without 'export QT_QPA_PLATFORMTHEME="qt5ct"' in my .xinitrc file. I need that environment variable to get qt apps like VLC to not look like shit.

The problem is that the dbus service `org.mpris.MediaPlayer2.plasma-browser-integration` doesn't load, making it impossible for me to control the browser's media or see what's currently playing through dbus.

How can I make sure plasma-browser-integration works with `QT_QPA_PLATFORMTHEME="qt5ct"`?

Comment 1 Kai Uwe Broulik 2018-12-03 08:37:38 UTC

Can you check its console output? If it prints *anything* on stdout other than communication with the browser, it breaks, likely Bug 400906

Comment 2 zjeffer 2018-12-03 11:29:37 UTC

This is the console output of /usr/bin/plasma-browser-integration-host, with 'export QT_QPA_PLATFORMTHEME="qt5ct"':

QSocketNotifier: Can only be used with threads started with QThread
Q{"action":"debug","payload":{"message":"using qt5ct plugin"},"subsystem":"debug"}C{"action":"created","payload":{"version":1},"subsystem":"settings"}E{"action":"created","payload":{"version":1},"subsystem":"kdeconnect"}D{"action":"created","payload":{"version":1},"subsystem":"downloads"}E{"action":"created","payload":{"version":1},"subsystem":"tabsrunner"}@{"action":"created","payload":{"version":1},"subsystem":"mpris"}*{"action":"loaded","subsystem":"settings"}

The first line is indeed the same as Bug 400906.

Comment 3 Kai Uwe Broulik 2018-12-03 11:47:50 UTC

Ok, thanks

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