setting a default printer does not work

Bug #38149 reported by Timo Aaltonen
14
Affects Status Importance Assigned to Milestone
gnome-cups-manager (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

system - administration - printing, and then select a printer to be default does not work. We have a central CUPS server that the clients connect to, and a lot of printers.. it would be nice to be able to set a default printer (if only for the current host)

d4ft (d4ft3d)
Changed in gnome-cups-manager:
status: Unconfirmed → Needs Info
Revision history for this message
era (era) wrote :

Are you saying that right-clicking on the printer you want and selecting "Make Default" does not make it the default printer? Are you still able to print on that printer? Do you see any error messages if you view the printer's property sheet?

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Yes, that's what I mean.

There are no errors in properties (?).

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

Same sorts of problems here:

* Never remembers default printer (from gnome-print manager)
* Doesn't show paper sizes or dpi available for remote printers in gnome-print manager.
* Always shows as printer@host, even if cups.d/browse.conf contains
  BrowseShortNames Yes
* Seems confused between printers and classses

In summary: This is highly regressed from breezy or current gentoo.

# roo is my central print server
# Dapper host
lpstat -t
scheduler is running
system default destination: laser@roo
members of class lp@roo:
        unknown
device for Colour@roo: ipp://eeyore.daria.co.uk:631/printers/Colour@roo
device for laser@roo: ipp://eeyore.daria.co.uk:631/printers/laser@roo
device for lp@roo: ipp://eeyore.daria.co.uk:631/classes/lp@roo

# from gentoo box

lpstat -t
scheduler is running
system default destination: laser
members of class lp:
        laser
device for Colour: ipp://roo:631/printers/Colour
device for laser: ipp://roo:631/printers/laser

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

On reflection, maybe these are CUPS (vice gnome-p-m) bugs. Sorry for any confusion. The initial title just brought out my whole fustrtaion with the state of printing in dapper.

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

Further to the above rants, having done my daily dist-upgrade 2006-04-14 appears to have done a lot to rectify the situation:

1. Initially the dialogue is ppoulated with foo@bar .. If I sleect "Advanced" and type in ipp://roo:631 ... etc, the dialogue will automagically change and create a local printer with the correct ppd details. Yeah. Paper size!

2. Log out/in. It remembers the deault. cool.

3. Now cupsd is premanantly taking 7% (AMD64 box) to 16% (PPC box) of the CPU. Think I'd like my cycles back.

Revision history for this message
Jonathan Hudson (jh+lpd) wrote :

Further: Redid my whole cups setup.

1. Removed all the policy stuff from cupsd.conf. This allowed gnome-cups-manager to 'see' the ppd stuff.

2. stopped cupsys

3. deleted /etc/cups/printers.conf, /etc/printcap and, importantly, /var/cache/cups/remote.cache (this is key)/

4. How everything works *until I change something using gnome-cups-manager*, which rewrites /var/cache/cups/remote.cache, may cause cups to crash, and, on restart I have laser@remotehost vice 'laser', and no default.

Revision history for this message
anime4christ (anime4christ) wrote :

Yup, same thing here, can't set default printer, but I think this may be a CUPS problem. The CUPS web interface gives me an unknown error when trying to set the default printer (not to mention that the web interface doesn't let me log in to perform administrative tasks).

Revision history for this message
ARR (alanrr-sr) wrote :

same bug of 34112??

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for gnome-cups-manager (Ubuntu) because there has been no activity for 60 days.]

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.