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 376183 - Python gnomekeyring segfaults on multicore systems
Python gnomekeyring segfaults on multicore systems
Status: RESOLVED DUPLICATE of bug 363019
Product: gnome-python-extras
Classification: Deprecated
Component: general
2.14.x
Other All
: Normal critical
: ---
Assigned To: Nobody's working on this now (help wanted and appreciated)
Python bindings maintainers
Depends on:
Blocks:
 
 
Reported: 2006-11-17 04:01 UTC by John Stowers
Modified: 2006-11-17 10:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Stowers 2006-11-17 04:01:32 UTC 
Steps to reproduce:
#!/usr/bin/python
import gnomekeyring
keyring = gnomekeyring.get_default_keyring_sync()


Stack trace:
Starting program: /usr/bin/python keyring_broken.py
[Thread debugging using libthread_db enabled]
[New Thread -1210394960 (LWP 13714)]

** (process:13714): WARNING **: g_set_application_name not set.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1210394960 (LWP 13714)]
0xb7e1ac53 in strlen () from /lib/tls/i686/cmov/libc.so.6
(gdb) thread apply all bt

+ Trace 87117

Thread 1 (Thread -1210394960 (LWP 13714))

  • #0 strlen
    from /lib/tls/i686/cmov/libc.so.6
  • #1 PyString_FromString
    at ../Objects/stringobject.c line 106
  • #2 initgnomekeyring
    from /usr/lib/python2.4/site-packages/gtk-2.0/gnomekeyring.so
  • #3 PyEval_EvalFrame
    at ../Python/ceval.c line 3552
  • #4 PyEval_EvalCodeEx
    at ../Python/ceval.c line 2741
  • #5 PyEval_EvalCode
    at ../Python/ceval.c line 484
  • #6 PyRun_FileExFlags
    at ../Python/pythonrun.c line 1285
  • #7 PyRun_SimpleFileExFlags
    at ../Python/pythonrun.c line 869
  • #8 Py_Main
    at ../Modules/main.c line 493
  • #9 main
    at ../Modules/python.c line 23 


Other information:
Running Ubuntu Edgy. I have a P4 3GHz hyperthreading (dual core?) CPU. The same code works on my P4 mobile laptop without trouble

This code snippet was isolated as causing the problem in a larger application I am working on (http://www.conduit-project.org)
Comment 1 Gustavo Carneiro 2006-11-17 10:43:23 UTC 

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