https://bugzilla.novell.com/show_bug.cgi?id=462639 User weigelt.bernd@web.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c2 Bernd Weigelt changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |weigelt.bernd@web.de --- Comment #2 from Bernd Weigelt 2008-12-28 04:00:54 MST --- I have a similar problem with my EPSON 1670 USB-Scanner, it is only usable as root. For cdburning i have to add the users to the group disk. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c4 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com Status|NEEDINFO |NEW Info Provider|kasievers@novell.com | --- Comment #4 from Kay Sievers 2008-12-29 10:24:08 MST --- (In reply to comment #0 from Dieter Jurzitza)

When installing a scsi-scanner in openSUSE 11.1, a regular user cannot access it. The corresponding udev-rule as existed in openSUSE 10.3 (for example) is not present in openSUSE 11.1:

50-udev-default.rules: # misc storage devices (non-block) KERNEL=="sg*", GROUP="disk", MODE="0640"

Scsi-generic devices of type "scanner" and "processor" intentionally do no get the group "disk" assigned, because they are not related to "storage". Anyway, no normal user should ever be in the "disk" group, it would allow the untrusted user to do things like format any disk on the system. (In reply to comment #3 from Marcus Meissner)

As for this problem, I am not sure our current HAL/udev setup can detect scanners reliably and make them available.

There is support in HAL for many USB scanners in fdi files. They match on vendor/product ids. In the fdi files is also support for SCSI scanners. It is expected to work, but I don't really know if it works reliably. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c6 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|udev rules for setting access permissions for |access permissions for scsi scanners missing |scsi scanners missing | --- Comment #6 from Kay Sievers 2008-12-29 11:59:08 MST --- (In reply to comment #5 from Dieter Jurzitza)

well, the above listed udev-rule stems from 10.3 "as is", so this was a probably meaningful decision by openSUSE some time ago.

There are no openSUSE specific rules, they are part of the common udev rules, and most distros ship the same thing. The current rule logic should prevent the SCSI scanner to be in the "disk" group. It seems not to work for your scanner, it's probably not SCSI type "3" or "6". As said, the "disk" group should not be used for anything else than a "backup daemon" and similar, never for "normal" users.

From an user's standpoint (and from a maintainer's standpoint) it is bad if a regular user is simply kicked out of the usage of the scanner, what is, IMHO, > a very "normal" usecase, what I hope you can agree with.

It's not related to udev rules. Normal users should get an ACL at the device node, which is not managed by udev, or udev rules.

If I get your comment to Marcus Meissner correct, there should be support for SCSI-scanners in "the fdi-files". Can you be more specific which files are concerned so I could play around and try to figure out what is going wrong?

