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 531939 - crash in Open Folder: Browsing samba folder. I...
crash in Open Folder: Browsing samba folder. I...
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-07 12:55 UTC by vesavan
Modified: 2008-05-07 13:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description vesavan 2008-05-07 12:55:18 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Browsing samba folder. I still get this error, even i updated, upgraded and restarted.




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 Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 457850880 vsize: 457850880 resident: 43544576 share: 17952768 rss: 43544576 rss_rlim: 18446744073709551615
CPU usage: start_time: 1210163567 rtime: 321 utime: 287 stime: 34 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 0x2ac3b69e6b80 (LWP 4109)]
(no debugging symbols found)
0x00002ac3b050bedf in waitpid () from /lib/libpthread.so.0

+ Trace 197125

Thread 1 (Thread 0x2ac3b69e6b80 (LWP 4109))

  • #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 (146 sec old) ---------------------
Window manager warning: Failed to read saved session file /home/vesa/.metacity/sessions/default0.ms: Failed to open file '/home/vesa/.metacity/sessions/default0.ms': No such file or directory
Initializing gnome-mount extension
seahorse nautilus module initialized
CalDAV Eplugin starting up ...
evolution-shell-Message: Killing old version of evolution-data-server...
** (evolution:4292): DEBUG: mailto URL command: evolution %s
** (evolution:4292): DEBUG: mailto URL program: evolution
BBDB spinning up...
(evolution:4292): evolution-mail-WARNING **: Cannot activate OAFIID:GNOME_Spell_Dictionary:0.3

(gnome-terminal:5496): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Window manager warning: last_user_time (375489184) is greater than comparison timestamp (694747).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACT
Window manager warning: 0x2e00020 (Terminal) appears to be one of the offending windows with a timestamp of 375489184.  Working around...
--------------------------------------------------
Comment 1 Paweł Paprota 2008-05-07 12:59:23 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 ***
Comment 2 vesavan 2008-05-07 13:10:21 UTC 
Removing thumbs.db from the samba network folder seems to correct this problem.

-Vesa