Bug 308174 - KMyMoney crash when right-clicking category
Summary: KMyMoney crash when right-clicking category
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.1
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-10 11:49 UTC by D. van Aken
Modified: 2014-07-29 09:12 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 D. van Aken 2012-10-10 11:49:05 UTC
Application: kmymoney (4.6.1)
KDE Platform Version: 4.8.5 (4.8.5)
Qt Version: 4.8.1
Operating System: Linux 3.2.0-31-generic i686
Distribution: Ubuntu 12.04.1 LTS

-- Information about the crash:
- What I was doing when the application crashed:
Using KMyMoney 4.6.1 under Kubuntu, KDE 4.8.5.
Changing some categories: in the Categories screen, I select one and click right to edit or delete it. At that point, the program sometimes crashes (not consistently, as far as I can see).

The crash can be reproduced some of the time.

-- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb77ab740 (LWP 18588))]

Thread 2 (Thread 0xb4960b40 (LWP 18597)):
#0  0x00632dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x03369315 in do_gettime (frac=0xb495ffb0, sec=0xb495ffa8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x03453226 in QTimerInfoList::updateCurrentTime (this=0xb4002074) at kernel/qeventdispatcher_unix.cpp:343
#4  0x0345357a in QTimerInfoList::timerWait (this=0xb4002074, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0x03451e23 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb49600bc) at kernel/qeventdispatcher_glib.cpp:136
#6  0x03451ebd in timerSourcePrepare (source=0xb4002040, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x01d30872 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x01d30faf in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x01d31201 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x034528e7 in QEventDispatcherGlib::processEvents (this=0xb4000468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#11 0x0341e50d in QEventLoop::processEvents (this=0xb4960240, flags=...) at kernel/qeventloop.cpp:149
#12 0x0341e7a9 in QEventLoop::exec (this=0xb4960240, flags=...) at kernel/qeventloop.cpp:204
#13 0x0330794c in QThread::exec (this=0x929a968) at thread/qthread.cpp:501
#14 0x033fbb5d in QInotifyFileSystemWatcherEngine::run (this=0x929a968) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x0330ade0 in QThreadPrivate::start (arg=0x929a968) at thread/qthread_unix.cpp:298
#16 0x00116d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x0525ff4e in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb77ab740 (LWP 18588)):
[KCrash Handler]
#7  0x00824416 in __kernel_vsyscall ()
#8  0x0519f1ef in raise () from /lib/i386-linux-gnu/libc.so.6
#9  0x051a2835 in abort () from /lib/i386-linux-gnu/libc.so.6
#10 0x007b313d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#11 0x007b0ed3 in ?? () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#12 0x007b0f0f in std::terminate() () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#13 0x007b105e in __cxa_throw () from /usr/lib/i386-linux-gnu/libstdc++.so.6
#14 0x0808939e in main (argc=<error reading variable: Cannot access memory at address 0x489c>, argv=<error reading variable: Cannot access memory at address 0x48a0>) at /build/buildd/kmymoney-4.6.1/kmymoney/main.cpp:185

Possible duplicates by query: bug 308151, bug 308107, bug 308099, bug 308053, bug 308052.

Reported using DrKonqi
Comment 1 Cristian Oneț 2012-11-29 16:27:23 UTC
Can you provide a meaningful backtrace or an anonymous file with which this could be reproduced?