Bug #15389
PDF files should be opened with Libreoffice Draw if specificaly asked
100%
Description
to reproduce :
right click on an editable PDF file, “open with another application”, select “libreoffice Draw” in the list
result :
Libreoffice Writer is started instead of Libreoffice Draw
The same thing happens when trying to open the pdf file from inside Libreoffice Draw.
I couldn’t reproduce this in Debian sid
Subtasks
History
#2 Updated by goupille 2018-03-08 17:29:41
I forgot to specify that I reproduced this issue in Tails 3.6~rc1
#3 Updated by intrigeri 2018-03-10 09:15:48
- Assignee changed from anonym to intrigeri
- Target version set to Tails_3.7
> Libreoffice Writer is started instead of Libreoffice Draw
Confirmed.
First, AppArmor is not involved: we don’t confine LibreOffice on Stretch.
I see these processes running so at least the .desktop
file seems to be correct:
/usr/lib/libreoffice/program/oosplash --draw file:///home/amnesia/confidential.pdf
/usr/lib/libreoffice/program/soffice.bin --draw file:///home/amnesia/confidential.pdf --splash-pipe=5
Running libreoffice --draw
on the command line correctly starts LibreOffice Draw.
But:
$ libreoffice --draw confidential.pdf
javaldx: Could not find a Java Runtime Environment!
Warning: failed to read path from javaldx
:1: parser error : Document is empty
%PDF-1.2
^
:1: parser error : Document is empty
%PDF-1.2
^
:1: parser error : Document is empty
%PDF-1.2
^
… opens the document in LibreOffice Writer. Same if I start LibreOffice Draw and do File → Open → confidential.pdf.
After installing default-jre
and libreoffice-java-common
I don’s see the Java-related warnings but the problem is still there.
I think the problem is not Stretch vs. sid but rather a missing package in Tails. But I did not find which one yet. I’ll come back to it later.
Next step: try to reproduce on feature/buster.
#4 Updated by intrigeri 2018-03-30 12:20:39
- Status changed from Confirmed to Resolved
- Target version changed from Tails_3.7 to Tails_4.0
- % Done changed from 0 to 100
intrigeri wrote:
> Next step: try to reproduce on feature/buster.
It works just fine on current feature/buster :)
If you think it’s worth spending more time on fixing this in Tails 3.x, please let me know.