Bug 258582 - kmymoney 4.5 crashes on launch every time
Summary: kmymoney 4.5 crashes on launch every time
Status: RESOLVED NOT A BUG
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-02 17:56 UTC by aidenn0
Modified: 2010-12-11 09:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description aidenn0 2010-12-02 17:56:42 UTC
Application: kmymoney (4.5.0)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.35-zen2 x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
Installed from gentoo portage package app-office/kmymoney-4.5-r2 on an amd64 system.  This happened the first time I ran it, so not a lot of steps to reproduce.

The crash can be reproduced every time.

 -- Backtrace:
Application: KMyMoney (kmymoney), signal: Aborted
[Current thread is 1 (Thread 0x7f9236ce8760 (LWP 2909))]

Thread 2 (Thread 0x7f921c8a8710 (LWP 2911)):
#0  0x00007f922f1cc759 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f9233397ad7 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/qt4/libQtCore.so.4
#2  0x00007f923338cc99 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#3  0x00007f9233396c15 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#4  0x00007f922f1c84f7 in start_thread () from /lib/libpthread.so.0
#5  0x00007f92319d828d in clone () from /lib/libc.so.6

Thread 1 (Thread 0x7f9236ce8760 (LWP 2909)):
[KCrash Handler]
#5  0x00007f9231936445 in raise () from /lib/libc.so.6
#6  0x00007f9231937941 in abort () from /lib/libc.so.6
#7  0x00007f92321c1f85 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6
#8  0x00007f92321c03b6 in ?? () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6
#9  0x00007f92321c03e3 in std::terminate() () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6
#10 0x00007f92321c0465 in __cxa_rethrow () from /usr/lib/gcc/x86_64-pc-linux-gnu/4.4.3/libstdc++.so.6
#11 0x00007f923348adc0 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4
#12 0x00007f92334b7e94 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#13 0x00007f92334b4844 in ?? () from /usr/lib64/qt4/libQtCore.so.4
#14 0x00007f922d10aecf in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0x00007f922d10ed08 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x00007f922d10eebc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0x00007f92334b454c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#18 0x00007f923267668f in ?? () from /usr/lib64/qt4/libQtGui.so.4
#19 0x00007f923348c079 in QCoreApplication::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4
#20 0x000000000045ae6c in _start ()

Possible duplicates by query: bug 254889, bug 248146, bug 226364, bug 223744.

Reported using DrKonqi
Comment 1 Cristian Oneț 2010-12-07 22:14:34 UTC
There is not a lot of info to work with on this. Judging by the stack KMyMoney code wasn't even entered yet. Could you reproduce this without debug symbols stripped?
Comment 2 Jack 2010-12-07 23:06:00 UTC
I'm also on Gentoo, and have the same version installed on amd64, with no problems.  Have you done an "emerge-sync" and "emerge -uDN" recently?  (D for deep - assuring latest version of all dependencies, and N in case any use flags have changed)
Comment 3 Cristian Oneț 2010-12-10 10:58:35 UTC
I'm closing this since no further information was provided and the report seems to describe an installation problem rather then a problem in KMyMoney.
Comment 4 aidenn0 2010-12-10 18:33:05 UTC
Sorry, spam filter caught the e-mails.  I re-installed the qt libs from portage and the problem was fixed.  Not sure what was going on there.