Bug 407579

Summary: Bad behavior of RadioButton groups in Optional Contents
Product: [Applications] okular Reporter: Édouard Canot <Edouard.Canot>
Component: PDF backendAssignee: Okular developers <okular-devel>
Status: RESOLVED UPSTREAM    
Severity: normal CC: aacid
Priority: NOR    
Version: 1.6.3   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: PDF 1.5 Standard Compliant example using RBGroups

Description Édouard Canot 2019-05-16 06:28:02 UTC
Created attachment 120100 [details]
PDF 1.5 Standard Compliant example using RBGroups

SUMMARY

When using RBGroups (RadioButton groups) of Optional Contents, we can switch from one group to another one in the "layers" panel of okular, but the drawing of the corresponding graphic objects is not updated.

STEPS TO REPRODUCE
1. open the attached file "Labels_and_Languages_3_OC.pdf"
2. open the "layers" panel
3. open the "Language" group
4. switch from one language to another

OBSERVED RESULT
The switching between languages in the user interface is correct (mutually exclusive Optional Contents is implemented via the RadioButton group) but the display is not updated: texts are overwritten on the display.

EXPECTED RESULT
Each language should lead to different text strings.


SOFTWARE/OS VERSIONS
Linux distro: Ubuntu-19.04 (and before)
Okular version: 1.6.3
PDF Backend: 0.6.5
KDE Framework: 5.56.0
Qt version: 5.12.2

ADDITIONAL INFORMATION
The PDF has been generated by my own graphic library Muesli. You can open the attached PDF file with any text editor since it uses only ASCII characters. To my knowledge, it is standard compliant: 'mupdf' doesn't claim about any errors, and the "PDF Tools Online" validator (https://www.pdf-online.com/osa/validate.aspx) returns nothing special about it:      
    Validating file "Labels_and_Languages_3_OC.pdf" for conformance level pdf1.5
    The document does conform to the PDF 1.5 standard.
    Done.
Comment 1 Albert Astals Cid 2019-05-16 15:46:15 UTC
Thanks for the report.

It was actually a poppler bug.

No need to report it, i already fixed it at https://gitlab.freedesktop.org/poppler/poppler/commit/65adf225eca287f63361cf49bd47388bff81af79