Bug 419815 – crash in Gimmie: I was using synaptics, a...

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 419815 - crash in Gimmie: I was using synaptics, a...


Summary:	crash in Gimmie: I was using synaptics, a...


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-18 17:57 UTC by r.e.buscher
Modified:	2007-03-18 23:43 UTC

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

Description r.e.buscher 2007-03-18 17:57:07 UTC

What were you doing when the application crashed?
I was using synaptics, and didn't even notice it crashed...
But since this report comes up, I guess it did. Hm.
Also I was using opera, a terminal and sky and gaim and had just closed zim (newly installed).
I run edgy on a lifebook s7010. 
Hope this helpss


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

Memory status: size: 101879808 vsize: 0 resident: 101879808 share: 0 rss: 26988544 rss_rlim: 0
CPU usage: start_time: 1174239537 rtime: 0 utime: 86 stime: 0 cutime:76 cstime: 0 timeout: 10 it_real_value: 0 frequency: 0

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

(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 -1209698640 (LWP 26833)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119785

Thread 1 (Thread -1209698640 (LWP 26833))

#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 PyFrame_New
#5 PyEval_EvalCodeEx
#6 PyClassMethod_New
#7 PyObject_Call
#8 PyEval_CallObjectWithKeywords
#9 PyObject_CallObject
#10 initgmenu
from /usr/lib/python2.4/site-packages/gmenu.so
#11 ??
from /usr/lib/libgnome-menu.so.2
#12 ??
#13 ??
#14 ??
#15 gmenu_tree_add_monitor
from /usr/lib/libgnome-menu.so.2
#16 gmenu_tree_get_directory_from_path
from /usr/lib/libgnome-menu.so.2
#17 ??
from /usr/lib/libgnome-menu.so.2
#18 ??
#19 ??
#20 ??
#21 ??
from /usr/lib/libgnome-menu.so.2
#22 ??
#23 ??
#0 __kernel_vsyscall

Comment 1 Tony Tsui 2007-03-18 22:07:32 UTC

This seems like a duplicate of bug 419271.

Comment 2 Alex Graveley 2007-03-18 23:43:42 UTC


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