It's in: /usr/share/hal/fdi/information/20thirdparty/70-scanner.fdi -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c8 --- Comment #8 from Dieter Jurzitza 2009-01-07 04:00:45 MST --- Hi Ludwig, I am currently working on a implementation of this, exactly. The only thing that I'd like to get is information on other SCSI-scanners from HP because they apparently all announce themselves as "processor". I have a patch for sane-desc.c doing all this work automatically - and as soon as I have more of those device entries I'd provide the patch. The problem is that a scanner promotes itself as C7670A, whereas sane announces it as "HP 6350" or something similar, but I need the "C7670A" to settle the patch. If you guys at openSUSE have some old SCSI-scanners sitting around, I'd appreciate very much if you'd be capable to provide the output of scanimage -L (if the device announces itself as "processor". The problem is understood, thank you for the pointer, I am just trying to figure out some more names in this regard. Take care Dieter -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c11 --- Comment #11 from Johannes Meixner 2009-01-09 03:40:48 MST --- Danny, I have a question regarding your comment #10 (but like to keep the "needinfo" from Dieter): Currently (i.e. for openSUSE 11.1 and for SLE11) I have in /usr/share/hal/fdi/information/20thirdparty/70-scanner.fdi ----------------------------------------------------------------------- <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> ----------------------------------------------------------------------- Should I remove it and submit a changed sane-backends package for SLE11 or can I simply keep it because it won't cause problems? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c13 --- Comment #13 from Johannes Meixner 2009-01-09 06:14:50 MST --- I fully agree and I always appreciate it when generic stuff is readymade provided by HAL itself. Please inform me, when it is actually provided by HAL itself so that I can then remove it from my 70-scanner.fdi file. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c15 --- Comment #15 from Johannes Meixner 2009-01-09 07:20:43 MST --- /etc/hal/fdi/information/20thirdparty/80-scanner.fdi is created by the YaST scnner module which calls /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions which actually does the job, see what I wrote in comment #9. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c17 --- Comment #17 from Dieter Jurzitza 2009-01-11 13:00:27 MST --- Ok, now I've found the time to do the tests as requested in #9. Please find the results attached to this bugreport. Take care Dieter -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c19 --- Comment #19 from Dieter Jurzitza 2009-01-11 13:10:42 MST --- Created an attachment (id=264373) --> (https://bugzilla.novell.com/attachment.cgi?id=264373) Output of test_and_set_scanner_permissions > logit 2>&1 -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c21 --- Comment #21 from Dieter Jurzitza 2009-01-11 13:11:37 MST --- Created an attachment (id=264375) --> (https://bugzilla.novell.com/attachment.cgi?id=264375) 2nd temporary file generated by the script -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|dieter.jurzitza@t-online.de | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c24 --- Comment #24 from Dieter Jurzitza 2009-01-14 12:47:23 MST --- Created an attachment (id=265116) --> (https://bugzilla.novell.com/attachment.cgi?id=265116) SCSI-Scanner devicesupport for hal & co This patch integrates the latest feedback from Julien Blanche and makes this version of sane-backends-1.0.19 _very_ similar to the one from sane website. Basically a backport to sane-backends-1.0.19 with additional "opensuse" stuff. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c26 --- Comment #26 from Dieter Jurzitza 2009-01-14 12:50:14 MST --- Added the next release of patches for sane-backends integrating the latest patches from Julien Blanche into sane-desc.c. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c28 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |dkukawka@novell.com --- Comment #28 from Johannes Meixner 2009-01-20 01:20:44 MST --- I.e. you mean that the new hal package provides now both - a generic ACL rule for SCSI devices with SCSI type "scanner" and - tons of rules for all the USB scanners in 70-scanner.fdi Regarding the latter (USB scanner entries): As there is no generic USB device class for scanners, there cannot be a generic rule for USB scanners so that USB scanners must be listed one by one an this list must be maintained all the time. Such a list of USB scanners depends on the current versions of the scanner driver packages (which models are currently known and supported by a scanner driver package). Currently our scanner driver packages are sane-backends, hplip, iscan-free, and iscan. The 70-scanner.fdi file which I provide in sane-backends is made from driver description files of all our scanner driver packages. Therefore I have in the sane-backend sources the files - models.dat (driver description for the hpaio driver in hplip) - epkowa.desc (driver description for the epkowa driver in iscan*) I assume you won't like to update your hal package for each new version of a scanner driver package? Furthermore really unsupported models which are also listed in the driver description files must be specially excluded from the list, see bug #439193. Do you think that I should really remove 70-scanner.fdi completely from the sane-backends package? If yes, you alone (more precisely the hal package maintainer) would become responsible when there is no scanner device access for normal desktop users. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User swamp@suse.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c30 Swamp Script User changed: What |Removed |Added ---------------------------------------------------------------------------- Status Whiteboard|marked-ForNextOS11.1:HAL |marked-ForNextOS11.1:HAL | |maint:released:11.1:22089 --- Comment #30 from Swamp Script User 2009-01-21 17:51:15 MST --- Update released for: hal, hal-debuginfo, hal-debuginfo-32bit, hal-debuginfo-x86, hal-debugsource, hal-devel Products: openSUSE 11.1 (debug, i586, ppc, ppc64, x86_64) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c31 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |dieter.jurzitza@t-online.de --- Comment #31 from Johannes Meixner 2009-01-22 04:31:18 MST --- According to attachment #264373 in comment #19 the "scanner" capability is already known to HAL for this SCSI scanner so that everything should be already o.k. which is the reason why test_and_set_scanner_access_permissions does not create an entry for this SCSI scanner in 80-scanner.fdi Currently I do not understand why it does not work when the "scanner" capability is already known to HAL for this SCSI scanner or what lets test_and_set_scanner_access_permissions falsely assume that the "scanner" capability is already known to HAL for this SCSI scanner. Dieter, could you attach the output of lshal when this SCSI scanner is connected? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c33 --- Comment #33 from Johannes Meixner 2009-01-22 09:18:50 MST --- I know about the "processor" stuff, just have a look at /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions I implemented generic(!) code to handle just this case for all SCSI "processor"-scanners (and not only for a few known models via a hardcoded list). This had worked all the time in the past and in particular it had worked perfectly for me when I had implemented and tested it with such a SCSI "processor"-scanner (which I currently no longer have available). Here I do not understand why it does not work when the "scanner" capability is already known to HAL for your SCSI scanner regardless which SCSI type this SCSI scanner has. According to attachment #264373 HAL already knows that this SCSI device is a "scanner" but I wonder why because it is a SCSI "processor" so that HAL should not know it as a "scanner" so that my code should write an entry for it to 80-scanner.fdi but it doesn't because HAL already knows it as a "scanner". Dieter, could you therefore please attach the output of lshal when this SCSI scanner is connected so that I might understand what is actually wrong here so that I could hopefully find and fix the real root cause of the issue. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c36 --- Comment #36 from Johannes Meixner 2009-01-23 07:36:29 MST --- Axel Braun, what does the command hal-find-by-capability --capability scanner result for you and what is the content of your /etc/hal/fdi/information/20thirdparty/80-scanner.fdi file? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c37 Axel Braun changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|dieter.jurzitza@t-online.de | --- Comment #37 from Axel Braun 2009-01-23 07:50:52 MST --- northpole:~ # hal-find-by-capability --capability scanner /org/freedesktop/Hal/devices/pci_1000_1_scsi_host_scsi_device_lun0_scsi_generic northpole:~ # more /etc/hal/fdi/information/20thirdparty/80-scanner.fdi /etc/hal/fdi/information/20thirdparty/80-scanner.fdi: Datei oder Verzeichnis nicht gefunden -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c39 Axel Braun changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|dieter.jurzitza@t-online.de | --- Comment #39 from Axel Braun 2009-01-23 09:25:52 MST --- Created an attachment (id=267315) --> (https://bugzilla.novell.com/attachment.cgi?id=267315) output from lshal -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c41 --- Comment #41 from Dieter Jurzitza 2009-01-23 12:22:03 MST --- Hi folks, as promised: I'll do this on the weekend, so, here you go. Please note that Danny Kukawka did more than only integrate the "normal" scanner sequence from 70-scanner.fdi into hal. He added another patch the hint to which I've received from him when discussing that stuff on the hal-mailinglist. Since the day I've integrated that into my hal package the scanner started working - except the processor issue. Anyway, please find both lshal-output and the patch for hal that makes things work attached. Take care Dieter -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c43 --- Comment #43 from Dieter Jurzitza 2009-01-23 12:24:24 MST --- Created an attachment (id=267376) --> (https://bugzilla.novell.com/attachment.cgi?id=267376) This is the patch I had to apply against current hal to make scanners work This patch makes scanners work that promote themselves as "scanners", however, is ineffective for scanners that promote themselves as "processors" -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c45 Danny Kukawka changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |axel.braun@gmx.de --- Comment #45 from Danny Kukawka 2009-01-24 01:35:52 MST --- @Axel: Please be sure that you have the latest HAL update installed. Attach a (or two) tar archives from the whole content of /usr/share/hal/fdi and /etc/hal/fdi. Please attach also lshal from this case. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User axel.braun@gmx.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c47 --- Comment #47 from Axel Braun 2009-01-24 06:44:40 MST --- Created an attachment (id=267457) --> (https://bugzilla.novell.com/attachment.cgi?id=267457) /usr/share/hal/fdi and /etc/hal/fdi -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c49 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #49 from Johannes Meixner 2009-01-27 01:08:49 MST --- Many thanks for the analysis! I cannot write to /usr/ in the running system because this might be mounted read-only, see https://bugzilla.novell.com/show_bug.cgi?id=438867#c34 Therefore /usr/lib/YaST2/bin/test_and_set_scanner_access_permissions writes to /etc/hal/fdi/information/20thirdparty/80-scanner.fdi In the end - as far as I can imagine - this means that somehow Axel Braun runs an outdated yast2-scanner package which also explains the unexpected second result in comment #37 On my openSUSE 11.1 workstation I have: ------------------------------------------------------------------------ root@host# ls /etc/hal/fdi/policy/10osvendor/80-scanner.fdi ls: cannot access /etc/hal/fdi/policy/10osvendor/80-scanner.fdi: No such file or directory root@host# ls /etc/hal/fdi/information/20thirdparty/80-scanner.fdi /etc/hal/fdi/information/20thirdparty/80-scanner.fdi user@host$ rpm -q --changelog yast2-scanner | head -n16 * Thu Dec 04 2008 jsmeix@suse.de - V 2.17.5 - Since openSUSE 11.1 'usb_device' must be replaced by 'usb' in HAL fdi files (see Novell/Suse Bugzilla bnc#438867). Adapted test_and_set_scanner_access_permissions so that it works for openSUSE 11.1 and is still to some extent backward compatible with openSUSE 11.0. * Wed Dec 03 2008 jsmeix@suse.de - V 2.17.4 - Using /usr/share/hal/fdi/information/20thirdparty/70-scanner.fdi instead of /etc/hal/fdi/policy/10osvendor/70-scanner.fdi and /etc/hal/fdi/information/20thirdparty/80-scanner.fdi instead of /etc/hal/fdi/policy/10osvendor/80-scanner.fdi (see Novell/Suse Bugzilla bnc#438867). ------------------------------------------------------------------------ Therefore from my point of view the whole issue is already fixed in yast2-scanner but somehow (which is beyond my control) at least some users have an outdated yast2-scanner RPM installed. When I search for "yast2-scanner" for "openSUSE 11.1" on http://software.opensuse.org/search I get only version 2.17.5 available in "openSUSE:11.1/standard" so that currently I do not have an idea how users got an outdated yast2-scanner RPM installed.

