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 530986 - crash in Home Folder: browsing a samba network...
crash in Home Folder: browsing a samba network...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-02 01:39 UTC by obcecado
Modified: 2008-05-02 23:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description obcecado 2008-05-02 01:39:51 UTC
What were you doing when the application crashed?
browsing a samba network share


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

System: Linux 2.6.24-1-686-bigmem #1 SMP Sat Apr 19 01:23:53 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Crux
Icon Theme: kids

Memory status: size: 145539072 vsize: 145539072 resident: 35225600 share: 16494592 rss: 35225600 rss_rlim: 4294967295
CPU usage: start_time: 1209685800 rtime: 12335 utime: 9224 stime: 3111 cutime:124 cstime: 24 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/nautilus'

(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b8f720 (LWP 3470)]
[New Thread 0xb11feb90 (LWP 6538)]
[New Thread 0xb19ffb90 (LWP 6534)]
[New Thread 0xb23fbb90 (LWP 6514)]
[New Thread 0xb3bfeb90 (LWP 6430)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b8f720 (LWP 3470))

  • #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

Comment 1 Cosimo Cecchi 2008-05-02 23:27:41 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 ***