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 497466 - crash in Open Folder: Examined "Properties" th...
crash in Open Folder: Examined "Properties" th...
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-16 20:08 UTC by andyw
Modified: 2007-11-18 02:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description andyw 2007-11-16 20:08:20 UTC
Version: 2.18.3

What were you doing when the application crashed?
Examined "Properties" through right mouse click on a file.


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

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

Memory status: size: 123039744 vsize: 123039744 resident: 24875008 share: 14954496 rss: 24875008 rss_rlim: 4294967295
CPU usage: start_time: 1195217184 rtime: 1786 utime: 1518 stime: 268 cutime:191 cstime: 78 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 0xb6d436b0 (LWP 3797)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6d436b0 (LWP 3797))

  • #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 ---------------------
** 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
xscreensaver: 20:08:37: 0: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 20:08:37: 0: for window 0x100ac72 (nautilus / Nautilus)
xscreensaver: 20:08:39: -1: unrecognised ClientMessage "_NET_WM_STATE" received
xscreensaver: 20:08:39: -1: for window 0x100ac72 ((null) / (null))
--------------------------------------------------
Comment 1 André Klapper 2007-11-18 02:27:29 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 ***