Bug 633 - HP Printer support broken again
Summary: HP Printer support broken again
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-04 17:20 CEST by Frank Griffin
Modified: 2011-04-04 22:20 CEST (History)
1 user (show)

See Also:
Source RPM: udev-166-2.mga1.x86_64.rpm
CVE:
Status comment:


Attachments

Description Frank Griffin 2011-04-04 17:20:50 CEST
On a fresh install, if you fire up system-config-printer and click "Add", an HP MF 3030 is not seen, and the following appears in syslog:

Apr  4 11:13:21 ftgme2 kernel: lp: driver loaded but no devices found
Apr  4 11:13:21 ftgme2 udev-configure-printer: add /module/lp
Apr  4 11:13:21 ftgme2 udev-configure-printer: Failed to get parent
Apr  4 11:13:21 ftgme2 python: io/hpmud/musb.c 2035: Invalid usb_open: Permission denied
Apr  4 11:13:21 ftgme2 hp[10144]: io/hpmud/musb.c 2035: Invalid usb_open: Permission denied

Earlier, during first boot of the system (don't know if this is significant):

Apr  4 10:25:12 localhost udev-configure-printer: Cups isn't installed, let's install it
Apr  4 10:25:12 localhost udev-configure-printer: InstallSpooler()
Apr  4 10:25:12 localhost udev-configure-printer: CheckInstalledSpooler()
Apr  4 10:25:12 localhost udev-configure-printer: InstallSpoolerFailed()


Reproducible: 

Steps to Reproduce:
Comment 1 Frank Griffin 2011-04-04 17:33:49 CEST
Oddly enough, an strace -e open of both s-c-p and the 3 running udev processes doesn't show any open() calls for anything containing "usb".
Comment 2 D Morgan 2011-04-04 21:10:48 CEST
is system-config-printer-applet started ?

CC: (none) => dmorganec

Comment 3 Frank Griffin 2011-04-04 22:20:04 CEST
Grrr.  I went to reproduce to answer your question, and now it works.  It was failing solidly, and I rebooted for other reasons, and now it's fine.  The applet is running now, but I can't say whether it was before.

I'll close this as INVALID for now, and try to remember to reopen it if my next fresh install on this machine has the problem again.  I install the fresh system, boot it, and install a whole raft of packages (~1200) from a reference list.  Possibly the install changes something that doesn't take effect until a reboot.  I'll see if the same pattern occurs next time.

Status: NEW => RESOLVED
Resolution: (none) => INVALID


Note You need to log in before you can comment on or make changes to this bug.