Bug#753797: marked as done (braille display incorrectly refreshed e.g. at tty change)
Your message dated Sun, 23 Nov 2014 21:48:49 +0100
with message-id <20141123204849.GA23656@type.youpi.perso.aquilenet.fr>
and subject line Re: braille display incorrectly refreshed e.g. at tty change
has caused the Debian Bug report #753797,
regarding braille display incorrectly refreshed e.g. at tty change
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 owner@bugs.debian.org
immediately.)
--
753797: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=753797
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: braille display incorrectly refreshed e.g. at tty change
- From: Sebastien Hinderer <sebastien.hinderer@ens-lyon.org>
- Date: Sat, 05 Jul 2014 09:51:29 +0200
- Message-id: <20140705075129.15328.37667.reportbug@pema.homeunix.org>
Package: brltty
Version: 5.0-2+b1
Severity: normal
The content of the braille display is not always refreshed correctly.
One example is at console change: when coming back to a previously
visited console, what's displayed is the window containing the cursor,
eventhough that was not the window which was displayed when the console
was left.
This bug is notpresent in the latest upstream.
--- End Message ---
--- Begin Message ---
- To: 753797-done@bugs.debian.org
- Subject: Re: braille display incorrectly refreshed e.g. at tty change
- From: Samuel Thibault <sthibault@debian.org>
- Date: Sun, 23 Nov 2014 21:48:49 +0100
- Message-id: <20141123204849.GA23656@type.youpi.perso.aquilenet.fr>
Version: 5.2~20141018-1
Hello,
Upstream's 5.2 fixed it.
Samuel
--- End Message ---
Reply to: