https://bugs.kde.org/show_bug.cgi?id=400906
Bug ID: 400906
Summary: Integration host does not receive messages from
browser plugin
Product: plasma-browser-integration
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: wolfgang.g...@gmx.at
Target Milestone: ---
SUMMARY
I am running your browser plugin and integration host executable with GNOME
3.30 as my desktop environment, mainly to control video/audio playback using
MPRIS and/or media keys. The integration is started by Firefox and running in
the background. Media control is activated in the Firefox addon settings, but
media key control does not work (see additional information for details).
STEPS TO REPRODUCE
1. On a GNOME + Firefox installation install also the integration
2. Open up a Youtube video and start it
3. Try to control it using the media keys (should work on KDE apparently I
guess)
OBSERVED RESULT
Nothing happens, i.e. video does not respond to play/pause commands.
EXPECTED RESULT
I would expect it to work even on GNOME desktop environment as this is plugging
into the general MPRIS2 DBus API and thus should be recognized by every desktop
environment/program that is capable to interface with MPRIS2. (And I really
would like to use it as sadly GNOME does not provide me such a nice
integration.)
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x64, GNOME 3.30.2
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: -
Qt Version: -
ADDITIONAL INFORMATION
After debugging the browser extension as a first try to identify the issue I
tried to run /usr/bin/plasma-browser-integration-host directly and it is
logging an error:
> QSocketNotifier: Can only be used with threads started with QThread
As far as I can see after some more debugging the application did not receive
any JSON messages sent to it by Firefox.
I 'fixed' it by replacing the `QApplication` in `main.cpp` by a
`QCoreApplication` and removing the `a.setQuitOnLastWindowClosed(false)` call.
This does eliminate the error for me and brings the extension to life.
However, I do not know the implications of this change regarding the KDE
desktop environment.
--
You are receiving this mail because:
You are watching all bug changes.
