Bug 507623 – crash in Computer: Clique droit sur un fich...

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 507623 - crash in Computer: Clique droit sur un fich...


Summary:	crash in Computer: Clique droit sur un fich...


Status:	RESOLVED DUPLICATE of bug 440988

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:	2008-01-06 07:56 UTC by leangeder
Modified:	2008-01-06 16:40 UTC

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

Description leangeder 2008-01-06 07:56:03 UTC

Version: 2.18.3

What were you doing when the application crashed?
Clique droit sur un fichier, puis selection affichage des propriétées du fichier


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (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: MidnightBlackPlastic2
Icon Theme: black-white

Memory status: size: 80797696 vsize: 80797696 resident: 27119616 share: 15126528 rss: 27119616 rss_rlim: 4294967295
CPU usage: start_time: 1199606029 rtime: 85 utime: 74 stime: 11 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 0xb6de56b0 (LWP 9585)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 184250

Thread 1 (Thread 0xb6de56b0 (LWP 9585))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 g_spawn_sync
from /usr/lib/libglib-2.0.so.0
#3 g_spawn_command_line_sync
from /usr/lib/libglib-2.0.so.0
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 <signal handler called>
#6 __kernel_vsyscall
#7 raise
from /lib/i686/cmov/libc.so.6
#8 abort
from /lib/i686/cmov/libc.so.6
#9 g_logv
from /usr/lib/libglib-2.0.so.0
#10 g_log
from /usr/lib/libglib-2.0.so.0
#11 g_assert_warning
from /usr/lib/libglib-2.0.so.0
#12 ??
from /usr/lib/libgtk-x11-2.0.so.0
#13 ??
from /usr/lib/libgtk-x11-2.0.so.0
#14 ??
from /usr/lib/libgtk-x11-2.0.so.0
#15 ??
#16 ??
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
from /usr/lib/libgtk-x11-2.0.so.0
#18 ??
from /usr/lib/libgtk-x11-2.0.so.0
#19 ??
#20 ??
#21 ??
#22 ??
#23 ??
#24 ??
#25 ??
#26 ??
#27 ??
#28 ??
#29 ??
#30 ??
#31 ??
#32 node_find_closest
at gsequence.c line 1136
#0 __kernel_vsyscall



----------- .xsession-errors ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
/usr/lib/python2.4/site-packages/GMenuSimpleEditor/maindialog.py:34: GtkWarning: Impossible de trouver le moteur de thème dans module_path : « ubuntulooks »
  self.xml = gtk.glade.XML (glade_file, "menu_editor_dialog", PACKAGE)
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.1/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
(bug-buddy:9734): Gtk-WARNING **: Impossible de trouver le moteur de thème dans module_path : « ubuntulooks »
--------------------------------------------------

Comment 1 André Klapper 2008-01-06 16:40:11 UTC

This has been fixed some time ago, please install any nautilus and glib updates provided by Debian!

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