Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#8415 - hal does not remove devices completely

Attached to Project: Arch Linux
Opened by Erwin Van de Velde (evdvelde) - Thursday, 25 October 2007, 14:51 GMT
Last edited by Jan de Groot (JGC) - Friday, 09 May 2008, 12:37 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity High
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
when attaching a USB device to your computer (e.g. USB keyboard), it is detected by hal. When you remove the USB device, the device is not completely removed from hal:
lshal still shows an entry with the info.udi = '/org/freedesktop/Hal/devices/usb_device_[...]' where [...] contains the device id.

This causes problems when removing a device and adding a device of the same type to the same USB port (properties of the first device are kept, e.g. MAC addresses of sensor devices).

Additional info:
* package version(s)
kernel26 2.6.23.1-4 and also tested with 2.6.22.9
hal 0.5.9.1-1
Architectures: i686 and x86_64

Steps to reproduce:
Add USB device, check lshal output
Remove USB device, check lshal output
This task depends upon

Closed by  Jan de Groot (JGC)
Friday, 09 May 2008, 12:37 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in 0.5.11rc2
Comment by João Rodrigues (gothicknight) - Friday, 29 February 2008, 09:43 GMT
I can confirm this. Although I cannot say that this is a bug.


Evidences:

[jprodrigues@archBOX ~]$ lshal -st > List.begin
[jprodrigues@archBOX ~]$ lshal -st > List.end
[jprodrigues@archBOX ~]$ diff List.begin List.end
79a80,87
> usb_device_930_653d_0E50336123A33961
> usb_device_930_653d_0E50336123A33961_usbraw
> usb_device_930_653d_0E50336123A33961_if0
> usb_device_930_653d_0E50336123A33961_if0_scsi_host
> usb_device_930_653d_0E50336123A33961_if0_scsi_host_scsi_device_lun0
> storage_serial_0930_USB_Flash_Memory_0E50336123A33961_0_0
> volume_uuid_7806_0982
> usb_device_930_653d_0E50336123A33961_if0_scsi_host_scsi_device_lun0_scsi_generic
[jprodrigues@archBOX ~]$ lshal -st > List.afterremove
[jprodrigues@archBOX ~]$ diff List.begin List.afterremove
79a80
> usb_device_930_653d_0E50336123A33961
Comment by Erwin Van de Velde (evdvelde) - Friday, 29 February 2008, 11:42 GMT
Please read this in the original post:
This causes problems when removing a device and adding a device of the same type to the same USB port (properties of the first device are kept, e.g. MAC addresses of sensor devices).

This is a major problem when working with several devices of the same type, connecting one at the time.
Comment by Jan de Groot (JGC) - Friday, 09 May 2008, 12:19 GMT
Is this still an issue with 0.5.11rc2?
Comment by Erwin Van de Velde (evdvelde) - Friday, 09 May 2008, 12:30 GMT
The issue seems to be fixed.. thanks for the follow-up!

Loading...