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 493708 - crash in Home Folder: Nautilus lock only whe...
crash in Home Folder: Nautilus lock only whe...
Status: RESOLVED DUPLICATE of bug 440988
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-11-05 12:27 UTC by hindenburgo
Modified: 2007-11-09 15:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description hindenburgo 2007-11-05 12:27:44 UTC
What were you doing when the application crashed?
	
Nautilus lock only when I trying to open the function ownership of the file


Distribution: Debian lenny/sid
Gnome Release: 2.20.0 2007-09-21 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-686 #1 SMP Mon Oct 22 22:11:56 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Debian-BR-CDD
Icon Theme: Debian-BR-CDD

Memory status: size: 75247616 vsize: 75247616 resident: 25255936 share: 15437824 rss: 25255936 rss_rlim: 4294967295
CPU usage: start_time: 1194263149 rtime: 1067 utime: 1015 stime: 52 cutime:0 cstime: 0 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/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb6e096b0 (LWP 3670)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread 0xb6e096b0 (LWP 3670))

  • #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 __kernel_vsyscall
  • #7 raise
    from /lib/i686/cmov/libc.so.6
  • #8 abort
    from /lib/i686/cmov/libc.so.6
  • #9 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #10 g_log
    from /usr/lib/libglib-2.0.so.0
  • #11 g_assert_warning
    from /usr/lib/libglib-2.0.so.0
  • #12 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 ??
  • #16 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 ??
  • #20 ??
  • #21 ??
  • #22 ??
  • #23 ??
  • #24 ??
  • #25 ??
  • #26 ??
  • #27 ??
  • #28 ??
  • #29 ??
  • #30 ??
  • #31 ??
  • #32 ??
  • #33 ??
  • #34 ??
  • #35 ??
  • #36 ??
  • #37 ??
  • #38 ??
  • #39 ??
  • #40 ??
  • #41 gtk_menu_reorder_child
    from /usr/lib/libgtk-x11-2.0.so.0
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
Aviso do gerenciador de janelas: A propriedade _NET_WM_NAME na janela 0x2e00025 continha UTF-8 inválido
Aviso do gerenciador de janelas: A propriedade _NET_WM_ICON_NAME na janela 0x2e00025 continha UTF-8 inválido
(gnome-panel:3669): Wnck-WARNING **: Property _NET_WM_ICON_NAME contained invalid UTF-8
Gtk-ERROR **: file /tmp/buildd/gtk+2.0-2.12.0/gtk/gtkliststore.c: line 1677 (gtk_list_store_compare_func): assertion failed: (VALID_ITER (&iter_b, list_store))
aborting...
warning: .dynamic section for "/usr/lib/libgtk-x11-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgdk-x11-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgdk_pixbuf-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Christoph Wolk 2007-11-09 15:04:00 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 results from  version incompatibilities. Updating some packages will likely fix it, see that bug for more information.

*** This bug has been marked as a duplicate of 440988 ***