Your message dated Sun, 27 Sep 2020 20:28:22 +0100
with message-id <[email protected]>
and subject line Re: Bug#941283: libvte: terminal crashes after a VTE error
has caused the Debian Bug report #941283,
regarding libvte: terminal crashes after a VTE error
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.)
--
941283: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941283
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libvte-2.91-0
Version: 0.58.0-1
Severity: important
File: libvte
Dear maintainer,
since last week, I've seen several terminal windows crash, with
gnome-terminal (official Debian testing) and roxterm (unofficial).
This happened on two computers, both using Debian testing and the same
terminal emulators. The WM is XMonad (tiling WM).
Unfortunately, I haven't seen any common cause. I've never had a crash
while typing. When I switch to a virtual desktop, the terminal windows
are gone or disappear immediately.
I saw nothing relevant in the logs, except for the last crash. From
journalctl:
sept. 27 20:37:45 org.gnome.Terminal[1063]: **
sept. 27 20:37:45 org.gnome.Terminal[1063]:t
VTE:ERROR:../src/vte.cc:555:void
vte::terminal::Terminal::set_hard_wrapped(vte::grid::row_t): assertion
failed (row < m_screen->insert_delta + m_row_count): (3091 < 3091)
sept. 27 20:37:45 sudo[6290]: pam_unix(sudo:session): session closed for
user root
I'd be glad to provide any detail you'd like.
Thanks
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (600, 'stable'), (50, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-2-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_WARN
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8),
LANGUAGE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libvte-2.91-0:amd64 depends on:
ii libatk1.0-0 2.34.0-1
ii libc6 2.29-1
ii libcairo2 1.16.0-4
ii libfribidi0 1.0.5-3.1
ii libglib2.0-0 2.60.6-2
ii libgnutls30 3.6.9-5
ii libgtk-3-0 3.24.11-1
ii libpango-1.0-0 1.42.4-7
ii libpangocairo-1.0-0 1.42.4-7
ii libpcre2-8-0 10.32-5+b1
ii libstdc++6 9.2.1-8
ii libvte-2.91-common 0.58.0-1
ii zlib1g 1:1.2.11.dfsg-1+b1
libvte-2.91-0:amd64 recommends no packages.
libvte-2.91-0:amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.58.1-1
On Sat, 28 Sep 2019 at 09:54:54 +0200, Egmont Koblinger wrote:
> This bug has already been reported upstream at
> https://gitlab.gnome.org/GNOME/vte/issues/176 and fixed by VTE's
> developers.
>
> The fix will be released in VTE 0.58.1.
Closing as fixed in that version.
smcv
--- End Message ---
