Bug#485597: Without spell checking psi works

2008-06-19 Thread Marcin Trybus
Package: psi
Version: 0.11-8
Followup-For: Bug #485597


I disabled spell checking and apparently psi works, or at least
doesn't crach right away. My guess is that it's some library
incompatibility, since libqt4 was updated a few times recently.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (50, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages psi depends on:
ii  libaspell150.60.5-2.2GNU Aspell spell-checker runtime l
ii  libc6  2.7-12GNU C Library: Shared libraries
ii  libgcc11:4.3.1-2 GCC support library
ii  libqca22.0.0-4   libraries for the Qt Cryptographic
ii  libqt4-gui 4.4.0-3   transitional package for Qt 4 GUI 
ii  libqt4-network 4.4.0-3   Qt 4 network module
ii  libqt4-qt3support  4.4.0-3   Qt 3 compatibility library for Qt 
ii  libqt4-xml 4.4.0-3   Qt 4 XML module
ii  libqtcore4 4.4.0-3   Qt 4 core module
ii  libstdc++6 4.3.1-2   The GNU Standard C++ Library v3
ii  libx11-6   2:1.1.4-2 X11 client-side library
ii  libxss11:1.1.3-1 X11 Screen Saver extension library
ii  zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime

Versions of packages psi recommends:
ii  libqca2-plugin-ossl   0.1~20070904-3 QCA OSSL plugin for libqca2
ii  sox   14.0.1-2+b1Swiss army knife of sound processi

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Bug#485597: Without spell checking psi works

2008-06-19 Thread Jan Niehusmann
On Thu, Jun 19, 2008 at 02:48:52PM +0200, Marcin Trybus wrote:
 I disabled spell checking and apparently psi works, or at least
 doesn't crach right away.

The segfault happens in the code which draws the red line below
unknown words. Therefore, with spell checking disabled, psi won't crash.
(At least not because of this bug *g*)

 My guess is that it's some library
 incompatibility, since libqt4 was updated a few times recently.

Sure, the fact that downgrading qt helps points in that direction. But
there were no related changes in the relevant versions of qt, therefore
it's not obvious where to look for the cause.

Jan



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]