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 530796 - crash in Open Folder: navigating through samba...
crash in Open Folder: navigating through samba...
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-30 20:40 UTC by acrueltasteofwinter
Modified: 2008-05-01 12:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description acrueltasteofwinter 2008-04-30 20:40:28 UTC 
Version: 2.20.0

What were you doing when the application crashed?
navigating through samba shares with nautilus


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: 455344128 vsize: 455344128 resident: 36503552 share: 18575360 rss: 36503552 rss_rlim: 18446744073709551615
CPU usage: start_time: 1209587504 rtime: 166 utime: 150 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2af838521b80 (LWP 23951)]
[New Thread 0x41802950 (LWP 24047)]
(no debugging symbols found)
0x00002af832046edf in waitpid () from /lib/libpthread.so.0

+ Trace 196551

Thread 1 (Thread 0x2af838521b80 (LWP 23951))

  • #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 (173984 sec old) ---------------------
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2b440,0x1d2b43c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2b440,0x1d2b43c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2b440,0x1d2b43c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2b440,0x1d2b43c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2b440,0x1d2b43c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2ba4c,0x1d2ba48): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bfe4,0x1d2bfe0): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bf70,0x1d2bf6c): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bca4,0x1d2bca0): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2c2b0,0x1d2c2ac): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bca4,0x1d2bca0): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bca4,0x1d2bca0): stub
fixme:process:GetProcessWorkingSetSize (0xffffffff,0x1d2bc7c,0x1d2bc78): stub
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-01 12:47:36 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 ***