You are not logged in.
Hey everybody,
The KDE doesn't recognize samba as being installed. I can still browse SMB shares but cannot share folders/files myself. Under the "Share" tab properties of the folder I want to share a message exclaims: "Samba is not installed on your system.". I have samba and kdenetwork-filesharing installed. I've removed my /etc/samba/smb.conf file and replaced it with the default config that comes with installing Samba. Does anyone know what could be the problem?
My second problem is in KDE's NetworkManager and connecting an ethernet NAS device. I need to access the device locally, normally this would be through the link-local method of setting up wired connections, which no longer works for any device I use it with. Absolutely no errors are thrown out in logs (journalctl/dmesg/etc) or launching networkmanager from the terminal. When it attempts to connect to the device it immediately disconnects without error or message. I have no clue what would be the issue.
Thank you for reading.
Last edited by awbs (2013-06-04 02:42:48)
Offline
Run testparm to see if you have any shares set up in you configuration file, and make sure that you have added yourself as a samba user with pdbedit -a -u <user> as root. https://wiki.archlinux.org/index.php/Samba
Can you connect to the web interface of the NAS device?
Andrew
Offline
The default shares in smb.conf are setup, a user account is also setup up through pdbedit, e.g. Samba is set up correctly but I cannot share folder's through KDE's Share interface, is says Samba isn't installed. I can connect to the NAS interface through my router but not through my computer's ethernet direct connection to it, which I used to be able to do by selecting the wired connection's method of link-local in NetworkManager. Now it just immediately disconnects when it attempts to connect without error.
Last edited by awbs (2013-05-31 19:15:58)
Offline
Hello, first poster here. I ran into this problem myself today.
I did some Googling and I stumbled upon this file: http://woldlab.caltech.edu/~diane/kde4. … plugin.cpp
This is a C++ source file from KDE 4.10.
If you search for "Samba is not installed on your system." in that text, you'll find that a label with that quote is being created when /usr/sbin/smbd or /usr/local/sbin/smbd cannot be found.
Running
pacman -Ql samba | grep smbd
shows that smbd is located at /usr/bin/smbd.
My hotfix was to create a symbolic link:
$ ln -s /usr/bin/smbd /usr/sbin/smbd
This works for me, but is not the optimal solution. How can we report this and to whom?
Last edited by SleekoNiko (2013-05-31 22:52:31)
Offline
Hello, first poster here. I ran into this problem myself today.
I did some Googling and I stumbled upon this file: http://woldlab.caltech.edu/~diane/kde4. … plugin.cpp
This is a C++ source file from KDE 4.10.If you search for "Samba is not installed on your system." in that text, you'll find that a label with that quote is being created when /usr/sbin/smbd or /usr/local/sbin/smbd cannot be found.
Running
pacman -Ql samba | grep smbd
shows that smbd is located at /usr/bin/smbd.
My hotfix was to create a symbolic link:
$ ln -s /usr/bin/smbd /usr/sbin/smbd
This works for me, but is not the optimal solution. How can we report this and to whom?
I tried looking into the source code too but never found that! Thanks. It seems like a KDE bug but maybe Samba is installed in a different location than most linux distros?
Offline
Using
sudo systemctl status NetworkManager
after plugging in the NAS gives this:
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> (eth0): device state change: config -> ip-config (reason 'none') [50 70 0]
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <warn> Activation (eth0) Stage 3 of 5 (IP Configure Start) failed to start avahi-autoipd: not found
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> (eth0): device state change: ip-config -> failed (reason 'autoip-start-failed') [70 120 20]
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> Marking connection 'MyBookLive' invalid.
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <warn> Activation (eth0) failed for connection 'MyBookLive'
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> (eth0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Jun 01 14:38:54 Arch_Alienware NetworkManager[426]: <info> (eth0): deactivating device (reason 'none') [0]
I'll be searching Google.
<warn> Activation (eth0) Stage 3 of 5 (IP Configure Start) failed to start avahi-autoipd: not found
Seems to be the most relevant line. Running 'avahi-autoipd eth0' gives this:
Found user 'avahi' (UID 84) and group 'avahi' (GID 84).
Successfully called chroot().
Successfully dropped root privileges.
Starting with address 169.254.194.24
Callout BIND, address 169.254.194.24 on interface eth0
Successfully claimed IP address 169.254.194.24
Although it seems I can't do anything with the IP address it gives me.
---
Edit: Choosing the 'Shared' network connection method through NetworkManager for the NAS did what link-local used to do, I can now access my NAS using this connection method.
Last edited by awbs (2013-06-01 21:28:56)
Offline
Today's upgrade (usr-move) fixes this problem. Symlinking is no longer necessary.
Regards.
Last edited by adorableGNU (2013-06-03 14:10:27)
Offline