[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Iinitial automounting by lenny/kde very slow after each X/kde-session start.



  Hello debian-kde list,

This problem occurs since a few months with KDE, but NOT with GNOME.

The system is debian/lenny on a dual core Intel PC where we normally use KDE.
Inserting a usbstick for the FIRST TIME after logging in to KDE via kdm or gdm results
in a delay of about TEN minutes before the kde-mount-screen appears!
Then everything works OK. All next inserts work normal.

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.

Please find below some debugging information, where the most informative is that the
10 minute delay seems to start AFTER a "hal-probe-storage", see hald logging info below.

Can anyone point me in a direction? I would be most grateful.
I already tried the debian-user list, but to no avail.

Here 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'.

Here output from lshal --monitor
================================

Start monitoring devicelist:
-------------------------------------------------
10:35:40.519: usb_device_781_7108_00000000000000046315 added
10:35:40.552: usb_device_781_7108_00000000000000046315_usbraw added
10:35:40.573: usb_device_781_7108_00000000000000046315_if0 added
10:35:40.577: usb_device_781_7108_00000000000000046315_if0_scsi_host added
10:35:45.552: usb_device_781_7108_00000000000000046315_if0_scsi_host_0 added
10:35:45.553: usb_device_781_7108_00000000000000046315_if0_scsi_host_0_scsi_device_lun0 added
10:35:45.566: usb_device_781_7108_00000000000000046315_if0_scsi_host_0_scsi_device_lun0_scsi_generic added
10:35:46.947: volume_uuid_76DE_0888 added
10:35:47.140: storage_serial_SanDisk_Cruzer_Titanium_00000000000000046315_0_0 added
10:35:47.140: storage_serial_SanDisk_Cruzer_Titanium_00000000000000046315_0_0 property info.interfaces = {'org.freedesktop.Hal.Device.Storage.Removable'} (new)

+++++++ here the 10 minute wait.

10:47:43.754: volume_uuid_76DE_0888 property volume.mount_point = '/media/disk'
10:47:43.755: volume_uuid_76DE_0888 property volume.is_mounted = true


Here 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

+++++++ here the 10 minute wait.


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

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

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


Reply to: