Bug 474156 – crash in Open Folder: dddddddd

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 474156 - crash in Open Folder: dddddddd


Summary:	crash in Open Folder: dddddddd


Status:	RESOLVED DUPLICATE of bug 443020

Product:	nautilus
Classification:	Core
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Nautilus Maintainers
QA Contact:	Nautilus Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-09-06 08:36 UTC by dohuyn1234
Modified:	2007-09-06 12:25 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description dohuyn1234 2007-09-06 08:36:58 UTC

Version: 2.18.1

What were you doing when the application crashed?
dddddddd


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 76152832 vsize: 76152832 resident: 17428480 share: 12492800 rss: 17428480 rss_rlim: 4294967295
CPU usage: start_time: 1189066474 rtime: 181 utime: 159 stime: 22 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 -1209084192 (LWP 3318)]
(no debugging symbols found)
0x00dd7402 in __kernel_vsyscall ()

+ Trace 160822

Thread 1 (Thread -1209084192 (LWP 3318))

#0 __kernel_vsyscall
#1 waitpid
from /lib/libpthread.so.0
#2 ??
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 pthread_mutex_lock
from /lib/libpthread.so.0
#5 ??
from /usr/lib/libcairo.so.2
#6 ??
from /usr/lib/libcairo.so.2
#7 ??
from /usr/lib/libcairo.so.2
#8 cairo_scaled_font_text_extents
from /usr/lib/libcairo.so.2
#9 ??
from /usr/lib/libpangocairo-1.0.so.0
#10 ??
from /usr/lib/libpangocairo-1.0.so.0
#11 ??
from /usr/lib/libpangocairo-1.0.so.0
#12 pango_font_get_glyph_extents
from /usr/lib/libpango-1.0.so.0
#13 ??
from /usr/lib/libpango-1.0.so.0
#14 ??
from /usr/lib/libpango-1.0.so.0
#15 pango_shape
from /usr/lib/libpango-1.0.so.0
#16 ??
from /usr/lib/libpango-1.0.so.0
#17 ??
from /usr/lib/libpango-1.0.so.0
#18 ??
from /usr/lib/libpango-1.0.so.0
#19 pango_layout_get_iter
from /usr/lib/libpango-1.0.so.0
#20 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#21 gdk_draw_layout_with_colors
from /usr/lib/libgdk-x11-2.0.so.0
#22 gdk_draw_layout
from /usr/lib/libgdk-x11-2.0.so.0
#23 ??
#24 ??
#25 ??
from /usr/lib/libeel-2.so.2
#26 ??
from /usr/lib/libeel-2.so.2
#27 ??
#28 ??
from /usr/lib/libgtk-x11-2.0.so.0
#29 ??
from /lib/libgobject-2.0.so.0
#30 g_closure_invoke
from /lib/libgobject-2.0.so.0
#31 ??
from /lib/libgobject-2.0.so.0
#32 g_signal_emit_valist
from /lib/libgobject-2.0.so.0
#33 g_signal_emit
from /lib/libgobject-2.0.so.0
#34 ??
from /usr/lib/libgtk-x11-2.0.so.0
#35 gtk_main_do_event
from /usr/lib/libgtk-x11-2.0.so.0
#36 ??
from /usr/lib/libgdk-x11-2.0.so.0
#37 gdk_window_process_all_updates
from /usr/lib/libgdk-x11-2.0.so.0
#38 ??
from /usr/lib/libgtk-x11-2.0.so.0
#39 ??
from /lib/libglib-2.0.so.0
#40 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#41 ??
from /lib/libglib-2.0.so.0
#42 g_main_loop_run
from /lib/libglib-2.0.so.0
#43 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#44 main
#0 __kernel_vsyscall

Comment 1 palfrey 2007-09-06 12:25:34 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 443020 ***