Print dialog - getting printer information failed

Bug #1506490 reported by mj
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
High
gtk+3.0 (Ubuntu)
Fix Released
Medium
Unassigned
Nominated for Trusty by Mathew Hodson

Bug Description

Running Ubuntu Mate 14.04 a number of printers fail when used from the print dialog. However they can be printed to successfully from LIbreOffice and can also have a test page sent to them.

When using the system print dialog the status of the printer is set to:

'Getting printer information failed'

And the Print button is disabled.

Tags: trusty
Revision history for this message
nadrimajstor (ipejic) wrote :

Could you please provide one simple set of exact basic steps needed to repeat the bug?

Changed in ubuntu-mate:
status: New → Incomplete
Revision history for this message
mj (maut) wrote :

This is actually quite hard to pin down. We have a print server with 38 printers and the machines browse the print server by putting the following in /etc/cups/client.conf

ServerName printserver.example.com

7 out of the 38 printers report the 'Getting printer information failed' error. We believe this to be a bug in the print dialog as an Linux Mint 13 system can print to all the printers just fine. Furthermore, applications that do not use the system print dialog can also print.

Basic steps are:

1. Open a MATE application e.g. Pluma
2. Click File->Print
3. Select a printer
4. Printer status changes to 'Getting printer information failed' and print button is disabled.

Revision history for this message
nadrimajstor (ipejic) wrote :

https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1473006 does mention upstream bug fix `gtk print dialog shows "Getting printer information failed" for cups remote printer`

Changed in ubuntu-mate:
status: Incomplete → New
Revision history for this message
mj (maut) wrote :

Will this get merged into 14.04 at some point in the near future or are alternative workarounds needed?

Revision history for this message
Mathew Hodson (mhodson) wrote :

Assuming that this is the same bug in gtk, I'm leaving this open to SRU the fix to gtk 3.10.8 on Trusty.

The other bug is for gtk 3.14 and probably contains changes that wouldn't be good for Trusty.

Changed in gtk+3.0 (Ubuntu):
importance: Undecided → Medium
tags: added: trusty
Revision history for this message
Sebastien Bacher (seb128) wrote :

that issue should be fixed in the current gtk version, closing

Changed in gtk+3.0 (Ubuntu):
status: New → Triaged
affects: gtk+3.0 (Ubuntu) → ubuntu
Changed in ubuntu:
status: Triaged → Fix Released
affects: ubuntu → gtk+3.0 (Ubuntu)
Revision history for this message
Sebastien Bacher (seb128) wrote :

if somebody wants to see that SRUed to trusty a first good step would be to make the bug compliant with https://wiki.ubuntu.com/StableReleaseUpdates (having a rational, test case, regression potential in the description)

Changed in gtk:
importance: Unknown → High
status: Unknown → Fix Released
no longer affects: ubuntu-mate
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.