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 513784 - crash in Home Folder: open propreties for pen ...
crash in Home Folder: open propreties for pen ...
Status: RESOLVED DUPLICATE of bug 355018
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-02-01 21:53 UTC by Marco Couto Ferreira
Modified: 2008-02-02 14:19 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Marco Couto Ferreira 2008-02-01 21:53:15 UTC 
What were you doing when the application crashed?
open propreties for pen drive (mp3 player) [icon for desktop]


Distribution: Debian lenny/sid
Gnome Release: 2.20.2 2007-11-29 (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: Clearlooks
Icon Theme: gnome

Memory status: size: 404832256 vsize: 404832256 resident: 33259520 share: 18423808 rss: 33259520 rss_rlim: 18446744073709551615
CPU usage: start_time: 1201902337 rtime: 1126 utime: 892 stime: 234 cutime:23 cstime: 2 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 0x2ae1b3cfc540 (LWP 3778)]
(no debugging symbols found)
0x00002ae1ad18134f in waitpid () from /lib/libpthread.so.0

+ Trace 187780

Thread 1 (Thread 0x2ae1b3cfc540 (LWP 3778))

  • #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 (10 sec old) ---------------------
** 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
** Message: drive = 0
** Message: volume = 0
JACK tmpdir identified as [/dev/shm]
JACK tmpdir identified as [/dev/shm]
--------------------------------------------------
Comment 1 Gianluca Borello 2008-02-02 14:19: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 355018 ***