Unable to print to a shared printer on Xenial64

Using applications, configuring, problems
Post Reply
Message
Author
p310don
Posts: 1492
Joined: Tue 19 May 2009, 23:11
Location: Brisbane, Australia

Unable to print to a shared printer on Xenial64

#1 Post by p310don »

I have a problem connecting to a printer on my home network.

The printer is a Samsung that was previously connected to Tahr32 and working fine. My other computers automatically saw that printer in CUPS and could use it.

Now I have Xenial64 on the PC attached to the printer and I cannot connect to that printer via CUPS.

The tahr version of cups was about 1.4ish I think? Now Xenial uses 2.1.3 which has some network issue I believe. Probably a security "feature". Not sure.

april

#2 Post by april »

Is cups running normally?
Can you see the printer in cups.
Check the defaults . My browser was set to "auto " which did not work

p310don
Posts: 1492
Joined: Tue 19 May 2009, 23:11
Location: Brisbane, Australia

#3 Post by p310don »

Is cups running normally?
Can you see the printer in cups.
Check the defaults . My browser was set to "auto " which did not work
Yes, CUPS is running normally.

I can see the printer on the server, not on any other PCs on the network.

What do you mean your browser was set to "auto"?

I have followed the instructions for setting up the P910nd print server. It works ok for Xen64 to Xen64, but my wife's older PC (that I'm not allowed to change, again) does not play.

When I click print test page in CUPS on that PC, it comes up with

Code: Select all

Unsupported format 'application/vnd.cups-banner'!
Not sure what that means, or why it is there.

The PC with the error is running Carolina with upgraded CUPS to 1.4.8 .

Note, this PC printed perfectly to earlier CUPS on the print server

jafadmin
Posts: 1249
Joined: Thu 19 Mar 2009, 15:10

#4 Post by jafadmin »

Thoughts:

Firewall is OFF?
PC's are set to use port 9100 RAW?
Is there a 64 v 32 bitness issue?
Is your village afflicted with voodoo or gremlins?

.

matchpoint
Posts: 168
Joined: Fri 26 Jan 2018, 20:54

#5 Post by matchpoint »

Is the new build using the old Ghostscript?

These are a few other mentions that popped up....

Unsupported format 'application/vnd.cups-raw'!

Maybe clear your /var/cache/cups directory?

foomatic?

april

#6 Post by april »

Code: Select all

Unsupported format 'application/vnd.cups-banner'!
The ppd printer file is wrong reinstall cups or update the ppd file

The defaults are Menu->Setup->Puppy Apps Defaults
Last edited by april on Mon 19 Feb 2018, 20:48, edited 2 times in total.

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#7 Post by Mike Walsh »

Just a thought, Don....and a query?

You haven't by any chance installed Chrome on there, have you.....as a .deb package? Because if you have, it'll muck up all kinds of things, and give you permissions problems throughout Pup.

Debian/Ubuntu are multi-user systems,of course, and they adjust everything for a '/home' directory.....which Pup doesn't have. Unfortunately, CUPS is often one of the victims of this.

You can find instructions for fixing this at the top of post #1 of my Chrome thread, here:-

http://www.murga-linux.com/puppy/viewtopic.php?t=107301


Mike. :wink:

p310don
Posts: 1492
Joined: Tue 19 May 2009, 23:11
Location: Brisbane, Australia

#8 Post by p310don »

Chrome is on the server. I'll check it out when I get home.

p310don
Posts: 1492
Joined: Tue 19 May 2009, 23:11
Location: Brisbane, Australia

#9 Post by p310don »

Annoyingly I had a look at the chrome issue that you suggested Mike, but I can't even get to see the permissions of initrd/pup_rw

Right click, permissions, nothing happens.

You might be right, you might be wrong, but I can't tell.

Frustrating.

Post Reply