Bug#494349: libqt3-mt: throws errors and sometimes crashes X

2011-01-30 Thread booiiing
Hi there,

I didn't have this problem for some time now and cannot reproduce it
with my current versions.
Build Date: 02 December 2010  01:10:32AM
xorg-server 2:1.7.7-10 (Julien Cristau )

Best regards,
Patric



-- 
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/AANLkTi=uigxs3j24h+lfgl6rvcphhjrclza1wp6_b...@mail.gmail.com



Bug#494349: libqt3-mt: throws errors and sometimes crashes X

2011-01-28 Thread Cyril Brulebois
Hi,

booiiing  (12/08/2008):
> i use the closed-source driver by nvidia, version
> x86_64-173.14.12-pkg2, the kernel-module is compiled by the
> installer using the boxed kernel 2.6.26-2 and its headers. for the
> first trace see the end of this mail.

still reproducible with an X stack from squeeze/sid, or from
experimental?

KiBi.


signature.asc
Description: Digital signature


Bug#494349: libqt3-mt: throws errors and sometimes crashes X

2008-08-12 Thread booiiing
2008/8/12 Michel Dänzer <[EMAIL PROTECTED]>:
> On Mon, 2008-08-11 at 22:32 +0200, booiiing wrote:
>> 2008/8/9 booiiing <[EMAIL PROTECTED]>:
>> > 2008/8/9 Julien Cristau <[EMAIL PROTECTED]>:
>> >> No, it's a bug in X.  Are you using a compositing manager? Which one?
>> > deactivating it didn't change anything, however.
> Well, at least compResizeWindow() can't really be involved anymore
> without a compositing manager. It would be good to get gdb backtraces
> for both cases. BTW, which video driver are you using?
i use the closed-source driver by nvidia, version
x86_64-173.14.12-pkg2, the kernel-module is compiled by the installer
using the boxed kernel 2.6.26-2 and its headers. for the first trace
see the end of this mail.

>> > but i'll try to restart X with composite completely disabled.
>> i tried some things now, but nothing helped. the guis are still
>> malformed and i still get those error, although it seems to me that
>> there are less of them with composite disabled.
>> what worries me, is that my Xorg.0.log says
>> (**) Extension "Composite" is disabled
>> and later
>> (II) Initializing built-in extension COMPOSITE
> No worries, the latter is a bit confusing and doesn't mean the extension
> is actually enabled. You can verify it with
> xdpyinfo|grep Composite
ok, verified. thank you.

it seems that without the composite-manager the apps don't crash x
anymore, however they're still not usable.
i ran qtconfig-qt3 in gdb and set a breakpoint to
QTextParagraph::lineInfo. here is the trace:

