An initial automounting by kde very slow after each X/kde-session start.

[Sietse Achterop <s.achterop@rug.nl>]

  Hello List,

This problem occurs since a few months, and I'm struggling to solve it.

The system is debian/lenny (kde/kdm) on a dual core Intel PC.
Inserting a usbstick for the FIRST TIME after logging in via kdm results
in a delay of about 10 minutes before the kde-mount-screen appears!
Then everything works OK. All next inserts work normal.
   (I regrettably have to restart the X-server on each logout, so
    with each login the X-server is also reset. So maybe the 10 minute delay
    is triggered by the X-server reset. But how?)

The devices are always directly created upon insertion (here /dev/sdb1),
and pmount can be used directly. There never is any warning or error to be found.

Here some debugging info from hald

OUTPUT from hald from /var/log/daemon.log:
==========================================
     .........
Aug 19 13:13:44 wingtip84 hald[5386]: 13:13:44.224 [I] blockdev.c:1622: hald-probe-storage --only-check-for-media returned 0 (exit_type=0)
Aug 19 13:22:39 wingtip84 hald[5386]: 13:22:39.186 [I] hald_dbus.c:5127: OK for method 'Mount' with signature 'ssas' on interface 'org.freedesktop.Hal.Device.Volume' for
UDI '/org/freedesktop/Hal/devices/volume_uuid_76DE_0888' and execpath 'hal-storage-mount'
     .........
======

Note the 10 minute delay between the hald-probe-storage and the "OK for method 'Mount'.


OUTPUT from hald in nodeamon and verbose mode (different attempt):
=============================================
     ........
!  full path is '/usr/lib/hal/hald-probe-volume', program_dir is '/usr/lib/hal'
pid 5476: rc=0 signaled=0: /usr/lib/hal/hald-probe-volume
Run started hald-probe-storage (10000) (0)
!  full path is '/usr/lib/hal/hald-probe-storage', program_dir is '/usr/lib/hal'
woohoo
pid 5485: rc=0 signaled=0: /usr/lib/hal/hald-probe-storage

+++++++
+++++++

Run started hal-storage-mount (0) (1)
!  full path is '/usr/lib/hal/hal-storage-mount', program_dir is '/usr/lib/hal'
5657: XYA attempting to get lock on /media/.hal-mtab-lock
5657: XYA got lock on /media/.hal-mtab-lock
device                           = /dev/sdb1
invoked by uid                   = 502
invoked by system bus connection = :1.36
 label ''  uuid '76DE-0888'
Looking at /etc/fstab entry '/dev/sda7'
/etc/fstab: device /dev/sda7 -> /dev/sda7

     ........
=======

The ++++++' stands for the 10 minutes of silence ....
And after that silence the screen appears.

Can anyone point me in the right direction?
Again note that there never is any warning or error to be found.
How could the 10 minute delay be triggered?
Is it an udev-rule problem?
  (at some point I had package dmsetup (devicemapper setup) installed and after
   fiddling with its udev-rules it seemed to work (once).
   Now dmsetup is not installed anymore)

   Thanks in advance.
     Sietse Achterop