Description of problem: When a printer is connected to a running Mageia 1 system, udev-configure-printer installs task-printing-server, and then nothing happens. Currently, it requires manually running system-config-printer, which then installs additional packages. Then the printer must be disconnected/reconnected, before system-config-printer can see it. In my opinion, task-printing-server should include a requires on system-configure-printer, and either find a way to retrigger the actions caused by a printer disconnect/connect, or display a message to the user asking them to disconnect/connect the printer, before running system-config-printer.
CC: (none) => magnus.mud
(In reply to comment #0) [..] > Currently, it requires manually running system-config-printer, > which then installs additional packages. Then the printer > must be disconnected/reconnected, before system-config-printer > can see it. > That's possibly a bug in system-config-printer > In my opinion, task-printing-server should include a requires > on system-configure-printer, and either find a way to retrigger > the actions caused by a printer disconnect/connect, or display > a message to the user asking them to disconnect/connect the > printer, before running system-config-printer. Ideally users would configure/add printers using drakconf, which installs system-config-printer and co.
Assignee: bugsquad => cjw
CC: (none) => marcello.anni
ping?
CC: (none) => marja11
what is your printer model ?
CC: (none) => dmorganecSource RPM: task-printing-scanning-2010-4.mga1.src.rpm => task-printing-scanning
I have a canon pixma mp150. lsusb shows ... Bus 001 Device 004: ID 04a9:1709 Canon, Inc. PIXMA MP150 Scanner
3 monthly ping
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX