Bug 153545 - Draw: a locked layer can be pasted into
Summary: Draw: a locked layer can be pasted into
Status: RESOLVED DUPLICATE of bug 107384
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Draw (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) macOS (All)
: medium normal
Assignee: Not Assigned
Depends on:
Reported: 2023-02-11 13:32 UTC by birnbach@posteo.de
Modified: 2023-02-11 16:04 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description birnbach@posteo.de 2023-02-11 13:32:42 UTC
A document has multiple layers, one of which is locked such as to prevent changes on it. If this layer is selected as the one to add new elements into, plain drawing will be prevented. However, pasting an element from the clipboard works. The added element will then be protected against manipulation (like deleting).

Steps to Reproduce:
1. create a drawing document 
2. draw a shape, e.g. a rectangle
3. cut the shape to the clipboard (CTRL-X) 
   or copy it (CTRL-C) and move the original a bit away
4. add extra layer "mylayer"
5. lock 'mylayer' by double-clicking and checking 'locked' in the dialog. 
   'mylayer' will be selected as the one to work in
6. paste (CTRL-V) the shape from the clipboard into the locked layer

Actual Results:
The shape appears on locked layer 'mylayer'

Expected Results:
Pasting the shape is prevented

Reproducible: Always

User Profile Reset: Yes

Additional Info:
Version: / LibreOffice Community
Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f
CPU threads: 6; OS: Mac OS X 10.15.7; UI render: default; VCL: osx
Locale: de-DE (de_DE.UTF-8); UI: de-DE
Calc: threaded
Comment 1 Regina Henschel 2023-02-11 16:04:01 UTC
As described. Tested with Version: (X86_64) / LibreOffice Community
Build ID: 9d44236a62bf59d120dda89924d0d1407b2bd52b
CPU threads: 8; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded

The problem is already known, see bug 107384.

*** This bug has been marked as a duplicate of bug 107384 ***