Bug 425605 – crash in File Browser:

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 425605 - crash in File Browser:


Summary:	crash in File Browser:


Status:	RESOLVED DUPLICATE of bug 425604

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-02 20:15 UTC by granchio74
Modified:	2007-04-09 22:35 UTC

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

Description granchio74 2007-04-02 20:15:51 UTC

Version: 2.18.0.1

What were you doing when the application crashed?



Distribution: Unknown
Gnome Release: 2.18.0 2007-03-19 (Archlinux)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-ARCH #1 SMP PREEMPT Sat Mar 24 10:51:35 CET 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Glossy
Icon Theme: Tango

Memory status: size: 91574272 vsize: 91574272 resident: 37089280 share: 17285120 rss: 37089280 rss_rlim: 4294967295
CPU usage: start_time: 1175537376 rtime: 1719 utime: 1591 stime: 128 cutime:70 cstime: 12 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 "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1227290944 (LWP 5394)]
[New Thread -1265947760 (LWP 5879)]
(no debugging symbols found)
0xb7f32410 in __kernel_vsyscall ()

+ Trace 124422

Thread 2 (Thread -1265947760 (LWP 5879))

#0 __kernel_vsyscall
#1 ??
from /lib/libpthread.so.0
#2 libgnomeui_segv_handle
from /opt/gnome/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 fbFetchTransformed
from /usr/lib/libcairo.so.2
#5 pixman_compositeGeneral
from /usr/lib/libcairo.so.2
#6 _cairo_pixman_composite
from /usr/lib/libcairo.so.2
#7 _cairo_image_surface_composite_trapezoids
from /usr/lib/libcairo.so.2
#8 _cairo_surface_composite_trapezoids
from /usr/lib/libcairo.so.2
#9 _composite_traps_draw_func
from /usr/lib/libcairo.so.2
#10 _clip_and_composite
from /usr/lib/libcairo.so.2
#11 _clip_and_composite_trapezoids
from /usr/lib/libcairo.so.2
#12 _cairo_surface_fallback_fill
from /usr/lib/libcairo.so.2
#13 _cairo_surface_fill
from /usr/lib/libcairo.so.2
#14 _cairo_gstate_fill
from /usr/lib/libcairo.so.2
#15 cairo_fill_preserve
from /usr/lib/libcairo.so.2
#16 cairo_fill
from /usr/lib/libcairo.so.2
#17 rsvg_cairo_render_path
from /usr/lib/librsvg-2.so.2
#18 rsvg_render_path
from /usr/lib/librsvg-2.so.2
#19 rsvg_node_path_draw
from /usr/lib/librsvg-2.so.2
#20 rsvg_node_draw
from /usr/lib/librsvg-2.so.2
#21 _rsvg_node_draw_children
from /usr/lib/librsvg-2.so.2
#22 rsvg_node_draw
from /usr/lib/librsvg-2.so.2
#23 rsvg_node_svg_draw
from /usr/lib/librsvg-2.so.2
#24 rsvg_node_draw
from /usr/lib/librsvg-2.so.2
#25 rsvg_handle_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#26 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#27 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#28 gdk_pixbuf__svg_image_stop_load
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#29 gdk_pixbuf_loader_close
from /usr/lib/libgdk_pixbuf-2.0.so.0
#30 gnome_gdk_pixbuf_new_from_uri_at_scale
from /opt/gnome/lib/libgnomeui-2.so.0
#31 gnome_thumbnail_factory_generate_thumbnail
from /opt/gnome/lib/libgnomeui-2.so.0
#32 ??
#33 ??
#34 ??
#35 ??
#36 ??



----------- .xsession-errors (8299 sec old) ---------------------
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-04-09 22:35:48 UTC


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