https://bugs.documentfoundation.org/show_bug.cgi?id=166647

            Bug ID: 166647
           Summary: Hand-written Ink objects ("mouse as pen") are doubled
                    each time a presentation is started or modified,
                    depending on version
           Product: LibreOffice
           Version: 24.2.7.2 release
          Hardware: x86-64 (AMD64)
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Impress
          Assignee: [email protected]
          Reporter: [email protected]

Description:
In some circumstances, Impress duplicates "Ink-Notes" (using "mouse as pen"
drawn while presenting) by a factor of 2 each time I start the presentation or
add another mouse-as-pen drawing.

In short: when I start the presentation and draw a circle, then stop it,
there's one red circle. Then I start and stop again (caveat: depends on the
"version", see below), there's two circles (exactly overlain on each other).
Start-Stop again makes it 4. Do that 10 times and we end up with >1000 copies
already, making LO unresponsive.

Steps to Reproduce:
Depending on factors I have not yet understood (see
https://bugs.documentfoundation.org/show_bug.cgi?id=112687#c20), the Ink is
either stored as a single polyline (possibility #1) or as a set of individual
lines and polygons (possibility #2, old behavior). This is something different
of course, but I found it to be related.

Depending on how the "ink" is stored/represented, I found two ways of
reproducing the behavior of duplicated "mouse-as-pen" drawings:
#1 (ink is a single polyline): start the presentation (no need to draw
anything, but it's the same if you do) and stop again.
All _previous_ drawings (mouse-as-pen-made) are duplicated.

#2 (ink is a set of lines and polygons): start the presentation, but this time
_you need to draw something_. Stop again: 
All _previous_ drawings (mouse-as-pen-made) are duplicated.

Actual Results:
My guess: all previous objects get duplicated once drawing has started. When
that happens, somehow depends on the hardware !?

I currently don't have to many different LO versions at hand to test, but
here's a few (testing results first, refs relate to versions in the "Other
Information" section):

[1a]: follows #2 (individual lines), duplicates when drawing new lines
[1b]: different machine: follows #1 (one polyline), duplicates when starting
the presentation
[1c]: Windows (VM), follows #1
[2]: follows #2
[3]: follows #1

So I don't see any pattern here with versions, rather than how the input might
be processed:
[1b, 1c, 3]: Laptop with Touchscreen and Pen (though drawings done with a
Mouse) and a VM (emulated USB Tablet)
[1a, 2]: Mouse only

Expected Results:
No duplication of drawings made using "mouse-as-pen" feature.


Reproducible: Always


User Profile Reset: Yes

Additional Info:
[1a]
Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Flatpak
Calc: threaded

[1b]
Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Flatpak
Calc: threaded

[1c] Version: 25.2.3.2 (X86_64) / LibreOffice Community
Build ID: bbb074479178df812d175f709636b368952c2ce3
CPU threads: 4; OS: Windows 11 X86_64 (10.0 build 26100); UI render:
Skia/Raster; VCL: win
Locale: de-DE (de_DE); UI: de-DE
Calc: threaded

[2]
Version: 25.2.2.2 (X86_64) / LibreOffice Community
Build ID: 7370d4be9e3cf6031a51beef54ff3bda878e3fac
CPU threads: 12; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded

[3]
Version: 24.2.7.2 (X86_64) / LibreOffice Community
Build ID: 420(Build:2)
CPU threads: 8; OS: Linux 6.8; UI render: default; VCL: gtk3
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Ubuntu package version: 4:24.2.7-0ubuntu0.24.04.4
Calc: threaded

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to