Created attachment 121494 [details] log of the WM when starting libreoffice passing it a file OS: Debian testing/strech LibreOffice version: 5.0.4.2 Tested component: LibreOffice Writer Window manager: i3wm for X11 [0] --- Hi all, trying to understand a strange behaviour in i3, i noticed from the window manager logs (attached) that calling libreoffice with a file as argument makes the application set multiple times, again and again, the class string to the same value ("libreoffice", "libreoffice-writer"), and not once on the window spawn as one would expect. I'm talking about something like 115 times for the 4 seconds the WM logging was active, so about 30 times per second. grep WM_CLASS libreoffice-file.log | wc -l 115 And it's reasonable to think that this would go on for the whole time the window stays open. On LO IRC channel i was asked to start soffice with SAL_USE_VCLPLUGIN=gen and SAL_USE_VCLPLUGIN=gtk, and since the result was the same they concluded that the affected code should be under vcl/unx/generic/. Anyway this doesn't happen when calling libreoffice with no file as argument. In this case the start center screen is showed and the class is set just one time to ("libreoffice", "libreoffice-startcenter") This was the main issue i was concerned about. Another issue is that before being set repeatedly to ("libreoffice", "libreoffice-writer") as described, the class is first set to ("libreoffice", "LibreOffice 5.0"), which the (linux) tools available to the user to extract informations from windows (e.g. xprop, xwininfo) can't even see, since this value is suddenly overwritten with by the mentioned repeated strings, which is the one that the user will see. As consequence, the user may fail to assign class-based criteria to its window manager. So is this first step required, or can it be skipped setting the class to the appropriate string directly? I hope i included as many details as i remember, sorry if i forgot something and tell me if i can provide more infos. Thanks. [0] https://i3wm.org/
Hello nfb, 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 Bug Submitter, 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-20171030
Dear Bug Submitter, 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-20171204