Package: xmlcopyeditor
Version: 1.2.1.3-4.3
Severity: serious
Justification: makes the package in question unusable or mostly so
X-Debbugs-Cc: s...@techie.net
Since the update to use wxwidgets3.2, xmlcopyeditor pops up "An
assertion failed!" dialogs on startup, with similar messages on
stderr:
$ xmlcopyeditor
./src/common/sizer.cpp(2258): assert "CheckSizerFlags(!((flags) &
(wxALIGN_CENTRE_VERTICAL)))" failed in DoInsert(): wxALIGN_CENTRE_VERTICAL will
be ignored in this sizer: only horizontal alignment flags can be used in
vertical sizers
DO NOT PANIC !!
If you're an end user running a program not developed by you, please ignore
this message, it is harmless, and please try reporting the problem to the
program developers.
You may also set WXSUPPRESS_SIZER_FLAGS_CHECK environment variable to
suppress all such checks when running this program.
If you're the developer, simply remove this flag from your code to avoid
getting this message. You can also call
wxSizerFlags::DisableConsistencyChecks() to globally disable all such checks,
but this is strongly not recommended.
This is because wx3.2 added consistency checks to sizer flag use and
moans when there are flags which don't make sense (which previously
were quietly ignored).
There seem to be two assertions that fail.
This fixes one of them:
diff -ru ../xmlcopyeditor-1.2.1.3/src/commandpanel.cpp
xmlcopyeditor-1.2.1.3/src/commandpanel.cpp
--- ../xmlcopyeditor-1.2.1.3/src/commandpanel.cpp 2014-09-06
13:54:53.000000000 +1200
+++ xmlcopyeditor-1.2.1.3/src/commandpanel.cpp 2022-09-21 16:23:36.927423010
+1200
@@ -135,7 +135,7 @@
bottomSizer->Add ( outputSizer, 0, wxLEFT | wxRIGHT |
wxALIGN_CENTER_VERTICAL, sizerOffset );
mainSizer = new wxBoxSizer ( wxVERTICAL );
- mainSizer->Add ( commandEdit, 0, wxLEFT | wxRIGHT |
wxALIGN_CENTER_VERTICAL | wxEXPAND, sizerOffset );
+ mainSizer->Add ( commandEdit, 0, wxLEFT | wxRIGHT | wxEXPAND,
sizerOffset );
mainSizer->Add ( bottomSizer );
I didn't locate the other one from a quick look (the backtrace in the dialog
doesn't show any locations in xmlcopyeditor's code, even with the dbgsym
installed).
It's possible there are further problems if any sizers are built on demand
rather than at startup - I did a quick run through the menus and didn't hit
any, but I'm not an active user of this app.
Cheers,
Olly
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.16.0-4-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_NZ.UTF-8, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8),
LANGUAGE=en_NZ:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages xmlcopyeditor depends on:
ii libaspell15 0.60.8-4+b1
ii libc6 2.34-8
ii libexpat1 2.4.8-2
ii libgcc-s1 12.2.0-3
ii libpcre3 2:8.39-14
ii libstdc++6 12.2.0-3
ii libwxbase3.2-0 3.2.1+dfsg-1
ii libwxgtk3.2-0 3.2.1+dfsg-1
ii libxerces-c3.2 3.2.3+debian-3+b1
ii libxml2 2.9.14+dfsg-1+b1
ii libxslt1.1 1.1.35-1
xmlcopyeditor recommends no packages.
xmlcopyeditor suggests no packages.
-- no debconf information
