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 371243 - crash in Calculator: pressing space bar a few...
crash in Calculator: pressing space bar a few...
Status: RESOLVED DUPLICATE of bug 354730
Product: gnome-calculator
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Rich Burridge
Rich Burridge
: 373030 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-05 21:53 UTC by linuxuser4ever
Modified: 2006-11-17 18:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description linuxuser4ever 2006-11-05 21:53:15 UTC
What were you doing when the application crashed?
pressing space bar a few times. history: changed calc mode a few times. Pasted some contents into calc.


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 91504640 vsize: 0 resident: 91504640 share: 0 rss: 13287424 rss_rlim: 0
CPU usage: start_time: 1162763328 rtime: 0 utime: 573 stime: 0 cutime:525 cstime: 0 timeout: 48 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208276768 (LWP 7415)]
(no debugging symbols found)
0x00bde402 in __kernel_vsyscall ()

Thread 1 (Thread -1208276768 (LWP 7415))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 __assert_fail
    from /lib/libc.so.6
  • #8 matherr
  • #9 matherr
  • #10 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /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 gtk_button_set_alignment
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_marshal_BOOLEAN__VOID
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 g_value_set_static_boxed
    from /lib/libgobject-2.0.so.0
  • #20 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_override_class_closure
    from /lib/libgobject-2.0.so.0
  • #22 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #23 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #24 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #26 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 gdk_add_client_message_filter
    from /usr/lib/libgdk-x11-2.0.so.0
  • #28 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #29 g_main_context_check
    from /lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 matherr
  • #33 __libc_start_main
    from /lib/libc.so.6
  • #34 g_object_unref
  • #0 __kernel_vsyscall

Comment 1 Rich Burridge 2006-11-05 23:30:28 UTC
It's probably yet another duplicate of bug #354730.
Hopefully the various distros with pick up 5.8.25 soon 
(where that problem is fixed).
Comment 2 Christian Kirbach 2006-11-09 17:10:43 UTC
*** Bug 373030 has been marked as a duplicate of this bug. ***
Comment 3 Rich Burridge 2006-11-17 18:12:07 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 ***