Created attachment 177187 [details] the spreadsheet causing isues I want to copy the content of cell B70 in the attached spreadsheet, and got the info-popup that the content of a protected cell can not be altered. So far, so good, but the pop-up cant be confirmed/removed! It blocks the complete desktop, I cant even click with the mouse into a different window/process. Only chance is alt-tab to an open console window and kill the process from there. Version: 7.2.5.1 / LibreOffice Community Build ID: 20(Build:1) CPU threads: 12; OS: Linux 5.15; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded Operating System: openSUSE Tumbleweed 20211224 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.2 Kernel Version: 5.15.8-1-default (64-bit) Graphics Platform: X11 Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz Memory: 15.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630
I couldn't reproduce with kf5 or gtk3: Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded or Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded In both cases I was able to try to modify cell B70, the message popped up, and I could press "OK" to make it disappear. On Ubuntu 18.04 with Budgie desktop environment. Could you please try in safe mode, Axel? Just to rule out issues related to the user profile. Can you also please confirm that the issue appears when you try to modify the cell, not when you "copy the contents" as you stated?
(In reply to stragu from comment #1) > Could you please try in safe mode, Axel? Just to rule out issues related to > the user profile. I tried in safe mode, same result, Switching from X11 to Wayland, the issue disappeared > Can you also please confirm that the issue appears when you try to modify > the cell, not when you "copy the contents" as you stated? It happened as soon as I clicked the entry line (below the menu) - without taking further action.
I found the following log entry in the wayland session: qt.qpa.wayland: setGrabPopup called with a parent, QtWaylandClient::QWaylandXdgSurface(0x558bb46920e0) which does not match the current topmost grabbing popup, QtWaylandClient::QWaylandXdgSurface(0x558bb49c0450) According to the xdg-shell protocol, this is not allowed. The wayland QPA plugin is currently handling it by setting the parent to the topmost grabbing popup. Note, however, that this may cause positioning errors and popups closing unxpectedly because xdg-shell mandate that child popups close before parents Maybe that is the issue (handled different in X11?)?
Ah, very interesting, I could reproduce now with the kf5 VCL, following these steps: 1. Open attachment 177187 [details] 2. Click on cell B70 3. Click in the input line / formula bar Result: The "Protected cells can not be modified" dialog pops up, but nothing responds to clicks, it is impossible to close it with the mouse. Trying to use other applications in other windows "jumps" you back to the LibreOffice window. However, I could press Enter on the keyboard to close the dialog (it is equivalent to pressing the "OK" button). Even after closing it by pressing the Enter key, I witness an annoying "jump" back to the LibreOffice window when using a different application. Note that you do not get the same response when trying to modify the cell in other ways, for example: - trying to paste something onto cell B70; - trying to remove the contents of cell B70 with the backspace key. In both cases, the dialog is responsive. Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 8; OS: Linux 5.4; UI render: default; VCL: kf5 (cairo+xcb) Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded
7.4.0.3 community version is still affected by this bug. Indeed pressing ENTER works around the issue (as it is another way to choose "OK").