Bug 232410 - KMix crashes while enabling composite
Summary: KMix crashes while enabling composite
Status: RESOLVED DUPLICATE of bug 182026
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-27 23:59 UTC by Bruno Barão
Modified: 2010-03-28 00:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno Barão 2010-03-27 23:59:17 UTC
Application: kmix (3.6-alpha2)
KDE Platform Version: 4.4.1 (KDE 4.4.1) (Compiled from sources)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-tuxonice-r5 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
My KDE allways starts with composite off. So after it starts, I press the shortcut to enable it (Alt Shift F12) and KMix crashes.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMix (kdeinit4), signal: Bus error
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.2200.5-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
[KCrash Handler]
#5  0x00007f58848ba1f8 in KPixmapCache::Private::mmapFile (this=0xdbcb20, filename=..., info=0xdbcb70, newsize=33656832)
    at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:491
#6  0x00007f58848bb594 in KPixmapCache::Private::mmapFiles (this=0xdbcb20) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:419
#7  0x00007f58848bb3b4 in KPixmapCache::Private::init (this=0xdbcb20) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1061
#8  0x00007f58848bc7fa in KPixmapCache::discard (this=0xdbaab0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1279
#9  0x00007f58848bce9c in KPixmapCache::deleteCache (name=...) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kpixmapcache.cpp:1255
#10 0x00007f5882531310 in Plasma::ThemePrivate::discardCache (this=0xda4f70) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/plasma/theme.cpp:221
#11 0x00007f588253156d in Plasma::ThemePrivate::compositingChanged (this=0xda4f70) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/plasma/theme.cpp:213
#12 0x00007f5882532b42 in Plasma::Theme::qt_metacall (this=0xda4eb0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff063a3dd0)
    at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/plasma/theme.moc:108
#13 0x0000003b1637f31f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007f58848b2e8f in KSelectionWatcher::newOwner (this=0x1027250, _t1=20971617) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1_build/kdeui/kmanagerselection.moc:152
#15 0x00007f58848b316a in KSelectionWatcher::owner (this=0xda6f20) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kmanagerselection.cpp:451
#16 0x00007f58848b424d in KSelectionWatcher::Private::x11Event (this=<value optimized out>, ev_P=0x0)
    at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/util/kmanagerselection.cpp:395
#17 0x00007f5884842d05 in KApplication::x11EventFilter (this=<value optimized out>, _event=0x7fff063a44e0)
    at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kdeui/kernel/kapplication.cpp:953
#18 0x0000003b1d02f431 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#19 0x0000003b1d03e501 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/qt4/libQtGui.so.4
#20 0x0000003b1d068f62 in ?? () from /usr/lib64/qt4/libQtGui.so.4
#21 0x00007f5883a0750d in g_main_dispatch (context=0xcb9d20) at gmain.c:1960
#22 IA__g_main_context_dispatch (context=0xcb9d20) at gmain.c:2513
#23 0x00007f5883a0aec8 in g_main_context_iterate (context=0xcb9d20, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#24 0x00007f5883a0aff0 in IA__g_main_context_iteration (context=0xcb9d20, may_block=1) at gmain.c:2654
#25 0x0000003b163959e3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#26 0x0000003b1d068b5e in ?? () from /usr/lib64/qt4/libQtGui.so.4
#27 0x0000003b1636af82 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#28 0x0000003b1636b354 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#29 0x0000003b1636f03b in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4
#30 0x0000003b1bc226da in kdemain () from /usr/lib64/libkdeinit4_kmix.so
#31 0x000000000040702f in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=<value optimized out>, envs=<value optimized out>, reset_env=false, 
    tty=0x0, avoid_loops=false, startup_id_str=0x40b304 "0") at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kinit/kinit.cpp:710
#32 0x0000000000407a4e in handle_launcher_request (sock=8, who=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kinit/kinit.cpp:1202
#33 0x000000000040878a in handle_requests (waitForPid=0) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kinit/kinit.cpp:1395
#34 0x0000000000408c8f in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at /var/tmp/portage/kde-base/kdelibs-4.4.1-r1/work/kdelibs-4.4.1/kinit/kinit.cpp:1834

Possible duplicates by query: bug 232393, bug 232147, bug 232119, bug 231987, bug 231169.

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-28 00:32:53 UTC
Fixed in KDE SC 4.4.2.
Regards

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