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 512362 - crash in File Browser: right-clic menu -> prope...
crash in File Browser: right-clic menu -> prope...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-27 13:57 UTC by roberto.civiero
Modified: 2008-01-27 14:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description roberto.civiero 2008-01-27 13:57:27 UTC
Version: 2.18.3

What were you doing when the application crashed?
right-clic menu -> properties on a folder in a mounted disk  /dev/hda2 on /media/hda2


Distribution: Debian lenny/sid
Gnome Release: 2.20.3 2008-01-12 (Debian)
BugBuddy Version: 2.20.1

System: Linux 2.6.22-3-amd64 #1 SMP Sun Nov 4 18:18:09 UTC 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy P
Icon Theme: OSX

Memory status: size: 332439552 vsize: 332439552 resident: 29167616 share: 16773120 rss: 29167616 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201440900 rtime: 217 utime: 190 stime: 27 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x2b4a1c075540 (LWP 16665)]
(no debugging symbols found)
0x00002b4a153ff34f in waitpid () from /lib/libpthread.so.0

Thread 1 (Thread 0x2b4a1c075540 (LWP 16665))

  • #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 strcmp
    from /lib/libc.so.6
  • #6 ??
  • #7 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #8 ??
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #11 ??
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 ??
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 gtk_list_store_remove
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 gtk_list_store_clear
    from /usr/lib/libgtk-x11-2.0.so.0
  • #18 ??
  • #19 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #20 ??
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #23 nautilus_file_emit_changed
  • #24 nautilus_directory_emit_change_signals
  • #25 nautilus_file_changed
  • #26 ??
  • #27 ??
    from /usr/lib/libgnomevfs-2.so.0
  • #28 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #29 ??
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #31 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #32 main
  • #0 waitpid
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
warning: .dynamic section for "/usr/lib/libcairo.so.2" is not at the expected address (wrong library or version mismatch?)
warning: .dynamic section for "/usr/lib/libgstreamer-0.10.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-01-27 14:05:31 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 355018 ***