| Summary: | CUPS does not share any printer over the network | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Thomas Canniot <thomas.canniot> |
| Component: | RPM Packages | Assignee: | D Morgan <dmorganec> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | doktor5000, marc.maurer, marja11 |
| Version: | 1 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | cups-1.4.6-3.1.mga1 | CVE: | |
| Status comment: | |||
| Attachments: |
CUPS Pinter conf file
CUPS config file CUPS ERror log |
||
|
Description
Thomas Canniot
2011-11-27 20:42:37 CET
Created attachment 1140 [details]
CUPS Pinter conf file
Created attachment 1141 [details]
CUPS config file
Hi, thanks for reporting this bug. Assigned to the package maintainer. Can you also attach /var/log/cups/error_log ? Keywords:
(none) =>
Triaged Created attachment 1142 [details]
CUPS ERror log
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED. @ dmorgan Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. CC:
(none) =>
marja11 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
Marc Maurer
2012-08-06 10:13:27 CEST
CC:
(none) =>
marc.maurer With Mageia 1 it was possible to use USB printer with box (LiveBox) (ipp://ip_box:631) but with Mageia 2 it is not working. Priority:
Normal =>
High
Marc Maurer
2012-08-06 10:16:28 CEST
Source RPM:
cups-1.4.6-3.1.mga1 =>
cups-1.4.6-3.1.mga1, cups-1.5.2-5.1mga2 (In reply to comment #7) > With Mageia 1 it was possible to use USB printer with box (LiveBox) > (ipp://ip_box:631) but with Mageia 2 it is not working. Sorry, priority should be set by the assignee, so setting that back to normal. Is ipp the only protocol that can be used in your setup, or can you try with lpd? Over my home network (but different setup than yours) I have very good results printing with lpd. Discovering the printers (attached to a print server) was never possible for me, though, but that is something that can only be solved by someone with the same hardware as me. Priority:
High =>
Normal The use of the printer direct connected on the computer is OK. But the USB printer is connected on the ADSL Box (here a LiveBox from Orange) to share it with all user without direct connection with the printer, the printer was shared. This configuration worked with Mageia 1 and cups-1.4.6-3.mga1.x86_64.rpm but don't working with Mageia 2 and cups-1.5.2-5.mga2.x86_64.rpm When i install the cups version 1.4.6-3.mag1 on the Mageia 2 in the place of the 1.5.2-5.mga2 version of cups, i can print of the printer connected on the LiveBox with USB. Here we have a regression of the cups software. No ? (In reply to comment #10) > When i install the cups version 1.4.6-3.mag1 on the Mageia 2 in the place of > the 1.5.2-5.mga2 version of cups, i can print of the printer connected on the > LiveBox with USB. Here we have a regression of the cups software. No ? Ouch, I misread (too much haste) when I replied to comment 7, I thought you were the original reporter of this bug. :-( The cause for your problem must be a different one than for the original reporter of this bug. As you can see, the original reporter filed this report against the versions of Mageia + cups you don't have problems with. So, in fact, your issue should go into a seperate report. Sorry for not having seen this before. Please file a seperate report about the regression. Here you can read which attachments are useful: https://wiki.mageia.org/en/Triage_guide#Printer_problems @ Thomas Do have this bug in Mageia 2, too? Version:
2 =>
1 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 =>
RESOLVED |