Description of problem: I am using a hp Laserjet 6MP, connected to a usb port (lpt-usb adaptor cable). This has always worked, but does not work any more on Mageia 3 Alpha2: drakconf.real does not detect the printer. The printer did still configure and work correctly during early QA testing of Alpha2 - the configuration created by that system had created a URI of "usb://HP/Laserjet%206MP". Simply using this URI on the Alpha2 configuration (the one now downloaded from the mirrors) does not work either. Version-Release number of selected component (if applicable): How reproducible: 100% Steps to Reproduce: 1. drakconf.real -> Hardware -> Setup the printer ... -> Add 2. wait until the "busy" indication stops 3. no printer is detected
disconnect your printer run "tailf /var/log/messages 2>&1 | tee output.txt" connect you printer _attach_ the file output.txt here
Source RPM: (none) => system-config-printer
Created attachment 2996 [details] Output obtained following instructions from comment #1
Thanks for the comment - that practically solves the problem. According to the output, facl does not exist on my system. After installing the acl rpm, the printer is recognized correctly and installs smoothly. So, the problem is: acl had been correctly and automatically pulled in up to early Alpha2 systems, but the Alpha2 downloaded from the mirror does not install acl any more (acl exists on the cdrom) - certainly some dependency has been lost.
ok cool how have you installed the alpha2 ? with the livecd/dvd or the classic install ? if it's the classic install can you provide the file /root/drakx/report.bug.gz as an attachment ? (to see if there was other errors too)
Priority: Normal => release_blockerSummary: Cannot configure Laserjet 6MP as usb printer => Cannot configure usb printer (rpm acl missing)
Created attachment 3002 [details] report.bug.xz from my system (classic install from 64-bit DVD)
I did a classic install from a DVD (64-bit) downloaded from the public mirrors. One precision for the record (and for help in case somebody else needs to apply this as a quick fix): installing acl must be followed by a re-boot. After installing acl, but before the reboot, system-config-printer only adds a "LPT #1" item to the device list, which is useless. After the reboot, it also adds an "HP Lasejet 6MP" item, which is the one that is needed.
this is really strange, acl was installed on your install, so something is wrong installing acl-2.2.51-4.mga3.x86_64.rpm lib64usbmuxd2-1.0.8-1.mga3.x86_64.rpm lib64usb1.0_0-1.0.14-1.mga3.x86_64.rpm usbmuxd-1.0.8-1.mga3.x86_64.rpm lib64plist1-1.8-1.mga2.x86_64.rpm libplist-1.8-1.mga2.x86_64.rpm libimobiledevice-1.1.4-1.mga3.x86_64.rpm lib64imobiledevice3-1.1.4-1.mga3.x86_64.rpm from /tmp/image/media/core starting installing packages created transaction for installing on /mnt (remove=0, install=0, upgrade=8) libplist-1.8-1.mga2.x86_64 lib64plist1-1.8-1.mga2.x86_64 lib64usb1.0_0-1.0.14-1.mga3.x86_64 acl-2.2.51-4.mga3.x86_64
Yes, this is weird (following comment #7 I checked here on my /root/drakx/install.log: also there I get confirmation that acl has really been installed during system generation) Doing today "rpm -aq --last | grep acl" gives acl-2.2.51-4.mga3.x86_64 Sat 27 Oct 2012 11:53:17 AM CEST lib64acl1-2.2.51-4.mga3.x86_64 Mon 22 Oct 2012 08:59:00 PM CEST (install date was 22.10, manual install following comment #1 was 27.10.). There is only one explanation: for reasons unknown acl has been removed - probably soon after system installation since I had the failure to detect the printer already late on 22.10. At the end of customiztopm I had done urpme --auto-orphans - but did not remark anything about acl. That I inadvertently did an explicit urpme acl is highly unlikely. I think I will try to reproduce my install and customization process on a spare partition, maybe something will show up. I suggest to close this bug - in the unlikely case that I can reproduce the disappearance of acl this should be posted as a separate bug.
yep thanks
Priority: release_blocker => NormalStatus: NEW => RESOLVEDResolution: (none) => WORKSFORME
It is now clear what happens: When, at the end of customization (installing additional packages, removing packages which I do not need), I do "urpme --auto-orphans", acl figures among the 16 packages that are removed. I think that indicates that none of the packages that are installed and need acl - for instance system-config-printer - has a dependency on acl. I checked with "urpmq --requires-recursive system-config-printer": no acl in the list of packages obtained. File a bug on the missing requirement in system-config-printer?
*** Bug 8013 has been marked as a duplicate of this bug. ***
CC: (none) => isolde
dup *** This bug has been marked as a duplicate of bug 8125 ***
Resolution: WORKSFORME => DUPLICATE