Bug 476612
| Summary: | Cannot print test page | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Christopher Beland <beland> | ||||||||||||
| Component: | system-config-printer | Assignee: | Tim Waugh <twaugh> | ||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||
| Priority: | low | ||||||||||||||
| Version: | rawhide | CC: | atu, johannbg, twaugh | ||||||||||||
| Target Milestone: | --- | Keywords: | Reopened | ||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | All | ||||||||||||||
| OS: | Linux | ||||||||||||||
| Whiteboard: | |||||||||||||||
| Fixed In Version: | system-config-printer-1.1.2-1.fc11 | Doc Type: | Bug Fix | ||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2009-01-20 11:01:58 UTC | Type: | --- | ||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||
| Documentation: | --- | CRM: | |||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||
| Embargoed: | |||||||||||||||
| Attachments: |
|
||||||||||||||
|
Description
Christopher Beland
2008-12-16 07:06:48 UTC
Created attachment 327072 [details]
troubleshoot.txt file provided by the troubleshooting GUI
If I try to print test page via http://127.0.0.1:631 following error are displayed: Unsupported format 'application/vnd.cups-banner'! After dirty rebuild new beta 2: the same error. This smells like a /etc/cups/mime.types & /etc/cups/mime.convs issue Try adding this to mime.types in the #CUPS-specific types above the first entry.. application/vnd.cups-banner string(0,'#CUPS-BANNER') And add this to the mime.convs in the #PostScript filters beneath the latest entry. application/vnd.cups-banner application/postscript 33 bannertops Ye could try diffing these files from a work vs non working instance of cups and see if the maintainer had made some changes and report back. Thank you.. The client-error-not-found could be ghostscript make sure it's installed and then try using older/newer version and see if it fixes things ( use koji.fedoraproject.org ) (In reply to comment #5) > The client-error-not-found could be ghostscript No, it definitely isn't that. CUPS is saying that it doesn't have a printer by that name. Unfortunately it seems to be just wrong about that, and I'm not sure why it thinks it. Ok so let's start from the top and keep ghostscript out of the picture.. Reported by "beland" "There was an error during the CUPS operation: 'server-error- service-unavailable'." & CUPS operation: 'client-error-not-found'. Cups was running so this smells like some permission errors.. A) s-c-p does not have the necessary privileges to create read etc gnome-keyring? policykit? selinux? B) file,directory permission errors. C) He created the printer again with the same name etc some conflict there. I do belive this is an s-c-p error and he can confirm that by creating and deleting a printer from the web interface and or manually creating and deleting a printer from cli. Reported by "atu" Now atu should have filed a different bug since his report does not confirm nor does not seem to relate to what beland reported and what he's ( atu) seeing seems to be mime.type mime.convs related ( these seem to be 2 separated bugs ) So "beland" could you test creating and deleting printers from the web and cli and also post the permissions of the cups directory and files. And you atu report back about comment4 fixes or does not fix your issue. Beland Does uninstall reinstall fix your issue ? ( one user reported similar problem he uninstalled and reinstalled in a hurry and he says it fixed his issue ) Btw is this an upgrade or a fresh rawhide install This is a rawhide upgrade from Fedora 10 snap 3. And yes, ghostscript-8.63-4.fc10.x86_64 is installed... I tried the web interface (http://localhost:631/admin) and added the HP again as a new printer called trip2. I can successfully print a test page on trip2 from http://localhost:631/printers/trip2 but not from the system-config-printer troubleshooter. What is it exactly that you would like me to reinstall? All of the cups RPMs? I assume by "cups directory" you mean one of the following? [root@free-spin beland]# ls -la /var/cache/cups/ total 12056 drwxrwxr-x 3 root lp 4096 2008-12-16 14:55 . drwxr-xr-x 14 root root 4096 2008-11-01 23:48 .. -rw-r--r-- 1 root root 842 2008-12-16 03:32 hp-LaserJet-1320-series.ipp -rw-r----- 1 root lp 24198 2008-12-16 14:58 job.cache -rw------- 1 lp lp 12237156 2008-12-16 01:32 ppds.dat -rw-r----- 1 root lp 75 2008-11-30 13:08 remote.cache drwxrwxr-x 2 root lp 4096 2008-09-25 06:53 rss -rw-r--r-- 1 root root 859 2008-12-16 14:56 trip2.ipp -rw-r--r-- 1 root root 849 2008-12-16 01:35 trip.ipp [root@free-spin beland]# ls -la /etc/cups/ppd/ total 88 drwxr-xr-x 2 root lp 4096 2008-12-16 14:55 . drwxr-xr-x 5 root lp 4096 2008-12-16 15:02 .. -rw-r--r-- 1 root root 19345 2008-12-16 03:32 hp-LaserJet-1320-series.ppd -rw-r--r-- 1 root root 17937 2008-12-16 14:56 trip2.ppd -rw-r--r-- 1 root root 17927 2008-12-16 01:35 trip.ppd No need reinstall cups now since we have determine t hat it's s-c-p not cups. Any obvious going on if you start s-c-p in debug mode.. ( system-config-printer ---debug ) Created attachment 327168 [details]
Debugging output
Attached is the debugging output from system-config-printer --debug. All I did was start it up, run the troubleshooter, try to print a test page, and quit.
OK, the problem is that the CUPS test page filename is now different. Please try system-config-printer-1.0.12-5.fc11. *** Bug 474190 has been marked as a duplicate of this bug. *** With system-config-printer-1.0.12-5.fc11.x86_64 the test page now prints, but I still get a dialog box with the error:
>>
CUPS server error
There was an error during the CUPS operation: 'server-error-
service-unavailable'.
<<
I tried to hit "Close" on this dialog box, but system-config-printer froze up.
system-config-printer --debug output please :) Created attachment 327275 [details]
Output from system-config-printer --debug
Output attached when running "system-config-printer --debug" as "beland". I just discovered I don't get an error dialog box when I run system-config-printer as "root".
Running system-config-printer --debug isn't nearly as useful as attaching the troubleshoot.txt file from running the troubleshooter through to the end... Alas, no troubleshoot.txt is produced because system-config-printer freezes when I try to close the server-error-service-unavailable dialog box. rpm -q system-config-printer ? system-config-printer-1.0.12-5.fc11.x86_64 Please run '/sbin/service cups restartlog' as root to clear out the error_log file, then '/usr/sbin/cupsctl -U root --debug-logging' to turn on debugging for CUPS, then do the same as before so that you get the server-error-service-unavailable message. Then please attach the /var/log/cups/error_log file here. Thanks. Created attachment 327699 [details]
/var/log/cups/error_log when experiencing hang
Done. I am now also getting the following errors in my xterm:
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
Xlib: extension "Generic Event Extension" missing on display "localhost:11.0".
(In reply to comment #24) > Xlib: extension "Generic Event Extension" missing on display "localhost:11.0". These are harmless. Could you try the latest system-config-printer RPM from rawhide (1.1.1-1.fc11)? I'm hoping it was fixed with this change: https://fedorahosted.org/system-config-printer/ticket/13 Sorry, I forgot to mention that the results reported in comment #24 and attachment were with system-config-printer-1.1.1-1.fc11.x86_64, which I had upgraded to in the meantime. I think this was fixed in 1.1.2-1.fc11, with this change: https://fedorahosted.org/system-config-printer/ticket/127 Confirmed, I'm able to print the test page with no crash with system-config-printer-1.1.2-1.fc11.x86_64. Thanks for your help! |