Bug 536380 – 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 536380 - crash in Home Folder:


Summary:	crash in Home Folder:


Status:	RESOLVED DUPLICATE of bug 522534

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-06-03 07:53 UTC by loubega
Modified:	2008-06-03 10:26 UTC

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

Description loubega 2008-06-03 07:53:42 UTC

What were you doing when the application crashed?



Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Gorilla
Icon Theme: Gorilla

Memory status: size: 94330880 vsize: 94330880 resident: 39645184 share: 17297408 rss: 39645184 rss_rlim: 4294967295
CPU usage: start_time: 1212479591 rtime: 293 utime: 279 stime: 14 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/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b73720 (LWP 3307)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 199463

Thread 1 (Thread 0xb6b73720 (LWP 3307))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 ??
#7 ??
#8 ??
#9 ??
#10 ??
from /usr/lib/libglib-2.0.so.0
#11 ??
#12 ??
#13 ??
#14 ??
from /usr/lib/libglib-2.0.so.0
#15 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
  -system        	Anwendung in System-Cache importieren	
  -codebase <url>	Ressourcen aus der angegebenen Code-Basis abrufen	
  -shortcut      	Verknüpfungen wie vom Benutzer zugelassene Aufforderung installieren	
  -association   	Zuordnungen wie vom Benutzer zugelassene Aufforderung installieren	
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x3c00007 festgelegt für 0x3c00011 (Java Web S).
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x3c00007 festgelegt für 0x3c00011 (Java Web S).
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x3c00007 festgelegt für 0x3c00011 (Anwendung ).
/dev/dsp: Das Gerät oder die Ressource ist belegt
** (nautilus:30738): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »share«), teilen Sie dies der gnome-vfs-Mailingliste mit.
seahorse nautilus module initialized
Initializing gnome-mount extension
** (nautilus:3307): WARNING **: Keine Beschreibung für MIME-Type »x-directory/smb-share« gefunden (Datei ist »share«), teilen Sie dies der gnome-vfs-Mailingliste mit.
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-06-03 10:26:13 UTC

Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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