On Thu, Aug 17, 2006 at 10:20:08PM -0300, Maximiliano Curia wrote:
> tags 381919 +moreinfo
> thanks
> 
> Hello,
> 
> I can't reproduce this bug. It may be due to a configuration file of a 
> previous incompatible version

I don't recall ever using qgo before.  But if you want an strace log, I
can provide it too.

> or to problem already fix in sid.
> 
> Here the output of reportbug qgo --template
> [...]

Not exactly the same as mine [1].   This would make me think libqt is in fault,
but looking at the changelog [2] it doesn't look like they fixed our crash in
-3.

Is anyone else able to reproduce this?  Does someone make sense out of the
backtrace I sent before?

[1] diff output:

--- old 2006-08-18 11:45:28.000000000 +0200
+++ new 2006-08-18 11:45:36.000000000 +0200
@@ -1,15 +1,15 @@
 libaudio2                   1.8-1
-libc6                       2.3.6-15
+libc6                       2.3.6-19
 libfontconfig1              2.3.2-7
 libfreetype6                2.2.1-2
-libgcc1                     1:4.1.1-5
+libgcc1                     1:4.1.1-10
 libice6                     1:1.0.0-3
 libjpeg62                   6b-13
 libpng12-0                  1.2.8rel-5.2
-libqt3-mt                   3:3.3.6-2
+libqt3-mt                   3:3.3.6-3
 libsm6                      1:1.0.0-4
-libstdc++6                  4.1.1-5
-libx11-6                    2:1.0.0-7
+libstdc++6                  4.1.1-10
+libx11-6                    2:1.0.0-8
 libxcursor1                 1.1.5.2-5
 libxext6                    1:1.0.0-4
 libxft2                     2.1.8.2-8

[2] http://packages.qa.debian.org/q/qt-x11-free/news/20060723T180249Z.html

-- 
Robert Millan

My spam trap is [EMAIL PROTECTED]  Note: this address is only intended for
spam harvesters.  Writing to it will get you added to my black list.


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

Reply via email to