Summary: | in Impress slides pane selecting a slide doesn't show it on every second click, instead runs different actions on it, occasionally even deleting it | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Simon Sievers <chip53> |
Component: | Impress | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | ilmari.lauhakangas, parchd+documentfoundation |
Priority: | medium | ||
Version: | 5.1.6.2 release | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 102283 |
Description
Simon Sievers
2016-11-04 16:49:01 UTC
The issue occurs when clicking different slides quite fast. How fast depends on the window manager used as it seems. Using awesome window manager and spectrwm reproduces the bug best as far as I know. In i3 the bug appears almost never. So far I have only been reproducing it on Archlinux. I am not sure about MS-Windows for now... It's a major bug in my opinion. It renders LO impress useless! Silently losing slides is a catastrophy! Can reproduce on Arch using openbox as window manager, but not with the same frequency as the original bug report. I believe it is actually a drag event rather than a click event causing the problem. Reproducing requires very fast clicking between slides (or even on a single slide with a slight drag motion). (In reply to parchd from comment #2) > Can reproduce on Arch using openbox as window manager, but not with the same > frequency as the original bug report. I believe it is actually a drag event > rather than a click event causing the problem. Reproducing requires very > fast clicking between slides (or even on a single slide with a slight drag > motion). I have discussed this same problem before: bug 91908 The last comment has: "After some tests I have to conclude that this is due to input devices (touchpad and mouse with kind of contact bounce)." Simon, parchd: could this be related to your input devices? I used xf86-input-synaptics. Tried switching to xf86-input-libinput with "pacman -S xf86-input-libinput" which automatically deinstalls xf86-input-synaptics and then restarted X. Problem persists. Here is some xinput output: xinput --list ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9 [slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=12 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ↳ Power Button id=6 [slave keyboard (3)] ↳ Video Bus id=7 [slave keyboard (3)] ↳ Power Button id=8 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=11 [slave keyboard (3)] ↳ Logitech USB Receiver id=13 [slave keyboard (3)] I notice there are two Logitech USB Receiver. Disabling id=9 makes the mouse not work anymore, disabling id=10 has no effect. I notice the same problem with libreoffice impress using my touchpad, no matter wether using synaptics or libinput driver. I notice "xinput --disable 12" makes the problem disappear. id=12 is my touchpad as you can see from the xinput output. Then, turning back on the touchpad with "xinput --enable 12" both the mouse and the touchpad don't show the problem. Maybe something goes wrong at boottime initializing the touchpad. Haven't tested the disable / enable workaround with synaptics input driver. Terminating libreoffice and restarting it again the problem was there again. The disable / enable didn't solve it then. Seems to have been coincidence it ever did. Tried one more USB mouse with a cable, same problem persists. So a hardware failure would be really unlikely. Wanted to add this, just to be sure. I used xinput --test to view the events the mouse clicks cause in libreoffice window. It shows there is always just the correct event, like button press and button release one time each, even though delete gets caused. In addition to the previous test all this leads me to the conclusion that the input device and input device drivers wouldn't be the culprit. Any further help and suggestions greatly appreciated. Still I am not at all sure what the cause for the misbehaviour is and it might very well not be libreoffice. Let's set to NEW as we have two people experiencing this and it doesn't seem to be related to input devices. Tested with different libreoffice backends by uncommenting lines in /etc/profile.d/libreoffice-still.sh, but problem persists. Tested kde4 and gtk with libreoffice-still. Tested again today with latest archlinux and libreoffice-fresh 5.4.3-3 and the problem still persists. ** 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 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 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: 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 Cannot reproduce the issue, in: Version: 6.1.4.2 Build ID: 6.1.4-4 CPU threads: 4; OS: Linux 4.20; UI render: default; VCL: gtk3; Locale: it-IT (en_GB.UTF-8); Calc: group threaded Dear Simon Sievers, 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 Simon Sievers, 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 |