Bug 156056 - Assertion failure when double-clicking <footer> element in master slide (debug build)
Summary: Assertion failure when double-clicking <footer> element in master slide (debu...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Master-Slide-View Crash-Assert
  Show dependency treegraph
 
Reported: 2023-06-26 01:55 UTC by Aron Budea
Modified: 2023-06-28 12:53 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Backtrace (13.08 KB, text/plain)
2023-06-26 01:55 UTC, Aron Budea
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Aron Budea 2023-06-26 01:55:34 UTC
Created attachment 188085 [details]
Backtrace

This can only be reproduced in a debug build.

- Start an empty presentation,
- Switch to master view eg. using Master View button on Properties sidebar,
- In Footer Area, click at the beginning of the <footer> place holder.

=> Crash (assertion failure) with the following:

xmloff/source/core/namespacemap.cxx:253: rtl::OUString SvXMLNamespaceMap::GetQNameByKey(sal_uInt16, const rtl::OUString&, bool) const: Assertion `false' failed
Comment 1 Julien Nabet 2023-06-26 07:55:34 UTC
On pc Debian x86-64 with master sources updated today, I could reproduce this with same bt as Aron's one.

Noel: thought you might be interested in this one.
Comment 2 Julien Nabet 2023-06-26 08:06:40 UTC
Interestingly, I got the same for date area (at bottom left) but not for Slide number area (at bottom right)
Comment 3 Julien Nabet 2023-06-26 08:17:07 UTC
The 2 which crash are defined on XML_NAMESPACE_PRESENTATION, the one which doesn't crash is on XML_NAMESPACE_TEXT
Comment 4 Noel Grandin 2023-06-28 11:10:40 UTC
Now why does this not trigger in my build?
Comment 5 Julien Nabet 2023-06-28 12:53:28 UTC
(In reply to Noel Grandin from comment #4)
> Now why does this not trigger in my build?

Argh, weird indeed, I still reproduce this with master sources updated today (with gtk3 or gen rendering)