Bug 281204 - crash when running fusion-icon
Summary: crash when running fusion-icon
Status: RESOLVED DUPLICATE of bug 274213
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-09-02 08:52 UTC by Mark Rooks
Modified: 2011-09-02 10:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Rooks 2011-09-02 08:52:52 UTC
Application: compiz ()
KDE Platform Version: 4.6.5 (4.6.5)
Qt Version: 4.7.3
Operating System: Linux 2.6.40.3-0.fc15.i686.PAE i686
Distribution: "Fedora release 15 (Lovelock)"

-- Information about the crash:
- What I was doing when the application crashed: I disbaled desktop effects in "System Settings" applet.

I ran sudo yum install fusion-icon, after installing compiz and the KDE compiz integration parts.

In KDE4 I selected fusion-icon from the menus.

The crash then occured. The fusion-icon was loaded into the KDE4 "System Tray" applet. The displayed windows had no decoration at this point.

I right clicked the fusion-icon in the "System Tray", select "reload window manager", carsh occurs again. This is consistent on this particular rpm git build.

When i switch the window manager to "Kwin", I get window decoration back but no window compositing evident.

The crash can be reproduced some of the time.

-- Backtrace:
Application:  (compiz), signal: Aborted
[KCrash Handler]
#7  0x00b38424 in __kernel_vsyscall ()
#8  0x0101e26f in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#9  0x0101fba5 in __GI_abort () at abort.c:93
#10 0x00778894 in g_logv (log_domain=0xee7b77 "glibmm", log_level=<optimized out>, format=0xee8da8 "\nunhandled exception (type std::exception) in signal handler:\nwhat: %s\n", args1=0xbfaf83fc "\354\265_\b\240m\352") at gmessages.c:557
#11 0x007788d4 in g_log (log_domain=0xee7b77 "glibmm", log_level=G_LOG_LEVEL_ERROR, format=0xee8da8 "\nunhandled exception (type std::exception) in signal handler:\nwhat: %s\n") at gmessages.c:577
#12 0x00ed85a6 in Glib::exception_handlers_invoke() () from /usr/lib/libglibmm-2.4.so.1
#13 0x00ed8c3d in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) () from /usr/lib/libglibmm-2.4.so.1
#14 0x0076f5bf in g_main_dispatch (context=0x83a8238) at gmain.c:2441
#15 g_main_context_dispatch (context=0x83a8238) at gmain.c:3014
#16 0x0076fd30 in g_main_context_iterate (context=0x83a8238, block=7858816, dispatch=1, self=0x83a7290) at gmain.c:3092
#17 0x00770457 in g_main_loop_run (loop=0x83a6638) at gmain.c:3300
#18 0x00eda2d4 in Glib::MainLoop::run() () from /usr/lib/libglibmm-2.4.so.1
#19 0x0806f0cb in CompScreen::eventLoop() ()
#20 0x08062707 in main ()

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

Possible duplicates by query: bug 279843, bug 277494.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-09-02 10:25:24 UTC

*** This bug has been marked as a duplicate of bug 274213 ***