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 492817 - crash in Open Folder: ping -l 65510 www.ris-me...
crash in Open Folder: ping -l 65510 www.ris-me...
Status: RESOLVED DUPLICATE of bug 436071
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-02 20:09 UTC by anonymous
Modified: 2007-11-03 01:38 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description anonymous 2007-11-02 20:09:56 UTC 
Version: 2.18.1

What were you doing when the application crashed?
ping -l 65510 www.ris-media.dk



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 83636224 vsize: 83636224 resident: 26931200 share: 14471168 rss: 26931200 rss_rlim: 4294967295
CPU usage: start_time: 1194050020 rtime: 717 utime: 676 stime: 41 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 -1208346912 (LWP 3549)]
(no debugging symbols found)
0x001ef402 in __kernel_vsyscall ()

+ Trace 174689

Thread 1 (Thread -1208346912 (LWP 3549))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 nautilus_file_compare_for_sort
  • #6 fm_icon_view_compare_files
  • #7 ??
  • #8 ??
  • #9 ??
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /lib/libglib-2.0.so.0
  • #11 ??
    from /lib/libglib-2.0.so.0
  • #12 ??
    from /lib/libglib-2.0.so.0
  • #13 ??
    from /lib/libglib-2.0.so.0
  • #14 ??
  • #15 ??
  • #16 ??
  • #17 g_cclosure_marshal_VOID__VOID
    from /lib/libgobject-2.0.so.0
  • #18 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #19 ??
    from /lib/libgobject-2.0.so.0
  • #20 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #21 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #22 nautilus_directory_emit_done_loading
  • #23 ??
  • #24 ??
  • #25 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
    from /lib/libglib-2.0.so.0
  • #32 ??
    from /lib/libpthread.so.0
  • #33 ??
  • #34 ??
    from /lib/libpthread.so.0
  • #35 ??
  • #36 ??
  • #37 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 g_slice_alloc
    from /lib/libglib-2.0.so.0
  • #0 __kernel_vsyscall 


----------- .xsession-errors (29 sec old) ---------------------
This can cause subtle evils like #48423
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3549): Gtk-CRITICAL **: gtk_label_set_label: assertion `str != NULL' failed
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
(nautilus:3549): GLib-CRITICAL **: g_filename_display_basename: assertion `filename != NULL' failed
--------------------------------------------------
Comment 1 Christoph Wolk 2007-11-03 01:38:27 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 436071 ***