Re: Logout at apt upgrade
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.org/debian testing/main amd64 Packages > > 100 /var/lib/dpkg/status > > 247.3-7+deb11u1 800 > > 800 http://ftp.us.debian.org/debian stable/main amd64 Packages > > > > IOW, this version isn't only in sid, it's also in testing. > > Yes, hence my comment on potential interactions between different > packages. The OP mentioned udev, but in their OP they talked about > manually restarting systemd services. I was under the impression > that systemd and udev are upgraded in step, and AFAICT (as I'm not > running bookworm or sid), they've had half a dozen upgrades in the > last two months. Plenty of scope for interactions there. > I run sid and am usually able to resolve the problems by myself. The fact is that during some upgrades X gets killed unexpectedly, without any warning, and on the console I see that some services do not start. I usually reboot but it's annoying; a couple of kills ago I tried to manually restart the failed services, and it's very time consuming. I still don't know *what upgrade(s)* kill(s) X. I have suspected logind, libpam and udev, but I don't know for sure. I'll try udevadm monitor as you suggested. Hence I asked if anybody else experienced the same behaviour, and implicitly what I could do to prevent those X kills. > Anyway, with my not having had similar problems, and receiving > confirmation that I'm not running the same revision, I'm not the > one to help troubleshoot this. (Boy, that's a load of negatives.) > Thanks for your help! That's a positive! Loïc
Re: loss of screen resolution
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 result after applying your xrandr workaround? If the problem remains in absence of the workaround, the inxi and log need to come from being in that condition. I have something similar needing no correction or workaround: # inxi -GSaz --vs --zl --hostname inxi 3.3.23-00 (2022-10-31) System: Host: gx62b Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters: root=LABEL= ipv6.disable=1 net.ifnames=0 biosdevname=0 plymouth.enable=0 noresume mitigations=auto consoleblank=0 Desktop: Trinity v: R14.0.13 tk: Qt v: 3.5.0 info: kicker wm: Twin v: 3.0 vt: 7 dm: 1: TDM 2: XDM Distro: Debian GNU/Linux 10 (buster) Graphics: Device-1: Intel 82945G/GZ Integrated Graphics vendor: Dell driver: i915 v: kernel arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports: active: DVI-D-1,VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2772 class-ID: 0300 Display: x11 server: X.Org v: 1.20.4 driver: X: loaded: intel unloaded: fbdev,modesetting,vesa dri: i915 gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 3600x1200 s-dpi: 120 s-size: 762x254mm (30.00x10.00") s-diag: 803mm (31.62") Monitor-1: DVI-D-1 mapped: DVI1 pos: primary,left model: NEC EA243WM serial: built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 520x320mm (20.47x12.6") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 Monitor-2: VGA-1 mapped: VGA1 pos: right model: Dell P2213 serial: built: 2012 res: 1680x1050 hz: 60 dpi: 91 gamma: 1.2 size: 470x300mm (18.5x11.81") diag: 558mm (22") ratio: 16:10 modes: max: 1680x1050 min: 720x400 API: OpenGL v: 1.4 Mesa 18.3.6 renderer: Mesa DRI Intel 945G direct render: Yes -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Logout at apt upgrade
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/status > 247.3-7+deb11u1 800 > 800 http://ftp.us.debian.org/debian stable/main amd64 Packages > > IOW, this version isn't only in sid, it's also in testing. Yes, hence my comment on potential interactions between different packages. The OP mentioned udev, but in their OP they talked about manually restarting systemd services. I was under the impression that systemd and udev are upgraded in step, and AFAICT (as I'm not running bookworm or sid), they've had half a dozen upgrades in the last two months. Plenty of scope for interactions there. Anyway, with my not having had similar problems, and receiving confirmation that I'm not running the same revision, I'm not the one to help troubleshoot this. (Boy, that's a load of negatives.) Cheers, David.
Re: Logout at apt upgrade
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_release -a >> No LSB modules are available. >> Distributor ID: Debian >> Description:Debian GNU/Linux bookworm/sid >> Release:n/a >> Codename: bookworm >> >> % LANG=C dpkg -l udev >> Desired=Unknown/Install/Remove/Purge/Hold >> | >> Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend >> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) >> ||/ Name Version Architecture Description >> +++-==---=== >> ii udev 252.1-1 amd64/dev/ and hotplug management >> daemon > > That does put a different complexion on your problem. I think that > with sid you are expected to do some troubleshooting of your own. 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/status 247.3-7+deb11u1 800 800 http://ftp.us.debian.org/debian stable/main amd64 Packages IOW, this version isn't only in sid, it's also in testing. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw signature.asc Description: OpenPGP digital signature
Re: loss of screen resolution
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 System: Kernel: 4.19.0-22-amd64 arch: x86_64 bits: 64 compiler: gcc v: 8.3.0 parameters: BOOT_IMAGE=/boot/vmlinuz-4.19.0-22-amd64 root=UUID=093750e2-4489-4550-a3fc-5e86b450320b ro quiet Desktop: FVWM v: 2.6.8 vt: 1 dm: startx Distro: Debian GNU/Linux 10 (buster) Graphics: Device-1: Intel 82946GZ/GL Integrated Graphics driver: i915 v: kernel arch: Gen-3.5 process: Intel 90nm built: 2005-06 ports: active: VGA-1 empty: none bus-ID: 00:02.0 chip-ID: 8086:2972 class-ID: 0300 Display: server: X.Org v: 1.20.4 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: i965 gpu: i915 display-ID: :0 screens: 1 Screen-1: 0 s-res: 1920x1200 s-dpi: 96 s-size: 507x317mm (19.96x12.48") s-diag: 598mm (23.54") Monitor-1: VGA-1 res: 1920x1200 hz: 60 size: N/A modes: max: 1024x768 min: 640x480 API: OpenGL v: 2.1 Mesa 18.3.6 renderer: Mesa DRI Intel 946GZ direct render: Yes > 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. From: Felix Miata Sent: Friday, December 2, 2022 10:12 AM To: debian-user@lists.debian.org Subject: Re: loss of screen resolution External Email: Use Caution 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 upstream. It's just a data collection and presentation script: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsmxi.org%2Fdocs%2Finxi-installation.htm%23inxi-manual-install&data=05%7C01%7Ckleenesj%40ucmail.uc.edu%7C0b895e40ae1845abc85b08dad477c4ea%7Cf5222e6c5fc648eb8f0373db18203b63%7C1%7C0%7C638055908118333462%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Od8tsIGlAhdF8HQbnDo2shuCpiPVRwr8jqATtd6vhhI%3D&reserved=0 To upgrade Debian's version, it's necessary to edit /etc/inxi.conf to remove the upgrade blockage, so change B_ALLOW_UPDATE=false to B_ALLOW_UPDATE=true, then run inxi -U to upgrade, and post here output from within an X terminal: inxi -GSaz Next, give us the whole log to see: cat /var/log/Xorg.0.log | pastebinit or cat ~/.local/share/xorg/Xorg.0.log | pastebinit and provide the resulting URI here, or attach the file to your reply. Don't paste its content into the email unless you know how to prevent line wrapping that makes a mess of it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: Logout at apt upgrade
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 updated package nothing should have killed X: > > > beyond udev there was a bunch of libreoffice and related (not using > > right > > > now), zathura (not using), not much more, at the very least, nothing > > that > > > looked susceptible to trigger a session crash. > > > > AFAICT udev was upgraded from 247.3-7 to 247.3-7+deb11u1 in > > early September, so which distribution are /you/ running? > > > % lsb_release -a > No LSB modules are available. > Distributor ID: Debian > Description:Debian GNU/Linux bookworm/sid > Release:n/a > Codename: bookworm > > % LANG=C dpkg -l udev > Desired=Unknown/Install/Remove/Purge/Hold > | > Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend > |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) > ||/ Name Version Architecture Description > +++-==---=== > ii udev 252.1-1 amd64/dev/ and hotplug management > daemon That does put a different complexion on your problem. I think that with sid you are expected to do some troubleshooting of your own. For example, if you suspect udev, you could run udevadm monitor … while upgrades are in progress, to see whether specific triggers are causing a problem. Etc. You also have to bear in mind that different users may have held or upgraded different versions of packages, and not get the same problems when caused by interaction between them. Perhaps see: https://lists.debian.org/debian-user/2021/02/msg00381.html (updating the codenames by one release). Cheers, David.
WiFi 802.11ax - no rx bitrate after few minutes on crowded 802.11ax AP
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.11ac AP (same brand) even crowded, there is no such problem, the rx bitrate is changing regularly, even disappearing when there is no trafic. When there is trafic, rx bitrate is reappearing. I've tested and reproduced the problem on GNU/Linux Debian 11, with the kernel 5.10, 5.18, 5.19 and 6.0.3 (backport). Even with Ubuntu 22.04, kernel 5.15, I've got the problem. Unfortunately, the GNU/Debian kernel doesn't the right flag ( https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging ), I move to Ubuntu to make some trace. Maybe I have to recompile the GNU/Linux Debian kernel with the right flag activated to make some trace, but I didn't compile my kernel for than 10 years. Is someone got this problem ? How to deal with the trace ? What can I do more ? Bests regards, J. Lienard
Re: loss of screen resolution
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 upstream. It's just a data collection and presentation script: https://smxi.org/docs/inxi-installation.htm#inxi-manual-install To upgrade Debian's version, it's necessary to edit /etc/inxi.conf to remove the upgrade blockage, so change B_ALLOW_UPDATE=false to B_ALLOW_UPDATE=true, then run inxi -U to upgrade, and post here output from within an X terminal: inxi -GSaz Next, give us the whole log to see: cat /var/log/Xorg.0.log | pastebinit or cat ~/.local/share/xorg/Xorg.0.log | pastebinit and provide the resulting URI here, or attach the file to your reply. Don't paste its content into the email unless you know how to prevent line wrapping that makes a mess of it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
Re: loss of screen resolution
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 the output from: > > cat /etc/debian_version 10.13 > lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 82946GZ/GL Integrated Graphics Controller (rev 02) > dpkg --get-selections | grep firmware firmware-linux-free install > dpkg --get-selections | grep xserver-xorg-video-* xserver-xorg-video-all install xserver-xorg-video-amdgpu install xserver-xorg-video-ati install xserver-xorg-video-fbdevinstall xserver-xorg-video-intelinstall xserver-xorg-video-nouveau install xserver-xorg-video-qxl install xserver-xorg-video-radeon install xserver-xorg-video-vesa install xserver-xorg-video-vmware install > grep Driver /var/log/Xorg.0.log|grep II [ 2059.194] (II) modesetting: Driver for Modesetting Kernel Drivers: kms I'll add that I did do a weekly apt upgrade shortly before this happened, but it's not obvious that any of the upgrades (firefox-esr grub-common grub-pc grub-pc-bin grub2-common krb5-locales libgssapi-krb5-2 libgssapi-krb5-2:i386 libk5crypto3 libk5crypto3:i386 libkrb5-3 libkrb5-3:i386 libkrb5support0 libkrb5support0:i386 vim-common vim-tiny xxd) are relevant. Thanks. From: Dan Ritter Sent: Friday, December 2, 2022 7:43 AM To: Kleene, Steven (kleenesj) Cc: debian-user@lists.debian.org Subject: Re: loss of screen resolution External Email: Use Caution 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 not list the 1920x1200 option at all. > (It usually does.) I was able to define and call that option in my base > window with: > > xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 > 1209 1245 -hsync +vsync > xrandr --addmode VGA-1 1920x1200_60.00 > xrandr --output VGA-1 --mode 1920x1200_60.00 > > This gave me my usual window and font size, but there are some side issues > (e.g. where icons go when I minimize them). > > In any case, I think the problem is upstream of X windows. I boot to a > console, and the font there was much bigger than usual. Where is that > controlled? Any idea how to get this back to normal? The monitor is set to > an aspect ratio of 16:1. Resetting the monitor and rebooting did not fix > the problem. I'm going to guess that this is a change in one or both of: - GPU firmware - X11 GPU driver Let's get the output from: cat /etc/debian_version to find out what you're running lspci | grep VGA to find out what your graphics hardware is dpkg --get-selections | grep firmware to find out what firmware is installed dpkg --get-selections | grep xserver-xorg-video-* to find out whether the right video driver is installed and finally, grep Driver /var/log/Xorg.0.log|grep II or if that file is missing, grep Driver ~/.local/share/xorg/Xorg.0.log | grep II to find out what driver is actually being used -dsr-
Re: loss of screen resolution
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 not list the 1920x1200 option at all. > (It usually does.) I was able to define and call that option in my base > window with: > > xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 > 1209 1245 -hsync +vsync > xrandr --addmode VGA-1 1920x1200_60.00 > xrandr --output VGA-1 --mode 1920x1200_60.00 > > This gave me my usual window and font size, but there are some side issues > (e.g. where icons go when I minimize them). > > In any case, I think the problem is upstream of X windows. I boot to a > console, and the font there was much bigger than usual. Where is that > controlled? Any idea how to get this back to normal? The monitor is set to > an aspect ratio of 16:1. Resetting the monitor and rebooting did not fix > the problem. I'm going to guess that this is a change in one or both of: - GPU firmware - X11 GPU driver Let's get the output from: cat /etc/debian_version to find out what you're running lspci | grep VGA to find out what your graphics hardware is dpkg --get-selections | grep firmware to find out what firmware is installed dpkg --get-selections | grep xserver-xorg-video-* to find out whether the right video driver is installed and finally, grep Driver /var/log/Xorg.0.log|grep II or if that file is missing, grep Driver ~/.local/share/xorg/Xorg.0.log | grep II to find out what driver is actually being used -dsr-
loss of screen resolution
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 usually does.) I was able to define and call that option in my base window with: xrandr --newmode "1920x1200_60.00" 193.25 1920 2056 2256 2592 1200 1203 1209 1245 -hsync +vsync xrandr --addmode VGA-1 1920x1200_60.00 xrandr --output VGA-1 --mode 1920x1200_60.00 This gave me my usual window and font size, but there are some side issues (e.g. where icons go when I minimize them). In any case, I think the problem is upstream of X windows. I boot to a console, and the font there was much bigger than usual. Where is that controlled? Any idea how to get this back to normal? The monitor is set to an aspect ratio of 16:1. Resetting the monitor and rebooting did not fix the problem. Thanks.
Re: Logout at apt upgrade
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 was a bunch of libreoffice and related (not using > right > > now), zathura (not using), not much more, at the very least, nothing > that > > looked susceptible to trigger a session crash. > > AFAICT udev was upgraded from 247.3-7 to 247.3-7+deb11u1 in > early September, so which distribution are /you/ running? > > Cheers, > David. > % lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Debian GNU/Linux bookworm/sid Release:n/a Codename: bookworm % LANG=C dpkg -l udev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==---=== ii udev 252.1-1 amd64/dev/ and hotplug management daemon Cheers, Loïc
