Bug 139929 - KghostviewlNuea.ps':execution failed with message:client-error-not-possible
Summary: KghostviewlNuea.ps':execution failed with message:client-error-not-possible
Status: CLOSED FIXED
Alias: None
Product: kdeprint
Classification: Applications
Component: kjobviewer (show other bugs)
Version: 0.1
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 21:57 UTC by Wayne Combs
Modified: 2008-12-31 20:40 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
hotmail (1.65 KB, application/octet-stream)
2007-01-13 03:07 UTC, Wayne Combs
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Wayne Combs 2007-01-11 21:57:16 UTC
Version:           0.1 (using KDE 3.5.3, Kubuntu Package 4:3.5.3-0ubuntu0.1 dapper)
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-26-386

cupsdoprint-P'homeprinter'-j"-H'127.0.0.1:631'-Uroot-o'copies=1
orientation-requested=3' '/tmp/Kde-wayne/Kghostview l Nuea.ps':execution failed with message:client-error-not-possible
Comment 1 Kurt Pfeifle 2007-01-11 23:19:07 UTC
(the command above is missing the blanks in between the parameters...)

Wayne,

have you tested with KDE 3.5.5 already? 

Also, it is a well known fact that early versions of Kubuntu Dapper shipped with b0rken CUPS and KDEPrint packages. Please check that you have upgraded to the newest versions (run "sudo apt-get update && sudo apt-get upgrade").

In any case, this is not a KDEPrint bug (but we will try to help you, if you respond), the message "client-error-not-possible" is generated by CUPS.

According to RFC 3196 (http://www.ietf.org/rfc/rfc3196.txt): 
      "client-error-not-possible: The request cannot be carried out 
       because of the state of the system."

An example for this could be that the CUPS printqueue (note: that is *not* the physical printer) is not accepting any requests (due to administrative setting to "disabled", or auto-setting to disabled by a CUPS backend which was erring when trying to contact the physical printer).

Should the problem persist after an upgrade, then please tell us the output of the following commands:

  lpstat -p homeprinter
  lpstat -p homeprinter -l
  lpstat -o homeprinter
  lpstat -W completed -o homeprinter | tail -n 2
  lpoptions -d homeprinter
  lpoptions -d homeprinter -l

Cheers,
Kurt

(Note: setting timeout for response by reporter to Feb 1, 2007)
Comment 2 Wayne Combs 2007-01-11 23:42:26 UTC
Kurt,
We installed a new hard drive and downloaded Mepis on it about a month 
ago,and,installed the printer.Everything had been working fine until this 
past weekend,when it started to show that a printer,was not installed.I 
reinstalled the printer Sunday night and printed a test page with no 
problems,but could not get it to print a document,it showed it could not 
find a backend.
Got back around to trying to fix this problem again today,this is when the 
new error code shwed up.I have been keeping all the Synaptic upgrades 
downloaded.
I'm new to LINUX and don't really know all I need to know yet.I was 
wondering if it would be best to go into Synaptic uninstall,then reinstall 
CUPS.
How do you test with KDE 3.5.5.All help will be highly 
appreciated.Thanks,Wayne
[bugs.kde.org quoted mail]

_________________________________________________________________
Type your favorite song.
Comment 3 Kurt Pfeifle 2007-01-12 02:01:26 UTC
Wayne,

can you print test pages from CUPS (that is the name of the printing system, which is not part of KDE)? To test, use a browser and point it to http://localhost:631/printers/ and then click on the "Print Test Page" link of your printer.

Does it print? If so, the CUPS installation is OK. If not, KDE can't do anything to fix it. Fixing CUPS must be done outside of KDE.

Please also give me the output of the commands I asked for. Here is a step by step procedure, if you run KDE:

 * Keyboard combination [alt]+[f2]
 * Type "konsole", click "Run"
 * Don't be afraid if it is all black :-)  [it may be a different color on Mepis, dunno]
 * This is a command interface

Now type these commands (each line is another one), and copy the output to a place where you can save it (or directly into your mail program). I'm assuming the name of your printer is still 'homeprinter':

  lpstat -r                      

If that last command fails, the next ones will not complete either.

  lpstat -p homeprinter
  lpstat -p homeprinter -l
  lpstat -o homeprinter
  lpstat -W completed -o homeprinter | tail -n 2
  lpoptions -d homeprinter
  lpoptions -d homeprinter -l

Cheers,
Kurt
Comment 4 Wayne Combs 2007-01-13 03:07:40 UTC
Kurt,
Tried the test page and it didn't work.I went in to cofigurations and tried 
to restart CUPS,today it let restart.Printed a couple of pages and 
everything seems to be working OK now.
I'll try to add the results of the run kosole command.Thanks again for the 
help,Wayne.


[bugs.kde.org quoted mail]

_________________________________________________________________
Dave vs. Carl: The Insignificant Championship Series. 
Comment 5 Kurt Pfeifle 2007-01-13 06:20:17 UTC
*** Bug has been marked as fixed ***.
Comment 6 Kurt Pfeifle 2007-01-13 06:31:24 UTC
This one is wrong, my bad! Instead of:

   lpstat -p homeprinter -l

it should swap parameters on the commandline, order is signifacant here:

   lpstat -l -p homeprinter

This one was correct, but you changed uppercase "-W" to lowercase "-w", and the pipe symbol "|" to a backslash "\":

   lpstat -W completed -o homeprinter | tail -n 2 

You are saver if you copy and paste this.  :-)
But it is not important any more, now that you can print OK.   :-)
Comment 7 John Layt 2008-12-31 20:40:25 UTC
Closing old Resolved status bug.