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 543015 - crash in Open Folder: browsing a smb share on ...
crash in Open Folder: browsing a smb share 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-07-15 02:13 UTC by yetr2quared
Modified: 2008-07-15 07:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description yetr2quared 2008-07-15 02:13:02 UTC 
Version: 2.20.0

What were you doing when the application crashed?
browsing a smb share on a remote windows machine


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

System: Linux 2.6.24-1-powerpc #1 Sat May 10 11:39:20 UTC 2008 ppc
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 82079744 vsize: 82079744 resident: 25731072 share: 18665472 rss: 25731072 rss_rlim: 4294967295
CPU usage: start_time: 1215730647 rtime: 1080 utime: 968 stime: 112 cutime:532 cstime: 53 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 0x4804bc00 (LWP 2916)]
(no debugging symbols found)
0x0ec51290 in waitpid () from /lib/libpthread.so.0

+ Trace 202843

Thread 1 (Thread 0x4804bc00 (LWP 2916))

  • #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 ??
  • #5 <signal handler called>
  • #6 ??
  • #7 ??
  • #8 ??
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #12 ??
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 ??
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #16 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
  • #18 ??
    from /lib/libc.so.6
  • #19 __libc_start_main
    from /lib/libc.so.6
  • #20 ??
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (323 sec old) ---------------------
  - Don't try to play a big DVD/DivX on a slow CPU! Try some of the lavdopts,
    e.g. -vfm ffmpeg -lavdopts lowres=1:fast:skiploopfilter=all.
- Broken file
  - Try various combinations of -nobps -ni -forceidx -mc 0.
- Slow media (NFS/SMB mounts, DVD, VCD etc)
  - Try -cache 8192.
- Are you using -cache to play a non-interleaved AVI file?
  - Try -nocache.
Read DOCS/HTML/en/video.html for tuning/speedup tips.
If none of this helps you, read DOCS/HTML/en/bugreports.html.
A:   7.9 V:   6.8 A-V:  1.182 ct: -0.005  54/ 54 23% 138%  0.9% 51 0            A:   8.0 V:   6.8 A-V:  1.194 ct: -0.004  55/ 55 22% 138%  0.9% 52 0            A:   8.0 V:   6.8 A-V:  1.208 ct: -0.0
Reason: Took too much time to process.
A:  32.3 V:  23.2 A-V:  9.059 ct: -0.009 547/547 12% 131%  0.8% 541 0           A:  32.3 V:  23.2 A-V:  9.073 ct: -0.008 548/548 12% 131%  0.8% 542 0           A:  32.4 V:  23.3 A-V:  9.086 ct: -0.0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-07-15 07:57:11 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 ***