From: "Thomas Weißschuh" <linux@weissschuh.net>
To: Storm Dragon <stormdragon2976@gmail.com>
Cc: George Kennedy <george.kennedy@oracle.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH] vc_screen: don't clobber return value in vcs_read
Date: Fri, 10 Mar 2023 21:32:23 +0000 [thread overview]
Message-ID: <e152e3ad-9485-4f9b-979f-eaabfe074aa1@t-8ch.de> (raw)
In-Reply-To: <ZAOi9hDBTYqoAZuI@hotmail.com>
On Sat, Mar 04, 2023 at 02:58:46PM -0500, Storm Dragon wrote:
> On Fri, Mar 03, 2023 at 11:25:00PM +0000, Thomas Weißschuh wrote:
>
> > Does this mean the screenreader now works correctly or is it still
> > broken somehow?
> >
> > Thomas
>
> I have still been testing this kernel. Most things work as expected, but
> the pasting functionality for Fenrir's clipboard is broken. After
> checking into the problem, it seems that tiocsti is disabled, and that
> is causing the problem. Was that something done in this test kernel
> only, or will that be the default for all new Arch kernels? If it is the
> default, is there a way to turn it back on? I tried the following:
>
> [storm@mjollnir ~] $ sudo sysctl dev.tty.legacy_tiocsti=1
> sysctl: setting key "dev.tty.legacy_tiocsti": Invalid argument
The sysctl to enable the ioctl should be fixed in 6.2.3:
pacman -U https://mirrors.edge.kernel.org/archlinux/testing/os/x86_64/linux-6.2.3.arch1-1-x86_64.pkg.tar.zst
Thomas
prev parent reply other threads:[~2023-03-10 21:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 21:21 Bug with /dev/vcs* devices Storm Dragon
2023-02-19 22:11 ` Randy Dunlap
2023-02-19 23:13 ` Storm Dragon
2023-02-20 6:46 ` [PATCH] vc_screen: don't clobber return value in vcs_read linux
2023-02-20 11:48 ` Jiri Slaby
2023-02-20 16:34 ` Thomas Weißschuh
2023-02-21 13:30 ` George Kennedy
2023-02-21 13:49 ` Thomas Weißschuh
2023-02-21 13:50 ` Greg Kroah-Hartman
2023-02-27 14:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-27 19:59 ` George Kennedy
2023-02-28 5:38 ` Linux regression tracking (Thorsten Leemhuis)
2023-02-20 16:06 ` Storm Dragon
2023-03-03 21:12 ` Thomas Weißschuh
2023-03-03 21:46 ` Storm Dragon
2023-03-03 23:25 ` Thomas Weißschuh
2023-03-04 3:30 ` Storm Dragon
2023-03-04 3:42 ` Storm Dragon
2023-03-04 19:58 ` Storm Dragon
2023-03-04 22:33 ` Thomas Weißschuh
2023-03-10 21:32 ` Thomas Weißschuh [this message]
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=e152e3ad-9485-4f9b-979f-eaabfe074aa1@t-8ch.de \
--to=linux@weissschuh.net \
--cc=george.kennedy@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=stormdragon2976@gmail.com \
/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
all inboxes | Powered by JetHome®