Bug 320335 – deskbar-applet 0.8.3 segfaults after a while

Bug 320335 - deskbar-applet 0.8.3 segfaults after a while


Summary:	deskbar-applet 0.8.3 segfaults after a while

Status:	RESOLVED FIXED

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

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

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2005-10-31 18:11 UTC by Mikkel Kamstrup Erlandsen
Modified:	2005-11-24 12:25 UTC (History)
CC List:	0 users

See Also:
GNOME target:	---
GNOME version:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Mikkel Kamstrup Erlandsen 2005-10-31 18:11:37 UTC

Steps to reproduce:
1. Add deskbar to the panel
2. wait


Stack trace:
Program received signal SIGSEGV, Segmentation fault.

+ Trace 63821

Thread NaN (LWP 15443)

#0 ??
#1 Py_GetPath
#2 PyTuple_Pack
#3 _PyObject_GC_Track
#4 _PyObject_GC_New
#5 PyList_New
#6 PyEval_EvalFrame
#7 PyEval_EvalFrame
#8 PyEval_EvalFrame
#9 PyEval_EvalFrame
#10 PyEval_EvalFrame
#11 PyEval_EvalFrame
#12 PyEval_EvalFrame
#13 PyEval_EvalCodeEx
#14 PyFunction_SetClosure
#15 PyObject_Call
#16 PyMethod_New
#17 PyObject_Call
#18 PyEval_CallObjectWithKeywords
#19 PyInstance_New
#20 PyObject_Call
#21 PyEval_EvalFrame
#22 PyEval_EvalFrame
#23 PyEval_EvalCodeEx
#24 PyFunction_SetClosure
#25 PyObject_Call
#26 PyEval_CallObjectWithKeywords
#27 PyObject_CallObject
#28 initgobject
#29 g_closure_invoke
from /usr/lib/libgobject-2.0.so.0
#30 g_signal_stop_emission
from /usr/lib/libgobject-2.0.so.0
#31 g_signal_emitv
from /usr/lib/libgobject-2.0.so.0
#32 initgobject
from /usr/lib/python2.4/site-packages/gtk-2.0/gobject.so
#33 PyEval_EvalFrame
#34 PyEval_EvalCodeEx
#35 PyFunction_SetClosure
#36 PyObject_Call
#37 PyMethod_New
#38 PyObject_CallFunction
#39 ??
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomevfs.so
#40 ??
#41 ??
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomevfs.so
#42 ??
#43 ??
#44 ??
#45 ??
#46 ??
#47 ??
from /usr/lib/libgnomevfs-2.so.0
#48 ??
#49 ??
#50 ??
#51 _gnome_vfs_monitor_do_cancel
from /usr/lib/libgnomevfs-2.so.0
#52 _gnome_vfs_monitor_do_cancel
#53 g_child_watch_add
from /usr/lib/libglib-2.0.so.0
#54 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#55 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#56 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#57 bonobo_main
from /usr/lib/libbonobo-2.so.0
#58 bonobo_generic_factory_main_timeout
from /usr/lib/libbonobo-2.so.0
#59 bonobo_generic_factory_main
from /usr/lib/libbonobo-2.so.0
#60 panel_applet_factory_main_closure
from /usr/lib/libpanel-applet-2.so.0
#61 initgnomeapplet
from /usr/lib/python2.4/site-packages/gtk-2.0/gnomeapplet.so
#62 PyEval_EvalFrame
#63 PyEval_EvalCodeEx
#64 PyEval_EvalCode
#65 PyRun_FileExFlags
#66 PyRun_SimpleFileExFlags
#67 Py_Main
#68 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#69 _start



Other information:

Comment 1 Raphael Slinckx 2005-10-31 18:25:37 UTC

Can you try to remove import gtk; gtk.threads_init() in deskbar-applet, and
replace it by

import gobject
gobject.threads_init()

Maybe that will work, and maybe it will also break everything else..

Comment 2 Mikkel Kamstrup Erlandsen 2005-10-31 18:48:54 UTC

I'm trying it right now... Just waiting for it to crash (if it still does that)

You do realize that this breaks window-mode deskbar..?

Comment 3 Raphael Slinckx 2005-10-31 19:01:33 UTC

No, i didn't try it here. Threads are evil. I hate Threads.

Why is window-mode broken ? is it a freeze ? you can add import gtk, if you
want, but after the import gobject: init() lines

Comment 4 Mikkel Kamstrup Erlandsen 2005-10-31 20:55:41 UTC

It's not broken in any unfixable way... It's just that we need the gtk module to
create the window :)

Adding a "import gtk" in the line 84 "if standalone:" statement should fix it I
think.

Until now, no segfaults since my last post...

Comment 5 Raphael Slinckx 2005-11-04 14:49:31 UTC

I think that is solved ?

Comment 6 Mikkel Kamstrup Erlandsen 2005-11-24 12:25:30 UTC

Since I'm on a crappy public computer, bugzilla is my only mean of 
communication...

I'll just say that I'll be off development a while since my wife and daughter 
(to be born) is commited to hospital. Internet acces is severely restricted 
here, and I have no idea when we'll be out again... It might be up to a 
month :-(

Keep up the happy hacking. I'm really sorry for bugging out on the Cuemiac 
branch this way, but real life is really real sometimes.

See ya 'round.

Cheers
Mikkkel

Note You need to log in before you can comment on or make changes to this bug.