Your message dated Thu, 11 Dec 2025 14:41:04 -0500
with message-id
<caaajcmzxlcq_cm5fpv928fu1up9vbffffxpjnkres8f1vqj...@mail.gmail.com>
and subject line Re: gnome-console 49 unlimited scrollback not possible
has caused the Debian Bug report #1115836,
regarding gnome-console 49 unlimited scrollback not possible
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.)
--
1115836: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115836
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gnome-console
Version: 49.0-1
Severity: important
Dear Maintainer,
since the update of gnome-console to v49, scrollback is no longer possible when
unlimited scrollback is enabled. Disabling that setting brings back the
scrollbar and the ability to scroll.
-- System Information:
Debian Release: forky/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-security'), (50, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6.16.7-falcot (SMP w/16 CPU threads; PREEMPT)
Kernel taint flags: TAINT_USER
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-console depends on:
ii dconf-gsettings-backend [gsettings-backend] 0.40.0-5
ii gsettings-desktop-schemas 49.0-1
ii libadwaita-1-0 1.8.0-1
ii libc6 2.41-12
ii libglib2.0-0t64 2.84.4-3
ii libgtk-4-1 4.20.1+ds-2
ii libgtop-2.0-11 2.41.3-2
ii libpango-1.0-0 1.56.3-2
ii libpangocairo-1.0-0 1.56.3-2
ii libvte-2.91-gtk4-0 0.80.3-3
gnome-console recommends no packages.
gnome-console suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 49.1-1
I looked at the commit log and it appears like this is fixed in 49.1.
Feel free to reopen if you are still experiencing this bug.
Thank you,
Jeremy Bícha
--- End Message ---
