** Description changed:

  Binary package hint: hal
  
  Installed Jaunty yesterday.  AMD 64 dual core.  Experienced several
  freezes with applications attempting file dialogs.
  
  This morning, found one cause.  An application had finished an operation
  on a USB mass storage device, which I then removed from the system.
  Subsequent attempts with other applications to use file dialogs caused
  applications to freeze.  System Monitor showed that hald was occupying
- virtually 100% of the CPU on one core.  Use of the other core allowed
- other applications and the desktop to continue limited operation.
+ virtually 100% of the CPU on one core.
+ 
+ Monitor shows many dozen instances of
+ 
+ hal-storage-unmount   Sleeping  ....  884.0 KiB  flock_lock_file_wait
+ 
+ Use of the other core allowed other applications and the desktop to
+ continue limited operation.
  
  On inspection of logs:
  
  ------------------------------------------------------------------------------
  kern log, many instances of:
  Apr 25 10:30:46 mikehome kernel: [ 2982.467307] FAT: Directory bread(block 
8216) failed
  
  ------------------------------------------------------------------------------
  daemon.log, many instances of 
  
  Apr 25 11:07:27 mikehome last message repeated 2080 times
  
  (with different counts) following a message:
  
  Apr 25 10:30:41 mikehome hald[2850]: forcibly attempting to lazy unmount
  /dev/sdc as enclosing drive was disconnected
  
  ------------------------------------------------------------------------------
  syslog: combination of the two.
  ------------------------------------------------------------------------------
  
  This continued even after the application(s)  which had connected to the
  USB device were closed.
  
  Nautilus may be involved. (ver 2.26.2) - on restarting Nautilus, the USB
  device mount points were visible in the navigation bar with "Unmount" as
  a right-click option. Attempting to unmount these gave an error dialog
  "Unable to mount..." with the message:  "DBus error
  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."

-- 
hald loads a core 100% attempting lazy unmount
https://bugs.launchpad.net/bugs/366660
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to