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 539555 - crash in Open Folder: Navigating to my neywork...
crash in Open Folder: Navigating to my neywork...
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-06-22 03:44 UTC by rongg
Modified: 2008-06-22 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description rongg 2008-06-22 03:44:04 UTC
Version: 2.20.0

What were you doing when the application crashed?
Navigating to my neywork drive:  smb://MSS-00113F/Public/Documents/office. Trying to open 'office' in Nautilus crashes every time.
Netowrk drive is Maxtor 300GB


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-686 #1 SMP Thu May 8 02:16:39 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 56791040 vsize: 56791040 resident: 22515712 share: 14794752 rss: 22515712 rss_rlim: 4294967295
CPU usage: start_time: 1214105699 rtime: 333 utime: 313 stime: 20 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 0xb6bc4940 (LWP 3907)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6bc4940 (LWP 3907))

  • #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 (10 sec old) ---------------------
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2804875 (Save as)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (soffice:3767): WARNING **: FIXME: No valid length
** (soffice:3767): WARNING **: FIXME: No valid length
** (soffice:3767): WARNING **: FIXME: No valid length
** (soffice:3767): WARNING **: FIXME: No valid length
Initializing gnome-mount extension
seahorse nautilus module initialized
** (nautilus:3907): WARNING **: No description found for mime type "x-directory/smb-share" (file is "config"), please tell the gnome-vfs mailing list.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-22 12:14:53 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 ***