FS#10690 - gedit and evince do not print

Attached to Project: Arch Linux
Opened by Josh Valdez (ExxonValdeez) - Wednesday, 18 June 2008, 23:54 GMT
Last edited by Jan de Groot (JGC) - Saturday, 21 June 2008, 14:33 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
I cannot seem to get either gedit or evince to print. I have recompiled both from source, tried using the abs, and recompiled libgnomeprint and libgnomecups. I have all the libgnome print libraries installed as well which would prevent them from printing. I tried recompiling cups using the abs and that did not work as well. I have had these same problems on my x86_64 machine and my i686 laptop.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:
Attempt to print documents from gedit or evince.
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 21 June 2008, 14:33 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed in gtk 2.12.10-3.
Comment by Glenn Matthys (RedShift) - Thursday, 19 June 2008, 07:10 GMT
Have you tried printing from some other application? You are 100% sure your printer is working & configured correctly? What doe the cups logs say?
Comment by Josh Valdez (ExxonValdeez) - Thursday, 19 June 2008, 07:19 GMT
I am sorry. I should have provided more information. Yes, I am sure my printer is configured and working. It is setup over IPP with an HP driver. Openoffice has no problem printing as well as Firefox. The cups logs seem to indicate that jobs were never started after attempting to print from either evince or gedit. After "printing" a file in either, a job fails to show up in both the localhost cups jobs screen and the print server jobs screen.
Comment by Glenn Matthys (RedShift) - Thursday, 19 June 2008, 07:22 GMT
Can you provide us these logs?
Comment by Jan de Groot (JGC) - Thursday, 19 June 2008, 07:28 GMT
Looks equal to this bugreport:
https://bugzilla.redhat.com/show_bug.cgi?id=248245

This has been fixed in upstream SVN recently, I'll add a patch to gtk2 soon.
Comment by Josh Valdez (ExxonValdeez) - Thursday, 19 June 2008, 07:41 GMT
Jan de Groot: Yes, that is it. Thanks! I tried to find something similar in bugs.gnome.org but couldn't. That report describes the same problem I am having.
Comment by Glenn Matthys (RedShift) - Thursday, 19 June 2008, 07:46 GMT
@JGC: why not wait untill the relevant software makes a new release? This looks important so it'll certainly make it in the next release...
Comment by Jan de Groot (JGC) - Thursday, 19 June 2008, 07:49 GMT
GTK releases can take 2-3 months before a minor update is done. Given the fact that 2.12.10 was released only two weeks ago and we're already applying some important patches, I don't think we should wait for 2.12.11. These patches are easy to get: they're in SVN for the next release, are approved for the stable branch and are fully documented with changelogs and bugreports.
Comment by Glenn Matthys (RedShift) - Thursday, 19 June 2008, 07:56 GMT
Ok, I'll request a close once the package has been updated. Mention in the PKGBUILD that the patch should be revised upon next release of GTK.

Loading...