Created attachment 1618064 [details]
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
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
When launching a qt application from qdbus or from flatpak it loses the theme.
The theme should work when launching qt applications in this way.
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)
Created attachment 1618065 [details]
what dolphin is supposed to look like
Does anyone pay attention to these bug reports?
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
FEDORA-2019-1f174ad525 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-1f174ad525
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
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)
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.
This is not fixed.
Related bug 1749362 ?
Yes. Same bug.
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).
*** Bug 1749362 has been marked as a duplicate of this bug. ***
It doesn't fix it, as dolphin can still be launched with dbus (for example - from a flatpak)
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).