Your message dated Fri, 04 Jan 2008 11:13:27 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#452162: hmmm... solved but maybe it's still a bug?
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libgtk2.0-0
Version: 2.12.1-3
Severity: important
Beginning somewhere around November 19, 2007 some printing has broken
and I think its related to gtkPrint. I realise there are lots of
printing changes going on in deb right now, but I think the commonality
I'm seeing in symptoms points to gtkPrint.
Specifically, in gnucash (which uses both gnomeprint and gtkprint) check
printing is broken. For each check printed, a blank page is printed.
This result is consistent whether printing to a file (pdf or ps) or to an actual
printer. Check printing in gnucash uses gtkprint. Meanwhile, report
printing, using gnomeprint, functions just fine. I've also tested this
on gnucash svn trunk with the same results.
In gnumeric, which uses gtkprint, printing is completely broken. It
causes an "foomatic-rip failed" error in cups. There is more to the
gnumeric issue, I think. I downgraded out of the ghostscript package
into the gs-* packages and the foomatic-rip failure went away, and
gnumeric then printed only blank pages.
I tried to downgrade libgtk, but that didn't seem to help, which
suggests it may be some other dependency involved. But I think it all
stems from gtkprint.
Please let me know what I can do to help debug this. I'm happy to
downgrade packages, or try different packages to help diagnose this.
thanks
A
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.22-3-k7 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libgtk2.0-0 depends on:
ii libatk1.0-0 1.20.0-1 The ATK accessibility toolkit
ii libc6 2.6.1-6 GNU C Library: Shared libraries
ii libcairo2 1.4.10-1 The Cairo 2D vector graphics libra
ii libcomerr2 1.40.2-1 common error description library
ii libcupsys2 1.3.4-1 Common UNIX Printing System(tm) -
ii libfontconfig1 2.5.0-2 generic font configuration library
ii libglib2.0-0 2.14.3-1 The GLib library of C routines
ii libgnutls13 2.0.4-1 the GNU TLS library - runtime libr
ii libgtk2.0-common 2.12.1-3 Common files for the GTK+ graphica
ii libjpeg62 6b-14 The Independent JPEG Group's JPEG
ii libkrb53 1.6.dfsg.3~beta1-2 MIT Kerberos runtime libraries
ii libpango1.0-0 1.18.3-1 Layout and rendering of internatio
ii libpng12-0 1.2.15~beta5-3 PNG library - runtime
ii libtiff4 3.8.2-7 Tag Image File Format (TIFF) libra
ii libx11-6 2:1.0.3-7 X11 client-side library
ii libxcomposite1 1:0.3.2-1+b1 X11 Composite extension library
ii libxcursor1 1:1.1.9-1 X cursor management library
ii libxdamage1 1:1.1.1-3 X11 damaged region extension libra
ii libxext6 1:1.0.3-2 X11 miscellaneous extension librar
ii libxfixes3 1:4.0.3-2 X11 miscellaneous 'fixes' extensio
ii libxi6 2:1.1.3-1 X11 Input extension library
ii libxinerama1 1:1.0.2-1 X11 Xinerama extension library
ii libxrandr2 2:1.2.2-1 X11 RandR extension library
ii libxrender1 1:0.9.4-1 X Rendering Extension client libra
ii zlib1g 1:1.2.3.3.dfsg-7 compression library - runtime
Versions of packages libgtk2.0-0 recommends:
ii hicolor-icon-theme 0.10-1 default fallback theme for FreeDes
ii libgtk2.0-bin 2.12.1-3 The programs for the GTK+ graphica
-- no debconf information
--- End Message ---
--- Begin Message ---
Closed by submitter suggestion.
Thomas
On Fri, 2008-01-04 at 09:28 -0800, Andrew Sackville-West wrote:
> On Fri, Jan 04, 2008 at 04:30:42PM +0100, Josselin Mouette wrote:
> > reassign 452162 gnucash
> > thanks
> >
> > Whoops, sorry for replying without reading this additional information.
> >
> > Le dimanche 25 novembre 2007 à 12:14 -0800, Andrew Sackville-West a
> > écrit :
> > > I went back to step zero. This problem showed up after a segfault in
> > > gnucash. This segfault occurred while printing checks (uses
> > > gtkprint). Subsequent instances of gnucash could no longer print
> > > checks. Since I had two machines fully-up-to-date. I decided to try a
> > > different user on the broken machine. lo and behold, no problem. :( or
> > > :) depending on your perspective. Anyway, moving ~/.gconf out of the
> > > way solved the problem.
> > >
> > > Clearly, the segfault corrupted something in ~/.gconf/* resulting in
> > > this behavior. There is probably no way to track down the segfault as
> > > it happened in an instance of gnucash that may have been up for many
> > > days and may have been up across a variety of upgrades...
> > >
> > > I have a copy of the problematic ~/.gconf available if you would
> > > like.
> >
> > This definitely looks like a bug in gnucash, and the copy of the
> > problematic gconf keys will certainly be useful to the gnucash
> > maintainer.
>
> I have that available. Well, I have the whole stinking tree available
> ;) if anyone wants it.
>
> The more I think about it, though, and the more I work on gnucash, I
> suspect this is a fleeting, one-time thing. I strongly suspect that
> instance of gnucash had been live across at least a couple significant
> updates in sid, which brought it to its knees. I don't think any app
> could be expected to gracefully recover from that kind of systemic
> change. It was an unfortunate side-effect of the crash that corrupted
> some gconf keys.
>
> This should probably be closed as unreproducible, or needinfo, or
> whatever.
>
> Oh and thanks for finally getting to this. I know it was cryptic at
> best.
>
> A
--- End Message ---
