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 559096 - crash in Home Folder: used konquerer, ctrl-f t...
crash in Home Folder: used konquerer, ctrl-f t...
Status: RESOLVED DUPLICATE of bug 554550
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-11-03 12:49 UTC by c.hapke
Modified: 2008-11-03 20:07 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description c.hapke 2008-11-03 12:49:40 UTC 
What were you doing when the application crashed?
used konquerer, ctrl-f to find files


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

System: Linux 2.6.26-1-amd64 #1 SMP Thu Oct 9 14:16:53 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 656363520 vsize: 656363520 resident: 140959744 share: 20664320 rss: 140959744 rss_rlim: 18446744073709551615
CPU usage: start_time: 1225701568 rtime: 5187 utime: 4287 stime: 900 cutime:622 cstime: 296 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0x7f640f894780 (LWP 4249)]
0x00007f640a88e5ef in waitpid () from /lib/libpthread.so.0

+ Trace 209157

Thread 1 (Thread 0x7f640f894780 (LWP 4249))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd/glib2.0-2.16.6/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 IA__g_type_check_instance
    at /build/buildd/glib2.0-2.16.6/gobject/gtype.c line 3236
  • #7 IA__g_signal_handlers_disconnect_matched
    at /build/buildd/glib2.0-2.16.6/gobject/gsignal.c line 1928
  • #8 remove_pending
    at fm-properties-window.c line 5058
  • #9 is_directory_ready_callback
    at fm-properties-window.c line 5085
  • #10 call_ready_callbacks_at_idle
    at nautilus-directory-async.c line 1878
  • #11 IA__g_main_context_dispatch
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2012
  • #12 g_main_context_iterate
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2645
  • #13 IA__g_main_loop_run
    at /build/buildd/glib2.0-2.16.6/glib/gmain.c line 2853
  • #14 IA__gtk_main
    at /scratch/build-area/gtk+2.0-2.12.11/gtk/gtkmain.c line 1163
  • #15 main
    at nautilus-main.c line 565
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (14 sec old) ---------------------
closing
closing
closing
closing
closing
closing
gnome-video-thumbnailer couldn't process file: 'file:///media/disk/OTV-AUFNAHMEN/Key-Files/The_Da_Vinci_Code_Sakrileg_Top_Tipp__08.10.12_20-15_pro7_175_TVOON_DE.mpg.avi'
Reason: Took too much time to process.
gnome-video-thumbnailer couldn't process file: 'file:///media/disk/OTV-AUFNAHMEN/Key-Files/The_Da_Vinci_Code_Sakrileg_Top_Tipp__08.10.12_20-15_pro7_175_TVOON_DE.mpg.avi'
Reason: Took too much time to process.
gnome-video-thumbnailer couldn't process file: 'file:///media/disk/OTV-AUFNAHMEN/dec/The_Da_Vinci_Code_Sakrileg_Top_Tipp__08.10.12_20-15_pro7_175_TVOON_DE.mpg.avi'
Reason: Took too much time to process.
Fenstermanager-Warnung:Ungültiges WM_TRANSIENT_FOR-Fenster 0x65 festgelegt für 0x1408d1c ().
(nautilus:4249): Eel-CRITICAL **: eel_timed_wait_stop: assertion `wait != NULL' failed
--------------------------------------------------
Comment 1 Susana 2008-11-03 20:07:17 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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