Bug 446733

Summary:	"Open in File Manager Command" not working
Product:	[Applications] digikam	Reporter:	hp <tantares>
Component:	Portability-Runtime	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles
Priority:	NOR
Version First Reported In:	7.3.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:	7.4.0
Sentry Crash Report:

Description hp 2021-12-09 14:18:17 UTC

SUMMARY
***
The command "Open in File Manager" is not working at all
***
The Command "Open in File Manager" for images or folders does not produce any visible action 

STEPS TO REPRODUCE
1. Select an image 
2. Right click and select the command
3. No visbible action

OBSERVED RESULT
 no action

EXPECTED RESULT
show image in default file manager

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Ubuntu 20.04.3 LTS/-
(available in About System)
KDE Plasma Version: -
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

The logged error message: 

apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/org/freedesktop/FileManager1" interface="org.freedesktop.FileManager1" member="ShowItems" mask="send" name="org.freedesktop.FileManager1" pid=3296 label="snap.digikam.digikam" peer_pid=2882 peer_label="unconfined"

Comment 1 caulier.gilles 2021-12-09 14:41:00 UTC

This sound like a sand-boxing restriction : apparmor="DENIED" operation="dbus_method_call"  bus="session" path="/org/freedesktop/FileManager1" ...

Did you use the flatpak package of digiKam? If yes, flatpak has plenty of limitations...

Gilles Caulier

Comment 2 hp 2021-12-09 15:22:17 UTC

Hi Gilles,

No, I used the standard Ubuntu software installer, which did install the snap version. But I agree, it is some form of sandbox (apparmor) error. Maybe I try the APT package, to see if there any differences.

Thank you

Comment 3 hp 2021-12-09 16:26:48 UTC

I tried with apt-get (dpkg) and got version 6.4.0, which did not produce the error. Then I used the 7.3.0 appimage version from the digikam web site, which also did not have that error.

So I got a workaround

Thank you Gilles for the hint