evince crashed in Catalog::embeddedFile

Bug #113133 reported by johannes
28
Affects Status Importance Assigned to Milestone
Poppler
Fix Released
Medium
poppler (Ubuntu)
Incomplete
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evince

couldn't reproduce the crash

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. Could you attach the pdf triggering the bug?

Changed in evince:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
johannes (j00hannes) wrote :

i'm sorry, i can't remember which document it was.

but i suppose that the reason was not in the document, because trying to open it again after the crash did not affect evince.

Revision history for this message
In , Sebastien Bacher (seb128) wrote :

The bug has been opened on https://bugs.launchpad.net/bugs/113133

"Binary package hint: evince

couldn't reproduce the crash
...
ProblemType: Crash
Architecture: i386
Date: Mon May 7 18:00:28 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/evince
...
i'm sorry, i can't remember which document it was.

but i suppose that the reason was not in the document, because trying to open it again after the crash did not affect evince.
..."

Debug backtrace of the crash:

"#0 0xb758f151 in Catalog::embeddedFile (this=0x8385510, i=0) at Catalog.cc:406
#1 0xb76b04ef in poppler_document_get_attachments () from /usr/lib/libpoppler-glib.so.1
#2 0x080a165d in pdf_document_get_attachments (document=0x834cca0) at ev-poppler.cc:393
#3 0x0809c30b in ev_document_get_attachments (document=0x834cca0) at ev-document.c:228
#4 0x0808932c in ev_sidebar_attachments_set_document (page=0x82302b0, document=0x834cca0) at ev-sidebar-attachments.c:624
#5 0x08087e40 in ev_sidebar_set_document (sidebar=0x8234630, document=0x834cca0) at ev-sidebar.c:507
#6 0x080817cf in ev_window_load_job_cb (job=0x834cb68, data=0x8146000) at ev-window.c:1102
#7 0xb71e99d9 in IA__g_cclosure_marshal_VOID__VOID (closure=0x8396758, return_value=0x0, n_param_values=1,
    param_values=0xbfc4b0fc, invocation_hint=0xbfc4b00c, marshal_data=0x80814e0) at gmarshal.c:77
#8 0xb71dc62b in IA__g_closure_invoke (closure=0x8396758, return_value=0x0, n_param_values=1, param_values=0xbfc4b0fc,
    invocation_hint=0xbfc4b00c) at gclosure.c:490
#9 0xb71ed103 in signal_emit_unlocked_R (node=0x839f310, detail=0, instance=0x834cb68, emission_return=0x0,
    instance_and_params=0xbfc4b0fc) at gsignal.c:2440
#10 0xb71ee627 in IA__g_signal_emit_valist (instance=0x834cb68, signal_id=257, detail=0,
    var_args=0xbfc4b33c "H�\034��{r�H�\034�X�Ŀ�\210\006\bh�4\b��4\bx�Ŀ\221 \026�h�4\b��;\bx�Ŀҿ\027�\b")
    at gsignal.c:2199
#11 0xb71ee7e9 in IA__g_signal_emit (instance=0x834cb68, signal_id=257, detail=0) at gsignal.c:2243
#12 0x08068d26 in ev_job_finished (job=0x834cb68) at ev-jobs.c:233
#13 0x080688f2 in notify_finished (job=0x834cb68) at ev-job-queue.c:67
#14 0xb7162091 in g_idle_dispatch (source=0x83bd2a8, callback=0, user_data=0x834cb68) at gmain.c:3928
#15 0xb7163df2 in IA__g_main_context_dispatch (context=0x810a108) at gmain.c:2045
#16 0xb7166dcf in g_main_context_iterate (context=0x810a108, block=1, dispatch=1, self=0x80e1258) at gmain.c:2677
#17 0xb7167179 in IA__g_main_loop_run (loop=0x812e8b0) at gmain.c:2881
#18 0xb7a38044 in IA__gtk_main_do_event (event=0x81307b0) at gtkmain.c:1320
#19 0x0808def0 in main (argc=2, argv=Cannot access memory at address 0x5
) at main.c:319"

Revision history for this message
Sebastien Bacher (seb128) wrote : Re: evince crashed without any obvious reason

Debug backtrace of the crash:

