Bug 1754395 - Qt applications lose system theme if launched via dbus activation (from flatpak applications or krunner)
Summary: Qt applications lose system theme if launched via dbus activation (from flatp...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: dolphin
Version: 31
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Daniel Vrátil
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1749362 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-23 07:17 UTC by P D
Modified: 2019-11-12 20:06 UTC (History)
6 users (show)

Fixed In Version: dolphin-19.08.2-2.fc31
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-31 00:57:17 UTC


Attachments (Terms of Use)
dolphin-ugly (72.36 KB, image/png)
2019-09-23 07:17 UTC, P D
no flags Details
what dolphin is supposed to look like (85.00 KB, image/png)
2019-09-23 07:17 UTC, P D
no flags Details

Description P D 2019-09-23 07:17:05 UTC
Created attachment 1618064 [details]
dolphin-ugly

Description of problem:

Note: I couldn't find which component to file this bug under so I picked dolphin because this bug affects dolphin (as well as other qt applications)

When launching a KDE / QT application such as Dolphin or Spectacle from an application that utilizes qdbus, the qt application will lose the user selected widget style (usually breeze) and use the ugly default qt theme. For example, in the dropbox flatpak from flathub, if I open dropbox folder from the tray icon, dolphin launches without theming and looks ugly. Or if I enabled the file / folder search in krunner, and open a folder that exists on my system in dolphin with krunner, it loses the theme. If I launch Dolphin (only the application, just launching from the .desktop file) in krunner the theme works. This issue can be quickly reproduced by launching Spectacle in the terminal normally (theme works), then launching it with this command: 

qdbus org.kde.Spectacle / StartAgent

in which spectacle launches without the theme (ugly)

Version-Release number of selected component (if applicable):

not sure what component provides qdbus

How reproducible:

Very.

Steps to Reproduce:
1. launch spectacle in terminal normally (theme works)
2. close spectacle
3. launch spectacle with this command: qdbus org.kde.Spectacle / StartAgent
4. notice theme looks ugly

Actual results:

When launching a qt application from qdbus or from flatpak it loses the theme.

Expected results:

The theme should work when launching qt applications in this way.

Additional info:

Attached is an screenshot of what Dolphin looks like on my system when launching from dropbox flatpak or selecting a folder in krunner. (dolphin-ugly.png)

Also attached is what dolphin looks like when launching normally. (dolphin-normal.png)

Comment 1 P D 2019-09-23 07:17:54 UTC
Created attachment 1618065 [details]
what dolphin is supposed to look like

Comment 2 P D 2019-10-17 12:57:32 UTC
Does anyone pay attention to these bug reports?

Comment 3 Rex Dieter 2019-10-17 16:38:39 UTC
Yes, people pay attention.  Personally, I've just had no time to look deeply yet, even less so to add acknowledgements for every incoming bug report.  Patience grasshopper.

That said, this almost certainly isn't a dolphin issue (ie, problem lies elsewhere).  One possibility:  dbus-activated applications may not inherit (all? any?) user environment variables

Comment 4 Fedora Update System 2019-10-18 16:16:08 UTC
FEDORA-2019-1f174ad525 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1f174ad525

Comment 5 Fedora Update System 2019-10-18 17:36:14 UTC
baloo-widgets-19.08.2-1.fc31, dolphin-19.08.2-2.fc31, dolphin-plugins-19.08.2-1.fc31, kate-19.08.2-1.fc31, kdialog-19.08.2-1.fc31, keditbookmarks-19.08.2-1.fc31, kfind-19.08.2-1.fc31, khelpcenter-19.08.2-1.fc31, konqueror-19.08.2-1.fc31, konsole5-19.08.2-1.fc31, yakuake-19.08.2-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-1f174ad525

Comment 6 P D 2019-10-19 01:12:24 UTC
Hi, thanks for taking a look at this. However, even with that dolphin update, the issue still occurs with dolphin. (And other qt applications, but that would require some other update)

Comment 7 Fedora Update System 2019-10-31 00:57:17 UTC
baloo-widgets-19.08.2-1.fc31, dolphin-19.08.2-2.fc31, dolphin-plugins-19.08.2-1.fc31, kate-19.08.2-1.fc31, kdialog-19.08.2-1.fc31, keditbookmarks-19.08.2-1.fc31, kfind-19.08.2-1.fc31, khelpcenter-19.08.2-1.fc31, konqueror-19.08.2-1.fc31, konsole5-19.08.2-1.fc31, yakuake-19.08.2-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.

Comment 8 P D 2019-10-31 03:29:58 UTC
This is not fixed.

Comment 9 Nick Cross 2019-11-11 07:39:00 UTC
Related bug 1749362 ?

Comment 10 P D 2019-11-11 07:43:09 UTC
Yes. Same bug.

Comment 11 Rex Dieter 2019-11-12 14:48:32 UTC
The update above should fix dolphin, as it is no longer dbus-activated on f31+ (it is autostarted with: dolphin --daemon on session start instead).

Comment 12 Rex Dieter 2019-11-12 14:50:34 UTC
*** Bug 1749362 has been marked as a duplicate of this bug. ***

Comment 13 P D 2019-11-12 15:37:00 UTC
It doesn't fix it, as dolphin can still be launched with dbus (for example - from a flatpak)

Comment 14 Rex Dieter 2019-11-12 20:06:32 UTC
Interesting, the mechanism is different now.

dolphin running as a background daemon listening on that dbus interface (as part of your user session) now launches dolphin, instead of dbus itself.  Means that the dolphin daemon isn't inheriting your session environment properly either?

Odd, I recall it working for me in my own testing at the time I made the update (I don't have a f31 box handy currently to retest).


Note You need to log in before you can comment on or make changes to this bug.