Bug 431674 – crash in Open Folder:

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


Summary:	crash in Open Folder:


Status:	RESOLVED DUPLICATE of bug 357939

Product:	nautilus
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-04-20 13:02 UTC by fois5
Modified:	2007-04-27 14:43 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description fois5 2007-04-20 13:02:25 UTC

What were you doing when the application crashed?



Distribution: openSUSE 10.2 (X86-64)
Gnome Release: 2.16.1 2006-11-28 (SUSE)
BugBuddy Version: 2.16.0

Memory status: size: 415989760 vsize: 415989760 resident: 30318592 share: 22372352 rss: 52690944 rss_rlim: 893726720
CPU usage: start_time: 1177073917 rtime: 1050 utime: 830 stime: 220 cutime:3 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/opt/gnome/bin/nautilus'

(no debugging symbols found)
Using host libthread_db library "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47565609071232 (LWP 4190)]
[New Thread 1115838784 (LWP 4210)]
0x00002b42ba7051f6 in poll () from /lib64/libc.so.6

+ Trace 129270

Thread 2 (Thread 1115838784 (LWP 4210))

#0 waitpid
from /lib64/libpthread.so.0
#1 gnome_gtk_module_info_get
from /opt/gnome/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib64/libc.so.6
#4 abort
from /lib64/libc.so.6
#5 __assert_fail
from /lib64/libc.so.6
#6 cairo_ft_scaled_font_unlock_face
from /usr/lib64/libcairo.so.2
#7 cairo_ft_scaled_font_lock_face
from /usr/lib64/libcairo.so.2
#8 script_engine_init
from /opt/gnome/lib64/pango/1.5.0/modules/pango-basic-fc.so
#9 pango_shape
from /opt/gnome/lib64/libpango-1.0.so.0
#10 pango_layout_set_width
from /opt/gnome/lib64/libpango-1.0.so.0
#11 pango_layout_iter_get_char_extents
from /opt/gnome/lib64/libpango-1.0.so.0
#12 pango_layout_iter_get_char_extents
from /opt/gnome/lib64/libpango-1.0.so.0
#13 pango_layout_iter_get_char_extents
from /opt/gnome/lib64/libpango-1.0.so.0
#14 pango_layout_get_pixel_extents
from /opt/gnome/lib64/libpango-1.0.so.0
#15 rsvg_error_get_type
from /opt/gnome/lib64/librsvg-2.so.2
#16 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#17 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#18 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#19 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#20 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#21 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#22 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#23 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#24 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#25 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#26 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#27 rsvg_handle_new_from_data
from /opt/gnome/lib64/librsvg-2.so.2
#28 rsvg_handle_render_cairo_sub
from /opt/gnome/lib64/librsvg-2.so.2
#29 rsvg_handle_get_pixbuf_sub
from /opt/gnome/lib64/librsvg-2.so.2
#30 fill_info
from /opt/gnome/lib64/gtk-2.0/2.10.0/loaders/svg_loader.so
#31 gdk_pixbuf_loader_close
from /opt/gnome/lib64/libgdk_pixbuf-2.0.so.0
#32 gnome_gdk_pixbuf_new_from_uri_at_scale
from /opt/gnome/lib64/libgnomeui-2.so.0
#33 gnome_thumbnail_factory_generate_thumbnail
from /opt/gnome/lib64/libgnomeui-2.so.0
#34 nautilus_marshal_BOOLEAN__POINTER
#35 start_thread
from /lib64/libpthread.so.0
#36 clone
from /lib64/libc.so.6
#37 ??

Comment 1 palfrey 2007-04-27 14:43:08 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 357939 ***