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 497860 - crash in Open Folder: I've tried to view propr...
crash in Open Folder: I've tried to view propr...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-18 11:29 UTC by natonx
Modified: 2007-11-18 16:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description natonx 2007-11-18 11:29:39 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I've tried to view proprieties of Folder


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 88588288 vsize: 88588288 resident: 38645760 share: 15446016 rss: 38645760 rss_rlim: 4294967295
CPU usage: start_time: 1195379651 rtime: 35088 utime: 29835 stime: 5253 cutime:4686 cstime: 459 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 0xb6e1f8c0 (LWP 4403)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 178485

Thread 1 (Thread 0xb6e1f8c0 (LWP 4403))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (2339 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
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 16:54:38 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 440988 ***