Bug 491000 – crash in Open Folder: Logging in.

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 491000 - crash in Open Folder: Logging in.


Summary:	crash in Open Folder: Logging in.


Status:	RESOLVED DUPLICATE of bug 442829

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-10-28 09:54 UTC by Stefan Linnemann
Modified:	2007-10-29 02:09 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description Stefan Linnemann 2007-10-28 09:54:51 UTC

Version: 2.18.3

What were you doing when the application crashed?
Logging in.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21 #1 SMP Fri Oct 26 08:58:59 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 42991616 vsize: 42991616 resident: 11706368 share: 9027584 rss: 11706368 rss_rlim: 4294967295
CPU usage: start_time: 1193565135 rtime: 23 utime: 19 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208801568 (LWP 2904)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 173387

Thread 1 (Thread -1208801568 (LWP 2904))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 g_cclosure_marshal_VOID__ENUM
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 PyModule_GetDict
from /usr/lib/libpython2.5.so.1.0
#5 nautilus_python_init_python
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#6 nautilus_module_initialize
from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
#7 ??
#8 g_type_module_use
from /lib/libgobject-2.0.so.0
#9 nautilus_module_init
#10 nautilus_application_startup
#11 main
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
and start dcopserver again.
---------------------------------
kdeinit: Communication error with launcher. Exiting!
DCOP aborting (delayed) call from 'kded' to 'klauncher'
---------------------------------
It looks like dcopserver is already running. If you are sure
that it is not already running, remove /home/root/.DCOPserver_53550894.cable.casema.nl__0
and start dcopserver again.
---------------------------------
KDE Daemon (kded) already running.
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Throttle level is 0
--------------------------------------------------

Comment 1 André Klapper 2007-10-29 02:09:28 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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