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 531029 - crash in Computer: Je parcourai le réseau a...
crash in Computer: Je parcourai le réseau a...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
2.20.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-02 09:27 UTC by o.chaurin
Modified: 2008-05-02 23:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description o.chaurin 2008-05-02 09:27:54 UTC
Version: 2.20.0

What were you doing when the application crashed?
Je parcourai le réseau avec Nautilus


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Fri Apr 18 23:08:22 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: RPanther3
Icon Theme: OSX

Memory status: size: 403812352 vsize: 403812352 resident: 44892160 share: 18640896 rss: 44892160 rss_rlim: 18446744073709551615
CPU usage: start_time: 1209720371 rtime: 360 utime: 343 stime: 17 cutime:0 cstime: 0 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b57781c3b80 (LWP 3413)]
(no debugging symbols found)
0x00002b5771ce8edf in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b57781c3b80 (LWP 3413))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 g_spawn_sync
    from /usr/lib/libglib-2.0.so.0
  • #2 g_spawn_command_line_sync
    from /usr/lib/libglib-2.0.so.0
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 ??
  • #6 ??
    from /usr/lib/libglib-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #10 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #11 ??
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #13 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 ??
  • #17 ??
  • #18 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
** Message: another SSH agent is running at: /tmp/ssh-AjbEqo3326/agent.3326
** (gnome-settings-daemon:3393): WARNING **: Failed to open file '/etc/gnome/config/General.ad': Aucun fichier ou répertoire de ce type
** (gnome-session:3326): WARNING **: Host name lookup failure on localhost.
Avertissement du gestionnaire de fenêtres : «  » trouvé dans la base de données de configuration n'est pas une valeur correcte pour la combinaison de touches « toggle_shaded »
Avertissement du gestionnaire de fenêtres : La lecture du fichier de session enregistré /home/olivier/.metacity/sessions/default0.ms a échoué : Failed to open file '/home/olivier/.metacity/sessi
seahorse nautilus module initialized
Initializing gnome-mount extension
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
** (nautilus:3413): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « DATAS »), veuillez avertir la liste de diffusion de gnome-vfs.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-02 23:22:50 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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