Bug#418129: Bug #418129: fcitx causes konsole to crash when launched from it
tags 418129 + wontfix Upstream doesn't maintain KDE3 compatibility any more, mark as Won't Fix. -- Regards, Aron Xu -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#418129: fcitx causes konsole to crash when launched from it
Hi Anyway, kconsole shouldn't crash, it's a problem. I didn't use KDE, I couldn't reproduce it. Could you give me more information, such as the log from .xsession-error? On 4/14/07, Wei Chen [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guanghui Yu wrote: Hi I don't think it's a bug. You should start fcitx before launch kconsole. I don't see reasons why it should not be launched from konsole. I launch it from konsole mainly because I only occasionally need to input Chinese characters and do not want to have the program running there all day. Furthermore, it seems that an IM is supposed to be launched along with the DE is not the reason that it should crash another program/terminal when launched in another way. See what you think about that... - -- Cheers, Wei Chen http://www.acplex.com/people/wchen/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIFSvCIqXQV6BF28RAlBgAJ9CToV3wnFU7QRmYOTh0Rc0tTwMSQCgwtFd MNQ4NuTidgVJLflF9E4nKLw= =JCw0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418129: fcitx causes konsole to crash when launched from it
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guanghui Yu wrote: Hi Anyway, kconsole shouldn't crash, it's a problem. I didn't use KDE, I couldn't reproduce it. Could you give me more information, such as the log from .xsession-error? Attached please find the information requested. 1. When launching fcitx from konsole, konsole crashed. The trace back information which was provided by /kde crash handler/ is in file ``backtrace1''. The .xsession-errors log can be found in the file ``errlog1''. 2. Then I opened a new konsole terminal, entering /killall fcitx/ to kill the fcitx process. konsole crashed again at that time. Information can be found in ``backtrace2'' and ``errlog2''. HTH - -- Cheers, Wei Chen http://www.acplex.com/people/wchen/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD4DBQFGIw3UCIqXQV6BF28RAoa7AJ91s3XaTfdJ19E316OM8V9lnsLKfwCY6lAg QI4ti4MKjN4NAg/s1SaFYg== =2Wi0 -END PGP SIGNATURE- (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1231812384 (LWP 5984)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [KCrash handler] #9 0xb6f539df in XSetICValues () from /usr/lib/libX11.so.6 #10 0xb634279e in QXIMInputContext::setXFontSet () from /usr/lib/qt3/plugins/inputmethods/libqxim.so #11 0xb63428d3 in QXIMInputContext::setMicroFocus () from /usr/lib/qt3/plugins/inputmethods/libqxim.so #12 0xb583edca in QMultiInputContext::setMicroFocus () from /usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so #13 0xb725de55 in QWidget::setMicroFocusHint () from /usr/lib/libqt-mt.so.3 #14 0xb666c82d in TEWidget::setCursorPos () from /usr/lib/libkdeinit_konsole.so #15 0xb6692848 in TEmulation::showBulk () from /usr/lib/libkdeinit_konsole.so #16 0xb6693133 in TEmulation::qt_invoke () from /usr/lib/libkdeinit_konsole.so #17 0xb6693184 in TEmuVt102::qt_invoke () from /usr/lib/libkdeinit_konsole.so #18 0xb72f6d4f in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #19 0xb72f77e0 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3 #20 0xb7681faa in QTimer::timeout () from /usr/lib/libqt-mt.so.3 #21 0xb731e603 in QTimer::event () from /usr/lib/libqt-mt.so.3 #22 0xb728ec26 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3 #23 0xb7290a43 in QApplication::notify () from /usr/lib/libqt-mt.so.3 #24 0xb7984e0e in KApplication::notify () from /usr/lib/libkdecore.so.4 #25 0xb7222421 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3 #26 0xb7281623 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3 #27 0xb723676f in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3 #28 0xb72a9179 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3 #29 0xb72a8f9a in QEventLoop::exec () from /usr/lib/libqt-mt.so.3 #30 0xb72907bf in QApplication::exec () from /usr/lib/libqt-mt.so.3 #31 0xb66b5d25 in kdemain () from /usr/lib/libkdeinit_konsole.so #32 0xb7fe1524 in kdeinitmain () from /usr/lib/kde3/konsole.so #33 0x0804e457 in ?? () #34 0x0001 in ?? () #35 0x08071480 in ?? () #36 0x0001 in ?? () #37 0x in ?? () (no debugging symbols found) Using host libthread_db library /lib/tls/i686/cmov/libthread_db.so.1. (no debugging symbols found) (no debugging symbols found)
Bug#418129: fcitx causes konsole to crash when launched from it
Hi I don't think it's a bug. You should start fcitx before launch kconsole. On 4/7/07, Wei Chen [EMAIL PROTECTED] wrote: Package: fcitx Version: 1:3.4.3-1 Severity: important How to reproduce: 1. Launch konsole 2. Enter: fcitx 3. Mouse click on the terminal window 4. Konsole crashes I guess this is a bug of fcitx since I can launch other programs from konsole with no problem. Thanks. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_HK.UTF-8, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2generic font configuration library ii libx11-62:1.0.3-6X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch none (no description available) pn ttf-arphic-gbsn00lp | ttf-arp none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418129: fcitx causes konsole to crash when launched from it
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guanghui Yu wrote: Hi I don't think it's a bug. You should start fcitx before launch kconsole. I don't see reasons why it should not be launched from konsole. I launch it from konsole mainly because I only occasionally need to input Chinese characters and do not want to have the program running there all day. Furthermore, it seems that an IM is supposed to be launched along with the DE is not the reason that it should crash another program/terminal when launched in another way. See what you think about that... - -- Cheers, Wei Chen http://www.acplex.com/people/wchen/ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGIFSvCIqXQV6BF28RAlBgAJ9CToV3wnFU7QRmYOTh0Rc0tTwMSQCgwtFd MNQ4NuTidgVJLflF9E4nKLw= =JCw0 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#418129: fcitx causes konsole to crash when launched from it
Package: fcitx Version: 1:3.4.3-1 Severity: important How to reproduce: 1. Launch konsole 2. Enter: fcitx 3. Mouse click on the terminal window 4. Konsole crashes I guess this is a bug of fcitx since I can launch other programs from konsole with no problem. Thanks. -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-686 Locale: LANG=en_HK.UTF-8, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1.2generic font configuration library ii libx11-62:1.0.3-6X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch none (no description available) pn ttf-arphic-gbsn00lp | ttf-arp none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
