Bug#494349: libqt3-mt: throws errors and sometimes crashes X
On Fri, Aug 08, 2008 at 06:12:59PM +0200, Patric Schenke wrote:
> Package: libqt3-mt
> Version: 3:3.3.8b-5
> Severity: grave
> Justification: renders package unusable
> QT3-Programs throw errors like "QTextParagraph::lineInfo: line 1 out of
> range!" at me and sometimes (about every second time) crash the whole
> X-Server when started. If they don't crash, the GUI is completely
> screwed up and unusable.
> I already tried to feed variations of that error to google, but it only
> came up with one result, which was in a language I don't understand.
> I also discussed the problem in #qt on freenode, because even
> qtconfig-qt3 fails to run and I supposed it might be related to QT
> itself. A wild guess there aimed at some font-rendering-infrastructure
> to be broken due to a system-update.
> Also, i tried to discuss the problem in #debian and got the advice to
> pstack the processes, however, pstack is not available on AMD64.
> Other toolkits, even QT4, work fine for me. Unfortunately I use QT3
> quite rarely, so I can't tell which update broke it :(
> Additionally, here is the trace of an X-Server that crashed when trying
> to start qtconfig-qt3:
> 0: /usr/X11R6/bin/X(xf86SigHandler+0x6a) [0x49162a]
> 1: /lib/libc.so.6 [0x7fb4a068ff80]
> 2: /usr/X11R6/bin/X [0x505326]
> 3: /usr/X11R6/bin/X(compResizeWindow+0xfb) [0x4c559b]
> 4: /usr/X11R6/bin/X(ConfigureWindow+0xbdd) [0x43c8ad]
> 5: /usr/X11R6/bin/X(ProcConfigureWindow+0x8d) [0x44ef2d]
> 6: /usr/X11R6/bin/X(Dispatch+0x342) [0x44f852]
> 7: /usr/X11R6/bin/X(main+0x4a5) [0x436bd5]
> 8: /lib/libc.so.6(__libc_start_main+0xe6) [0x7fb4a067c1a6]
> 9: /usr/X11R6/bin/X(FontFileCompleteXLFD+0x281) [0x435e99]
> Fatal server error:
> Caught signal 11. Server aborting
> I saved the complete log, so I can attach it later if needed.
Looking at this backtrace it looks more like a problem with your xorg system
than a qt one :?
Looking at your apt policy line:
> -- System Information:
> Debian Release: lenny/sid
> APT prefers testing
> APT policy: (900, 'testing'), (400, 'stable'), (300, 'unstable')
> Architecture: amd64 (x86_64)
i guess you are using mainly testing with some unstable. Was this problem
triggered after some special update :?
Current version of qt3 was uploaded months ago...