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 538347 - crash in Computer: explor network
crash in Computer: explor network
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-06-14 18:06 UTC by plessis.adrien
Modified: 2008-06-15 10:12 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description plessis.adrien 2008-06-14 18:06:17 UTC 
Version: 2.20.0

What were you doing when the application crashed?
explor network


Distribution: Debian lenny/sid
Gnome Release: 2.22.2 2008-05-29 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Gorilla

Memory status: size: 557998080 vsize: 557998080 resident: 58376192 share: 20320256 rss: 58376192 rss_rlim: 18446744073709551615
CPU usage: start_time: 1213458944 rtime: 14291 utime: 4472 stime: 9819 cutime:10517 cstime: 2016 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 0x2ab7b8e61240 (LWP 3482)]
(no debugging symbols found)
0x00002ab7b2357edf in waitpid () from /lib/libpthread.so.0

+ Trace 200438

Thread 1 (Thread 0x2ab7b8e61240 (LWP 3482))

  • #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 (1081 sec old) ---------------------
[00000287] main playlist: stopping playback
Avertissement du gestionnaire de fenêtres : Received a NET_CURRENT_DESKTOP message from a broken (outdated) client who sent a 0 timestamp

(gnome-terminal:8430): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.

(gnome-terminal:8430): atk-bridge-WARNING **: AT_SPI_REGISTRY was not started at session startup.

(gnome-terminal:8430): atk-bridge-WARNING **: IOR not set.

(gnome-terminal:8430): atk-bridge-WARNING **: Could not locate registry
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-15 10:12:11 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 ***