Step to reproduce : 1. Clear your preferences in order to make a fresh LibO install. 2. Open LibO 3.6.1 release (Version 3.6.1.2 (Build ID: e29a214) ) 3. Wait for it to finish launch. 4. Go to another application by clicking an icon in the dock 5. Try to return to LibO by clicking LibO icon in dock LibO window should be showed at foreground. Try to right click on this icon and "Force to quit" is shown insted of "Quit" (habitually, this mean that the system as detected that the process do not respond...) We can ever switch to LibO by using Alt+Tab or clicking directly in the window. After quit and relaunch LibO, it have a normal behavior.
This correct my previous post : Expected behaviour : LibO window should be showed at foreground. Current behavior : Nothing happen
Thank you very much for your bug report! REPRODUCIBLE with LibreOffice 3.6.1.2 (Build ID: e29a214), German langpack installed, on Mac OS X 10.6.8 (Intel). → Therefore adapted Summary field (removed version number). Also adapted Importance field: no offence, we just want to begin with sorting bugs by importance, and this is really a very minor issue, even if I agree that it can be rather irritating.
Well, I realize the reason for marking it as not so important from a programming point of view, but I must say this bug may have lost us a few users. I almost joined them. I downloaded LO, started it up, and instead of seeing a splash screen I see nothing. When I go to the icon in the dock it behaves as if the program is frozen and I was about to "force quit" it, before playing a bit more with it. I suggest that most casual "Let's try this free thing" users will dismiss LO as unusable right away, because of this bug.
Just by curiosity, is it better with LO 4.1.3?
Nope. And annoying as hell still.
** 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 (4.4.1 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-04-18
OS X 10.10.3 Version: 5.1.0.0.alpha1+ Build ID: fb6dd2a73074b9695bd8ddf7ba40f1819b03024e TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2015-06-17_23:34:12 Locale: de-DE (de.UTF-8) Since there is no specific commit fixing this issue, setting to WORKSFORME. FIXED is used only when a commit exists. Feel free to reopen this issue if you still can reproduce this particular problem or if I missed something peculiar.