Bug 421425 – crash in Gimmie: nothing, just crash

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 421425 - crash in Gimmie: nothing, just crash


Summary:	crash in Gimmie: nothing, just crash


Status:	RESOLVED DUPLICATE of bug 419271

Product:	gimmie
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Gimmie Maintainers
QA Contact:	Gimmie Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-22 10:46 UTC by Hansen
Modified:	2007-03-22 19:32 UTC

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

Description Hansen 2007-03-22 10:46:41 UTC

What were you doing when the application crashed?
nothing, just crash


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.3 2007-01-31 (Red Hat, Inc)
BugBuddy Version: 2.16.0

System: Linux 2.6.18-1.2868.fc6 #1 SMP Fri Dec 15 17:32:54 EST 2006 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70101000
Selinux: No
Accessibility: Disabled

Memory status: size: 122613760 vsize: 0 resident: 122613760 share: 0 rss: 19054592 rss_rlim: 0
CPU usage: start_time: 1174560252 rtime: 0 utime: 425 stime: 0 cutime:289 cstime: 0 timeout: 136 it_real_value: 0 frequency: 0

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

(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 -1208105280 (LWP 7522)]
(no debugging symbols found)
0x0086b402 in __kernel_vsyscall ()

+ Trace 121088

Thread 1 (Thread -1208105280 (LWP 7522))

#0 __kernel_vsyscall
#1 waitpid
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 PyEval_EvalCodeEx
from /usr/lib/libpython2.4.so.1.0
#9 PyClassMethod_New
from /usr/lib/libpython2.4.so.1.0
#10 PyObject_Call
from /usr/lib/libpython2.4.so.1.0
#11 PyEval_CallObjectWithKeywords
from /usr/lib/libpython2.4.so.1.0
#12 PyObject_CallObject
from /usr/lib/libpython2.4.so.1.0
#13 ??
from /usr/lib/python2.4/site-packages/gmenu.so
#14 gmenu_tree_get_menu_file
from /usr/lib/libgnome-menu.so.2
#15 gmenu_tree_get_directory_from_path
from /usr/lib/libgnome-menu.so.2
#16 ??
from /usr/lib/libgnome-menu.so.2
#17 gmenu_tree_get_directory_from_path
from /usr/lib/libgnome-menu.so.2
#18 g_source_is_destroyed
from /lib/libglib-2.0.so.0
#19 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#20 g_main_context_check
from /lib/libglib-2.0.so.0
#21 g_main_loop_run
from /lib/libglib-2.0.so.0
#22 bonobo_main
from /usr/lib/libbonobo-2.so.0
#23 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#24 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#25 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#26 ??
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomeapplet.so
#27 PyCFunction_Call
from /usr/lib/libpython2.4.so.1.0
#28 PyEval_EvalFrame
from /usr/lib/libpython2.4.so.1.0
#29 PyEval_EvalFrame
from /usr/lib/libpython2.4.so.1.0
#30 PyEval_EvalCodeEx
from /usr/lib/libpython2.4.so.1.0
#31 PyEval_EvalCode
from /usr/lib/libpython2.4.so.1.0
#32 Py_CompileString
from /usr/lib/libpython2.4.so.1.0
#33 PyRun_SimpleFileExFlags
from /usr/lib/libpython2.4.so.1.0
#34 PyRun_AnyFileExFlags
from /usr/lib/libpython2.4.so.1.0
#35 Py_Main
from /usr/lib/libpython2.4.so.1.0
#36 main
#0 __kernel_vsyscall



----------- .xsession-errors (366 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x342f147 (Headers/Fo)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Lost connection to the display ':0.0';
most likely the X server was shut down or you killed/destroyed
the window manager.
File /home/hansen/tmp/test-sheet.ods has finished changing
flushing all words
Finished indexing. Waiting for new events...
File /home/hansen/tmp/test-sheet.ods has finished changing
flushing all words
Finished indexing. Waiting for new events...
File /home/hansen/work/bluefish/useracl.bfproject has finished changing
flushing all words
Finished indexing. Waiting for new events...
--------------------------------------------------

Comment 1 Alex Graveley 2007-03-22 19:32:10 UTC


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