Mailinglist Archive: opensuse-bugs (12871 mails)

< Previous Next >
[Bug 462639] access permissions for scsi scanners missing
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Tue, 27 Jan 2009 01:08:52 -0700 (MST)
  • Message-id: <20090127080852.810DCCC7D5@xxxxxxxxxxxxxxxxxxxxxx>

User jsmeix@xxxxxxxxxx added comment

Johannes Meixner <jsmeix@xxxxxxxxxx> changed:

What |Removed |Added
Resolution| |FIXED

--- Comment #49 from Johannes Meixner <jsmeix@xxxxxxxxxx> 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

writes to

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

user@host$ rpm -q --changelog yast2-scanner | head -n16
* Thu Dec 04 2008 jsmeix@xxxxxxx
- 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@xxxxxxx
- 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
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:
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >