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 484984 - deskbar-applet crashed with SIGSEGV in PyType_Type()
deskbar-applet crashed with SIGSEGV in PyType_Type()
Status: RESOLVED INCOMPLETE
Product: deskbar-applet
Classification: Deprecated
Component: general
2.20.x
Other Linux
: Normal critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-10-09 09:16 UTC by Sebastien Bacher
Modified: 2010-01-20 01:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Sebastien Bacher 2007-10-09 09:16:37 UTC 
The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/deskbar-applet/+bug/150730

"Binary package hint: deskbar-applet

I was using firefox for about 5 minutes when this happened nothing else. Don't know why it happened so this is quite a bad bug report.
...
Package: deskbar-applet 2.20.0-0ubuntu2
...
.

+ Trace 168968

Thread 1 (process 5786)

  • #0 visit_decref
    at ../Modules/gcmodule.c line 270
  • #1 dict_traverse
    at ../Objects/dictobject.c line 1889
  • #2 collect
    at ../Modules/gcmodule.c line 295
  • #3 _PyObject_GC_New
    at ../Modules/gcmodule.c line 897
  • #4 PyList_New
    at ../Objects/listobject.c line 103
  • #5 string_split
    at ../Objects/stringobject.c line 1421
  • #6 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3564
  • #7 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #8 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #9 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2831
  • #10 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3660
  • #11 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2831
  • #12 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3660
  • #13 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #14 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #15 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2831
  • #16 function_call
    at ../Objects/funcobject.c line 517
  • #17 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #18 instancemethod_call
    at ../Objects/classobject.c line 2509
  • #19 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #20 PyEval_CallObjectWithKeywords
    at ../Python/ceval.c line 3433
  • #21 PyInstance_New
    at ../Objects/classobject.c line 560
  • #22 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #23 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3775
  • #24 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #25 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #26 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #27 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #28 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #29 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2831
  • #30 function_call
    at ../Objects/funcobject.c line 517
  • #31 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #32 instancemethod_call
    at ../Objects/classobject.c line 2509
  • #33 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #34 PyEval_CallObjectWithKeywords
    at ../Python/ceval.c line 3433
  • #35 PyInstance_New
    at ../Objects/classobject.c line 560
  • #36 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #37 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3775
  • #38 PyEval_EvalFrameEx
    at ../Python/ceval.c line 3650
  • #39 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2831
  • #40 function_call
    at ../Objects/funcobject.c line 517
  • #41 PyObject_Call
    at ../Objects/abstract.c line 1860
  • #42 PyEval_CallObjectWithKeywords
    at ../Python/ceval.c line 3433
  • #43 PyObject_CallObject
    at ../Objects/abstract.c line 1851 
..."
Comment 1 André Klapper 2009-11-08 13:10:14 UTC 
This crash report has not seen any changes or updates for more than 2 years.

Does this issue still happen in GNOME 2.26 or 2.28? Can you please update this
report by adding a short comment, removing the NEEDINFO state again and
updating the "Version" field if this is still an issue?

Again thank you for reporting this bug and we are sorry it could not be handled
for the version you originally used here.
Comment 2 Javier Jardón (IRC: jjardon) 2010-01-20 01:16:57 UTC 
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!