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 537284 - crash in File Browser: i was intent access to f...
crash in File Browser: i was intent access to f...
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-08 17:43 UTC by jesus.a.cortes
Modified: 2008-06-08 17:56 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description jesus.a.cortes 2008-06-08 17:43:24 UTC 
Version: 2.20.0

What were you doing when the application crashed?
i was intent access to file server in my home LAN, and later i see this window to Herramienta de informe de errores 


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

System: Linux 2.6.18-5-amd64 #1 SMP Tue Dec 18 21:39:26 UTC 2007 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: 486813696 vsize: 486813696 resident: 44564480 share: 20705280 rss: 44564480 rss_rlim: 18446744073709551615
CPU usage: start_time: 1212943142 rtime: 1342 utime: 1208 stime: 134 cutime:0 cstime: 3 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 0x2b460d720c20 (LWP 2962)]
[New Thread 0x43005950 (LWP 3415)]
(no debugging symbols found)
0x00002b4606c16edf in waitpid () from /lib/libpthread.so.0

+ Trace 199880

Thread 1 (Thread 0x2b460d720c20 (LWP 2962))

  • #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 (9 sec old) ---------------------
closing
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
(.:3539): Gtk-CRITICAL **: gtk_container_remove: assertion `GTK_IS_TOOLBAR (container) || widget->parent == GTK_WIDGET (container)' failed
** (nautilus:2962): WARNING **: Hit unhandled case 2 (Error genérico) in fm_report_error_loading_directory
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-08 17:56:50 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 ***