Bug 359408 – crash in Deskbar: enabled beagle search, t...

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 359408 - crash in Deskbar: enabled beagle search, t...


Summary:	crash in Deskbar: enabled beagle search, t...


Status:	RESOLVED DUPLICATE of bug 359335

Product:	deskbar-applet
Classification:	Deprecated
Component:	general
Version:	unspecified
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Deskbar Applet Maintainer(s)
QA Contact:	Deskbar Applet Maintainer(s)

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-03 20:57 UTC by michael.rose
Modified:	2006-10-03 23:01 UTC

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

Description michael.rose 2006-10-03 20:57:08 UTC

What were you doing when the application crashed?
enabled beagle search, then began to type a search string, I typed one letter "g" and it crashed.

:(


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

Memory status: size: 90750976 vsize: 0 resident: 90750976 share: 0 rss: 38952960 rss_rlim: 0
CPU usage: start_time: 1159908938 rtime: 0 utime: 341 stime: 0 cutime:312 cstime: 0 timeout: 29 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/libexec/deskbar-applet'

(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 -1210231120 (LWP 12861)]
[New Thread -1279427680 (LWP 12867)]
[New Thread -1271034976 (LWP 12865)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 74352

Thread 1 (Thread -1210231120 (LWP 12861))

#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 PyObject_Malloc
#5 PyCObject_FromVoidPtr
#6 PyArg_UnpackTuple
#7 PyArg_UnpackTuple
#8 PyArg_ParseTupleAndKeywords
#9 PyArg_ParseTuple
#10 initposix
#11 initposix
#12 PyEval_EvalFrame
#13 PyEval_EvalFrame
#14 PyEval_EvalCodeEx
#15 PyEval_EvalFrame
#16 PyEval_EvalCodeEx
#17 PyEval_EvalFrame
#18 PyEval_EvalFrame
#19 PyEval_EvalFrame
#20 PyEval_EvalFrame
#21 PyEval_EvalFrame
#22 PyEval_EvalFrame
#23 PyEval_EvalFrame
#24 PyEval_EvalFrame
#25 PyEval_EvalFrame
#26 PyEval_EvalFrame
#27 PyEval_EvalCodeEx
#28 PyClassMethod_New
#29 PyObject_Call
#30 PyClass_IsSubclass
#31 PyObject_Call
#32 PyEval_CallObjectWithKeywords
#33 PyObject_CallObject
#34 init_gobject
from /var/lib/python-support/python2.4/gtk-2.0/gobject/_gobject.so
#35 g_source_get_current_time
from /usr/lib/libglib-2.0.so.0
#36 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#37 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#38 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#39 bonobo_main
from /usr/lib/libbonobo-2.so.0
#40 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#41 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#42 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#43 initgnomeapplet
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomeapplet.so
#44 PyEval_EvalFrame
#45 PyEval_EvalCodeEx
#46 PyEval_EvalCode
#47 PyRun_FileExFlags
#48 PyRun_SimpleFileExFlags
#49 Py_Main
#50 main
#0 __kernel_vsyscall

Comment 1 Sebastien Bacher 2006-10-03 23:01:55 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 359335 ***