[Touch-packages] [Bug 1913571] Re: apt autoremove does not remove old kernel
The kernel version 5.8.0-38.43 is indeed marked as manually installed,
though I never installed a kernel manually, only installed new kernels
during apt full-upgrade. However, the problem is now solved. Thank you
so much for your time looking at this, have a great time!
--
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/1913571
Title:
apt autoremove does not remove old kernel
Status in apt package in Ubuntu:
Incomplete
Bug description:
Ubuntu 20.10
Apt version 2.1.10ubuntu0.2
Here the content of /etc/apt/01autoremove-kernels:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-.*-5\.8\.0-40-lowlatency$";
"^linux-.*-5\.8\.0-41-lowlatency$";
"^kfreebsd-.*-5\.8\.0-40-lowlatency$";
"^kfreebsd-.*-5\.8\.0-41-lowlatency$";
"^gnumach-.*-5\.8\.0-40-lowlatency$";
"^gnumach-.*-5\.8\.0-41-lowlatency$";
"^.*-modules-5\.8\.0-40-lowlatency$";
"^.*-modules-5\.8\.0-41-lowlatency$";
"^.*-kernel-5\.8\.0-40-lowlatency$";
"^.*-kernel-5\.8\.0-41-lowlatency$";
};
/* Debug information:
# dpkg list:
rc linux-image-5.8.0-25-lowlatency 5.8.0-25.26
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-29-lowlatency 5.8.0-29.31
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-31-lowlatency 5.8.0-31.33
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-33-lowlatency 5.8.0-33.36
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-34-lowlatency 5.8.0-34.37
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-36-lowlatency 5.8.0-36.40
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-38-lowlatency 5.8.0-38.43
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-40-lowlatency 5.8.0-40.45
amd64Signed kernel image lowlatency
iF linux-image-5.8.0-41-lowlatency 5.8.0-41.46
amd64Signed kernel image lowlatency
ii linux-image-lowlatency5.8.0.41.45
amd64lowlatency Linux kernel image
# list of installed kernel packages:
5.8.0-38-lowlatency 5.8.0-38.43
5.8.0-40-lowlatency 5.8.0-40.45
5.8.0-41-lowlatency 5.8.0-41.46
# list of different kernel versions:
5.8.0-41.46
5.8.0-40.45
5.8.0-38.43
# Installing kernel: 5.8.0-41.46 (5.8.0-41-lowlatency)
# Running kernel: 5.8.0-40.45 (5.8.0-40-lowlatency)
# Last kernel: 5.8.0-41.46
# Previous kernel: 5.8.0-40.45
# Kernel versions list to keep:
5.8.0-40.45
5.8.0-41.46
# Kernel packages (version part) to protect:
5\.8\.0-40-lowlatency
5\.8\.0-41-lowlatency
*/
Running sudo apt autoremove results in:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It worked properly in previous versions of apt, but since upgrade to
apt version 2.1.10ubuntu0.2 I seem to be unable to autoremove old
kernels. I expect the kernel version 5.8.0-38.43 to be removed with
the autoremove command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1913571/+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 1859610] Re: python-gi/arm64 segfaults with the focal-proposed libffi version
** Changed in: libffi (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: libffi (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libffi in Ubuntu. https://bugs.launchpad.net/bugs/1859610 Title: python-gi/arm64 segfaults with the focal-proposed libffi version Status in libffi package in Ubuntu: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in libffi source package in Focal: Fix Released Status in pygobject source package in Focal: Fix Released Bug description: Testcase, on focal/arm64 $ sudo apt install python3-goocalendar $ python3 -c "import goocalendar ; print(goocalendar.__version__)" -> works fine install the python3-gi package from focal-proposed it segfaults in libffi Program received signal SIGSEGV, Segmentation fault. 0x in ?? () (gdb) bt #0 0x in ?? () #1 0xf7390ff8 in ffi_call_SYSV () at ../src/aarch64/sysv.S:114 #2 0xf7390634 in ffi_call_int (cif=0xa12d78, fn=, orig_rvalue=, avalue=0x0, closure=) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1859610/+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 1913629] [NEW] adduser: \/usr/bin/chfn -f systemd Time Synchronization systemd-timesync' returned error code 1. Exiting.`
Public bug reported: Hello to everyone. Actually I'm trying to run X86 applications on my Jetson Nano using qemu and debootstrapping debian 9 on ubuntu 18.04 for arm64,but it seems that an old bug that it seems to be fixed here but it's not : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745082 This is what I did to achieve my goal : sudo apt-get update apt-get install qemu qemu-user qemu-user-static binfmt-support debootstrap binutils debootstrap --foreign --arch i386 stretch ./chroot-stretch-i386/ and this is what happens : http://ftp.us.debian.org/debian W: Cannot check Release signature; keyring file not available /usr/share/keyrings/debian-archive-keyring.gpg I: Retrieving InRelease I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Found additional required dependencies: libaudit-common libaudit1 libbz2-1.0 libcap-ng0 libdb5.3 libdebconfclient0 libgcrypt20 libgpg-error0 liblz4-1 libncursesw5 libsemanage-common libsemanage1 libsystemd0 libudev1 libustr-1.0-1 I: Found additional base dependencies: dmsetup gnupg-agent libapparmor1 libassuan0 libbsd0 libcap2 libcryptsetup4 libdevmapper1.02.1 libdns-export162 libelf1 libfastjson4 libffi6 libgmp10 libgnutls30 libhogweed4 libidn11 libidn2-0 libip4tc0 libip6tc0 libiptc0 libisc-export160 libksba8 liblocale-gettext-perl liblognorm5 libmnl0 libncurses5 libnetfilter-conntrack3 libnettle6 libnfnetlink0 libnpth0 libp11-kit0 libpsl5 libseccomp2 libsqlite3-0 libtasn1-6 libtext-charwidth-perl libtext-iconv-perl libtext-wrapi18n-perl libunistring0 libxtables12 pinentry-curses xxd I: Checking component main on http://ftp.us.debian.org/debian... I: Retrieving libacl1 2.2.52-3+b1 . I: Extracting zlib1g... At this point I've mounted the partitions : sudo mount -t sysfs /sys/ ./chroot-stretch-i386/sys/ sudo mount -t proc /proc/ ./chroot-stretch-i386/proc/ sudo mount --bind /dev ./chroot-stretch-i386/dev/ sudo mount --bind /dev/pts ./chroot-stretch-i386/dev/pts/ sudo mount --bind /dev/shm ./chroot-stretch-i386/dev/shm/ and I've copied the qemu static on the chrooted debian i386 folder : cp /usr/bin/qemu-i386-static ./chroot-stretch-i386/usr/bin and I've started the second stage of debootstrap : root@ziomario-desktop:~/Scrivania/qemu-x86# sudo chroot ./chroot-stretch-i386/ /debootstrap/debootstrap --second-stage at some point this is what happens : libc6 is not installed ; libdebconfclient0 is not installed ; awk is not installed ; libbz2-1.0 is not installed ; libc6 is not installed ; liblzma5 is not installed ; libselinux1 is not installed ; zlib1g is not installed ; tar is not installed ; libgcc1 is not installed ; dash is not installed ; libtinfo5 is not installed ; libblkid1 is not installed ; libcomerr2 is not installed ; libss2 is not installed ; libuuid1 is not installed ; util-linux is not installed ; libpcre3 is not installed ; libpam0g is not installed ; libpam-modules-bin is not installed. Adding group \systemd-journal' (GID 101) ...` Done. at this point I saw the error that should have been fixed : chfn: PAM: System error adduser: \/usr/bin/chfn -f systemd Time Synchronization systemd- timesync' returned error code 1. Exiting.` dpkg: error processing package systemd (--install): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin (2.24-11+deb9u4) ... Errors were encountered while processing: systemd W: Failure trying to run: dpkg --force-overwrite --force-confold --skip-same-version --install /var/cache/apt/archives/adduser_3.115_all.deb /var/cache/apt/archives/libapparmor1_2.11.0-3+deb9u2_i386.deb /var/cache/apt/archives/libcryptsetup4_2%3a1.7.3-4_i386.deb /var/cache/apt/archives/libip4tc0_1.6.0+snapshot20161117-6_i386.deb /var/cache/apt/archives/libkmod2_23-2_i386.deb /var/cache/apt/archives/libcap2_1%3a2.25-1_i386.deb /var/cache/apt/archives/libidn11_1.33-1+deb9u1_i386.deb /var/cache/apt/archives/libseccomp2_2.3.1-2.1+deb9u1_i386.deb /var/cache/apt/archives/dmsetup_2%3a1.02.137-2_i386.deb /var/cache/apt/archives/libdevmapper1.02.1_2%3a1.02.137-2_i386.deb /var/cache/apt/archives/libncurses5_6.0+20161126-1+deb9u2_i386.deb /var/cache/apt/archives/libprocps6_2%3a3.3.12-3+deb9u1_i386.deb /var/cache/apt/archives/procps_2%3a3.3.12-3+deb9u1_i386.deb /var/cache/apt/archives/systemd_232-25+deb9u12_i386.deb W: See //debootstrap/debootstrap.log for details (possibly the package systemd is at fault) u can find the full log here : https://pastebin.com/XwkQp91Y what to do ? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1913629 Title: adduser: \/usr/bin/chfn -f systemd Time Synchronization systemd- timesync' returned error
[Touch-packages] [Bug 1913632] [NEW] Ubuntu 20.10 Pulseaudio won't recognize audio line-out until pulseaudio restarted
Public bug reported: Ubuntu 20.10 (PopOS on a custom Skylake generation server, not System76) Problem started occurring after upgrade from Ubuntu 20.04 to Ubuntu 20.10 PopOS. System never experienced this problem before that upgrade and it's a 5 year old server. Pulseaudio does not recognize speakers attached to green line-out port of built-in analog card. This is temporarily corrected by restarting pulseaudio service. However, upon next reboot the problem reoccurs. Thus, requiring a pulseaudio restart after every reboot. To reproduce problem: 1. Speakers plugged in (through green line-out port of built-in card) and speakers are powered on 2. Restart Linux (either after hard power off, or reset, or soft reboot, doesn't matter. BIOS changes do nothing.) 3. System comes up, and pulseaudio dashboard shows no built-in analog stereo under "Output Devices" 4. Restart pulseaudio: systemctl --user restart pulseaudio.service 5. Pulseaudio dashboard now shows built-in analog stereo under "Output Devices" CONFIGURATION INFORMATION: cat /etc/issue Pop!_OS 20.10 uname -a Linux walkubu 5.8.0-7630-generic #32~1609193707~20.10~781bb80-Ubuntu SMP Tue Jan 5 21:29:56 UTC 2 x86_64 x86_64 x86_64 GNU/Linux arecord -L null Discard all samples (playback) or generate zero samples (capture) default Playback/recording through the PulseAudio sound server samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open Sound System pulse PulseAudio Sound Server upmix Plugin for channel upmix (4,6,8) vdownmix Plugin for channel downmix (stereo) with a simple spacialization hw:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Hardware device with all software conversions sysdefault:CARD=PCH HDA Intel PCH, ALC1150 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Front output / input dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Direct sample snooping device usbstream:CARD=PCH HDA Intel PCH USB Stream Output hw:CARD=C525,DEV=0 HD Webcam C525, USB Audio Direct hardware device without any conversions plughw:CARD=C525,DEV=0 HD Webcam C525, USB Audio Hardware device with all software conversions sysdefault:CARD=C525 HD Webcam C525, USB Audio Default Audio Device front:CARD=C525,DEV=0 HD Webcam C525, USB Audio Front output / input dsnoop:CARD=C525,DEV=0 HD Webcam C525, USB Audio Direct sample snooping device usbstream:CARD=C525 HD Webcam C525 USB Stream Output usbstream:CARD=NVidia HDA NVidia USB Stream Output ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1913632 Title: Ubuntu 20.10 Pulseaudio won't recognize audio line-out until pulseaudio restarted Status in systemd package in Ubuntu: New Bug description: Ubuntu 20.10 (PopOS on a custom Skylake generation server, not System76) Problem started occurring after upgrade from Ubuntu 20.04 to Ubuntu 20.10 PopOS. System never experienced this problem before that upgrade and it's a 5 year old server. Pulseaudio does not recognize speakers attached to green line-out port of built-in analog card. This is temporarily corrected by restarting pulseaudio service. However, upon next reboot the problem reoccurs. Thus, requiring a pulseaudio restart after every reboot. To reproduce problem: 1. Speakers plugged in (through green line-out port of built-in card) and speakers are powered on 2. Restart Linux (either after hard power off, or reset, or soft reboot, doesn't matter. BIOS changes do nothing.) 3. System comes up, and pulseaudio dashboard shows no built-in analog stereo under "Output Devices" 4. Restart pulseaudio: systemctl --user restart pulseaudio.service 5. Pulseaudio dashboard now shows built-in analog stereo under "Output Devices" CONFIGURATION INFORMATION: cat /etc/issue Pop!_OS 20.10 uname -a Linux walkubu 5.8.0-7630-generic #32~1609193707~20.10~781bb80-Ubuntu SMP Tue Jan 5 21:29:56 UTC 2 x86_64 x86_64 x86_64 GNU/Linux arecord -L null Discard all samples (playback) or generate zero samples (capture) default Playback/recording through the PulseAudio sound server samplerate Rate Converter Plugin Using Samplerate Library
[Touch-packages] [Bug 1884932] Re: Install pulseaudio-module-gsettings by default
** Changed in: ubuntu-meta (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1884932 Title: Install pulseaudio-module-gsettings by default Status in ubuntu-meta package in Ubuntu: Invalid Bug description: It provides a very useful settings to switch all running streams when a new output becomes available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1884932/+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 1908903] Re: Replace pulseaudio with pipewire
** Changed in: ubuntu-meta (Ubuntu) Status: New => Incomplete ** Changed in: ubuntu-meta (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1908903 Title: Replace pulseaudio with pipewire Status in ubuntu-meta package in Ubuntu: Invalid Bug description: Pipewire is clearly better at supporting bluetooth codecs and have drop-in support for pulseaudio https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/249 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/227 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1908903/+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 1913482] Re: Update tzdata to version 2021a
Verification for Bionic:
bdmurray@clean-bionic-amd64:~$ apt-cache policy tzdata
tzdata:
Installed: 2021a-0ubuntu0.18.04
Candidate: 2021a-0ubuntu0.18.04
Version table:
*** 2021a-0ubuntu0.18.04 500
500 http://ubuntu.osuosl.org/ubuntu bionic-proposed/main amd64 Packages
500 http://ubuntu.osuosl.org/ubuntu bionic-proposed/main i386 Packages
100 /var/lib/dpkg/status
2020f-0ubuntu0.18.04 500
500 http://ubuntu.osuosl.org/ubuntu bionic-updates/main amd64 Packages
500 http://ubuntu.osuosl.org/ubuntu bionic-updates/main i386 Packages
500 http://ubuntu.osuosl.org/ubuntu bionic-security/main amd64 Packages
500 http://ubuntu.osuosl.org/ubuntu bionic-security/main i386 Packages
2018d-1 500
500 http://ubuntu.osuosl.org/ubuntu bionic/main amd64 Packages
500 http://ubuntu.osuosl.org/ubuntu bionic/main i386 Packages
bdmurray@clean-bionic-amd64:~$ zdump -v Africa/Juba | grep 2021
Africa/Juba Sun Jan 31 20:59:59 2021 UT = Sun Jan 31 23:59:59 2021 EAT isdst=0
gmtoff=10800
Africa/Juba Sun Jan 31 21:00:00 2021 UT = Sun Jan 31 23:00:00 2021 CAT isdst=0
gmtoff=7200
System V Test Case:
bdmurray@clean-bionic-amd64:~$ diff <(zdump -v America/Phoenix | cut -d' '
-f2-) <(zdump -v SystemV/MST7 | cut -d' ' -f2-)
bdmurray@clean-bionic-amd64:~$
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
Verification for Xenial:
(xenial-amd64)root@impulse:~# apt-cache policy tzdata
tzdata:
Installed: 2021a-0ubuntu0.16.04
Candidate: 2021a-0ubuntu0.16.04
Version table:
*** 2021a-0ubuntu0.16.04 500
500 http://ubuntu.osuosl.org/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
2020f-0ubuntu0.16.04 500
500 http://ubuntu.osuosl.org/ubuntu xenial-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64
Packages
2016d-0ubuntu0.16.04 500
500 http://ubuntu.osuosl.org/ubuntu xenial/main amd64 Packages
(xenial-amd64)root@impulse:~# zdump -v Africa/Juba | grep 2021
Africa/Juba Sun Jan 31 20:59:59 2021 UT = Sun Jan 31 23:59:59 2021 EAT isdst=0
gmtoff=10800
Africa/Juba Sun Jan 31 21:00:00 2021 UT = Sun Jan 31 23:00:00 2021 CAT isdst=0
gmtoff=7200
(xenial-amd64)root@impulse:~# diff <(zdump -v America/Phoenix | cut -d' ' -f2-)
<(zdump -v SystemV/MST7 | cut -d' ' -f2-)
(xenial-amd64)root@impulse:~#
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
tzdata verification on groovy:
bdmurray@clean-groovy-amd64:~$ zdump -v Africa/Juba | grep 2021
bdmurray@clean-groovy-amd64:~$ apt-cache policy tzdata
tzdata:
Installed: 2021a-0ubuntu0.20.10
Candidate: 2021a-0ubuntu0.20.10
Version table:
*** 2021a-0ubuntu0.20.10 500
500 http://192.168.10.7/ubuntu groovy-proposed/main amd64 Packages
500 http://192.168.10.7/ubuntu groovy-proposed/main i386 Packages
100 /var/lib/dpkg/status
2020f-0ubuntu0.20.10.1 500
500 http://192.168.10.7/ubuntu groovy-updates/main amd64 Packages
500 http://192.168.10.7/ubuntu groovy-updates/main i386 Packages
500 http://192.168.10.7/ubuntu groovy-security/main amd64 Packages
500 http://192.168.10.7/ubuntu groovy-security/main i386 Packages
2020b-1ubuntu1 500
500 http://192.168.10.7/ubuntu groovy/main amd64 Packages
500 http://192.168.10.7/ubuntu groovy/main i386 Packages
bdmurray@clean-groovy-amd64:~$ zdump -v Africa/Juba | grep 2021
Africa/Juba Sun Jan 31 20:59:59 2021 UT = Sun Jan 31 23:59:59 2021 EAT isdst=0
gmtoff=10800
Africa/Juba Sun Jan 31 21:00:00 2021 UT = Sun Jan 31 23:00:00 2021 CAT isdst=0
gmtoff=7200
ICU data verification:
bdmurray@clean-groovy-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz =
ICUtzinfo(TimeZone.createTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1"
2:00:00
** Tags removed: verification-needed-groovy
** Tags added: verification-done-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1886314] Re: preinstall `earlyoom` by default
Any progress on this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1886314 Title: preinstall `earlyoom` by default Status in ubuntu-meta package in Ubuntu: New Bug description: Fedora done this https://fedoraproject.org/wiki/Changes/EnableEarlyoom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1886314/+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 1913632] Re: Ubuntu 20.10 Pulseaudio won't recognize audio line-out until pulseaudio restarted
Thank you for your bug report, that's a bug to report to popOS or upstream (https://gitlab.freedesktop.org/pulseaudio/pulseaudio/) though since you aren't using Ubuntu ** Package changed: systemd (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low ** Changed in: pulseaudio (Ubuntu) Status: New => Invalid -- 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/1913632 Title: Ubuntu 20.10 Pulseaudio won't recognize audio line-out until pulseaudio restarted Status in pulseaudio package in Ubuntu: Invalid Bug description: Ubuntu 20.10 (PopOS on a custom Skylake generation server, not System76) Problem started occurring after upgrade from Ubuntu 20.04 to Ubuntu 20.10 PopOS. System never experienced this problem before that upgrade and it's a 5 year old server. Pulseaudio does not recognize speakers attached to green line-out port of built-in analog card. This is temporarily corrected by restarting pulseaudio service. However, upon next reboot the problem reoccurs. Thus, requiring a pulseaudio restart after every reboot. To reproduce problem: 1. Speakers plugged in (through green line-out port of built-in card) and speakers are powered on 2. Restart Linux (either after hard power off, or reset, or soft reboot, doesn't matter. BIOS changes do nothing.) 3. System comes up, and pulseaudio dashboard shows no built-in analog stereo under "Output Devices" 4. Restart pulseaudio: systemctl --user restart pulseaudio.service 5. Pulseaudio dashboard now shows built-in analog stereo under "Output Devices" CONFIGURATION INFORMATION: cat /etc/issue Pop!_OS 20.10 uname -a Linux walkubu 5.8.0-7630-generic #32~1609193707~20.10~781bb80-Ubuntu SMP Tue Jan 5 21:29:56 UTC 2 x86_64 x86_64 x86_64 GNU/Linux arecord -L null Discard all samples (playback) or generate zero samples (capture) default Playback/recording through the PulseAudio sound server samplerate Rate Converter Plugin Using Samplerate Library speexrate Rate Converter Plugin Using Speex Resampler jack JACK Audio Connection Kit oss Open Sound System pulse PulseAudio Sound Server upmix Plugin for channel upmix (4,6,8) vdownmix Plugin for channel downmix (stereo) with a simple spacialization hw:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Direct hardware device without any conversions hw:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Direct hardware device without any conversions plughw:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Hardware device with all software conversions plughw:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Hardware device with all software conversions sysdefault:CARD=PCH HDA Intel PCH, ALC1150 Analog Default Audio Device front:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Front output / input dsnoop:CARD=PCH,DEV=0 HDA Intel PCH, ALC1150 Analog Direct sample snooping device dsnoop:CARD=PCH,DEV=2 HDA Intel PCH, ALC1150 Alt Analog Direct sample snooping device usbstream:CARD=PCH HDA Intel PCH USB Stream Output hw:CARD=C525,DEV=0 HD Webcam C525, USB Audio Direct hardware device without any conversions plughw:CARD=C525,DEV=0 HD Webcam C525, USB Audio Hardware device with all software conversions sysdefault:CARD=C525 HD Webcam C525, USB Audio Default Audio Device front:CARD=C525,DEV=0 HD Webcam C525, USB Audio Front output / input dsnoop:CARD=C525,DEV=0 HD Webcam C525, USB Audio Direct sample snooping device usbstream:CARD=C525 HD Webcam C525 USB Stream Output usbstream:CARD=NVidia HDA NVidia USB Stream Output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1913632/+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 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement
This bug was fixed in the package gzip - 1.10-2ubuntu3 --- gzip (1.10-2ubuntu3) hirsute; urgency=medium * Enable DFLTCC optimisations on s390x by default. LP: #1884514 -- Dimitri John Ledkov Thu, 28 Jan 2021 15:56:12 + ** Changed in: gzip (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Released Status in gzip package in Ubuntu: Fix Released Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: Thanh Nguyen (32nguyen) => (unassigned) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1895937] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 13
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/1895937 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: getting this error again and again. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Sep 17 12:51:39 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2020-01-22 (238 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to focal on 2020-05-29 (110 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1895937/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.16.04
---
tzdata (2021a-0ubuntu0.16.04) xenial; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
-- Brian Murray Wed, 27 Jan 2021 13:53:41 -0800
** Changed in: tzdata (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.16.04
---
tzdata (2021a-0ubuntu0.16.04) xenial; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
-- Brian Murray Wed, 27 Jan 2021 13:53:41 -0800
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
** Description changed: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. - - Userspace tool common name: as - - The userspace tool has the following bit modes: 64-bit + + Userspace tool common name: as + + The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils - Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 + + [Impact] + + * Vector alignment hints were enabled for z14 processors, but not z13 + + * Since the z13 processors support vector alignment hints, binutils should +have them enabled for z13 + + [Test Case] + + * Run the test suite to make sure all tests pass + + * Pull in the change, and re-run the test suite to make sure all +tests still pass. This backport includes tests for the vector +alignment hints. + + [Where problems could occur] + + * If vector alignment hints were not enabled correctly we could still +compile code with incorrectly ordered opcodes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: In Progress Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 [Impact] * Vector alignment hints were enabled for z14 processors, but not z13 * Since the z13 processors support vector alignment hints, binutils should have them enabled for z13 [Test Case] * Run the test suite to make sure all tests pass * Pull in the change, and re-run the test suite to make sure all tests still pass. This backport includes tests for the vector alignment hints. [Where problems could occur] * If vector alignment hints were not enabled correctly we could still compile code with incorrectly ordered opcodes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.20.04
---
tzdata (2021a-0ubuntu0.20.04) focal; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
* Update ICU timezone data files which are utilized by php and update them
to 2021a.
-- Brian Murray Wed, 27 Jan 2021 13:32:53 -0800
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.20.04
---
tzdata (2021a-0ubuntu0.20.04) focal; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
* Update ICU timezone data files which are utilized by php and update them
to 2021a.
-- Brian Murray Wed, 27 Jan 2021 13:32:53 -0800
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.20.10
---
tzdata (2021a-0ubuntu0.20.10) groovy; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
* Update ICU timezone data files which are utilized by php and update them
to 2021a.
-- Brian Murray Wed, 27 Jan 2021 11:53:19 -0800
** Changed in: tzdata (Ubuntu Groovy)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Update Released
The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.18.04
---
tzdata (2021a-0ubuntu0.18.04) bionic; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
-- Brian Murray Wed, 27 Jan 2021 13:46:22 -0800
** Changed in: tzdata (Ubuntu Bionic)
Status: Fix Committed => Fix Released
** Changed in: tzdata (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
This bug was fixed in the package tzdata - 2021a-0ubuntu0.18.04
---
tzdata (2021a-0ubuntu0.18.04) bionic; urgency=medium
* New upstream version (LP: #1913482), affecting the following future
timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
-- Brian Murray Wed, 27 Jan 2021 13:46:22 -0800
** Changed in: tzdata (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Released
Status in tzdata source package in Bionic:
Fix Released
Status in tzdata source package in Focal:
Fix Released
Status in tzdata source package in Groovy:
Fix Released
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
This bug was fixed in the package wpa - 2:2.9-1ubuntu10 --- wpa (2:2.9-1ubuntu10) hirsute; urgency=medium * debian/patches/git_dbus_bridge.patch - Allow changing an interface bridge via D-Bus (lp: #1893563) [ Andrej Shadura ] * Security fix: CVE-2020-12695. A vulnerability in the UPnP SUBSCRIBE command can trigger the AP to initiate a HTTP (TCP/IP) connection to an arbitrary URL or to trigger misbehavior in hostapd and cause the process to either get terminated or to start using more CPU resources. The issue can also be mitigated by building hostapd without UPnP support (CONFIG_WPS_UPNP=n) or disabling it at runtime by removing the upnp_iface parameter. (Closes: #976106) [ Paolo Pisati ] * debian/patches/nl80211-Unbreak-mode-processing-due-to-presence-of-S.patch: - backport upstream fix (commit 52a1b28345123c374fd0127cbce623c41a760730) for S1G band (lp: #1912609) -- Sebastien Bacher Thu, 28 Jan 2021 15:10:07 +0100 ** Changed in: wpa (Ubuntu Hirsute) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12695 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: Fix Released Status in wpa source package in Hirsute: Fix Released Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1893563] Re: netplan: can't login to ap mode with psk
This bug was fixed in the package wpa - 2:2.9-1ubuntu10 --- wpa (2:2.9-1ubuntu10) hirsute; urgency=medium * debian/patches/git_dbus_bridge.patch - Allow changing an interface bridge via D-Bus (lp: #1893563) [ Andrej Shadura ] * Security fix: CVE-2020-12695. A vulnerability in the UPnP SUBSCRIBE command can trigger the AP to initiate a HTTP (TCP/IP) connection to an arbitrary URL or to trigger misbehavior in hostapd and cause the process to either get terminated or to start using more CPU resources. The issue can also be mitigated by building hostapd without UPnP support (CONFIG_WPS_UPNP=n) or disabling it at runtime by removing the upnp_iface parameter. (Closes: #976106) [ Paolo Pisati ] * debian/patches/nl80211-Unbreak-mode-processing-due-to-presence-of-S.patch: - backport upstream fix (commit 52a1b28345123c374fd0127cbce623c41a760730) for S1G band (lp: #1912609) -- Sebastien Bacher Thu, 28 Jan 2021 15:10:07 +0100 ** Changed in: wpa (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-12695 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Status in wpa package in Ubuntu: Fix Released Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected
** Changed in: ubuntu-cdimage Assignee: (unassigned) => Thanh Nguyen (32nguyen) -- 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/1871268 Title: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected Status in Ubuntu CD Images: Fix Released Status in apt package in Ubuntu: Fix Released Status in apt source package in Bionic: In Progress Status in apt source package in Focal: Fix Released Status in apt source package in Groovy: Fix Released Status in apt package in Debian: Unknown Bug description: [Impact] Installations that really succeeded would then fail because APT could not immediately configure a package. Which is a pointless way to fail at that point, because everything did work out anyway. We have two changes that help address this: * The first one stops immediately configuring multi-arch siblings (e.g. libc6:i386 when it's configuring libc6:amd64). This was not necessary, and caused all the libc6:i386 failures here. * The second change sort of also supersedes the first one: It just ignores any errors from immediate configuration, relying on the fact that it's checked and rectified at a later point if there are unconfigured packages (which is what made all those failures happen spuriously after having successfully installed everything). [Test case] We have one test case in EIPP format in the Debian bug 973305 which was only helped by the second change, not the first one. Run /usr/lib/apt/planners < eipp.log and check there are no errors. TODO: It's unclear if the APT from proposed installed in the live session will fix the installer, needs investigation, but would make a useful test case. [Regression potential] It's imaginable that we missed something somewhere and some path that checked for a set error doesn't check it anymore, and we report success when we hit an error, but it seems unlikely. Behavior of --simulate changes. This used to fail before as well, and will now only produce a warning. We don't believe that is a reason of concern. [Groovy SRU] The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable which also incorporates changes to the documentation: A typo fix, replacing focal with groovy in examples, and minor Dutch manual pages translation updates. We do not have test cases for the documentation changes, and we do not consider there to be a huge regression potential. As long as they build, they should be readable - maybe some words are wrong in the translation, who knows. [Original bug report] Test Case 1. Install Ubuntu Desktop on hardware with an nVidia card and select to install 3rd party drivers 2. Proceed with installation The following error message is displayed in /var/log/syslog /plugininstall.py: Verifying downloads ... /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: "Version: '4.4.10-10ubuntu4' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: '9.3.0-1ubuntu2' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: '1.2.11.dfsg-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: '1.0.9-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: '1.1.3-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: '1.3.4-0ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: '3.6.0-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: '1.6.9-2ubuntu1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: '1.1.5-1' not found." /plugininstall.py: Failed to find package object for /cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: '5.0.3-1' not found." /plugininstall.py: Failed to find package object for
[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode
Problem has NOT been fixed for my setup: - Kernel: 5.4.0-65-generic - OS: Ubuntu 20.04.1 LTS - Machine: Dell EliteBook - Headset: Oppo Enco Quiet -- 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/1871794 Title: [Bluetooth] No audio output/input in HSP/HFP mode Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm testing with Sony bluetooth headset SBH20, works fine in A2DP profile, but I can't get audio input and output work in HSP/HFP profile. [Reproduce steps] 1. Scan and pair BT headset in Bluetooth setting 2. Switch to HSP/HFP profile in Sound setting 3. Test sound output/input [Machine information] ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 16:26:52 2020 InstallationDate: Installed on 2020-04-09 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) SourcePackage: pulseaudio Symptom: audio Symptom_Card: SBH20 Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1359 F pulseaudio Symptom_Type: No sound at all Title: [SBH20, recording] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 0188D1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.product.sku: 08B0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1871794/+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 1913480] [NEW] Sound>Output>Configuration always resets
You have been subscribed to a public bug: In "Settings>Sound>Output" If set my "Output Device" to "HDMI / DisplayPort 5" and set "Configuration" to "Digital Surround 5.1" If I close the receiver and open it again... The configuration will reset to "Digital stereo" The expected behavior would be to keep the "Digital Surround 5.1"; not resetting it every time. Ubuntu 20.04 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment focal -- Sound>Output>Configuration always resets https://bugs.launchpad.net/bugs/1913480 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio 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 1913480] Re: Sound>Output>Configuration always resets
The settings panel is only a configuration interface, it has no backend or service always active and isn't the one applying the configuration when the devices are connected, the issue is probably rather on the sound service pulseaudio ** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) ** Changed in: pulseaudio (Ubuntu) Importance: Undecided => Low -- 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/1913480 Title: Sound>Output>Configuration always resets Status in pulseaudio package in Ubuntu: New Bug description: In "Settings>Sound>Output" If set my "Output Device" to "HDMI / DisplayPort 5" and set "Configuration" to "Digital Surround 5.1" If I close the receiver and open it again... The configuration will reset to "Digital stereo" The expected behavior would be to keep the "Digital Surround 5.1"; not resetting it every time. Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1913480/+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 1907789] Re: 2.35.50 breaks ld -no-pie
** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in Ubuntu on IBM z Systems: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1913482] Re: Update tzdata to version 2021a
Hello Brian, or anyone else affected,
Accepted tzdata into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2021a-
0ubuntu0.20.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Focal)
Status: New => Fix Committed
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
New
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
Hello Brian, or anyone else affected,
Accepted tzdata into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2021a-
0ubuntu0.18.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Bionic)
Status: New => Fix Committed
** Tags added: verification-needed-bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913571] [NEW] apt autoremove does not remove old kernel
Public bug reported:
Ubuntu 20.10
Apt version 2.1.10ubuntu0.2
Here the content of /etc/apt/01autoremove-kernels:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-.*-5\.8\.0-40-lowlatency$";
"^linux-.*-5\.8\.0-41-lowlatency$";
"^kfreebsd-.*-5\.8\.0-40-lowlatency$";
"^kfreebsd-.*-5\.8\.0-41-lowlatency$";
"^gnumach-.*-5\.8\.0-40-lowlatency$";
"^gnumach-.*-5\.8\.0-41-lowlatency$";
"^.*-modules-5\.8\.0-40-lowlatency$";
"^.*-modules-5\.8\.0-41-lowlatency$";
"^.*-kernel-5\.8\.0-40-lowlatency$";
"^.*-kernel-5\.8\.0-41-lowlatency$";
};
/* Debug information:
# dpkg list:
rc linux-image-5.8.0-25-lowlatency 5.8.0-25.26
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-29-lowlatency 5.8.0-29.31
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-31-lowlatency 5.8.0-31.33
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-33-lowlatency 5.8.0-33.36
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-34-lowlatency 5.8.0-34.37
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-36-lowlatency 5.8.0-36.40
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-38-lowlatency 5.8.0-38.43
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-40-lowlatency 5.8.0-40.45
amd64Signed kernel image lowlatency
iF linux-image-5.8.0-41-lowlatency 5.8.0-41.46
amd64Signed kernel image lowlatency
ii linux-image-lowlatency5.8.0.41.45
amd64lowlatency Linux kernel image
# list of installed kernel packages:
5.8.0-38-lowlatency 5.8.0-38.43
5.8.0-40-lowlatency 5.8.0-40.45
5.8.0-41-lowlatency 5.8.0-41.46
# list of different kernel versions:
5.8.0-41.46
5.8.0-40.45
5.8.0-38.43
# Installing kernel: 5.8.0-41.46 (5.8.0-41-lowlatency)
# Running kernel: 5.8.0-40.45 (5.8.0-40-lowlatency)
# Last kernel: 5.8.0-41.46
# Previous kernel: 5.8.0-40.45
# Kernel versions list to keep:
5.8.0-40.45
5.8.0-41.46
# Kernel packages (version part) to protect:
5\.8\.0-40-lowlatency
5\.8\.0-41-lowlatency
*/
Running sudo apt autoremove results in:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It worked properly in previous versions of apt, but since upgrade to apt
version 2.1.10ubuntu0.2 I seem to be unable to autoremove old kernels. I
expect the kernel version 5.8.0-38.43 to be removed with the autoremove
command.
** Affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
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/1913571
Title:
apt autoremove does not remove old kernel
Status in apt package in Ubuntu:
New
Bug description:
Ubuntu 20.10
Apt version 2.1.10ubuntu0.2
Here the content of /etc/apt/01autoremove-kernels:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-.*-5\.8\.0-40-lowlatency$";
"^linux-.*-5\.8\.0-41-lowlatency$";
"^kfreebsd-.*-5\.8\.0-40-lowlatency$";
"^kfreebsd-.*-5\.8\.0-41-lowlatency$";
"^gnumach-.*-5\.8\.0-40-lowlatency$";
"^gnumach-.*-5\.8\.0-41-lowlatency$";
"^.*-modules-5\.8\.0-40-lowlatency$";
"^.*-modules-5\.8\.0-41-lowlatency$";
"^.*-kernel-5\.8\.0-40-lowlatency$";
"^.*-kernel-5\.8\.0-41-lowlatency$";
};
/* Debug information:
# dpkg list:
rc linux-image-5.8.0-25-lowlatency 5.8.0-25.26
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-29-lowlatency 5.8.0-29.31
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-31-lowlatency 5.8.0-31.33
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-33-lowlatency 5.8.0-33.36
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-34-lowlatency 5.8.0-34.37
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-36-lowlatency 5.8.0-36.40
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-38-lowlatency 5.8.0-38.43
amd64Signed
[Touch-packages] [Bug 1889742] Re: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils)
Thanks for preparing the package and getting it uploaded. The diff and change seem to be fine, but since this is an upload to a toolchain package, we need to build it against -security (since these uploads go instantly to both -updates and -security, per policy). So I'll reject it from the queue and upload it to a -security enabled Bileto PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4412 Once the builds finish there I'll perform a bin-sync to focal-proposed and accept it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1889742 Title: [UBUNTU 20.04] Accept vector alignment hints on z13 (binutils) Status in Ubuntu on IBM z Systems: In Progress Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Focal: In Progress Status in binutils source package in Groovy: Fix Released Bug description: == Comment: #0 - Heinz-Werner Seeck - 2020-07-31 03:28:30 == On z13 we have that vector alignment hints are already accepted. This backport enables GAS to accept such hints not only for target z14 but also for z13. Since GCCs default target on Ubuntu is z13 for s390x, we could greatly benefit from such alignment hints. (note a separate bugzilla entry for GCC allowing to emit alignment hints for z13 will be opened shortly) This is a backport of upstreams commit 26b6ab7a0e. Userspace tool common name: as The userspace tool has the following bit modes: 64-bit Userspace rpm: binutils Already included within 20.10 via LP: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1888654 This should also be SRUed for 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1889742/+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 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
I'm running latest HWE kernel on 20.04 (5.4.0-65). If I connect a microphone via USB or the headphone socket then it works (in chromium too). But if I disconnect the microphone then Gnome doesn't detect any built- in microphone. As I've made some changes to my modules settings, I think I'll wipe the system and try it with a fresh install. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+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 1913482] Re: Update tzdata to version 2021a
Hello Brian, or anyone else affected,
Accepted tzdata into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2021a-
0ubuntu0.20.10 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Groovy)
Status: New => Fix Committed
** Tags added: verification-needed verification-needed-groovy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
New
Status in tzdata source package in Bionic:
New
Status in tzdata source package in Focal:
New
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1913482] Re: Update tzdata to version 2021a
Hello Brian, or anyone else affected,
Accepted tzdata into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/tzdata/2021a-
0ubuntu0.16.04 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
xenial to verification-done-xenial. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-xenial. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Changed in: tzdata (Ubuntu Xenial)
Status: New => Fix Committed
** Tags added: verification-needed-xenial
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1907789] Re: 2.35.50 breaks ld -no-pie
This bug was fixed in the package s390-tools - 2.15.1-0ubuntu6 --- s390-tools (2.15.1-0ubuntu6) hirsute; urgency=medium * debian/patches/s390-tools-lp1903984-hirsute.patch zcryptstats: Fix handling of partial results with many domains Thanks to Ingo Franzki (LP: #1903984) -- Frank Heimes Tue, 19 Jan 2021 18:58:26 +0100 ** Changed in: s390-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1907789 Title: 2.35.50 breaks ld -no-pie Status in binutils: Fix Released Status in binutils package in Ubuntu: Fix Released Status in qemu package in Ubuntu: Fix Released Status in s390-tools package in Ubuntu: Fix Released Bug description: The qemu build reaches (and always did) a step where it tries to link some img files. That is done via the command: $ ld -m elf_i386 -T /<>/pc-bios/optionrom//flat.lds -no-pie -s -o multiboot.img multiboot.o Recently that still works in Debian [1] but no more in Ubuntu [2]. I think that the new binutils broke me. In hirsute proposed those are at 2.35.50.20201210-0ubuntu1 The issue is easily isolated, and by copying the two files around I found the following: Hirsute: 2.35.50.20201210-0ubuntu1 - bad Hirsute: 2.35.50.20201207-0ubuntu1 - bad Sid: 2.35.1-4 - good Groovy: 2.35.1-1ubuntu1 - good Focal: 2.34-6ubuntu1 - good I'll attach these two files to the bug, just thro them into a directory and run the command: $ ld -m elf_i386 -T ./flat.lds -no-pie -s -o linuxboot.img linuxboot.o If that is an intentional change please guide how this is now supposed to work. [1]: https://buildd.debian.org/status/fetch.php?pkg=qemu=amd64=1%3A5.2%2Bdfsg-2=1607598738=1 [2]: https://launchpadlibrarian.net/510801929/buildlog_ubuntu-hirsute-amd64.qemu_1%3A5.2+dfsg-2ubuntu1~ppa2_BUILD To manage notifications about this bug go to: https://bugs.launchpad.net/binutils/+bug/1907789/+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 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work
I just tried this now on a freshly installed Ubuntu 20.04 with kernel 5.8.0-41-generic and it works great in both Gnome and in Chromium. Happy to mark this resolved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1868330 Title: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work Status in alsa-driver package in Ubuntu: Confirmed Bug description: On Focal Fossa the microphone is recognised but doesn't work. Chromium shows the microphone as present but off, and if it is renabled it goes off again after a couple of seconds. Chromium logs this error: [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 0x0 [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th chromium_chromium.desktop[9531]: [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation is nullptr. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 1687 F pulseaudio /dev/snd/pcmC0D0p: user 1687 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 20 23:03:01 2020 InstallationDate: Installed on 2020-03-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed Symptom_Card: sof-hda-dsp - sof-hda-dsp Symptom_Jack: Black Mic, Right Symptom_Type: None of the above Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1868330/+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 1913657] Re: ubuntu-bug option 'other' fails
I can confirm if I `ubuntu-bug` with no options.. a dialog soon pops up, where on clicking "Other" I get "No package specified: You need to specify a package or a PID. See --help for more information". For me `apport` is (hirsute) 2.20.11-0ubuntu56 ** Package changed: ubiquity (Ubuntu) => apport (Ubuntu) -- 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/1913657 Title: ubuntu-bug option 'other' fails Status in apport package in Ubuntu: Confirmed Bug description: Apologies for tagging this bug report incorrectly. Executing ubuntu-bug without options results in a panel asking for more information. Choosing option 'other' results in a panel saying "You need to specify a package or a PID. See --help for more information" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 09:57:47 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-01-14 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1913657/+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 1913657] Re: ubuntu-bug option 'other' fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- 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/1913657 Title: ubuntu-bug option 'other' fails Status in apport package in Ubuntu: Confirmed Bug description: Apologies for tagging this bug report incorrectly. Executing ubuntu-bug without options results in a panel asking for more information. Choosing option 'other' results in a panel saying "You need to specify a package or a PID. See --help for more information" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 09:57:47 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-01-14 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1913657/+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 1913657] Re: ubuntu-bug option 'other' fails
Note: I expect this is intended behaviour, it's just not likely what most users would expect The "Other" choice maybe could give warning you'll need to submit bug another way, but this is just opinion. -- 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/1913657 Title: ubuntu-bug option 'other' fails Status in apport package in Ubuntu: Confirmed Bug description: Apologies for tagging this bug report incorrectly. Executing ubuntu-bug without options results in a panel asking for more information. Choosing option 'other' results in a panel saying "You need to specify a package or a PID. See --help for more information" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 09:57:47 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-01-14 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1913657/+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 1913613] Re: Second monitor is detected but has no signal
Here's the decoded EDID of the affected monitor on HDMI-1-0: EDID version: 1.3 Manufacturer: BNQ Model 30926 Serial Number 21573 Made in week 3 of 2015 Digital display Maximum image size: 53 cm x 30 cm Gamma: 2.20 DPMS levels: Off RGB color display Default (sRGB) color space is primary color space First detailed timing is preferred timing Color Characteristics Red: 0.6416, 0.3339 Green: 0.3339, 0.6240 Blue: 0.1523, 0.0498 White: 0.3134, 0.3291 Established Timings I & II 720x40070.082 Hz 9:531.467 kHz 28.320 MHz (IBM) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (DMT) 640x48075.000 Hz 4:337.500 kHz 31.500 MHz (DMT) 800x60060.317 Hz 4:337.879 kHz 40.000 MHz (DMT) 800x60075.000 Hz 4:346.875 kHz 49.500 MHz (DMT) 832x62474.551 Hz 4:349.726 kHz 57.284 MHz (Apple) 1024x76860.004 Hz 4:348.363 kHz 65.000 MHz (DMT) 1024x76875.029 Hz 4:360.023 kHz 78.750 MHz (DMT) 1280x1024 75.025 Hz 5:479.976 kHz 135.000 MHz (DMT) 1152x87075.062 Hz 192:145 68.681 kHz 100.000 MHz (Apple) Standard Timings 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (DMT) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (DMT) 1280x80059.810 Hz 16:10 49.702 kHz 83.500 MHz (DMT) 1280x1024 60.020 Hz 5:463.981 kHz 108.000 MHz (DMT) 1600x90060.000 Hz 16:960.000 kHz 108.000 MHz (DMT, RB) 1680x1050 59.954 Hz 16:10 65.290 kHz 146.250 MHz (DMT) Detailed mode: Clock 148.500 MHz, 531 mm x 299 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Display Product Serial Number: Y1F02711SL0 Display Range Limits Monitor ranges (GTF): 50-76 Hz V, 30-83 kHz H, max dotclock 170 MHz Display Product Name: BenQ GL2460 Has 1 extension block Checksum: 0x86 CTA-861 Extension Block Revision 3 Underscans PC formats by default Basic audio support Supports YCbCr 4:4:4 Supports YCbCr 4:2:2 1 native detailed modes 30 bytes of CTA data blocks Video Data Block 1920x1080 60.000 Hz 16:967.500 kHz 148.500 MHz (VIC 16, native) 1920x1080i 60.000 Hz 16:933.750 kHz 74.250 MHz (VIC 5) 1280x72060.000 Hz 16:945.000 kHz 74.250 MHz (VIC 4) 720x48059.940 Hz 16:931.469 kHz 27.000 MHz (VIC 3) 720x48059.940 Hz 4:331.469 kHz 27.000 MHz (VIC 2) 640x48059.940 Hz 4:331.469 kHz 25.175 MHz (VIC 1) 720x57650.000 Hz 4:331.250 kHz 27.000 MHz (VIC 17) 720x57650.000 Hz 16:931.250 kHz 27.000 MHz (VIC 18) 1280x72050.000 Hz 16:937.500 kHz 74.250 MHz (VIC 19) 1920x1080i 50.000 Hz 16:928.125 kHz 74.250 MHz (VIC 20) 1440x480i 59.940 Hz 4:315.734 kHz 27.000 MHz (VIC 6) 1440x480i 59.940 Hz 16:915.734 kHz 27.000 MHz (VIC 7) 1440x576i 50.000 Hz 4:315.625 kHz 27.000 MHz (VIC 21) 1440x576i 50.000 Hz 16:915.625 kHz 27.000 MHz (VIC 22) 1920x1080 50.000 Hz 16:956.250 kHz 148.500 MHz (VIC 31) Audio Data Block Linear PCM, max channels 2 Supported sample rates (kHz): 48 44.1 32 Supported sample sizes (bits): 24 20 16 Vendor-Specific Data Block, OUI 0x000c03 (HDMI) Source physical address 1.0.0.0 Speaker Allocation Data Block Speaker map: FL/FR - Front Left/Right Detailed mode: Clock 148.500 MHz, 531 mm x 299 mm 1920 2008 2052 2200 ( 88 44 148) 1080 1084 1089 1125 ( 4 5 36) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 67.500 kHz Detailed mode: Clock 74.250 MHz, 531 mm x 299 mm 1920 2008 2052 2200 ( 88 44 148) 540 542 547 562 ( 2 5 15) +hsync +vsync VertFreq: 60.000i Hz, HorFreq: 33.750 kHz Detailed mode: Clock 74.250 MHz, 531 mm x 299 mm 1280 1390 1430 1650 (110 40 220) 720 725 730 750 ( 5 5 20) +hsync +vsync VertFreq: 60.000 Hz, HorFreq: 45.000 kHz Detailed mode: Clock 27.000 MHz, 531 mm x 299 mm 720 736 798 858 ( 16 62 60) 480 489 495 525 ( 9 6 30) -hsync -vsync VertFreq: 59.940 Hz, HorFreq: 31.469 kHz Checksum: 0xe7 ** Tags added: amdgpu hybrid nvidia ** Summary changed: - Second monitor is detected but has no signal + [nvidia] [amdgpu] Second monitor is detected but has no signal -- 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/1913613 Title: [nvidia] [amdgpu] Second monitor is detected but has no signal Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: xrandr Screen
[Touch-packages] [Bug 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Oh actually maybe upstream already answered that: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/637 -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
I think the right answer is to ask upstream first so we don't have to carry more customizations which we don't understand as well as they do. And someone already did: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/81 So for the moment we are waiting on a reply. ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #81 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/81 ** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #637 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/637 -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1913613] Re: [nvidia] [amdgpu] Second monitor is detected but has no signal
Thanks for the bug report. It appears the affected monitor is connected to the Nvidia GPU, but your system doesn't seem to have the Nvidia driver loaded properly. This might be an installation issue or it might be an incompatibility between needing 'modeset' enabled for the amdgpu driver, and needing 'modeset' disabled for the nvidia driver. I'm actually not sure what the best way is to support such a combination. ** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-460 (Ubuntu) -- 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/1913613 Title: [nvidia] [amdgpu] Second monitor is detected but has no signal Status in nvidia-graphics-drivers-460 package in Ubuntu: New Bug description: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93 1024x768 59.93 800x600 59.93 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9450.00 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: LANGUAGE=es TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Touch-packages] [Bug 1913657] [NEW] ubuntu-bug option 'other' fails
You have been subscribed to a public bug: Apologies for tagging this bug report incorrectly. Executing ubuntu-bug without options results in a panel asking for more information. Choosing option 'other' results in a panel saying "You need to specify a package or a PID. See --help for more information" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 09:57:47 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-01-14 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.2 -- ubuntu-bug option 'other' fails https://bugs.launchpad.net/bugs/1913657 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport 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 1913666] [NEW] acl dropped in Focal server image
Public bug reported: The acl package is not shipped by default in the Focal server image (though it looks like libacl1 is still being shipped), it was last shipped in the Bionic server image. Just to double check, was dropping acl intentional? It is a reverse-dependency of LXD if that might be the explanation (as it's now shipped as a snap in Focal rather than the deb in Bionic)? And the same question applies to uidmap, another LXD dependency no longer shipped in the Focal server image. Thank you! ** Affects: acl (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to acl in Ubuntu. https://bugs.launchpad.net/bugs/1913666 Title: acl dropped in Focal server image Status in acl package in Ubuntu: New Bug description: The acl package is not shipped by default in the Focal server image (though it looks like libacl1 is still being shipped), it was last shipped in the Bionic server image. Just to double check, was dropping acl intentional? It is a reverse-dependency of LXD if that might be the explanation (as it's now shipped as a snap in Focal rather than the deb in Bionic)? And the same question applies to uidmap, another LXD dependency no longer shipped in the Focal server image. Thank you! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acl/+bug/1913666/+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 1913657] Re: ubuntu-bug option 'other' fails
If this is intended then it is entirely user-UN-friendly. IMHO it is most likely the result of sloppy maintenance. -- 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/1913657 Title: ubuntu-bug option 'other' fails Status in apport package in Ubuntu: Confirmed Bug description: Apologies for tagging this bug report incorrectly. Executing ubuntu-bug without options results in a panel asking for more information. Choosing option 'other' results in a panel saying "You need to specify a package or a PID. See --help for more information" ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 29 09:57:47 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-01-14 (14 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1913657/+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 1913613] [NEW] Second monitor is detected but has no signal
Public bug reported: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93 1024x768 59.93 800x600 59.93 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) 1920x1080 60.00 + 59.9450.00 1680x1050 59.95 1600x900 60.00 1280x1024 75.0260.02 1280x800 59.81 1280x720 60.0059.9450.00 1024x768 75.0360.00 800x600 75.0060.32 720x576 50.00 720x480 59.94 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:109f] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: LANGUAGE=es TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFX505DT.315:bd09/22/2020:svnASUSTeKCOMPUTERINC.:pnTUFGamingFX505DT_FX505DT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFX505DT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming dmi.product.name: TUF Gaming FX505DT_FX505DT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A 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 N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic corruption ubuntu -- 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/1913613 Title: Second monitor is detected but has no signal Status in xorg package in Ubuntu: New Bug description: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm 1920x1080 59.93*+ 39.99 1680x1050 59.93 1280x1024 59.93 1440x900 59.93 1280x800 59.93 1280x720 59.93
[Touch-packages] [Bug 1878969] Re: time-epoch never changes in SRUs
Is there any timeline on when this will be considered for SRU'ing back
to focal so it is usable in i.e. UC20?
--
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/1878969
Title:
time-epoch never changes in SRUs
Status in ubuntu-core-initramfs:
New
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
New
Status in systemd source package in Bionic:
New
Status in systemd source package in Focal:
New
Bug description:
[Impact]
* Systems without hwclock come up with a fixed time epoch which is not
updated in SRUs
* Ideally booting with a newer built of systemd should move time epoch to be
at least when systemd was last built. For example to the value of
SOURCE_DATE_EPOCH.
[Test Case]
* Boot without network NTP or hwclock
* Observe that the epoch is the same as the time when NEWS entry in the
systemd source code was last touched.
* Boot newer update of systemd, observe that the time epoch is at least 2020
[Regression Potential]
* Bad epoch, may result in unable to perform TLS connections,
validated GPG signatures, and snapd assertions. Changing epoch to be
more recent is desired. Some machines may rely on the fact that
"bionic" without hwclock always comes up in year 2018. But in practice
that is incorrect thing to do.
[Other Info]
* By default
option('time-epoch', type : 'integer', value : '-1',
description : 'time epoch for time clients')
in systemd is set to the modification time of the NEW entry
time_epoch = run_command(stat, '-c', '%Y', NEWS).stdout().to_int()
If available, it should be set to SOURCE_DATE_EPOCH=1585051767 value
to be compliant with the https://reproducible-
builds.org/docs/timestamps/ specification.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-core-initramfs/+bug/1878969/+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 1882500] Re: software-properties-qt: add option to remove unused deps in unattended upgrades
** Changed in: software-properties (Ubuntu) Status: New => Invalid -- 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/1882500 Title: software-properties-qt: add option to remove unused deps in unattended upgrades Status in software-properties package in Ubuntu: Invalid Bug description: Right now i'm using this command: sudo sed -i 's|//Unattended-Upgrade::Remove-Unused-Dependencies.*|Unattended-Upgrade::Remove-Unused-Dependencies "true";|g' /etc/apt/apt.conf.d/50unattended-upgrades But, i want software-properties-qt to have option like these in gui (see attachment) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1882500/+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 1913482] Autopkgtest regression report (tzdata/2021a-0ubuntu0.18.04)
All autopkgtests for the newly accepted tzdata (2021a-0ubuntu0.18.04) for
bionic have finished running.
The following regressions have been reported in tests triggered by the package:
gnustep-base/1.25.1-2ubuntu3 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1779767] Re: Default cron PATH does not include /snap/bin
** Tags added: fr-1092 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in cron package in Ubuntu: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1779767] Re: Default cron PATH does not include /snap/bin
@laney i would agree to patch cron with our default path, with snap/bin included. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in cron package in Ubuntu: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1890619] Re: poppler fails to build on s390x with gcc10 due to symbols changes
the symbols got updated since, we are probably not going to investigate why they changed at this point so closing ** Changed in: poppler (Ubuntu) Status: New => Invalid ** Changed in: poppler (Ubuntu) Assignee: Dimitri John Ledkov (xnox) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1890619 Title: poppler fails to build on s390x with gcc10 due to symbols changes Status in poppler package in Ubuntu: Invalid Bug description: The build log is there https://launchpadlibrarian.net/491645678/buildlog_ubuntu-groovy-s390x.poppler_0.86.1-0ubuntu1_BUILDING.txt.gz the errors are * Build-Depends-Package: libpoppler-glib-dev - (regex)"^_Z.*@Base$" 0.86.1 +#MISSING: 0.86.1-0ubuntu1# (regex)"^_Z.*@Base$" 0.86.1 + _ZN7Poppler19UnicodeParsedStringERKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEE@Base 0.86.1-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1890619/+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 1779767] Re: Default cron PATH does not include /snap/bin
** Tags removed: rls-ff-incoming rls-hh-incoming ** Also affects: cron (Ubuntu Hirsute) Importance: Medium Status: Confirmed ** Also affects: cron (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cron in Ubuntu. https://bugs.launchpad.net/bugs/1779767 Title: Default cron PATH does not include /snap/bin Status in cron package in Ubuntu: Confirmed Status in cron source package in Focal: New Status in cron source package in Hirsute: Confirmed Bug description: I recently changed from a .deb install of LXD to a snap, and was surprised that one of my crontab scripts stopped working. I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas my default shell also includes "/snap/bin". It seems to me that for the best user experience with snaps, "/snap/bin" should be part of the default $PATH in cron. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: cron 3.0pl1-128.1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40 kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jul 2 14:30:06 2018 InstallationDate: Installed on 2017-12-20 (194 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cron UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1779767/+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 1913187] Re: iproute2 segfaults when filtering sockets
# verfication
$ dpkg -l iproute2 | grep ii
ii iproute2 4.15.0-2ubuntu1.3 amd64networking and traffic
control tools
$ ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 && echo
worked
worked
good to migrate. thank you.
-rafaeldtinoco
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Changed in: iproute2 (Ubuntu Bionic)
Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iproute2 in Ubuntu.
https://bugs.launchpad.net/bugs/1913187
Title:
iproute2 segfaults when filtering sockets
Status in iproute2 package in Ubuntu:
Fix Released
Status in iproute2 source package in Bionic:
Fix Committed
Bug description:
[Impact]
* The ss tool crashes when a query returns no results (seg fault)
[Test Case]
* $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1
Segmentation fault
* PPA with the fix:
https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
[Where problems could occur]
* The ss tool is impacted and it has its code changed for the fix.
* The fix is a clean cherry-pick and straightforward (moving
declaration after a NULL check).
[Other Info]
When in Ubuntu Bionic, if one calls:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58910 127.0.0.1:22
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
it works. Just like when in Groovy:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp 00
127.0.0.1:58908 127.0.0.1:22
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
but.. if there is nothing to show, in Bionic we get a segfault:
$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1908502] Re: [MIR] libdeflate
** Changed in: libdeflate (Ubuntu Hirsute) Assignee: Sebastien Bacher (seb128) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in tiff package in Ubuntu: Triaged Status in libdeflate source package in Hirsute: New Status in tiff source package in Hirsute: Triaged Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+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 1884514] Re: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement
** Changed in: gzip (Ubuntu) Status: New => In Progress ** Changed in: gzip (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to zlib in Ubuntu. https://bugs.launchpad.net/bugs/1884514 Title: [FFe][20.10 FEAT] zlib/gzip hardware compression enablement Status in Ubuntu on IBM z Systems: Fix Released Status in gzip package in Ubuntu: In Progress Status in zlib package in Ubuntu: Fix Released Bug description: [Feature Freeze Exception] 1. Feature: The latest s390x hardware comes with a new concept for hardware assisted compression/decompression, based on a 'Next Accelerator Function unit' (NXU). This is an on-chip concept, a co-processor for compression available to all cores on the same chip. It provides functions as normal 'problem state' instructions (in other words user space instructions that are directly consumable by libraries and applications) and supports DEFLATE compliant compression/decompression + GZIP CRC/ZLIB Adler. To enable this hardware support for zlib and gzip, zlib needs to be compiled with CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e". The value of 0x7e enables hardware compression for the compression levels 1-6 (out of 0-9). There is a significant business value of having the enablement active by default, since tests on a system with 4 IFLs and hardware compression enabled this way offered (especially for DEFLATE as best case) a speed up of more than 40x. 2. Changes Adding CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" attributes/macro during build of zlib and gzip. 3. Regression risk The concept is new and comes with IBM z15 and LinuxONE III only and is with that specific and limited to s390x. Hence a potential regressions of this late addition would be limited to s390x and there again with the above changes to zlib (and gzip). In case of unforeseen issues with the NXU hardware component, a fallback to software is done. On top a modified zlib package was build and made available in a PPA for further testing. This change should have been included earlier, but was blocked by other zlib tickets/bugs that needed to be fixed and integrated first (like LP 1893170), hence this request for late addition. __ HW Compression need to be enabled with Default-Compression-Level 6. Adding following CFLAGS attributes during build of zlib and gzip "-DDFLTCC_LEVEL_MASK=0x7e" CFLAGS="-O2 -DDFLTCC -DDFLTCC_LEVEL_MASK=0x7e" ./configure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1884514/+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 1913613] Re: Second monitor is detected but has no signal
** Description changed: xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 16384 x 16384 eDP connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 194mm -1920x1080 59.93*+ 39.99 -1680x1050 59.93 -1280x1024 59.93 -1440x900 59.93 -1280x800 59.93 -1280x720 59.93 -1024x768 59.93 -800x600 59.93 -640x480 59.93 + 1920x1080 59.93*+ 39.99 + 1680x1050 59.93 + 1280x1024 59.93 + 1440x900 59.93 + 1280x800 59.93 + 1280x720 59.93 + 1024x768 59.93 + 800x600 59.93 + 640x480 59.93 HDMI-1-0 connected (normal left inverted right x axis y axis) -1920x1080 60.00 + 59.9450.00 -1680x1050 59.95 -1600x900 60.00 -1280x1024 75.0260.02 -1280x800 59.81 -1280x720 60.0059.9450.00 -1024x768 75.0360.00 -800x600 75.0060.32 -720x576 50.00 -720x480 59.94 -640x480 75.0059.9459.93 + 1920x1080 60.00 + 59.9450.00 + 1680x1050 59.95 + 1600x900 60.00 + 1280x1024 75.0260.02 + 1280x800 59.81 + 1280x720 60.0059.9450.00 + 1024x768 75.0360.00 + 800x600 75.0060.32 + 720x576 50.00 + 720x480 59.94 + 640x480 75.0059.9459.93 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 - GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 + GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: - + CompositorRunning: None Date: Thu Jan 28 16:52:43 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: - nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed - rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed + nvidia, 460.32.03, 5.4.0-64-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-42-generic, x86_64: installed + rtl8821ce, 5.5.2.1, 5.4.0-64-generic, x86_64: installed GraphicsCard: - NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:109f] - Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] + NVIDIA Corporation Device [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:109f] + Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Device [1043:18f1] InstallationDate: Installed on 2021-01-27 (0 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FX505DT_FX505DT ProcEnviron: - LANGUAGE=es - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_ES.UTF-8 - SHELL=/bin/bash + LANGUAGE=es + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic root=UUID=a4e7f6c4-6b4b-46b3-b120-84a8805ac9dd ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FX505DT.315 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FX505DT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a
tzdata verification for focal:
bdmurray@clean-focal-amd64:~$ zdump -v Africa/Juba | grep 2021
bdmurray@clean-focal-amd64:~$ sudo apt-get install tzdata
[sudo] password for bdmurray:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
tzdata
1 upgraded, 0 newly installed, 0 to remove and 30 not upgraded.
Need to get 295 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://192.168.10.7/ubuntu focal-proposed/main amd64 tzdata all
2021a-0ubuntu0.20.04 [295 kB]
Fetched 295 kB in 0s (9,897 kB/s)
Preconfiguring packages ...
(Reading database ... 223660 files and directories currently installed.)
Preparing to unpack .../tzdata_2021a-0ubuntu0.20.04_all.deb ...
Unpacking tzdata (2021a-0ubuntu0.20.04) over (2020f-0ubuntu0.20.04.1) ...
Setting up tzdata (2021a-0ubuntu0.20.04) ...
Current default time zone: 'America/Los_Angeles'
Local time is now: Thu Jan 28 09:33:43 PST 2021.
Universal Time is now: Thu Jan 28 17:33:43 UTC 2021.
Run 'dpkg-reconfigure tzdata' if you wish to change it.
bdmurray@clean-focal-amd64:~$ zdump -v Africa/Juba | grep 2021
Africa/Juba Sun Jan 31 20:59:59 2021 UT = Sun Jan 31 23:59:59 2021 EAT isdst=0
gmtoff=10800
Africa/Juba Sun Jan 31 21:00:00 2021 UT = Sun Jan 31 23:00:00 2021 CAT isdst=0
gmtoff=7200
verification of the icu-data change:
bdmurray@clean-focal-amd64:~$ python3 -c "from datetime import datetime; from
icu import ICUtzinfo, TimeZone; tz = ICUtzinfo(TimeZone.create
TimeZone('Africa/Juba')); print(str(tz.utcoffset(datetime(2021, 2, 1"
2:00:00
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1910943] Re: package util-linux 2.34-0.1ubuntu9.1 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed')
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1910943 Title: package util-linux 2.34-0.1ubuntu9.1 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed') Status in util-linux package in Ubuntu: New Bug description: failing message have been soving by system in VM of linux. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: util-linux 2.34-0.1ubuntu9.1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: util-linux:amd64: Configure liberror-perl:amd64: Install git-man:amd64: Install git:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 11 08:15:55 2021 ErrorMessage: package util-linux is not ready for configuration cannot configure (current status 'half-installed') InstallationDate: Installed on 2021-01-05 (5 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: util-linux Title: package util-linux 2.34-0.1ubuntu9.1 failed to install/upgrade: package util-linux is not ready for configuration cannot configure (current status 'half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1910943/+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 1910975] Re: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flite in Ubuntu. https://bugs.launchpad.net/bugs/1910975 Title: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in flite package in Ubuntu: New Bug description: it refused to install updates ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libflite1:amd64 2.2-1 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 11 13:05:06 2021 DuplicateSignature: package:libflite1:amd64:2.2-1 Setting up python-apt-common (2.1.3ubuntu1.3) ... dpkg: error processing package libflite1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-01-01 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: flite Title: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1910975/+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 1909334] Re: bug
Thank you for using Ubuntu and taking the time to report a bug. Your report should contain, at a minimum, the following information so we can better find the source of the bug and work to resolve it. Submitting the bug about the proper source package is essential. For help see https://wiki.ubuntu.com/Bugs/FindRightPackage . Additionally, in the report please include: 1) The release of Ubuntu you are using, via 'cat /etc/lsb-release' or System -> About Ubuntu. 2) The version of the package you are using, via 'dpkg -l PKGNAME | cat' or by checking in Synaptic. 3) What happened and what you expected to happen. The Ubuntu community has also created debugging procedures for a wide variety of packages at https://wiki.ubuntu.com/DebuggingProcedures . Following the debugging instructions for the affected package will make your bug report much more complete. Thanks! ** Information type changed from Private Security to Public ** Changed in: xorg (Ubuntu) Status: New => Invalid -- 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/1909334 Title: bug Status in xorg package in Ubuntu: Invalid Bug description: bug ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-170.220-generic 3.13.11-ckt39 Uname: Linux 3.13.0-170-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 25 18:45:40 2020 DistUpgraded: 2020-12-22 12:02:59,073 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:30a3] InstallationDate: Installed on 2020-12-21 (4 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: LENOVO 10AAS39X00 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-170-generic root=UUID=956b6a42-972b-4ae3-813d-38976087b2bf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2020-12-22 (3 days ago) dmi.bios.date: 10/22/2014 dmi.bios.vendor: LENOVO dmi.bios.version: FBKTA1AUS dmi.board.name: SHARKBAY dmi.board.vendor: LENOVO dmi.board.version: 0B98401 WIN dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvrFBKTA1AUS:bd10/22/2014:svnLENOVO:pn10AAS39X00:pvrThinkCentreM93p:rvnLENOVO:rnSHARKBAY:rvr0B98401WIN:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: 10AAS39X00 dmi.product.version: ThinkCentre M93p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Dec 24 01:04:29 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 10293 vendor HWP xserver.version: 2:1.15.1-0ubuntu2.11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1909334/+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 1909602] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1909602 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: i don't knwo any details, sorry ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic i686 ApportVersion: 2.20.1-0ubuntu2.28 Architecture: i386 Date: Sun Dec 27 22:23:23 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2011-07-27 (3443 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-07-19 (1259 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1909602/+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 1910975] Re: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flite in Ubuntu. https://bugs.launchpad.net/bugs/1910975 Title: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in flite package in Ubuntu: New Bug description: it refused to install updates ProblemType: Package DistroRelease: Ubuntu 20.10 Package: libflite1:amd64 2.2-1 ProcVersionSignature: Ubuntu 5.8.0-36.40-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Jan 11 13:05:06 2021 DuplicateSignature: package:libflite1:amd64:2.2-1 Setting up python-apt-common (2.1.3ubuntu1.3) ... dpkg: error processing package libflite1:amd64 (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-01-01 (9 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.1 SourcePackage: flite Title: package libflite1:amd64 2.2-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1910975/+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 1909602] Re: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1909602 Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 Status in unattended-upgrades package in Ubuntu: New Bug description: i don't knwo any details, sorry ProblemType: Package DistroRelease: Ubuntu 16.04 Package: unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 ProcVersionSignature: Ubuntu 3.13.0-116.163-generic 3.13.11-ckt39 Uname: Linux 3.13.0-116-generic i686 ApportVersion: 2.20.1-0ubuntu2.28 Architecture: i386 Date: Sun Dec 27 22:23:23 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2011-07-27 (3443 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32ubuntu0.2 SourcePackage: unattended-upgrades Title: package unattended-upgrades 1.1ubuntu1.18.04.7~16.04.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2017-07-19 (1259 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1909602/+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 1913493] Re: pc
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1913493 Title: pc Status in xorg package in Ubuntu: New Bug description: pc ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic i686 .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Jan 28 00:27:54 2021 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Device [1234:] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Device [1af4:1100] InstallationDate: Installed on 2019-05-05 (633 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1) Lsusb: Bus 001 Device 004: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 003: ID 0409:55aa NEC Corp. Hub Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=UUID=218dfaed-f9ed-4bbe-af1a-aeb8953f26c8 ro quiet splash Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.1-0-ga5cab58e9a3f-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.0:cvnQEMU:ct1:cvrpc-i440fx-4.0: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.0 dmi.sys.vendor: QEMU version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A 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 N/A xserver.bootTime: Thu Jan 28 00:23:55 2021 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1913493/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Note that meet + chrome is unusable with auto_switch=2 and bose QC35 II. I only managed to make it work once when initially investigating the option. I haven't been able to make a single google meet call with chrome ever since I activated that option, I must regularly start firefox specifically for these calls. -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1913482] Autopkgtest regression report (tzdata/2021a-0ubuntu0.20.04)
All autopkgtests for the newly accepted tzdata (2021a-0ubuntu0.20.04) for focal
have finished running.
The following regressions have been reported in tests triggered by the package:
libical3/3.0.8-1 (s390x)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1830955] Re: Systemd removes OpenVPN IP addresses
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
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/1830955
Title:
Systemd removes OpenVPN IP addresses
Status in systemd package in Ubuntu:
Invalid
Bug description:
This is probably related to, but not a duplicate of, bug 1815101.
Running
root@third:/home/leroy# lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
Systemd version:
root@third:/home/leroy# apt-cache policy systemd
systemd:
Installed: 237-3ubuntu10.21
Candidate: 237-3ubuntu10.21
Version table:
*** 237-3ubuntu10.21 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64
Packages
100 /var/lib/dpkg/status
237-3ubuntu10.19 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
237-3ubuntu10 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
I expected the OpenVPN IP addresses to remain, instead they were
removed, the physical NIC address remained, process:
Start OpenVPN with systemctl start openvpn@ (in this
situation, two instances). Result:
root@third:/etc/openvpn# ip addr sh tun0
7: tun0: mtu 1500 qdisc fq_codel
state UNKNOWN group default qlen 100
link/none
inet 10.57.3.1 peer 10.57.3.2/32 scope global tun0
valid_lft forever preferred_lft forever
inet6 fe80::f0ea:151b:cb91:5d1b/64 scope link stable-privacy
valid_lft forever preferred_lft forever
root@third:/etc/openvpn# ip addr sh tun1
8: tun1: mtu 1500 qdisc fq_codel
state UNKNOWN group default qlen 100
link/none
inet 10.222.108.234 peer 10.222.108.233/32 scope global tun1
valid_lft forever preferred_lft forever
inet6 fe80::3103:7936:cf19:6237/64 scope link stable-privacy
valid_lft forever preferred_lft forever
Test a configuration (which, incidentally, isn't valid for this
system) with 'netplan try ..' and allow it to revert (which should
have restored the previous configuration), see below:
root@third:/etc/openvpn# cd ~leroy/Downloads
root@third:/home/leroy/Downloads# ll *.yaml
-rw-rw-r-- 1 leroy leroy 555 May 29 10:46 startup.yaml
root@third:/home/leroy/Downloads# netplan --debug try --config-file
~leroy/Downloads/startup.yaml --timeout 15
DEBUG:eno1 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eno1:
addresses:
- 10.15.0.37/24
dhcp4: false
gateway4: 10.15.0.1
nameservers:
addresses:
- 10.15.0.8
- 10.3.77.11
- 10.45.77.11
- 8.8.8.8
vlans: {}
wifis: {}
DEBUG:New interfaces: {'eno1'}
** (generate:8216): DEBUG: 11:19:39.770: Processing input file
/etc/netplan/01-network-manager-all.yaml..
** (generate:8216): DEBUG: 11:19:39.771: starting new processing pass
** (generate:8216): DEBUG: 11:19:39.771: Processing input file
/etc/netplan/startup.1559146779.768221.yaml..
** (generate:8216): DEBUG: 11:19:39.771: starting new processing pass
** (generate:8216): DEBUG: 11:19:39.771: eno1: setting default backend to 2
** (generate:8216): DEBUG: 11:19:39.771: Generating output files..
** (generate:8216): DEBUG: 11:19:39.771: networkd: definition eno1 is not for
us (backend 2)
DEBUG:no netplan generated networkd configuration exists
DEBUG:netplan generated NM configuration exists, restarting NM
DEBUG:eno1 not found in {}
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets:
eno1:
addresses:
- 10.15.0.37/24
dhcp4: false
gateway4: 10.15.0.1
nameservers:
addresses:
- 10.15.0.8
- 10.3.77.11
- 10.45.77.11
- 8.8.8.8
vlans: {}
wifis: {}
DEBUG:Skipping non-physical interface: lo
DEBUG:Skipping non-physical interface: enp2s0
DEBUG:Skipping non-physical interface: virbr0
DEBUG:Skipping non-physical interface: virbr0-nic
DEBUG:Skipping non-physical interface: tun0
DEBUG:Skipping non-physical interface: tun1
DEBUG:{}
DEBUG:netplan triggering .link rules for lo
DEBUG:netplan triggering .link rules for enp2s0
DEBUG:netplan triggering .link rules for virbr0
DEBUG:netplan triggering .link rules for virbr0-nic
DEBUG:netplan triggering .link rules for tun0
DEBUG:netplan triggering .link rules for tun1
Do you want to keep these settings?
Press ENTER before the timeout to accept the new configuration
Changes will revert in 1 seconds
Reverting.
DEBUG:no netplan generated networkd configuration exists
DEBUG:netplan generated NM configuration exists, restarting NM
DEBUG:Merged config:
network:
bonds: {}
bridges: {}
ethernets: {}
vlans: {}
wifis: {}
DEBUG:Skipping non-physical
[Touch-packages] [Bug 1901528] Re: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip)
This bug was fixed in the package gzip - 1.10-2ubuntu1.1 --- gzip (1.10-2ubuntu1.1) groovy; urgency=medium * Applying patch from upstream to fix a segfault caused by passing multiple files larger than 5kb to a gzip command while zlib acceleration is enabled (LP: #1901528) -- William 'jawn-smith' Wilson Tue, 19 Jan 2021 12:57:57 -0600 ** Changed in: gzip (Ubuntu Groovy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) Status in Ubuntu on IBM z Systems: Fix Committed Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Groovy: Fix Released Bug description: When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB. This problem does not happen when running gzip against a single file at a time. It only happens when you provide multiple files as gzip arguments. So this works whether zlib acceleration is enabled or not: for file in file1 file2; do gzip $file ; done But this fails (when zlib acceleration is enabled): gzip file1 file2 The patch to fix this has been accepted upstream: https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc [Impact] * With zlib acceleration enabled, attempting to compress multiple files over 5MB would cause a segmentation fault. * The files could still be compressed in separate commands [Test Case] * Create two files that are larger than 5MB * Enable zlib acceleration (z15 hardware required) * Run the command gzip * NOTE: we do not have access to z15 hardware and therefore are relying on IBM to verify this fix [Where problems could occur] * Due to lack of testing resources, it's possible the bug has not been fully fixed, and the segmentation fault could still occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+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 1913482] Autopkgtest regression report (tzdata/2021a-0ubuntu0.20.10)
All autopkgtests for the newly accepted tzdata (2021a-0ubuntu0.20.10) for
groovy have finished running.
The following regressions have been reported in tests triggered by the package:
gnustep-base/1.27.0-3build3 (armhf)
Please visit the excuses page listed below and investigate the failures,
proceeding afterwards as per the StableReleaseUpdates policy regarding
autopkgtest regressions [1].
https://people.canonical.com/~ubuntu-archive/proposed-
migration/groovy/update_excuses.html#tzdata
[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/1913482
Title:
Update tzdata to version 2021a
Status in tzdata package in Ubuntu:
In Progress
Status in tzdata source package in Xenial:
Fix Committed
Status in tzdata source package in Bionic:
Fix Committed
Status in tzdata source package in Focal:
Fix Committed
Status in tzdata source package in Groovy:
Fix Committed
Bug description:
New upstream version affecting the following timestamp:
- South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets
changed in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed.
If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo,
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba'));
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 |
cut -d' ' -f2-)
Nothing should be returned by the above command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+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 1901528] Update Released
The verification of the Stable Release Update for gzip has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) Status in Ubuntu on IBM z Systems: Fix Committed Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Groovy: Fix Committed Bug description: When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB. This problem does not happen when running gzip against a single file at a time. It only happens when you provide multiple files as gzip arguments. So this works whether zlib acceleration is enabled or not: for file in file1 file2; do gzip $file ; done But this fails (when zlib acceleration is enabled): gzip file1 file2 The patch to fix this has been accepted upstream: https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc [Impact] * With zlib acceleration enabled, attempting to compress multiple files over 5MB would cause a segmentation fault. * The files could still be compressed in separate commands [Test Case] * Create two files that are larger than 5MB * Enable zlib acceleration (z15 hardware required) * Run the command gzip * NOTE: we do not have access to z15 hardware and therefore are relying on IBM to verify this fix [Where problems could occur] * Due to lack of testing resources, it's possible the bug has not been fully fixed, and the segmentation fault could still occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+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 1901528] Re: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip)
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) Status in Ubuntu on IBM z Systems: Fix Released Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Groovy: Fix Released Bug description: When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB. This problem does not happen when running gzip against a single file at a time. It only happens when you provide multiple files as gzip arguments. So this works whether zlib acceleration is enabled or not: for file in file1 file2; do gzip $file ; done But this fails (when zlib acceleration is enabled): gzip file1 file2 The patch to fix this has been accepted upstream: https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc [Impact] * With zlib acceleration enabled, attempting to compress multiple files over 5MB would cause a segmentation fault. * The files could still be compressed in separate commands [Test Case] * Create two files that are larger than 5MB * Enable zlib acceleration (z15 hardware required) * Run the command gzip * NOTE: we do not have access to z15 hardware and therefore are relying on IBM to verify this fix [Where problems could occur] * Due to lack of testing resources, it's possible the bug has not been fully fixed, and the segmentation fault could still occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+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 1913571] Re: apt autoremove does not remove old kernel
This is probably a local configuration issue, you probably manually
installed the 38 version or something, go and have a look at apt-mark
showmanual, and like aptitude why or sth.
As you've shown, the configuration is the same, and nothing in the code
using it changed.
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
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/1913571
Title:
apt autoremove does not remove old kernel
Status in apt package in Ubuntu:
Incomplete
Bug description:
Ubuntu 20.10
Apt version 2.1.10ubuntu0.2
Here the content of /etc/apt/01autoremove-kernels:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-.*-5\.8\.0-40-lowlatency$";
"^linux-.*-5\.8\.0-41-lowlatency$";
"^kfreebsd-.*-5\.8\.0-40-lowlatency$";
"^kfreebsd-.*-5\.8\.0-41-lowlatency$";
"^gnumach-.*-5\.8\.0-40-lowlatency$";
"^gnumach-.*-5\.8\.0-41-lowlatency$";
"^.*-modules-5\.8\.0-40-lowlatency$";
"^.*-modules-5\.8\.0-41-lowlatency$";
"^.*-kernel-5\.8\.0-40-lowlatency$";
"^.*-kernel-5\.8\.0-41-lowlatency$";
};
/* Debug information:
# dpkg list:
rc linux-image-5.8.0-25-lowlatency 5.8.0-25.26
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-29-lowlatency 5.8.0-29.31
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-31-lowlatency 5.8.0-31.33
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-33-lowlatency 5.8.0-33.36
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-34-lowlatency 5.8.0-34.37
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-36-lowlatency 5.8.0-36.40
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-38-lowlatency 5.8.0-38.43
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-40-lowlatency 5.8.0-40.45
amd64Signed kernel image lowlatency
iF linux-image-5.8.0-41-lowlatency 5.8.0-41.46
amd64Signed kernel image lowlatency
ii linux-image-lowlatency5.8.0.41.45
amd64lowlatency Linux kernel image
# list of installed kernel packages:
5.8.0-38-lowlatency 5.8.0-38.43
5.8.0-40-lowlatency 5.8.0-40.45
5.8.0-41-lowlatency 5.8.0-41.46
# list of different kernel versions:
5.8.0-41.46
5.8.0-40.45
5.8.0-38.43
# Installing kernel: 5.8.0-41.46 (5.8.0-41-lowlatency)
# Running kernel: 5.8.0-40.45 (5.8.0-40-lowlatency)
# Last kernel: 5.8.0-41.46
# Previous kernel: 5.8.0-40.45
# Kernel versions list to keep:
5.8.0-40.45
5.8.0-41.46
# Kernel packages (version part) to protect:
5\.8\.0-40-lowlatency
5\.8\.0-41-lowlatency
*/
Running sudo apt autoremove results in:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It worked properly in previous versions of apt, but since upgrade to
apt version 2.1.10ubuntu0.2 I seem to be unable to autoremove old
kernels. I expect the kernel version 5.8.0-38.43 to be removed with
the autoremove command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1913571/+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 1913571] Re: apt autoremove does not remove old kernel
I suggest consulting one of the user support sites such ask askubuntu or
the #ubuntu irc channel for help.
--
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/1913571
Title:
apt autoremove does not remove old kernel
Status in apt package in Ubuntu:
Incomplete
Bug description:
Ubuntu 20.10
Apt version 2.1.10ubuntu0.2
Here the content of /etc/apt/01autoremove-kernels:
// DO NOT EDIT! File autogenerated by /etc/kernel/postinst.d/apt-auto-removal
APT::NeverAutoRemove
{
"^linux-.*-5\.8\.0-40-lowlatency$";
"^linux-.*-5\.8\.0-41-lowlatency$";
"^kfreebsd-.*-5\.8\.0-40-lowlatency$";
"^kfreebsd-.*-5\.8\.0-41-lowlatency$";
"^gnumach-.*-5\.8\.0-40-lowlatency$";
"^gnumach-.*-5\.8\.0-41-lowlatency$";
"^.*-modules-5\.8\.0-40-lowlatency$";
"^.*-modules-5\.8\.0-41-lowlatency$";
"^.*-kernel-5\.8\.0-40-lowlatency$";
"^.*-kernel-5\.8\.0-41-lowlatency$";
};
/* Debug information:
# dpkg list:
rc linux-image-5.8.0-25-lowlatency 5.8.0-25.26
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-29-lowlatency 5.8.0-29.31
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-31-lowlatency 5.8.0-31.33
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-33-lowlatency 5.8.0-33.36
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-34-lowlatency 5.8.0-34.37
amd64Signed kernel image lowlatency
rc linux-image-5.8.0-36-lowlatency 5.8.0-36.40
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-38-lowlatency 5.8.0-38.43
amd64Signed kernel image lowlatency
ii linux-image-5.8.0-40-lowlatency 5.8.0-40.45
amd64Signed kernel image lowlatency
iF linux-image-5.8.0-41-lowlatency 5.8.0-41.46
amd64Signed kernel image lowlatency
ii linux-image-lowlatency5.8.0.41.45
amd64lowlatency Linux kernel image
# list of installed kernel packages:
5.8.0-38-lowlatency 5.8.0-38.43
5.8.0-40-lowlatency 5.8.0-40.45
5.8.0-41-lowlatency 5.8.0-41.46
# list of different kernel versions:
5.8.0-41.46
5.8.0-40.45
5.8.0-38.43
# Installing kernel: 5.8.0-41.46 (5.8.0-41-lowlatency)
# Running kernel: 5.8.0-40.45 (5.8.0-40-lowlatency)
# Last kernel: 5.8.0-41.46
# Previous kernel: 5.8.0-40.45
# Kernel versions list to keep:
5.8.0-40.45
5.8.0-41.46
# Kernel packages (version part) to protect:
5\.8\.0-40-lowlatency
5\.8\.0-41-lowlatency
*/
Running sudo apt autoremove results in:
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
It worked properly in previous versions of apt, but since upgrade to
apt version 2.1.10ubuntu0.2 I seem to be unable to autoremove old
kernels. I expect the kernel version 5.8.0-38.43 to be removed with
the autoremove command.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1913571/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
Thanks for the patch Paolo, I uploaded to hirsute now -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Hirsute: Fix Committed Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1912609] Re: mac80211_hwsim: hostapd fails to start with S1G band
** Changed in: wpa (Ubuntu Hirsute) Importance: Undecided => High ** Changed in: wpa (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1912609 Title: mac80211_hwsim: hostapd fails to start with S1G band Status in wpa package in Ubuntu: Fix Committed Status in wpa source package in Hirsute: Fix Committed Bug description: Hostapd fails to start on a recent 5.10+ kernel: $ cat repro.sh #!/bin/sh sudo modprobe mac80211_hwsim sudo ip a flush dev wlan0 sudo ip a add 192.168.5.1/24 dev wlan0 cat << EOF > hostapd.conf interface=wlan0 driver=nl80211 hw_mode=b channel=1 ssid=fake net EOF sudo hostapd hostapd.conf ubuntu@hirsute-amd64:~$ ./repro.sh Configuration file: hostapd.conf nl80211: kernel reports: expected nested data Using interface wlan0 with hwaddr 02:00:00:00:00:00 and ssid "fake net" wlan0: interface state UNINITIALIZED->ENABLED wlan0: AP-ENABLED ^C wlan0: interface state ENABLED->DISABLED wlan0: AP-DISABLED wlan0: CTRL-EVENT-TERMINATING nl80211: deinit ifname=wlan0 disabled_11b_rates=0 this due to the mismanagement of the newly added S1G band, the attached patch fixes it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1912609/+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 1901528] Comment bridged from LTC Bugzilla
--- Comment From heinz-werner_se...@de.ibm.com 2021-01-28 09:27 EDT--- IBM Bugzilla status->closed, Fix Released with groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gzip in Ubuntu. https://bugs.launchpad.net/bugs/1901528 Title: [Ubuntu 20.10] - When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB (gzip) Status in Ubuntu on IBM z Systems: Fix Released Status in gzip package in Ubuntu: Fix Released Status in gzip source package in Groovy: Fix Released Bug description: When zlib acceleration is enabled, gzip fails when given multiple files larger than 5KB. This problem does not happen when running gzip against a single file at a time. It only happens when you provide multiple files as gzip arguments. So this works whether zlib acceleration is enabled or not: for file in file1 file2; do gzip $file ; done But this fails (when zlib acceleration is enabled): gzip file1 file2 The patch to fix this has been accepted upstream: https://git.savannah.gnu.org/cgit/gzip.git/commit/?id=be0a534ba2b6e77da289de8da79e70843b1028cc [Impact] * With zlib acceleration enabled, attempting to compress multiple files over 5MB would cause a segmentation fault. * The files could still be compressed in separate commands [Test Case] * Create two files that are larger than 5MB * Enable zlib acceleration (z15 hardware required) * Run the command gzip * NOTE: we do not have access to z15 hardware and therefore are relying on IBM to verify this fix [Where problems could occur] * Due to lack of testing resources, it's possible the bug has not been fully fixed, and the segmentation fault could still occur. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1901528/+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 1893563] Re: netplan: can't login to ap mode with psk
** Changed in: wpa (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1893563 Title: netplan: can't login to ap mode with psk Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Triaged Status in wpa package in Ubuntu: Fix Committed Bug description: I've setup my wifi cards as ap over a bridge using netplan. If I add: auth: key-management: psk password: "testinglang" then my clients are unable to connect. If I remove those lines above in netplan then the clients are able to connect but without a password. If I run wpa_cli -i wlp3s0 status, I get: bssid=4c:1d:96:71:a3:90 freq=2412 ssid=walad2 id=0 mode=AP pairwise_cipher=CCMP+TKIP group_cipher=TKIP key_mgmt=UNKNOWN wpa_state=COMPLETED p2p_device_address=4c:1d:96:71:a3:91 address=4c:1d:96:71:a3:90 uuid=85d86b40-7e3d-5fc5-b5fc-aae9af55b29a I notice that key_mgmt=UNKNOWN. Perhaps that's the problem? Any pointers on how to debug and fix this? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: netplan.io 0.99-0ubuntu3~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Aug 30 23:11:48 2020 InstallationDate: Installed on 2020-08-16 (14 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: netplan.io UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1893563/+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 1913601] [NEW] add-apt-repository does not correctly enable sources
Public bug reported: [impact] 'add-apt-repository -s' should enable deb-src for all existing repos, but doesn't [test case] root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-updates restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-backports restricted universe multiverse main deb http://security.ubuntu.com/ubuntu groovy-security restricted universe multiverse main root@sp-g:~# add-apt-repository -s Enabling deb-src for all repositories. Press [ENTER] to continue or Ctrl-c to cancel. Enabled: None Enabled: None Enabled: deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse universe restricted main Enabled: deb-src http://archive.canonical.com/ubuntu groovy partner Enabled: None Hit:1 http://security.ubuntu.com/ubuntu groovy-security InRelease Get:2 http://security.ubuntu.com/ubuntu groovy-security/universe Sources [6608 B] Hit:3 http://archive.ubuntu.com/ubuntu groovy InRelease Hit:4 http://archive.ubuntu.com/ubuntu groovy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu groovy-backports InRelease Get:6 http://archive.ubuntu.com/ubuntu groovy/multiverse Sources [279 kB] Get:7 http://archive.ubuntu.com/ubuntu groovy/universe Sources [16.3 MB] Get:8 http://archive.canonical.com/ubuntu groovy InRelease [11.4 kB] Get:9 http://archive.ubuntu.com/ubuntu groovy-updates/multiverse Sources [3124 B] Get:10 http://archive.ubuntu.com/ubuntu groovy-updates/universe Sources [19.0 kB] Get:11 http://archive.ubuntu.com/ubuntu groovy-backports/universe Sources [2004 B] Get:12 http://archive.canonical.com/ubuntu groovy/partner Sources [720 B] Fetched 16.6 MB in 6s (2884 kB/s) Reading package lists... Done root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-updates multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-updates multiverse universe deb http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.ubuntu.com/ubuntu groovy-backports multiverse restricted main universe deb-src http://archive.canonical.com/ubuntu groovy partner deb http://security.ubuntu.com/ubuntu groovy-security multiverse restricted main universe deb-src http://security.ubuntu.com/ubuntu groovy-security multiverse universe [regression potential] any regression would likely cause add-apt-repository to incorrectly update the apt sources.list and/or sources.list.d file(s), most likely when modifying the deb-src lines [scope] this is needed in g and later the --enable-source parameter in focal and earlier could only be used with a specific repo to be modified, so this is not applicable to f or earlier ** Affects: software-properties (Ubuntu) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: software-properties (Ubuntu Groovy) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Affects: software-properties (Ubuntu Hirsute) Importance: Medium Assignee: Dan Streetman (ddstreet) Status: In Progress ** Also affects: software-properties (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: software-properties (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Groovy) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: software-properties (Ubuntu Hirsute) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: software-properties (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Groovy) Importance: Undecided => Medium ** Changed in: software-properties (Ubuntu Hirsute) Status: New => In Progress ** Changed in: software-properties (Ubuntu Groovy) Status: New => In Progress -- 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/1913601 Title: add-apt-repository does not correctly enable sources Status in software-properties package in Ubuntu: In Progress Status in software-properties source package in Groovy: In Progress Status in software-properties source package in Hirsute: In Progress Bug description: [impact] 'add-apt-repository -s' should enable deb-src for all existing repos, but doesn't [test case] root@sp-g:~# add-apt-repository -sL deb http://archive.ubuntu.com/ubuntu groovy restricted universe multiverse main deb http://archive.ubuntu.com/ubuntu groovy-updates restricted universe
[Touch-packages] [Bug 1907433] Update Released
The verification of the Stable Release Update for glib2.0 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1907433 Title: [SRU] New stable release 2.64.6 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Focal: Fix Released Bug description: [ Description ] Take this new upstrem stable release. It was easiest for me to merge the latest release in this series from Debian, and then import the subsequent point releases on top of that. Visually in the diff there is one change resulting from this: splitting a two-patch upstream cherry pick into two individual patch files. This is cleaner anyway IMO, but is also no change if you look at the resulting patched source. Overview of changes in GLib 2.64.6 == * This is expected to be the last release in the 2.64 series; the new stable series is 2.66, and maintenance efforts will shift to that * Bugs fixed: - #2194 gtk3/glib crash on gimp - #2209 gthreadedresolver: faulty logic in parse_res_txt - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64 - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64 - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to glib-2-64 - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64 - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not succeeding” to glib-2-64 - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too far in the past” to glib-2-64 * Translation updates: - Croatian - Portuguese Overview of changes in GLib 2.64.5 == * Fix deadlock in `g_subprocess_communicate_async()` (work by Alexander Larsson) (#2182) * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868) * Bugs fixed: - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual Studio” to glib-2-64 - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64 - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked URI list” to glib-2-64 - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to glib-2-64 - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never blocks” to glib-2-64 - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to glib-2-64 Overview of changes in GLib 2.64.4 == * Bugs fixed: - #2140 calling malloc in fork child is undefined-behaviour - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to return” to glib-2-64 - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64 - !1547 Backport !1544 “Resolve "calling malloc in fork child is undefined-behaviour"” to glib-2-64 * Translation updates: - Kazakh - Slovenian [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+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 1907433] Re: [SRU] New stable release 2.64.6
This bug was fixed in the package glib2.0 - 2.64.6-1~ubuntu20.04.1
---
glib2.0 (2.64.6-1~ubuntu20.04.1) focal; urgency=medium
[ Iain Lane ]
* New upstream release (LP: #1907433), fixing bugs:
- Ensure g_subprocess_communicate_async() never blocks
- Fix large writes in gfileutils
- Fix splice behavior on cancellation
- gdatetime: Avoid integer overflow creating dates too far in the past
- gdesktopappinfo: Fix unnecessarily copied and leaked URI list
- gthreadedresolver: faulty logic in parse_res_txt
- gtk3/glib crash on gimp
- gvariant: Ensure GVS.depth is initialised
- trash portal: Handle portal failures
* gbp.conf: Set upstream branch to upstream/2.64.x
* Drop patches applied upstream:
- glib-compile-resources-Fix-exporting-on-Visual-Studio.patch
- gdesktopappinfo-Fix-unnecessarily-copied-and-leaked-URI-l.patch
* Revert changes from Debian which we don't need in this SRU:
+ Revert "d/tests/build: Don't exercise static linking for GIO"
+ control{,.in}: Re-lower libmount BD version.
The problems that prompted this to be raised happened post-focal.
-- Iain Lane Wed, 09 Dec 2020 11:23:14 +
** Changed in: glib2.0 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1907433
Title:
[SRU] New stable release 2.64.6
Status in glib2.0 package in Ubuntu:
Fix Released
Status in glib2.0 source package in Focal:
Fix Released
Bug description:
[ Description ]
Take this new upstrem stable release.
It was easiest for me to merge the latest release in this series from
Debian, and then import the subsequent point releases on top of that.
Visually in the diff there is one change resulting from this:
splitting a two-patch upstream cherry pick into two individual patch
files. This is cleaner anyway IMO, but is also no change if you look
at the resulting patched source.
Overview of changes in GLib 2.64.6
==
* This is expected to be the last release in the 2.64 series; the new stable
series is 2.66, and maintenance efforts will shift to that
* Bugs fixed:
- #2194 gtk3/glib crash on gimp
- #2209 gthreadedresolver: faulty logic in parse_res_txt
- !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
- !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
- !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to
glib-2-64
- !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
- !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not
succeeding” to glib-2-64
- !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too
far in the past” to glib-2-64
* Translation updates:
- Croatian
- Portuguese
Overview of changes in GLib 2.64.5
==
* Fix deadlock in `g_subprocess_communicate_async()` (work by
Alexander Larsson) (#2182)
* Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)
* Bugs fixed:
- !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual
Studio” to glib-2-64
- !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
- !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked
URI list” to glib-2-64
- !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to
glib-2-64
- !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never
blocks” to glib-2-64
- !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to
glib-2-64
Overview of changes in GLib 2.64.4
==
* Bugs fixed:
- #2140 calling malloc in fork child is undefined-behaviour
- !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to
return” to glib-2-64
- !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
- !1547 Backport !1544 “Resolve "calling malloc in fork child is
undefined-behaviour"” to glib-2-64
* Translation updates:
- Kazakh
- Slovenian
[ QA ]
Upstream release, so QA already performed by maintainers
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME
This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.
[ What could go wrong ]
This update contains fixes in multiple places so multiple apps could
be affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.
Pretty much all parts of GNOME use GLib, so test anything in the
desktop that you can. If you reboot the machine and can get to the
desktop, that's already tested GLib extensively. But also run
