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 496590 - crash in Open Folder: Right click > Properties...
crash in Open Folder: Right click > Properties...
Status: RESOLVED DUPLICATE of bug 355018
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-13 22:55 UTC by isilia
Modified: 2007-11-14 09:59 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description isilia 2007-11-13 22:55:28 UTC 
Version: 2.18.3

What were you doing when the application crashed?
Right click > Properties on a folder, then it crashed
I just left the folder that caused the crash


Distribution: Debian lenny/sid
Gnome Release: 2.18.3 2007-07-03 (Debian)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks-Edge
Icon Theme: GnomeCorsair2

Memory status: size: 75395072 vsize: 75395072 resident: 25616384 share: 15028224 rss: 25616384 rss_rlim: 4294967295
CPU usage: start_time: 1194994155 rtime: 389 utime: 372 stime: 17 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6db96b0 (LWP 11698)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 177543

Thread 1 (Thread 0xb6db96b0 (LWP 11698))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 872
  • #3 <signal handler called>
  • #4 strcmp
    from /lib/i686/cmov/libc.so.6
  • #5 changed_group_callback
    at fm-properties-window.c line 1646
  • #6 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
  • #7 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #8 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #9 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #10 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #11 gtk_combo_box_model_row_deleted
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkcombobox.c line 3119
  • #12 IA__g_cclosure_marshal_VOID__BOXED
    at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 566
  • #13 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #14 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #15 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #16 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #17 IA__gtk_tree_model_row_deleted
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtktreemodel.c line 1537
  • #18 IA__gtk_list_store_remove
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 969
  • #19 IA__gtk_list_store_clear
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c line 1167
  • #20 synch_groups_combo_box
    at fm-properties-window.c line 1794
  • #21 IA__g_cclosure_marshal_VOID__VOID
    at /tmp/buildd/glib2.0-2.14.1/gobject/gmarshal.c line 77
  • #22 IA__g_closure_invoke
    at /tmp/buildd/glib2.0-2.14.1/gobject/gclosure.c line 490
  • #23 signal_emit_unlocked_R
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2440
  • #24 IA__g_signal_emit_valist
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2199
  • #25 IA__g_signal_emit
    at /tmp/buildd/glib2.0-2.14.1/gobject/gsignal.c line 2243
  • #26 nautilus_file_emit_changed
    at nautilus-file.c line 5522
  • #27 nautilus_directory_emit_change_signals
    at nautilus-directory.c line 794
  • #28 nautilus_file_changed
    at nautilus-file.c line 5468
  • #29 deep_count_callback
    at nautilus-directory-async.c line 2430
  • #30 dispatch_job_callback
    at gnome-vfs-job.c line 237
  • #31 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 4132
  • #32 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2061
  • #33 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2694
  • #34 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.14.1/glib/gmain.c line 2898
  • #35 IA__gtk_main
    at /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkmain.c line 1146
  • #36 main
    at nautilus-main.c line 548
  • #0 __kernel_vsyscall 


----------- .xsession-errors (2360 sec old) ---------------------
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
fixme:wininet:InternetGetConnectedState always returning LAN connection.
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-14 09:59:49 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 355018 ***