Description: Extension Manager generates error when updating extension MRI - UNO Object Inspection Tool from version 1.3.3 to 1.3.4. Steps to Reproduce: 1. $ loffice (or open via GNU) 2. Select tools/extension manager 3. Click 'Check for updates': Extension Update Available extension updates MRI - UNO Object Inspection Tool Version 1.3.4 4. Click 'Install': Download and Installation Installation finished Result (edited for readability): Error while installing extension MRI - UNO Object Inspection Tool. The error message is: Cannot detect media-type: file:///tmp/TJiylU_/vQfBh6_/4a425d00-08a5-11e9-9a77-0d8bd079b003 /build/libreoffice-PVihB3/libreoffice-7.0.3/desktop/source/deployment/registry/dp_registry.cxx:481 The extension will not be installed. 5. Rebooting and repeating all of the above steps yields the identical error message -- including the /tmp path names. Actual Results: Result (line breaks added for readability): Error while installing extension MRI - UNO Object Inspection Tool. The error message is: Cannot detect media-type: file:///tmp/TJiylU_/vQfBh6_/4a425d00-08a5-11e9-9a77-0d8bd079b003 /build/libreoffice-PVihB3/libreoffice-7.0.3/desktop/source/deployment/registry/dp_registry.cxx:481 The extension will not be installed. Expected Results: Some sort of successful completion. Reproducible: Always User Profile Reset: Yes OpenGL enabled: Yes Additional Info: Version: 7.0.3.1 Build ID: 00(Build:1) CPU threads: 4; OS: Linux 5.8; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Ubuntu package version: 1:7.0.3-0ubuntu0.20.10.1 Calc: threaded MRI files currently installed: ~/.config/libreoffice/4/user/uno_packages/cache/uno_packages/lu33648zlk261.tmp_/ * MRI-1.3.3.oxtproperties * MRI-1.3.3.oxt * MRI-1.3.3.oxt/mri.uno.rdb * MRI-1.3.3.oxt/icons/mri_hc.png * MRI-1.3.3.oxt/icons/mri.png * MRI-1.3.3.oxt/MRILib * MRI-1.3.3.oxt/MRI.py --- SYSTEM ENVIRONMENT $ uname --all Linux pop8 5.8.0-7642-generic #47~1614007149~20.10~82fb226-Ubuntu SMP Tue Feb 23 02:59:01 UTC x86_64 x86_64 x86_64 GNU/Linux Settings About: memory: 7.6 GiB processor: Intel Core I5-6200U CPU @ 2.3 GHz x 4 graphics: Mesa Intel HD Graphics 520 (SKL GT2) disk capacity: 1.0 TB OS Name: Pop!_OS 20.10 OS Type: 64-bit
Tom, unfortunately nobody could confirm this bug report for half a year. So I'd like to ask, if it is still valid. 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 Tom Eubank, 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 Tom Eubank, 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