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 494899 - crash in Open Folder: I tried to get the prope...
crash in Open Folder: I tried to get the prope...
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-08 09:14 UTC by csfulop
Modified: 2007-11-13 21:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description csfulop 2007-11-08 09:14:16 UTC 
Version: 2.18.3

What were you doing when the application crashed?
I tried to get the properties dialog of the root of my usb drive.	


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

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 75886592 vsize: 75886592 resident: 24764416 share: 15527936 rss: 24764416 rss_rlim: 4294967295
CPU usage: start_time: 1194513068 rtime: 243 utime: 223 stime: 20 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c8d6b0 (LWP 10215)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 176264

Thread 1 (Thread 0xb6c8d6b0 (LWP 10215))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/i686/cmov/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 ??
  • #4 ??
  • #5 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (4534 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 André Klapper 2007-11-13 12:03:07 UTC 
Thanks for taking the time to report this bug.
Unfortunately, the stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash.

Could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here. Thanks in advance!

[1] Please install debug packages for nautilus, glib2, gtk2, pango, gnome-vfs2, libgnome, and libgnomeui.

More details can be found here: http://live.gnome.org/GettingTraces
Comment 2 csfulop 2007-11-13 21:01:12 UTC 
Hi,

I have managed to repeat the crash. Here are the new logs. However I could not find dbg package for 'libgnome' in Debian. Please let me know if something is still missing from this trace.

Br,
Csaba

=============================================================

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

System: Linux 2.6.22-2-k7 #1 SMP Fri Aug 31 01:02:37 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 75812864 vsize: 75812864 resident: 24641536 share: 15425536 rss: 24641536 rss_rlim: 4294967295
CPU usage: start_time: 1194983489 rtime: 294 utime: 269 stime: 25 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 0xb6d076b0 (LWP 6542)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 177519

Thread 1 (Thread 0xb6d076b0 (LWP 6542))

  • #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 (7 sec old) ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 3 André Klapper 2007-11-13 21:53:53 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 ***