Created attachment 150632 [details] Spreadsheet should shown graph when inserted as linked OLE object Editing a document, insert OLE object, create from file, type "Libre Office 6.1 Spreadsheet" with "link to file" checked. Ugly "Object 1" blob is shown instead of OLE preview (which is present in linked file). Example file is attached.
Created attachment 150662 [details] ole_object not reproducible, ole object is shown in attached spreadsheet
I have this problem inserting the object into a *write* document, not a spreadsheet. I have no idea why someon changed the problem from 'write' to 'calc'. Please let me know if you cannot reproduce in *write* and I'll post an example *write* document where I cannot insert the object. Thanks!
Created attachment 150664 [details] test ole writer linked attached writer document is linked to attached spreadsheet. lo asks to update the reference on load and displays the ole object.
I've attached the image I see. Using Windows 10 64-bit.
Created attachment 150665 [details] OLE object not displayed in write document
(In reply to Dave Nadler from comment #2) > I have this problem inserting the object into a *write* document, not a > spreadsheet. I have no idea why someon changed the problem from 'write' to > 'calc'. Sorry, my fault. => I chnaged it back to Writer
(In reply to Dave Nadler from comment #5) > Created attachment 150665 [details] > OLE object not displayed in write document Please check if "Display Images and Opjects" is enabled under Tools =>Options => LibreOffice Writer => View
Created attachment 150666 [details] LibreOffice Write document not showing linked OLE object Example document showing the problem...
Created attachment 150667 [details] Options panel image "Display Images and Opjects" is enabled under Tools =>Options, image attached.
Are you able to reproduce this problem??? Thanks!
I could repoduce it with Version: 6.2.2.2 (x64) Build-ID: 2b840030fec2aae0fd2658d8d4f9548af4e3518d CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: threaded but not with Version: 6.3.0.0.alpha0+ (x64) Build ID: 421e6fc3cd2e6fe37afbef341e2d0ad7b8edde37 CPU threads: 4; OS: Windows 10.0; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-04-07_01:12:58 Locale: en-US (de_DE); UI-Language: en-US Calc: threaded So I think, this bug already has been fixed. Can you try it with LO master? (https://dev-builds.libreoffice.org/daily/master/Win-x86_64@42/) I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in master. Change to RESOLVED WORKSFORME, if the problem went away.
Is there a Windows installer that will quickly install a test version without deranging my existing install? I can't afford to waste even more time with a buggy alpha release... Thanks, Best Regards, Dave
(In reply to Dave Nadler from comment #12) > Is there a Windows installer that will quickly install a test version > without deranging my existing install? you can try with an administrative network install, e.g.: msiexec /a LibreOffice_6.1.6.1_Win_x64.msi TARGETDIR="C:\Program Files\LibreOffice 6.1" this will extract the files only without system integration. i recommend to change the "bootstrap.ini" too, e.g.: UserInstallation=$SYSUSERCONFIG/LibreOffice/61 this will create a new user profile folder "61" in %appdata%\LibreOffice
Created attachment 151007 [details] Screenshot showing 6.3 is still broken Still broken. Version: 6.3.0.0.alpha0+ (x64) Build ID: 3083fe569f96bf0289da1e9d0ef7da15ab22e2f6 Note I did not re-save the calc document prior to adding the OLE link to it.
Try with Help - Restart in safe mode and then Continue in safe mode. Also, please copy and paste here the contents of your Help - About. This allows us to know more about your system. Set to NEEDINFO. Change back to UNCONFIRMED after you have provided the information.
Dear Dave Nadler, 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
(In reply to Buovjaga from comment #15) > Try with Help - Restart in safe mode and then Continue in safe mode. > > Also, please copy and paste here the contents of your Help - About. This > allows us to know more about your system. > > Set to NEEDINFO. > Change back to UNCONFIRMED after you have provided the information. Dave: you did not do what I asked, though.
Dear Dave Nadler, 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