"#0 0xb758f151 in Catalog::embeddedFile (this=0x8385510, i=0) at Catalog.cc:406
#1 0xb76b04ef in poppler_document_get_attachments () from /usr/lib/libpoppler-glib.so.1
#2 0x080a165d in pdf_document_get_attachments (document=0x834cca0) at ev-poppler.cc:393
#3 0x0809c30b in ev_document_get_attachments (document=0x834cca0) at ev-document.c:228
#4 0x0808932c in ev_sidebar_attachments_set_document (page=0x82302b0, document=0x834cca0) at ev-sidebar-attachments.c:624
#5 0x08087e40 in ev_sidebar_set_document (sidebar=0x8234630, document=0x834cca0) at ev-sidebar.c:507
#6 0x080817cf in ev_window_load_job_cb (job=0x834cb68, data=0x8146000) at ev-window.c:1102
#7 0xb71e99d9 in IA__g_cclosure_marshal_VOID__VOID (closure=0x8396758, return_value=0x0, n_param_values=1,
    param_values=0xbfc4b0fc, invocation_hint=0xbfc4b00c, marshal_data=0x80814e0) at gmarshal.c:77
#8 0xb71dc62b in IA__g_closure_invoke (closure=0x8396758, return_value=0x0, n_param_values=1, param_values=0xbfc4b0fc,
    invocation_hint=0xbfc4b00c) at gclosure.c:490
#9 0xb71ed103 in signal_emit_unlocked_R (node=0x839f310, detail=0, instance=0x834cb68, emission_return=0x0,
    instance_and_params=0xbfc4b0fc) at gsignal.c:2440
#10 0xb71ee627 in IA__g_signal_emit_valist (instance=0x834cb68, signal_id=257, detail=0,
    var_args=0xbfc4b33c "H�\034��{r�H�\034�X�Ŀ�\210\006\bh�4\b��4\bx�Ŀ\221 \026�h�4\b��;\bx�Ŀҿ\027�\b")
    at gsignal.c:2199
#11 0xb71ee7e9 in IA__g_signal_emit (instance=0x834cb68, signal_id=257, detail=0) at gsignal.c:2243
#12 0x08068d26 in ev_job_finished (job=0x834cb68) at ev-jobs.c:233
#13 0x080688f2 in notify_finished (job=0x834cb68) at ev-job-queue.c:67
#14 0xb7162091 in g_idle_dispatch (source=0x83bd2a8, callback=0, user_data=0x834cb68) at gmain.c:3928
#15 0xb7163df2 in IA__g_main_context_dispatch (context=0x810a108) at gmain.c:2045
#16 0xb7166dcf in g_main_context_iterate (context=0x810a108, block=1, dispatch=1, self=0x80e1258) at gmain.c:2677
#17 0xb7167179 in IA__g_main_loop_run (loop=0x812e8b0) at gmain.c:2881
#18 0xb7a38044 in IA__gtk_main_do_event (event=0x81307b0) at gtkmain.c:1320
#19 0x0808def0 in main (argc=2, argv=Cannot access memory at address 0x5
) at main.c:319"

Changed in evince:
status: Needs Info → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :
Changed in poppler:
status: Unknown → Confirmed
Revision history for this message
In , Sebastien Bacher (seb128) wrote :

There is a similar crash on https://bugs.launchpad.net/ubuntu/+source/evince/+bug/147197 using poppler 0.6 and GNOME 2.20.0

Revision history for this message
In , Carlos Garcia Campos (carlosgc) wrote :

Could you please attach here a copy of the pdf document causing this crash?

Revision history for this message
In , Brad Hards (bradh) wrote :

Without a copy of a document that causes the crash, this is probably not going to be fixed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could anybody attach an example to the bug?

Changed in poppler:
status: Confirmed → Incomplete
Revision history for this message
In , Nicholas Miell (nmiell-deactivatedaccount) wrote :

"PDF Reference and Related Documentation (PDF, 15.3M) (Updated on Oct. 23, 2007 with revised errata)" located at http://www.adobe.com/devnet/acrobat/pdfs/pdf_reference.pdf is one such document.

Open it multiple times, sometimes it crashes immediately, sometimes it opens but gives errors when attempting to open the attachments, sometimes it opens and opening the attachments succeeds.

evince 2.20.2, poppler 0.6.2

Revision history for this message
In , Nicholas Miell (nmiell-deactivatedaccount) wrote :

http://bugzilla.gnome.org/show_bug.cgi?id=415714 seems to be the Evince clearinghouse for this bug, you may be able to find other PDFs that also cause this crash amongst the hundreds of reports.

Revision history for this message
alonso (giulio-alfano) wrote :

My file is copyrighted, if you need it send me a mail giulio.alfano (at) gmail.com. The bug

Changed in poppler:
status: Incomplete → Triaged
Revision history for this message
In , Albert Astals Cid (aacid) wrote :

Could you try this with a newer poppler?

Also don't think it's a splash bug.

Revision history for this message
Sebastien Bacher (seb128) wrote :

could somebody try if that's still an issue in jaunty or karmic?

Changed in poppler (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could somebody try if that's still an issue in jaunty or karmic?

Changed in poppler:
importance: Unknown → Medium
Changed in poppler:
importance: Medium → Unknown
Changed in poppler:
importance: Unknown → Medium
Changed in poppler:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.