Bug 153091 - A lot of KDE applications freezes for few minutes, in many situations, when there is an error on a samba mounting.
Summary: A lot of KDE applications freezes for few minutes, in many situations, when t...
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords: investigated, needs_verification, triaged
Depends on:
Blocks:
 
Reported: 2007-11-28 21:11 UTC by Amund Sjaavaag
Modified: 2018-10-21 04:28 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amund Sjaavaag 2007-11-28 21:11:41 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Mandriva RPMs
OS:                Linux

I have mounted /home/amuns/h to a windows server. If there is any error on this mount, it triggers some serious problems with KDE.

If i open a composer window in kmail, or a new window in konqueror, the application freezes for few minutes. Then they respond again, and do the task it should do.
The same freeze happens, when i go to menus and dialogs to attach files or print, etc.

None of theese applications are using any files under the mounted samba share, and they should have no excuse to freeze.

If i run df, it list most of the mounted systems at once, then it waits a long time, before it shows info about /home/amuns/h:
# df
Filesystem            Size  Used Avail Use% Mounted on
/dev/hdb3             9,7G  5,8G  3,4G  64% /
/dev/hdb6             121G   91G   24G  80% /mnt/hd
/dev/hda1             8,8G  6,9G  2,0G  79% /c
/dev/hda6              12G  6,3G  4,9G  57% /home
/dev/hdb5              12G   77M   12G   1% /media/hd
/dev/hda8             8,2G   33M  8,1G   1% /media/hd2
/dev/hda5             7,2G  5,9G  883M  88% /oldroot
df: `/home/amuns/h': Input/output error

In /var/log/messages, i find messages like this:

Nov 28 20:35:32 freedom kernel: smb_add_request: request [d0b1ee80, mid=10014] timed out!
Nov 28 20:35:32 freedom kernel: smb_lookup: find //bin failed, error=-5
Nov 28 20:36:02 freedom kernel: smb_add_request: request [d0b1ee80, mid=10015] timed out!
Nov 28 20:36:02 freedom kernel: smb_lookup: find //bin failed, error=-5
Nov 28 20:36:32 freedom kernel: smb_add_request: request [d0b1ee80, mid=10016] timed out!
Nov 28 20:36:32 freedom kernel: smb_lookup: find //bin failed, error=-5
Nov 28 20:37:02 freedom kernel: smb_add_request: request [d0b1ee80, mid=10017] timed out!
Nov 28 20:37:02 freedom kernel: smb_lookup: find //bin failed, error=-5
Nov 28 20:37:32 freedom kernel: smb_add_request: request [d0b1ee80, mid=10018] timed out!
Nov 28 20:37:32 freedom kernel: smb_lookup: find //bin failed, error=-5
Nov 28 20:38:02 freedom kernel: smb_add_request: request [d0b1ee80, mid=10019] timed out!
Comment 1 FiNeX 2008-11-24 15:40:49 UTC
Can you explain how I can reproduce a similar error on mounting remote shares? I want to test it using new software version.
Comment 2 Dario Andres 2009-04-03 00:31:16 UTC
Marking as NEEDSINFO
Comment 3 Andrew Crouthamel 2018-09-19 04:26:39 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Andrew Crouthamel 2018-10-21 04:28:48 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!