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 418890 - crash in Calculator: Converting hex to decima...
crash in Calculator: Converting hex to decima...
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-03-16 08:52 UTC by cdaguin
Modified: 2007-03-16 13:52 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description cdaguin 2007-03-16 08:52:03 UTC 
What were you doing when the application crashed?
Converting hex to decimal. I was entering a number with the keyboard			


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

Memory status: size: 55099392 vsize: 0 resident: 55099392 share: 0 rss: 14241792 rss_rlim: 0
CPU usage: start_time: 1174033666 rtime: 0 utime: 246 stime: 0 cutime:240 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 -1225386320 (LWP 9691)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119061

Thread 1 (Thread -1225386320 (LWP 9691))

  • #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 matherr
  • #11 matherr
  • #12 _gtk_marshal_BOOLEAN__BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #17 gtk_widget_get_default_style
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 gtk_propagate_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 _gdk_events_init
    from /usr/lib/libgdk-x11-2.0.so.0
  • #21 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #22 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 matherr
  • #26 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #27 ??
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-03-16 13:52:19 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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