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

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |stephane.guillou@libreoffic
                   |                            |e.org
                URL|                            |https://ask.libreoffice.org
                   |                            |/t/impress-slide-content-no
                   |                            |t-shown-on-notes-page/4172

--- Comment #11 from Stéphane Guillou (stragu) 
<[email protected]> ---
Repro in recent trunk build with first attachment 107396:

Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 92e5898fa9ffa4dd8742f5f26e790563feef286e
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded

...however, steps to reproduce from scratch would be welcome, because the
element showing the slide contents is absent and could have been inadvertently
deleted by the user.

(In reply to nodatalog from comment #3)
> http://ask.libreoffice.org/en/question/18353/impress-slide-content-not-shown-
> on-notes-page/
The workaround of clicking on the layout in the sidebar does work for me for
attachment 107396, it restores the slide contents on the notes page.

(In reply to nodatalog from comment #3)
> Created attachment 110907 [details]
> Multiple master slides in notes view
I think this should be considered a different issue: this is misplaced content,
not missing slide contents. And again, steps to reproduce are needed. If I move
the object back to where it should be, it stays there after a save and reload
(in both LO 4.0.0.3 and the trunk build above).

Now that Impress can show the Notes View page contents in the Navigator (since
LO 7.5, for bug 155393), it's easier to investigate the different issues.

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

Reply via email to