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 537726 - crash in File Browser: Nautilus crashed while I...
crash in File Browser: Nautilus crashed while 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-06-11 05:54 UTC by Marek Skrobacki
Modified: 2008-06-11 11:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Marek Skrobacki 2008-06-11 05:54:58 UTC 
Version: 2.20.0

What were you doing when the application crashed?
Nautilus crashed while I was browsing samba resources.


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 Sat Apr 19 00:37:55 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Foresight
Icon Theme: Vista-Inspirate_1.0

Memory status: size: 95690752 vsize: 95690752 resident: 27496448 share: 16789504 rss: 27496448 rss_rlim: 4294967295
CPU usage: start_time: 1213161889 rtime: 358 utime: 322 stime: 36 cutime:0 cstime: 1 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 0xb6bd5720 (LWP 3287)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 200096

Thread 1 (Thread 0xb6bd5720 (LWP 3287))

  • #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 ---------------------
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
err:win:DefWindowProcW called for other process window 0x10020
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-11 11:14:03 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 ***