Application: compiz ()
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 2.6.40-4.fc15.x86_64 x86_64
Distribution: "Fedora release 15 (Lovelock)"

-- Information about the crash:
- What I was doing when the application crashed:
just power on note and login
- Unusual behavior I noticed:
window managers seems to hangs up for a while
- Custom settings of the application:
compiz & emerald are installed

The crash can be reproduced every time.

-- Backtrace:
Application:  (compiz), signal: Aborted
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007fae54ef42d5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007fae54ef5beb in __GI_abort () at abort.c:93
#8  0x0000003b05a4b5ee in g_logv (log_domain=0x3ceb64eed7 "glibmm", log_level=<optimized out>, format=0x3ceb650208 "\nunhandled exception (type std::exception) in signal handler:\nwhat: %s\n", args1=0x7fff192db488) at gmessages.c:557
#9  0x0000003b05a4b682 in g_log (log_domain=<optimized out>, log_level=<optimized out>, format=<optimized out>) at gmessages.c:577
#10 0x0000003ceb642b4b in glibmm_unexpected_exception () at exceptionhandler.cc:71
#11 Glib::exception_handlers_invoke () at exceptionhandler.cc:150
#12 0x0000003ceb6430fe in Glib::Source::dispatch_vfunc (callback=<optimized out>, user_data=<optimized out>) at main.cc:896
#13 0x0000003b05a427ed in g_main_dispatch (context=0x26f7710) at gmain.c:2441
#14 g_main_context_dispatch (context=0x26f7710) at gmain.c:3014
#15 0x0000003b05a42fc8 in g_main_context_iterate (context=0x26f7710, block=<optimized out>, dispatch=1, self=<optimized out>) at gmain.c:3092
#16 0x0000003b05a4360d in g_main_loop_run (loop=0x26f7600) at gmain.c:3300
#17 0x000000000042aae2 in CompScreen::eventLoop (this=0x2654e30) at /usr/src/debug/core/src/screen.cpp:128
#18 0x000000000041ec4c in main (argc=<optimized out>, argv=0x7fff192db858) at /usr/src/debug/core/src/main.cpp:272

This bug may be a duplicate of or related to bug 275450.

Possible duplicates by query: bug 277494.

Reported using DrKonqi