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 494633 - crash in Open Folder: I right-clicked an execu...
crash in Open Folder: I right-clicked an execu...
Status: RESOLVED DUPLICATE of bug 440988
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-07 15:37 UTC by Matt McCutchen
Modified: 2007-11-08 01:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Matt McCutchen 2007-11-07 15:37:23 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I right-clicked an executable in a Nautilus folder window and clicked Properties.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Mist-Matt
Icon Theme: Clearlooks

Memory status: size: 168304640 vsize: 168304640 resident: 29163520 share: 23175168 rss: 29163520 rss_rlim: 4294967295
CPU usage: start_time: 1194312830 rtime: 1777 utime: 1563 stime: 214 cutime:50 cstime: 15 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208305952 (LWP 26112)]
0x00110402 in __kernel_vsyscall ()

+ Trace 176073

Thread 1 (Thread -1208305952 (LWP 26112))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #11 node_find_closest
    at gsequence.c line 1136
  • #12 node_insert_sorted
    at gsequence.c line 1301
  • #13 g_sequence_sort_changed_iter
    at gsequence.c line 566
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 gtk_list_store_set_valist
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 gtk_list_store_set
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 attach_selinux_data_popup_field
    at fm-properties-window.c line 2176
  • #18 append_title_selinux_edit_pair
    at fm-properties-window.c line 2329
  • #19 create_permissions_page
    at fm-properties-window.c line 5116
  • #20 is_directory_ready_callback
    at fm-properties-window.c line 5475
  • #21 ready_callback_call
    at nautilus-directory-async.c line 1265
  • #22 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1883
  • #23 ??
    from /lib/libglib-2.0.so.0
  • #24 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #25 ??
    from /lib/libglib-2.0.so.0
  • #26 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #27 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #28 main
    at nautilus-main.c line 548
  • #0 __kernel_vsyscall 


----------- .xsession-errors (641651 sec old) ---------------------
Find Items 0
get hashproduct pop://hashproduct@pop.gmail.com/
Find Items 0
get hashproduct pop://hashproduct@pop.gmail.com/
Find Items 0
get hashproduct pop://hashproduct@pop.gmail.com/
Find Items 0
get hashproduct pop://hashproduct@pop.gmail.com/
Find Items 0
get vzeu2dsg pop://vzeu2dsg@incoming.verizon.net/
Find Items 0
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4000003 (Evince Doc)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-08 01:41:21 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


*** This bug has been marked as a duplicate of 440988 ***