Description of problem: Clean install of Mageia 4Beta1, trying to add a printer that is on the network, it refuses to add the printer. When you type in the IP address in "Find network printer" in the Network Printer section, you are then told the port of the printer. However, when you press "Forward" to complete the installation, nothing happens. The "busy" icon appears, and that is all. All you can do is cancel the operation because it does not want to do anything to complete installation. A possible CUPS problem, CUPS is installed. Version-Release number of selected component (if applicable): Clean install of Mageia 4 Beta 1 (with updates installed) How reproducible: Try installing a network printer. Reproducible: Steps to Reproduce:
(In reply to DariuszSki from comment #0) > Description of problem: > Clean install of Mageia 4Beta1, trying to add a printer that is on the > network, it refuses to add the printer. you might want to re-try with a clean 4beta2 install ;-) please attach: /etc/cups/printers.conf /var/log/cups/error_log and the output of (as root) journalctl -f from when you try to add the printer Btw, which printer is it and which protocol (e.g. "ipp") does it use in Mageia 3?
CC: (none) => marja11, qa-bugs, thierry.vignaudWhiteboard: (none) => 4beta1
Keywords: (none) => NEEDINFO
As the symptoms are similar to my problem 2 in bug 11684, may I suggest also checking whether the package task-printing-misc is installed.
CC: (none) => mageia
After your suggestion, it appears that not all packages to do with printing were installed when first setting up via MCC to enable the printing system. As soon as I installed the missing printer / cups related packages, the printer was added no problem. So need to add the packages that were left out of the printing install / initialisation script.
*** Bug 12090 has been marked as a duplicate of this bug. ***
CC: (none) => paiiou
I have just attempted to install a Samsung SCX-4521F printer on a Cauldron installation (via USB) which has never had a printer attached. Running "MCC -> Hardware -> Configure Printers and Scanning" a heap of packages were installed, but task-printing was *not* one of them. There was no way that I could get my printer to work. Installing task-printing pulled a further 48 packages after which it was possible to set up my printer. Bumping to release blocker as this will cause real headaches for new users attempting to enable a printer.
Severity: major => criticalPriority: Normal => release_blockerCC: (none) => zen25000
You are forttunate! printerdrake just gives me a black screen, so I am forced to use the Web-based config.
CC: (none) => laidlaws
(In reply to Doug Laidlaw from comment #6) > You are forttunate! printerdrake just gives me a black screen, so I am > forced to use the Web-based config. Please provide : version of printerdrake output when launched from command line
CC: (none) => makowski.mageia
Was trying to open printerdrake from MCC Typing "printerdrake" as root, reply: "bash: printerdrake: command not found" urpmi printerdrake: "Package system-config-printer-1.5.4-1.mga5.i586 is already installed." System is Cauldron fully updated. Happens with i586 and x86-64.
(In reply to Doug Laidlaw from comment #8) > Was trying to open printerdrake from MCC > > > Typing "printerdrake" as root, reply: > > "bash: printerdrake: command not found" > of course, sorry call, system-config-printer that is what it is called by MCC there is no "printerdrake" command
"system-config-printer" opens a small fully functional window. Icons are missing, but that will be something else. From MCC -> Hardware -> Configure printing, the window (not the screen, but the window is fullscreen) used to go black and stay that way. There has been an update to MCC since I last tried, and just before I reported. Now the black screen is only momentary, and I get a fullscreen version of the small printerdrake window. Sounds as though the bug was in MCC, and has been fixed.
Is this bug fixed then?
CC: (none) => ennael1
Never had the original problem. Comment 6 has gone away.
Using it everyday here without any pb. Closing this bug. Feel free to reopen if needed
Resolution: (none) => WORKSFORMEStatus: NEW => RESOLVED