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 533140 - crash in Open Folder: Accessing a folder on a ...
crash in Open Folder: Accessing a folder on a ...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-14 16:29 UTC by foilistforever
Modified: 2008-05-14 16:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description foilistforever 2008-05-14 16:29:51 UTC
Version: 2.20.0

What were you doing when the application crashed?
Accessing a folder on a shared drive.  The shared drive is controlled by a Linksys NAS NSLU2 with firmware revision V2.3R73.  The drive is a WD MyBook 160 GB connected to the NAS via USB port 1.  The folder of interest contains 112 or so subfolders and almost all of them are pictures.  The folder of interest also contains a dozen or so photos--at least one of which is about 8GB.  I'm pretty sure I've accessed this folder before using this machine with the current OS, but it may have been a previous version.

HTH,

Al


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

System: Linux 2.6.24-1-amd64 #1 SMP Thu Mar 27 16:52:38 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 448155648 vsize: 448155648 resident: 35446784 share: 16871424 rss: 35446784 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210782172 rtime: 164 utime: 145 stime: 19 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2ab556438b80 (LWP 28803)]
(no debugging symbols found)
0x00002ab54ff5dedf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2ab556438b80 (LWP 28803))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors (20 sec old) ---------------------
** (gnomebaker:1661): WARNING **: gbcommon_mkdir - failed to create [28]
(gnomebaker:1661): Gtk-WARNING **: Attempting to store changes into `/home/alan/.recently-used.xbel', but failed: Failed to write file '/home/alan/.recently-used.xbel.NJESAU': fwrite() failed: No spac
Warning: more than one line!
** (gnomebaker:19917): WARNING **: gbcommon_close_temp_file - Temporary file descriptor [/tmp/GnomeBaker-alan/gnomebaker-SRE5AU] could not be closed
** Message: <info>  You are now connected to the wired network.
** (gnome-system-monitor:14508): WARNING **: SELinux was found but is not enabled.
Window manager warning: Received a _NET_WM_MOVERESIZE message for 0x16e9dde (hdd_1_1_1 ); these messages lack timestamps and therefore suck.
seahorse nautilus module initialized
Initializing gnome-mount extension
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-14 16:53:37 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 ***