https://bugs.kde.org/show_bug.cgi?id=373629
Henrik Fehlauer <rk...@lab12.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Filename in move file |Filename in move/copy/link
|dialog is not set to actual |dialogs missing for GTK2
|filename |platformtheme/QPA
Status|RESOLVED |REOPENED
Ever confirmed|0 |1
Resolution|UPSTREAM |---
--- Comment #20 from Henrik Fehlauer <rk...@lab12.net> ---
Thanks for your continued investigations, Oded. Did some more testing and
discovered it can be misleading to use XDG_CURRENT_DESKTOP=gnome, because
depending on distro and env this results in either a GTK2 or a GTK3 dialog
(i.e. scratch my previous finding about this being a GTK3 regression).
Proper test matrix, confirming your observations:
BROKEN:
QT_QPA_PLATFORMTHEME=gtk2 gwenview ~/Pictures
WORKING:
QT_QPA_PLATFORMTHEME=gtk2 kdialog --getsavefilename ~/file.ext
QT_QPA_PLATFORMTHEME=gtk2 kate ~/file.ext
QT_QPA_PLATFORMTHEME=gtk3 gwenview ~/Pictures
QT_QPA_PLATFORMTHEME=gtk3 kdialog --getsavefilename ~/file.ext
QT_QPA_PLATFORMTHEME=gtk3 kate ~/file.ext
This is a bit weird, I wonder why that is. Maybe because kdialog is a
standalone app? However, testing with Kate (open file, trigger "save as"), GTK2
also works. I guess the next step would be to compare the code snippets
responsible for opening the dialog in Gwenview and Kate respectively (let me
know if you are interested and need help in getting started with this). Note
this does not yet mean Gwenview is at fault :)
In general Gwenview is supposed to work in a GTK environment, but I'm not sure
which desktops are still stuck on GTK2 and have no plans of migrating to GTK3.
I'm reopening and adapting the title a bit, but I don't think the issue is of
high priority and users can set GTK3 for Gwenview as a workaround for now.
--
You are receiving this mail because:
You are watching all bug changes.
