Bug 388436 – crash in Image Viewer: using page down to move ...

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 388436 - crash in Image Viewer: using page down to move ...


Summary:	crash in Image Viewer: using page down to move ...


Status:	RESOLVED DUPLICATE of bug 360691

Product:	eog
Classification:	Core
Component:	general
Version:	2.16.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-12-21 22:42 UTC by dwayne
Modified:	2006-12-24 03:49 UTC

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

Description dwayne 2006-12-21 22:42:13 UTC

Version: 2.16.1

What were you doing when the application crashed?
using page down to move to the next image in the directory (which was an SVG file produced by inkscape)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 61845504 vsize: 0 resident: 61845504 share: 0 rss: 24125440 rss_rlim: 0
CPU usage: start_time: 1166740823 rtime: 0 utime: 218 stime: 0 cutime:148 cstime: 0 timeout: 70 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226794816 (LWP 15709)]
[New Thread -1251284064 (LWP 15711)]
[New Thread -1228444768 (LWP 15710)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 96090

Thread 2 (Thread -1251284064 (LWP 15711))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/tls/i686/cmov/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 cairo_restore
from /usr/lib/libcairo.so.2
#5 pango_cairo_show_glyph_string
from /usr/lib/libpangocairo-1.0.so.0
#6 pango_renderer_draw_glyphs
from /usr/lib/libpango-1.0.so.0
#7 pango_renderer_draw_layout_line
from /usr/lib/libpango-1.0.so.0
#8 pango_renderer_draw_layout
from /usr/lib/libpango-1.0.so.0
#9 pango_cairo_show_error_underline
from /usr/lib/libpangocairo-1.0.so.0
#10 rsvg_error_get_type
from /usr/lib/librsvg-2.so.2
#11 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#12 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#13 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#14 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#15 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#16 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#17 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#18 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#19 rsvg_handle_new_from_data
from /usr/lib/librsvg-2.so.2
#20 rsvg_handle_render_cairo_sub
from /usr/lib/librsvg-2.so.2
#21 rsvg_handle_get_pixbuf_sub
from /usr/lib/librsvg-2.so.2
#22 rsvg_handle_get_pixbuf
from /usr/lib/librsvg-2.so.2
#23 fill_info
from /usr/lib/gtk-2.0/2.10.0/loaders/svg_loader.so
#24 ??
#25 ??
#26 ??
#27 gnome_vfs_find_directory
from /usr/lib/libgnomevfs-2.so.0
#28 gdk_pixbuf_loader_close
from /usr/lib/libgdk_pixbuf-2.0.so.0
#29 eog_image_load
#30 eog_window_get_uri
#31 eog_job_call_action
#32 eog_job_manager_add
#33 g_thread_create_full
from /usr/lib/libglib-2.0.so.0
#34 start_thread
from /lib/tls/i686/cmov/libpthread.so.0
#35 clone
from /lib/tls/i686/cmov/libc.so.6

Comment 1 Bruno Boaventura 2006-12-24 03:49:37 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 360691 ***