Bug 228787 - dolphin freezes and can't be launched anymore when nfs hangs
Summary: dolphin freezes and can't be launched anymore when nfs hangs
Status: RESOLVED DUPLICATE of bug 256291
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.3
Platform: Mandriva RPMs Unspecified
: NOR normal
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 236463 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-02-27 18:11 UTC by Balcaen John
Modified: 2011-12-03 11:47 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
.xsession logs (24.88 KB, application/octet-stream)
2010-02-27 18:12 UTC, Balcaen John
Details
dmesg if it can be useful (37.72 KB, text/plain)
2010-02-27 18:14 UTC, Balcaen John
Details
oops notice on the qnap part making nfs not available anymore (4.50 KB, text/plain)
2010-02-27 18:15 UTC, Balcaen John
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Balcaen John 2010-02-27 18:11:11 UTC
Version:            (using KDE 4.3.5)
Installed from:    Mandriva RPMs

I've noticed a « bug » with kde 4.3.5 when i'm using an nfs server is not available anymore.
I can reproduced it everytime:
1) get a Qnap TS-210 , format the disk on ext4 & export a folder via nfs on your computer
2) stress the qnap using rsync to backup for example your home (here i'm using backintime )
3) the stress is going to make the qnap kernel to oops due to ext4 (according to the dmesg i read and the fact that switching to ext3 does not provide any more oops)
4) plasma-desktop is going to freeze 
i'm there not able to attach to it via gdb neither i'm able to launch dolphin anymore
if a dolphin's session was arlready running it's going to freeze too , on ps the process are in 'D' state but i'm able to kill them via kill -9.
i'm just not able to restart them again even if i umount the nfs share .

I need to restart the kde session (well the whole X session via CTRL+ALT+SUPPR) to get it work again.
Comment 1 Balcaen John 2010-02-27 18:12:13 UTC
Created attachment 41169 [details]
.xsession logs

the xsession-errors
Comment 2 Balcaen John 2010-02-27 18:13:10 UTC
I don't have another nfs server which i could « unplugged » to reproduce the issue without the Qnap but i guess it's relative to this
Comment 3 Balcaen John 2010-02-27 18:14:09 UTC
Created attachment 41170 [details]
dmesg if it can be useful
Comment 4 Balcaen John 2010-02-27 18:15:00 UTC
Created attachment 41171 [details]
oops notice on the qnap part making nfs not available anymore
Comment 5 Etienne Lepercq 2010-03-03 16:14:39 UTC
I have a small NAS running linux, with NFS exports (ext3). They are mounted on /media/* (two exports)
I am using mandriva 2010, KDE4.3 up to date (using my distribution packages).

I tried to copy a big file (8GiB) from the NAS to my desktop. While downloading, login to the NAS and /etc/init.d/nfs-kernel-server stop
 * The copy pauses (normal)
 * Nothing freezes
 * Dolphin can't be opened anymore. Loading cursor appears, but disappears after a while.
Here is what happens in console :

glurb@xglurb:~$ dolphin
<unknown program name>(29556)/: Communication problem with  "dolphin" , it probably crashed.
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." "

Then, starting the NFS export (on NAS) and remounting them make dolphin loading, everything restarts (even the copy).

Seems related, but not AS bad as what is described in the first post (but I am not using KDE 4.4)

Please ask anything for more information, as it is fairly easy to reproduce.
Comment 6 Ruediger Meier 2011-04-05 17:52:08 UTC
seems to be duplicate of #158606
Comment 7 Matteo Agostinelli 2011-12-01 19:00:08 UTC
*** Bug 236463 has been marked as a duplicate of this bug. ***
Comment 8 Aaron J. Seigo 2011-12-03 11:47:48 UTC

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