Registered Member
|
Hi,
I have 2 cifs servers in my network, one qnap nas server and an acryan dvr player. the shares are configured in /etc/fstab and are mounted in a sub directory in my home directory. The shares appear in the side bar of dolphin. All that works fine, unless one of the servers is unavailable. For example, if i switch off the acryan dvr player while my laptop is on, dolphin freezes when entering my home directory. So does any file::open dialog from kde and even the shutdown area in the k-menu. The CLI works fine: if i do an ls in the directory where the shares are mounted, the shell gives an error after a few seconds and is usable again. I tried several settings in /etc/fstab, but they all have the same result. this is my last attempt:
Riinse, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
I would try mounting them outside of $HOME and check if these freezes still occur.
|
Registered Member
|
thanks for your reply
i tried that, but the same result. The GUI of dolphin stops responding as soon as the acryan is offline.
Riinse, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Does dolphin spit something on console?
|
Registered Member
|
Only what dolphin always prints on console, see below.
What i do notice is that when i start dolphin, the smb-server immediatly reacts on it (hard disk spin). So apperently, when starting dolphin, it tries to connect to the shares that are present in its side bar. Also, plasma freezes when i want to open the k-menu, so apperently, plasma too tries to connect to the shares defined in /etc/fstab when i open the menu.
Riinse, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
Riinse, proud to be a member of KDE forums since 2008-Oct.
|
Registered Member
|
I have exactly the same as you have/had. I got the tip to unmount the external connections before I shutdown those computers, or acryan in your case. Once done that, there is no problem anymore. It's just some extra work but it saves you from a lot of trouble.
The funny thing is, this used to work in Gnome 2 , when I skipped to KDE the trouble started. So, sudo umount shared-folder1 sudo umount shared-folder2 etc Since today I have a new error: Dolphin just stops responding altogether. The kick-off menu is open right now and stays open, I can't close it anymore. This when not using the network at all, all other computers are off and stay off. It really is time for the KDE guys to do something about this: I never had this trouble when using Gnome. I reported this bug but somehow I never receive any news about it, it seems to me nobody is working on it. This makes KDE a real big disappointment. Yes, it looks great, but watching a opened Kickoff menu for half an hour is not what I want. |
Registered Member
|
You could help to find more info for https://bugs.kde.org/show_bug.cgi?id=184062
|
Registered Member
|
I just filed another complaint about this bug which is as old as KDE is, so it seems. No idea why nobody is working on this. It sure is a pain in the b*t. |
Administrator
|
This issue only occurs when you mount shares at the kernel level, through /etc/fstab (or manually with the mount command). This "hang" behaviour comes from the Linux Kernel itself, and is not under the control of KDE at all. Filing bugs against KDE for hanging when a network share is down will not get the issue corrected as you are reporting issues to the wrong place.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
I don't know if you are right about that. I didn't have these issues when I was still using Gnome as DE. Then I could do what I please with my computers, nothing was hanging when a mounted network drive would be switched of. That was my reason to look for help in the KDE forums and file a bug report there, as many others have done as well. |
KDE Developer
|
You could switch to using fusesmb instead.
fuse runs in userspace so it doesn't lock anything else up if it goes down. Usage: "fusesmb -s /destination/mount/point" This will "mount" the entire worgroup, so you may want to add symlinks to the right places. |
Registered users: Bing [Bot], Google [Bot], Yahoo [Bot]