#0  QTextParagraph::lineInfo (this=0x1c85cb0, l=0, [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]) at kernel/qrichtext_p.cpp:554
#1  0x7f4a2e77a79d in QTextParagraph::paint (this=0x1c85cb0,
[EMAIL PROTECTED], [EMAIL PROTECTED], cursor=0x0, drawSelections=false,
clipx=0, clipy=0, clipw=196, cliph=520) at kernel/qrichtext.cpp:4623
#2  0x7f4a2e77b2ec in QTextDocument::drawParagraph (this=0x7fff370234e0,
p=0x7fff370237f0, parag=0x1c85cb0, cx=0, cy=0, cw=196, ch=520,
[EMAIL PROTECTED], [EMAIL PROTECTED], drawCursor=false,
cursor=0x0, resetChanged=true) at kernel/qrichtext.cpp:3240
#3  0x7f4a2e77bc4d in QTextDocument::draw (this=0x1c804f0,
p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520, [EMAIL PROTECTED],
onlyChanged=false, drawCursor=false, cursor=0x1d58070, resetChanged=true)
at kernel/qrichtext.cpp:3300
#4  0x7f4a2e855d5c in QTextEdit::paintDocument (this=0x1c7d120,
drawAll=true, p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520)
at widgets/qtextedit.cpp:1059
#5  0x7f4a2e8698ee in QTextEdit::drawContents (this=0x1c85cb0,
p=0x7fff370237f0, cx=0, cy=0, cw=196, ch=520) at widgets/qtextedit.cpp:1081
#6  0x7f4a2e81c8c7 in QScrollView::viewportPaintEvent (this=0x1c7d120,
pe=0x7fff37023d00) at widgets/qscrollview.cpp:1709
#7  0x7f4a2e81dc33 in QScrollView::eventFilter (this=0x1c7d120,
obj=0x1c7e0a0, e=0x7fff37023d00) at widgets/qscrollview.cpp:1492
#8  0x7f4a2e867295 in QTextEdit::eventFilter (this=0x1c7d120, o=0x1c7e0a0,
e=0x7fff37023d00) at widgets/qtextedit.cpp:3030
#9  0x7f4a2e725972 in QObject::activate_filters (this=0x1c7e0a0,
e=0x7fff37023d00) at kernel/qobject.cpp:906
#10 0x7f4a2e7259c7 in QObject::event (this=0x1c7e0a0, e=0x7fff37023d00)
at kernel/qobject.cpp:738
#11 0x7f4a2e756df3 in QWidget::event (this=0x1c85cb0, e=0x0)
at kernel/qwidget.cpp:4681
#12 0x7f4a2e6d0953 in QApplication::internalNotify (
this=, receiver=0x1c7e0a0, e=0x7fff37023d00)
at kernel/qapplication.cpp:2638
#13 0x7f4a2e6d162e in QApplication::notify (this=0x7fff37024510,
receiver=0x1c7e0a0, e=0x7fff37023d00) at kernel/qapplication.cpp:2526
#14 0x7f4a2e6a7f11 in QWidget::repaint (this=0x1c7e0a0, [EMAIL PROTECTED],
erase=false) at kernel/qapplication.h:523
#15 0x7f4a2e6d20d5 in QApplication::sendPostedEvents (receiver=0x0,
event_type=0) at kernel/qapplication.cpp:3299
#16 0x7f4a2e6869dd in QEventLoop::processEvents (this=0x1c3ff80, flags=4)
at kernel/qeventloop_x11.cpp:147
#17 0x7f4a2e6e5001 in QEventLoop::enterLoop (this=0x1c85cb0)
at kernel/qeventloop.cpp:201
#18 0x7f4a2e6e4eb2 in QEventLoop::exec (this=0x1c85cb0)
at kernel/qeventloop.cpp:148
#19 0x0040f26d in main (argc=1, argv=)
at main.cpp:44


Bug#494349: libqt3-mt: throws errors and sometimes crashes X

2008-08-12 Thread Michel Dänzer
On Mon, 2008-08-11 at 22:32 +0200, booiiing wrote:
> 2008/8/9 booiiing <[EMAIL PROTECTED]>:
> > 2008/8/9 Julien Cristau <[EMAIL PROTECTED]>:
> >> No, it's a bug in X.  Are you using a compositing manager? Which one?
> > deactivating it didn't change anything, however. 

Well, at least compResizeWindow() can't really be involved anymore
without a compositing manager. It would be good to get gdb backtraces
for both cases. BTW, which video driver are you using?

> > but i'll try to restart X with composite completely disabled.
> i tried some things now, but nothing helped. the guis are still
> malformed and i still get those error, although it seems to me that
> there are less of them with composite disabled.
> 
> what worries me, is that my Xorg.0.log says
> (**) Extension "Composite" is disabled
> and later
> (II) Initializing built-in extension COMPOSITE

No worries, the latter is a bit confusing and doesn't mean the extension
is actually enabled. You can verify it with

xdpyinfo|grep Composite


-- 
Earthling Michel Dänzer   |  http://tungstengraphics.com
Libre software enthusiast |  Debian, X and DRI developer



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



Bug#494349: libqt3-mt: throws errors and sometimes crashes X

2008-08-11 Thread booiiing
2008/8/9 booiiing <[EMAIL PROTECTED]>:
> 2008/8/9 Julien Cristau <[EMAIL PROTECTED]>:
>> No, it's a bug in X.  Are you using a compositing manager? Which one?
> deactivating it didn't change anything, however. but i'll try to
> restart X with composite completely disabled.
i tried some things now, but nothing helped. the guis are still
malformed and i still get those error, although it seems to me that
there are less of them with composite disabled.

what worries me, is that my Xorg.0.log says
(**) Extension "Composite" is disabled
and later
(II) Initializing built-in extension COMPOSITE

so maybe composite isn't really disabled in my x-server?

i am starting to get a bit worried about this, because reinstalling
this machine isn't really an option :/

kind regards,
patric



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