Bug 541778 – crash in Home Folder: Das Fenster geschlossen.

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 541778 - crash in Home Folder: Das Fenster geschlossen.


Summary:	crash in Home Folder: Das Fenster geschlossen.


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:	2008-07-06 16:17 UTC by schenck
Modified:	2008-07-06 21:23 UTC

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

Description schenck 2008-07-06 16:17:48 UTC

What were you doing when the application crashed?
Das Fenster geschlossen.


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.25.10 #1 SMP Sat Jul 5 13:56:00 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Dirty-Ice
Icon Theme: stilllife

Memory status: size: 83546112 vsize: 83546112 resident: 23056384 share: 14905344 rss: 23056384 rss_rlim: 4294967295
CPU usage: start_time: 1215359528 rtime: 1255 utime: 1183 stime: 72 cutime:0 cstime: 1 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 0xb6c1f720 (LWP 7038)]
(no debugging symbols found)
0xb7473f91 in waitpid () from /lib/libpthread.so.0

+ Trace 202169

Thread 1 (Thread 0xb6c1f720 (LWP 7038))

#0 waitpid
from /lib/libpthread.so.0
#1 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#2 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#3 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#4 <signal handler called>
#5 gconf_client_remove_dir
from /usr/lib/libgconf-2.so.4
#6 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#7 ??
#8 ??
from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
#9 ??
#0 waitpid
from /lib/libpthread.so.0



----------- .xsession-errors ---------------------
(gnumeric:7210): Gtk-WARNING **: Im Modulpfad »cleanice« konnte keine Themen-Engine gefunden werden,
Reading file:///home/ulrich/Daten/<>/xx.gnumeric
(gnumeric:7389): Gtk-WARNING **: Im Modulpfad »cleanice« konnte keine Themen-Engine gefunden werden,
Reading file:///home/ulrich/Daten/<>/xx.gnumeric
(gnumeric:7391): Gtk-WARNING **: Im Modulpfad »cleanice« konnte keine Themen-Engine gefunden werden,
Reading file:///home/ulrich/Daten/<>/xx.gnumeric
(gnumeric:7417): Gtk-WARNING **: Im Modulpfad »cleanice« konnte keine Themen-Engine gefunden werden,
Reading file:///home/ulrich/Daten/<>/xx.gnumeric
Writing file:///home/ulrich/Daten/<>/xx.gnumeric
(bug-buddy:7468): Gtk-WARNING **: Im Modulpfad »cleanice« konnte keine Themen-Engine gefunden werden,
--------------------------------------------------

Comment 1 A. Walton 2008-07-06 21:23:41 UTC


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