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 316595 - Crash in gnome-vfs if any python extension for nautilus is installed
Crash in gnome-vfs if any python extension for nautilus is installed
Status: RESOLVED FIXED
Product: nautilus-python
Classification: Other
Component: general
Git Master
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-09-17 20:17 UTC by shackan
Modified: 2005-09-19 19:35 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12



Description shackan 2005-09-17 20:17:03 UTC
Steps to reproduce:
1. install the example module pyfs.py (
/usr/share/doc/python2.4-gnome2/examples/vfs/pygvfsmethod )
2. install the example nautilus extension open-terminal.py (
/usr/share/doc/python-nautilus/examples/ )
3. try tu run the above gnome-vfs module following the instructions in the README
4. BOOM!

Stack trace:

can't get a stack trace (can't find a ready-made debug build of nautilus), the
only useful thing gdb tells me, after the crash, is 

(gdb) Current source file is ../Python/pystate.c

Probably either the python gnome-vfs bindings or the python-nautilus bindings
have don't acquire/release the GIL properly, or fail to set the proper
theadstate somewhere, anyway seems a bad beast to debug..

Other information:
the paths above refer to Ubuntu Linux.

the same behaviour appeared whenever a python nautilus extension and a python
gvfs module were run (thus, not only with those above indicated), including some
I'm developing myself.

Python g-vfs modules stop crashing if every python nautilus extension is removed.
Comment 1 Brent Smith (smitten) 2005-09-18 00:18:31 UTC
this is all I get when attempting to run nautilus after copying pyfs.conf to
~/.gnome2/vfs/modules/

nautilus: symbol lookup error: nautilus: undefined symbol: nautilus_sound_init
Comment 2 shackan 2005-09-18 15:07:13 UTC
I got a stack trace:

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226520896 (LWP 11067)]
[New Thread -1242068048 (LWP 11079)]
[New Thread -1241801808 (LWP 11078)]
[New Thread -1228301392 (LWP 11068)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226520896 (LWP 11067))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 PyObject_GetAttrString
    at ../Objects/object.c line 1011

Comment 3 shackan 2005-09-18 19:35:16 UTC
using nautilus-python from CVS removes the crash
Comment 4 Brent Smith (smitten) 2005-09-19 19:35:12 UTC
reassigning to correct product and closing as fixed based on reporter's feedback.