Bug 103260 - No images in Help
Summary: No images in Help
Status: CLOSED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Documentation (show other bugs)
Version:
(earliest affected)
5.2.2.2 release
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-16 17:37 UTC by Petr Valach
Modified: 2016-10-30 23:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Valach 2016-10-16 17:37:27 UTC
Description:
In some last versions, I cannot see any images in Help documentation. It persists for at least one year.

Steps to Reproduce:
1.Open any module.
2.Print F1 to see Help.


Actual Results:  
No images at any pages. Question mark appears instead of them.

Expected Results:
Icons and images appears everywhere.


Reproducible: Always

User Profile Reset: Yes

Additional Info:


User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:49.0) Gecko/20100101 Firefox/49.0
Comment 1 Dennis Roczek 2016-10-16 18:10:20 UTC
I guess for the offline-built-in-help.

which version are you using and on which distribution?
Comment 2 Petr Valach 2016-10-16 18:57:50 UTC
I use the last 5.2.2 and now I install the version from web and I can see images in Help there. But persist another problem, no images of modules in Quick Starter. But I can use it in that installation, quick launch is inaccessible in version from repository. I use Linux Mint on KDE.

OK, it seems that problem with images in Help is problem of distribution (and I can see no Firebird support in Base, for example, too). But problem with inaccessible icons in Quick Launch is caused with web version. Should I start with new topic?
Comment 3 Buovjaga 2016-10-26 18:55:24 UTC
Maybe you should report it to Mint: https://bugs.launchpad.net/linuxmint
Or if you are unsure, if it is a real bug, ask in their forum first: http://forum.linuxmint.com/

Let's close for now. If it turns out to be due to LibreOffice itself, we can always revisit.