Bug 370236 – crash: saving and closing

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 370236 - crash: saving and closing


Summary:	crash: saving and closing


Status:	VERIFIED DUPLICATE of bug 353450

Product:	GnuCash
Classification:	Other
Component:	General
Version:	2.0.x
Hardware:	Other All

Importance:	Normal critical
Target Milestone:	---
Assigned To:	Chris Lyttle
QA Contact:	Chris Lyttle

URL:
Whiteboard:

Duplicates:	370656 374498 (view as bug list)
Depends on:
Blocks:

Reported:	2006-11-03 22:15 UTC by tim
Modified:	2018-06-29 21:14 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description tim 2006-11-03 22:15:39 UTC

What were you doing when the application crashed?
saving and closing	


Distribution: Slackware Slackware 11.0.0
Gnome Release: 2.16.0 2006-10-03 (Dropline GNOME)
BugBuddy Version: 2.16.0

Memory status: size: 47849472 vsize: 0 resident: 47849472 share: 0 rss: 31969280 rss_rlim: 0
CPU usage: start_time: 1162592029 rtime: 0 utime: 720 stime: 0 cutime:702 cstime: 0 timeout: 18 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnucash'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1232660192 (LWP 4204)]
0xb6b1704e in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 82532

Thread 1 (Thread -1232660192 (LWP 4204))

#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0
#1 libgnomeui_module_info_get
from /usr/lib/libgnomeui-2.so.0
#2 <signal handler called>
#3 gdk_keyval_convert_case
from /usr/lib/libgdk-x11-2.0.so.0
#4 ??
#5 gdk_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#6 ??
#7 ??
#0 __waitpid_nocancel
from /lib/tls/libpthread.so.0

Comment 1 Andreas Köhler 2006-11-05 23:46:32 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Christian Stimming 2006-11-06 10:50:26 UTC

Also, what exact steps did you do when this crashed? Does this happen every time when you do these steps?

Comment 3 Christian Stimming 2006-11-06 10:50:47 UTC

*** Bug 370656 has been marked as a duplicate of this bug. ***

Comment 4 Christian Stimming 2006-11-16 10:23:10 UTC

*** Bug 374498 has been marked as a duplicate of this bug. ***

Comment 5 Christian Stimming 2006-11-16 10:24:18 UTC

Potentially duplicate of bug#353450

Comment 6 Christian Stimming 2006-11-17 09:22:07 UTC


*** This bug has been marked as a duplicate of 353450 ***

Comment 7 John Ralls 2018-06-29 21:14:47 UTC

GnuCash bug tracking has moved to a new Bugzilla host. This bug has been copied to https://bugs.gnucash.org/show_bug.cgi?id=370236. Please update any external references or bookmarks.