[Bug 271509] New: Compiz "KDE/Qt Event Loop" crashes when logging into Unity

[Daniel Hahler]

https://bugs.kde.org/show_bug.cgi?id=271509

           Summary: Compiz "KDE/Qt Event Loop" crashes when logging into
                    Unity
           Product: kde
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: NEW
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: kde-bugzilla at thequod.de


Application: compiz (0.0.1)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic i686
Distribution: Ubuntu 11.04

-- Information about the crash:
Logging into Unity (used with Ubuntu Natty (11.04)), triggers this crash.

After the KDE Crash reporting dialog pops up, Unity apparently is getting
restarted and the same crash will happen again.

This results in an endless loop, where each iteration adds another kde crash
handler instance.

I had to "metacity --replace" from a VT and kill the running compiz instance.

-- Backtrace:
Application: Compiz KDE event loop plugin (compiz), signal: Segmentation fault
[Current thread is 1 (Thread 0xb78cb760 (LWP 6093))]

Thread 3 (Thread 0xb78c9b70 (LWP 6096)):
#0  0x005d73c9 in g_main_context_query () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#1  0x005d7e8c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#2  0x005d892b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x00422304 in ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
#4  0x006012df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x00181e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#6  0x00cc673e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb271cb70 (LWP 6102)):
#0  0x00725416 in __kernel_vsyscall ()
#1  0x00186834 in pthread_cond_timedwait@@GLIBC_2.3.2 () from
/lib/i386-linux-gnu/libpthread.so.0
#2  0x0091ef0e in ?? () from /usr/lib/i386-linux-gnu/libgthread-2.0.so.0
#3  0x005ab42c in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x005abf6d in g_async_queue_timed_pop () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x00603980 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0x006012df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0x00181e99 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#8  0x00cc673e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb78cb760 (LWP 6093)):
[KCrash Handler]
#7  0x03c9ed21 in QApplicationPrivate::notify_helper (this=0x9240bf8,
receiver=0x915ce70, e=0xbfa8cb64) at kernel/qapplication.cpp:4462
#8  0x03ca38ce in QApplication::notify (this=0x923c840, receiver=0x915ce70,
e=0xbfa8cb64) at kernel/qapplication.cpp:3862
#9  0x029ef3ca in KApplication::notify (this=0x923c840, receiver=0x915ce70,
event=0xbfa8cb64) at ../../kdeui/kernel/kapplication.cpp:311
#10 0x0183c0bb in QCoreApplication::notifyInternal (this=0x923c840,
receiver=0x915ce70, event=0xbfa8cb64) at kernel/qcoreapplication.cpp:731
#11 0x00913f7f in SocketObject::callback() () from /usr/lib/compiz/libkde.so
#12 0x00914134 in ?? () from /usr/lib/compiz/libkde.so
#13 0x0806fa3e in CompWatchFd::internalCallback(Glib::IOCondition) ()
#14 0x0014cf85 in Glib::IOSource::dispatch(sigc::slot_base*) () from
/usr/lib/libglibmm-2.4.so.1
#15 0x0014cab9 in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*),
void*) () from /usr/lib/libglibmm-2.4.so.1
#16 0x005d7aa8 in g_main_context_dispatch () from
/lib/i386-linux-gnu/libglib-2.0.so.0
#17 0x005d8270 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#18 0x005d892b in g_main_loop_run () from /lib/i386-linux-gnu/libglib-2.0.so.0
#19 0x0014dff5 in Glib::MainLoop::run() () from /usr/lib/libglibmm-2.4.so.1
#20 0x0806ec8b in CompScreen::eventLoop() ()
#21 0x08066e48 in main ()

Possible duplicates by query: bug 271412, bug 271393, bug 271306, bug 271254,
bug 271201.

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.