Bug 361903 – crashed while try to mark

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 361903 - crashed while try to mark


Summary:	crashed while try to mark


Status:	RESOLVED DUPLICATE of bug 316907

Product:	evince
Classification:	Core
Component:	general
Version:	unspecified
Hardware:	Other other

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-13 10:24 UTC by t.juettemann
Modified:	2006-10-13 22:40 UTC

See Also:
GNOME target:	---
GNOME version:	2.13/2.14

Description t.juettemann 2006-10-13 10:23:25 UTC

Distribution: Fedora Core release 5 (Bordeaux)
Package: evince
Severity: Normal
Version: GNOME2.14.3 unspecified
Gnome-Distributor: Red Hat, Inc
Synopsis: crashed while try to mark
Bugzilla-Product: evince
Bugzilla-Component: documentation
Bugzilla-Version: unspecified
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. searched in pdf for word "disadvantage" 
2. tried to mark some words using mouse
3. crash

Expected Results:


How often does this happen?
first time

Additional Information:



Debugging Information:

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its
symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208677504 (LWP 24429)]
[New Thread -1211868256 (LWP 24430)]
(no debugging symbols found)
0x006cc402 in __kernel_vsyscall ()

+ Trace 76117

Thread 1 (Thread -1208677504 (LWP 24429))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 gnome_gtk_module_info_get
from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 CairoFont::CairoFont
from /usr/lib/libpoppler-glib.so.1
#5 CairoFontEngine::getFont
from /usr/lib/libpoppler-glib.so.1
#6 CairoOutputDev::updateFont
from /usr/lib/libpoppler-glib.so.1
#7 TextSelectionPainter::visitWord
from /usr/lib/libpoppler.so.1
#8 TextWord::visitSelection
from /usr/lib/libpoppler.so.1
#9 TextLine::visitSelection
from /usr/lib/libpoppler.so.1
#10 TextBlock::visitSelection
from /usr/lib/libpoppler.so.1
#11 TextPage::visitSelection
from /usr/lib/libpoppler.so.1
#12 TextPage::drawSelection
from /usr/lib/libpoppler.so.1
#13 TextOutputDev::drawSelection
from /usr/lib/libpoppler.so.1
#14 poppler_page_render_selection
from /usr/lib/libpoppler-glib.so.1
#15 pdf_selection_render_selection
#16 pdf_document_find_get_progress
#17 ??
#18 ??
#19 g_list_remove_link
from /usr/lib/libglib-2.0.so.0
#20 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#21 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#22 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#23 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#24 ??
#25 __libc_start_main
from /lib/libc.so.6
#26 ??





------- Bug created by bug-buddy at 2006-10-13 10:24 -------

Comment 1 Reinout van Schouwen 2006-10-13 12:39:31 UTC

Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Comment 2 Karsten Bräckelmann 2006-10-13 22:40:28 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 316907 ***