Re: I think I found a quite severe bug, what is the next step?
On 2/16/23 18:45, Storm Dragon wrote: Howdy, Same output: cat: /dev/vcsa1: No such device or address Same for me - in my case I see gdm as owner of vcsa1 so perhaps there is no buffer to read in this case? Sorry I know nothing about these devices and man vcs didn't enlighten me - i have plain gnome and a bunch of text terminals - but they are all associated with the usual /dev/pty/xxx and many more of those than vcs ones.
I think I found a quite severe bug, what is the next step?
Howdy,
I started this new topic, because I think we have gone from weird quirk
to serious bug. Fenrir, in the console, uses /dev/vcsa and /dev/vcsu.
Here is the output of ls -l for each of them:
[storm@mjollnir dev] $ ls -1l vcsa*
crw-rw 1 root tty 7, 128 Feb 15 18:30 vcsa
crw-rw 1 root tty 7, 129 Feb 15 18:30 vcsa1
crw-rw 1 root tty 7, 130 Feb 15 18:30 vcsa2
crw-rw 1 root tty 7, 131 Feb 15 18:30 vcsa3
crw-rw 1 root tty 7, 132 Feb 15 18:30 vcsa4
crw-rw 1 root tty 7, 133 Feb 15 18:30 vcsa5
crw-rw 1 root tty 7, 134 Feb 15 18:30 vcsa6
crw-rw 1 root tty 7, 135 Feb 15 18:30 vcsa7
[storm@mjollnir dev] $ ls -1l vcsu*
crw-rw 1 root tty 7, 64 Feb 15 18:30 vcsu
crw-rw 1 root tty 7, 65 Feb 15 18:30 vcsu1
crw-rw 1 root tty 7, 66 Feb 15 18:30 vcsu2
crw-rw 1 root tty 7, 67 Feb 15 18:30 vcsu3
crw-rw 1 root tty 7, 68 Feb 15 18:30 vcsu4
crw-rw 1 root tty 7, 69 Feb 15 18:30 vcsu5
crw-rw 1 root tty 7, 70 Feb 15 18:30 vcsu6
crw-rw 1 root tty 7, 71 Feb 15 18:30 mcsu7
And now, things get interesting:
[storm@mjollnir dev] $ sudo \cat /dev/vcsa
cat: /dev/vcsa1: No such device or address
Same for /dev/vcsu also including 1-7 for each of them.
Other tests I tried. Importing them with python results the same for
vcsa and vcsu:
[root@mjollnir ~]# python
Python 3.10.9 (main, Dec 19 2022, 17:35:49) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
import os
useVCSA = os.access('/dev/vcsa', os.R_OK)
print(useVCSA)
True
vcsa= open("/dev/vcsa",'rb')
d = vcsa.read()
Traceback (most recent call last):
File "", line 1, in
OSError: [Errno 6] No such device or address
I hope I have provided enough information. I'm kind of stuck at this
point. What should I do next? This happened yesterday after updates. I
can add the pacman logs from yesterday if those are needed.
Thanks,
Storm
signature.asc
Description: PGP signature
Re: TTY behaving strangely after yesterday update
Howdy Matthew, Thank you for your reply. The .screenrc file is the same one I have had for over 10 years with no problems before now. I only mentioned it because it is the only other weird thing to happen in conjunction with the Fenrir problem. Screen, however, still does work. Thanks, Storm signature.asc Description: PGP signature
Re: cannot resolve "libxml"
On Thu, 2023-02-16 at 12:28 -0600, Doug Newgard wrote: > On Thu, 16 Feb 2023 19:23:55 +0100 > Ralf Mardorf wrote: > > > Hi, > > > > isn't the issue shown below worth a comment on "Latest News" and on > > arch-announce? > > No, it's a simple packaging bug. It's worth a bug report. Maybe I made a typo when searching for a bug report, before I sent my request to the mailing list. A bug report already exists, https://bugs.archlinux.org/index.php?do=details=details.addvote_id=77545 Thanks, Ralf
Re: cannot resolve "libxml"
On Thu, 16 Feb 2023 19:23:55 +0100 Ralf Mardorf wrote: > Hi, > > isn't the issue shown below worth a comment on "Latest News" and on > arch-announce? No, it's a simple packaging bug. It's worth a bug report.
cannot resolve "libxml"
Hi, isn't the issue shown below worth a comment on "Latest News" and on arch-announce? [rocketmouse@archlinux ~]$ sudo pacman -Syu [snip] resolving dependencies... warning: cannot resolve "libxml", a dependency of "yoshimi" :: The following package cannot be upgraded due to unresolvable dependencies: yoshimi :: Do you want to skip the above package for this upgrade? [y/N] [snip] "libxml (virtual)" - https://archlinux.org/packages/community/x86_64/yoshimi/ Regards, Ralf
TTY behaving strangely after yesterday update
Howdy, I use the fenrir screen reader, and after updating yesterday, it will no longer work in the console. I have tested it in a PTY, and it works fine there, so it's not a change in the screen reader itself. Also, it is the same version that was being used before the update. Also, interestingly, screen gives an error when I launch it now. It did not used to do this, but it flashes up an error that I can't review because it's gone as quickly as it appears. I probably wouldn't have noticed it at all if it wasn't for speakup reading the error. So I'm probably not spelling this exactly, but it sounds like it is saying: /home/storm/.screenrc expected character, x, or ioctl 38 The interesting part from the Fenrir log is, there are quite a few of these errors: ERROR 2023-02-16 06:55:48.420559: VCSA:updateWatchdog:[Errno 6] No such device or address I have checked and all the /dev/vcs stuff is there. It even seems to have the correct permissions and ownership. Here is a sample: crw-rw 1 root tty 7, 1 Feb 15 18:30 /dev/vcs1 Does anyone have any idea what may be going on with this? Oh, and I'm using Linux-lts: linux-lts 5.15.94-1 Thanks, Storm signature.asc Description: PGP signature
