Your message dated Wed, 7 Feb 2024 12:17:25 +0100
with message-id <[email protected]>
and subject line Resolved in 2.0.0
has caused the Debian Bug report #893858,
regarding tilda: sometimes crashes with X Error: BadMatch (invalid parameter
attributes)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
893858: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893858
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: tilda
Version: 1.4.1-2
Severity: important
Dear Maintainer,
sometimes Tilda crashes with the message:
** (tilda:14324): ERROR **: X Error: BadMatch (invalid parameter attributes)
Not sure if this happens in background or when I try to unroll it. I
experienced this several times for the past days.
-- System Information:
Debian Release: buster/sid
APT prefers oldoldstable-updates
APT policy: (500, 'oldoldstable-updates'), (500, 'oldoldstable'),
(500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=ru_UA.UTF-8, LC_CTYPE=ru_UA.UTF-8 (charmap=UTF-8),
LANGUAGE=ru_UA:ru (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages tilda depends on:
ii libc6 2.27-2
ii libconfuse2 3.2.1+dfsg-4
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libglib2.0-0 2.54.3-2
ii libgtk-3-0 3.22.29-1
ii libpango-1.0-0 1.40.14-1
ii libvte-2.91-0 0.52.0-1
ii libx11-6 2:1.6.4-3
tilda recommends no packages.
tilda suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Tilda 2.0.0 is now in unstable and contains several fixes related to BadMatch
and BadWindow errors. I hope that this resolved the bug. If you can still
reproduce the problem with 2.0.0, then please reopen this bug with more
information.
--- End Message ---
