Your message dated Sun, 14 May 2006 11:33:48 +0200
with message-id <[EMAIL PROTECTED]>
and subject line konqueror: kio_file : apparent hang when opening HOME directory
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: konqueror
Version: 4:3.1.5-2
Severity: normal
For some reason konqueror tries to read not only the directory you have
clicked on (here HOME) but also tries to access some 'previous' files (stored
somewhere in .kde directory).
Some of these files MIGHT be of a remote filesystem (e.g NFS mounted).
When you use the automounter, accessing (or statting ?) those files causes the
automouter to try to mount these filesystems (which could of course be down).
After the timeout of the mount command, for some reason, kio_file tries to
reread the same file (some retry count somewhere ?).
Together with the timeout of the mount and this retry count, makes the
kio_file/konqueror window hang for a VERY long time making it seem like a
ghost window (one that does not repeat).
I have noticed that kmail has similar behavior when trying to attach a file
and when the recent file list of kmail contains a remote file. However here
the retry count is smaller (not existant) so the timeout is just annoying.
How am I sure that it is kde ?
I straced the mount command (which locks on the connect to the remote mountd),
I traced the autofs which basically returns an error and returns the forked
autofs process taking care of that mount request.
I also straced the kio_file which, when mount is killed simulating an error,
does something and a new mount request appears. So it must be kio_file that
tries to reread the same file
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.2-rc1ii libfreetype6 2.1.7-2 FreeType 2
font engine, shared lib
ii libgcc1 1:3.3.3-1 GCC support library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libkonq4 4:3.1.5-2 Core libraries for KDE's file
mana
di libpcre3 4.3-4 Philip Hazel's Perl 5 Compatible
R
ii libpng12-0 1.2.5.0-5 PNG library - runtime
ii libqt3c102-mt 3:3.2.3-2 Qt GUI Library (Threaded runtime
v
ii libstdc++5 1:3.3.3-1 The GNU Standard C++ Library v3
ii libxcursor1 1.0.2-4 X Cursor management library
ii libxft2 2.1.2-5 FreeType-based font drawing
librar
ii libxrender1 0.8.3-5 X Rendering Extension client
libra
hi xlibmesa3-gl [libgl1] 4.2.1-10 Mesa 3D graphics library
[XFree86]
hi xlibs 4.2.1-10 X Window System client libraries
ii zlib1g 1:1.2.1-4 compression library - runtime
-- no debconf information
Locale: LANG=C, LC_CTYPE=C
Versions of packages konqueror depends on:
ii kate 4:3.1.5-2 KDE Advanced Text Editor
ii kcontrol 4:3.1.5-2 KDE Control Center
ii kdelibs4 4:3.1.5-1 KDE core libraries
ii kdesktop 4:3.1.5-2 KDE Desktop
ii kfind 4:3.1.5-2 KDE File Find Utility
ii libart-2.0-2 2.3.16-1 Library of functions for 2D
graphi
ii libaudio2 1.6c-1 The Network Audio System (NAS).
(s
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries
an
ii libfam0c102 2.7.0-5 client library to control the FAM
ii libfontconfig1 2.2.1-16 generic font configuration
library
--- End Message ---
--- Begin Message ---
konqueror obviously needs to read its configuration files that are
under .kde
there is nothing that you can do against it, as it's *normal*. it's
not a bug at all.
I also strongly advise to avoid the use of automounter for $HOME,
automount is *not* efficient, and worse, it's not reliable.
On Sat, Feb 28, 2004 at 02:39:56PM +0100, wim delvaux wrote:
> Package: konqueror
> Version: 4:3.1.5-2
> Severity: normal
>
> For some reason konqueror tries to read not only the directory you have
> clicked on (here HOME) but also tries to access some 'previous' files (stored
> somewhere in .kde directory).
>
> Some of these files MIGHT be of a remote filesystem (e.g NFS mounted).
>
> When you use the automounter, accessing (or statting ?) those files causes
> the
> automouter to try to mount these filesystems (which could of course be down).
>
> After the timeout of the mount command, for some reason, kio_file tries to
> reread the same file (some retry count somewhere ?).
>
> Together with the timeout of the mount and this retry count, makes the
> kio_file/konqueror window hang for a VERY long time making it seem like a
> ghost window (one that does not repeat).
>
> I have noticed that kmail has similar behavior when trying to attach a file
> and when the recent file list of kmail contains a remote file. However here
> the retry count is smaller (not existant) so the timeout is just annoying.
>
> How am I sure that it is kde ?
>
> I straced the mount command (which locks on the connect to the remote
> mountd),
> I traced the autofs which basically returns an error and returns the forked
> autofs process taking care of that mount request.
> I also straced the kio_file which, when mount is killed simulating an error,
> does something and a new mount request appears. So it must be kio_file that
> tries to reread the same file
--
·O· Pierre Habouzit
··O [EMAIL PROTECTED]
OOO http://www.madism.org
signature.asc
Description: Digital signature
--- End Message ---
