GNOME Bugzilla – Bug 309919
evolution-2.3.4: printing does not work
Last modified: 2008-01-29 13:10:00 UTC
Version details: 2.3.4 Distribution/Version: Yellow Dog Linux 4.0.1 See gdb session below... Hopefully, this is something simple. -Joseph =============================================================== (gdb) run Starting program: /opt/garnome-2.11-20050630.2240/bin/evolution-2.4 [Thread debugging using libthread_db enabled] [New Thread 813475648 (LWP 26231)] es menu class init Detaching after fork from child process 26237. adding hook target 'source' [New Thread 825129760 (LWP 26239)] [New Thread 833518368 (LWP 26240)] (evolution-2.4:26231): Gdk-CRITICAL **: gdk_gc_set_foreground: assertion `GDK_IS _GC (gc)' failed [New Thread 843582240 (LWP 26243)] (evolution-2.4:26231): camel-WARNING **: Invalid root: '/home/jsacco/.evolution/ mail/local/Open Source.sbd/Gnome.ibex.index' (evolution-2.4:26231): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution-2.4:26231): camel-WARNING **: block size: 1024 (1024) OK (evolution-2.4:26231): camel-WARNING **: free: 0 (0 add size < 169984) OK (evolution-2.4:26231): camel-WARNING **: last: 169984 (169984 and size: 169984) OK (evolution-2.4:26231): camel-WARNING **: flags: unSYNC (evolution-2.4:26231): camel-WARNING **: Could not find key entry for word '0x00 000000': Bad file descriptor (evolution-2.4:26231): camel-WARNING **: Could not find key entry for word '0x00 000000': Bad file descriptor (evolution-2.4:26231): camel-WARNING **: Invalid root: '/home/jsacco/.evolution/ mail/local/Open Source.sbd/YDL.ibex.index' (evolution-2.4:26231): camel-WARNING **: version: TEXT.000 (TEXT.000) (evolution-2.4:26231): camel-WARNING **: block size: 1024 (1024) OK (evolution-2.4:26231): camel-WARNING **: free: 0 (0 add size < 154624) OK (evolution-2.4:26231): camel-WARNING **: last: 154624 (154624 and size: 154624) OK (evolution-2.4:26231): camel-WARNING **: flags: unSYNC [New Thread 854592288 (LWP 26245)] (evolution-2.4:26231): camel-WARNING **: Could not find key entry for word '0x30 000000': Bad file descriptor (evolution-2.4:26231): camel-WARNING **: Could not find key entry for word '0x80 000000': Bad file descriptor (evolution-2.4:26231): camel-WARNING **: Could not find key entry for word '0000 0000': Bad file descriptor requesting object classid: attachment.0x101b5038.1024.mixed.1 object_found: 1 requesting object classid: attachment.0x101b5038.1024.mixed.2 object_found: 1 requesting object classid: attachment.0x101b5038.1024.mixed.1 object_found: 1 requesting object classid: attachment.0x101b5038.1024.mixed.2 object_found: 1 [New Thread 863034144 (LWP 26250)] [New Thread 871422752 (LWP 26251)] [New Thread 879811360 (LWP 26252)] [Thread 871422752 (LWP 26251) exited] [Thread 879811360 (LWP 26252) exited] [Thread 863034144 (LWP 26250) exited] [New Thread 863034144 (LWP 26253)] [New Thread 879811360 (LWP 26254)] [New Thread 871422752 (LWP 26255)] ** (evolution-2.4:26231): WARNING **: failed request with status 200 (evolution-2.4:26231): GnomePrintCupsPlugin-WARNING **: iconv does not support p pd character encoding: ISOLatin1, trying CSISOLatin1 ** (evolution-2.4:26231): WARNING **: failed request with status 200 [Thread 871422752 (LWP 26255) exited] (evolution-2.4:26231): GnomePrintCupsPlugin-WARNING **: Unknown Duplex setting = = 'Notcapable' ** (evolution-2.4:26231): WARNING **: failed request with status 200 [Thread 879811360 (LWP 26254) exited] [Thread 863034144 (LWP 26253) exited] [New Thread 863034144 (LWP 26257)] [Thread 863034144 (LWP 26257) exited] Program received signal SIGSEGV, Segmentation fault.
+ Trace 61639
Thread 813475648 (LWP 26231)
adding printing keyword.
Looks like a gnomeprint bug.
Luis, evolution-2.3.5.1, built within a gnome-2.11.5 framework [garnome-2.11.5.1], cannot print. If you can print from evolution-2.3.x, which gnome framework are you running: * 2.10.x * 2.11.x -Joseph
I don't have a printer, nor do I use evo ATM, because I don't have an ISP that (1) provides IMAP and (2) provides several gigs of quota :) I'm just saying that from the output, this looks like a gnomeprint bug and not an evo bug. Jody?
Luis, I wish you had said "I tested it and it works" rather than "I don't have a printer". Nevertheless, I believe you are correct is asserting that is "looks like a gnomeprint bug". I got someone else on the GARNOME IRC channel to try printing from evo-2.3.5.1, built within a GNOME-2.11.5 framework [garnome-2.11.5.1]. This person successfully printed both to a network print and a PDF, which is good news. The successful test was conducted on a lintel box running a current version of archlinux. The failed test occurred on a linuxPPC running YDL_4.0.1. I would hate to think that an endian issue has crept into gnomeprint. To test your conjecture, I took evo out of the picture completely. Using ./tests/simple.c from libgnomeprint-2.11.0, I built a debug version of "simple" . I was careful to use pkg-config to fetch the correct cflags and libs. Results from running "simple": * gnome-2.11.5 framework ==> segfaults * gnome-2.10.2 framework ==> OK * gnome-2.6.0 framework ==> OK Some initial GDB probing of the gnome-2.11.5, reveals that something is amiss. For example: 67 gpc = gnome_print_job_get_context (job); (gdb) p job $1 = (GnomePrintJob *) 0x10018a80 (gdb) p *job $2 = {object = {g_type_instance = {g_class = 0x38323636}, ref_count = 892810550, qdata = 0x50}, config = 0x59, meta = 0x1, input_file = 0x0, priv = 0x7fd3a2d8} I don't [yet] know much about the libgnomeprint code, but I cannot imagine an object with a ref_count in the stratosphere. So something is very wrong. Please accept my apologies for wasting your time. -Joseph
Dude! That's why I reassigned it to gnomeprint :) No time wasted, and thanks for looking further into it. Jody, does this information shine any light on the problem?
Moving all gnome-cups-manager bugs to new product. Filter on Kjartan's spring cleaning.