gene heskett <ghesk...@shentel.net> writes: > now my additional reply is munged, backspaces or Del's will not "take" > What the heck is this vertical bar it uses for a quote level, whats wrong > with > >> etc for quote indicators? There's a button containing an A > overlaid by a graphical double square as the last line above the window > that claims to "remove text styling" but it does nothing. Under options > ->delivery format, plain text is checked, but obviously its still sending > and rendering what I see as HTML. That's not the end of the bug list
Just a note, in my end your post is just text: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Not HTML, not multipart/alternative with one part text and one HTML. I don't know if there's any filtering in-between, I read this list via Gmane's NNTP server. > This install feels good yet, but at 36 hours uptime, I've used > half the typical uptime I've managed in 30 previous installs. > I have had to replace some memory, but now memtest can't > be found, I guess because it is a 16 bit build, and can't be > changed. But it ran ON THIS 6 core i5, probably 8 or 9 times > pre bullseye. Debian 11 packages memtest86 and memtest86+ in the main repository with those package names exactly. Those are quite old and if you managed a UEFI installation they aren't bootable. > So what replaces it? From the thread about its MIA status, I > am not the only one wanting it or a 64 bit substitute back > on the grub menu. > > I have a $100 bill for the talented coder who brings that > or a new 64 bit from scratch version back. The commercial memtest86 v9 Pro from Passmark goes for $44 today. They have a free edition too with limited features. > It does not!!!!!!!!!! That's what I'm screaming about. > It sets the perms so only root can use them. I just > plugged at least one of them in: > root@coyote:/lib/udev/rules.d# ls -l /dev/ttyUSB* > crw-rw---- 1 root dialout 188, 0 Jun 15 05:31 /dev/ttyUSB0 > > 020660. The common user can't touch it. So what IS > the "approved fix" so the user CAN use it? A fix that > will actually survive a reboot. That's the question > asked that every reply so far has ignored. I've looked into this and I have a draft of another post about that but basically it looks like it'll amount to just "I don't know why" and "it works for me." I need to test a few things though. A rude hack to fix the permissions would be to setup /etc/rc.local and do your chgrps and/or chmods in there. Instructions at https://blog.wijman.net/enable-rc-local-in-debian-bullseye/ for example.