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 539571 - 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-06-22 10:12 UTC by gaillard.thierry
Modified: 2008-06-22 12:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description gaillard.thierry 2008-06-22 10:12:55 UTC
Version: 2.20.0

What were you doing when the application crashed?



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

System: Linux 2.6.24-1-686-bigmem #1 SMP Thu May 8 02:55:42 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: tish
Icon Theme: black-white_2-Neon

Memory status: size: 62332928 vsize: 62332928 resident: 27181056 share: 15294464 rss: 27181056 rss_rlim: 4294967295
CPU usage: start_time: 1214129519 rtime: 180 utime: 168 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6b77940 (LWP 6736)]
[New Thread 0xb62b9b90 (LWP 6757)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6b77940 (LWP 6736))

  • #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 ---------------------
Initializing nautilus-open-terminal extension
seahorse nautilus module initialized
Initializing gnome-mount extension
/home/kik/.themes/tish/gtk-2.0/gtkrc:59: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:60: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:61: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:62: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:59: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:60: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:61: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:62: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:59: Clearlooks configuration option "sunkenmenu" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:60: Clearlooks configuration option "menuitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:61: Clearlooks configuration option "listviewitemstyle" is not supported and will be ignored.
/home/kik/.themes/tish/gtk-2.0/gtkrc:62: Clearlooks configuration option "progressbarstyle" is not supported and will be ignored.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-06-22 12:14:35 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 ***