From kde-core-devel  Thu May 25 09:10:28 2006
From: Andras Mantia <amantia () kde ! org>
Date: Thu, 25 May 2006 09:10:28 +0000
To: kde-core-devel
Subject: Kicker crash with compiz
Message-Id: <200605251210.28405.amantia () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=114854844114914
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1953406.YNvHo2vR4P"

--nextPart1953406.YNvHo2vR4P
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Hi,

 Today I played with Xgl and compiz and there are two annoying bugs:
=2D sometimes menus stop to appear (especially after=20
connecting/disconnecting to the internet using kppp)
=2D kicker crashes on disconnect from the internet


The latter one at least gives me a backtrace, so there is a bigger=20
chance to find what's wrong:

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47456798671184 (LWP 4721)]
[KCrash handler]
#5  0x00002b2962209ed6 in QXEmbed::x11Event (this=3D0x9de740,=20
e=3D0x7fff491b8720)
    at /data/development/sources/kde-3.5/kdelibs/kdeui/qxembed.cpp:1060
#6  0x00002b29634e8ae4 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#7  0x00002b29634f822f in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#8  0x00002b29635566a1 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#9  0x00002b296355654a in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#10 0x00002b29660a0e54 in kdemain ()
   from /data/kde-35/lib64/libkdeinit_kicker.so
#11 0x0000000000407daa in launch (argc=3D1, _name=3D0x51e140 "kicker",=20
args=3D0x0,=20
    cwd=3D0x0, envc=3D0, envs=3D0x0, reset_env=3Dfalse, tty=3D0x0,=20
avoid_loops=3Dfalse,=20
    startup_id_str=3D0x40becf "0")
    at /data/development/sources/kde-3.5/kdelibs/kinit/kinit.cpp:639
#12 0x0000000000409a92 in main (argc=3D2, argv=3D0x7fff491b8ff8,=20
    envp=3D0x7fff491b9010)
    at /data/development/sources/kde-3.5/kdelibs/kinit/kinit.cpp:1839

kdeui/qxembed.cpp:1060 contains: "if( !d->xplain )".  This cannot crash=20
only if d is NULL or there is some other memory corruption before. d=20
cannot be NULL, only if the QXEmbed::x11Event( XEvent* e) is called=20
*after* the QXEmbed object is destroyed.=20

My question: can this really happen or the problem is at completely=20
different place, just that it appears here?

Andras

=2D-=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

--nextPart1953406.YNvHo2vR4P
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBEdXSETQdfac6L/08RArVJAKC573+Xxp7/u/Y8c/cjiceFR9tdkACfdJRR
6AHR40DlXabSdTj3yzNt6Ic=
=w8xb
-----END PGP SIGNATURE-----

--nextPart1953406.YNvHo2vR4P--