Bug 568444 – crash in Home Folder:

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 568444 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 480179

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2009-01-20 15:53 UTC by meier
Modified:	2009-01-20 16:52 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description meier 2009-01-20 15:53:16 UTC

What were you doing when the application crashed?



Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79769600 vsize: 79769600 resident: 22056960 share: 15568896 rss: 22056960 rss_rlim: 4294967295
CPU usage: start_time: 1232466729 rtime: 184 utime: 171 stime: 13 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6a17710 (LWP 5648)]
0xb7f59424 in __kernel_vsyscall ()

+ Trace 211711

Thread 1 (Thread 0xb6a17710 (LWP 5648))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 gconf_client_remove_dir
from /usr/lib/libgconf-2.so.4
#8 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#9 ??
#10 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#11 ??
#0 __kernel_vsyscall



----------- .xsession-errors (22 sec old) ---------------------
  at Mono.Addins.Setup.AddinStore.DownloadObject (IProgressMonitor monitor, System.String url, System.Type type) [0x00000] 
  at Mono.Addins.Setup.RepositoryRegistry.UpdateRepository (IProgressMonitor monitor, System.Uri baseUri, Mono.Addins.Setup.RepositoryRecord rr) [0x00000] 
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Fenstermanager-Warnung:Bildschirm 0 auf Anzeige »:0.0« hat bereits einen Fenstermanager
Initializing gnome-mount extension
seahorse nautilus module initialized
Initializing nautilus-open-terminal extension
--------------------------------------------------

Comment 1 palfrey 2009-01-20 16:52:15 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 480179 ***