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 582456 - crash in Home Folder: xdgfxdgfxdfg
crash in Home Folder: xdgfxdgfxdfg
Status: RESOLVED DUPLICATE of bug 449488
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-05-13 11:28 UTC by f
Modified: 2009-05-13 17:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description f 2009-05-13 11:28:56 UTC
What were you doing when the application crashed?
xdgfxdgfxdfg


Distribution: Debian squeeze/sid
Gnome Release: 2.22.3 2008-09-18 (Debian)
BugBuddy Version: 2.24.2

System: Linux 2.6.26-2-486 #1 Thu Mar 26 00:13:41 UTC 2009 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10402000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Nuvola
Icon Theme: Nuvola

Memory status: size: 58204160 vsize: 58204160 resident: 18345984 share: 12898304 rss: 18345984 rss_rlim: 18446744073709551615
CPU usage: start_time: 1242214273 rtime: 24 utime: 20 stime: 4 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

[Thread debugging using libthread_db enabled]
[New Thread 0xb6955760 (LWP 1176)]
0xb720f32e in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6955760 (LWP 1176))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 382
  • #2 IA__g_spawn_command_line_sync
    at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/glib/gspawn.c line 694
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #5 <signal handler called>
  • #6 raise
    from /lib/libc.so.6
  • #7 abort
    from /lib/libc.so.6
  • #8 Py_FatalError
    from /usr/lib/libpython2.5.so.1.0
  • #9 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #10 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #11 nautilus_module_load
    at nautilus-module.c line 99
  • #12 IA__g_type_module_use
    at /build/buildd-glib2.0_2.20.0-2-i386-rcJiVy/glib2.0-2.20.0/gobject/gtypemodule.c line 257
  • #13 nautilus_module_init
    at nautilus-module.c line 176
  • #14 nautilus_application_startup
    at nautilus-application.c line 410
  • #15 main
    at nautilus-main.c line 550
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0

----------- .xsession-errors ---------------------
Fatal Python error: could not import gnomevfs
Initializing nautilus-image-converter extension
Fatal Python error: could not import gnomevfs
Initializing nautilus-image-converter extension
Fatal Python error: could not import gnomevfs
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
Initializing nautilus-image-converter extension
Fatal Python error: could not import gnomevfs
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
Initializing nautilus-image-converter extension
Fatal Python error: could not import gnomevfs
warning: Lowest section in /usr/lib/libicudata.so.40 is .hash at 000000b4
--------------------------------------------------
Comment 1 palfrey 2009-05-13 17:05:27 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 has been marked as a duplicate of 449488 ***