Smb4K Activity
Advanced Network Neighborhood Browser and Samba Share Mounting Utility
Brought to you by:
areinholdt
Activity for Smb4K
-
Alexander Reinholdt posted a comment on discussion General Discussion
I haven't used KDE Linux or any other immutable distro yet, so I don't have any advice at the moment.
-
Sarreq Teryx posted a comment on discussion General Discussion
with the error: sudo cmake --install build -- Install configuration: "Release" -- Installing: /lib/libsmb4kcore.so CMake Error at build/core/cmake_install.cmake:52 (file): file INSTALL cannot copy file "/home/sarreq/Downloads/smb4k-4.0.6/build/bin/libsmb4kcore.so" to "/lib/libsmb4kcore.so": Read-only file system. Call Stack (most recent call first): build/cmake_install.cmake:47 (include) because of the immutable fs KDE Linux is using. is there another way to get this to work?
-
Smb4K 4.0.6 released
-
Smb4K released /4.0.6/smb4k-4.0.6.tar.xz
-
-
Stefan v. Wachter posted a comment on discussion Help
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...
-
No, that doesn't make a change.
-
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...
-
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...
-
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...
-
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....
-
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...
-
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...
-
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....
-
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?
-
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
-
-
Smb4K 4.0.5 (security bug fix release)
-
-
-
Home
-
Home
-
Thank you for sharing this. I will have a look and fix it.
-
Dean posted a comment on discussion Help
Currently, SMB4K with WS-Discovery enabled correctly finds Windows hosts on the network. However, when a discovered host is clicked in the “Network Neighborhood” browser no shares are displayed. BTW, I think this pane would be better described as "Discovered hosts/shares", as the former description is only applicable to SMB1/NetBIOS samba environments (long since deprecated). By contrast, Dolphin (using KIO/WS-Discovery) is able to enumerate and show available shares on the same host without issue....
-
Smb4K 4.0.4 released
-
-
-
-
-
Smb4K 4.0.3
-
-
Smb4K 4.0.2 released
-
-
-
Smb4K 4.0.2 released
-
-
-
Smb4K 4.0.1 released
-
-
Smb4K 4.0.1 released
-
-
James posted a comment on discussion Help
I know this is a really late reply, but I just checked my samba version and it is 4.15.13-Ubuntu . I should be upgrading the OS on all my servers this year and will try to post back with results when I do.
-
Smb4K 4.0.0 released
-
Smb4K 4.0.0 released
-
-
-
Home
-
Release date of Smb4K 4.0
-
Release date of Smb4K 4.0
-
Smb4K 4.0 rc3 (3.2.92) released
-
Smb4K 4.0 rc3 (3.2.92) released
-
-
-
Smb4K 4.0 rc2 (3.2.91) released
-
Thank you for reporting this. To be able to reproduce this, I have got a comprehension question: You connect via xrdp to your virtual machine that runs Kubuntu and want to mount a share on that VM. Correct?
-
Thnak you for reporting this. To be able to reproduce this, I have got a comprehension question: You connect via xrdp to your virtual machine that runs Kubuntu and want to mount a share on that VM. Correct?
-
This is a not a standard setup so I'm not sure where to post this question. I figured I'd start here. I have an LXD virtual machine with Kubuntu 24.04.1 installed which I am not able to mount shares on when I am connected through xrdp. The dialog to enter the username and password never displays. When I click the bookmark of the share it simply displays Mounting... and then Done. in the bottom left of the window. I am using the KDE Wallet to store credentials and the prompt for the wallet works fine....
-
Smb4K 4.0 rc (3.2.90) released
-
-
Smb4K 4.0 beta2 (3.2.81) released
-
Smb4K 4.0beta2 (3.2.81) released
-
-
Home
-
Home
-
Home
-
Home
-
-
Smb4K 4.0 beta1 (3.2.80) released
-
Martin Krischik posted a comment on discussion Help
I see. It was just the servername. Which is a valid reply for the the German word "Ort". I was also wondering why only entering the the ip address is not enough. Now I understand: the dialog can't enumerate the shares of a server which I expected it to do when only a server name or ip address is entered.
-
The OK button is enabled when the location ("Ort") was set. However, it needs to have one of the following formats: //[USER@]SERVER/SHARE \\[USER@]SERVER\SHARE [smb:]//[user@]server[:port]/share The sequences in square brackets can be omitted. If you entered the location in such a format, I would be interested in how the format of the string you entered looks like (maybe there is a bug in the code then).
-
The OK button is enabled when the location ("Ort") was set. However, it needs to have one of the following format: //[USER@]SERVER/SHARE \\[USER@]SERVER\SHARE [smb:]//[user@]server[:port]/share The sequences in square brackets can be omitted. If you entered the location in such a format, I would be interested in how the format of the string you entered looks like (maybe there is a bug in the code then).
-
I filled everything in but the OK button is still not enabled. See Screenshot. What is the problem? This is a horrible user experience as there is no indication what is needed.
-
I filled everything in but the OK button is still not enabled. See Screenshot. What is the problem?
-
-
Smb4K 4.0 alpha3 (3.2.72) released
-
Smb4K 4.0 alpha2 (3.2.71) released
-
-
That custom settings are made for new shares is a shortcoming. I should fix this.
-
Thank you for the link. For Samba versions prior 4.20.0, this means, I guess, you should better use SMB protocol version 2.1 for mounting. However, I read through the release notes of Samba 4.20.0 and found that there is a new per share setting: smb3 unix extensions = yes | no I set it for a test share to "yes" and now everything works again out of the box with SMB protocol version 3.1.1 and enabled "All or most of the servers support the CIFS Unix extensions" setting. Can you please confirm thi...
-
For future reference the unix extensions do not work with smb3. I found an old thread (https://lists.samba.org/archive/samba/2017-October/211517.html) that states this fact. I'm guessing they have not implemented it yet.
-
I just tested again and found that a custom settings were made for the share. When I deleted them it works as expected. I wasn't aware that custom setting are made by default for new shares. Thanks for your help. I will now begin to figure out why the Unix extensions are not working for me.
-
I have the same problem that the shares are mounted as root. So, this seems to be a Samba issue. Unchecking the "All or most of the servers support the CIFS Unix extensions" setting on the "Mounting" configuration page and, thus, setting the UID and GID fixed the problem for me. If this does not work for you, please check, if there are custom settings defined for the share.
-
I tested by mounting manually using the command: sudo mount.smb3 //servername/share /home/username/smb4k/servername/share -o uid=1000,gid=1000,username=user,password=pass and the permissions were set to my user and group. None of the options in the mount section of SMB4K settings are working. User ID, Group ID under common mount settings and definitely assign the UID, definitely assign the GID always set the mounted directory permissions to root.
-
Recently SMB4K is setting the user and group to root on the mounted directory. I no longer have permission to view files. I have configured the User ID and Group ID to my user in the common mount settings but this makes no difference. Before Kubuntu 23.10 I did not have this problem. Do I need to change some settings?
-
Smb4K 4.0.0 will be Qt6 / KF6 only
-
Smb4K 4.0.0 will be Qt6 / KF 6 only
-
Home
-
Smb4K 4.0.0 alpha (3.2.70) released
-
Smb4K 4.0.0 alpha (3.2.70) released
-
Smb4K 4.0.0 alpha (3.2.70) released
-
-
Thank you for the feedback. Obviously, I forgot to set the tag. Sorry! I will do that now.
-
Sérgio M. Basto modified a comment on a blog post
no tag available on https://invent.kde.org/network/smb4k/-/tags , I want use packit on Fedora , but packit AFAIK just uses git repository and tags
-
no tag avaliable on https://invent.kde.org/network/smb4k/-/tags , I wnat use packit on Fedora , but packit AFAIK just uses git repository and tags
-
-
-
Smb4K 3.2.5 released
-
Pamela Whitfield posted a comment on discussion Help
Looks like that fixed it! Thanks Pam On Fri, Nov 10, 2023 at 1:00 PM Alexander Reinholdt areinholdt@users.sourceforge.net wrote: I could reproduce the problem with my Debian 12 installation. I am quite puzzled why this is, because the signing key is supposed to be valid until 2026... I triggered a new build of the packages, but could not test afterwards if that fixed the problem. Can you please check? repo signing key problem https://sourceforge.net/p/smb4k/discussion/help/thread/067b0c0fe8/?limit=25#12e4...
-
I could reproduce the problem with my Debian 12 installation. I am quite puzzled why this is, because the signing key is supposed to be valid until 2026... I triggered a new build of the packages, but could not test afterwards due to time constraints if that fixed the problem. Can you please check?
1 >
