| Summary: | FILEASSOC Uninstalling Libreoffice removes Microsoft Office file associations | ||
|---|---|---|---|
| Product: | LibreOffice | Reporter: | Charles <tanstaafl> |
| Component: | Installation | Assignee: | Not Assigned <libreoffice-bugs> |
| Status: | NEW --- | QA Contact: | |
| Severity: | major | ||
| Priority: | high | CC: | timar74 |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | Windows (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
Charles
2012-01-04 12:56:29 UTC
Just before this I also added another bug/enhancement request for a proper 'File Associations Manager', to provide a way to control these file associations (and change/reset them if desired without having to re-run the full installer), if anyone is interested... https://bugs.freedesktop.org/show_bug.cgi?id=44462 Please to consider this bug much more important than it seems and to rise its importance consequently. It is not a blocker but ... almost, for these reasons: 1) it happens much more frequently (for me 100% ratio) if you, after un install, _upgrade_ a LibO installation on a dual Office (Microsoft & LibreOffice) system. 2) it cause the damaging of the Microsoft Office installation that, for repairing, needs a total repair or reinstall of the Microsoft Office itself. This is a real BAD PUBLICITY for all users that tests LibreOffice. It is really a pain for the professional that have to do a dual installation whenever it wants to upgrade LibO and it is even worse for the home / casual user since it usually do not have the skill (or the disks) to repair / reinstall MSO causing that usually it will _never_ try LibO again considering it a dangerous product... 3) it is a longstanding bug that affect all the 3.4, 3.5 and 3.6 (still present in version 3.6.4 ...) series and it is simply time to have it fixed! ... I suggest to provide a patch (quick & dirty) and do not wait more for the mythical FAM being ready for production... Thank you! Perhaps I have an answer to the apparently strange and random behaviour I've observed. If I have installed Microsoft Office but, for some reason, I haven't used it _yet_ or not used yet with the user (I do not know which of the two actions is acting here) that I use for both Microsoft and Libre Office install, then the LibO installer/uninstaller do not see any MSO associations which are present as system but currently not as the current user, -or- not present yet and configured just by the first run of the current user (again I do not know which action it follows here), and take precendence. May be an explanation? If yes it could be without any real solution ... but we can find out just a "best way to do it" inserted in the i.e. FAQ or INSTALL or the manual or somewherelse that could be very useful for system administrators like me or for an help for massive installs help for i.e. P.A.s ... Something like: 1) Install MSO 2) _RUN_ it as administrator 3) _then_ install/unistall/upgrade LibO Comments? ** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) Thank you for your help! -- The LibreOffice QA Team |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.