Bug 497979 – crash in File Browser: opening properties menu ...

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 497979 - (schin) crash in File Browser: opening properties menu ...

(schin)
Summary:	crash in File Browser: opening properties menu ...


Status:	RESOLVED DUPLICATE of bug 355018

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-11-18 19:46 UTC by schinoisrising
Modified:	2007-12-23 15:31 UTC

See Also:
GNOME target:	---
GNOME version:	2.19/2.20

Description schinoisrising 2007-11-18 19:46:57 UTC

Version: 2.18.3

What were you doing when the application crashed?
opening properties menu of a device


Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.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: Serenity
Icon Theme: OpenWorld

Memory status: size: 79556608 vsize: 79556608 resident: 28225536 share: 16744448 rss: 28225536 rss_rlim: 4294967295
CPU usage: start_time: 1195418228 rtime: 525 utime: 489 stime: 36 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 0xb6ceb8c0 (LWP 6964)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 178566

Thread 1 (Thread 0xb6ceb8c0 (LWP 6964))

#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 ---------------------
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:510: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:517: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:522: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:529: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:534: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:541: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:546: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:553: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:558: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:565: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:570: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:577: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:582: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:589: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:594: Background image options specified without filename
--------------------------------------------------

Comment 1 André Klapper 2007-11-19 02:16:08 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 schinoisrising 2007-11-19 19:57:47 UTC

Distribution: Debian lenny/sid
Gnome Release: 2.20.1 2007-10-26 (Debian)
BugBuddy Version: 2.20.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: Serenity
Icon Theme: OpenWorld

Memory status: size: 76107776 vsize: 76107776 resident: 24576000 share: 16285696 rss: 24576000 rss_rlim: 4294967295
CPU usage: start_time: 1195505278 rtime: 129 utime: 117 stime: 12 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 0xb6d618c0 (LWP 5061)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 178786

Thread 1 (Thread 0xb6d618c0 (LWP 5061))

#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 emit_change_signals_for_all_files
at nautilus-directory.c line 270
#29 corba_metafile_ready
at nautilus-directory-metafile-monitor.c line 110
#30 ORBit_c_stub_invoke
from /usr/lib/libORBit-2.so.0
#31 Nautilus_MetafileMonitor_metafile_ready
at nautilus-shell-interface-stubs.c line 17
#32 metafile_read_mark_done
at nautilus-metafile.c line 849
#33 metafile_read_done
at nautilus-metafile.c line 1867
#34 ??
from /usr/lib/libeel-2-2.18.so
#35 ??
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:510: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:517: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:522: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:529: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:534: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:541: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:546: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:553: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:558: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:565: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:570: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:577: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:582: Background image options specified without filename
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:589: Impossibile trovare il file di immagine in pixmap_path: "spin.png"
/home/francesco/.themes/Serenity/gtk-2.0/gtkrc:594: Background image options specified without filename
--------------------------------------------------

Comment 3 André Klapper 2007-12-21 03:22:28 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 ***

Comment 4 schinoisrising 2007-12-23 15:31:09 UTC

Thanks for taking the time to fix this bug. bye