GNOME Bugzilla – Bug 171588
should give better diagnosis of documents with no pages
Last modified: 2008-06-16 17:53:31 UTC
Distribution: Fedora Core release 3 (Heidelberg) Package: gpdf Severity: normal Version: GNOME2.8.0 unspecified Gnome-Distributor: Red Hat, Inc Synopsis: gpdf crashes when given the following PDF Bugzilla-Product: gpdf Bugzilla-Component: general Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: (gpdf:12751): Bonobo-CRITICAL **: file bonobo-control-frame.c: line 539 (bonobo_control_frame_control_deactivate): assertion `frame->priv->control != CORBA_OBJECT_NIL' failed Steps to reproduce the crash: 1. attempt to view a certain file 2. 3. Expected Results: An error dialog informing me that the file is not well-formed? How often does this happen? every time! Additional Information: Here's the file in binary form... [richard@biostar music]$ od -x test.pdf 0000000 5025 4644 312d 322e 250a ecc7 a28f 330a 0000020 3020 6f20 6a62 3c0a 203c 542f 7079 2065 0000040 502f 6761 7365 2f20 694b 7364 5b20 5d0a 0000060 2f20 6f43 6e75 2074 0a30 3e3e 650a 646e 0000100 626f 0a6a 2031 2030 626f 0a6a 3c3c 542f 0000120 7079 2065 432f 7461 6c61 676f 2f20 6150 0000140 6567 2073 2033 2030 0a52 3e3e 650a 646e 0000160 626f 0a6a 2032 2030 626f 0a6a 3c3c 502f 0000200 6f72 7564 6563 2872 4e47 2055 6847 736f 0000220 7374 7263 7069 2074 2e37 3730 3e29 653e 0000240 646e 626f 0a6a 7278 6665 300a 3420 300a 0000260 3030 3030 3030 3030 2030 3536 3335 2035 0000300 2066 300a 3030 3030 3030 3630 2038 3030 0000320 3030 2030 206e 300a 3030 3030 3030 3131 0000340 2036 3030 3030 2030 206e 300a 3030 3030 0000360 3030 3130 2035 3030 3030 2030 206e 740a 0000400 6172 6c69 7265 3c0a 203c 532f 7a69 2065 0000420 2034 522f 6f6f 2074 2031 2030 2052 492f 0000440 666e 206f 2032 2030 0a52 3e3e 730a 6174 0000460 7472 7278 6665 310a 3636 250a 4525 464f 0000500 000a 0000501 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-25 09:45 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "gpdf". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was r.oak@nospam.btopenworld.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Man generating that file was a PITA. (od switches the endianness) anyway here is the backtrace against gpdf 2.10.0: (gpdf:22071): Bonobo-CRITICAL **: bonobo_control_frame_control_deactivate: assertion `frame->priv->control != CORBA_OBJECT_NIL' failed Backtrace was generated from '/usr/libexec/gnome-pdf-viewer' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) `system-supplied DSO at 0xffffe000' has disappeared; keeping its symbols. (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1223629120 (LWP 22073)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 61874
Thread 1 (Thread -1223629120 (LWP 22073))
Created attachment 49438 [details] the file which causes the crash here is the file that was generated from the submitter's report
stack trace is unique according to simple-dup-finger, marking new. note that this also causes evince 0.3.2 to crash, I will be filing a bug for that shortly as well...
Brent, if it causes poppler and gpdf to crash, the right thing to do is file a bug against 'poppler' (the pdf library, culled from xpdf) in bugzilla.freedesktop.org.
'causes evince and gpdf to crash', I meant.
The error I get from acroread 7.0 is "The file cannot be opened because there are no pages".
Gpdf is no longer maintained, closing WONTFIX. Please use Evince for your pdf viewing needs. http://www.gnome.org/projects/evince/
evince 0.5.0 does not crash, but what it does do is unhelpful - it pops up its normal display, but with a gray box where the content area should be, all the controls grayed out, and "of 0" next to the page number type-in box. It is not immediately obvious from this that the PDF has no content. It should instead display some sort of diagnostic - I recommend something like firefox 1.5's nice in-the-page server error displays. (So, for instance, the content area could have the yellow ! sign and the words "This PDF has no content.") Recommend reopening, reassigning to evince, retitling "need more helpful diagnosis of PDFs with no pages."
Done by someone else, and I've just fixed the title. Thanks.
Would showing an error dialog be a good idea?
IMO this is not an error demanding the user's immediate attention. Per comment #8, my recommendation is to display some sort of message in the content area, where the user will see it the next time they look at the window, but will not be bothered by it until then.
Fixed in svn trunk now.