|
Bugzilla – Full Text Bug Listing |
| Summary: | no resmgr permissions for scanners after update | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Johannes Meixner <jsmeix> |
| Component: | Update Problems | Assignee: | Johannes Meixner <jsmeix> |
| Status: | RESOLVED FIXED | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Minor | ||
| Priority: | P5 - None | ||
| Version: | Beta 8 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | SuSE Linux 10.1 | ||
| Whiteboard: | |||
| Found By: | Development | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | the content of the RPM post-install script regarding this bug | ||
|
Description
Johannes Meixner
2006-03-10 14:10:13 UTC
Added postinstall script (because it must run sane-find-scanner to get USB bus and device numbers for the resmgr calls). Submitted package sane to STABLE. Created attachment 72575 [details]
the content of the RPM post-install script regarding this bug
Only for information and perhaps for further discussion the content of the post-install script regarding this bug.
For your information: I tested a 10.0 -> 10.1 beta8 update. /etc/hal/fdi/policy/10osvendor/80-scanner.fdi is perfectly created. Nevertheless there are still no resmgr permissions for scanners after update without additional reboot because at package update time the "resmgr add ..." calls fail and in /var/log/YaST2/y2logRPM is: ---------------------------------------------------------------------- 2006-03-20 16:18:03 sane-1.0.17-8.x86_64.rpm installed ok Additional rpm output: warning: /etc/sane.d/dll.conf created as /etc/sane.d/dll.conf.rpmnew Unable to connect to resource manager: Connection refused Unable to connect to resource manager: Connection refused ---------------------------------------------------------------------- There is nothing I can do here (still FIXED as good as possible). The udev -> HAL -> resmgr dependencies are too complicated so that normal users who don't know which services to restart will end up in Windows-like reboots. |