Bug 442602 – crash in Gimmie: nothing..

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 442602 - crash in Gimmie: nothing..


Summary:	crash in Gimmie: nothing..


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-05-31 14:24 UTC by sergiovier
Modified:	2007-09-04 21:24 UTC

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

Description sergiovier 2007-05-31 14:24:42 UTC

What were you doing when the application crashed?
nothing..


Distribution: Debian lenny/sid
Gnome Release: 2.18.1 2007-04-25 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-1-amd64 #1 SMP Fri May 18 23:28:21 CEST 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Pharago
Icon Theme: humility-icons-MERGE

Memory status: size: 276135936 vsize: 276135936 resident: 32899072 share: 15773696 rss: 32899072 rss_rlim: 18446744073709551615
CPU usage: start_time: 1180618694 rtime: 73 utime: 58 stime: 15 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/lib/bug-buddy/gimmie_applet'

(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 47311307396848 (LWP 3072)]
(no debugging symbols found)
0x00002b0784ed4c9f in waitpid () from /lib/libpthread.so.0

+ Trace 137022

Thread 1 (Thread 47311307396848 (LWP 3072))

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



----------- .xsession-errors (1537 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------

Comment 1 Benedikt Henrichs 2007-09-04 21:24:29 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 ***