https://bugs.documentfoundation.org/show_bug.cgi?id=161256
Michael Weghorn <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #5 from Michael Weghorn <[email protected]> --- (In reply to Julien Nabet from comment #4) > Michael: I don't know if you're working on gtk4 ... Not actively. (I started working on gtk4 a11y, but this is currently paused, mainly due to lack of upstream GTK 4 API, see https://lists.freedesktop.org/archives/libreoffice/2024-March/091665.html ). > ... but I noticed accessibility > part in Buovjaga's bt, thought you might be interested. That backtrace shows an assert in a11y code, which is only relevant in debug builds. (I've occasionally seen that with gtk4 as well when actually working on a11y, i.e. when Accerciser or Orca were running, but not without them active. The underlying issue is somewhere else and would need further investigation.) In any case, that shouldn't be any problem with release builds. @Reporter: Does this still happen with a current development version of LO? If so, can you please get + attach a backtrace? @Buovjaga: Is that backtrace for the specific scenario/steps described in the initial description? Do you have any AT running? Does commenting the assert make things work as expected? Note that the gtk4 VCL plugin is currently experimental, and therefore it's not used anywhere by default. -> Reducing severity to "normal" again for now. -- You are receiving this mail because: You are the assignee for the bug.
