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 527331 - crash in Open Folder: Accessing a directory on...
crash in Open Folder: Accessing a directory on...
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-04-10 12:00 UTC by someman7
Modified: 2008-04-11 10:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description someman7 2008-04-10 12:00:34 UTC
Version: 2.20.0

What were you doing when the application crashed?
Accessing a directory on my network, which is actually a partition shared on a Windows computer. I actualy entered the directory, but when I accessed a subdirectory, it crashed.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu Mar 27 17:45:04 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Simple
Icon Theme: gnome

Memory status: size: 75165696 vsize: 75165696 resident: 25202688 share: 15310848 rss: 25202688 rss_rlim: 4294967295
CPU usage: start_time: 1207823781 rtime: 216 utime: 200 stime: 16 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 0xb6ba7720 (LWP 3217)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6ba7720 (LWP 3217))

  • #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 ??
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (8 sec old) ---------------------
Error reading ulBuffNum
Error reading ulBuffNum
Error reading ulBuffNum
Error reading ulBuffNum
/usr/lib/python2.4/site-packages/apt/__init__.py:18: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
Window manager warning: last_user_time (3076129840) is greater than comparison timestamp (940948721).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET
Window manager warning: 0x2e00003 (Software U) appears to be one of the offending windows with a timestamp of 3076129840.  Working around...
current dist not found in meta-release file
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3217): WARNING **: No description found for mime type "x-directory/smb-share" (file is "Podaci%20(D)"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Gianluca Borello 2008-04-11 10:53:59 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 522534 ***