From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] drawterm: canlock errors (posix-generic/tas.c) on x86_64
Date: Tue, 03 Nov 2020 22:29:24 +0100 [thread overview]
Message-ID: <20201103212924.Nrp46yB3DOz1vmeioQtD_Pf4-TkrZloScE1DFnxkYxI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26109@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
Closed issue by ashpooljh on void-packages repository
https://github.com/void-linux/void-packages/issues/26109
Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System
* xuname: `Void 5.8.17_1 x86_64 GenuineIntel uptodate hold rmFFFFFFFFFFFF`
* package: `drawterm-0.0.20200619_1`
### Expected behavior
`drawterm` works normally. No error messages (e.g. `canlock: corrupted 0x2`) are printed.
### Actual behavior
Upon authenticating on a CPU server the background of the terminal window starts filling up with error messages. All the messages are of the same type:
```
canlock: corrupted 0xXX
```
where `XX` is replaced by a different hexadecimal number each time. An example of this behavior can be observed on the attached screenshot:
These messages can appear when any input is sent to the terminal (e.g. typing commands, moving and creating windows, etc). It is barely possible to use the terminal without interruption, since the messages will obstruct any windows created.
### Steps to reproduce the behavior
* Run `drawterm` as built by the Void Linux project on x86_64 arch
* Authenticate on a 9front CPU server
* Run `rio` (done from `lib/profile` in my case)
* Do pretty much anything
next prev parent reply other threads:[~2020-11-03 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 18:43 [ISSUE] " ashpooljh
2020-11-03 18:50 ` ashpooljh
2020-11-03 21:29 ` q66 [this message]
2020-11-03 21:29 ` q66
2020-11-03 21:48 ` ashpooljh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201103212924.Nrp46yB3DOz1vmeioQtD_Pf4-TkrZloScE1DFnxkYxI@z \
--to=q66@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).