Bug 419854 – crash in Document Viewer: Ik sloot Open Office Pre...

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 419854 - crash in Document Viewer: Ik sloot Open Office Pre...


Summary:	crash in Document Viewer: Ik sloot Open Office Pre...


Status:	RESOLVED DUPLICATE of bug 423690

Product:	evince
Classification:	Core
Component:	general
Version:	0.6.x
Hardware:	Other All

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-03-18 19:30 UTC by d.mommaerts
Modified:	2007-04-07 15:15 UTC

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

Description d.mommaerts 2007-03-18 19:30:38 UTC

Version: 0.6.1

What were you doing when the application crashed?
Ik sloot Open Office Presentatie af.


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

Memory status: size: 114118656 vsize: 0 resident: 114118656 share: 0 rss: 56639488 rss_rlim: 0
CPU usage: start_time: 1174246193 rtime: 0 utime: 195 stime: 0 cutime:177 cstime: 0 timeout: 18 it_real_value: 0 frequency: 0

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

(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 -1229842768 (LWP 8890)]
[New Thread -1231721568 (LWP 8892)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 119819

Thread 1 (Thread -1229842768 (LWP 8890))

#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 g_type_instance_get_private
from /usr/lib/libgobject-2.0.so.0
#5 pango_fc_font_lock_face
from /usr/lib/libpangoft2-1.0.so.0
#6 g_type_create_instance
from /usr/lib/libgobject-2.0.so.0
#7 g_object_set
from /usr/lib/libgobject-2.0.so.0
#8 g_object_newv
from /usr/lib/libgobject-2.0.so.0
#9 g_object_new_valist
from /usr/lib/libgobject-2.0.so.0
#10 g_object_new
from /usr/lib/libgobject-2.0.so.0
#11 pango_cairo_fc_font_get_type
from /usr/lib/libpangocairo-1.0.so.0
#12 pango_cairo_fc_font_map_get_type
from /usr/lib/libpangocairo-1.0.so.0
#13 pango_fc_font_map_get_type
from /usr/lib/libpangoft2-1.0.so.0
#14 pango_font_map_load_fontset
from /usr/lib/libpango-1.0.so.0
#15 pango_context_get_font_description
from /usr/lib/libpango-1.0.so.0
#16 pango_itemize_with_base_dir
from /usr/lib/libpango-1.0.so.0
#17 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#18 pango_layout_iter_get_char_extents
from /usr/lib/libpango-1.0.so.0
#19 pango_layout_get_pixel_extents
from /usr/lib/libpango-1.0.so.0
#20 gtk_cell_renderer_text_new
from /usr/lib/libgtk-x11-2.0.so.0
#21 gtk_cell_renderer_get_size
from /usr/lib/libgtk-x11-2.0.so.0
#22 gtk_icon_view_selected_foreach
from /usr/lib/libgtk-x11-2.0.so.0
#23 gtk_icon_view_scroll_to_path
from /usr/lib/libgtk-x11-2.0.so.0
#24 gtk_icon_view_scroll_to_path
from /usr/lib/libgtk-x11-2.0.so.0
#25 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#27 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#28 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#29 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#30 ??
#31 ??
#32 ??
#33 ??
#34 ??
#0 __kernel_vsyscall

Comment 1 gnome 2007-03-21 11:19:51 UTC

For the non-dutch-reading people: he was closing an openoffice.org presentation and evince crashed on him.

Comment 2 palfrey 2007-04-07 15:15:24 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 423690 ***