Mailinglist Archive: opensuse-bugs (14787 mails)
| < Previous | Next > |
[Bug 218393] no scanner access permissions via HAL/resmgr
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 27 Nov 2006 04:27:55 -0700 (MST)
- Message-id: <20061127112755.2CD7DF2F@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=218393
------- Comment #21 from jsmeix@xxxxxxxxxx 2006-11-27 04:27 MST -------
For your information:
User access works perfectly for another new connected scanner
which is also listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi
This file is never changed after it was created.
YaST writes only to 80-scanner.fdi, see comment #0.
I.e. the crucial difference seems to be whether or not the fdi file exists
during startup of the HAL machinery and according to comment #19 this means
to do a reboot when only one scanner is connected (which is the normal 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, or are watching someone who is.
------- Comment #21 from jsmeix@xxxxxxxxxx 2006-11-27 04:27 MST -------
For your information:
User access works perfectly for another new connected scanner
which is also listed in /etc/hal/fdi/policy/10osvendor/70-scanner.fdi
This file is never changed after it was created.
YaST writes only to 80-scanner.fdi, see comment #0.
I.e. the crucial difference seems to be whether or not the fdi file exists
during startup of the HAL machinery and according to comment #19 this means
to do a reboot when only one scanner is connected (which is the normal 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, or are watching someone who is.
| < Previous | Next > |