https://bugs.kde.org/show_bug.cgi?id=387215
Christoph Feck changed:
What|Removed |Added
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO
https://bugs.kde.org/show_bug.cgi?id=387215
--- Comment #7 from T R T ---
Another thing: I've used the experimental KDE+flatpak repo to try the
flatpakked KDE apps. I haven't tried them today.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387215
--- Comment #6 from T R T ---
By using either firejail or flatpak(the backend is bubblewrap) - these are the
most popular sandboxing solutions. I guess KIO provides a global file dialog
for every X app and if an application connects to X(and KDE) KIO ca
https://bugs.kde.org/show_bug.cgi?id=387215
--- Comment #5 from Christoph Feck ---
> Sandbox a KDE app
How? Please add exact steps to reproduce. Assuming you are using Linux, there
are several tools to restrict file system access, and we need more information
which setup you are using, and why i
https://bugs.kde.org/show_bug.cgi?id=387215
--- Comment #4 from T R T ---
I don't know what you've failed to understand. KDE services(like KIO) help
programs escape the sandbox. How to reproduce? Sandbox a KDE app and try to
select files with KDE's file dialog. If the sandboxed app's *directory
s
https://bugs.kde.org/show_bug.cgi?id=387215
--- Comment #3 from Christoph Feck ---
If you can provide the information requested in comment #2, please add it.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=387215
Christoph Feck changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=387215
GOD changed:
What|Removed |Added
CC||godgodgodd...@gmail.com
--- Comment #1 from GOD ---
Ther
https://bugs.kde.org/show_bug.cgi?id=387215
T R T changed:
What|Removed |Added
Product|dolphin |kde
Component|bars: filter|gen