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 510875 - crash in Home Folder:
crash in Home Folder:
Status: RESOLVED DUPLICATE of bug 518824
Product: nautilus-python
Classification: Other
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Johan (not receiving bugmail) Dahlin
Johan (not receiving bugmail) Dahlin
: 533560 533561 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-01-20 19:26 UTC by kuller2
Modified: 2008-06-09 22:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description kuller2 2008-01-20 19:26:06 UTC
What were you doing when the application crashed?



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

System: Linux 2.6.22-3-k7 #1 SMP Mon Nov 12 09:12:50 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: crystalproject

Memory status: size: 25550848 vsize: 25550848 resident: 10444800 share: 8237056 rss: 10444800 rss_rlim: 4294967295
CPU usage: start_time: 1200857318 rtime: 8 utime: 7 stime: 1 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb6d306b0 (LWP 4012)]
0xb764a2fe in __waitpid_nocancel () from /lib/libpthread.so.0

Thread 1 (Thread 0xb6d306b0 (LWP 4012))

  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 369
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.14.3/glib/gspawn.c line 677
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 PyModule_GetDict
    at ../Objects/moduleobject.c line 47
  • #6 nautilus_python_init_python
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #7 nautilus_module_initialize
    from /usr/lib/nautilus/extensions-1.0/libnautilus-python.so
  • #8 nautilus_module_load
    at nautilus-module.c line 98
  • #9 IA__g_type_module_use
    at /tmp/buildd/glib2.0-2.14.3/gobject/gtypemodule.c line 190
  • #10 nautilus_module_init
    at nautilus-module.c line 172
  • #11 nautilus_application_startup
    at nautilus-application.c line 404
  • #12 main
    at nautilus-main.c line 533
  • #0 __waitpid_nocancel
    from /lib/libpthread.so.0


----------- .xsession-errors ---------------------
(bug-buddy:3961): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
seahorse nautilus module initialized
(nautilus:4002): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
(bug-buddy:4004): Gtk-WARNING **: Theme directory 1256x256/apps of theme crystalproject has no size field
(bug-buddy:4004): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion `g_utf8_validate (text, len, NULL)' failed
seahorse nautilus module initialized
(nautilus:4012): Nautilus-Python-WARNING **: g_module_open libpython failed: libpython2.4.so: Kann die Shared-Object-Datei nicht \xf6ffnen: Datei oder Verzeichnis nicht gefunden
(bug-buddy:4015): Gtk-WARNING **: Theme directory 1256x256/apps of theme crystalproject has no size field
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-17 13:41:12 UTC
*** Bug 533561 has been marked as a duplicate of this bug. ***
Comment 2 Cosimo Cecchi 2008-05-17 13:41:18 UTC
*** Bug 533560 has been marked as a duplicate of this bug. ***
Comment 3 Germán Poo-Caamaño 2008-06-09 22:17:47 UTC

It has the same pattern as
https://bugs.launchpad.net/ubuntu/+source/nautilus-python/+bug/195322

which was also reported and fixed in bug 518824.

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