Specification of mount point

[Stefan v. Wachter]

I am using SMB4K 4.0.5 on Ubuntu 22.04 with KDE Plasma (Tuxedo OS).

With previous SMB4K version smb shares were mounted on /home/username/smb4k

Now they are on /run/smb4k/username

Unfortunately I can not use this path to open a file as a "recently used
file". It results in an error "can't open /run/user/1000/doc/eb2ac1.....
does not exist"

I would like to specify the mount path - or did I miss anything?

Stefan

[Alexander Reinholdt]

The ability to specify the mount prefix was removed from Smb4K, because of severe security concerns (see https://security.opensuse.org/2025/12/10/smb4k-major-issues-in-kauth-helper.html for a comprehensive report by the SUSE Security Team).

Can you please elaborate on what exactly does not work? Is the share mounted, but the files can not be accessed, i.e. there is a permission issue?

[Stefan v. Wachter]

• I can see the files in the filesystem eg. in Dolphin or Konsole.
• It works normal if I use e.g. Kate or Firefox to open a file
• The Problem is appearant in LibreOffice: I open the file from Dolphin via double click in /run/smb4k/user....
  If I open "Eigenschaften" in LibreOffice it shows the file path as /run/user/1000/doc/
  Seems like for every mount action a new dir is created there with a random name e.g. eb2ac1
  After a new mount action from smb4k these dirs remain but won`t contain the smb share.
  Seems like LibreOffice uses a non-standard way to access the file system: In the file open dialog I can't see /run/smb4k at all!

[Alexander Reinholdt]

Thank you for the additional information. I tried to reproduce the LibreOffice problem on my system, but wasn't successfull:

• When opening a file from within Dolphin, the location shown under 'Properties' ('Eigenschaften') is correct: /run/smb4k/username/server name/share name/.
• Opening a file from the 'Recently Used' menu works like expected.
• The share is visible in the file open dialog.

I am using Manjaro KDE Plasma Edition with LibreOffice Version 25.8.4.2 (X86_64) / LibreOffice Community.

I will try the recent version of TUXEDO OS next. Let's see if I can reproduce the problem there.

[Stefan v. Wachter]

It's really strange: Even if I open my SMB-CIFS-Share via Dolphin/Network I get the behaviour described above. My system is up to date:
Operating System: TUXEDO OS
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-119037-tuxedo (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
Memory: 16 GiB of RAM (15.3 GiB usable)
Graphics Processor: Intel® UHD Graphics 620
Manufacturer: TUXEDO
Product Name: InfinityBook Pro 14 v4

[Alexander Reinholdt]

I just tried Smb4K 4.0.5 under a fresh TUXEDO OS install and I haven't had any issues.

Maybe your LibreOffice setup is somehow buggy? To test it, you could go to the ~/.config folder and rename the 'libreoffice' subdirectory to e.g. 'libreoffice.test'. Start LibreOffice, open the file and test again. After you finished, you can safely remove the newly created 'libreoffice' folder and rename the backed up folder 'libreoffice.test' to 'libreoffice'. All settings should be back.

What is the outcome?

[Stefan v. Wachter]

No, that doesn't make a change.

[Stefan v. Wachter]

Yes, the problem is related to my flatpak installation of LibreOffice: There is a known and open bug:
https://github.com/flathub/org.libreoffice.LibreOffice/issues/309
Possible solutions are:
1. Use another type of installation: native or appImage
2. install flatpak-kcm
$ apt install kde-config-flatpak
In System settings / Security / application grants click „Manage Flatpak settings“
In "File system access" add an entry „/run/smb4k“ or appropriate with „read/write“ access
Click apply button. See screenshot. Start LibreOffice. Now it should be possible to navigate to /run/smb4k/ to open a document.
Thanks a lot Alexander for your genious support!