Bug 373030 – crash in Calculator: pasted a URL by accident...

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 373030 - crash in Calculator: pasted a URL by accident...


Summary:	crash in Calculator: pasted a URL by accident...


Status:	RESOLVED DUPLICATE of bug 371243

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-09 17:04 UTC by spammy
Modified:	2006-11-09 17:10 UTC

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

Description spammy 2006-11-09 17:04:08 UTC

What were you doing when the application crashed?
pasted a URL by accident. cleared it and then typed "asdf"


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

System: Linux 2.6.18-1.2798.fc6 #1 SMP Mon Oct 16 14:37:32 EDT 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled
----------- .xsession-errors (4705 sec old) ---------------------
/etc/xdg/xfce4/xinitrc: line 54: xscreensaver: command not found
** (xfdesktop:2585): CRITICAL **: xfdesktop_grid_is_free_position: assertion `row < icon_view->priv->nrows && col < icon_view->priv->ncols' failed
(xfdesktop:2585): Gtk-CRITICAL **: gtk_style_detach: assertion `style->attach_count > 0' failed
Error: No running window found
The application 'xfdesktop' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
Error: No running window found
Error: No running window found
Error: No running window found
Error: No running window found
Error: No running window found
Error: No running window found
--------------------------------------------------

Memory status: size: 58671104 vsize: 0 resident: 58671104 share: 0 rss: 11485184 rss_rlim: 0
CPU usage: start_time: 1163091496 rtime: 0 utime: 455 stime: 0 cutime:412 cstime: 0 timeout: 43 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 -1208936752 (LWP 18096)]
(no debugging symbols found)
0x00aa9402 in __kernel_vsyscall ()

+ Trace 84781

Thread 1 (Thread -1208936752 (LWP 18096))

#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 matherr
#11 matherr
#12 gtk_marshal_BOOLEAN__VOID
from /usr/lib/libgtk-x11-2.0.so.0
#13 g_closure_invoke
from /lib/libgobject-2.0.so.0
#14 g_signal_override_class_closure
from /lib/libgobject-2.0.so.0
#15 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#16 g_signal_emit
from /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_add_client_message_filter
from /usr/lib/libgdk-x11-2.0.so.0
#21 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#22 g_main_context_check
from /lib/libglib-2.0.so.0
#23 g_main_loop_run
from /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/libc.so.6
#27 g_object_unref
#0 __kernel_vsyscall

Comment 1 Christian Kirbach 2006-11-09 17:10:43 UTC

Comment #1 from Rich Burridge (gcalctool developer, points: 20) 
2006-11-05 23:30 UTC [reply] 
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).


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