I'm using unoconv 0.4 and if I access a document with unoconv Writer is on the next start not maximized anymore. Steps to reproduce: 1. Open Writer and maximize the window. 2. Save the empty document to /tmp/test.odf and close Writer. 3. Access the document with "unoconv /tmp/test.odf". 4. Open Writer. 5. Writer is now not maximized anymore.
There is a little typo: The filename must be /tmp/test.odt and not /tmp/test.odf.
This issue was first reported on the unoconv issue-tracker, but was forwarded to the LibreOffice community.
Sorry, can not understand. After using unoconv, Writer forgets that should be maximized initially or impossible to maximize it?
I just tested this myself, and I cannot reproduce this with LibreOffice 3.4.5 or LibreOffice 3.5.0. I can however reproduce this with OpenOffice 3.2.1, where without running unoconv the file would open maximized, but after running unoconv (default actions is to convert to PDF) the file would open in a smaller (default) window. And this happens even without reopening the same file, so using the UNO bindings apparently resets the global window state. Maybe LibreOffice used to have this bug as well ? With LibO 3.4.5 and LibO 3.5.0, the window size would not be affected by the file, or unoconv calls (UNO bindings) and would persist even when restarting Writer subsequently with no actions. While OpenOffice 3.2.1 would always fall back to the default windows size/location.
Thanks for information and additional testing. So, problem fixed in last versions?
In the newest trunk of unoconv and LibreOffice 3.5.0 Beta 2 the bug still exists. LibreOffice will not be maximized anymore if I used unoconv for a document (means the LibreOffice window is using only ~99% of the window instead of a native maximized window).
my be problem is in unoconv? I issued this on console: [s@t2 program]$ unoconv --version and output of this command is: unoconv 0.4svn Written by Dag Wieers <dag@wieers.com> Homepage at http://dag.wieers.com/home-made/unoconv/ platform posix/linux2 python 2.7.1 (r271:86832, Apr 12 2011, 16:15:16) [GCC 4.6.0 20110331 (Red Hat 4.6.0-2)] build revision $Rev$ I can not reproduce this problem, my be we have different versions?
sworddragon@ubuntu:~/data/dagwieers-unoconv-70c897d$ unoconv --version unoconv 0.4 Written by Dag Wieers <dag@wieers.com> Homepage at http://dag.wieers.com/home-made/unoconv/ platform posix/linux2 python 2.7.2+ (default, Feb 16 2012, 18:47:58) [GCC 4.6.2] build revision $Rev$
Oops, I called the system version and not the one in the directory (but the bug appears in both versions). sworddragon@ubuntu:~/data/dagwieers-unoconv-70c897d$ ./unoconv --version unoconv 0.5 Written by Dag Wieers <dag@wieers.com> Homepage at http://dag.wieers.com/home-made/unoconv/ platform posix/linux2 python 2.7.2+ (default, Feb 16 2012, 18:47:58) [GCC 4.6.2] LibreOffice 3.5 build revision $Rev$
And if installed several versions of LibreOffice, this reproducible with all versions?
unoconv does not do anything that would/should affect the configuration of the window size. In fact we simply open a file, and save it using a different export filter (with potentially custom filter options) using UNO. That is why I requested to have this issue opened with the LibreOffice project.
> And if installed several versions of LibreOffice, this reproducible with all versions? LibreOffice 3.4.4 is affected too.
Why test with 3.4.4 when 3.4.5 is out and I cannot reproduce it on 3.4.5 ? Could you please test with 3.4.5 and 3.5.0 just to make sure that it's not already (unintentionally) fixed.
> Why test with 3.4.4 when 3.4.5 is out and I cannot reproduce it on 3.4.5 ? Because LibreOffice 3.4.4 is in the Ubuntu repository. I have tested this now with the final version of LibreOffice 3.5.0 and the bug still exists (all LibreOffice versions were from the Ubuntu repository). After this I have tested this with LibreOffice 3.4.5 (from the official site) and I can't reproduce the bug. This gives me the impression that this bug happens only with the packages from the Ubuntu repository. I wanted to try this with LibreOffice 3.5.0 from the official site but the latest trunk from unoconv can't convert the document with this version.
Ok, sorry for that. From the previous reports it was unclear what versions were tested. I can confirm that in my case the LibO versions 3.4.5 and 3.5.0 were indeed the upstream RPM packages, and not the ones that come with the distribution.
so, bug reproducible in 3.4.5 and 3.5.0 both from repository and from libreoffice.org?
Current state: Ubuntu LibreOffice 3.4.4: Reproduceable Ubuntu LibreOffice 3.5.0: Reproduceable Upstream LibreOffice 3.4.5: Not reproduceable Upstream LibreOffice 3.5.0: Can't be tested because of this: https://github.com/dagwieers/unoconv/issues/43
Thanks for additional testing @ Bjoern Please, take look at this bug. It looks like Ubuntu specific bug.
PLease first confirm this to be an issue with 3.5.0 upstream, as a lot of vendor-specific stuff was removed between 3.4 and 3.5 in Debian/Ubuntu (actually we started from scratch with much fewer vendor patches in 3.5).
This information depends on this issue: https://github.com/dagwieers/unoconv/issues/43 But it seems bugzilla doesn't support dependencies to external sites.
You can add bugs to Google code, Launchpad and Debian. Not to Github, Red Hat or anything else, a pity :-/
I have tested this now with the newest trunk of unoconv and the final release of LibreOffice 3.5.0 (I have deleted ~/.config/libreoffice before) and the bug still exists.
NOT reproducible anymore: Tested with Libo 4.2.4.2 and unoconv 0.6
I'm still able to reproduce the problem with LibreOffice 4.2.4 and unoconv 0.6.
Bodhi Linux x64 (built on Ubuntu 12.04) LibreOffice 4.1.6.2 Unoconv 0.4 Setting as: New (confirmed) Trivial - really almost no impact on anything Lowest - you can tell that this is really affecting almost no one by the fact that there are no other users reporting the same issue in years.
** 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 (5.0.0.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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2015-09-03
With LibreOffice 5.0.1.2 on Linux 4.1.3 I'm still seeing this issue.
** 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 (5.1.5 or 5.2.1 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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20160920
Dear sworddragon2, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear sworddragon2, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug