Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-07 Thread Jan Niehusmann
Hi Sune, (Cc: to all the other addresses, because just removing the 3 patches may not give meaningfull results.) On Sun, Jul 06, 2008 at 05:51:24PM +0200, Sune Vuorela wrote: Try on a updated unstable system: apt-get source qt4-x11 open debian/patches/series with your favourite editor and

Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-07 Thread Sune Vuorela
On Monday 07 July 2008 10:40:05 Jan Niehusmann wrote: Hi Sune, (Cc: to all the other addresses, because just removing the 3 patches may not give meaningfull results.) Removing those for now. I just did a similar thing: I did not comment the three patches, but just added a single

Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-07 Thread Jan Niehusmann
On Mon, Jul 07, 2008 at 11:31:31AM +0200, Jan Niehusmann wrote: I'll try with 4.3.0-5 first, as, according to the changelog-dates, may be the version used to compile the qt packages. Direct comparison shows that the segfault occurs if libQtGui.so is compiled with gcc 4.3.0-5, and it doesn't

Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-07 Thread mmo
I've recompiled qt4-x11 with gcc version 4.3.1 (Debian 4.3.1-2). Jan's test app now works, psi still doesn't. To reproduce : remove .psi from ~ register new account enter some text in the server-name field -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe.

Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-06 Thread Sune Vuorela
Hi! I'm one of the Qt4 maintainers - but I'm not a psi user and have no real clue on how to try/retry this bug, but it would be very nice if some of you had some spare cpu cycles to spend on this problem. Try on a updated unstable system: apt-get source qt4-x11 open debian/patches/series

Bug#476217: psi vs Qt4.4.0-3 segmentation fault

2008-07-06 Thread Jan Niehusmann
On Sun, Jul 06, 2008 at 05:51:24PM +0200, Sune Vuorela wrote: I'm one of the Qt4 maintainers - but I'm not a psi user and have no real clue on how to try/retry this bug, but it would be very nice if some of you had some spare cpu cycles to spend on this problem. As another data point, this