On Fri 30 Jan 2026 at 18:50:20 (-0600), [email protected] wrote: [ … ] I'll just make the odd comment.
> I have been fighting annoyances cubed. I had written most > of my replies to your email when Firefox went back to email > login and all changes were lost except for an early save I > had done. I always prepare text in emacs, so that very little is lost even should the machine crash when a document hasn't been explicitly saved for a while. > When I tried to log in today, I found this > computer was running -37- Xwayland instead of -36- Xorg. If you're prepared to run buster, then I can't see anything wrong with sticking with -36-. (My machine has had no problem with -37- apart from the ¤/© characters all over VCs 2-6.) > I use a NAS because I have six computers which collectively run > eleven operating systems. On this computer, using a NAS has > worked properly since I loaded Debian 7. On the new computer > -36- works fine. So does Sun Solaris and Apple Darwin. I did > check and saw in -37- that the files from the NAS were mounted. > If a computer has trouble mounting the file systems from a NAS, > the default is to mount them Read Only. But in this case the > error messages included that I could not read my files. You would have to be more specific than that. Maybe missing modules? > I had to track down what VC meant since I only use simple terminals. > The system went back to a Display Manager with a login window. As I run X with a fvwm, I don't get into that situation at login. But from what's below, it sounds like the video driver stuff. > Things acted like a regular terminal such as a VT100. But I was not > able to switch to anything different. Sometimes when using your > combination keys, it would go back to the login screen with Xwayland > running. Ah. Well that might be running on the one VC that's working properly, so with a DM, you would never see that one. Here, with -37-, I normally run X on VC1, the one that works. VCs 2-6 show nothing but ¤/©. To get both a VC and X, I just start X on VC2, by blindly typing my loginname, password, and xxx (a script that runs startx) into the ¤/© junk, which leaves VC1 available for use. > >> Warning: > >> Unsupported maximum keycode 569, clipping. This was reported in 2011 > and > >> 2012. The other related messaged were also present. I looked that up, and it seems its cause is understood (though not by me). > It sounds reasonable that Xwayland might be causing the problems. > When I tried to blacklist Xwayland, the system would not boot. I don't know what blacklisting Xwayland means. I thought you had been able to run Xorg in -36-. Nothing else changed with the kernel upgrade here: Start-Date: 2025-12-13 21:49:11 Commandline: apt-get dist-upgrade Install: linux-image-5.10.0-37-amd64:amd64 (5.10.247-1, automatic) Upgrade: linux-image-amd64:amd64 (5.10.244-1, 5.10.247-1) End-Date: 2025-12-13 21:50:01 Start-Date: 2025-12-13 21:50:59 Commandline: apt-get --purge autoremove Purge: linux-image-5.10.0-35-amd64:amd64 (5.10.237-1) End-Date: 2025-12-13 21:51:27 > >> Trying to read, > >> write, or create a file on the NAS was DENIED. The user number of the > >> file > >> matched the User's number. > > > > Again, does this relate to the upgrade, or is it still a problem > > when running the older kernel version? > > As described above, the NAS problem started with the upgrade. The actual error message would be more helpful. For example, there are simple file permissions; then there are more subtle things like apparmor restrictions; and recently someone got caught out by the addition of ProtectHome in a systemd file. > Since my new computer has four solid state disks, my plan is to > put Ubuntu, buster, bullseye, and bookworm on them. If bookworm > worked properly, I would first put in on this one (older) in place > of bullseye. Once trixie has matured a little, I would then replace > bullseye on the new computer with trixie. Buster is being kept > around until the sound works properly in bookworm or trixie. The > sound does not work properly in bullseye. For a long time bullseye > would not find my Epson scanner like buster does. Now bullseye > does find it. Yes, I think sound on DEs has changed quite a lot with the introduction of things like pulseaudio and pipewire. I've always just carried on using alsamixer, controlled by FVWM's keybindings, though I have sometimes seen pipewire running (no idea what started it). And I got used to scanning onto a USB stick 20 years ago at work, and have carried on doing that. It's never felt inconvenient as I have to stand at the scanner anyway, handling the original. Good luck, though. Cheers, David.
