Bug 294541 - kimpanel segfault on start
Summary: kimpanel segfault on start
Status: RESOLVED UNMAINTAINED
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:
: 294546 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-02-21 03:06 UTC by tuppa
Modified: 2012-02-21 05:40 UTC (History)
3 users (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 tuppa 2012-02-21 03:06:00 UTC
Application: kimpanel (0.1.0)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Linux Mint 12 KDE

-- Information about the crash:
- What I was doing when the application crashed:

Just starting it from konsole (running kimpanel literally)

The crash can be reproduced every time.

-- Backtrace:
Application: Input Method Panel (kimpanel), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f650882b7a0 (LWP 19019))]

Thread 2 (Thread 0x7f64eefb5700 (LWP 19020)):
#0  0x00007f65061cdac0 in pthread_mutex_unlock (mutex=0x13e6c08) at forward.c:184
#1  0x00007f6502d92f3f in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6502d93dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6502d94429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f65075fbf3e in QEventDispatcherGlib::processEvents (this=0x1407040, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#5  0x00007f65075cfcf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f65075cfef7 in QEventLoop::exec (this=0x7f64eefb4db0, flags=...) at kernel/qeventloop.cpp:201
#7  0x00007f65074e727f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#8  0x00007f65075b2cbf in QInotifyFileSystemWatcherEngine::run (this=0x13e2f10) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f65074e9d05 in QThreadPrivate::start (arg=0x13e2f10) at thread/qthread_unix.cpp:331
#10 0x00007f6503861efc in start_thread (arg=0x7f64eefb5700) at pthread_create.c:304
#11 0x00007f65061bf89d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f650882b7a0 (LWP 19019)):
[KCrash Handler]
#6  data (this=0x8) at ../../include/QtCore/../../src/corelib/tools/qscopedpointer.h:135
#7  qGetPtrHelper<QScopedPointer<QObjectData> > (p=...) at ../../include/QtCore/../../src/corelib/global/qglobal.h:2343
#8  d_func (this=0x0) at graphicsview/qgraphicsscene.h:297
#9  QGraphicsScene::addItem (this=0x0, item=<optimized out>) at graphicsview/qgraphicsscene.cpp:2543
#10 0x00007f6508449c61 in KIMLookupTable::KIMLookupTable (this=0x13f14f0, agent=<optimized out>, corona=<optimized out>, parent=<optimized out>) at ../../../../applets/kimpanel/src/kimlookuptable.cpp:101
#11 0x0000000000401e86 in KIMPanel::KIMPanel (this=0x7fffe69cb0b0, parent=<optimized out>) at ../../../../applets/kimpanel/src/paneldialog.cpp:57
#12 0x0000000000401a8b in main (argc=1, argv=0x7fffe69cb2d8) at ../../../../applets/kimpanel/src/main.cpp:39

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-02-21 04:05:34 UTC
kimpanel has been rewritten in KDE SC 4.8. 

Adding the current maintainer into CC list to check whether this crash report is useful or relevant for the new version.
Comment 2 Weng Xuetian 2012-02-21 05:17:33 UTC
Kimpanel will no longer be a standalone program since KDE SC 4.8, but it will be plasmoid-only.

Sorry but I can't fix this for you.
1. KDE 4.7 series live has end.
2. It's completely rewritten in 4.8.

If you have some bug for kde 4.8, you can open another bug report.

For now, if you want a standalone kimpanel replacement for 4.7, you can try 
http://kde-apps.org/content/show.php/KIMToy?content=140967
Comment 3 Jekyll Wu 2012-02-21 05:40:01 UTC
*** Bug 294546 has been marked as a duplicate of this bug. ***