Bug 327867 – nautils don't start

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 327867 - nautils don't start


Summary:	nautils don't start


Status:	RESOLVED DUPLICATE of bug 327739

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-01-20 13:55 UTC by cyrille.mortreux
Modified:	2006-01-20 14:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description cyrille.mortreux 2006-01-20 13:55:05 UTC

Distribution: Ubuntu 6.04 (dapper)
Package: gnome-panel
Severity: Normal
Version: GNOME2.13.5 unspecified
Gnome-Distributor: Ubuntu
Synopsis: nautils don't start
Bugzilla-Product: gnome-panel
Bugzilla-Component: general
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.13.2)
Description:
Description of the crash:

Nautilus can't start at login. 

I tried in a console : 

cyrille@badlieutenant:~$ nautilus
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
Exception exceptions.ImportError: 'could not import gobject' in 'garbage
collection' ignored
Fatal Python error: unexpected exception during garbage collection

Steps to reproduce the crash:

Just log into your Gnome session.

Expected Results:


How often does this happen?

Every time

Additional Information:

Using Dapper, after the 2006-01-20 update. 



Debugging Information:

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

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1225292096 (LWP 5508)]
[New Thread -1228203088 (LWP 5509)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 65414

Thread 1 (Thread -1225292096 (LWP 5508))

#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 _PyObject_GC_Del
from /usr/lib/libpython2.4.so.1.0
#9 PyGC_Collect
from /usr/lib/libpython2.4.so.1.0
#10 Py_Finalize
from /usr/lib/libpython2.4.so.1.0
#11 nautilus_module_shutdown
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#12 nautilus_module_unload
at nautilus-module.c line 110
#13 g_type_module_unuse
from /usr/lib/libgobject-2.0.so.0
#14 nautilus_module_init
at nautilus-module.c line 174
#15 nautilus_application_startup
at nautilus-application.c line 360
#16 main
at nautilus-main.c line 424
#17 __libc_start_main
from /lib/tls/i686/cmov/libc.so.6
#18 _start
at ../sysdeps/i386/elf/start.S line 119
#0 __kernel_vsyscall





------- Bug created by bug-buddy at 2006-01-20 13:55 -------


Bugreport moved from gnome-panel / general
  to nautilus / general

Comment 1 Christian Kirbach 2006-01-20 14:02:47 UTC

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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