Description: Hi The name of LibreOffice within the menu bar of Ubuntu's Unity 7 Desktop is "Unknown Application Name" since quite a while. Regards, Atalanttore Steps to Reproduce: 1. Open LibreOffice on Ubuntu with Unity 7 Desktop. 2. Check the name within the menu bar. Actual Results: LibreOffice is called "Unknown Application Name". Expected Results: The name "LibreOffice". Reproducible: Always User Profile Reset: No Additional Info:
Created attachment 144249 [details] Screenshot showing the problem.
Sorry, without confirming or looking I'll close as NotOutBug. Please report to Ubuntu. If you diagree and consider this LO bug please explain why.
Reported to Ubuntu: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1787642
Based on this comment, the bug is in LO: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1589215/comments/23 Could this be fixed? A more precise issue:
I can confirm this issue on Ubuntu with Unity 7. You can fix it manually by adding ‘env XDG_CURRENT_DESKTOP=Unity’ to every 'Exec=' line in the .desktop files, so it's probably a LO issue. There is also a discussion in the Unity Development thread on community.ubuntu.com: https://discourse.ubuntu.com/t/testing-unity-session-in-18-04/987/257 See also Khurshids comment here: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1589215/comments/25
Created attachment 144820 [details] LibreOffice under Unity 7 with fixed menu Here is a screenshot of LO 6.0.6.2 under Ubuntu 18.04 with Unity 7 and the applied 'env XDG_CURRENT_DESKTOP=Unity' workaround. As you can see, the 'Unknown Application Name' is gone and the Gnome App Menu also don't get loaded under Unity as it should be.
Searching in the internet, I found the XDG_CURRENT_DESKTOP has changed from Unity to Unity:Unity7:ubuntu. I'm wordering if https://gerrit.libreoffice.org/#/c/60489/ would fix it... Anyone with Unity7 could try it ?
(In reply to Xisco Faulí from comment #7) > Anyone with Unity7 could try it ? I can test it, if you tell me how.
Let's close this as a dupe of bug 119881, which is the way to fix this, by iterating over the colons... *** This bug has been marked as a duplicate of bug 119881 ***