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 507713 - crash in Home Folder: Ich wollte mir die eigen...
crash in Home Folder: Ich wollte mir die eigen...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-06 19:59 UTC by 23517
Modified: 2008-01-07 13:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description 23517 2008-01-06 19:59:32 UTC 
What were you doing when the application crashed?
Ich wollte mir die eigenschaften anzeigen lassen 


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686-bigmem #1 SMP Mon Nov 12 09:52:20 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Clearlooks
Icon Theme: glass-icons

Memory status: size: 77438976 vsize: 77438976 resident: 28393472 share: 15835136 rss: 28393472 rss_rlim: 4294967295
CPU usage: start_time: 1199649526 rtime: 308 utime: 288 stime: 20 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 0xb6d716b0 (LWP 3364)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 184308

Thread 1 (Thread 0xb6d716b0 (LWP 3364))

  • #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 strcmp
    from /lib/i686/cmov/libc.so.6
  • #7 ??
  • #8 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (6 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-07 13:34:26 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 355018 ***