Description: EDITING In LibreOffice Calc when I get into a deleting dialogue, e.g. when deleting a single cell or a selection of unsequential columns with ctrl -, my keyboard stops working. To get it back I need to defocus the LibreoOffice Calc window and then refocus it back. This also happens when opening the About in Help. Not much of a hassle (once I figured out how to get it back) but should be fixed. Installation details: Version: 6.2.2.2 Build ID: 6.2.2-2 CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: kde5; running on Manjaro based on Arch. Steps to Reproduce: 1. click on a cell in Calc 2. press ctrl - to open delete cell dialogue 3. press Ok Actual Results: Calc is refocused but keyboard stops working. To get it back I need to defocus the Calc window and then refocus it back. Expected Results: Calc is refocused and keyboard should work. Reproducible: Sometimes User Profile Reset: No OpenGL enabled: Yes Additional Info: Version: 6.2.2.2 Build ID: 6.2.2-4 CPU threads: 8; OS: Linux 4.19; UI render: default; VCL: kde5; Locale: en-US (mk_MK.UTF-8); UI-Language: en-US Calc: threaded
no repro with ver: Version: 6.3.0.0.alpha0+ (x64) Build ID: 35d9a2618dc0116378ab795a7b9277d248c5afd4 CPU threads: 8; OS: Windows 6.1; UI render: default; VCL: win; TinderBox: Win-x86_64@42, Branch:master, Time: 2019-04-05_04:55:04 Locale: de-DE (de_DE); UI-Language: en-US Calc: *unthreaded* *threaded* not tested, above ver. is known buggy in threaded, all subsequent known for crashing, reg. b.
You were running the kde5 backend with early 6.2.x versions, where it had still some nasty bugs. Please tell us how it behaves now with an up-to-date version Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Dear Branko, 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 Branko, 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
Hi guys, Sorry for keeping you waiting - the bug is indeed resolved with the new version. There are some new issues I will report in a separate comment. It would be much easier to report and discuss bugs if you moved to GitHub and GitLab, please consider it in the future. Thanks, Branko (In reply to QA Administrators from comment #4) > Dear Branko, > > 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
(In reply to Branko from comment #5) > Hi guys, > > Sorry for keeping you waiting - the bug is indeed resolved with the new > version. > There are some new issues I will report in a separate comment. > It would be much easier to report and discuss bugs if you moved to GitHub > and GitLab, please consider it in the future. From my experience it would not be easier. I am curious how exactly do you consider it would be easier.
(In reply to Buovjaga from comment #6) > (In reply to Branko from comment #5) > > Hi guys, > > > > Sorry for keeping you waiting - the bug is indeed resolved with the new > > version. > > There are some new issues I will report in a separate comment. > > It would be much easier to report and discuss bugs if you moved to GitHub > > and GitLab, please consider it in the future. > > From my experience it would not be easier. I am curious how exactly do you > consider it would be easier. Let me say that I don't want to diss the setup you have running. On my side, I'm not used to using bugzilla. On the other hand, I've discussed some issues for free software tools hosted on GitHub and I found the experience very smooth, e.g. https://github.com/spyder-ide/spyder/issues Here are some points I find better off of the top of my head: - comment writing is much cleaner: - there's no quotation of the comment you are replying to in the start of the text you're entering (like when I'm writing this) - markdown is supported and allows inserting `code`, and images as printscreens, as well as nested lists (like this one), - you can +1 other comments or use emojis - no need to log-in to bugzilla, or a project based webservice - I'm always logged in on GitHub/GitLab so I don't have to remmember/reset my password like I did today : ) - searching for issues allows for tags I'm not sure if bugzilla offers any of these, but again people are more or less used to working on GitHub/GitLab, and having a different forum for different projects get's time to get accustomed to. This ultimately hurts issues reporting and the project. Maybe this discussion should be in a different thread? : )
(In reply to Branko from comment #7) > (In reply to Buovjaga from comment #6) > > (In reply to Branko from comment #5) > > > Hi guys, > > > > > > Sorry for keeping you waiting - the bug is indeed resolved with the new > > > version. > > > There are some new issues I will report in a separate comment. > > > It would be much easier to report and discuss bugs if you moved to GitHub > > > and GitLab, please consider it in the future. > > > > From my experience it would not be easier. I am curious how exactly do you > > consider it would be easier. > > Let me say that I don't want to diss the setup you have running. On my side, > I'm not used to using bugzilla. On the other hand, I've discussed some > issues for free software tools hosted on GitHub and I found the experience > very smooth, e.g. https://github.com/spyder-ide/spyder/issues > > Here are some points I find better off of the top of my head: > - comment writing is much cleaner: > - there's no quotation of the comment you are replying to in the start of > the text you're entering (like when I'm writing this) I don't get this: you don't have to quote in Bugzilla if you don't want to. Likewise, you *can* quote in GitHub, if you want to by clicking the "meatballs" element in the top right corner of a message. > - markdown is supported and allows inserting `code`, and images as > printscreens, as well as nested lists (like this one), The next version of Bugzilla (already live at https://bugzilla.mozilla.org ) has markdown support. Inline images will also be supported through an extension. > - you can +1 other comments or use emojis Emojis work in the nextgen Bugzilla. +1/reactions don't provide any value. If someone leaves such a comment now, we hide it with a tag like me-too or no-value. Discussion in a Bugzilla upstream ticket seems to be along the same lines: https://bugzilla.mozilla.org/show_bug.cgi?id=1421401 "I'd like us to get away from voting because it implies that design decisions are up for popular vote." > - no need to log-in to bugzilla, or a project based webservice - I'm always > logged in on GitHub/GitLab so I don't have to remmember/reset my password > like I did today : ) We would never use a hosted service like Github in any case. In theory, it would be a self-hosted GitLab, but your existing gitlab.com account would be useless. Popular hosted services have the advantage of a smooth authentication experience, but a monoculture has many disadvantages. The next version of Bugzilla will support our single sign-on service, so we will have a rather good coverage across all TDF web applications. You can log into the wiki, gerrit code review etc. all with a single account. > - searching for issues allows for tags The search of GitHub/-Lab is inferior compared to Bugzilla. "Tags" in Bugzilla are called keywords. There is also the whiteboard field for completely freeform metadata. Bugzilla's advanced search interface provides a very finegrained way to filter reports. This is absolutely crucial for quality assurance. We also make extensive use of the Bugzilla API to provide automated reports etc. > I'm not sure if bugzilla offers any of these, but again people are more or > less used to working on GitHub/GitLab, and having a different forum for > different projects get's time to get accustomed to. This ultimately hurts > issues reporting and the project. This is again about the advantages and disadvantages of a monoculture.