Bug 427477

Summary:	/mnt directory not visible in Linux file system / Collection cannot be added from removable media
Product:	[Applications] digikam	Reporter:	Fred Brigham <frbrigham>
Component:	Setup-Collections	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, metzpinguin
Priority:	NOR
Version First Reported In:	7.1.0
Target Milestone:	---
Platform:	Debian stable
OS:	ChromeOS
Latest Commit:		Version Fixed/Implemented In:	7.3.0
Sentry Crash Report:
Attachments:	attachment-7113-0.html

Description Fred Brigham 2020-10-09 09:08:46 UTC

SUMMARY
I have installed digiKam 7.1.0 from Flatpak as a Linux App on my Lenovo Flex 5 Chromebook. The installation appears to have been successful.
I wish to add a Collection from an sd card and note that "removable media are supported". The sd card has been "Shared with Linux" and is visible in the /mnt directory via the Terminal. I can see /mnt and link to the sd card in other Linux apps, e.g. Handbrake. However, the mnt directory does not appear in the Linux file system in digiKam when selecting a Collection. 

STEPS TO REPRODUCE
1. Share sd card with Linux in Chrome OS.
2. Open digiKam and go to Collections Settings.
3. Click on Add Collection and navigate to the top level directories.

OBSERVED RESULT
The top level directories are visible but not /mnt.

EXPECTED RESULT
/mnt should be visible allowing the sd card to be shared. 
Note: The expected result is obtained with other Linux apps such as Handbrake which are installed on the Chromebook and there is no problem reading from or writing to the sd card.

SOFTWARE/OS VERSIONS
Chrome OS: version 85
Linux: Debian GNU/Linux 10 (Buster)

ADDITIONAL INFORMATION
The Chrome OS platform with Android apps plus Linux is becoming increasingly popular. In the future I see great opportunity for widespread use of digiKam on Chromebooks. It would therefore be good to provide a fix for this issue.

Comment 1 Maik Qualmann 2020-10-09 10:35:59 UTC

Switch to the native file dialogs in the digiKam settings. Is digiKam from AppImage or native Debian packages? Otherwise we already know the problem of broken file dialogs under Debian / Red Hat, this is a package error, the set file filter is not processed correctly.

Maik

Comment 2 Maik Qualmann 2020-10-09 10:43:29 UTC

see you write Flatpak...

Maik

Comment 3 Maik Qualmann 2020-10-09 11:05:38 UTC


*** This bug has been marked as a duplicate of bug 425138 ***

Comment 4 Fred Brigham 2020-10-09 14:26:36 UTC

Created attachment 132237 [details]
attachment-7113-0.html

Thanks Maik. I switched to "use native file dialogs from system" and I can
now see /mnt and the sd card but cannot select a folder. When I select a
folder and click on Open the folder is opened but not selected in digiKam.
Also it says that the folder I created for the database doesn't exist even
though I can see this folder in my home directory. digiKam offers to create
the folder but this always fails. Something is still wrong. Perhaps I do
not have the correct permissions although my Linux setup on the Chromebook
appears to be fine as other apps work correctly. As a beginner to Linux I
am struggling with this problem and I wouldn't know how to check the
permissions.

Not sure whether digiKam is from AppImage or native Debian packages. I
installed
from flathub which I assume is a reliable source:
https://flathub.org/apps/details/org.kde.digikam

Fred

On Fri, 9 Oct 2020 at 11:36, Maik Qualmann <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=427477
>
> Maik Qualmann <metzpinguin@gmail.com> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |metzpinguin@gmail.com
>
> --- Comment #1 from Maik Qualmann <metzpinguin@gmail.com> ---
> Switch to the native file dialogs in the digiKam settings. Is digiKam from
> AppImage or native Debian packages? Otherwise we already know the problem
> of
> broken file dialogs under Debian / Red Hat, this is a package error, the
> set
> file filter is not processed correctly.
>
> Maik
>
> --
> You are receiving this mail because:
> You reported the bug.

Comment 5 Maik Qualmann 2020-10-09 18:50:33 UTC

I haven't dealt with the Flatpak yet. But it uses a sandbox. There is probably a configuration tool to give digiKam the right to access your file system. I recommend you download the AppImage from www.digikam.org. You just have to set the file flag to execute and you can just start it. It should be easier for you than the Flatpak.

Maik

Comment 6 Fred Brigham 2020-10-10 13:45:50 UTC

Thanks for the good advice. I downloaded the AppImage as recommended and all works fine! Sorry for reporting a bug with digiKam when this is more of a Flatpak issue. However, lots of people are likely to use Flatpak to get digiKam and many will have the same problem.

Comment 7 caulier.gilles 2021-04-04 07:36:47 UTC

Fixed with #425138