The component I was using when I first saw this bug was Base. I inserted a pushbutton control into a form and modified the graphics property (in the control property dialog box) to be an absolute path reference to a png icon file. The graphic was displayed properly in the button at the time, and I saved the database document as an odb file. I then invoked that odb file via a symbolic link in my Desktop folder (which is different than the folder the actual odb file is stored in) and the icon does not appear on the button. Upon investigation, I found that the path name that I had entered for the icon had been modified based on whether I invoked the database from the original odb file or the symbolic link pointing to that file. Actual path to icon file: /home/USER/Projects/kitchen/images/icon.png Actual path to odb file /home/USER/Projects/kitchen/db.odb Path to link to odb: /home/USER/Desktop/db.odb Path entered in the control dialog box for graphic: /home/USER/Projects/kitchen/images/icon.png (this path is reported any time database is opened from the actual file) Path reported in control dialog box for graphic when opened from link: /home/USER/Projects/Projects/images/icon.png This transformation of path is reproducible. Any time the database is opened from the actual database odb file, the correct pathname is used and the graphics appear properly. Any time the database is opened from the link on the desktop, the reduplication of the Projects element occurs and the graphics do not appear. I have discovered a work-around that works in this particular case, but is untested in any other case. If I enter the path for the icon as ~/Projects/kitchen/icon.png, the problem does not occur, and the database opens properly from either the actual odb file or the symbolic link referencing it.
No problem here when I set things up and open the symlink. Note for testers: in the right-click - Control for the Push button, when you scroll down in the General tab and insert the Graphics, insert it as link. Michael: what Linux distro are you using? Arch Linux 64-bit Version: 6.0.3.2 Build ID: 6.0.3-1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Arch Linux 64-bit Version: 6.1.0.0.alpha0+ Build ID: de07f40030bbd604bc42d58f0e954cca284a2646 CPU threads: 8; OS: Linux 4.16; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on April 21st 2018
I'm running Ubuntu 16.04 LTS with LibreOffice 6.0.3.2 00m0(Build:2) installed. As noted in my original report, I have a work-around that works consistently regardless of whether the odb file is invoked (via double-click in Nautilus graphic file manager) from the folder in which it resides or from a symlink in another folder.
Hello Michael Milliman, A new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Michael Milliman, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Michael Milliman, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp