Bug 294546 - Can't access ibus language bar
Summary: Can't access ibus language bar
Status: RESOLVED DUPLICATE of bug 294541
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: 2012-02-21 05:34 UTC by Gary Lin
Modified: 2012-02-21 05:40 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 Gary Lin 2012-02-21 05:34:42 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: Ubuntu 11.10

-- Information about the crash:
No icon show on system tray.  No language bar.  So I try to launch kimpanel from terminal and get this crash report.

The crash can be reproduced every time.

-- Backtrace:
Application: Input Method Panel (kimpanel), signal: Segmentation fault
[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 0x00007f10afa0cc61 in KIMLookupTable::KIMLookupTable (this=0xf984b0, agent=<optimized out>, corona=<optimized out>, parent=<optimized out>) at ../../../../applets/kimpanel/src/kimlookuptable.cpp:101
#11 0x0000000000401e86 in KIMPanel::KIMPanel (this=0x7fffe1807ba0, parent=<optimized out>) at ../../../../applets/kimpanel/src/paneldialog.cpp:57
#12 0x0000000000401a8b in main (argc=1, argv=0x7fffe1807dc8) at ../../../../applets/kimpanel/src/main.cpp:39

Possible duplicates by query: bug 294541.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-02-21 05:40:01 UTC

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