Bug 564494 – crash in File Browser: Zamykanie kosza. Przedte...

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 564494 - crash in File Browser: Zamykanie kosza. Przedte...


Summary:	crash in File Browser: Zamykanie kosza. Przedte...


Status:	RESOLVED DUPLICATE of bug 437065

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-12-14 16:36 UTC by Ominous
Modified:	2008-12-14 18:48 UTC

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

Description Ominous 2008-12-14 16:36:26 UTC

Version: 2.20.0

What were you doing when the application crashed?
Zamykanie kosza. Przedtem czyszczenie kosza.
Closing trash. In advance cleaning of trash.



Distribution: Debian 5.0
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-1-686 #1 SMP Wed Nov 26 19:14:11 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 85524480 vsize: 85524480 resident: 23797760 share: 12709888 rss: 23797760 rss_rlim: 4294967295
CPU usage: start_time: 1229252475 rtime: 7845 utime: 7133 stime: 712 cutime:244 cstime: 40 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6ab4710 (LWP 3109)]
[New Thread 0xb4167b90 (LWP 6987)]
[New Thread 0xb6210b90 (LWP 6912)]
0xb7fb4424 in __kernel_vsyscall ()

+ Trace 210787

Thread 1 (Thread 0xb6ab4710 (LWP 3109))

#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_get_activation_uri
at nautilus-file.c line 2779
#8 get_activation_action
at fm-directory-view.c line 4639
#9 real_update_menus
at fm-directory-view.c line 7774
#10 fm_icon_view_update_menus
at fm-icon-view.c line 1580
#11 fm_directory_view_update_menus
at fm-directory-view.c line 9518
#12 update_menus_timeout_callback
at fm-directory-view.c line 2959
#13 g_timeout_dispatch
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 3446
#14 IA__g_main_context_dispatch
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
#15 g_main_context_iterate
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
#16 IA__g_main_loop_run
at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
#17 IA__gtk_main
at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
#18 main
at nautilus-main.c line 565
#0 __kernel_vsyscall



----------- .xsession-errors (60 sec old) ---------------------
Missing argument for -i
Uruchom "gnome-appearance-properties --help" aby zobaczyć listę wszystkich dostępnych opcji.
** (nautilus:3109): WARNING **: Error opening file '/usr/share/applications/gnome-theme-installer.desktop': Brak dostępu
** (nautilus:3109): WARNING **: Error opening file '/usr/share/applications/gnome-theme-installer.desktop': Brak dostępu
** (nautilus:3109): WARNING **: Error opening file '/usr/share/applications/gnome-theme-installer.desktop': Brak dostępu
** (nautilus:3109): WARNING **: Error opening file '/usr/share/applications/gnome-theme-installer.desktop': Brak dostępu

(shares-admin:6925): Gtk-WARNING **: Unknown property: GtkComboBox.items

** (nautilus:3109): WARNING **: destroyed file has call_when_ready pending
--------------------------------------------------

Comment 1 Cosimo Cecchi 2008-12-14 18:48:43 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 437065 ***