Ubuntu
gtk+2.0 package

evolution 2.10.0 won't print to network printer

Bug #104958 reported by Alan Hoffman
2
Affects Status Importance Assigned to Milestone
GTK+
Fix Released
Medium
gtk+2.0 (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

This is 7.04 beta clean install. Two printers installed, one local and one network via SMB to windows XP box.

Evolution can see and print to the local printer. Network printer appears in dialog box, but 'Print' button is grayed out. Other applications can print to the network printer. This configuration used to work in Edgy.

Here's my /etc/cups/printers.conf:

# Printer configuration file for CUPS v1.2.8
# Written by cupsd on 2007-04-07 18:43
<Printer CanonFaxGS>
Info CanonFaxGS
Location
DeviceURI smb://alan:@BART/CanonFAX_GS
State Idle
StateTime 1175996085
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-job
</Printer>
<Printer DeskJet-5550>
Info
Location
DeviceURI hp:/par/deskjet_5550?device=/dev/parport0
State Idle
StateTime 1175996636
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-job
</Printer>

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug. Can you use the network printer with gtk-demo? What other application did you try?

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Unconfirmed → Needs Info
Revision history for this message
Alan Hoffman (alan426) wrote :

Thanks for your response. Yes, the same problem happens in
evince and gtk-demo. Printing works ok in gimp, firefox, and oog.

Revision history for this message
Alan Hoffman (alan426) wrote :

Correction ... OOo = OpenOffice, not oog.

Revision history for this message
Sebastien Bacher (seb128) wrote :

That's a GTK bug then, likely an upstream one. Would be nice if somebody with a such setup could work with upstream on it

Changed in evolution:
status: Needs Info → Unconfirmed
Revision history for this message
Alan Hoffman (alan426) wrote :

I filed a bug report on bugzilla.gnome.org. Might as well close this one.

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you have the upstream bug number?

Changed in gtk+2.0:
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

closing this one since the bug has been opened upstream but the submitter didn't give the number

Changed in gtk+2.0:
status: Incomplete → Invalid
Revision history for this message
Alan Hoffman (alan426) wrote :

Oops, sorry. bug #429845

Andreas Moog (ampelbein)
Changed in gtk+2.0:
status: Invalid → Confirmed
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: Unknown → New
Revision history for this message
Sebastien Bacher (seb128) wrote :

the upstream bug you indicated is a gnome-cups-manager one which is not used currently in ubuntu

Changed in gtk+2.0:
status: Confirmed → Incomplete
Revision history for this message
Alan Hoffman (alan426) wrote :

I give up. I am a lay user, not a developer. I filed the bug to be helpful and was told to move it upstream. I had to guess what "upstream" meant. Other users on that page confirmed the bug. Now, in September, you say it's in the wrong place. I don't know what else to do. A more explicit suggestion about where and how I should handle this would be welcome, rather than telling me that I did it wrong.

I understand that as a developer, you need to focus on the projects and bodies of code that you are more familiar with. I also understand that you are possibly donating your time to this project. However, there is only so much "homework" and expert knowledge you can expect from an average user. I've reach my limit.

With utmost respect & wishing you well with the project ...

Revision history for this message
Sebastien Bacher (seb128) wrote :

The question was just to know why the upstream bug was on gnome-cups-manager and not gtk, seems to be an error so I've reassigned it to gtk now, would be interesting to know if the bug is fixed in intrepid if you can try a current version CD

Changed in gtk+2.0:
status: Incomplete → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
status: New → Fix Released
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

Changed in gtk+2.0 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount) wrote :

Closing then as no further information has been provided. Thanks for reporting.

Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in gtk:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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