Description: Main LO window closes with some LO application Steps to Reproduce: 1. Start $ libreofficedev6.4 or $ soffice --> Main LO window opens 2. Open some document, for example, .odt 3. Close .odt from 2 Actual Results: .odt closes and main LO window closes too Expected Results: Do not close main LO window Reproducible: Always User Profile Reset: No Additional Info: Reproduced for 6.4.0.0 and older Version: 6.4.0.0.alpha0+ Build ID: 1496a1831d1be0a2d24be9fe3ecf627b2664e938 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kf5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2019-09-04_14:52:26 Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US Calc: threaded
Thank you reporting the problem, cannot be reproduce in Version: 7.0.0.0.alpha0+ Build ID: 4ff12ba6f4639c73587f2bb58afcc3ca6fb30105 CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kf5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-01-24_21:09:14 Locale: id-ID (id_ID.UTF-8); UI-Language: en-US Calc: threaded
Vera: can you still see it with the stable 6.4?
(In reply to Buovjaga from comment #2) > Vera: can you still see it with the stable 6.4? Hello. I've tried Version: 6.4.5.0.0+ Build ID: f7fb6d11e185bf5c462457d6d977fba308cea414 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5; TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:libreoffice-6-4, Time: 2020-05-11_19:52:44 Locale: ru-RU (ru_RU.UTF-8); UI-Language: en-US Calc: threaded Bug is still reproducible. (In reply to Stanislaus J. Pinasthika from comment #1) > Thank you reporting the problem, cannot be reproduce in > Version: 7.0.0.0.alpha0+ > Build ID: 4ff12ba6f4639c73587f2bb58afcc3ca6fb30105 > CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: kf5; > TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: > 2020-01-24_21:09:14 > Locale: id-ID (id_ID.UTF-8); UI-Language: en-US > Calc: threaded Unfortunately, I can. 1) $ libreoffiedev7.0 2) Open some odt 2) Close odt --> main LO widow closes Version: 7.0.0.0.alpha1+ Build ID: 572c9db0440d9aba4945fb1761ec7f83e717c2f0 CPU threads: 4; OS: Linux 5.4; UI render: default; VCL: kf5; Locale: ru-RU (ru_RU.UTF-8); UI: en-US TinderBox: Linux-rpm_deb-x86_64@86-TDF, Branch:master, Time: 2020-05-11_09:34:08 Calc: threaded
I can't reproduce it myself. Arch Linux 64-bit Version: 7.0.0.0.alpha1+ Build ID: e84d6f512fceb8b354b2d111193a9fd7d834acc5 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: en-US (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 11 May 2020
Hello Vera, Do you reproduce this issue with SAL_USE_VCLPLUGIN=gen ?
Dear Vera Blagoveschenskaya, 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
Dear Vera Blagoveschenskaya, 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-FollowUp