From my current point of view the bug was never in HAL or in yast2-scanner or in any software and all we did was in the end a waste of time because the root cause is somewhere outside of the software which lets at least some users get outdated packages installed.

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

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c51 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | AssignedTo|jsmeix@novell.com |dkukawka@novell.com --- Comment #51 from Johannes Meixner 2009-01-27 08:26:22 MST --- I can reproduce it now (installed the old SCSI host adapter for my HP ScanJet 6200C into my workstation) => reopening. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c53 --- Comment #53 from Johannes Meixner 2009-01-27 08:30:45 MST --- Created an attachment (id=267963) --> (https://bugzilla.novell.com/attachment.cgi?id=267963) lshal -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c55 --- Comment #55 from Johannes Meixner 2009-01-27 08:59:03 MST --- In contrast to comment #40 the workaround in comment #7 does not work for me. I added to /usr/share/hal/fdi/information/20thirdparty/70-scanner.fdi those lines <match key="info.category" string="scsi_generic"> <match key="@info.parent:scsi.type" string="processor"> <match key="@info.parent:scsi.vendor" string="HP"> <append key="info.capabilities" type="strlist">scanner</append> </match> </match> </match> but got still no ACL fo normal users for /dev/sg6 after a complete reboot is is still "crw-rw---- root root". According to comment #45 I will check that I "have the latest HAL update installed"... -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dkukawka@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c58 --- Comment #58 from Danny Kukawka 2009-01-27 11:03:58 MST --- You have an outdated HAL version installed in the system. It's hal-0.5.12-10.1 but the actual latest version (check e.g. http://download.opensuse.org/update/11.1/rpm/i586/) is hal-0.5.12-10.12.1 . I've updated the package on your system and now I have: ------------------------------------------------------------------ udi = '/org/freedesktop/Hal/devices/pci_1022_2020_scsi_host_scsi_device_lun0_scsi_generic' access_control.file = '/dev/sg6' (string) access_control.type = 'scanner' (string) info.callouts.add = {'hal-acl-tool --add-device'} (string list) info.callouts.remove = {'hal-acl-tool --remove-device'} (string list) info.capabilities = {'scsi_generic', 'scanner', 'scanner', 'access_control'} (string list) info.category = 'scsi_generic' (string) info.parent = '/org/freedesktop/Hal/devices/pci_1022_2020_scsi_host_scsi_device_lun0' (string) info.product = 'SCSI Generic Interface' (string) info.subsystem = 'scsi_generic' (string) info.udi = '/org/freedesktop/Hal/devices/pci_1022_2020_scsi_host_scsi_device_lun0_scsi_generic' (string) linux.device_file = '/dev/sg6' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'scsi_generic' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1e.0/0000:02:0a.0/host3/target3:0:4/3:0:4:0/scsi_generic/sg6' (string) scsi_generic.device = '/dev/sg6' (string) ------------------------------------------------------------------ This should set the needed ACLs. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User dieter.jurzitza@t-online.de added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c60 Dieter Jurzitza changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | --- Comment #60 from Dieter Jurzitza 2009-01-27 12:57:54 MST --- Hi folks, I think this is not all that needs to be done here. If you kindly look into my patches - well, might sound penetrant now - there is an additional line that should go into 70-scanner.fdi that says: <match key="@info.parent:scsi.model" string="C6270A"> </match> specifically for Johannes' 6200C device. And I had had asked on the hal list whether or not it would be acceptable to open any device that stems from HP (or EPSON) promoting itself "processor" and assign it the property "scanner". Well, nobody commented on that but I think it is not a good idea to do so. You can argue now that this will only happen if you readily connected the scanner - however, it can. Therefore the key shown above should be added and it can be extracted from /proc/scsi/scsi. This is what latest sane-desc.c cares for. Take care Dieter -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=462639 User jsmeix@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=462639#c61 Johannes Meixner changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED --- Comment #61 from Johannes Meixner 2009-01-28 02:27:07 MST --- Dieter, why do you reopen it when it is fixed? What does not work for you when you use our packages (an up-to-date yast2-scanner and the updated hal)? I can confirm that it works with the updated hal package (now hal-0.5.12-10.12.1) so that I close it again as fixed. Strange: I used http://software.opensuse.org/search to search for "hal" for openSUSE 11.1 and got only "openSUSE:11.1/standard" but no result for "update" which is from my point of view a bug in http://software.opensuse.org/search because of course I do want to see also our official update packages. Dieter, you mix up something. Of course we (i.e. Suse/Novell) and the SANE project appreciate your enhancement for SCSI scanners very much but you cannot enforce us to apply your patches now. Again: Of course we appreciate your patches. But I am the sane-backends package maintainer and I (together with my colleagues) decide (based on our general packaging policies and individual reasoning) when and how we apply which patches and when and how we make new package versions available and you cannot enforce what work I have to do first of all because you are not my employer - this is Suse/Novell - not you. You confuse a hardcoded list of SCSI scanners in the SANE sources which creates a better 70-scanner.fdi during build-time of the SANE software with my generic stuff in test_and_set_scanner_access_permissions (just read my comment #33) which runs at runtime on the end-user's system to add missing scanners (both USB and SCSI) to 80-scanner.fdi. When we upgrade the SANE software we will have better built-in support for some SCSI scanner "processors" via 70-scanner.fdi but we still need support for all SCSI scanner "processors" so that I cannot drop the generic stuff. Therefore I want to have the generic stuff working which is what the bug is about. Only when the hardcoded list of SCSI scanners in SANE is complete and continuously updated for new SCSI scanners - note Olaf Meeuwissen's mail http://lists.alioth.debian.org/pipermail/sane-devel/2009-January/023512.html then we do no longer need the generic stuff. -- 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.