Bug 113390 - Changing the process name to libreoffice
Summary: Changing the process name to libreoffice
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
6.0.0.0.alpha0+
Hardware: All All
: medium trivial
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-23 22:45 UTC by Frank Brütting
Modified: 2017-11-08 19:42 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Frank Brütting 2017-10-23 22:45:19 UTC 
Description:
As this isn’t star office since a long time, please update the process name! :)

Steps to Reproduce:
.

Actual Results:  
.

Expected Results:
.


Reproducible: Always

User Profile Reset: No

Additional Info:


User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0
Comment 1 Buovjaga 2017-11-07 17:20:10 UTC 
What is your detailed proposal on achieving this?
I mentioned your report on #libreoffice-dev and got this response:
"quite possible that there are scripts out there that would break if "soffice.bin was" changed to "libreoffice" . and would it on Windows be "libreoffice.exe" and the wrapper executable still be called "soffice.exe" then? or would it be "libreoffice.exe" and "libreoffice.bin"?"
Comment 2 Frank Brütting 2017-11-08 01:38:31 UTC 
Well, the executable currently isn’t named correctly – so this is an obvious bug.

Scripts should be ported since they rely on a wrong application name – double-bugs still are bugs, there are no easier fixes than that being just changing one name. Relying on wrong stuff shouldn’t lead to let things stay wrong. O_o

For Win: I don’t have any idea about this, but I’d remove all soffice stuff entirely for things being done clean.
Comment 3 Buovjaga 2017-11-08 13:43:16 UTC 
Ok, bounced your comment to devs and they were not convinced. Backwards compatibility is more important than this renaming. Closing.
Comment 4 Frank Brütting 2017-11-08 19:42:10 UTC 
Thanks! But this is sad, as the upcoming mayor version update allows API breakage.