LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 01-18-2011, 06:32 AM   #1
satinet
Senior Member
 
Registered: Feb 2004
Location: England
Distribution: Slackware 11, Sabayon 3.1
Posts: 1,464

Rep: Reputation: 46
Can't print - "Unable to open image file for printing!"


HI,

Since slackware 13.0 (upgraded to 13.1), I haven't been able to print anything. I can add printers no problem using the cups gui (or whatever). However any print I send to any printer fails because of:

"Unable to open image file for printing!"

I can post the whole error log if that helps, but I can't see much in it. I haven't been able to print for about 6 months, which is getting a bit annoying.

Any ideas?

Cheers

Tom

p.s, as a I lazy option I upgraded to the cups in -current, but that didn't help (although I don't think it was a very different version).
 
Old 01-18-2011, 07:31 AM   #2
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Hello satinet,
Quote:
Originally Posted by satinet View Post
..."Unable to open image file for printing!"...
which images? what are you printing? (which filetype) and out of which program?

Could you please provide more information about your hardware, printertype and how the printer is connected?

Markus
 
Old 01-18-2011, 07:55 AM   #3
satinet
Senior Member
 
Registered: Feb 2004
Location: England
Distribution: Slackware 11, Sabayon 3.1
Posts: 1,464

Original Poster
Rep: Reputation: 46
Hi,

I don't think this is a hardware problem. I get the same error message whether it's a network printer (lp), USB printer, samba printer, or serial printer. Also programmes are effected. The same printers would print using slackware 12.2 btw - no changes to the PC since then.

The Unable to open image file for printing!" comes from the cups error log. If you go in to the GUI you can also see this message.

Tom
 
Old 01-18-2011, 10:01 AM   #4
lumak
Member
 
Registered: Aug 2008
Location: Phoenix
Distribution: Arch
Posts: 799
Blog Entries: 32

Rep: Reputation: 109Reputation: 109
What printer is it make/model? what driver are you using? does the driver require compiling/did you recompile? if it's a binary, did they recompile? libpng was updated with an incompatible version that requires binaries to be re linked with it. Did you do an 'upgrade' from 12.2 to 13.0 to 13.1 or did you re install each time? Have you checked for conflicting configuration files? did you read the changes and hints file?

This problem just seems so odd to me that I'm sure anybody trying to help you is going to need as much information as possible no matter how insignificant you may feel it is.
 
Old 01-18-2011, 10:41 AM   #5
satinet
Senior Member
 
Registered: Feb 2004
Location: England
Distribution: Slackware 11, Sabayon 3.1
Posts: 1,464

Original Poster
Rep: Reputation: 46
HI,

The sypmtom is the same regardless of the printer. Any printer has the same problem. I am just using the cups drivers, not my own compiles.

I did a fresh install of 13.0. No printing after that. I have upgraded to 13.1 now via slackpg.

I think I had a read of the changes file. I don't remember "printing doesn't work" being one of changes!

Tom
 
Old 01-18-2011, 10:42 AM   #6
satinet
Senior Member
 
Registered: Feb 2004
Location: England
Distribution: Slackware 11, Sabayon 3.1
Posts: 1,464

Original Poster
Rep: Reputation: 46
root can't print either btw for the same reason.
 
Old 01-18-2011, 11:11 AM   #7
lumak
Member
 
Registered: Aug 2008
Location: Phoenix
Distribution: Arch
Posts: 799
Blog Entries: 32

Rep: Reputation: 109Reputation: 109
yes yes, but sometimes the changes and hits section contains other information that may lead you to thinking what might be wrong.

Like maybe "HP multifunction printers/scanners require the user to be part of the lp group" Which could lead you to check the permissions of the device file regardless of it being HP or not.

But being you tried as root, that's probably not the case. So lets try again...

Maybe all the printers you try require firmware?... No I think that would only be for USB connection...

Let's see... by 'every printer I try' can only assume you have tried 5 different printers and all of them are different brands and all of them have compatible default cups drivers. Well I guess I can't help with a google search on those models. Besides it's -every- printer. Which would point to a cups problem.

Which would lead me to reading the cups changelog for clues which offers nothing obvious. Or perhaps you some how got 32bit and 64bit binaries conflicting? I don't know that's a stab in the dark. I'm sure that's not the case. Either that or I would try removing all printer configurations, starting over and rebooting... or at least restarting the server. Speaking of which. I'm sure a computer reboot was already done recently because the kernel was probably updated. So that probably has nothing to do with it.

You know what? I'm stumped. I'm not on your system, I don't have the error logs, and I can't use diagnostic tools on your computer.

My only guess would be related to the issues people were having with firefox crashing. That required either a firefox or a cups upgrade. Being that a lot of things link with cups, I probably would use the latest one packaged for 13.1. i.e. cups-1.4.5 in /patches...

---

An old bug post regarding cups on fedora had something to do with the file name starting with BM. That issue was related to an improperly defined Mime type of all things. It also seems to relate to other 2 capital letter prefixes. I don't suppose you have tried various different filetypes and names?

Last edited by lumak; 01-18-2011 at 11:18 AM.
 
Old 01-18-2011, 11:42 AM   #8
markush
Senior Member
 
Registered: Apr 2007
Location: Germany
Distribution: Slackware
Posts: 3,970

Rep: Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848Reputation: 848
Using google, I find that this errormessage "Unable to open image file for printing!" is due to imagefiles which cannot be printed.

Did you check if normal *.txt or *.pdf files can be printed?

Markus
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] "Unable to open config file '//nrpe.cfg' for reading" when using netd.conf MensaWater Other *NIX 1 10-25-2010 07:24 AM
Unable to open configuration file "/etc/samba/smb.conf" Permission denied jijawm Linux - Enterprise 8 08-18-2010 11:47 AM
printing hh in hh:mm using "awk '{FS=":";print $1}'" misses first line of output!! mayankmehta83 Linux - Newbie 2 12-03-2009 02:55 AM
Trying to convert VMWare image to raw using Qemu: error - "image open" JamesHall Linux - Software 1 07-22-2008 04:59 AM
unable to open "compiled HTML Help file" rahul_khare15 Linux - Newbie 1 11-07-2007 12:48 AM


All times are GMT -5. The time now is 05:03 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration