Bug 74662 - Uninstall LibreOffice 4.2 leftovers
Summary: Uninstall LibreOffice 4.2 leftovers
Status: RESOLVED DUPLICATE of bug 67706
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Installation (show other bugs)
Version:
(earliest affected)
4.0.6.2 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-07 11:39 UTC by Pedro
Modified: 2015-01-23 11:10 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
PDF listing the leftover files after LO 4.2.0.4 uninstall under Windows XP (18.20 KB, application/pdf)
2014-02-07 11:41 UTC, Pedro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro 2014-02-07 11:39:42 UTC
After uninstalling LO 4.2.0.4 under Windows XP Pro x86 SP3 there are some items remaining

1) The "LibreOffice 4.2" program group (under %CommonStartMenu%) is not removed even if it's empty

2) The "LibreOffice 4" folder (under %ProgramFiles%) is not emptied and not removed.

A PDF listing the leftover files will be attached to the next comment (to avoid Bugzilla's bug)
Comment 1 Pedro 2014-02-07 11:41:24 UTC
Created attachment 93599 [details]
PDF listing the leftover files after LO 4.2.0.4 uninstall under Windows XP
Comment 2 Pedro 2014-02-07 16:01:23 UTC
After a new 4.2.0.4 install and un-install the python-core 3.3.0 folder isn't there. It was probably a leftover from a previous 4.x version.

This means that as python versions are updated some leftovers will remain. 

Wouldn't it make sense to remove these when an update with a newer version of python is installed?
Comment 3 Jean-Baptiste Faure 2014-02-12 05:56:03 UTC
Please do not set your own bug report to new. Each bug report must be confirmed independently.

Thank you for your understanding.

Best regards. jBF
Comment 4 Pedro 2014-02-12 06:33:59 UTC
(In reply to comment #3)
> Please do not set your own bug report to new. Each bug report must be
> confirmed independently.

I DID NOT SET THE REPORT TO NEW. THIS IS A BUG IN BUGZILLA. STOP TREATING EXPERIENCED TESTERS AS IRRESPONSIBLE KIDS!!!!
Comment 5 retired 2014-02-12 08:46:45 UTC
Pedro, can you stay friendly? JBF is a known QA team member and does awesome work. Volunteering in his free time to help triaging  bugs.

Besides that: he's perfectly right. Bugs arrive in unconfirmed state. The fact that some people use bugzilla (and not BSA) to report bugs results in bugs in the state "NEW". While LO does not want to kill bugreporting via bugzilla, since many devs use it that way, the correct state for a new bug is still UNCONFIRMED.

With that said, this is still unconfirmed. Please be nice, we are all investing our time, to improve LO because we like the concept of opensource software.
Comment 6 Pedro 2014-02-12 09:47:03 UTC
(In reply to comment #5)
> Pedro, can you stay friendly? JBF is a known QA team member and does awesome

I have been contributing to this project since the beginning (back in October 2010!) so spare me the lectures!

I OBVIOUSLY know that the status for new bugs is UNCONFIRMED.

If someone wants to ask me to stop submitting bugs through Bugzilla, that is fine. Telling me not to set my own bugs to NEW is at the least insulting!

I think as a regular contributor I deserve a little more consideration. Probably I'm wrong.
Comment 7 Pedro 2014-02-17 13:01:06 UTC
Additional information: just uninstalled version 4.0.6 and the Startup group is also not removed and the python 3.3.0 files are left behind.
Comment 8 Andras Timar 2014-03-13 15:56:16 UTC

*** This bug has been marked as a duplicate of bug 67706 ***