https://bugs.kde.org/show_bug.cgi?id=500231
--- Comment #10 from BOF <bugs_kde_org.5.k...@spamgourmet.com> --- (In reply to Tobias Leupold from comment #9) > If you know how to have an AppImage built automatically, feel free to file a > PR adding this! I don't … > > However, I now dowloaded Neo (neon-user-20250202-0745.iso), installed it > into a QEMU VM, booted it, installed all needed dependencies, build KGeoTag > git master, downloaded your test image dragged and dropped it onto the > unassigned images list. The image was added like it should be. > > Apparently, this is either some local problem of your machine, or some > downstream issue. No matter what I do, I can't reproduce it, no matter where > I build KGeoTag (three different distributions tested so far) or if I use > git master or v1.7.0. And if I can't reproduce it, I can't fix it … > > Maybe, this is some Flatpak or whatever issue? May it be some sandboxed > KGeoTag isn't allowed to read the file system under some circumstances?! I > honestly have no idea how to help you :-( Have you tried the flatpak version as well or just your own builds? As your idea that it might be related to flatpak already was a problem at one time in the for me, I checked this. When I use flatseal to allow KGeoTag access to "filesystem=home" drag & drop works. Though I do not understand why opening the image would work with the regular menu though if it's just about access rights - maybe Wayland and some security thingy could be involved here? Do you think that there could be any difference between X11 and Wayland here? -- You are receiving this mail because: You are watching all bug changes.
