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 526946 - crash in Computer:
crash in Computer:
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-08 13:43 UTC by huji
Modified: 2008-04-10 08:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description huji 2008-04-08 13:43:59 UTC
Version: 2.20.0

What were you doing when the application crashed?



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

System: Linux 2.6.24-1-686 #1 SMP Mon Feb 11 14:37:45 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: black-white

Memory status: size: 68661248 vsize: 68661248 resident: 20639744 share: 13905920 rss: 20639744 rss_rlim: 4294967295
CPU usage: start_time: 1207662165 rtime: 488 utime: 452 stime: 36 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6c48720 (LWP 4343)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6c48720 (LWP 4343))

  • #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 istr_hash
    at nautilus-directory-async.c line 170
  • #7 ??
    from /usr/lib/libglib-2.0.so.0
  • #8 ??
  • #0 __kernel_vsyscall


----------- .xsession-errors (11 sec old) ---------------------
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 4 (Paramètres non valides) in fm_report_error_loading_directory
** (nautilus:4343): WARNING **: Hit unhandled case 2 (Erreur générique) in fm_report_error_loading_directory
--------------------------------------------------
Comment 1 André Klapper 2008-04-10 08:36:09 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 ***