| Summary: | Crash when performing many operations | ||
|---|---|---|---|
| Product: | [Applications] kmymoney | Reporter: | p.com |
| Component: | general | Assignee: | KMyMoney Devel Mailing List <kmymoney-devel> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | crash | CC: | philr, wbauer1 |
| Priority: | NOR | ||
| Version: | 4.8.0 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
segaafult after typing a single character in a dilogue
Backtrace rekonq segfault after first key down on text input |
||
The backtrace reveals no information. Do other Qt4 based applications work? Application: KMyMoney (kmymoney), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fceac64a900 (LWP 15280))] Thread 2 (Thread 0x7fce92b3b700 (LWP 15281)): #0 0x00007fcea674808d in poll () at /lib64/libc.so.6 #1 0x00007fcea1f8fce9 in () at /usr/lib64/libglib-2.0.so.0 #2 0x00007fcea1f8fdfc in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x00007fcea76fdf0e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #4 0x00007fcea76cc3f4 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #5 0x00007fcea76cc75e in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4 #6 0x00007fcea75bec56 in QThread::exec() () at /usr/lib64/libQtCore.so.4 #7 0x00007fcea76ac943 in () at /usr/lib64/libQtCore.so.4 #8 0x00007fcea75c1514 in () at /usr/lib64/libQtCore.so.4 #9 0x00007fcea37aa4e7 in start_thread () at /lib64/libpthread.so.0 #10 0x00007fcea6751a2f in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7fceac64a900 (LWP 15280)): [KCrash Handler] #6 0x00007fcea816a2de in QApplication::x11ProcessEvent(_XEvent*) () at /usr/lib64/libQtGui.so.4 I had tried some KDE apps with no problem, but in response to your question, I tried opening "QT4 designer" and as soon as I type there is a segfault. So this must not be just a kmymoney problem. My apologies, thank you. Would you mind sharing the information (backtrace) of that Qt Deisgner crash here as well? They might be related to KMyMoney, that is why I am asking for it. I experience similar crashes with kmymoney, rekonq and KeePassX on a text input with the first key down. I will attach the backtrace frm rekonq. KeePassX doesn't open the KCrash handler. Platform openSUSE Tumbleweed. Created attachment 106008 [details]
Backtrace rekonq segfault after first key down on text input
When I run QT designer and hit a key, it segfaults, but the crash handler doesn't open. I tried running it through strace, but it didn't look very interesting to me. I also have keepassx and tried that, it has the same problem. Let me know if there is something I can do to add information. Backtrace from comment #5 for rekonq is identical to the kmymoney4 crash from comment #1, in other words, the creah looks unrelated to kmymoney4. I suggest to report this issue to the bug tracker of your distribution. If you do, please add the link here. Thomas, time to release the KF5 port ;) This is a general problem with Qt4 and ibus in Tumbleweed currently. See http://bugzilla.opensuse.org/show_bug.cgi?id=1043734 Workaround: uninstall or disable ibus |
Created attachment 105968 [details] segaafult after typing a single character in a dilogue Kmymoney crashes(segfaults) in many dialogues, including typing in fields like payee, or new institution, or beginning to fill out the dialogue for an entirely new file. Perhaps I have some library problem, but other KDE based programs have no such issues?