Bug 472245 – crash in Computer: login

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 472245 - crash in Computer: login


Summary:	crash in Computer: login


Status:	RESOLVED DUPLICATE of bug 449488

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-08-31 15:35 UTC by lord117
Modified:	2007-09-11 13:56 UTC

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

Description lord117 2007-08-31 15:35:53 UTC

Version: 2.18.3

What were you doing when the application crashed?
login	


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.20-2931.fc7xen #1 SMP Mon Aug 13 10:12:37 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 41009152 vsize: 41009152 resident: 9285632 share: 7831552 rss: 9285632 rss_rlim: 4294967295
CPU usage: start_time: 1188573128 rtime: 27 utime: 4 stime: 23 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/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208129824 (LWP 3016)]
(no debugging symbols found)
0x0029b402 in __kernel_vsyscall ()

+ Trace 159397

Thread 1 (Thread -1208129824 (LWP 3016))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/nosegneg/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 ??
from /usr/lib/libhal.so.1
#5 _init
from /usr/lib/libhal.so.1
#6 call_init
from /lib/ld-linux.so.2
#7 _dl_init_internal
from /lib/ld-linux.so.2
#8 dl_open_worker
from /lib/ld-linux.so.2
#9 _dl_catch_error
from /lib/ld-linux.so.2
#10 _dl_open
from /lib/ld-linux.so.2
#11 dlopen_doit
from /lib/libdl.so.2
#12 _dl_catch_error
from /lib/ld-linux.so.2
#13 _dlerror_run
from /lib/libdl.so.2
#14 dlopen
from /lib/libdl.so.2
#15 g_module_open
from /lib/libgmodule-2.0.so.0
#16 ??
#17 g_type_module_use
from /lib/libgobject-2.0.so.0
#18 nautilus_module_init
#19 nautilus_application_startup
#20 main
#0 __kernel_vsyscall


----------- .xsession-errors ---------------------
localuser:root being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2901
(nautilus:3016): libgnomevfs-WARNING **: Failed to activate daemon: Process /usr/libexec/gnome-vfs-daemon received signal 11
(gnome-panel:3014): libgnomevfs-WARNING **: Failed to activate daemon: Process /usr/libexec/gnome-vfs-daemon received signal 11
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
--------------------------------------------------

Comment 1 André Klapper 2007-09-11 13:56:22 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 449488 ***