If I were maintaining the package, I personally would cheatĪnd just ask the user to confirm whether or not they want to (re)start gdm.Įxpected/desired behavior 2: upgrades shouldn't change the system keymap.įailing that, upgrades running interactively should ask or warn about changes Is somewhat unusual and I suspect actually detecting this is a lot moreĬomplicated.
Sessions on TTYs when running interactively. (I had been using a custom keymap - Dvorak with Finnish characters added.Įxpected/desired behavior 1: confirmation before killing or replacing running The system keymap was also changed to qwerty. (I'm guessing it was continuing parts of the update, but don't know) beforeĪ gdm login screen appeared. My X server was killed with no confirmation. I was running in an X server on TTY1, started with startx. I tried 'apt update' because I thought it I've been upgrading piecemeal to bullseye from Debian 10, mostly using Remember if it had been replaced by a newer version under Debian 10.
#TEX LIVE UTILITY VALIDATING SERVER PATCH#
an X server patch to fix an FD leak on context switch, but I don't
Were there any non-Debian packages installed before the upgrade? If Maintainers evaluate the report efficiently - e.g., by filling X-Debbugs-Cc: provide enough information to help the Debian
0 kommentar(er)
