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 511974 - crash in File Browser: Ingresando a mi carpeta ...
crash in File Browser: Ingresando a mi carpeta ...
Status: RESOLVED DUPLICATE of bug 459221
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-25 06:02 UTC by e_correopablo
Modified: 2008-01-25 09:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description e_correopablo 2008-01-25 06:02:17 UTC
What were you doing when the application crashed?
Ingresando a mi carpeta personal.


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.18-5-486 #1 Mon Dec 24 16:04:42 UTC 2007 i586
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 79302656 vsize: 79302656 resident: 21860352 share: 13971456 rss: 21860352 rss_rlim: 4294967295
CPU usage: start_time: 1201240802 rtime: 2024 utime: 1887 stime: 137 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 0xb6db76b0 (LWP 3614)]
(no debugging symbols found)
0xb7633321 in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6db76b0 (LWP 3614))

  • #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 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #8 g_log
    from /usr/lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #10 ??
  • #11 ??
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
xrdb:  "*Text.foreground" on line 238 overrides entry on line 192
Advertencia del gestor de ventanas: last_user_time (3075642416) is greater than comparison timestamp (2944373164).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x1e00003 (Preferenci) appears to be one of the offending windows with a timestamp of 3075642416.  Working around...
** Message: Could not connect to power manager: Could not get owner of name 'org.freedesktop.PowerManagement': no such name
Advertencia del gestor de ventanas: last_user_time (3076658224) is greater than comparison timestamp (2944604306).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2600003 (Preferenci) appears to be one of the offending windows with a timestamp of 3076658224.  Working around...
Advertencia del gestor de ventanas: last_user_time (3076555824) is greater than comparison timestamp (2944792122).  This most likely represents a buggy client sending inaccurate timestamps in messages
Advertencia del gestor de ventanas: 0x2600003 (Preferenci) appears to be one of the offending windows with a timestamp of 3076555824.  Working around...
** ERROR **: file nautilus-navigation-window.c: line 723 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
** ERROR **: file nautilus-navigation-window.c: line 723 (activate_nth_short_list_item): assertion failed: (index < g_list_length (window->details->short_list_viewers))
aborting...
Failed to read a valid object file image from memory.
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-25 09:11:04 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 459221 ***