Your message dated Thu, 09 Dec 2021 22:22:37 +0100 with message-id <[email protected]> and subject line Re: Bug#1001390: xterm / uxterm / lxterm suddenly missing from alternatives has caused the Debian Bug report #1001390, regarding xterm / uxterm / lxterm suddenly missing from alternatives to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1001390: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001390 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xterm Version: 370-1 Severity: normal After upgrading xterm to the most recent package in xterm, suddenly the x-terminal-emulator alternative was pointing to gnome-terminal instead of uxterm (before the upgrade). Even worse, xterm and uxterm are apparently no longer even registered with the alternatives mechanism. I checked the debian changelog, and it didn't state any related change. So I conclude this is a bug and xterm / uxterm / lxterm should of course still show up in the alternatives, as it has always been. /var/lib/dpkg/alternatives/x-terminal-emulator on unstable: ----------- /usr/bin/x-terminal-emulator x-terminal-emulator.1.gz /usr/share/man/man1/x-terminal-emulator.1.gz /usr/bin/gnome-terminal.wrapper 40 /usr/share/man/man1/gnome-terminal.1.gz ----------- /var/lib/dpkg/alternatives/x-terminal-emulator on Debian 10: ----------- /usr/bin/x-terminal-emulator x-terminal-emulator.1.gz /usr/share/man/man1/x-terminal-emulator.1.gz /usr/bin/koi8rxterm 20 /usr/share/man/man1/koi8rxterm.1.gz /usr/bin/lxterm 30 /usr/share/man/man1/lxterm.1.gz /usr/bin/uxterm 20 /usr/share/man/man1/uxterm.1.gz /usr/bin/xterm 20 /usr/share/man/man1/xterm.1.gz ----------- -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.14.0-4-amd64 (SMP w/4 CPU threads) Kernel taint flags: TAINT_DIE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xterm depends on: ii libc6 2.32-5 ii libfontconfig1 2.13.1-4.2 ii libfreetype6 2.11.0+dfsg-1 ii libice6 2:1.0.10-1 ii libtinfo6 6.3-1 ii libutempter0 1.2.1-2 ii libx11-6 2:1.7.2-2+b1 ii libxaw7 2:1.0.13-1.1 ii libxext6 2:1.3.4-1 ii libxft2 2.3.2-2 ii libxinerama1 2:1.1.4-2 ii libxmu6 2:1.1.2-2+b3 ii libxpm4 1:3.5.12-1 ii libxt6 1:1.2.0-1 ii xbitmaps 1.1.1-2.1 Versions of packages xterm recommends: ii x11-utils 7.7+5 Versions of packages xterm suggests: pn xfonts-cyrillic <none> -- no debconf information
--- End Message ---
--- Begin Message ---On 2021-12-09 21:50 +0100, Harald Welte wrote: > Hi Sven, > > On Thu, Dec 09, 2021 at 07:28:22PM +0100, Sven Joachim wrote: >> There is a postinst script in dpkg which moves the misplaced files from >> /var/lib/dpkg to /var/lib/dpkg/alternatives, but if more than one >> package sets up an alternative, that is apparently not enough. The gnome-terminal package has seen an upload rather recently on December 5, so I suspect the buggy update-alternatives from dpkg 1.21.0 installed /var/lib/dpkg/x-terminal-emulator with just the entries for gnome-terminal, and the dpkg 1.21.1 postinst moved that file to the alternatives directory, clobbering the entries for xterm. > I didn't have any 'suspicious' files there. If you want to be super careful, comparing the files in /var/lib/dpkg/alternatives with a recent backup from before December 7 could be useful. The alternatives database is backed up in /var/backups on a daily basis. >> My recommendation would be to reinstall affected packages like xterm, >> and configure the alternatives again. > > reinstalling xterm solved the problem. Good to hear that. > This bug can be closed. Doing that now, glad I could help. :) Cheers, Sven
--- End Message ---
