Bug 362469 – crash in Calculator: I tried to open the calc...

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 362469 - crash in Calculator: I tried to open the calc...


Summary:	crash in Calculator: I tried to open the calc...


Status:	RESOLVED DUPLICATE of bug 354730

Product:	gnome-calculator
Classification:	Core
Component:	general
Version:	5.8.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	Rich Burridge
QA Contact:	Rich Burridge

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-15 21:47 UTC by odal
Modified:	2006-11-18 16:26 UTC

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

Description odal 2006-10-15 21:47:00 UTC

What were you doing when the application crashed?
I tried to open the calculator via the menu. I didn't do something special. 
The calculator didn't even start, it crashed before a window could be seen. I have edgy eft beta and I had at the same time the following programs open:

- Bittornado
- A folder
- Firefox
- Evince

My Computer: 
Ubuntu 6.10 edgy eft beta
Athlon 2000+ XP
512 MB RAM
Nvidia Geforce 5600 XT 128MB RAM


sry for my english, I'm german. thx


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

Memory status: size: 65773568 vsize: 0 resident: 65773568 share: 0 rss: 14016512 rss_rlim: 0
CPU usage: start_time: 1160948540 rtime: 0 utime: 89 stime: 0 cutime:83 cstime: 0 timeout: 6 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 -1224935232 (LWP 7967)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76527

Thread 1 (Thread -1224935232 (LWP 7967))

#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 strlen
from /lib/tls/i686/cmov/libc.so.6
#5 matherr
#6 matherr
#7 matherr
#8 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#9 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#10 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#11 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#12 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#13 gtk_toggle_button_toggled
from /usr/lib/libgtk-x11-2.0.so.0
#14 gtk_radio_button_new_from_widget
from /usr/lib/libgtk-x11-2.0.so.0
#15 g_cclosure_marshal_VOID__VOID
from /usr/lib/libgobject-2.0.so.0
#16 g_value_set_boxed
from /usr/lib/libgobject-2.0.so.0
#17 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#18 g_signal_chain_from_overridden
from /usr/lib/libgobject-2.0.so.0
#19 g_signal_emit_valist
from /usr/lib/libgobject-2.0.so.0
#20 g_signal_emit
from /usr/lib/libgobject-2.0.so.0
#21 gtk_button_clicked
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_toggle_button_set_active
from /usr/lib/libgtk-x11-2.0.so.0
#23 matherr
#24 matherr
#25 matherr
#26 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#27 ??
#0 __kernel_vsyscall

Comment 1 Rich Burridge 2006-10-16 01:22:27 UTC

I just tried this on my Ubuntu Edgy system, with all of the latest
updates, and did not get a crash. gcalctool (v5.8.24) came up just
fine.

This one could be tricky to track down. It looks similar to the
stack trace in bug #358337. If it is that, then it was fixed in
v5.9.3 of gcalctool. I'll be generated a gcalctool tarball for
GNOME 2.17.1 tomorrow morning (which should include that fix).

Any chance you can try that one and see if the problem goes away?

Comment 2 odal 2006-10-16 11:15:36 UTC

I just retried it and it opened now, perhaps my system was just "overloaded" the last time. I checked the version which is 5.8.24. Perhaps there is, as you said, already a fix out in the next version, but I didn't get it yet (?).

Thx

DrOdal

Comment 3 Rich Burridge 2006-10-16 11:41:11 UTC

Okay, thanks for the feedback. Lowering priority to "normal"
as you can't consistently reproduce it. I'll keep the bug
open for now, but unless this problem reappears, I'll probably
close it out in a week or two as INCOMPLETE.

Comment 4 odal 2006-10-16 20:21:26 UTC

Ok, btw, thx :o) .

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

Just a note that I've generated a new gcalctool (v5.8.25) for
GNOME 2.16.X. Hopefully the various distros will pick it up
soon. This new version includes fixes for:

* Fixed bug #354730 - crash in Calculator: running 3x1038 using bi..
* Fixed bug #359291 - crash when localized decimal point is greater
 than 1 char. Removed the bogus assert.
* Fixed bug #358337 - gcalctool no longer crashes in the Oriya locale
 due to sloppy string handling. 

I expect we will have a stabler calculator at that point.

Comment 6 Rich Burridge 2006-11-18 16:26:43 UTC

Closing this as a duplicate of bug #354730. We've just got to wait
for the various Linux distro's to pick it up.


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