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 510035 - crash in Home Folder: I was showing the proper...
crash in Home Folder: I was showing the proper...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-17 00:16 UTC by thesupermouse
Modified: 2008-01-17 01:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description thesupermouse 2008-01-17 00:16:01 UTC 
What were you doing when the application crashed?
I was showing the properties of a folder in my home directory.
I am using Gnome 2.20 in Debian Lenny, and the problem occur whenever i try to show the properties of a folder.


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

System: Linux 2.6.22-3-486 #1 Mon Nov 12 07:53:08 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SlicknesS(black)
Icon Theme: black-white_2-Neon

Memory status: size: 80015360 vsize: 80015360 resident: 30142464 share: 15126528 rss: 30142464 rss_rlim: 4294967295
CPU usage: start_time: 1200528834 rtime: 188 utime: 174 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 0xb6d7c6b0 (LWP 3764)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 185631

Thread 1 (Thread 0xb6d7c6b0 (LWP 3764))

  • #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 






Comment 1


André Klapper





          2008-01-17 01:10:48 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 440988 ***