Bug 113558 - could not configure local printer
Summary: could not configure local printer
Status: RESOLVED DUPLICATE of bug 104874
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: i686 All
: P5 - None : Major
Target Milestone: ---
Assignee: Michal Zugec
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-27 16:16 UTC by Jean-Daniel Dodin
Modified: 2005-09-02 11:35 UTC (History)
0 users

See Also:
Found By: Beta-Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
yast logs (1.32 MB, application/x-gtar)
2005-08-27 16:18 UTC, Jean-Daniel Dodin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jean-Daniel Dodin 2005-08-27 16:16:46 UTC
after an update beta2->beta3, the local printer do not works no more (in fact I
don't know if it worked on beta2, but in beta1 it did)

it's a deskjet 930C on /dev/lp0.

I can't delete the line of this printer in yast (shown "not configured"). If I
try  to configure it, I get afterward the message "vous utilisez un spouleur
différent" (you are using a different spooler);
If I try to add a printer, the new printer takes the place of the non configured
one (only if i give the same printer model), but what ever try I did, same error.
When exiting ysat, I have the cups error message: cups(file)
DoRequesterror:client-error-not-possible
I attach the Yast logs
Comment 1 Jean-Daniel Dodin 2005-08-27 16:18:04 UTC
Created attachment 47866 [details]
yast logs

yast logs for cups problem.
Comment 2 Jean-Daniel Dodin 2005-08-27 16:18:38 UTC
I could configure a laser printer on a lpd server... without any problem
Comment 3 Michal Zugec 2005-09-02 09:34:42 UTC
there was a but with unloading lp module
can you reproduce it on rc1, please?
Comment 4 Jean-Daniel Dodin 2005-09-02 09:41:06 UTC
I will try as soon as lc1 is out :-)
Comment 5 Michal Zugec 2005-09-02 11:35:14 UTC
but now I am sure it'a duplicate of #104874
if the problem still, reopen it

*** This bug has been marked as a duplicate of 104874 ***