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 534422 - crash in Home Folder: Used Bluetooth (Obex) wi...
crash in Home Folder: Used Bluetooth (Obex) wi...
Status: RESOLVED DUPLICATE of bug 522534
Product: nautilus
Classification: Core
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-05-23 00:29 UTC by vamp898
Modified: 2008-05-23 09:17 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description vamp898 2008-05-23 00:29:59 UTC 
What were you doing when the application crashed?
Used Bluetooth (Obex) with my Sony Ericsson K610i


Distribution: Debian lenny/sid
Gnome Release: 2.22.1 2008-04-08 (Debian)
BugBuddy Version: 2.22.0

System: Linux 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10400090
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: gnome

Memory status: size: 550547456 vsize: 550547456 resident: 53829632 share: 20602880 rss: 53829632 rss_rlim: 18446744073709551615
CPU usage: start_time: 1211491514 rtime: 1189 utime: 986 stime: 203 cutime:0 cstime: 4 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 0x2b53ff23b240 (LWP 3212)]
[New Thread 0x43005950 (LWP 8059)]
0x00002b53f8a31edf in waitpid () from /lib/libpthread.so.0

+ Trace 198420

Thread 1 (Thread 0x2b53ff23b240 (LWP 3212))

  • #0 waitpid
    from /lib/libpthread.so.0
  • #1 IA__g_spawn_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 374
  • #2 IA__g_spawn_command_line_sync
    at /tmp/buildd/glib2.0-2.16.3/glib/gspawn.c line 682
  • #3 ??
    from /usr/lib/gtk-2.0/modules/libgnomebreakpad.so
  • #4 <signal handler called>
  • #5 istr_hash
    at nautilus-directory-async.c line 170
  • #6 g_hash_table_insert_internal
    at /tmp/buildd/glib2.0-2.16.3/glib/ghash.c line 118
  • #7 dequeue_pending_idle_callback
    at nautilus-directory-async.c line 848
  • #8 directory_load_callback
    at nautilus-directory-async.c line 1035
  • #9 dispatch_job_callback
    at gnome-vfs-job.c line 237
  • #10 IA__g_main_context_dispatch
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2009
  • #11 g_main_context_iterate
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2642
  • #12 IA__g_main_loop_run
    at /tmp/buildd/glib2.0-2.16.3/glib/gmain.c line 2850
  • #13 IA__gtk_main
    at /build/buildd/gtk+2.0-2.12.9/gtk/gtkmain.c line 1163
  • #14 main
    at nautilus-main.c line 556
  • #15 __libc_start_main
    from /lib/libc.so.6
  • #16 _start
  • #0 waitpid
    from /lib/libpthread.so.0 


----------- .xsession-errors (557 sec old) ---------------------
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_set_text: assertion `layout != NULL' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_set_text: assertion `layout != NULL' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_set_text: assertion `layout != NULL' failed
(realplay.bin:9438): Pango-CRITICAL **: pango_layout_get_pixel_extents: assertion `PANGO_IS_LAYOUT (layout)' failed
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Cosimo Cecchi 2008-05-23 09:17:09 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 522534 ***