[Touch-packages] [Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
I concluded that the description was related to the use of the us+dvorak-alt-intl layout, and not to g-c-c setting incorrect options. Observations from use of the us+intl layout: Alternate Characters Key to None $ gsettings get org.gnome.desktop.input-sources xkb-options ['lv3:ralt_alt'] Right Alt according to xev: Alt_R Alternate Characters Key to None + Compose key to Right Ctrl $ gsettings get org.gnome.desktop.input-sources xkb-options ['lv3:ralt_alt', 'compose:rctrl'] Right Alt according to xev: Alt_R Right Ctrl according to xev: Multi_key Alternate Charters Key to None + Compose key to Right Alt - $ gsettings get org.gnome.desktop.input-sources xkb-options ['lv3:ralt_alt', 'compose:ralt'] Right Alt according to xev: Multi_key I see only expected options and expected results. So please elaborate on how you think that g-c-c behaves incorrectly, preferably with a reproducible use case. ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout Status in gnome-control-center package in Ubuntu: Incomplete Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
This may be a duplicate of https://launchpad.net/bugs/1969162 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: New Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
> And AFAICT gnome-control-center sets the expected XKB options, > so it's not a g-c-c bug. Maybe an xkeyboard-config bug. >From my initial bug report: Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. So no, gnome-control-center was not setting the expected XKB options either. ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout Status in gnome-control-center package in Ubuntu: New Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969544] [NEW] package libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0'
Public bug reported: wine installed but recieving wine 32 not installed error cuz of dependenceis but the dependecies goes into rabbit hole like 6 or more, it just doesnt end ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 20 06:39:02 2022 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.14.4-dmo7+deb10u1 InstallationDate: Installed on 2022-04-12 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.1 apt 2.0.6 SourcePackage: gst-plugins-good1.0 Title: package libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.14.4-dmo7+deb10u1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gst-plugins-good1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1969544 Title: package libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.14.4-dmo7+deb10u1 Status in gst-plugins-good1.0 package in Ubuntu: New Bug description: wine installed but recieving wine 32 not installed error cuz of dependenceis but the dependecies goes into rabbit hole like 6 or more, it just doesnt end ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Apr 20 06:39:02 2022 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.14.4-dmo7+deb10u1 InstallationDate: Installed on 2022-04-12 (7 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.1 apt 2.0.6 SourcePackage: gst-plugins-good1.0 Title: package libgstreamer-plugins-good1.0-0 1.16.2-1ubuntu2.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libgstbasecamerabinsrc-1.0.so.0', which is also in package libgstreamer-plugins-bad1.0-0:amd64 1:1.14.4-dmo7+deb10u1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-good1.0/+bug/1969544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969118] Re: Certificate viewer shows extra bytes for RSA keys
Hello Mikko, thanks for the report; I believe that's working as intended, those bytes are part of the DER encoding; there's an excellent answer at https://crypto.stackexchange.com/a/19982/1400 that describes the meanings of each of those bytes. Thanks ** Information type changed from Private Security to Public Security ** Changed in: gcr (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1969118 Title: Certificate viewer shows extra bytes for RSA keys Status in gcr package in Ubuntu: Invalid Bug description: When I view a x509 certificate using gcr-viewer .../path/to/certificate.pem and open the "Details" section and check the RSA public key information, the section that lists the public key renders extra 8 bytes at the start and 5 bytes at the end which are not actually part of the key. I haven't tried if this happens with other file types except x509, or with encryption methods except RSA. The exact certificate I viewed can be downloaded from https://crt.sh/?d=6454583403 and the expected public key modulus should start with 00:b6:28:0b:44:... but the certificate viewer shows public key starting with bytes 30 82 01 0A 02 82 01 01 00 B6 28 0B 44. Note the extra bytes 30 82 01 0A 02 82 01 01. The extra bytes seem to be static and do not change after re-lanching the viewer again. There are also extra bytes in the end of the displayed key. I'm marking this bug as a security vulnerability for now because (1) This tool is supposed to used to check encryption credentials, and (2) It's still unknown if this is some kind of 8 byte underflow/5 byte overflow or just a rendering problem. I'm not aware of the viewer writing extra bytes to any memory location so I would assume this is just a rendering issue. I'm fine with this issue being public so feel free to publish at your discretion. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gcr 3.28.0-1 ProcVersionSignature: Ubuntu 5.4.0-107.121~18.04.1-lowlatency 5.4.174 Uname: Linux 5.4.0-107-lowlatency x86_64 ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 CurrentDesktop: MATE Date: Thu Apr 14 15:47:18 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-05 (1194 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: gcr UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1969118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
Here's the postinst I've got for that package. Maybe the
reload_dbus_config() could use a --reply-timeout=5000 or something?
Thanks
$ cat /fst/trees/ubuntu/main/d/dbus/dbus_1.12.20-2ubuntu4/debian/dbus.postinst
#!/bin/sh
# Copyright © 2003 Colin Walters
# Copyright © 2006 Sjoerd Simons
set -e
MESSAGEUSER=messagebus
MESSAGEHOME=/var/run/dbus
LAUNCHER=/usr/lib/dbus-1.0/dbus-daemon-launch-helper
# This is what the init script would do, but it's simpler (and less
# dependent on sysvinit vs. Upstart vs. etc.) if we do it directly.
reload_dbus_config() {
[ -S /var/run/dbus/system_bus_socket ] || return 0
dbus-send --print-reply --system --type=method_call \
--dest=org.freedesktop.DBus \
/ org.freedesktop.DBus.ReloadConfig > /dev/null || true
}
if [ "$1" = triggered ]; then
reload_dbus_config
exit 0
fi
if [ "$1" = configure ]; then
adduser --system \
--quiet \
--home /nonexistent \
--no-create-home \
--disabled-password \
--group "$MESSAGEUSER"
if ! dpkg-statoverride --list "$LAUNCHER" >/dev/null; then
dpkg-statoverride --update --add root "$MESSAGEUSER" 4754 "$LAUNCHER"
fi
# This is idempotent, so it's OK to do every time. The system bus' init
# script does this anyway, but you also have to do this before a session
# bus will work, so we do this here for the benefit of people starting
# a temporary session bus in a chroot
dbus-uuidgen --ensure
fi
if [ "$1" = configure ] && [ -n "$2" ]; then
# On upgrades, we only reload config, and don't restart (restarting the
# system bus is not supported by upstream). The code added by
# dh_installinit -r creates a start action, below.
# Recommend a reboot if there is a dbus-daemon running in the same root
# as us. Deliberately not using anything init-related here, to be
# init-agnostic: if we get a false positive (at least one dbus-daemon
# is running but it isn't the system bus) that isn't the end of the
# world, because it's probably a session bus, so the user needs to
# log out and back in anyway.
#
# Debian has /usr/bin/dbus-daemon, Ubuntu has /bin/dbus-daemon.
# Look for both.
if pidof -c /bin/dbus-daemon /usr/bin/dbus-daemon >/dev/null; then
echo "A reboot is required to replace the running dbus-daemon." >&2
echo "Please reboot the system when convenient." >&2
# trigger an update notification that recommends a reboot
# (used by unattended-upgrades etc.)
touch /var/run/reboot-required || true
if ! grep -Fqsx dbus /run/reboot-required.pkgs; then
echo dbus >> /run/reboot-required.pkgs || true
fi
# same thing for the older update-notifier interface
[ -x /usr/share/update-notifier/notify-reboot-required ] && \
/usr/share/update-notifier/notify-reboot-required || true
fi
# Clean up old compatibility symlinks that were used to upgrade from
# Debian 8 to Debian 9. This can be dropped after Debian 10 is released.
for bus in system session; do
conf="/etc/dbus-1/${bus}.conf"
exp_target="/usr/share/dbus-1/${bus}.conf"
target="$(readlink -f "${conf}")" || continue
if [ -h "${conf}" ] && [ "_${target}" = "_${exp_target}" ]; then
rm -f "${conf}"
fi
done
fi
#DEBHELPER#
# Do this after the debhelper-generated bits so that dpkg-maintscript-helper
# will have finished moving configuration files around. We only need to do
# this for upgrades, not new installations.
if [ "$1" = configure ] && [ -n "$2" ]; then
reload_dbus_config
fi
# We don't start dbus.service in postinst, so ensure dbus.socket is running
if [ "$1" = configure ] && [ -d /run/systemd/system ]; then
systemctl try-restart sockets.target || true
fi
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1968845
Title:
Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
reboot
Status in dbus package in Ubuntu:
New
Bug description:
Upgrading on a virtual machine from 20.04 to 22.04. I have had this
happen twice now, I got one upgrade done without this bug.
Basically the package installation stops at dbus package asking for a
reboot as it was unable to upgrade as dbus-daemon was running. And
rebooting at this stage obviously will cause a non-functioning system.
Added a screenshot of the upgrade window.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
Found more specific terms of the problem. I have the keepassxc password manager version 2.7.1 compiled from source, it stores the keys and it adds them to ssh-agent, under such conditions this error appears. The problem arose only after updating openssh to 8.9p1 and only on arm. With version 8.8p1 it continues to work, but on PC it also works with 8.9p1. If you put the keys in the .ssh folder, then everything works, it stopped working only in conjunction with keepassxc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot
Yikes, does it actually *stop* at that point? That's .. not ideal. Thanks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1968845 Title: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot Status in dbus package in Ubuntu: New Bug description: Upgrading on a virtual machine from 20.04 to 22.04. I have had this happen twice now, I got one upgrade done without this bug. Basically the package installation stops at dbus package asking for a reboot as it was unable to upgrade as dbus-daemon was running. And rebooting at this stage obviously will cause a non-functioning system. Added a screenshot of the upgrade window. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912577] Re: package linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: initramfs-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1912577 Title: package linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: When i am put update and upgrade comment this error will appear. what can i do. a few days ago same problem occur and i lost my ubuntu. then i re-instaled it. now the same problem will occur what can i do, kindly help me. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Jan 21 09:20:45 2021 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2021-01-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: initramfs-tools Title: package linux-image-5.8.0-40-generic 5.8.0-40.45~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1912577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969396] Re: gnome-control-center compose key setting does not set compose key
>> 1. Which keyboard layout are you using? > > English (Dvorak, alt. intl.) There is something with that layout. With that enabled I can reproduce the problem. Both on jammy and impish. >> 2. What happens if you drop the 'lv3:none' option, so you only have: >> ['altwin:menu', 'compose:ralt'] > > This works. It doesn't work for me with the "English (Dvorak, alt. intl.)" layout. Unlike when using for instance the Swedish or "English (US, intl., with dead keys)" layout, 'compose:ralt' does not override the layout's default definition of "Right Alt" as the 3rd level key. Can it be some kind of race condition? So it seems to be the combination of Right Alt as compose key and the English (Dvorak, alt. intl.) layout which does not work. I changed the bug title accordingly. And AFAICT gnome-control-center sets the expected XKB options, so it's not a g-c-c bug. Maybe an xkeyboard-config bug. @Steve: Are we agreed on this problem description? ** Summary changed: - gnome-control-center compose key setting does not set compose key + Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout ** Package changed: gnome-control-center (Ubuntu) => xkeyboard-config (Ubuntu) ** Changed in: xkeyboard-config (Ubuntu) Importance: High => Medium ** Changed in: xkeyboard-config (Ubuntu) Status: Incomplete => Confirmed ** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1969396 Title: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout Status in xkeyboard-config package in Ubuntu: Confirmed Bug description: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1969396/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969396] [NEW] Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout
You have been subscribed to a public bug: I noticed after upgrade from impish to jammy that my compose key is not working correctly. Going into gnome-control-center -> Keyboard, I see that 'Alternate Characters Key' and 'Compose Key' are both set to Right Alt. Setting Alternate Characters Key to None, and moving the Compose Key setting around between different options (and then back to Right Alt), the behavior of the Right Alt key is still AltGr and not Compose. From xev: KeyPress event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242336, (310,502), root:(434,617), state 0x10, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 37, synthetic NO, window 0x401, root 0x50e, subw 0x0, time 287242456, (310,502), root:(434,617), state 0x90, keycode 108 (keysym 0xfe03, ISO_Level3_Shift), same_screen YES, XKeysymToKeycode returns keycode: 92 XLookupString gives 0 bytes: XFilterEvent returns: False ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu12 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Apr 18 16:01:10 2022 InstallationDate: Installed on 2019-12-23 (847 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-04-15 (3 days ago) ** Affects: xkeyboard-config (Ubuntu) Importance: Medium Status: Confirmed ** Tags: amd64 apport-bug jammy rls-jj-incoming -- Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout https://bugs.launchpad.net/bugs/1969396 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xkeyboard-config in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1877194 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969291] Re: apport-collect & ubuntu-bug failing to switch to firefox
** Tags added: lubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1969291 Title: apport-collect & ubuntu-bug failing to switch to firefox Status in apport package in Ubuntu: New Bug description: In attempting to file a bug report on Lubuntu jammy ISO (QA-test installed yesterday using ISO 2020-04-15) -- guiverc@dc7700-2re:~$ apport-collect 1969290 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://launchpad.net/+authorize-token?oauth_token=6K7rwSbKHlbLWmkK65sj_permission=DESKTOP_INTEGRATION' --- On attempting to file using `ubuntu-bug apport` --- guiverc@dc7700-2re:~$ ubuntu-bug apport *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. . *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (5.0 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s *** Uploading problem information The collected information is being sent to the bug tracking system. This might take a few minutes. 96% *** To continue, you must visit the following URL: https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8? You can launch a browser now, or copy this URL into a browser on another computer. Choices: 1: Launch a browser now C: Cancel Please choose (1/C): 1 /usr/bin/xdg-open: 882: firefox: not found /usr/bin/xdg-open: 882: firefox: not found xdg-open: no method available for opening 'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/02e65c1c-bdf7-11ec-a167-40a8f03099c8?' --- ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: apport 2.20.11-0ubuntu82 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sun Apr 17 12:34:57 2022 InstallationDate: Installed on 2022-04-16 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220415) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969291/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1926906] Re: (Ubuntu 21.04) RPi4 audio is slow and crackling
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 ** This bug is no longer a duplicate of bug 1899962 Wrong audio output device selected on Raspberry Pi Desktop ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1926906 Title: (Ubuntu 21.04) RPi4 audio is slow and crackling Status in pulseaudio package in Ubuntu: New Bug description: I'm using a Raspberry Pi 4. After updating from Ubuntu 20.10 to 21.04, I noticed audio problems. The sound is slow and crackling. I'm using the headphone jack and the config.txt option: dtparam=audio=on If I start a video or audio file in VLC player and select the VLC options: Audio: Output module: ALSA Audio Output Device: bcm2835 Headphones, bcm2835 Headphones Default Audio Device Then the playback speed seems to be normal but the "electric" crackling in voices remains. And system-wide the problem persists, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1926906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
*** This bug is a duplicate of bug 1877194 *** https://bugs.launchpad.net/bugs/1877194 Looks like this fell off my radar, but looking at vanvugt's comment this is indeed a duplicate of bug 1877194 (and still occurs in Jammy). I'll mark it as such ** This bug has been marked a duplicate of bug 1877194 switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: Expired Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
>If direct access to Launchpad is blocked how was a bug report filed in the first place? Clicking the "Report a Bug" link on any project's page in LP. This is done from a machine outside of the airgapped or restricted access lab where the hardware sits. Also, I should point out (which I mentioned originally) that one can, and I'll also start suggesting they do this, use --save with ubuntu-bug to create a bug report that can be submitted later from a different machine. I'm just asking to have apport-collect also feature this... Perhaps the solution since, as you pointed out, apport needs to read the bug to know which package to collect files for, is to require the package as part of the commmand... e.g. apport-collect --save=/path/to/filename --package=$PACKAGE $BUG_NUMBER -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection Status in apport package in Ubuntu: Incomplete Bug description: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
If direct access to Launchpad is blocked how was a bug report filed in the first place? apport-collect is designed to gather information from a system about an existing bug report. Additionally, apport-collect looks at the bug report in Launchpad to determine which package is affected and to to determine which apport-package hook to run. Without the connection Launchpad only general information about the system would be gathered. ** Changed in: apport (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection Status in apport package in Ubuntu: Incomplete Bug description: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969477] [NEW] apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection
Public bug reported: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1969477 Title: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection Status in apport package in Ubuntu: New Bug description: We very often tell our hardware partners to "file a bug" when they encounter issues. This requires them to run apport-collect to gather and submit logs for the bug. However, very often, the hardware that has the problem is in a lab that has tight security restrictions and direct access to launchpad is blocked. This makes it nearly impossible for them to gather any requested logs, since apport-collect requires a direct line to Launchpad. apport-collect needs to adopt the --save feature of apport-bug/ubuntu- bug to save the prescribed logs and system data in a tarball that can then be attached to a bug after the fact. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: apport 2.20.11-0ubuntu27.23 ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166 Uname: Linux 5.4.0-100-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl icp nvidia_modeset zcommon znvpair nvidia ApportLog: ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 19 10:25:54 2022 InstallationDate: Installed on 2016-02-11 (2258 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
I'm working on a SRU for apparmor and evince to introduce the snap_browsers abstraction on apparmor as a workaround for this issue. It is based on these two merge requests from upstream: https://gitlab.com/apparmor/apparmor/-/merge_requests/806 https://gitlab.com/apparmor/apparmor/-/merge_requests/877 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
it sounds like something that we should fix one way or another at least for the LTS, maybe in the futur we will have evince as a snap instead and the situation will be different. Could you suggest a patch for review with the change you described? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap Status in apparmor package in Ubuntu: Confirmed Status in evince package in Ubuntu: Triaged Status in evince package in Debian: New Bug description: This is related to bug #1792648. After fixing that one (see discussion at https://salsa.debian.org/gnome-team/evince/merge_requests/1), clicking a hyperlink in a PDF opens it correctly if the default browser is a well-known application (such as /usr/bin/firefox), but it fails to do so if the default browser is a snap (e.g. the chromium snap). This is not a recent regression, it's not working on bionic either. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: evince 3.30.0-2 ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5 Uname: Linux 4.18.0-7-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 24 12:28:06 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2016-07-02 (813 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: evince UpgradeStatus: Upgraded to cosmic on 2018-09-14 (9 days ago) modified.conffile..etc.apparmor.d.abstractions.evince: [modified] mtime.conffile..etc.apparmor.d.abstractions.evince: 2018-09-24T11:35:41.904158 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1959475] Re: "machinectl shell" connections immediately terminated
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1959475 Title: "machinectl shell" connections immediately terminated Status in systemd package in Ubuntu: Confirmed Bug description: The command "machinectl shell" does not work in systemd 249.9-0ubuntu2: $ sudo machinectl shell ns-xxx Connected to machine ns-xxx. Press ^] three times within 1s to exit session. Connection to machine ns-xxx terminated. The issue seems to be described here: https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899 https://github.com/systemd/systemd/issues/22234 and solved here: https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969475] [NEW] package linux-image-5.14.0-1033-oem 5.14.0-1033.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Found linux image: /boot/vmlinuz-5.14.0-1032-oem Found initrd image: /boot/initrd.img-5.14.0-1032-oem Found linux image: /boot/vmlinuz-5.14.0-1031-oem Found initrd image: /boot/initrd.img-5.14.0-1031-oem Adding boot menu entry for UEFI Firmware Settings done Processing triggers for linux-image-5.14.0-1033-oem (5.14.0-1033.36) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.14.0-1033-oem ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.14.0-1033-oem I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. xz: (stdout): Write error: No space left on device E: mkinitramfs failure xz --check=crc32 --threads=0 1 update-initramfs: failed for /boot/initrd.img-5.14.0-1033-oem with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.14.0-1033-oem (--configure): installed linux-image-5.14.0-1033-oem package post-installation script subprocess returned error ex it status 1 Errors were encountered while processing: linux-image-5.14.0-1033-oem E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1033-oem 5.14.0-1033.36 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 19 08:07:10 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2022-03-11 (39 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: initramfs-tools Title: package linux-image-5.14.0-1033-oem 5.14.0-1033.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1969475 Title: package linux-image-5.14.0-1033-oem 5.14.0-1033.36 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: Found linux image: /boot/vmlinuz-5.14.0-1032-oem Found initrd image: /boot/initrd.img-5.14.0-1032-oem Found linux image: /boot/vmlinuz-5.14.0-1031-oem Found initrd image: /boot/initrd.img-5.14.0-1031-oem Adding boot menu entry for UEFI Firmware Settings done Processing triggers for linux-image-5.14.0-1033-oem (5.14.0-1033.36) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 5.14.0-1033-oem ...done. /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.14.0-1033-oem I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/vgubuntu-swap_1) I: Set the RESUME variable to override this. xz: (stdout): Write error: No space left on device E: mkinitramfs failure xz --check=crc32 --threads=0 1 update-initramfs: failed for /boot/initrd.img-5.14.0-1033-oem with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 dpkg: error processing package linux-image-5.14.0-1033-oem (--configure): installed linux-image-5.14.0-1033-oem package post-installation script subprocess returned error ex it status 1 Errors were encountered while processing: linux-image-5.14.0-1033-oem E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1033-oem 5.14.0-1033.36 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Apr 19 08:07:10 2022 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Description changed: - 1) Ubuntu 22.04 - 2) software-properties-gtk 0.99.22 - 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 - 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. + 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu + Ubuntu 22.04 + + 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center + software-properties-gtk 0.99.22 + + 3) What you expected to happen + No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 + It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. + + 4) What happened instead + It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969460] [NEW] software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
Public bug reported: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Tags: jammy oem-priority wayland-session ** Attachment added: "_usr_bin_software-properties-gtk.1001.crash" https://bugs.launchpad.net/bugs/1969460/+attachment/5581435/+files/_usr_bin_software-properties-gtk.1001.crash ** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: New Bug description: 1) Ubuntu 22.04 2) software-properties-gtk 0.99.22 3) No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 4) It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968876] Re: ssh-agent: Error connecting to agent: Connection refused
I tried reproducing the issue on a Rpi4, cloning a repository via ssh using pubkey authentication with a rsa2048 key stored in ssh-agent, it worked fine. If you believe there's actually a bug here please provide some steps we can follow to reproduce the issue from a clean Jammy system, and we'll look into this again. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1968876 Title: ssh-agent: Error connecting to agent: Connection refused Status in openssh package in Ubuntu: Incomplete Bug description: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: openssh 1:8.9p1-3 Architecture: arm64 CasperMD5CheckResult: pass CurrentDesktop: MATE raspberry pi 4. The keys are added, but for example, when cloning a repository via ssh, the ssh agent crashes, restarting does not help, the repository is not cloned. When launch the command ssh-add -L Error connecting to agent: Connection refused. I rolled back to the package version 1: 8.8p1-1 and everything works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1968876/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install Status in vim package in Ubuntu: New Bug description: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory I discovered this because my .selected-editor was vim.tiny after running crontab -e $ crontab -e Select an editor. To change later, run 'select-editor'. 1. /bin/nano< easiest 2. /usr/bin/vim.tiny 3. /bin/ed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
the recent update suggests the white rendering was indeed bug #1966418 which is resolved now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
It seems that view, as provided by vim.tiny now attempts to load defaults.vim, which is shipped in the large vim-runtime package. All vims depend on vim-common. It would seem to me that we should move defaults.vim from vim-runtime to vim-common. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install Status in vim package in Ubuntu: New Bug description: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory I discovered this because my .selected-editor was vim.tiny after running crontab -e $ crontab -e Select an editor. To change later, run 'select-editor'. 1. /bin/nano< easiest 2. /usr/bin/vim.tiny 3. /bin/ed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968461] Re: sudo apt install crashes computer
Not an apt bug in either case if it crashes your system ** Package changed: apt (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968461 Title: sudo apt install crashes computer Status in Ubuntu: Fix Released Bug description: On Ubuntu 22.04, when installing software, especially when it hits snap, it will crash the computer. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Apr 10 02:31:17 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-04-07 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity Symptom: installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1968461/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install
I also noticed this by launching "view /var/log/installer/syslog" on a freshly installed Ubuntu desktop system. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to vim in Ubuntu. https://bugs.launchpad.net/bugs/1968912 Title: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install Status in vim package in Ubuntu: New Bug description: Ubuntu 22.04 When running vim.tiny it says: $ vim.tiny E1187: Failed to source defaults.vim Press ENTER or type command to continue This is due to the defaults.vim file not being available. If you just run it as vi $ vi this message does not appear as vim.tiny runs in compatibility mode. I found mention of this issue in: https://github.com/grml/grml-etc-core/issues/99 The defaults.vim file is provided by the package vim-runtime. I'm unsure what the issue is, if something needs to be in /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg claims vimrc is in vim-common, but no file is installed for me from that package, or if vim-runtime needs to be a required package for vim-tiny $ dpkg -S /etc/vim/vimrc vim-common: /etc/vim/vimrc $ ls -al /etc/vim/vimrc ls: cannot access '/etc/vim/vimrc': No such file or directory I discovered this because my .selected-editor was vim.tiny after running crontab -e $ crontab -e Select an editor. To change later, run 'select-editor'. 1. /bin/nano< easiest 2. /usr/bin/vim.tiny 3. /bin/ed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: vim-tiny 2:8.2.3995-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30 Uname: Linux 5.15.0-1005-raspi aarch64 ApportVersion: 2.20.11-0ubuntu81 Architecture: arm64 CasperMD5CheckResult: unknown Date: Wed Apr 13 11:56:35 2022 ImageMediaBuild: 20201022 ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: vim UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop
Another quick update: in recent days we've gone from "blank white space" back to "incorrect stride corruption" in all documented cases (embedded browsers, help windows, MiniBrowser, etc). I note in the dpkg logs, libglx-mesa0 got updated a few days ago, but unfortunately I'm unsure exactly when the change occurred so this is speculation on my part. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1924251 Title: Embedded browser display corruption under Wayland on Pi desktop Status in gtk+3.0 package in Ubuntu: Confirmed Status in webkit2gtk package in Ubuntu: Confirmed Status in yelp package in Ubuntu: Confirmed Bug description: On the hirsute Pi desktop, under a wayland session with the "full" KMS overlay enabled, and "kms-modifiers" present in the org.gnome.mutter/experimental-features, the body of a window containing an HTML renderer (e.g. help text or a login page) displays corruption. These reproduction cases may not be entirely reliable given that *some* pages appear to render correctly, but I'll include a couple in the hopes of making it reliably reproducible: 1. Open the Lights Off game 2. Select "Help" from the menu 3. In the help window that appears, select any link "Basics", "Rules", and "Strategy" all reliably reproduce the issue for me, but "Help Translate" doesn't so you may need to click around some links until the corruption appears -- however, once it does even navigating back to the prior page which rendered happily now displays the same corruption. Another reproduction case: 1. Open the Settings application 2. Select the Online Applications option from the left 3. Select the Google entry in the list 4. The login window that appears always displays corruption for me The Microsoft option always reliably corrupts for me, but the Facebook one doesn't so again I wonder how reproducible this may be for others (might be worth trying several options if the first doesn't display corruption). The corruption appears in the form of "shredded" content as if a horizontal stride is set incorrectly somewhere, but only appears in the body of the window; the window decorations are unaffected. I'll attach a screenshot of the corrupted help window to illustrate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
[Impact] * Cannot use ucf to install templated configuration when using dpkg-divert with the destination config file * Affects various packages including dovecot and any custom config packages using both config-package-dev and ucf [Test Plan] * Create a config-package-dev based config-packagename.deb to replace existsing config * Include a line in the postinst in the config.deb to install a template for a config file also spcified in the displace file (which is therefore diverted by dpkg-divert) [Where problems could occur] * Any issue with patch may cause issues with packages installing config via ucf (this includes dovecot, openssh-server, php7.4, gdm3) [Other Info] * Tested with config-package-dev rolled config deb package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
Divert related fixes from ucf 3.0040 and also from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354 Allows ucf to work when using dpkg-divert or config-package-dev for diverts eg ucf --three-way ucfr Tested and working as expected Note: ucf does not working with --debconf-ok flag (both with and without patch) ** Bug watch added: Debian Bug tracker #979354 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354 ** Patch added: "ucf-3.0038-divertfix.patch" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5581412/+files/ucf-3.0038-divertfix.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891110] Re: Focal ucf need redirect fixes backported to ensure working with config-package-dev
** Patch removed: "patches from ucf 3.0040 to fix diversions issue with config-package-dev" https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+attachment/5400552/+files/honor-dpkg-diversions-1+2+3.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ucf in Ubuntu. https://bugs.launchpad.net/bugs/1891110 Title: Focal ucf need redirect fixes backported to ensure working with config-package-dev Status in ucf package in Ubuntu: Fix Released Status in ucf source package in Focal: Incomplete Status in ucf package in Debian: Fix Released Bug description: When using config-package-dev and diverting config files for packages that use ucf to manage installation of their config files, this patch is necessary to ensure config files are correctly diverted. Please apply to upstream Focal UCF package To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/1891110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels
unattended-upgrades in jammy did not need a change, we'll see if SRUs will need changes, hence keeping the task so we can add them later on without having to reset to launchpad API shenanigans. ** Description changed: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable - unattended-upgrades needs changes to its test suite to accommodate this. + unattended-upgrades may need changes to its test suite to accommodate + this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. ** Changed in: unattended-upgrades (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1968154 Title: Only keep 2 kernels Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Invalid Bug description: [Impact] APT currently keeps 3 kernels or even 4 in some releases. Our boot partition is sized for a steady state of 2 kernels + 1 new one being unpacked, hence users run out of space and new kernels fail to install, upgrade runs might abort in the middle. It's not nice. [Test plan] 1. Have two kernels installed (let's call them version 3, 2) 2. Check that both kernels are not autoremovable 3. Install an old kernel (let's call it 1), and mark it automatic 4. Check that 1 will be autoremovable (apt autoremove -s) 5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s) 6. Actually remove 2 7. Reboot into 3 and check that both 1 and 3 are now not autoremovable unattended-upgrades may need changes to its test suite to accommodate this. [Where problems could occur] We could keep the wrong kernels installed that the user did not expect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1968154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969189] Re: I CANT INSTALL NVIDIA
Thanks for the bug report. Please open the 'Additional Drivers' app to install the correct Nvidia driver. If you still have problems after that then please explain what the issue is in more detail. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969189 Title: I CANT INSTALL NVIDIA Status in Ubuntu: Incomplete Bug description: i need install nvidia RTX2060 in my ubuntu 20.04LTS ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 15 08:47:19 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.103.01, 5.13.0-39-generic, x86_64: built openrazer-driver, 3.3.0, 5.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b8] NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. TU106 [GeForce RTX 2060 SUPER] [1043:870b] InstallationDate: Installed on 2022-03-31 (14 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) MachineType: Dell Inc. Latitude 5400 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-39-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2022 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0PD9KD dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd02/10/2022:br1.16:svnDellInc.:pnLatitude5400:pvr:rvnDellInc.:rn0PD9KD:rvrA00:cvnDellInc.:ct10:cvr:sku08B8: dmi.product.family: Latitude dmi.product.name: Latitude 5400 dmi.product.sku: 08B8 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1969189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()
Hi Shyam, I am closer to getting this to work on 22.04 (22.10 should be easier once we've sorted out 22.04). I'll be off this week (tomorrow onward!) and will definitely have something for you by the next week. Let me know if you have any questions or concerns. TIA. \o/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to keyutils in Ubuntu. https://bugs.launchpad.net/bugs/1962453 Title: Apply default TTL to records obtained from getaddrinfo() Status in keyutils package in Ubuntu: Fix Released Status in keyutils source package in Bionic: Fix Released Status in keyutils source package in Focal: Incomplete Status in keyutils source package in Impish: Incomplete Bug description: [Impact] There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for DNS resolution. The keyutils package contains the userspace utility to update the kernel keyring with the DNS mapping to IP address. Prior to 1.6.2, this utility may erroneously set unlimited lifetime for this keyring in the kernel. [Test plan] === 1. Create a file share on an SMB server (can be a samba server) with two IP addresses. Make sure that FQDN of the server resolves to one of these addresses. 2. mount the created share on the cifs client using the FQDN for the server. Make sure that the mount point is accessible. 3. Using the ss command on the client, to kill the sockets that connect to the server: sudo ss -K dport :445 4. Now update the DNS entry to make sure that the server FQDN now resolves to the second IP address of the server. Make sure that nslookup on the client now resolves to the new IP address. 5. Repeat step 3 to kill the sockets that connect to server to force re-connection again. Without the fix, after step 5, with the "ss -t" command, you'll see that the client has reconnected to the old IP address, even when DNS lookups return the new IP. With the fix (after a reboot of the client machine to make sure that kernel keys are refreshed), you'll see that the client reconnects to the new IP address. The bug is due to unlimited lifetime set by key.dns_resolver (which is part of keyutils package). As a result, even if IP address for the DNS entries change, the kernel filesystems would continue to use old IP address, due to the cached keys. This issue causes clients to misbehave when Azure Files service endpoints move to a different cluster. [Where problems could occur] Address records obtained from getaddrinfo() don't come with any TTL information, even if they're obtained from the DNS, so if someone is relying on this particularly, might face some problem/regression but I don't think they would face that as it would still be highly configurable. [Other information] === This request is essentially from one of our cloud partners and they're highly affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1969305] Re: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well
What file or binary package does this bug report related to? Also what version of Ubuntu are you using? ** Changed in: xorg (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1969305 Title: Export XDG_CONFIG_HOME and XDG_DATA_HOME as well Status in xorg package in Ubuntu: Incomplete Bug description: These base directories should also be included to make scripting easier. Their default values should be set as per XDG base-dir spec, i.e.: XDG_CONFIG_HOME="$HOME/.config" XDG_DATA_HOME="$HOME/.local/share" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969305/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
