Bug 328318 - crashes on printing budget reporrs
Summary: crashes on printing budget reporrs
Status: RESOLVED WORKSFORME
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 4.6.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords: drkonqi, triaged
Depends on:
Blocks:
 
Reported: 2013-12-02 09:25 UTC by Deanne
Modified: 2018-10-27 04:13 UTC (History)
1 user (show)

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 Deanne 2013-12-02 09:25:19 UTC
Application: kmymoney (4.6.3)
KDE Platform Version: 4.11.2
Qt Version: 4.8.4
Operating System: Linux 3.11.0-13-generic x86_64
Distribution: Ubuntu 13.10

-- Information about the crash:
- What I was doing when the application crashed:
Printing a budge report
I set up a budget then tried to print it.  Each budget report option I chose crashed and closed the program.

The crash can be reproduced every time.

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

Thread 3 (Thread 0x7f37a64df700 (LWP 19052)):
#0  0x00007f37ba7f9f7d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f37b5e3f6a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f37b5e3fb0a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f37ad6e2b66 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4  0x00007f37b5e640f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f37b6508f6e in start_thread (arg=0x7f37a64df700) at pthread_create.c:311
#6  0x00007f37ba8069cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f37a5415700 (LWP 19053)):
#0  0x00007f37b5e7f0ea in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f37b5e7f399 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f37b5e3f595 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f37b5e3f7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f37b5e3f7f9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f37b5e640f5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f37b6508f6e in start_thread (arg=0x7f37a5415700) at pthread_create.c:311
#7  0x00007f37ba8069cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f37bfeef7c0 (LWP 19049)):
[KCrash Handler]
#5  0x00007f37ba742f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x00007f37ba7465e8 in __GI_abort () at abort.c:90
#7  0x00007f37bb04e6e5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#8  0x00007f37bb04c856 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f37bb04c883 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f37bb04caae in __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x0000000000456027 in main (argc=1, argv=0x7fffd4f3e158) at /build/buildd/kmymoney-4.6.3/kmymoney/main.cpp:185

Possible duplicates by query: bug 327905, bug 327844, bug 327718, bug 327574, bug 326518.

Reported using DrKonqi
Comment 1 Cristian Oneț 2014-07-31 09:52:06 UTC
Could you reproduce this with debug symbols installed? Or provide an anonymous file?
Comment 2 Andrew Crouthamel 2018-09-25 03:42:19 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-27 04:13:13 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!