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 558583 - crash in Home Folder: wollte eine Datei auf de...
crash in Home Folder: wollte eine Datei auf de...
Status: RESOLVED DUPLICATE of bug 434026
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-10-30 19:29 UTC by fahrradralf
Modified: 2008-11-01 12:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description fahrradralf 2008-10-30 19:29:19 UTC
What were you doing when the application crashed?
wollte eine Datei auf dem Wechseldatenträger zum Kopieren anklicken


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 Thu Oct 9 15:18:09 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: 103960576 vsize: 103960576 resident: 39923712 share: 21798912 rss: 39923712 rss_rlim: 4294967295
CPU usage: start_time: 1225394719 rtime: 623 utime: 557 stime: 66 cutime:35 cstime: 16 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb69ec710 (LWP 14063)]
[New Thread 0xb5d6ab90 (LWP 25657)]
0xb7fb3424 in __kernel_vsyscall ()

Thread 1 (Thread 0xb69ec710 (LWP 14063))

  • #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 IA__g_list_foreach
    at /tmp/buildd/glib2.0-2.16.6/glib/glist.c line 788
  • #8 nautilus_file_list_unref
    at nautilus-file.c line 5916
  • #9 nautilus_file_list_free
    at nautilus-file.c line 5928
  • #10 remove_pending
    at fm-properties-window.c line 4745
  • #11 is_directory_ready_callback
    at fm-properties-window.c line 5085
  • #12 ready_callback_call
    at nautilus-directory-async.c line 1260
  • #13 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1878
  • #14 g_idle_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 4090
  • #15 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #16 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #17 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #18 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #19 main
    at nautilus-main.c line 565
  • #0 __kernel_vsyscall


----------- .xsession-errors (6 sec old) ---------------------
(gnome-panel:14056): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -9 and height 24
WARNING: modinfo for module nvidia_new failed: modinfo: could not find module nvidia_new
WARNING: modinfo for module nvidia failed: modinfo: could not find module nvidia
WARNING: modinfo for module nvidia_legacy failed: modinfo: could not find module nvidia_legacy
WARNING: modinfo for module fglrx failed: modinfo: could not find module fglrx
ERROR: Only administrators can use this function.
gnome-video-thumbnailer couldn't process file: 'file:///media/CASIO-DSC/dcim/100casio/cimg3611.avi'
Reason: Took too much time to process.
(nautilus:14063): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-11-01 12:26:54 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 ***