Bug 192194 - raw file printing doesn't work after upgrading to cups-1.2.0-1.1
raw file printing doesn't work after upgrading to cups-1.2.0-1.1
Product: Fedora
Classification: Fedora
Component: cups (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
: 192232 (view as bug list)
Depends On:
Blocks: FC6Target
  Show dependency treegraph
Reported: 2006-05-18 05:56 EDT by Steve
Modified: 2007-11-30 17:11 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-05-18 12:02:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
printconf-tui --Xexport (2.85 KB, text/plain)
2006-05-18 11:34 EDT, Steve
no flags Details

  None (edit)
Description Steve 2006-05-18 05:56:10 EDT
Description of problem:
raw file printing doesn't work afer upgradind to cups-1.2.0-1.1

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.upgrade to cups-1.2.0-1.1
2.print from a remote machine
3.see wath you get and the error_log
Actual results:

Print-Job client-error-document-format-not-supported: Unsupported format

Expected results:

Additional info:
Comment 1 Tim Waugh 2006-05-18 06:30:37 EDT
How about if you run these commands, as root, on the server?:

/usr/sbin/printconf-backend --force-rebuild
/sbin/service cups restart
Comment 2 Steve 2006-05-18 06:54:11 EDT
Nothing appears, same error(s) as before.
Comment 3 Steve 2006-05-18 07:16:52 EDT
There in another error before, here is the log:

I [18/May/2006:13:16:46 +0200] Configured for up to 100 clients.
I [18/May/2006:13:16:46 +0200] Allowing up to 100 client connections per host.
I [18/May/2006:13:16:46 +0200] Using policy "default" as the default!
I [18/May/2006:13:16:46 +0200] Full reload is required.
I [18/May/2006:13:16:46 +0200] Loaded MIME database from '/etc/cups': 34 types,
39 filters...
I [18/May/2006:13:16:46 +0200] Loading job cache file "/var/cache/cups/job.cache"...
I [18/May/2006:13:16:46 +0200] Full reload complete.
I [18/May/2006:13:16:46 +0200] Listening to :::631 on fd 0...
I [18/May/2006:13:16:46 +0200] Listening to on fd 2...
E [18/May/2006:13:16:46 +0200] Unable to set ACLs on root certificate
"/var/run/cups/certs/0" - Operation not supported
E [18/May/2006:13:17:14 +0200] Print-Job
client-error-document-format-not-supported: Unsupported format
Comment 4 Tim Waugh 2006-05-18 07:53:45 EDT
Please attach the output of 'printconf-tui --Xexport'.  Thanks.
Comment 5 Tim Waugh 2006-05-18 10:57:19 EDT
*** Bug 192232 has been marked as a duplicate of this bug. ***
Comment 6 Steve 2006-05-18 11:34:27 EDT
Created attachment 129436 [details]
printconf-tui --Xexport
Comment 7 Tim Waugh 2006-05-18 11:38:52 EDT
You don't have a raw queue defined, and so printconf doesn't configure CUPS for
raw printing.  At some point, I expect you edited /etc/cups/mime.convs by hand
to enable raw printing.

Using Desktop->Administration->Printing, add a raw print queue.  Just call it
'raw' if you like.  On the 'Printer model' page, scroll down to the bottom and
select 'Raw Print Queue'.

Does printing work now?
Comment 8 Steve 2006-05-18 11:50:44 EDT
it is new in cups 1.2 ??
Comment 9 Steve 2006-05-18 11:55:55 EDT
works just perfect! but this is definitively new in 1.2.
Comment 10 Pasi Sainio 2006-05-18 12:39:09 EDT
Thanks, fixed my problem too!
Comment 11 Tim Waugh 2006-05-18 12:43:11 EDT
This is not new in CUPS-1.2; CUPS-1.1.x behaves in exactly the same way.

In fact it is system-config-printer that does this, changing the mime.types file
automatically depending on whether raw queues are defined.  It has always
behaved that way on FC5.

If you've had raw printing working before without raw queues being defined, you
have edited /etc/cups/mime.types by hand (or some other program has done for
you).  This will always be overwritten whenever you change your printer
configuration or update CUPS.
Comment 12 Steve 2006-05-18 12:55:02 EDT
before 1.2, i never had to do this way!
anyway, thanks for your help...
Comment 13 Tim Waugh 2006-05-18 12:55:59 EDT
But had you edited /etc/cups/mime.types to uncomment the octet-stream line?
Comment 14 Steve 2006-05-18 13:25:43 EDT
yes, i always have (had) to uncomment the octet-stream's in mime.types an
Comment 15 Steve 2006-05-24 10:19:26 EDT
now, with cups-1.2.1-1.2, it's just perfect, like before, without the "raw share"!

Note You need to log in before you can comment on or make changes to this bug.