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 524799 - crash in Computer: je telecharge avec mldon...
crash in Computer: je telecharge avec mldon...
Status: RESOLVED DUPLICATE of bug 480179
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-03-28 14:37 UTC by siaud.xavier
Modified: 2008-03-29 18:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description siaud.xavier 2008-03-28 14:37:49 UTC 
Version: 2.20.0

What were you doing when the application crashed?
je telecharge avec mldonkey, et je modifie des fichiers avec easytag, et j'ecoute la musique avec gmusicbrowser, et je range mes fichiers avec nautilus tout en meme temps, et c'est là que nautilus s'arrete brutalement.


Distribution: Debian lenny/sid
Gnome Release: 2.22.0 2008-03-14 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Sun Feb 10 20:20:49 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 97443840 vsize: 97443840 resident: 48021504 share: 16359424 rss: 48021504 rss_rlim: 4294967295
CPU usage: start_time: 1206714300 rtime: 2153 utime: 2028 stime: 125 cutime:141 cstime: 8 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6c18720 (LWP 5644)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 193533

Thread 1 (Thread 0xb6c18720 (LWP 5644))

  • #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 gconf_client_remove_dir
    from /usr/lib/libgconf-2.so.4
  • #7 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #8 ??
  • #9 ??
    from /usr/lib/nautilus/extensions-1.0/libnautilus-actions.so
  • #10 ??
  • #0 __kernel_vsyscall 


----------- .xsession-errors (614166 sec old) ---------------------
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Avertissement du gestionnaire de fenêtres : Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x2401c43 (Avertissem)
Avertissement du gestionnaire de fenêtres : meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--- Hash table keys for warning below:
--> file:///root/Desktop
(nautilus:4224): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above)
--- Hash table keys for warning below:
--> file:///root/Desktop
(nautilus:4224): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time (keys above)
Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0.  This shouldn't happen!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-03-29 18:24:14 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 480179 ***