Mailinglist Archive: opensuse-bugs (12871 mails)

< Previous Next >
[Bug 462639] access permissions for scsi scanners missing
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 23 Jan 2009 13:56:45 -0700 (MST)
  • Message-id: <20090123205645.C533BCC7CD@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=462639

User dkukawka@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=462639#c44





--- Comment #44 from Danny Kukawka <dkukawka@xxxxxxxxxx> 2009-01-23 13:56:41
MST ---
(In reply to comment #38)
Strange!

According to comment #35 the udi
/org/freedesktop/Hal/devices/pci_1000_1_scsi_host_scsi_device_lun0
does not have a capability "scanner" but then according
to comment #37 hal-find-by-capability reports a similar udi
/org/freedesktop/Hal/devices/pci_1000_1_scsi_host_scsi_device_lun0_scsi_generic
as a "scanner" which then of course lets YaST
think that HAL knows that this device is a "scanner"
so that there is no need to write 80-scanner.fdi for it.

For me this looks now like an issue in HAL.

I don't think this is caused by hal. There is only one way to mark a scsi
device as scanner: via this rule (which don't apply to this device AFAICS):

<deviceinfo version="0.2">
<device>
<match key="info.category" string="scsi_generic">
<match key="@info.parent:scsi.type" string="scanner">
<append key="info.capabilities" type="strlist">scanner</append>
</match>
</match>
</device>
</deviceinfo>

Maybe you should request a tar archive from /usr/share/hal/fdi and /etc/hal/fdi
and check all fdi files to see whats going wrong.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >