Bug 368885 – crash in Calculator: Just calculating. I was ...

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 368885 - crash in Calculator: Just calculating. I was ...


Summary:	crash in Calculator: Just calculating. I was ...


Status:	RESOLVED DUPLICATE of bug 354730

Product:	gnome-calculator
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Rich Burridge
QA Contact:	Rich Burridge

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-11-01 15:01 UTC by Sebazzz
Modified:	2006-11-17 18:11 UTC

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

Description Sebazzz 2006-11-01 15:01:46 UTC

What were you doing when the application crashed?
Just calculating. I was doing something with '0'. The calculator gave no other answer than zero.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 52883456 vsize: 0 resident: 52883456 share: 0 rss: 14991360 rss_rlim: 0
CPU usage: start_time: 1162392661 rtime: 0 utime: 348 stime: 0 cutime:334 cstime: 0 timeout: 14 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224963904 (LWP 6402)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81450

Thread 1 (Thread -1224963904 (LWP 6402))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 __kernel_vsyscall
#5 raise
from /lib/tls/i686/cmov/libc.so.6
#6 abort
from /lib/tls/i686/cmov/libc.so.6
#7 __assert_fail
from /lib/tls/i686/cmov/libc.so.6
#8 matherr
#9 matherr
#10 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#11 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#13 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#14 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#15 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#16 gtk_button_set_alignment
from /usr/lib/libgtk-x11-2.0.so.0
#17 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#18 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#19 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#21 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#22 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#23 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_button_released
from /usr/lib/libgtk-x11-2.0.so.0
#25 _gtk_marshal_BOOLEAN__BOXED
from /usr/lib/libgtk-x11-2.0.so.0
#26 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#27 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#28 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#29 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#31 gtk_widget_get_default_style
from /usr/lib/libgtk-x11-2.0.so.0
#32 gtk_propagate_event
from /usr/lib/libgtk-x11-2.0.so.0
#33 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#34 _gdk_events_init
from /usr/lib/libgdk-x11-2.0.so.0
#35 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#37 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#38 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#39 matherr
#40 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#41 ??
#0 __kernel_vsyscall

Comment 1 Rich Burridge 2006-11-01 16:05:25 UTC

Unfortunately the stack trace isn't telling me much.
If you can give me steps to reliably reproduce it, that
would be very helpful. 

Alternatively, here are some questions that might help isolate
the problem.

What locale are you running in?

what mode were you in? (i.e. Is the View->Use Arithmetic Precedence 
checkbox checked?

What view were you in (Nasic, Advanced, Financial, Scientific)?

What numeric base (Bin, Oct, Dec, Hex)? 

What numerical mode (Eng, Fix, Sci)?

Thanks.

Comment 2 Sebazzz 2006-11-02 11:37:58 UTC

I was using Scientific view with Dec and Fix.
I was doing some calculations with the 10's
power, like 5,6 x 10^-2 and such stuff. But it gave
always 0, so I tried 1+1, and it gave 0, and eventually
when trying to devide bij zero it crashed.

Comment 3 Rich Burridge 2006-11-02 14:20:17 UTC

Thanks. You might be running into bug #354730. This is fixed in v5.9.2.

What version of the calculator are you running (see Help->About)?

Comment 4 Sebazzz 2006-11-02 14:32:16 UTC

I'm running GCalcTool 5.8.24 on Edgy.

Comment 5 Rich Burridge 2006-11-02 20:02:11 UTC

Thanks. Yup, I think you are seeing bug #354730. I've just
created a new gcalctool tarball for the GNOME 2.16.X series
(version 5.8.25). Hopefully the Ubuntu folks will pick it up
soon. 

Let's leave it open for now, but if you can get back to me
when gcalctool v5.8.25 comes out, that would be great. Thanks.

Comment 6 Sebazzz 2006-11-02 20:38:20 UTC

Do you know if its going to be on the auto-update? Wil it be shipped with a new gnome or just standalone?

Comment 7 Rich Burridge 2006-11-02 20:46:59 UTC

Sorry, I don't. I'd like to think that it'll appear in a future 
Ubuntu edgy auto-update, but I don't know for sure. Perhaps a 
question to ask in one of the Ubuntu chat forums...

Comment 8 Rich Burridge 2006-11-17 18:11:59 UTC

This is yet another duplicate of bug #354730. Closing as such.
I've created a new gcalctool tarball for the GNOME 2.16.X series.
Hopefully the various Linux distros we pick it up soon.

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