Bug 239730

Summary: yast2 printer forgets printer Model for LPD queues
Product: [openSUSE] openSUSE 10.2 Reporter: Bryce Nesbitt <bryce2>
Component: YaST2Assignee: Michal Zugec <mzugec>
Status: RESOLVED WONTFIX QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---
Attachments: Log of complete failure cycle
Screenshot of yast after quit/reload

Description Bryce Nesbitt 2007-01-29 02:23:42 UTC
This is what happens on my openSUSE 10.2 system:

1) Add an LPD printer (e.g. 192.168.1.202, queue BINARY_P1)
2) Assign it a Model (e.g. Brother HL-1470N)
3) Observe that Model shows in YaST2 under "Model".

Now exit YaST2 and restart.  The printer entry will still be there, but the "Model" will show as "unknown".  No amount of setting the model type results in joy.
Comment 1 Cyril Hrubis 2007-01-29 12:29:52 UTC
Please attach y2logs. If you are in doubt please follow:

http://en.opensuse.org/Bugs/YaST


Thanks!
Comment 2 Bryce Nesbitt 2007-01-29 17:45:48 UTC
Created attachment 115945 [details]
Log of complete failure cycle
Comment 3 Bryce Nesbitt 2007-01-29 17:46:10 UTC
Attached tail -f from /var/log/YaST2 during a cycle of:

1) Load printer
2) Set type to "Brother HL-1470N", save, exit.
3) Load printer again, verify setting did not stick.
Comment 4 Michal Zugec 2007-01-31 17:11:37 UTC
could you attach screenshot of that dialog, please?
Comment 5 Bryce Nesbitt 2007-02-13 05:54:30 UTC
Created attachment 118767 [details]
Screenshot of yast after quit/reload
Comment 6 Bryce Nesbitt 2007-02-13 05:55:32 UTC
This is VERY problematic for me.  I basically can't use this printer.  No amount of selecting PPD files or printer models will 'stick' after YAST2 exits.
Comment 7 Bryce Nesbitt 2007-02-13 05:56:33 UTC
This is VERY problematic for me.  I basically can't use this printer.  No amount of selecting PPD files or printer models will 'stick' after YAST2 exits.
Comment 8 Bryce Nesbitt 2007-02-13 06:26:17 UTC
I finally went into /etc/cpus and manually copied a .ppd file:

hardhat:/etc/cups/ppd # ls -la
total 93
drwxr-xr-x 2 lp   lp     144 2007-02-12 22:14 .
drwxrwxr-x 6 lp   lp     656 2007-02-12 22:12 ..
-rw-r--r-- 1 root root 11912 2007-02-12 22:12 basherBR2.ppd
-rw-r--r-- 1 lp   lp   12045 2007-02-12 22:01 basherps.ppd
-rw-r--r-- 1 lp   lp   66427 2005-11-20 23:41 color.ppd

My printouts are no better, but at least Yast shows the printer model correctly.
Something is definitely broken here.  My printouts, by the way, are all scaled about 60%.  The same printer works fine from a PC with either PCL or Postscript, and from a Mac in Postscript.  I've been using this printer for years, first with Redhat, then with SUSE 10.0 and 10.1.  It's not the printer.  It's the OS.
Comment 9 Johannes Meixner 2007-02-14 14:21:56 UTC
I cannot reproduce it.
It works well for me.
Note that the model name in YaST is what there is in the PPD
as ModelName.
Perhaps there is no such entry in your PPD?
 
Comment 10 Bryce Nesbitt 2007-02-14 16:37:27 UTC
It does NOT work here.
It IS broken.

A resolution where I copy ppd files as root is hardly a resolution.
Maybe I should invite you to log in to my machine with a remote X session and see this.

Yast is NOT saving the information properly.

Yast must think it is saving the information, but actually fails to.  Note that on this same machine yast must be run directly as root, it won't run from the GUI.  Perhaps that's related?
Comment 11 Bryce Nesbitt 2007-02-14 17:06:43 UTC
Related to bug #223341 ?
Comment 12 Michal Zugec 2007-02-14 18:26:19 UTC
First one question - did you running as a root?
There is possibility to run printer module as non-root (but you will able only to see settings, not change them), so check it to be sure.

Please, to help us reproduce it, could you:
1 - delete your current configuration
2 - delete your log files (or backup them away)
3 - try to reproduce and write down step-by-step (please write also details like printer model, hwinfo --printer output, ppd filename)
4 - attach yast-log files
5 - attach /etc/cups/* content

Probably this will enought to reproduce here
Comment 13 Bryce Nesbitt 2007-02-14 18:34:34 UTC
I run yast as root from the command line.

As for your other requests, see above. I've done all that.
Comment 14 Michal Zugec 2007-08-06 12:05:25 UTC
after 10.3
Comment 15 Stephan Kulow 2008-06-25 09:19:43 UTC
mass reopening all 10.2 LATER+REMIND bugs.
Comment 16 Stephan Kulow 2008-06-25 09:24:00 UTC
close all 10.2 LATER/REMIND bugs as WONTFIX. Reopen yourself if you still plan to work on it.