[Bug 1927963] [NEW] package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1903214 *** https://bugs.launchpad.net/bugs/1903214 Public bug reported: I went to install MATLAB to my Ubuntu OS and hit this error 33% into the process. A lot of the existing errors I see listed do not state a "subprocess" returned the error exit status 1. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: matlab-support 0.0.21.1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 AptOrdering: matlab-support:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 10 08:15:58 2021 DuplicateSignature: package:matlab-support:0.0.21.1 Setting up matlab-support (0.0.21.1) ... No matlab found and maybe running in non-interactive mode. No way out -- failing... dpkg: error processing package matlab-support (--configure): installed matlab-support package post-installation script subprocess returned error exit status 1 ErrorMessage: installed matlab-support package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2021-04-17 (23 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all 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.5 SourcePackage: matlab-support Title: package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: matlab-support (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927963 Title: package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/1927963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927963] Re: package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1
*** This bug is a duplicate of bug 1903214 *** https://bugs.launchpad.net/bugs/1903214 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1903214, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1903214 package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927963 Title: package matlab-support 0.0.21.1 failed to install/upgrade: installed matlab-support package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/matlab-support/+bug/1927963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904521] Re: Intel Tiger Lake IDs supplement
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904521 Title: Intel Tiger Lake IDs supplement To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1904521/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 58002] Re: Some programs create root-owned files in user $HOME when run under sudo
I know it's been a long time since the original bug was reported and the last message was posted. However, I am unable to reproduce this bug on Ubuntu 20.04.2. Perhaps that's because I already have everything mentioned here as my own user. If I rename ~/.vimrc and ~/.viminfo and then run `sudo vi /etc/apt/source.list`, then a default .vimrc and .viminfo are not created in my user directory. I can also see that there is still nothing in /etc/skel related to vim. It has been 8 years and things do change. I've only been using vim for a couple of years, so it's quite possible that the ~/.vimrc isn't created upon first running `vi` or `vim` anymore. What should we do with this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/58002 Title: Some programs create root-owned files in user $HOME when run under sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/58002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
** Description changed: + [Impact] + + * An explanation of the effects of the bug on users and + + * justification for backporting the fix to the stable release. + + * In addition, it is helpful, but not required, to include an +explanation of how the upload fixes this bug. + + [Test Plan] + + * detailed instructions how to reproduce the bug + + * these should allow someone who is not familiar with the affected +package to reproduce the bug and verify that the updated package fixes +the problem. + + * if other testing is appropriate to perform before landing this update, +this should also be described here. + + [Where problems could occur] + + * Think about what the upload changes in the software. Imagine the change is +wrong or breaks something else: how would this show up? + + * It is assumed that any SRU candidate patch is well-tested before +upload and has a low overall risk of regression, but it's important +to make the effort to think about what ''could'' happen in the +event of a regression. + + * This must '''never''' be "None" or "Low", or entirely an argument as to why +your upload is low risk. + + * This both shows the SRU team that the risks have been considered, +and provides guidance to testers in regression-testing the SRU. + + [Other Info] + + * Anything else you think is useful to include + * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board + * and address these questions in advance + + [Original Description] + Fixed in focal and later, due to sync from debian Bionic affected. I'll add a proper description in a moment. RH: https://bugzilla.redhat.com/show_bug.cgi?id=1419280 Debian BTS: https://bugs.debian.org/895381 ML: http://www.spinics.net/lists/linux-nfs/msg62111.html ML: http://www.spinics.net/lists/linux-nfs/msg62099.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927745 Title: Non-thread-safe functions used in multi-threaded rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927712] Re: The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic
Hi Paride, Thank you. I didn't know this subtility about resource-agents. I provided this fix because it is the simple commit to fix the current issue. What do you mean by "universe" and community support ? Is there a repository where I can propose something ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927712 Title: The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1927712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927970] [NEW] Maximised gnome-terminal not returning to normal size
Public bug reported: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927970 Title: Maximised gnome-terminal not returning to normal size To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
A patch we carry on e2fsprogs changes the default blocksize for small
filesystems. That is what breaks the test. We should probably add the
block size when creating these filesystems under LTP.
Description: Use 4k blocksize in all ext4 mke2fs.conf such that lvm migration
between non-4k PVs and 4k PVs works irrespective of the volume size.
Author: Dimitri John Ledkov
Bug-Ubuntu: https://bugs.launchpad.net/bugs/1817097
--- e2fsprogs-1.45.1.orig/misc/mke2fs.conf.in
+++ e2fsprogs-1.45.1/misc/mke2fs.conf.in
@@ -15,12 +15,10 @@
inode_size = 256
}
small = {
- blocksize = 1024
inode_size = 128
inode_ratio = 4096
}
floppy = {
- blocksize = 1024
inode_size = 128
inode_ratio = 8192
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853610
Title:
mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in
ubuntu_ltp fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853610/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
https://lists.linux.it/pipermail/ltp/2021-May/022536.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1853610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926362] Re: maxima fails at launch at command line with said error message
I have the same problem. The error message is: The assertion realpath(s,o) on line 471 of main.c in function mbin failed: Invalid argumentAbortado (`core' generado). This seems also to be the problem why the wxmaxima (gui for maxima) is not working properly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926362 Title: maxima fails at launch at command line with said error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1926362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
Reproducer tool from RH bug
** Description changed:
[Impact]
- * An explanation of the effects of the bug on users and
+ * An explanation of the effects of the bug on users and
- * justification for backporting the fix to the stable release.
+ * justification for backporting the fix to the stable release.
- * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
+ * In addition, it is helpful, but not required, to include an
+ explanation of how the upload fixes this bug.
[Test Plan]
+ # Create a bionic VM. Login and get its ip, and take note of it:
+ export IP=$(ip route get default 8.8.8.8 | grep ^8 | awk '{print $7}')
+ echo $IP
- * detailed instructions how to reproduce the bug
+ # adjust /etc/hosts:
+ echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
- * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+ # adjust /etc/resolv.conf:
+ echo "search example.com" | sudo tee -a /etc/resolv.conf
- * if other testing is appropriate to perform before landing this update,
-this should also be described here.
+ # verify hostname -f returns the fqdn of the vm, i.e., a name with the
.example.com domain:
+ hostname -f
+
+ # Run these commands, and when asked:
+ # - for realm: EXAMPLE.COM
+ # - for kdc and admin server: use the vm's IP
+
+ sudo apt update && apt install nfs-server krb5-kdc krb5-admin-server
+ krb5-user gcc
+
+
+ # adjust nfs config and restart the nfs server:
+ sudo sed -r -i "s,^NEED_SVCGSSD=.*,NEED_SVCGSSD=\"yes\","
/etc/default/nfs-kernel-server
+ sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
+ sudo systemctl restart nfs-server
+
+
+ # create a kerberos realm. When prompted, use any password you want:
+ sudo krb5_newrealm
+
+ # create an nfs service ticket, and store it in the keytab
+ sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
+ sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
+
+
+ # create test directories
+ sudo mkdir -p /mnt/test_krb5/
+ sudo mkdir -p /export
+ sudo touch /export/foo
+
+ # configure an nfs export:
+ echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a
/etc/exports
+ sudo exportfs -rva
+
+ # confirm it's available
+ sudo showmount -e localhost
+
+
+ # mount it
+ sudo mount $(hostname -f):/export /mnt/test_krb5/
+ sudo ls -la /mnt/test_krb5
+
+
+ # download bug attachments
+ (TBD)
+
+ # build reproducer
+ gcc stat_as.c -o stat_as
+
+ # run as root
+ sudo ./bz1419280_test_threads
+
+ # wait
+ # Once you get the confirmation:
+ calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
+ reproduced the bug after 114 iterations
+
+ # Check for a "stat_as" D state process:
+ $ ps axw|grep stat_as
+ 17814 pts/1D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035
+
+ # With the updated packages, the script will not detect the bug and never
stop.
+
[Where problems could occur]
- * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+ * Think about what the upload changes in the software. Imagine the change is
+ wrong or breaks something else: how would this show up?
- * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+ * It is assumed that any SRU candidate patch is well-tested before
+ upload and has a low overall risk of regression, but it's important
+ to make the effort to think about what ''could'
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
Reproducer script from RH bug
** Attachment added: "bz1419280_test_threads"
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496167/+files/bz1419280_test_threads
** Description changed:
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Plan]
# Create a bionic VM. Login and get its ip, and take note of it:
export IP=$(ip route get default 8.8.8.8 | grep ^8 | awk '{print $7}')
echo $IP
# adjust /etc/hosts:
- echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
+ echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
# adjust /etc/resolv.conf:
- echo "search example.com" | sudo tee -a /etc/resolv.conf
+ echo "search example.com" | sudo tee -a /etc/resolv.conf
# verify hostname -f returns the fqdn of the vm, i.e., a name with the
.example.com domain:
hostname -f
# Run these commands, and when asked:
# - for realm: EXAMPLE.COM
# - for kdc and admin server: use the vm's IP
sudo apt update && apt install nfs-server krb5-kdc krb5-admin-server
krb5-user gcc
-
# adjust nfs config and restart the nfs server:
sudo sed -r -i "s,^NEED_SVCGSSD=.*,NEED_SVCGSSD=\"yes\","
/etc/default/nfs-kernel-server
- sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
- sudo systemctl restart nfs-server
-
+ sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
+ sudo systemctl restart nfs-server
# create a kerberos realm. When prompted, use any password you want:
- sudo krb5_newrealm
+ sudo krb5_newrealm
# create an nfs service ticket, and store it in the keytab
- sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
- sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
-
+ sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
+ sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
# create test directories
- sudo mkdir -p /mnt/test_krb5/
- sudo mkdir -p /export
+ sudo mkdir -p /mnt/test_krb5/
+ sudo mkdir -p /export
sudo touch /export/foo
# configure an nfs export:
- echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a
/etc/exports
- sudo exportfs -rva
+ echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a /etc/exports
+ sudo exportfs -rva
# confirm it's available
- sudo showmount -e localhost
-
+ sudo showmount -e localhost
# mount it
- sudo mount $(hostname -f):/export /mnt/test_krb5/
+ sudo mount $(hostname -f):/export /mnt/test_krb5/
sudo ls -la /mnt/test_krb5
-
# download bug attachments
- (TBD)
+ wget -ct0
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496166/+files/stat_as.c
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496167/+files/bz1419280_test_threads
+ chmod +x bz1419280_test_threads
# build reproducer
- gcc stat_as.c -o stat_as
+ gcc stat_as.c -o stat_as
- # run as root
- sudo ./bz1419280_test_threads
-
- # wait
- # Once you get the confirmation:
- calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
- reproduced the bug after 114 iterations
-
- # Check for a "stat_as" D state process:
- $ ps axw|grep stat_as
- 17814 pts/1D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035
-
- # With the updated packages, the script will not detect the bug and never
stop.
+ # run as root
+ sudo ./bz1419280_test_threads
+ # wait
+ # Once you get the confirmation:
+ calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
+ reproduced the bug after 114 iterations
+
+ # Check for a "stat_as" D state process:
+ $ ps axw|gr
[Bug 1905591] Re: no brightness control in {455, 460} after update from 450
Just to add to the report by @manzood, this bug affects my variant of y540 as
well.
My complete laptop spec is as follows:
Lenovo Legion Y540
NVIDIA GTX 2060 Mobile
Ubuntu 18.04
kernel 5.4.0-72-generic
and again, the workaround suggested by @sureshot16 does not work, editing
/sys/class/backlight/acpi_video0/brightness does not work(except when
prime-select is set to intel),
adding 'Option "RegistryDwords" "EnableBrightnessControl=1"' to
/usr/share/X11/xorg.conf.d/10-nvidia-brightness.conf does not work neither does
adding kernel parameters in grub config.
This brightness issue has been a thorn in my side for the better part of
a year, the only version which works is the Nouveau display driver
installed via "Software & Updates" but has no CUDA support or Steam
integration so that's a deal breaker for me.
Unlike @manzood, suspending the laptop and resuming has never worked for
me and causes artifacts and flickering in 460 specifically. Issue
persists in 465 as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905591
Title:
no brightness control in {455,460} after update from 450
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1905591/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927978] [NEW] Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Public bug reported: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable. Updated changelog and diff against Debian unstable to be attached below. ** Affects: db5.3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
Attaching patch against Debian unstable. Test builds available from the following PPA: https://launchpad.net/~waveform/+archive/ubuntu/db/+packages ** Patch added: "1-1927978.debdiff" https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+attachment/5496169/+files/1-1927978.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926853] Re: package grub-efi-amd64-signed 1.167+2.04-1ubuntu44 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926853 Title: package grub-efi-amd64-signed 1.167+2.04-1ubuntu44 failed to install/upgrade: installed grub-efi-amd64-signed package post- installation script subprocess returned error exit status 255 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1926853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926362] Re: maxima fails at launch at command line with said error message
It not linked to wxmaxima, but due to maxima itself. If you launch maxima from terminal, you will have exactly the same error message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926362 Title: maxima fails at launch at command line with said error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maxima/+bug/1926362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827442] Re: [MIR] libheif
Anything we could do to help move this forward? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827442 Title: [MIR] libheif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/1827442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926843] Re: online accounts integration with fb isn't working
But can you confirm: sudo add-apt-repository ppa:folke-schwinning/personal sudo apt-get update sudo apt-get install desktop-facebook sudo apt install npm nodejs-legacy git https://snapcraft.io/install/facebook-webapp/ubuntu Its this safe as worksaground or may is get safety issue? I want replacement for linux, because windows 10 android works with facebook but did no know how becauce is hard to get to works with wine HQ or other software? Because i did not know if APT get or other repo is protected other than wrong repo to old config, because some software may be maded only because developer get money for works with other company that get money on password leaks or other. Not sure if some of apps if safe because it can come software bugs to safety also. Or is snap\apt-get safe with install apps? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927980] [NEW] smartd-runner bug causes loss of email recipients
Public bug reported: *** Expected, documented, and desired behavior: In /etc/smartd.conf it is permitted to specify multiple email recipients. Here is the relevant snippet: ### DEFAULT -d removable -n standby \ -a -M test \ -s S/../.././01 \ -m root,jsd \ -M exec /usr/share/smartmontools/smartd-runner ### The last line is relevant, and the next-to-last line is super-relevant, insofar as it contains a comma-separated list of recipients. The code in smartd itself handles this just fine, and always has. *** Observed bad behavior: I observe that the smartd-runner script throws away all recipients after the first. *** Remark: The root problem is that smartd-runner assumes it will be called with exactly three arguments. It can be expected that this will cause multiple bugs, not just the one reported here. *** Patch to fix the problem A patch file is attached. *** Platform details ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Mon May 10 07:13:51 2021 Dependencies: debianutils 4.9.1 gcc-10-base 10.2.0-5ubuntu1~20.04 libc6 2.31-0ubuntu9.2 libcap-ng0 0.7.9-2.1build1 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10.2.0-5ubuntu1~20.04 libgcrypt20 1.8.5-5ubuntu1 libgpg-error-l10n 1.37-1 libgpg-error0 1.37-1 libidn2-0 2.2.0-2 liblz4-1 1.9.2-2 liblzma5 5.2.4-1ubuntu1 libpcre2-8-0 10.34-7 libselinux1 3.0-1build2 libstdc++6 10.2.0-5ubuntu1~20.04 libsystemd0 245.4-4ubuntu3.6 libunistring2 0.9.10-2 lsb-base 11.1.0ubuntu2 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2010-07-10 (3957 days ago) InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) Package: smartmontools 7.1-1build1 [modified: usr/share/smartmontools/smartd-runner] PackageArchitecture: amd64 ProcCpuinfoMinimal: processor : 1 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Core(TM)2 Duo CPU T9600 @ 2.80GHz stepping : 10 microcode : 0xa07 cpu MHz: 800.000 cache size : 6144 KB physical id: 0 siblings : 2 core id: 1 cpu cores : 2 apicid : 1 initial apicid : 1 fpu: yes fpu_exception : yes cpuid level: 13 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts nopl cpuid aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm pti tpr_shadow vnmi flexpriority vpid dtherm ida vmx flags : vnmi flexpriority tsc_offset vtpr vapic bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit bogomips : 5585.85 clflush size : 64 cache_alignment: 64 address sizes : 36 bits physical, 48 bits virtual power management: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: smartmontools Tags: focal Uname: Linux 5.11.0+ x86_64 UpgradeStatus: Upgraded to focal on 2020-08-09 (273 days ago) _MarkForUpload: True modified.conffile..etc.default.apport: [modified] modified.conffile..etc.default.smartmontools: [modified] modified.conffile..etc.smartd.conf: [modified] mtime.conffile..etc.default.apport: 2020-08-09T18:38:49.803212 mtime.conffile..etc.default.smartmontools: 2010-11-12T20:22:37 mtime.conffile..etc.smartd.conf: 2016-05-14T13:58:08.981915 ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New ** Patch added: "smartd-runner.diff" https://bugs.launchpad.net/bugs/1927980/+attachment/5496170/+files/smartd-runner.diff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927980 Title: smartd-runner bug causes loss of email recipients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1927980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927982] [NEW] package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2
Public bug reported: password cannot be stored to use mysql ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 (not installed) ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 10 19:23:45 2021 ErrorMessage: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2021-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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.5 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927982 Title: package mysql-server-8.0 (not installed) failed to install/upgrade: installed mysql-server-8.0 package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1927982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857404] Re: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: the installed subprocess of the mysql-server-8.0 package, the post-installation script returned exit statu
while starting mysql my password is not being stored -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857404 Title: package mysql-server-8.0 8.0.18-0ubuntu0.19.10.1 failed to install/upgrade: the installed subprocess of the mysql-server-8.0 package, the post-installation script returned exit status error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1857404/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1927836] Re: freezing
Thanks for the answer. I will bring back computer to the store and look for another one. Greetings Jean Matau Le lun. 10 mai 2021 à 09:30, Daniel van Vugt <1927...@bugs.launchpad.net> a écrit : > Thanks. Yes that looks like the same hardware problem. It sounds like > the faulty component is the NVME solid state drive, so you might want to > look at replacing that. Although there's no guarantee that is the > problem -- it might also be a motherboard fault :( > > ** Changed in: linux (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1927836 > > Title: > freezing > > Status in linux package in Ubuntu: > Invalid > > Bug description: > Computer freeze after max. 2 min > New Acer Aspire 3 > Kubuntu or Ubuntu same thing > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 > Uname: Linux 5.8.0-50-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat May 8 19:33:23 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Device [8086:4e61] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Acer Incorporated [ALI] Device [1025:150d] > InstallationDate: Installed on 2021-05-08 (0 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > Lsusb: >Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub >Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. >Bus 001 Device 002: ID 30fa:0300 USB OPTICAL MOUSE >Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > Lsusb-t: >/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M >/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M >|__ Port 4: Dev 2, If 0, Class=Human Interface Device, > Driver=usbhid, 1.5M >|__ Port 8: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M >|__ Port 8: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M > MachineType: Acer Aspire A317-33 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic > root=UUID=fd7ae629-e58b-4181-8297-c5139f747581 ro quiet splash vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/23/2020 > dmi.bios.release: 1.1 > dmi.bios.vendor: Insyde Corp. > dmi.bios.version: V1.01 > dmi.board.asset.tag: Type2 - Board Chassis Location > dmi.board.name: Lilac_JL > dmi.board.vendor: JSL > dmi.board.version: V1.01 > dmi.chassis.type: 10 > dmi.chassis.vendor: Acer > dmi.chassis.version: V1.01 > dmi.ec.firmware.release: 1.0 > dmi.modalias: > dmi:bvnInsydeCorp.:bvrV1.01:bd11/23/2020:br1.1:efr1.0:svnAcer:pnAspireA317-33:pvrV1.01:rvnJSL:rnLilac_JL:rvrV1.01:cvnAcer:ct10:cvrV1.01: > dmi.product.family: Aspire 3 > dmi.product.name: Aspire A317-33 > dmi.product.sku: > dmi.product.version: V1.01 > dmi.sys.vendor: Acer > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx N/A > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927836/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927836 Title: freezing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927983] [NEW] package r-cran-mgcv 1.8-31-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
Public bug reported: Ubuntu itself showed that it has to be reported. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: r-cran-mgcv 1.8-31-1 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 AptOrdering: ant-optional:amd64: Remove ant:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Mon May 10 18:56:42 2021 DpkgTerminalLog: Removing ant-optional (1.10.7-1) ... Removing ant (1.10.7-1) ... [1mdpkg:[0m error processing package r-cran-mgcv (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2021-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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.5 SourcePackage: mgcv Title: package r-cran-mgcv 1.8-31-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) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927983 Title: package r-cran-mgcv 1.8-31-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1927037] Re: ath9k driver: miniPCIe Atheros AR93xx not recognized
After running modprobe ath9k, ath9k shows up in the output from lsmod. However, iw still doesn’t see the interface. On Mon, May 10, 2021 at 1:15 AM Juerg Haefliger <1927...@bugs.launchpad.net> wrote: > What happens if you manually load the driver? modprobe ath9k. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1927037 > > Title: > ath9k driver: miniPCIe Atheros AR93xx not recognized > > Status in linux-raspi package in Ubuntu: > New > Status in linux-raspi source package in Focal: > New > Status in linux-raspi source package in Groovy: > New > Status in linux-raspi source package in Hirsute: > New > > Bug description: > Expected behavior: > Network adapter should be visible via `iw list`, `iwconfig`, and > `ifconfig`. > > Actual behavior: > Network adapter is visible in `lspci` and `lshw`, but not in `iw list`, > `iwconfig`, or `ifconfig` > > Details: > The Atheros network card is detected by the ath9k driver when installed > into a machine with x86_64 architecture. When the same card is installed > into a miniPCIe-to-PCIe adapter, then plugged into a Raspberry Pi CM4 IO > breakout board, the network adapter can be seen via lspci and lshw but is > not seen by iw, iwconfig, or ifconfig. > > lspci: > ubuntu@ubuntu:~$ sudo lspci -v > 00:00.0 PCI bridge: Broadcom Inc. and subsidiaries Device 2711 (rev 20) > (prog-if 00 [Normal decode]) > Flags: bus master, fast devsel, latency 0, IRQ 41 > Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 > I/O behind bridge: -0fff [size=4K] > Memory behind bridge: f800-f80f [size=1M] > Prefetchable memory behind bridge: [disabled] > Capabilities: [48] Power Management version 3 > Capabilities: [ac] Express Root Port (Slot-), MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [180] Vendor Specific Information: ID= Rev=0 > Len=028 > Capabilities: [240] L1 PM Substates > Kernel driver in use: pcieport > > 01:00.0 Network controller: Qualcomm Atheros AR93xx Wireless Network > Adapter (rev 01) > Subsystem: Qualcomm Atheros AR93xx Wireless Network Adapter > Flags: fast devsel, IRQ 255 > Memory at 6 (64-bit, non-prefetchable) [disabled] > [size=128K] > Expansion ROM at 60002 [virtual] [disabled] [size=64K] > Capabilities: [40] Power Management version 3 > Capabilities: [50] MSI: Enable- Count=1/4 Maskable+ 64bit+ > Capabilities: [70] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [140] Virtual Channel > Capabilities: [300] Device Serial Number 00-00-00-00-00-00-00-00 > > - > lshw: > ubuntu@ubuntu:~$ sudo lshw -c net > *-network UNCLAIMED > description: Network controller > product: AR93xx Wireless Network Adapter > vendor: Qualcomm Atheros > physical id: 0 > bus info: pci@:01:00.0 > version: 01 > width: 64 bits > clock: 33MHz > capabilities: pm msi pciexpress cap_list > configuration: latency=0 > resources: memory:6-60001 memory:60002-60002 > *-network > description: Ethernet interface > physical id: 1 > logical name: eth0 > serial: dc:a6:32:f4:69:36 > size: 1Gbit/s > capacity: 1Gbit/s > capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt > 100bt-fd 1000bt 1000bt-fd autonegotiation > configuration: autonegotiation=on broadcast=yes driver=bcmgenet > driverversion=v2.0 duplex=full ip=REDACTED link=yes multicast=yes port=MII > speed=1Gbit/s > > - > iw list/iwconfig: > ubuntu@ubuntu:~$ iw list > ubuntu@ubuntu:~$ iwconfig > lono wireless extensions. > > eth0 no wireless extensions. > > - > ubuntu@ubuntu:~$ lsb_release -rd > Description: Ubuntu 20.04.2 LTS > Release: 20.04 > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.4.0-1034-raspi 5.4.0-1034.37 > ProcVersionSignature: User Name 5.4.0-1034.37-raspi 5.4.101 > Uname: Linux 5.4.0-1034-raspi aarch64 > ApportVersion: 2.20.11-0ubuntu27.16 > Architecture: arm64 > CasperMD5CheckResult: skip > Date: Tue May 4 02:59:25 2021 > ImageMediaBuild: 20210201.1 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: linux-raspi > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1927037/+subscriptions > -- *Ash Wilson* | Technical Director *e:* ash.wil...@valimail.com This email and all data transmitted with it contains confidential and/or propri
[Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
** No longer affects: libreoffice (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
The patches for LP:#1888395 were reverted with the ensuing point release that was picked up in 1923036, so I think the testing of LP:#1923036 can cover it. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927742] Re: dolphin in focal can't delete webdav directories running on focal's apache
Yes, BrowserMatch " Konqueror/5" redirect-carefully does fix the bug. ** Changed in: apache2 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927742 Title: dolphin in focal can't delete webdav directories running on focal's apache To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1927742/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923880] Re: Add support for Intel Jasper Lake, Alder Lake
This bug was fixed in the package libdrm - 2.4.105-3 --- libdrm (2.4.105-3) experimental; urgency=medium * Revert a commit causing additional dependencies to be added to *.pc.in. Also drop libpciaccess-dev from libdrm-dev Depends. -- Timo Aaltonen Sat, 08 May 2021 22:52:07 +0300 ** Changed in: libdrm (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923880 Title: Add support for Intel Jasper Lake, Alder Lake To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1923880/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927988] [NEW] package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1724352 *** https://bugs.launchpad.net/bugs/1724352 Public bug reported: using All In One - System Rescue Toolkit. This is based on Ubuntu 16.04.7 LTS. I performed a system update, which clude a large number of updates. This error appeared at the completion of the update process. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: cryptsetup 2:1.6.6-5ubuntu2.1 ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17 Uname: Linux 4.10.0-28-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.30 Architecture: amd64 CasperVersion: 1.376.2 Date: Mon May 10 14:29:10 2021 ErrorMessage: subprocess installed post-installation script returned error exit status 1 LiveMediaBuild: Lubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.7 apt 1.2.35 SourcePackage: cryptsetup Title: package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) crypttab: # fstab: aufs / aufs rw 0 0 tmpfs /tmp tmpfs nosuid,nodev 0 0 ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927988 Title: package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1927988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall
Hi, yes it can occur on any machine (slave or master) with the same configuration / OS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926265 Title: slapd enter in infinite loop on sched_yield syscall To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1926265/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927988] Re: package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
*** This bug is a duplicate of bug 1724352 *** https://bugs.launchpad.net/bugs/1724352 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1724352, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1724352 package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927988 Title: package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1927988/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926437] Autopkgtest regression report (python-apt/2.2.0~ubuntu0.21.04.1)
All autopkgtests for the newly accepted python-apt (2.2.0~ubuntu0.21.04.1) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: apport/2.20.11-0ubuntu65 (amd64) sshuttle/1.0.4-1ubuntu4 (ppc64el) 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/hirsute/update_excuses.html#python-apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926437 Title: [SRU] Backport zstd support, fix bug in python-apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926926] Re: CVE-2021-27928 et al affects MariaDB in Ubuntu
You might want to consider issuing a USN for these updates as well. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926926 Title: CVE-2021-27928 et al affects MariaDB in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.5/+bug/1926926/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927491] Re: sru cloud-init (21.1-19 to 21.2-0) Bionic, Focal, Groovy, and Hirsute
** Tags added: verification-needed-bionic verification-needed-focal verification-needed-groovy verification-needed-hirsute ** Also affects: cloud-init (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927491 Title: sru cloud-init (21.1-19 to 21.2-0) Bionic, Focal, Groovy, and Hirsute To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1927491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923036] Re: [SRU] Ussuri stable releases
This bug was fixed in the package nova - 2:21.2.0-0ubuntu1 --- nova (2:21.2.0-0ubuntu1) focal; urgency=medium * New stable point release for OpenStack Ussuri (LP: #1923036). * d/p/lp1888395-*: Removed after patch landed upstream. nova (2:21.1.2-0ubuntu2) focal; urgency=medium * Fix live migration for SDNs that do not support port binding extensions (LP: #1888395) - d/p/lp1888395-functest.patch: Add functional test to validate live migration failure with multiport bindings - d/p/lp1888395-migration.patch: Validate the SDN supports port binding extensions before populating migrate_data with vifs -- Chris MacNaughton Mon, 12 Apr 2021 12:14:07 + ** Changed in: nova (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923036 Title: [SRU] Ussuri stable releases To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1923036/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
This bug was fixed in the package nova - 2:21.2.0-0ubuntu1 --- nova (2:21.2.0-0ubuntu1) focal; urgency=medium * New stable point release for OpenStack Ussuri (LP: #1923036). * d/p/lp1888395-*: Removed after patch landed upstream. nova (2:21.1.2-0ubuntu2) focal; urgency=medium * Fix live migration for SDNs that do not support port binding extensions (LP: #1888395) - d/p/lp1888395-functest.patch: Add functional test to validate live migration failure with multiport bindings - d/p/lp1888395-migration.patch: Validate the SDN supports port binding extensions before populating migrate_data with vifs -- Chris MacNaughton Mon, 12 Apr 2021 12:14:07 + ** Changed in: nova (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888395] Update Released
The verification of the Stable Release Update for nova 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
** Summary changed: - on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login + on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
Thanks for the feedback folks. We spent some time thinking through this and the goals of the split and have come up with using -base and -extras. There's some prior art to this in the archive and we don't want to go with any naming convention that would indicate a "value" judgment on the two different packages. The goal is to call out the ones that the Ubuntu Server team has tested and validated and the others which the community provides and are valid for specific use cases, but do not have that level of assurance from our team as we work with these packages. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927983] Re: package r-cran-mgcv 1.8-31-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration
** Package changed: ubuntu => mgcv (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927983 Title: package r-cran-mgcv 1.8-31-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mgcv/+bug/1927983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1827442] Re: [MIR] libheif
It's unclear to me if this ever was approved by the MIR team, possibly comment 1 was intended to be a MIR team review, but it's not clear if that was the intention and certainly doesn't have the normal MIR review details. Technically after security team review, this should have been changed to status 'In Progress' to wait for seeding updates, but I think this got 'lost' in the process since it was in state 'CONFIRMED' but the MIR team has only been looking at 'NEW' state unclaimed bugs. @paelzer I updated the 'All open unclaimed MIR bugs' link on the MIR wiki page to show both NEW and CONFIRMED bugs, and I think we should be sure to include 'CONFIRMED' state bugs in our weekly review, not just 'NEW' state bugs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827442 Title: [MIR] libheif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libde265/+bug/1827442/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927995] [NEW] i dont know
Public bug reported: apparently a bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.15.10 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME Date: Tue May 11 02:14:41 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: LANGUAGE=en_AU.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: grub-installer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: grub-installer (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.15.10 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927995 Title: i dont know To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1927995/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927994] [NEW] /usr/lib/update-notifier/backend_helper.py:FileNotFoundError:/usr/lib/update-notifier/backend_helper.py@166:show_updates:call:__init__:_execute_child
Public bug reported: update-notifier-common depends on update-manager-core and update- notifier depends on update-manager | update-manager-gnome. However, calling "backend_helper.py show_updates" from update-notifier-common will crash w/o update-manager. (focal-amd64)root@impulse:/home/bdmurray/tmp# /usr/bin/python3 /usr/lib/update-notifier/backend_helper.py show_updates Traceback (most recent call last): File "/usr/lib/update-notifier/backend_helper.py", line 166, in res = f(**f_kwargs) File "/usr/lib/update-notifier/backend_helper.py", line 22, in show_updates res = subprocess.call(cmd) File "/usr/lib/python3.8/subprocess.py", line 340, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.8/subprocess.py", line 854, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'update-manager' [Errors Bucket] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.36, the problem page at https://errors.ubuntu.com/problem/0d32a54a459e849834245732febb0b408adddecc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal groovy hirsute rls-ii-incoming xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927994 Title: /usr/lib/update-notifier/backend_helper.py:FileNotFoundError:/usr/lib /update- notifier/backend_helper.py@166:show_updates:call:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927993] [NEW] Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
Public bug reported: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". ** Affects: ubuntu Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
it did it again after many hours ** Attachment added: "this is from running sudo journalctl -b-1 |tee ~/tmp/prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+attachment/5496196/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
"package" Not passage. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
Also, the Activities overview is unresponsive to touchpad interaction. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926949] Re: FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)`
** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402474 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926949 Title: FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927994] Re: /usr/lib/update-notifier/backend_helper.py:FileNotFoundError:/usr/lib/update-notifier/backend_helper.py@166:show_updates:call:__init__:_execute_child
** Description changed: + update-notifier-common depends on update-manager-core and update- + notifier depends on update-manager | update-manager-gnome. However, + calling "backend_helper.py show_updates" from update-notifier-common + will crash w/o update-manager. + + (focal-amd64)root@impulse:/home/bdmurray/tmp# /usr/bin/python3 /usr/lib/update-notifier/backend_helper.py show_updates + Traceback (most recent call last): + File "/usr/lib/update-notifier/backend_helper.py", line 166, in + res = f(**f_kwargs) + File "/usr/lib/update-notifier/backend_helper.py", line 22, in show_updates + res = subprocess.call(cmd) + File "/usr/lib/python3.8/subprocess.py", line 340, in call + with Popen(*popenargs, **kwargs) as p: + File "/usr/lib/python3.8/subprocess.py", line 854, in __init__ + self._execute_child(args, executable, preexec_fn, close_fds, + File "/usr/lib/python3.8/subprocess.py", line 1702, in _execute_child + raise child_exception_type(errno_num, err_msg, err_filename) + FileNotFoundError: [Errno 2] No such file or directory: 'update-manager' + + [Errors Bucket] The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.36, the problem page at https://errors.ubuntu.com/problem/0d32a54a459e849834245732febb0b408adddecc contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927994 Title: /usr/lib/update-notifier/backend_helper.py:FileNotFoundError:/usr/lib /update- notifier/backend_helper.py@166:show_updates:call:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
** Description changed:
[Impact]
+ rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. This is caused because the daemon uses the
strtok() function which is not thread safe.
- * An explanation of the effects of the bug on users and
-
- * justification for backporting the fix to the stable release.
-
- * In addition, it is helpful, but not required, to include an
- explanation of how the upload fixes this bug.
+ The fix from upstream removes strtok() and uses strsep() instead. These
+ patches are already applied in focal and later, via merges from debian.
[Test Plan]
# Create a bionic VM. Login and get its ip, and take note of it:
export IP=$(ip route get default 8.8.8.8 | grep ^8 | awk '{print $7}')
echo $IP
# adjust /etc/hosts:
echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
# adjust /etc/resolv.conf:
echo "search example.com" | sudo tee -a /etc/resolv.conf
# verify hostname -f returns the fqdn of the vm, i.e., a name with the
.example.com domain:
hostname -f
# Run these commands, and when asked:
# - for realm: EXAMPLE.COM
# - for kdc and admin server: use the vm's IP
sudo apt update && sudo apt install nfs-server krb5-kdc krb5-admin-
server krb5-user gcc
# create a kerberos realm. When prompted, use any password you want:
sudo krb5_newrealm
# create an nfs service ticket, and store it in the keytab
sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
# create test directories
sudo mkdir -p /mnt/test_krb5/
sudo mkdir -p /export
sudo touch /export/foo
# adjust nfs config and restart the nfs server:
sudo sed -r -i "s,^NEED_SVCGSSD=.*,NEED_SVCGSSD=\"yes\","
/etc/default/nfs-kernel-server
sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
sudo systemctl restart nfs-server
# configure an nfs export:
echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a /etc/exports
sudo exportfs -rva
# confirm it's available
sudo showmount -e localhost
# mount it
sudo mount $(hostname -f):/export /mnt/test_krb5/
sudo ls -la /mnt/test_krb5
# download bug attachments
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496166/+files/stat_as.c
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496167/+files/bz1419280_test_threads
chmod +x bz1419280_test_threads
# build reproducer
gcc stat_as.c -o stat_as
# run test script as root. It may take a few minutes to trigger the bug
sudo ./bz1419280_test_threads
# wait
# Once you get the confirmation:
calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
reproduced the bug after 114 iterations
# Check for a "stat_as" D state process:
$ ps axw|grep stat_as
17814 pts/1D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035
# With the updated packages, the script will not detect the bug and
never stop.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
* and address these questions in advance
[Original Description]
Fixed in focal and later, due to sync from debian
Bionic affected.
I'll add a proper description in a moment.
RH: https://bugzilla.redhat.com/show_bug.cgi?id=1419280
Debian BTS: https://bugs.debian.org/895381
ML: http://www.spinics.net/lists/linux-nfs/msg62111.html
ML: http://www.spinics.net/lists/linux-nfs/msg62099.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927745
Title:
Non-thread-safe functions used in multi-threaded rpc.gssd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
** Description changed: Snapd will soon support to have DTBs in the kernel snap that are automatically installed on kernel refreshes. To support this, please add the following file to the pi-kernel: This should also add "assumes: [kernel-assets]" to the meta/snap.yaml so that the updated kernel/gadget are only used by a snap version that understand this, see https://github.com/snapcore/snapd/pull/ $ cat meta/kernel.yaml assets: pidtbs: update: true content: - - dtbs/broadcom/ - - dtbs/overlays/ + - dtbs/ - This will allow the gadget to select DTBs from the kernel. The gadget - needs to be updated to have all dtb files removed. And the gadget.yaml - needs to change to something like + This will allow the gadget to select DTBs from the kernel. The arm64 + gadget needs to be updated to have all dtb files removed. And the + gadget.yaml needs to change to something like $ head -20 meta/gadget.yaml device-tree: bcm2709-rpi-3-b-plus volumes: pi: schema: mbr bootloader: u-boot structure: - name: ubuntu-seed role: system-seed filesystem: vfat type: 0C size: 1200M content: - source: $kernel:pidtbs/dtbs/broadcom/ target: / - source: $kernel:pidtbs/dtbs/overlays/ target: /overlays - source: boot-assets/ target: / - name: ubuntu-boot role: system-boot ... + + AFAICT the armhf needs to be updated differently because the layout + of the dtbs folder is different in the armhf kernel: + + $ head -20 meta/gadget.yaml + volumes: + pi: + schema: mbr + bootloader: u-boot + structure: + - name: ubuntu-seed + role: system-seed + filesystem: vfat + type: 0C + size: 1200M + content: + - source: $kernel:pidtbs/dtbs/ + target: / + - source: boot-assets/ + target: / + - name: ubuntu-boot + role: system-boot + + + If those could be provided in a snap branch that would be *amazing* -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode. To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1927993/+editstatus and add the package name in the text box next to the word Package. [This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.] ** Tags added: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927980] Re: smartd-runner bug causes loss of email recipients
The attachment "smartd-runner.diff" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927980 Title: smartd-runner bug causes loss of email recipients To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1927980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927978] Re: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable
** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927978 Title: Please merge db5.3 5.3.28+dfsg1-0.8 from Debian unstable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/db5.3/+bug/1927978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927161] Re: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one
ubuntu@lp1927161-h:~$ pull-lp-source openssl hirsute ... ubuntu@lp1927161-h:~$ cd openssl-1.1.1j/ ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-parsechangelog | grep Version Version: 1.1.1j-1ubuntu3.1 ubuntu@lp1927161-h:~/openssl-1.1.1j$ quilt pop -a ubuntu@lp1927161-h:~/openssl-1.1.1j$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1j-1ubuntu3.1 dpkg-buildpackage: info: source distribution hirsute dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ubuntu@lp1927161-g:~$ pull-lp-source openssl groovy ... ubuntu@lp1927161-g:~$ cd openssl-1.1.1f/ ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-parsechangelog | grep Version Version: 1.1.1f-1ubuntu4.4 ubuntu@lp1927161-g:~/openssl-1.1.1f$ quilt pop -a ... ubuntu@lp1927161-g:~/openssl-1.1.1f$ dpkg-buildpackage -d -S dpkg-buildpackage: info: source package openssl dpkg-buildpackage: info: source version 1.1.1f-1ubuntu4.4 dpkg-buildpackage: info: source distribution groovy dpkg-buildpackage: info: source changed by Matthew Ruffell ... dpkg-buildpackage: info: binary and diff upload (original source NOT included) ** Tags removed: verification-needed verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927161 Title: dpkg-source: error: diff 'openssl/debian/patches/pr12272.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a single one To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1927161/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927997] [NEW] Focal update: v5.4.115 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.115 upstream stable release from git://git.kernel.org/ gpio: omap: Save and restore sysconfig pinctrl: lewisburg: Update number of pins in community arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] perf auxtrace: Fix potential NULL pointer dereference HID: google: add don USB id HID: alps: fix error return code in alps_input_configured() HID: wacom: Assign boolean values to a bool variable ARM: dts: Fix swapped mmc order for omap3 net: geneve: check skb is large enough for IPv4/IPv6 header s390/entry: save the caller of psw_idle xen-netback: Check for hotplug-status existence before watching cavium/liquidio: Fix duplicate argument csky: change a Kconfig symbol name to fix e1000 build error ia64: fix discontig.c section mismatches ia64: tools: remove duplicate definition of ia64_mf() on ia64 x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access net: hso: fix NULL-deref on disconnect regression USB: CDC-ACM: fix poison/unpoison imbalance Linux 5.4.115 UBUNTU: upstream stable to v5.4.115 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.115 upstream stable release + from git://git.kernel.org/ -v5.4.115 upstream stable release -from git://git.kernel.org/ + gpio: omap: Save and restore sysconfig + pinctrl: lewisburg: Update number of pins in community + arm64: dts: allwinner: Revert SD card CD GPIO for Pine64-LTS + perf/x86/intel/uncore: Remove uncore extra PCI dev HSWEP_PCI_PCU_3 + perf/x86/kvm: Fix Broadwell Xeon stepping in isolation_ucodes[] + perf auxtrace: Fix potential NULL pointer dereference + HID: google: add don USB id + HID: alps: fix error return code in alps_input_configured() + HID: wacom: Assign boolean values to a bool variable + ARM: dts: Fix swapped mmc order for omap3 + net: geneve: check skb is large enough for IPv4/IPv6 header + s390/entry: save the caller of psw_idle + xen-netback: Check for hotplug-status existence before watching + cavium/liquidio: Fix duplicate argument + csky: change a Kconfig symbol name to fix e1000 build error + ia64: fix discontig.c section mismatches + ia64: tools: remove duplicate definition of ia64_mf() on ia64 + x86/crash: Fix crash_setup_memmap_entries() out-of-bounds access + net: hso: fix NULL-deref on disconnect regression + USB: CDC-ACM: fix poison/unpoison imbalance + Linux 5.4.115 + UBUNTU: upstream stable to v5.4.115 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927997 Title: Focal update: v5.4.115 upstream stable release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927997/+subscriptions -- ubuntu-bugs ma
[Bug 1927996] [NEW] /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:__init__:_execute_child
Public bug reported: update-notifier-common does not depend on lsb-release The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.40.1, the problem page at https://errors.ubuntu.com/problem/b26aeaa1e162c894747c195ce1b13a70c981e3eb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: update-notifier (Ubuntu) Importance: Undecided Status: New ** Tags: focal hirsute xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927996 Title: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib /update- notifier/apt_check.py@16:check_output:run:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927996] Re: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:__init__:_execute_child
Here's the Traceback: Traceback (most recent call last): File "/usr/lib/update-notifier/apt-check", line 16, in DISTRO = subprocess.check_output( File "/usr/lib/python3.9/subprocess.py", line 424, in check_output return run(*popenargs, stdout=PIPE, timeout=timeout, check=True, File "/usr/lib/python3.9/subprocess.py", line 505, in run with Popen(*popenargs, **kwargs) as process: File "/usr/lib/python3.9/subprocess.py", line 951, in __init__ self._execute_child(args, executable, preexec_fn, close_fds, File "/usr/lib/python3.9/subprocess.py", line 1821, in _execute_child raise child_exception_type(errno_num, err_msg, err_filename) FileNotFoundError: [Errno 2] No such file or directory: 'lsb_release' ** Description changed: + update-notifier-common does not depend on lsb-release + The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.40.1, the problem page at https://errors.ubuntu.com/problem/b26aeaa1e162c894747c195ce1b13a70c981e3eb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927996 Title: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib /update- notifier/apt_check.py@16:check_output:run:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926949] Re: FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)`
** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402506 ** Merge proposal linked: https://code.launchpad.net/~chad.smith/ubuntu/+source/ubuntu-advantage-tools/+git/ubuntu-advantage-tools/+merge/402509 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926949 Title: FTBFS: apt can't resolve `dh-systemd | debhelper (>= 13.3)` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1926949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1925010] Re: shim-signed 15.4 does not boot on EFI 1.10 systems
Verified 1.47+15.4-0ubuntu2 on Hirsute on the MacBook Air (MBA 5,2) I have first observed the problem: rbalint@chaos:~$ sudo apt install shim-signed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: shim-signed 1 upgraded, 0 newly installed, 0 to remove and 17 not upgraded. Need to get 447 kB of archives. After this operation, 1.024 B of additional disk space will be used. Get:1 http://hu.archive.ubuntu.com/ubuntu hirsute-proposed/main amd64 shim-signed amd64 1.47+15.4-0ubuntu2 [447 kB] Fetched 447 kB in 0s (2.059 kB/s) Preconfiguring packages ... (Reading database ... 321160 files and directories currently installed.) Preparing to unpack .../shim-signed_1.47+15.4-0ubuntu2_amd64.deb ... Unpacking shim-signed (1.47+15.4-0ubuntu2) over (1.46+15.4-0ubuntu1) ... Setting up shim-signed (1.47+15.4-0ubuntu2) ... Installing grub to /boot/efi. Installing for x86_64-efi platform. Installation finished. No error reported. Scanning processes... Scanning processor microcode... Scanning linux images... Running kernel seems to be up-to-date. The processor microcode seems to be up-to-date. No services need to be restarted. No containers need to be restarted. No user sessions are running outdated binaries. rbalint@chaos:~$ Shared connection to chaos-w closed. $ ssh chaos rbalint@chaos:~$ sudo ls -alhR /boot/efi/EFI/ /boot/efi/EFI/: total 16K drwx-- 4 root root 4,0K jan 18 2018 . drwx-- 3 root root 4,0K jan1 1970 .. drwx-- 2 root root 4,0K febr 4 2019 BOOT drwx-- 3 root root 4,0K febr 7 2020 ubuntu /boot/efi/EFI/BOOT: total 1,9M drwx-- 2 root root 4,0K febr 4 2019 . drwx-- 4 root root 4,0K jan 18 2018 .. -rwx-- 1 root root 933K máj 10 18:24 BOOTX64.EFI -rwx-- 1 root root 84K máj 10 18:24 fbx64.efi -rwx-- 1 root root 837K máj 10 18:24 mmx64.efi /boot/efi/EFI/ubuntu: total 3,5M drwx-- 3 root root 4,0K febr 7 2020 . drwx-- 4 root root 4,0K jan 18 2018 .. -rwx-- 1 root root 108 máj 10 18:24 BOOTX64.CSV -rwx-- 1 root root 82K ápr 19 16:33 fbx64.efi drwx-- 2 root root 4,0K jún3 2017 fw -rwx-- 1 root root 126 máj 10 18:24 grub.cfg -rwx-- 1 root root 1,7M máj 10 18:24 grubx64.efi -rwx-- 1 root root 837K máj 10 18:24 mmx64.efi -rwx-- 1 root root 933K máj 10 18:24 shimx64.efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925010 Title: shim-signed 15.4 does not boot on EFI 1.10 systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1925010/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
** Package changed: ubuntu => wayland (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1927993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
** Description changed:
[Impact]
- rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. This is caused because the daemon uses the
strtok() function which is not thread safe.
+ rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. The problem happens because the daemon uses the
strtok() function which is not thread safe.
The fix from upstream removes strtok() and uses strsep() instead. These
patches are already applied in focal and later, via merges from debian.
[Test Plan]
# Create a bionic VM. Login and get its ip, and take note of it:
export IP=$(ip route get default 8.8.8.8 | grep ^8 | awk '{print $7}')
echo $IP
# adjust /etc/hosts:
echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
# adjust /etc/resolv.conf:
echo "search example.com" | sudo tee -a /etc/resolv.conf
# verify hostname -f returns the fqdn of the vm, i.e., a name with the
.example.com domain:
hostname -f
# Run these commands, and when asked:
# - for realm: EXAMPLE.COM
# - for kdc and admin server: use the vm's IP
sudo apt update && sudo apt install nfs-server krb5-kdc krb5-admin-
server krb5-user gcc
# create a kerberos realm. When prompted, use any password you want:
sudo krb5_newrealm
# create an nfs service ticket, and store it in the keytab
sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
# create test directories
sudo mkdir -p /mnt/test_krb5/
sudo mkdir -p /export
sudo touch /export/foo
# adjust nfs config and restart the nfs server:
sudo sed -r -i "s,^NEED_SVCGSSD=.*,NEED_SVCGSSD=\"yes\","
/etc/default/nfs-kernel-server
sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
sudo systemctl restart nfs-server
# configure an nfs export:
echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a /etc/exports
sudo exportfs -rva
# confirm it's available
sudo showmount -e localhost
# mount it
sudo mount $(hostname -f):/export /mnt/test_krb5/
sudo ls -la /mnt/test_krb5
# download bug attachments
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496166/+files/stat_as.c
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496167/+files/bz1419280_test_threads
chmod +x bz1419280_test_threads
# build reproducer
gcc stat_as.c -o stat_as
# run test script as root. It may take a few minutes to trigger the bug
sudo ./bz1419280_test_threads
# wait
# Once you get the confirmation:
calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
reproduced the bug after 114 iterations
# Check for a "stat_as" D state process:
$ ps axw|grep stat_as
17814 pts/1D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035
- # With the updated packages, the script will not detect the bug and
- never stop.
+ # To restore functionality, restart rpc-gssd:
+ sudo systemctl restart rpc-gssd.service
+
+
+ With the updated packages, the script will not detect the bug and never stop.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
* and address these questions in advance
[Original Description]
Fixed in focal and later, due to sync from debian
Bionic affected.
I'll add a proper description in a moment.
RH: https://bugzilla.redhat.com/show_bug.cgi?id=1419280
Debian BTS: https://bugs.debian.org/895381
ML: http://www.spinics.net/lists/linux-nfs/msg62111.html
ML: http://www.spinics.net/lists/linux-nfs/msg62099.html
** Description changed:
[Impact]
rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. The problem happens because the daemon uses the
strtok() function which is not thread safe.
The fix from upstream removes strtok() and uses strsep() instead. These
patches are already applied in focal and later, via merges from debian.
[Test Plan]
+ As with all race conditions, this test case may take a while to reproduce the
problem.
+
# Create a bion
[Bug 1888395] Re: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration
** Changed in: cloud-archive/ussuri Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888395 Title: live migration of a vm using the single port binding work flow is broken in train as a result of the introduction of sriov live migration To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1888395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927998] [NEW] Jitter/noise in document scan
Public bug reported: Ubuntu 21.04 Documentscanner 3.38.1 When using the documentscanner about 10 times, without restarting the app, closing the previous scan (delete button), starting a new scan everytime, the background window (white) shows jitter/noise (in black) which will stay there every next scan. It may even become worse. The noise become part of the actual scan too! You will have to stop the app and reconnect the scanner. I've noticed this problem to be reproducable. See attached screen output. Kind regards, Gerard van Drielen ** Affects: ubuntu Importance: Undecided Status: New ** Attachment added: "Schermafdruk van 2021-05-09 10-37-51.png" https://bugs.launchpad.net/bugs/1927998/+attachment/5496206/+files/Schermafdruk%20van%202021-05-09%2010-37-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927998 Title: Jitter/noise in document scan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1927998/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926641] Re: FFADO 2.4.4 only runs properly with sudo
Pander, I don't know why you refuse to report these bugs to Debian. It's a Debain-imported package and no Ubuntu developer has touched it. The way it works is that Ubuntu syncs packages from Debian during the development cycle. Unless you see a "-xUbuntux" in the package name, it's a Debian package. PLEASE report this bug to Debian. Thank you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926641 Title: FFADO 2.4.4 only runs properly with sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1926641/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927996] Re: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:__init__:_execute_child
** Description changed: - update-notifier-common does not depend on lsb-release + update-notifier-common does not depend on lsb-release and both + apt_check.py and apt-cdrom-check both utilize lsb_release. The Ubuntu Error Tracker has been receiving reports about a problem regarding update-notifier. This problem was most recently seen with package version 3.192.40.1, the problem page at https://errors.ubuntu.com/problem/b26aeaa1e162c894747c195ce1b13a70c981e3eb contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927996 Title: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib /update- notifier/apt_check.py@16:check_output:run:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921475] Re: [2.9.2] Commissioning does not collect correct storage information
systemd doesn't report any 'E:ID_ATA_ROTATION_RATE_RPM' value for the SCSI drive, because it's a SCSI drive, not an ATA drive. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921475 Title: [2.9.2] Commissioning does not collect correct storage information To manage notifications about this bug go to: https://bugs.launchpad.net/lxd/+bug/1921475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 461628] Re: /var/lib/dpkg/info/ffado-mixer-qt4.postinst: line 3: xdg-desktop-icon: command not found
** Changed in: libffado (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/461628 Title: /var/lib/dpkg/info/ffado-mixer-qt4.postinst: line 3: xdg-desktop-icon: command not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/461628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1790707] Re: ffado-mixer crashed with RuntimeError in /usr/share/ffado-mixer-qt4/ffado/import_pyqt.py: the PyQt5.QtCore and PyQt4.QtCore modules both wrap the QObject class
** Changed in: libffado (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790707 Title: ffado-mixer crashed with RuntimeError in /usr/share/ffado-mixer- qt4/ffado/import_pyqt.py: the PyQt5.QtCore and PyQt4.QtCore modules both wrap the QObject class To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1790707/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1705821] Re: ffado-diag crashed with TypeError in : bad operand type for unary -: '_Helper'
Thank you for reporting this bug to Ubuntu. Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: libffado (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1705821 Title: ffado-diag crashed with TypeError in : bad operand type for unary -: '_Helper' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1705821/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 445823] Re: jackd can't connect to firewire sound card
** Changed in: libffado (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/445823 Title: jackd can't connect to firewire sound card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/445823/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794539] Re: ffado-mixer crashes immediately on invocation with ValueError
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Debian/Bugs. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794539 Title: ffado-mixer crashes immediately on invocation with ValueError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1794539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927999] [NEW] 20.04 installer Errno 5
Public bug reported: I have a laptop that was running 18.04, 20.04 would not install. 21.04 also failed. Fedora 34 installed without issue. Ubuntu GUI said The installer encountered an error copying files to the hard disk: [Errno 5] dmesg said SQUASHFS error: zlib decompression failed, data probably corrupt SQUASHFS error: failed to read block 0x2df825be: -5 /var/log/casper.log said cannot read /var/lib/dpkg/info/diffutils.list (Input/output error) the iso sha matches, badblocks and cat found no issues with the source or destination disk. ** Affects: base-installer (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927999 Title: 20.04 installer Errno 5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1927999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1794539] Re: ffado-mixer crashes immediately on invocation with ValueError
After evaluating this bug, it would be impossible to upgrade the verison of FFADO in Ubuntu 18.04 to a newer version, especially considering it's in the Universe repository which is only supported for 3 years. Closing. ** Changed in: libffado (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1794539 Title: ffado-mixer crashes immediately on invocation with ValueError To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1794539/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927996] Re: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib/update-notifier/apt_check.py@16:check_output:run:__init__:_execute_child
** Changed in: update-notifier (Ubuntu) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: update-notifier (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927996 Title: /usr/lib/update-notifier/apt_check.py:FileNotFoundError:/usr/lib /update- notifier/apt_check.py@16:check_output:run:__init__:_execute_child To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1927996/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928000] [NEW] open-iscsi fails to upgrade (2.0.874-7.1ubuntu6.2)
Public bug reported: When upgrading my ubuntu 20.04.2 with "sudo apt-get dist-upgrade" the upgrade hangs after the following error: Setting up open-iscsi (2.0.874-7.1ubuntu6.2) ... grep: /lib/modules-load.d/open-iscsi.conf: No such file or directory After a couple of hours I killed the process and now I have package problems: E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Actually, the folder /lib/modules-load.d is empty. The configuration of the package open-iscsi is pretty standard, I used the command iscsiadm and put my configuration files in /etc/iscsi, I definitely didn't touch the modules. I am still able to connect to a remote disk using the iscsi protocol. Ubuntu release: Ubuntu 20.04.2 LTS Package version: - Previous: 2.0.874-7.1ubuntu6.1 - Installed (failed to complete): 2.0.874-7.1ubuntu6.2 ** Affects: open-iscsi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928000 Title: open-iscsi fails to upgrade (2.0.874-7.1ubuntu6.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1928000/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
Thanks Rick. > There's some prior art to this in the archive I think it would really be good for the server team to follow up on this naming convention and get some agreement across the distro (not only for server team maintained packages), as we don't want different teams/people coming up with different naming conventions/styles for the same problem. And then it would be great if it was documented somewhere, maybe at https://packaging.ubuntu.com/html/packaging-new-software.html and/or we could add it to the MIR wiki page (though MIR isn't really the only, or even correct, time for package binary deb naming to be evaluated). Also note that while 'base' and 'extra' might have been used before, you might not have seen Seth's comment 7 that indicated it didn't turn out very well for apparmor, so maybe 'base' and 'extra' aren't the best names, even if they've been used before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1926050/+attachment/5496207/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1926050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system
I can't report crashes in the var / crash, an error appears that the program is not installed. If you want I can send it as an attachment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1926050/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928001] [NEW] [SRU] New stable release 2.68.1
Public bug reported: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ 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. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Hirsute) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1907056] Re: Please add meta/kernel.yaml
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: snapd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1907056 Title: Please add meta/kernel.yaml To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1907056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
I am testing this again (this is supposed to work OOTB now, at least on Intel GPUs), and I'm seeing the following: libva info: VA-API version 1.9.0 libva info: User environment variable requested driver 'i965' libva info: Trying to open /snap/chromium/1568/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: va_openDriver() returns -1 even when I explicitly export LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri. This is caused by the snapcraft gnome-3-28 extension unconditionally overriding LIBVA_DRIVERS_PATH here: https://github.com/snapcore/snapcraft/blob/master/extensions/desktop/common /desktop-exports#L92 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816497 Title: [snap] vaapi chromium no video hardware decoding To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927865] Re: Ubuntu 20.04 missing pip binary
Verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927865 Title: Ubuntu 20.04 missing pip binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1927865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914239] Re: ubuntu-20.04 pip3 ignores /etc/pip.conf
Verified. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914239 Title: ubuntu-20.04 pip3 ignores /etc/pip.conf To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1914239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926437] Autopkgtest regression report (python-apt/2.0.0ubuntu0.20.04.5)
All autopkgtests for the newly accepted python-apt (2.0.0ubuntu0.20.04.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: unattended-upgrades/2.3ubuntu0.1 (armhf) apt-clone/0.4.1ubuntu3 (ppc64el, amd64, arm64, s390x, 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/focal/update_excuses.html#python-apt [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926437 Title: [SRU] Backport zstd support, fix bug in python-apt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1926437/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909131] Re: [radeon] wayland - cursor is not affected by night light mode
Could you send a tutorial for the installation? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909131 Title: [radeon] wayland - cursor is not affected by night light mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
** Description changed:
[Impact]
rpc-gssd can hang or crash when a kerberos nfsv4 mount point is accessed by
multiple users simultaneously. The problem happens because the daemon uses the
strtok() function which is not thread safe.
The fix from upstream removes strtok() and uses strsep() instead. These
patches are already applied in focal and later, via merges from debian.
[Test Plan]
As with all race conditions, this test case may take a while to reproduce the
problem.
# Create a bionic VM. Login and get its ip, and take note of it:
export IP=$(ip route get default 8.8.8.8 | grep ^8 | awk '{print $7}')
echo $IP
# adjust /etc/hosts:
echo "$IP $(hostname).example.com" | sudo tee -a /etc/hosts
# adjust /etc/resolv.conf:
echo "search example.com" | sudo tee -a /etc/resolv.conf
# verify hostname -f returns the fqdn of the vm, i.e., a name with the
.example.com domain:
hostname -f
# Run these commands, and when asked:
# - for realm: EXAMPLE.COM
# - for kdc and admin server: use the vm's IP
sudo apt update && sudo apt install nfs-server krb5-kdc krb5-admin-
server krb5-user gcc
# create a kerberos realm. When prompted, use any password you want:
sudo krb5_newrealm
# create an nfs service ticket, and store it in the keytab
sudo kadmin.local -q "addprinc -randkey nfs/$(hostname -f)"
sudo kadmin.local -q "ktadd nfs/$(hostname -f)"
# create test directories
sudo mkdir -p /mnt/test_krb5/
sudo mkdir -p /export
sudo touch /export/foo
# adjust nfs config and restart the nfs server:
sudo sed -r -i "s,^NEED_SVCGSSD=.*,NEED_SVCGSSD=\"yes\","
/etc/default/nfs-kernel-server
sudo sed -r -i "s,^NEED_GSSD=.*,NEED_GSSD=\"yes\"," /etc/default/nfs-common
sudo systemctl restart nfs-server
# configure an nfs export:
echo "/export *(sec=krb5,rw,sync,no_subtree_check)" | sudo tee -a /etc/exports
sudo exportfs -rva
# confirm it's available
sudo showmount -e localhost
# mount it
sudo mount $(hostname -f):/export /mnt/test_krb5/
sudo ls -la /mnt/test_krb5
# download bug attachments
wget -ct0
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496166/+files/stat_as.c
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+attachment/5496167/+files/bz1419280_test_threads
chmod +x bz1419280_test_threads
# build reproducer
gcc stat_as.c -o stat_as
# run test script as root. It may take a few minutes to trigger the bug
sudo ./bz1419280_test_threads
# wait
# Once you get the confirmation:
calling stat on '/mnt/test_krb5/foo' with uids 9995 through 10035
reproduced the bug after 114 iterations
# Check for a "stat_as" D state process:
$ ps axw|grep stat_as
17814 pts/1D 0:00 ./stat_as /mnt/test_krb5/foo 9995 10035
# To restore functionality, restart rpc-gssd:
sudo systemctl restart rpc-gssd.service
With the updated packages, the script will not detect the bug and never
stop.
[Where problems could occur]
-
- * Think about what the upload changes in the software. Imagine the change is
- wrong or breaks something else: how would this show up?
-
- * It is assumed that any SRU candidate patch is well-tested before
- upload and has a low overall risk of regression, but it's important
- to make the effort to think about what ''could'' happen in the
- event of a regression.
-
- * This must '''never''' be "None" or "Low", or entirely an argument as to why
- your upload is low risk.
-
- * This both shows the SRU team that the risks have been considered,
- and provides guidance to testers in regression-testing the SRU.
+ NFS v4 services are more complex than earlier versions, and are comprised of
several services/daemons. It's possible for the restart done after the
automatic package upgrade to show up as a regression due to several factors:
+ - not all needed services were restarted (bug, but not introduced by this
change)
+ - depending on mount options, client mount points may appear as hung and take
a while to recover
+ - configuration errors on the server which were up until now not noticed, and
only manifest themselves after a restart
+ - some sites, due to the lack of configuration options in /etc/default/nfs-*,
might have overriden systemd service files and hardcoded other command line
options there. If not done properly (i.e., not done in /etc/systemd via
overrides), these local changes will be lost after the package upgrade
[Other Info]
+ The upstream patches have been applied since February 2017 and have not been
changed or reverted. They are also applied in Debian and Fedora, and ubuntu
since focal at least.
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and
the Technical Board
- * and address these questions in advance
+ There is an additional patch, but part of the fix, which dupes the
[Bug 1851671] Re: CVE 2019-3465
** Changed in: simplesamlphp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1851671 Title: CVE 2019-3465 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simplesamlphp/+bug/1851671/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1926355] Re: Snap applications segfault with new core20 (rev: 1015+)
Unfortunately I don't know how to easily remove glibc from the snaps in a way that would confirm that they work, I don't have time to manually build all of these snaps that are broken, I tried the basic thing of unpacking the snap and `rm -rf ./lib/x86_64-linux-gnu/libc-2.31.so ./lib/x86_64-linux-gnu/libc.so.6` and then repacking and installing these snaps, but then the still segfault and fail with: $ snap run htop *** stack smashing detected ***: terminated Aborted (core dumped) Which I don't know if that's because I didn't fully remove traces of glibc from the snap or if it's because beta version of core20 (snap revision 1015) is still broken. I did try building the matterhorn snap since I found the source for it at https://github.com/popey/matterhorn-snap.git, but that doesn't seem to build at all. Perhaps Sergio can help confirm if these snaps work if rebuilt without libc6 getting staged into the snap? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926355 Title: Snap applications segfault with new core20 (rev: 1015+) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-core20/+bug/1926355/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1914239] Autopkgtest regression report (python-pip/20.0.2-5ubuntu1.4)
All autopkgtests for the newly accepted python-pip (20.0.2-5ubuntu1.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: doit/0.31.1-3.2ubuntu1 (ppc64el, amd64, arm64, s390x, 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/focal/update_excuses.html#python-pip [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1914239 Title: ubuntu-20.04 pip3 ignores /etc/pip.conf To manage notifications about this bug go to: https://bugs.launchpad.net/pip/+bug/1914239/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927865] Autopkgtest regression report (python-pip/20.0.2-5ubuntu1.4)
All autopkgtests for the newly accepted python-pip (20.0.2-5ubuntu1.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: doit/0.31.1-3.2ubuntu1 (ppc64el, amd64, arm64, s390x, 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/focal/update_excuses.html#python-pip [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927865 Title: Ubuntu 20.04 missing pip binary To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1927865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927712] Re: The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic
Hi David, on "main" vs "universe" see: https://help.ubuntu.com/community/Repositories/Ubuntu For community help, possibly on driving a Stable Release Upgrade, see: https://ubuntu.com/support/community-support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927712 Title: The Pacemaker module "ocf:heartbeat:CTDB" does not work on Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1927712/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927078] Re: Don't allow useradd to use fully numeric names
** Tags added: fr-1357 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927078 Title: Don't allow useradd to use fully numeric names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927745] Re: Non-thread-safe functions used in multi-threaded rpc.gssd
** Merge proposal linked: https://code.launchpad.net/~ahasenack/ubuntu/+source/nfs-utils/+git/nfs-utils/+merge/402515 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927745 Title: Non-thread-safe functions used in multi-threaded rpc.gssd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1927745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927004] Re: [MIR] fence-agents
"Also note that while 'base' and 'extra' might have been used before, you might not have seen Seth's comment 7 that indicated it didn't turn out very well for apparmor, so maybe 'base' and 'extra' aren't the best names, even if they've been used before." Thanks, I did see that and we discussed it. That was my direct reply about avoiding terms that imply judgment. I appreciate that it would be good to have a common ground on how to go about this problem. That said, in our discussions, we're finding different cases at play. In our case, the agents that we're looking to place into Main are ones that we feel cover some 80% of the typical use cases along with some particular ones that our team has an interest in adding testing and validation. The other agents are not bad or any less, it's just an admission that the ones in Main our team will be working on that testing, adding documentation to the server guide, etc. We cannot provide that for all of them and thus the split to help reality and expectations align. Honestly, most use cases will only leverage a single fence-agent or resource-agent and in an ideal world they'd all be independent packages that could be treated as individuals but the burden of 45+ different packages for this would be unsustainable from the team. In our case -core doesn't work because you don't have to have that package installed to use anything from -extras. You also can't replace using something in -extras with something in base. Good/bad are not legitimate distinguishers imo. Supported is indeed overloaded and not the best wording. In the end, I don't know that a single "this is how to do it" fits in the myriad of use cases we've discussed so far. Given that there's not a current single-use case I've encouraged the team to not let perfect be the enemy of the good and help move forward the work we're doing to build out a well-supported set of tools for HA on Ubuntu. I very much appreciate the feedback and think we're heading in a better direction than started. I'm happy to dive more into the discussions and if there's a better pattern that's been identified that works with the concerns I've raised I'm happy to learn about them. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927004 Title: [MIR] fence-agents To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fence-agents/+bug/1927004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927029] Re: ua attach command fails
snap --version: $ snap --version snap2.49.2 snapd 2.49.2 series 16 ubuntu 16.04 kernel 4.4.0-145-generic Tried the steps here: $ sudo ua disable livepatch Livepatch is not currently enabled See: sudo ua status Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools $ sudo snap remove --purge livepatch snap "livepatch" is not installed $ sudo ua enable livepatch One moment, checking your subscription first Unable to configure Livepatch: Failed running command '/snap/bin/canonical-livepatch config remote-server=https://livepatch.canonical.com' [exit(1)]. Message: 2021/05/10 18:04:55 error executing config: Livepatchd error: Couldn't setup system logger. ERROR: Unable to configure Livepatch: Failed running command '/snap/bin /canonical-livepatch config remote- server=https://livepatch.canonical.com' [exit(1)]. Message: 2021/05/10 18:04:55 error executing config: Livepatchd error: Couldn't setup system logger. Unexpected error(s) occurred. For more details, see the log: /var/log/ubuntu-advantage.log To file a bug run: ubuntu-bug ubuntu-advantage-tools -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903312] Re: Ubiquity not selecting correct timezone when connected to Internet
@leok - Do you have another location and WiFi network where you can test this? It'd be interesting to know if it happens there. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903312 Title: Ubiquity not selecting correct timezone when connected to Internet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoip-database/+bug/1903312/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927029] Re: ua attach command fails
Attaching the full ubuntu-advantage.log file too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1927886] Re: xenial powerpc build failures golang dependency issues
** Also affects: ubuntu-advantage-tools (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: ubuntu-advantage-tools (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: ubuntu-advantage-tools (Ubuntu) Status: New => Fix Committed ** Also affects: ubuntu-advantage-tools (Ubuntu Impish) Importance: Undecided Status: Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927886 Title: xenial powerpc build failures golang dependency issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1927886/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
