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 526136 - crash in Computer: I was just going on the ...
crash in Computer: I was just going on the ...
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-04-04 12:17 UTC by philippe
Modified: 2008-04-04 12:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description philippe 2008-04-04 12:17:36 UTC
Version: 2.20.0

What were you doing when the application crashed?
I was just going on the Intranet which is under Windows


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

System: Linux 2.6.24-1-amd64 #1 SMP Mon Feb 11 13:47:43 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: glass-icons

Memory status: size: 353492992 vsize: 353492992 resident: 33705984 share: 17870848 rss: 33705984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1207310454 rtime: 413 utime: 393 stime: 20 cutime:0 cstime: 1 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 0x2b0f22135b80 (LWP 3616)]
(no debugging symbols found)
0x00002b0f1bc4334f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b0f22135b80 (LWP 3616))

  • #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 (6 sec old) ---------------------

** (gnome-cups-add:3972): WARNING **: IPP request failed with status 1028

(gnome-terminal:4143): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Avertissement du gestionnaire de fenêtres : last_user_time (1659847328) is greater than comparison timestamp (425337638).  This most likely represents a buggy client sending inaccurate timestamps in
Avertissement du gestionnaire de fenêtres : 0x300001e (Terminal) appears to be one of the offending windows with a timestamp of 1659847328.  Working around...
(nautilus:3616): Pango-WARNING **: failed to find shape engine, expect ugly output. engine-type='PangoRenderFc', script='common'
** (nautilus:3616): WARNING **: Hit unhandled case 38 (Service non disponible) in fm_report_error_loading_directory
** (nautilus:3616): WARNING **: Aucune description trouvée pour le type MIME « x-directory/smb-share » (le fichier est « ECHANGE »), veuillez avertir la liste de diffusion de gnome-vfs.
connection_message_func(): Callback
CALLBACK: fill-authentication!!!
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-04-04 12:21:02 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 522534 ***