Re: Logout at apt upgrade

2022-12-02 Thread Loïc Grenié
On Sat Dec, 3, 2022 at 04:03, David Wright wrote: > On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote: > > > > FWIW: > > > > $ apt-cache policy udev > > udev: > > Installed: 252.1-1 > > Candidate: 252.1-1 > > Version table: > > *** 252.1-1 900 > > 900 http://ftp.us.debian.o

Re: loss of screen resolution

2022-12-02 Thread Felix Miata
Kleene, Steven (kleenesj) composed on 2022-12-02 02:20 (UTC): >> Next, give us the whole log to see: > cat /var/log/Xorg.0.log | pastebinit > http://paste.debian.net/1262700/ > That's a lot to look at. Thank you. I don't see anything to suggest that there's anything wrong. Did these re

Re: Logout at apt upgrade

2022-12-02 Thread David Wright
On Fri 02 Dec 2022 at 21:33:45 (-0500), The Wanderer wrote: > > FWIW: > > $ apt-cache policy udev > udev: > Installed: 252.1-1 > Candidate: 252.1-1 > Version table: > *** 252.1-1 900 > 900 http://ftp.us.debian.org/debian testing/main amd64 Packages > 100 /var/lib/dpkg/statu

Re: Logout at apt upgrade

2022-12-02 Thread The Wanderer
On 2022-12-02 at 21:04, David Wright wrote: > On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote: > >> On Fri Dec 2 2022 at 04:31, David Wright wrote: >>> AFAICT udev was upgraded from 247.3-7 to 247.3-7+deb11u1 in early >>> September, so which distribution are /you/ running? >> >> % lsb_

Re: loss of screen resolution

2022-12-02 Thread Kleene, Steven (kleenesj)
On December 1, 2022 9:41 PM, I wrote: >> Out of the blue today, my usual screen resolution (1920x1200) became >> unavailable. ... On December 2, 2022 10:12 AM, Felix Miata wrote: > ... run > inxi -U > to upgrade, and post here output from within an X terminal: > inxi -GSaz Syst

Re: Logout at apt upgrade

2022-12-02 Thread David Wright
On Fri 02 Dec 2022 at 09:04:35 (+0100), Loïc Grenié wrote: > On Fri Dec 2 2022 at 04:31, David Wright wrote: > > On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote: > > > Happened once again. This time I think the culprit was udev (but I > > > cannot > > > be too sure). Among the upda

WiFi 802.11ax - no rx bitrate after few minutes on crowded 802.11ax AP

2022-12-02 Thread Jérémie Lienard
Dear list, On my new laptop with an Intel AX200 (iwlwifi kernel driver and the non-free firmware), i've got no trafic when i'm on an AP 802.11ax (Aruba HP, model unknown) crowded (more than 80 equipment connected). "# iw dev wlp3s0 station dump" report than there is no rx bitrate anymore. On 802

Re: loss of screen resolution

2022-12-02 Thread Felix Miata
Kleene, Steven (kleenesj) composed on 2022-12-02 13:11 (UTC): > I'll add that I did do a weekly apt upgrade shortly before this happened, Now let's see how all those things Dan asked for work together: Install/Upgrade inxi. Buster's inxi is a broken antique. Best to install directly from upstre

Re: loss of screen resolution

2022-12-02 Thread Kleene, Steven (kleenesj)
On December 1, 2022 9:41 PM, I wrote: >> Out of the blue today, my usual screen resolution (1920x1200) became >> unavailable. ... On December 2, 2022 7:43 AM, Dan Ritter replied: > I'm going to guess that this is a change in one or both of: > > - GPU firmware > - X11 GPU driver > > Let's get th

Re: loss of screen resolution

2022-12-02 Thread Dan Ritter
Kleene, Steven (kleenesj) wrote: > Out of the blue today, my usual screen resolution (1920x1200) became > unavailable. I booted to the console and called startx, which brings up > fvwm. But my default base window went way off-screen, and the type was huge. > xrandr said I was at 1024x768 and did

loss of screen resolution

2022-12-02 Thread Kleene, Steven (kleenesj)
Out of the blue today, my usual screen resolution (1920x1200) became unavailable. I booted to the console and called startx, which brings up fvwm. But my default base window went way off-screen, and the type was huge. xrandr said I was at 1024x768 and did not list the 1920x1200 option at all. (It

Re: Logout at apt upgrade

2022-12-02 Thread Loïc Grenié
On Fri Dec 2 2022 at 04:31, David Wright wrote: > On Wed 30 Nov 2022 at 14:25:19 (+0100), Loïc Grenié wrote: > > Happened once again. This time I think the culprit was udev (but I > > cannot > > be too sure). Among the updated package nothing should have killed X: > > beyond udev there wa