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 409031 - crash in Gnome Calculator:
crash in Gnome Calculator:
Status: RESOLVED DUPLICATE of bug 354730
Product: gnome-calculator
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Rich Burridge
Rich Burridge
Depends on:
Blocks:
 
 
Reported: 2007-02-17 19:14 UTC by Amr Hamdy
Modified: 2007-02-17 21:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Amr Hamdy 2007-02-17 19:14:58 UTC 
What were you doing when the application crashed?



Distribution: openSUSE 10.2 (i586)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 56754176 vsize: 0 resident: 56754176 share: 0 rss: 3477504 rss_rlim: 0
CPU usage: start_time: 1171739606 rtime: 0 utime: 195 stime: 0 cutime:185 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

Backtrace was generated from '/opt/gnome/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 -1226512176 (LWP 7565)]
(no debugging symbols found)
0xb7f13410 in __kernel_vsyscall ()

+ Trace 111572

Thread 1 (Thread -1226512176 (LWP 7565))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /opt/gnome/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 matherr
  • #11 matherr
  • #12 gtk_marshal_BOOLEAN__VOID
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #14 g_signal_override_class_closure
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /opt/gnome/lib/libgobject-2.0.so.0
  • #17 gtk_widget_get_default_style
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #18 gtk_propagate_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #19 gtk_main_do_event
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #20 gdk_add_client_message_filter
    from /opt/gnome/lib/libgdk-x11-2.0.so.0
  • #21 g_main_context_dispatch
    from /opt/gnome/lib/libglib-2.0.so.0
  • #22 g_main_context_prepare
    from /opt/gnome/lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /opt/gnome/lib/libglib-2.0.so.0
  • #24 gtk_main
    from /opt/gnome/lib/libgtk-x11-2.0.so.0
  • #25 matherr
  • #26 __libc_start_main
    from /lib/libc.so.6
  • #27 g_object_unref
  • #0 __kernel_vsyscall 






Comment 1


Rich Burridge





          2007-02-17 21:44:18 UTC
        



Duplicate of bug #354730. Fixed in gcalctool v5.8.25 (which is
in GNOME 2.16.2). Hopefully the variopus Linux distros will 
pick it up soon.

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