Bug 420530 – crash in Gimmie: Updating some system pac...

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 420530 - crash in Gimmie: Updating some system pac...


Summary:	crash in Gimmie: Updating some system pac...


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-20 13:49 UTC by Deji Akingunola
Modified:	2007-03-20 20:19 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Deji Akingunola 2007-03-20 13:49:31 UTC

What were you doing when the application crashed?
Updating some system packages


Distribution: Fedora release 6.91 (Rawhide)
Gnome Release: 2.18.0 2007-03-13 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-1.2997.fc7 #1 SMP Fri Mar 16 22:09:12 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10299901
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks-Curve3
Icon Theme: Bluecurve

Memory status: size: 542445568 vsize: 542445568 resident: 19537920 share: 7155712 rss: 19537920 rss_rlim: 18446744073709551615
CPU usage: start_time: 1174277309 rtime: 653 utime: 569 stime: 84 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912499847472 (LWP 27690)]
(no debugging symbols found)
0x000000333380d83f in waitpid () from /lib64/libpthread.so.0

+ Trace 120346

Thread 1 (Thread 46912499847472 (LWP 27690))

#0 waitpid
from /lib64/libpthread.so.0
#1 ??
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 __assert_fail
from /lib64/libc.so.6
#6 PyEval_EvalCodeEx
from /usr/lib64/libpython2.5.so.1.0
#7 ??
from /usr/lib64/libpython2.5.so.1.0
#8 PyObject_Call
from /usr/lib64/libpython2.5.so.1.0
#9 PyEval_CallObjectWithKeywords
from /usr/lib64/libpython2.5.so.1.0
#10 ??
from /usr/lib64/python2.5/site-packages/gmenu.so
#11 ??
from /usr/lib64/libgnome-menu.so.2
#12 ??
from /usr/lib64/libgnome-menu.so.2
#13 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#14 ??
from /lib64/libglib-2.0.so.0
#15 g_main_loop_run
from /lib64/libglib-2.0.so.0
#16 bonobo_main
from /usr/lib64/libbonobo-2.so.0
#17 bonobo_generic_factory_main_timeout
from /usr/lib64/libbonobo-2.so.0
#18 panel_applet_factory_main_closure
from /usr/lib64/libpanel-applet-2.so.0
#19 ??
from /usr/lib64/python2.5/site-packages/gtk-2.0/gnomeapplet.so
#20 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#21 PyEval_EvalFrameEx
from /usr/lib64/libpython2.5.so.1.0
#22 PyEval_EvalCodeEx
from /usr/lib64/libpython2.5.so.1.0
#23 PyEval_EvalCode
from /usr/lib64/libpython2.5.so.1.0
#24 ??
from /usr/lib64/libpython2.5.so.1.0
#25 PyRun_FileExFlags
from /usr/lib64/libpython2.5.so.1.0
#26 PyRun_SimpleFileExFlags
from /usr/lib64/libpython2.5.so.1.0
#27 Py_Main
from /usr/lib64/libpython2.5.so.1.0
#28 __libc_start_main
from /lib64/libc.so.6
#29 _start
#0 waitpid
from /lib64/libpthread.so.0

Comment 1 Alex Graveley 2007-03-20 20:19:36 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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