Bug 555868 – crash in File Browser: I was trying to view the...

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 555868 - crash in File Browser: I was trying to view the...


Summary:	crash in File Browser: I was trying to view the...


Status:	RESOLVED DUPLICATE of bug 434026

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-10-11 01:26 UTC by carlosalves90
Modified:	2008-10-14 17:53 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description carlosalves90 2008-10-11 01:26:47 UTC

Version: 2.20.0

What were you doing when the application crashed?
I was trying to view the properties of a video file (an ogg with theora video
and vorbis audio)



Distribution: Debian lenny/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Wed Oct 1 12:03:14 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 104230912 vsize: 104230912 resident: 41480192 share: 20307968 rss: 41480192 rss_rlim: 4294967295
CPU usage: start_time: 1223688092 rtime: 890 utime: 808 stime: 82 cutime:1 cstime: 6 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6ade710 (LWP 3134)]
0xb7f51424 in __kernel_vsyscall ()

+ Trace 208030

Thread 1 (Thread 0xb6ade710 (LWP 3134))

#0 __kernel_vsyscall
#1 waitpid
from /lib/i686/cmov/libpthread.so.0
#2 IA__g_spawn_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at /tmp/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
#4 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#5 ??
from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
#6 <signal handler called>
#7 nautilus_file_unref
at nautilus-file.c line 593
#8 IA__g_list_foreach
at /tmp/buildd/glib2.0-2.16.6/glib/glist.c line 789
#9 nautilus_file_list_unref
at nautilus-file.c line 5916
#10 nautilus_file_list_free
at nautilus-file.c line 5928
#11 remove_pending
at fm-properties-window.c line 4745
#12 is_directory_ready_callback
at fm-properties-window.c line 5085
#13 ready_callback_call
at nautilus-directory-async.c line 1260
#14 call_ready_callbacks_at_idle
at nautilus-directory-async.c line 1878
#15 g_idle_dispatch
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 4090
#16 IA__g_main_context_dispatch
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
#17 g_main_context_iterate
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
#18 IA__g_main_loop_run
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
#19 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
#20 main
at nautilus-main.c line 565
#0 __kernel_vsyscall



----------- .xsession-errors (11 sec old) ---------------------
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
** Message: GetValue variable 1 (1)
** Message: GetValue variable 2 (2)
(nautilus:3134): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
(nautilus:3134): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(nautilus:3134): GLib-GObject-CRITICAL **: g_signal_handlers_disconnect_matched: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-10-14 17:53:57 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 434026 ***