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 304587 - nautilus-file-management-properties crash with message "Fatal Python error: This module can only be used from nautilus"
nautilus-file-management-properties crash with message "Fatal Python error: T...
Status: RESOLVED DUPLICATE of bug 161946
Product: nautilus
Classification: Core
Component: Preferences
unspecified
Other other
: Normal normal
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-05-17 22:55 UTC by schlupp23
Modified: 2005-05-18 07:42 UTC
See Also:
GNOME target: ---
GNOME version: 2.9/2.10


Description schlupp23 2005-05-17 22:55:21 UTC 
Distribution: Debian 3.1
Package: nautilus
Severity: normal
Version: GNOME2.10.1 unspecified
Gnome-Distributor: Ubuntu
Synopsis: nautilus-file-management-properties crash with message "Fatal Python error: This module can only be used from nautilus"
Bugzilla-Product: nautilus
Bugzilla-Component: Preferences
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.10.0)
Description:
Description of the crash:


Steps to reproduce the crash:
1. nautilus-file-management-properties 
2. 
3. 

Expected Results:
Fatal Python error: This module can only be used from nautilus

How often does this happen?
Always

Additional Information:
Ubuntu 5.10


Debugging Information:

Backtrace was generated from
'/usr/bin/nautilus-file-management-properties'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
[Thread debugging using libthread_db enabled]
[New Thread -1224218944 (LWP 15666)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 59826

Thread 1 (Thread -1224218944 (LWP 15666))

  • #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 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 Py_FatalError
    from /usr/lib/libpython2.4.so.1.0
  • #8 initnautilus
    from /usr/lib/nautilus-python/nautilus.so
  • #9 _PyImport_LoadDynamicModule
    from /usr/lib/libpython2.4.so.1.0
  • #10 _PyImport_FindModule
    from /usr/lib/libpython2.4.so.1.0
  • #11 PyImport_ReloadModule
    from /usr/lib/libpython2.4.so.1.0
  • #12 PyImport_ReloadModule
    from /usr/lib/libpython2.4.so.1.0
  • #13 PyImport_ImportModuleEx
    from /usr/lib/libpython2.4.so.1.0
  • #14 _PyUnicodeUCS4_ToLowercase
    from /usr/lib/libpython2.4.so.1.0
  • #15 PyCFunction_Call
    from /usr/lib/libpython2.4.so.1.0
  • #16 PyObject_Call
    from /usr/lib/libpython2.4.so.1.0
  • #17 PyObject_CallFunction
    from /usr/lib/libpython2.4.so.1.0
  • #18 PyImport_Import
    from /usr/lib/libpython2.4.so.1.0
  • #19 PyImport_ImportModule
    from /usr/lib/libpython2.4.so.1.0
  • #20 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #21 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #22 nautilus_module_load
    at nautilus-module.c line 98
  • #23 g_type_module_use
    from /usr/lib/libgobject-2.0.so.0
  • #24 nautilus_module_init
    at nautilus-module.c line 172
  • #25 main
    at nautilus-file-management-properties-main.c line 62
  • #0 __kernel_vsyscall 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-17 22:55 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@bugzilla.gnome.org.
   Previous reporter was schlupp23@gmx.net.
Comment 1 Sebastien Bacher 2005-05-18 07:42:04 UTC 
this crash is due to the python-nautilus package duplicate of bug #161946

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