[Bug 1893984] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (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/1893984 Title: Wayland is still unstable with ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888653] Re: [UBUNTU 20.10] GCC: Accept vector alignment hints on z13
20.04 will be done, whenever gcc packages will be updated again in focal, batched up with other gcc upstream point release. I don't have an ETA at the moment. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888653 Title: [UBUNTU 20.10] GCC: Accept vector alignment hints on z13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1888653/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1273258] Re: Hundreds of dbus-daemon processes
I have the same bug: a number of /usr/bin/dbus-deamon processes which spawn from "/sbin/init splash". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1273258 Title: Hundreds of dbus-daemon processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1273258/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1672091] Re: new tool for nvme target configuration in 4.8 on up kernels
@ddstreet, I spoke to Server team about this yesterday as we all agreed we should talk to Linux Blocks Teams (salsa.debian.org/linux-blocks-team/ , and Bruno Leitao ?) if they have any plans in creating this package (together with nvme-cli). Idea is that we can try to sync it (hopefully with no delta) back to 21.04. We can start in universe in the beginning and, as soon as we're comfy, do a MIR if that makes sense (just like we recently did with LIO and targetcli). Since you're already taking care of LP: #1867366, would you like to ask Debian project about it or you want me to do ? I can start checking this in a few days if needed. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1672091 Title: new tool for nvme target configuration in 4.8 on up kernels To manage notifications about this bug go to: https://bugs.launchpad.net/yakkety-backports/+bug/1672091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893984] [NEW] Wayland is still unstable with ubuntu 20.04
Public bug reported: Wayland is running almost smoothly on Ubuntu 20.04,however there are some small issues that should be addressed. .the run command (ALT+F2) is not working correctly ...For example "r" for restarting the gnome-shell doesn't work. .my computer froze on a wayland session .geometry specified in the .config for apps like Mpv are ignored in wayland sessions ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern 1436 F pulseaudio /dev/snd/pcmC0D0p: regern 1436 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Sep 2 21:06:01 2020 InstallationDate: Installed on 2020-05-16 (109 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro transparent_hugepage=never quiet splash DEEPIN_GFXMODE= vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893984 Title: Wayland is still unstable with ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800012] Re: ogg vorbis corruption
Is there a timeline for when the fix for Focal will be released? I have corrupted half my music collection due to this bug, good thing I had a backup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800012 Title: ogg vorbis corruption To manage notifications about this bug go to: https://bugs.launchpad.net/taglib/+bug/1800012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893983] [NEW] package libopencore-amrnb0 (not installed) failed to install/upgrade: subprocess dpkg-split returned error exit status 2
Public bug reported: Am installing xubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libopencore-amrnb0 (not installed) ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic i686 ApportVersion: 2.20.9-0ubuntu7 Architecture: i386 Date: Wed Sep 2 14:38:44 2020 ErrorMessage: subprocess dpkg-split returned error exit status 2 Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: opencore-amr Title: package libopencore-amrnb0 (not installed) failed to install/upgrade: subprocess dpkg-split returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: opencore-amr (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package bionic i386 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893983 Title: package libopencore-amrnb0 (not installed) failed to install/upgrade: subprocess dpkg-split returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/opencore-amr/+bug/1893983/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli
Okay, checking focal source code..
config::hostid seems to used at:
build_options() <- generic function setting variables
connect_ctrl() <- function connecting to NVMEoF controller
connect() <- function to to connect to NVMEoF
discover() <- same thing
nvmf_hostid_file() <- function reading config file and setting variable
So, for connect() we do have:
{"hostnqn", 'q', "LIST", CFG_STRING, ,
required_argument, "user-defined hostnqn" },
{"hostid", 'I', "LIST", CFG_STRING, ,
required_argument, "user-defined hostid (if default not used)"},
and for discovery we have:
{"hostnqn", 'q', "LIST", CFG_STRING, ,
required_argument, "user-defined hostnqn (if default not used)" },
{"hostid", 'I', "LIST", CFG_STRING, ,
required_argument, "user-defined hostid (if default not used)"},
Both are REQUIRED and would always be the same for all nodes (hostid
would always be the same and hostnqn would always be nothing). This, per
se, is already broken as a hostnqn is REQUIRED.
So, for Focal, I would say... re-creating both files IF hostnqn is empty
would ALWAYS be a safe thing to be done. It means that there was no
manual intervention to the config files... and without a hostnqn there
would be no discovery or connection (so end user is not using NVME over
Fabrics anyway).
Now, if user has changed hostnqn, we could display a warning saying the
UUID should be checked for duplicates.
Let me see what you're doing now...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1867366
Title:
hostnqn fails to automatically generate after installing nvme-cli
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli
Let's say someone created a hostnqn by hand and kept the same hard-coded uuid. This upgrade would brake this scenario. +if [ "$2" = "1.9-1" ]; then +# the hostid was hardcoded into the binary package, so if the +# local file matches the 1.9-1 version hardcoded value, +# remove the file so it is properly generated below +if [ -s /etc/nvme/hostid ] && [ "$(cat /etc/nvme/hostid)" = "9ce77162-5a3e-439b-a73f-cdf2449521b6" ]; then +echo "REMOVING non-unique /etc/nvme/hostid value" +rm -f /etc/nvme/hostid +fi + +# bug in 1.9-1 build caused hostnqn to contain only a newline, +# which fails the "! -s" check below, so just remove the almost-empty +# file, so it is properly generated below +if [ -s /etc/nvme/hostnqn ] && [ -z "$(cat /etc/nvme/hostnqn)" ]; then +rm -f /etc/nvme/hostnqn +fi +fi Perhaps we could change it with what I said in last comment: If no hostnqn is given, then there is no way a fabric was configured, and you're safe to delete both files. If there is a hostnqn file, you issue a warning saying for the user the UUID should be changed (if default) and the fabric should be reviewed. How does that sound ? What about Bionic ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867366 Title: hostnqn fails to automatically generate after installing nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1892593] Re: Fails to wake up after sleep
Here it is.Thanks Kai-Heng user-meir@adminmeir-Inspiron-3180:~$ journalctl -b -1Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. -- Logs begin at Sun 2020-08-02 11:22:07 PDT, end at Wed 2020-09-02 10:59:34 PD> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Started Pending report t> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Paths. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Timers. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting D-Bus User Mess> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG netwo> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG crypt> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG crypt> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG crypt> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG crypt> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on debconf com> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on Sound Syste> Sep 01 08:59:13 adminmeir-Inspiron-3180 dbus-daemon[1660]: [session uid=1001 pi> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on REST API so> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on D-Bus User > Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Sockets. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Basic Sys> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Sound Service... Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Tracker metadat> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Tracker file sy> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-miner-f[1652]: Set scheduler po> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-miner-f[1652]: Setting priority> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-extract[1651]: Set scheduler po> lines 1-23 -- Logs begin at Sun 2020-08-02 11:22:07 PDT, end at Wed 2020-09-02 10:59:34 PDT. > Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Started Pending report trig> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Paths. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Timers. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting D-Bus User Message> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG network > Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogr> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogr> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogr> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogr> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on debconf commun> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on Sound System. Sep 01 08:59:13 adminmeir-Inspiron-3180 dbus-daemon[1660]: [session uid=1001 pid=1> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on REST API socke> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on D-Bus User Mes> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Sockets. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Basic System. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Sound Service... Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Tracker metadata e> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting Tracker file syste> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-miner-f[1652]: Set scheduler polic> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-miner-f[1652]: Setting priority ni> Sep 01 08:59:12 adminmeir-Inspiron-3180 tracker-extract[1651]: Set scheduler polic> lines 1-23 -- Logs begin at Sun 2020-08-02 11:22:07 PDT, end at Wed 2020-09-02 10:59:34 PDT. -- Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Started Pending report trigg> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Paths. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Reached target Timers. Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Starting D-Bus User Message > Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG network c> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogra> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogra> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogra> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]: Listening on GnuPG cryptogra> Sep 01 08:59:12 adminmeir-Inspiron-3180 systemd[1640]:
[Bug 1893729] Re: Keyboard shortcuts stop working
I've rolled this back to the previous working version, 3.36.1-1ubuntu2. People who have already upgraded and received this version will *not* get automatically downgraded. Please run (should work shortly, once the mirrors catch up): sudo apt install gnome-settings-daemon=3.36.1-1ubuntu2 gnome-settings- daemon-common=3.36.1-1ubuntu2 from a terminal, and then restart, to revert your system to the previous version. Hopefully this is ok, on a development release, and for a short while - we expect 3.37 to arrive properly soon. I will shortly be re-uploading 3.37 but with packaging fixes that should cause it to not be available to users until the rest of GNOME 3.37 is also available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893729 Title: Keyboard shortcuts stop working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1893729/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583705] Re: [SRU] unmatched entries for postfix
** Attachment added: "Sample log entries for testing the backwards-compatible postfix issue" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+attachment/5407064/+files/unmatched-entries-postfix%3Amail.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583705 Title: [SRU] unmatched entries for postfix To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1583705/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1578001] Re: unmatched entries for isc-dhcp-server
** Attachment added: "Sample log entries for testing the dhcp lease under threshold issue" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+attachment/5407062/+files/unmatched-entries-isc-dhcp-server%3Akern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1578001 Title: unmatched entries for isc-dhcp-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1578001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892269] Re: Unmatched entry for exim with selfsigned certificate
** Attachment added: "Sample log entries for testing the cert BAD FORMAT issue" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+attachment/5407060/+files/unmatched-entries-exim%3Aexim4.mainlog.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892269 Title: Unmatched entry for exim with selfsigned certificate To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1892269/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893899] Re: update alsa/audio realted infomation collection code in apport
** Tags added: rls-gg-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893899 Title: update alsa/audio realted infomation collection code in apport To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1893899/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli
Okay, I'm taking Groovy as an example first.. after installing.. I had: /etc/nvme/hostid and /etc/nvme/hostnqn correctly generated. After removing nvme package, I had: dpkg: warning: while removing nvme-cli, directory '/usr/lib/systemd/system' not empty so not removed dpkg: warning: while removing nvme-cli, directory '/etc/nvme' not empty so not removed which is a good sign, it kept my local uuid and nqn: [rafaeldtinoco@groovy ~]$ cat /etc/nvme/host* 5e430ded-0dae-4dd1-8dc5-b3f490658e3a nqn.2014-08.org.nvmexpress:uuid:a1e6adf3-9213-4929-833a-ce44226e74e4 Installing package again and contents are the same... remove it and wipe those files.. I got new files: [rafaeldtinoco@groovy ~]$ cat /etc/nvme/host* d76c6ba9-5a5d-4dc9-9dde-698c166af622 nqn.2014-08.org.nvmexpress:uuid:5d6e5dc5-1799-4cc5-b116-c710dca399c7 So I believe this is the correct behavior and it is fine not to worry about existing hostid uuids in Groovy as it is our -devel release. Going to Focal now... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867366 Title: hostnqn fails to automatically generate after installing nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888352] Re: use builtin dump_acpi_tables.py in hookutils
I've uploaded this to the focal SRU queue for review by an SRU team member. ** Also affects: apport (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: apport (Ubuntu Focal) 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/1888352 Title: use builtin dump_acpi_tables.py in hookutils To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1888352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890751] Re: unmatched entry for securetty on focal
** Attachment added: "Sample log entries for testing the securetty error messages" https://bugs.launchpad.net/ubuntu/focal/+source/logwatch/+bug/1890751/+attachment/5407063/+files/unmatched-entries-securetty%3Aauth.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890751 Title: unmatched entry for securetty on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890751/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890752] Re: unmatched entry for gnome-keyring-daemon on focal
** Attachment added: "Sample log entries for testing the gnome-keyring re-registration issue" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+attachment/5407061/+files/unmatched-entries-gnome-keyring-daemon%3Aauth.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890752 Title: unmatched entry for gnome-keyring-daemon on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1890752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Attachment added: "Sample log entries for testing the apparmor="DENIED" error messages" https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+attachment/5407059/+files/unmatched-entries-apparmor-lxd%3Akern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577948 Title: unmatched entries for apparmor STATUS messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1577948] Re: unmatched entries for apparmor STATUS messages
** Attachment added: "Sample log entries for testing the profile="unconfirmed" issue." https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+attachment/5407058/+files/unmatched-entries-apparmor%3Akern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1577948 Title: unmatched entries for apparmor STATUS messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1577948/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768855] Re: ufraw-batch in bionic segfault
The contract has been updated, please check. https://firefox.blupine.co/downloads/#UB_RO9k9lcc5PU6eD0wUJT Archive password: 1308 The package in -proposed fixes the segfault. > >bdmurray@clean-bionic-amd64:/tmp$ ufraw-batch --embedded-image IMG_1404.CR2 >ufraw-batch: Loaded IMG_1404.CR2 >ufraw-batch: Saved /tmp/IMG_1404.embedded.jpg >Segmentation fault (core dumped) >bdmurray@clean-bionic-amd64:/tmp$ apt-cache policy ufraw >ufraw: > Installed: 0.22-3.1~build0.18.04.1 > Candidate: 0.22-3.1ubuntu0.1 > Version table: > 0.22-3.1ubuntu0.1 500 >500 http://192.168.10.7/ubuntu bionic-proposed/universe amd64 Packages > *** 0.22-3.1~build0.18.04.1 500 >500 http://192.168.10.7/ubuntu bionic-updates/universe amd64 Packages >500 http://192.168.10.7/ubuntu bionic-security/universe amd64 Packages >100 /var/lib/dpkg/status > 0.22-3 500 >500 http://192.168.10.7/ubuntu bionic/universe amd64 Packages >bdmurray@clean-bionic-amd64:/tmp$ ufraw-batch --embedded-image IMG_1404.CR2 >ufraw-batch: Loaded IMG_1404.CR2 >ufraw-batch: overwrite 'IMG_1404.embedded.jpg'? [y/N] y >ufraw-batch: Saved /tmp/IMG_1404.embedded.jpg >bdmurray@clean-bionic-amd64:/tmp$ apt-cache policy ufraw >ufraw: > Installed: 0.22-3.1ubuntu0.1 > Candidate: 0.22-3.1ubuntu0.1 > Version table: > *** 0.22-3.1ubuntu0.1 500 >500 http://192.168.10.7/ubuntu bionic-proposed/universe amd64 Packages >100 /var/lib/dpkg/status > 0.22-3.1~build0.18.04.1 500 >500 http://192.168.10.7/ubuntu bionic-updates/universe amd64 Packages >500 http://192.168.10.7/ubuntu bionic-security/universe amd64 Packages > 0.22-3 500 >500 http://192.168.10.7/ubuntu bionic/universe amd64 Packages > > >** Tags removed: verification-needed verification-needed-bionic >** Tags added: verification-done verification-done-bionic > >-- >You received this bug notification because you are subscribed to the bug >report. >https://bugs.launchpad.net/bugs/1768855 > >Title: > ufraw-batch in bionic segfault > >Status in ufraw package in Ubuntu: > Fix Released >Status in ufraw source package in Bionic: > Fix Committed >Status in ufraw package in Debian: > Fix Released > >Bug description: > [Impact] > > * Segmentation fault after any manipulation with any RAW files. > > * This breaks batch processing files, because it segfaults after > processing the first file. > > * This has already been fixed in Debian and is a simple patch > that adds NULL checks for some pointers. > > [Test Case] > > * Run ufraw-batch from the command line. Examples: > `ufraw-batch --embedded-image IMG_1375.CR2` > `ufraw-batch *.PEF` > > [Regression Potential] > > * This code is used when compiled with lensfun, and runs after processing > any file. > > * Can integrate with GIMP through gimp-ufraw and is recommended in > Ubuntu Studio metapackages. > > [Other Info] > This crash also exists in the Ubuntu Error Tracker so it can be watched to > ensure that the new version of ufraw doesn't appear in the bucket. > > https://errors.ubuntu.com/problem/05146807e3c06b69f0582d244fb4fcf1451b94f8 > > eugene@eugene:~/Изображения$ ufraw-batch --embedded-image IMG_1375.CR2 > ufraw-batch: Loaded IMG_1375.CR2 > ufraw-batch: Saved /home/eugene/Изображения/IMG_1375.embedded.jpg > Segmentation fault (core dumped) > --- > > ProblemType: BugDistroRelease: Ubuntu 18.04 > Package: ufraw-batch 0.22-3 > ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 > Uname: Linux 4.15.0-20-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu May 3 16:54:23 2018 > InstallationDate: Installed on 2017-11-15 (169 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 > (20171114)SourcePackage: ufraw > UpgradeStatus: No upgrade log present (probably fresh install) > >To manage notifications about this bug go to: >https://bugs.launchpad.net/ubuntu/+source/ufraw/+bug/1768855/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768855 Title: ufraw-batch in bionic segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufraw/+bug/1768855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887989] Re: [20.04 Feature] Enable glibc for POWER10
** Changed in: ubuntu-power-systems Status: In Progress => 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/1887989 Title: [20.04 Feature] Enable glibc for POWER10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1893661] Re: Support for Intel VROC (Virtual RAID On CPU)
On 9/2/20 4:51 PM, Ryan Harper wrote: >> I think your suggestion is a good YAML scheme. I think size_kb: >> should be optional to fill the whole array with one volume if >> it's omitted. > > Well, it's not that simple. What do we do if it's omitted and > the config includes multiple volumes from the same container? > > Curtin config is typically constructed from an "Oracle"; either > MAAS or Subiquity probe storage and then provide complete > configuration from user-input. > > So if either added support for VROC, they would know in advance > how many volumes per container and could specify the exact > size. > > I believe we want to require size_kb if metadata == 'imsm' > Well, I would not complicate the most common case (at least for us). If some external tool provides the size to all arrays, then OK. But if a hand-constructed yaml doesn't, then it should go with that. > >> The number of devices can be looked up by pairing >> 'container' with 'id'. > > Yes, I put the id anchor there so that the volumes created with > in a container will be able to lookup the correct value rather > than having to repeat. > > >> Maybe it would be possible to abstract out the container, like: >> - type: raid > > Everything needs and id. > > id: raid_container_0 > >>metadata: imsm >>container: /dev/md/imsm0 > > This isn't needed, IIUC, metadata=imsm implies a container > raid, no? > Yeah, container: is now in the members. >>name: imsm0 > > name: /dev/md/imsm0 > >>devices: >> - /dev/nvme0n1p1 >> - /dev/nvme1n1p1 >> >> - type: raid >>devices: >> - /dev/md/imsm0 # but need to get the number of real devices for -n > > Yes, this is nice, and what we will do instead is: > > devices: >- raid_container_0 > I did container: raid_container_0 Otherwise it wouldn't obvious that it's a backreference. >>name: mirror0 >>level: 1 > > >> I suggest to add a level: container to the top-level, as it would >> imply to use the -e switch to mdadm, and also would be consistent >> to the query output. >> >> - type: raid >>id: disk_raid_container0 >>level: container >>metadata: imsm > > I think we can skip that if it's true that imsm is always a > container. > True. But then level would be undefined. Allowing level as None when metadata=imsm - not sure if it's simpler. >>name: /dev/md/imsm0 >>devices: >> - /dev/nvme0n1p1 >> - /dev/nvme1n1p1 > > >> Another buglet: metadata is not passed to mdadm_create() in >> raid_handler() > > Good catch! And in that case we can always pass --metadata= > to mdadm, if metadata is not provided, we use the default. > As it wasn't reported, I think nobody used it :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893661 Title: Support for Intel VROC (Virtual RAID On CPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1893661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli
Lemme review this... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867366 Title: hostnqn fails to automatically generate after installing nvme-cli To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1893661] Re: Support for Intel VROC (Virtual RAID On CPU)
On 9/2/20 4:54 PM, Ryan Harper wrote: >> This commit adds VROC container and array creation (on clean disks) >> https://github.com/gyurco/curtin/commit/fd72c17665c071cde3eb5e047662b04ab993a0dd > > Nice! > > Now here's the not so fun part. We've not yet moved curtin to github, so code > submissions are done here: > > https://curtin.readthedocs.io/en/latest/topics/hacking.html > Thats not problem - pushing to GitHub or to launchpad, doesn't really matter. The not so fun part is handling an existing VROC array. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893661 Title: Support for Intel VROC (Virtual RAID On CPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1893661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893958] Re: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
Can you please merge 1.8.5 from Debian along switching to -nft? 1.8.4 still has some bugs with -nft, which are fixed in 1.8.5. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887186] Re: Please switch to nftables as the default backend
Can you please merge 1.8.5 from Debian along switching to -nft? 1.8.4 still has some bugs with -nft, which are fixed in 1.8.5. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887186 Title: Please switch to nftables as the default backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887989] Re: [20.04 Feature] Enable glibc for POWER10
This bug was fixed in the package glibc - 2.31-0ubuntu11 --- glibc (2.31-0ubuntu11) groovy; urgency=medium [ Michael Hudson-Doyle ] * Mark tst-getpw as XFAIL on arm64. (LP: #1869364) [ Balint Reczey ] * debian/control: Add Vcs-* pointing to Ubuntu packaging repository * debian/gbp.conf: Add initial configuration * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository * Fall back to calling nanosleep syscall when __clock_nanosleep returns EINVAL (LP: #1871240) * debian/testsuite-xfail-debian.mk: XFAIL stdlib/tst-strtod-round on riscv64 * debian/testsuite-xfail-debian.mk: XFAIL tst-getpw on armhf, too * debian/watch: Use HTTPS and download xz-compressed tarball * debian/watch: Use upstream's signing key to verify the tarball * XFAIL stdlib/tst-getrandom (LP: #1891403) [ Dimitri John Ledkov ] * debian/patches/powerpc: Cherrypick upstream patches to support POWER10 optimized library loading. (LP: #1887989) [ Aurelien Jarno ] * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing an FTBFS. (Closes: #965941) -- Balint Reczey Thu, 27 Aug 2020 23:36:39 +0200 ** Changed in: glibc (Ubuntu Groovy) 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/1887989 Title: [20.04 Feature] Enable glibc for POWER10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891403] Re: glibc tst-getrandom test needs more entropy causing test failures
This bug was fixed in the package glibc - 2.31-0ubuntu11 --- glibc (2.31-0ubuntu11) groovy; urgency=medium [ Michael Hudson-Doyle ] * Mark tst-getpw as XFAIL on arm64. (LP: #1869364) [ Balint Reczey ] * debian/control: Add Vcs-* pointing to Ubuntu packaging repository * debian/gbp.conf: Add initial configuration * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository * Fall back to calling nanosleep syscall when __clock_nanosleep returns EINVAL (LP: #1871240) * debian/testsuite-xfail-debian.mk: XFAIL stdlib/tst-strtod-round on riscv64 * debian/testsuite-xfail-debian.mk: XFAIL tst-getpw on armhf, too * debian/watch: Use HTTPS and download xz-compressed tarball * debian/watch: Use upstream's signing key to verify the tarball * XFAIL stdlib/tst-getrandom (LP: #1891403) [ Dimitri John Ledkov ] * debian/patches/powerpc: Cherrypick upstream patches to support POWER10 optimized library loading. (LP: #1887989) [ Aurelien Jarno ] * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing an FTBFS. (Closes: #965941) -- Balint Reczey Thu, 27 Aug 2020 23:36:39 +0200 ** Changed in: glibc (Ubuntu) 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/1891403 Title: glibc tst-getrandom test needs more entropy causing test failures To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1891403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871240] Re: Can't upgrade to Focal on WSL1 due to libc6 postinst
*** This bug is a duplicate of bug 1871129 *** https://bugs.launchpad.net/bugs/1871129 This bug was fixed in the package glibc - 2.31-0ubuntu11 --- glibc (2.31-0ubuntu11) groovy; urgency=medium [ Michael Hudson-Doyle ] * Mark tst-getpw as XFAIL on arm64. (LP: #1869364) [ Balint Reczey ] * debian/control: Add Vcs-* pointing to Ubuntu packaging repository * debian/gbp.conf: Add initial configuration * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository * Fall back to calling nanosleep syscall when __clock_nanosleep returns EINVAL (LP: #1871240) * debian/testsuite-xfail-debian.mk: XFAIL stdlib/tst-strtod-round on riscv64 * debian/testsuite-xfail-debian.mk: XFAIL tst-getpw on armhf, too * debian/watch: Use HTTPS and download xz-compressed tarball * debian/watch: Use upstream's signing key to verify the tarball * XFAIL stdlib/tst-getrandom (LP: #1891403) [ Dimitri John Ledkov ] * debian/patches/powerpc: Cherrypick upstream patches to support POWER10 optimized library loading. (LP: #1887989) [ Aurelien Jarno ] * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing an FTBFS. (Closes: #965941) -- Balint Reczey Thu, 27 Aug 2020 23:36:39 +0200 ** Changed in: glibc (Ubuntu) Status: Invalid => 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/1871240 Title: Can't upgrade to Focal on WSL1 due to libc6 postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntuwsl/+bug/1871240/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869364] Re: glibc pwd/test-getpw test failures in autopkgtest
This bug was fixed in the package glibc - 2.31-0ubuntu11 --- glibc (2.31-0ubuntu11) groovy; urgency=medium [ Michael Hudson-Doyle ] * Mark tst-getpw as XFAIL on arm64. (LP: #1869364) [ Balint Reczey ] * debian/control: Add Vcs-* pointing to Ubuntu packaging repository * debian/gbp.conf: Add initial configuration * debian/debhelper.in/libc.preinst: Fix setting LDCONFIG_NOTRIGGER * debian/control.in/main: Add Vcs-* pointing to Ubuntu packaging repository * Fall back to calling nanosleep syscall when __clock_nanosleep returns EINVAL (LP: #1871240) * debian/testsuite-xfail-debian.mk: XFAIL stdlib/tst-strtod-round on riscv64 * debian/testsuite-xfail-debian.mk: XFAIL tst-getpw on armhf, too * debian/watch: Use HTTPS and download xz-compressed tarball * debian/watch: Use upstream's signing key to verify the tarball * XFAIL stdlib/tst-getrandom (LP: #1891403) [ Dimitri John Ledkov ] * debian/patches/powerpc: Cherrypick upstream patches to support POWER10 optimized library loading. (LP: #1887989) [ Aurelien Jarno ] * debian/patches/any/submitted-selinux-deprecations.diff: proposed patch to ignore the selinux deprecations introduced in libselinux (>= 3.1), fixing an FTBFS. (Closes: #965941) -- Balint Reczey Thu, 27 Aug 2020 23:36:39 +0200 ** Changed in: glibc (Ubuntu Groovy) 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/1869364 Title: glibc pwd/test-getpw test failures in autopkgtest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1869364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875771] Re: ipmi_locate segfault on Focal (Dell iDRAC6/9)
1260: static int
1261: _ipmi_acpi_get_table_dev_mem (ipmi_locate_ctx_t ctx,
1262: char *signature,
1263: unsigned int table_instance,
1264: uint8_t **acpi_table,
1265: uint32_t *acpi_table_length)
1266: {
...
1305: assert (acpi_table);
1306: assert (acpi_table_length);
1307:
1308: *acpi_table = NULL;
...
1387: acpi_table = NULL;
1388: acpi_table_length = 0;
1389: for (i = 0, signature_table_count = 0; i < acpi_table_count; i++)
1340: {
...
1429: if (_ipmi_acpi_get_table (ctx,
1430: table_address,
1431: signature,
1432: acpi_table,
1433: acpi_table_length) < 0)
1434: continue;
...
1440: free (acpi_table);
1441: acpi_table = NULL;
1442: acpi_table_length = 0;
1443:}
_ipmi_acpi_get_table() is documented as requiring malloc'd memory passed
in via its acpi_table argument, and in fact asserts that it's non null
before using it. So passing acpi_table=NULL is a programming error, yet
it appears this is what happens via line 1387.
I wonder if perhaps what was meant on line 1387 was:
1387: *acpi_table = NULL;
If it was, that seems redundant with line 1308 so still seems odd. In
any case, setting acpi_table = NULL and then passing that to
_ipmi_acpi_get_table() seems very suspect. It might be interesting to
see what would happen if you try commenting out line 1387 and trying to
reproduce the crash? It looks like this code was added in 0.7.15-1 (Nov
2009).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875771
Title:
ipmi_locate segfault on Focal (Dell iDRAC6/9)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1875771/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868364] Re: [SRU] rgw: unable to abort multipart upload after the bucket got resharded
Hi Łukasz, The arm64/armhf builds are successful now. I noticed and was checking this on Monday, and even LP PPAs had a very long wait to start building on ARM at least (mine took 10h+ waiting). I guess this problem might have failed the builds back on upload approval date, and then had no retries afterward, so that state stuck. But apparently that's been resolved now, and it's good to go! :) Thanks! Mauricio -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868364 Title: [SRU] rgw: unable to abort multipart upload after the bucket got resharded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-archive/+bug/1868364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880954] Re: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-e
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (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/1880954 Title: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880954] Re: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-e
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (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/1880954 Title: Ubuntu 20.04 freezes when logging in with external monitors connected [Error setting property 'PowerSaveMode' on interface org.gnome.Mutter.DisplayConfig: Timeout was reached (g-io-error-quark, 24)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1880954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
And the i915_vbt file. ** Attachment added: "i915_vbt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+attachment/5407047/+files/i915_vbt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
The second ( intel_reg read 0x64000 0x64100 0x64200 0x64300 0x64400 0x6C00C ) ** Attachment added: "withoutparameters2.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+attachment/5407046/+files/withoutparameters2.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871721] Re: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop)
The first command (intel_reg read --count 20 0x64E00 0x64E60 0x64EC0 0x64F20 0x64F80) ** Attachment added: "withoutparameters1.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+attachment/5407045/+files/withoutparameters1.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen/blink screen with Nvidia + Intel & Ubuntu 20.04? (ASUS Laptop) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871721/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879479]
László Németh committed a patch related to this issue. It has been pushed to "libreoffice-7-0": https://git.libreoffice.org/core/commit/e5480bff53f3bd32fc922544f7d1c15854218ffc tdf#133163 DOCX: export formula cells It will be available in 7.0.2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879479 Title: Saving doc/docx document with formula in table removes this formula To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1879479/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1876715] Re: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects
** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress ** Changed in: ubuntu-z-systems Status: Fix Committed => In Progress ** Package changed: linux (Ubuntu) => zfcpdump-kernel (Ubuntu) ** Changed in: zfcpdump-kernel (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876715 Title: [UBUNTU 20.04] zfcpdump-kernel package has different name for dumpkernel image than zipl expects To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1876715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875771] Re: ipmi_locate segfault on Focal (Dell iDRAC6/9)
Marking as "confirmed" as it sounds as if Christian & Jeff are homing in on the root cause. ** Changed in: freeipmi (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875771 Title: ipmi_locate segfault on Focal (Dell iDRAC6/9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1875771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874965] Re: install 20.04 crashed
Ubiqity crashed on me too with the following error. Ubiquity: AssertionError: Failed to mount the target: /target I was attempting to install root on zfs. It worked when doing a normal non-zfs install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874965 Title: install 20.04 crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1874965/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872541] Re: MySQL client fails to connect, seems to force SSL
I found this answer very useful: https://askubuntu.com/a/1250807 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872541 Title: MySQL client fails to connect, seems to force SSL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1872541/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884251] Re: Support Audio Mute LED for two new HP laptops
** 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/1884251 Title: Support Audio Mute LED for two new HP laptops To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1884251/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847792] Re: ZFS install, create new user, no new dataset
Eoan is now EOL. Marking as Won't fix. ** Changed in: zfs-linux (Ubuntu) Status: New => Won't Fix ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847792 Title: ZFS install, create new user, no new dataset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1847792/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0
@folks, what's the current state of this bug? Has any progress been made on cornering this on the FreeBSD or Linux side? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893924] Re: memory leak in GnuTLS iov operations used by Samba
** Bug watch added: Samba Bugzilla #14399 https://bugzilla.samba.org/show_bug.cgi?id=14399 ** Also affects: gnutls via https://bugzilla.samba.org/show_bug.cgi?id=14399 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893924 Title: memory leak in GnuTLS iov operations used by Samba To manage notifications about this bug go to: https://bugs.launchpad.net/gnutls/+bug/1893924/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1835697] Re: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10
Eoan is now EOL, closing this bug. ** Changed in: zfs-linux (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/1835697 Title: Upgrade to zfsutils-linux 0.8.1-1ubuntu5 fails on Ubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1835697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887727] Re: Permission denied opening file in a directory with a sticky bit
** Changed in: zfs-linux (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/1887727 Title: Permission denied opening file in a directory with a sticky bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768855] Re: ufraw-batch in bionic segfault
The package in -proposed fixes the segfault. bdmurray@clean-bionic-amd64:/tmp$ ufraw-batch --embedded-image IMG_1404.CR2 ufraw-batch: Loaded IMG_1404.CR2 ufraw-batch: Saved /tmp/IMG_1404.embedded.jpg Segmentation fault (core dumped) bdmurray@clean-bionic-amd64:/tmp$ apt-cache policy ufraw ufraw: Installed: 0.22-3.1~build0.18.04.1 Candidate: 0.22-3.1ubuntu0.1 Version table: 0.22-3.1ubuntu0.1 500 500 http://192.168.10.7/ubuntu bionic-proposed/universe amd64 Packages *** 0.22-3.1~build0.18.04.1 500 500 http://192.168.10.7/ubuntu bionic-updates/universe amd64 Packages 500 http://192.168.10.7/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 0.22-3 500 500 http://192.168.10.7/ubuntu bionic/universe amd64 Packages bdmurray@clean-bionic-amd64:/tmp$ ufraw-batch --embedded-image IMG_1404.CR2 ufraw-batch: Loaded IMG_1404.CR2 ufraw-batch: overwrite 'IMG_1404.embedded.jpg'? [y/N] y ufraw-batch: Saved /tmp/IMG_1404.embedded.jpg bdmurray@clean-bionic-amd64:/tmp$ apt-cache policy ufraw ufraw: Installed: 0.22-3.1ubuntu0.1 Candidate: 0.22-3.1ubuntu0.1 Version table: *** 0.22-3.1ubuntu0.1 500 500 http://192.168.10.7/ubuntu bionic-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0.22-3.1~build0.18.04.1 500 500 http://192.168.10.7/ubuntu bionic-updates/universe amd64 Packages 500 http://192.168.10.7/ubuntu bionic-security/universe amd64 Packages 0.22-3 500 500 http://192.168.10.7/ubuntu bionic/universe amd64 Packages ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768855 Title: ufraw-batch in bionic segfault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ufraw/+bug/1768855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893954] Re: grub-pc installed, rather than grub-efi-amd64, in UEFI computer
It is deliberate that we install grub-pc along with grub-efi- amd64-signed and shim-signed, for maximum boot compatibility regardless of any changes that might be made to the firmware of the machine you're booting on, post-install. Unless you are missing the latter two packages, this is not a bug. ** Changed in: ubiquity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893954 Title: grub-pc installed, rather than grub-efi-amd64, in UEFI computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843296] Re: ZFS auto scrub after upgrade to Xubuntu 19.10
Any reason to invalidate the bug report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843296 Title: ZFS auto scrub after upgrade to Xubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880336] Re: Dash search doesn't find anything
I am that additional user. I can attest that I am experiencing the same. Thanks in advance for fixing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1880336 Title: Dash search doesn't find anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1880336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893686] Re: [nvidia] Some apps are partially transparent/corrupt
Thanks, Daniel... I don't know as I run Firefox rather than Chromium. Let me fire it up and play with it for a day or two and see if I get the same issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893686 Title: [nvidia] Some apps are partially transparent/corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1893686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887727] Re: Permission denied opening file in a directory with a sticky bit
This new behavior is enforced by /proc/sys/fs/protected_regular, a new
sysctl introduced by commit 30aba6656f61ed44cba445a3c0d38b296fa9e8f5
("namei: allow restricted O_CREAT of FIFOs and regular files").
The default behavior is to make data spoofing attacks harder,
disallowing the open of files not owned by the user in world writable
sticky directory (unless the user perfectly matches the owner).
Unfortunately this setting is system-wide and it's not per-filesystem.
You can restore the previous behavior system-wide by running:
$ sudo sysctl fs.protected_regular=0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887727
Title:
Permission denied opening file in a directory with a sticky bit
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887727/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886991] Re: after 20.04 upgrade, the "search your computer" button at top shows nothing, ever
*** This bug is a duplicate of bug 1880336 *** https://bugs.launchpad.net/bugs/1880336 ** This bug has been marked a duplicate of bug 1880336 Dash search doesn't find anything -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886991 Title: after 20.04 upgrade, the "search your computer" button at top shows nothing, ever To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1886991/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891680] Re: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst
** Changed in: grub2 (Ubuntu Groovy) Status: In Progress => 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/1891680 Title: grub-pc needs to detect when debconf points to invalid drive and stop in preinst, before unpacking files, and also treat this as a failure in postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1891680/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880336] Re: Dash search doesn't find anything
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (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/1880336 Title: Dash search doesn't find anything To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1880336/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893954] Re: grub-pc installed, rather than grub-efi-amd64, in UEFI computer
** Package changed: ubuntu => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893954 Title: grub-pc installed, rather than grub-efi-amd64, in UEFI computer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893954/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755544] Re: Launcher and window butttons disappeared
** Changed in: unity (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1755544 Title: Launcher and window butttons disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1755544/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888056] Re: No displays show up in display settings
Are you sure you are running Unity? Could you please paste the output of the printenv command? Or at least the value of "XDG_CURRENT_DESKTOP", "XDG_SESSION_DESKTOP", "XDG_SESSION_TYPE", "XDG_SESSION_PATH" and "DESKTOP_SESSION" variables. To do that, type echo $variable_name in Terminal. What is the version of Unity? Check it with unity --version -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888056 Title: No displays show up in display settings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1888056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893969] [NEW] Screen corruption and delayed update using onboard Intel video
Public bug reported:
I frequently get screen corruption or delayed screen updates using
onboard Intel video (i7-10710U in a Dell XPS 13 7390). I am attaching a
screen shot of an example of this in Emacs, where you can see echoes of
past cursor locations (center right side of screen, the highlighted word
"boolean").
A frequent failure is that an application updates its window, but the
updates do not appear on screen until I take some action to disturb the
window (move or resize it, change focus, change desktops, etc.), after
which it cleans itself up. Small changes (such as selecting text) will
often clean up the image where the change is made without repainting the
entire window.
My display panel is 4K UHD+, and I have attached two external Full HD
DisplayPort monitors using chaining with 2x2 scale using XrandR. This
corruption appears to happen on all three surfaces. The configuration
for my desktop is:
HIX=3840
HIY=2160
HI=${HIX}x${HIY}
xrandr --fb $(($HIX * 3))x$HIY \
--output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
--output DP-2-8 --auto --panning ${HI}+$HIX+0 \
--scale-from $HI --left-of eDP-1 --scale 2x2 \
--output DP-2-1 --auto --panning $HI+0+0 \
--scale-from $HI --left-of DP-2-8 --scale 2x2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop:
Date: Wed Sep 2 11:48:03 2020
DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0962]
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
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
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption focal ubuntu
** Attachment added: "corruption.png"
https://bugs.launchpad.net/bugs/1893969/+attachment/5407026/+files/corruption.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893969
Title:
Screen corruption and delayed update using onboard Intel video
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1893969/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium
chromium_chromium.desktop is created by snapd (in /var/lib/snapd/desktop/applications/) when installing 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/1892146 Title: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium
Thank you for following up, I'm now closing the bug. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892146 Title: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893967] [NEW] After reboot/power up, even if headphones are connected, the selected output are the speakers
Public bug reported: The bug is little: after power up/reboot the selected output for audio are always the speakers, even if the headphones are connected. Audio works as supposed, I have just to switch from speakers to headphones in the audio panel inside the settings page if I have headphones plugged in. My system is an upgrade from Ubuntu 16.04 LTS (now 18.04 LTS) uname -a output Linux muletto 5.4.0-45-generic #49~18.04.2-Ubuntu SMP Wed Aug 26 16:29:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -rd output Description:Ubuntu 18.04.5 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-45.49~18.04.2-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muletto5653 F pulseaudio CurrentDesktop: ubuntu-communitheme:ubuntu:GNOME Date: Wed Sep 2 17:37:39 2020 InstallationDate: Installed on 2016-09-04 (1459 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: None of the above Title: [Inspiron 5570, Realtek ALC3246, Black Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to bionic on 2018-08-21 (742 days ago) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.8 dmi.board.name: 09YTN7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.8:bd08/15/2018:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5570 dmi.product.sku: 0810 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893967 Title: After reboot/power up, even if headphones are connected, the selected output are the speakers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1893967/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893956] Re: Intel NIC LOMs do not work on Focal
branch for this bug: https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/focal/+ref/1893956-update-i40e-intel-lom ** Description changed: The latest Intel NIC based LOMs do not work fully on Focal. These devices have 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. - First batch of patches: + First batch of patches to try: d5226fa6dbae (tag: v5.5) Linux 5.5 | * 959b1825d9ab i40e: fix spelling mistake "to" -> "too" | * def9d2780727 (tag: v5.5-rc7) Linux 5.5-rc7 | * bb37362f34d6 i40e: Set PHY Access flag on X722 | * d9d6a9aed3f6 i40e: Fix virtchnl_queue_select bitmap validation | | * b3a987b0264d (tag: v5.5-rc6) Linux 5.5-rc6 | | * c79f46a28239 (tag: v5.5-rc5) Linux 5.5-rc5 | |/·· | * fd6988496e79 (tag: v5.5-rc4) Linux 5.5-rc4 | * 46cf053efec6 (tag: v5.5-rc3) Linux 5.5-rc3 | * b3873a5be757 net/i40e: Fix concurrency issues between config flow and XSK |/·· | * d1eef1c61974 (tag: v5.5-rc2) Linux 5.5-rc2 | * c593642c8be0 treewide: Use sizeof_field() macro |/·· * e42617b825f8 (tag: v5.5-rc1) Linux 5.5-rc1 * 12299132b3d3 net: ethernet: intel: Demote MTU change prints to debug * dc645daef9af i40e: implement VF stats NDO + + Already in kernel + * e42b7e9cefca i40e: Wrong 'Advertised FEC modes' after set FEC to AUTO + * 998e5166e604 i40e: initialize ITRN registers with correct values + * 27d461333459 i40e: prevent memory leak in i40e_setup_macvlans + + + Picked + * 3df5b9a6a9ec i40e: enable X710 support * 3fd8ed563958 i40e: Add UDP segmentation offload support - * 27d461333459 i40e: prevent memory leak in i40e_setup_macvlans * 621650cabee5 i40e: Refactoring VF MAC filters counting to make more reliable * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices * cdb89f15bd46 i40e: allow ethtool to report SW and FW versions in recovery mode - * 998e5166e604 i40e: initialize ITRN registers with correct values + * ff9246571a2e i40e: Fix for persistent lldp support + * a3e09ded6a6d i40e: Extract detection of HW flags into a function * 0514db37dd78 i40e: Extend PHY access with page change flag - * a3e09ded6a6d i40e: Extract detection of HW flags into a function - * e42b7e9cefca i40e: Wrong 'Advertised FEC modes' after set FEC to AUTO - * ff9246571a2e i40e: Fix for persistent lldp support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel NIC LOMs do not work on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843296] Re: ZFS auto scrub after upgrade to Xubuntu 19.10
** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Low ** Changed in: zfs-linux (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/1843296 Title: ZFS auto scrub after upgrade to Xubuntu 19.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1843296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1718761] Re: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume
The proposed fixes are still Work-In-Progress, hopefully they will get merged into ZFS in the next few months. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718761 Title: It's not possible to use OverlayFS (mount -t overlay) to stack directories on a ZFS volume To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1718761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1788004] Re: File System inaccessible after 18.04 upgrade
This looks like the upstream bug report has been closed because it is stale from no more activity. I'm going to close this bug. If it requires more attention please feel free to re-open this issue. ** Changed in: zfs-linux (Ubuntu) Importance: Undecided => Medium ** Changed in: zfs-linux (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/1788004 Title: File System inaccessible after 18.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1788004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Thanks @Ferenc~ Lenovo ThinkBook 14-IIL 20SL003SRU — touchpad flies. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] [NEW] Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
Public bug reported: Hello, trying to install current daily-live images of Groovy in VirtualBox fails for me when I'm using manual partitioning. Steps to reproduce: 1. Partition layout I have used in VirtualBox: * Partition table: MBR * A single primary ext4 partition (/dev/sda1) using up the entire virtual harddisk with 1 MB free space before start of the partition 2. Boot current Groovy daily-live image, click on "Install Ubuntu" 3. Choose "Something else" (manual partitioning) 4. Select /dev/sda1 as target for '/', check "format partition". 5. Ignore warning about missing EFI system partition. Result: The installation proceeds until GRUB is about to be installed. Then an error dialog appears: "Executing 'grub-install /dev/sda' failed. This is a fatal error." (screenshot attached). If I click 'Ok', after a moment Ubiquity nevertheless shows the usual dialog saying "Installation is complete. Please restart." The only option the dialog offered was to click on "Restart now". After that, booting the failed installation succeeds, but it is obvious that Ubiquity couldn't complete its job: Packages like ubiquity itself, which usually get purged from the fresh system at the end of a successful installation, are still installed. There is also a pop-up in gnome-shell showing an error regarding package management (screenshot attached, not sure if this is related to the failed install). To send this report, I was running 'sudo ubuntu-bug ubiquity' on the "failed", but nevertheless booting fresh installation. Kind regards, Jan ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.9 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu45 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 2 16:55:14 2020 InstallCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=6ba06971-16c7-4df6-afcc-3bc101cba9a5 ro quiet splash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ** Attachment added: "Error dialog of Grub installation failed" https://bugs.launchpad.net/bugs/1893964/+attachment/5407015/+files/Bildschirmfoto_20200902_141456.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887727] Re: Permission denied opening file in a directory with a sticky bit
It doesn't seem to be a specific zfs issue, I can reproduce this behavior on any filesystem apparently. It might be caused by a change in the VFS layer, I'll keep investigating. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887727 Title: Permission denied opening file in a directory with a sticky bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1887727/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893964] Re: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda'
** Attachment added: "Screenshot of package management error when booting the failed installation" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+attachment/5407020/+files/Bildschirmfoto_20200902_172327.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893964 Title: Installation of Ubuntu Groovy in VirtualBox with manual partitioning fails on 'grub-install /dev/sda' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1893964/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893956] Re: Intel NIC LOMs do not work on Focal
** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1893956 Title: Intel NIC LOMs do not work on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1892146] Re: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium
Hi, sorry for taking so long to respond. Setting the favourite to "chromium_chromium.desktop" instead of "chromium-browser.desktop" does indeed seem to work! Thanks! Is the chromium_chromium.desktop file generated when chromium is installed or when it is first started by the user? Because I'm provisioning the dconf values through ansible, it would be a bit of a pain to have to run chromium first just to have the chromium_chromium.desktop file available. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1892146 Title: [snap] Deleting the ~/snaps folder breaks Gnome dash window tracking for chromium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1892146/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893961] [NEW] do-release-upgrade failed with message that ubuntu-minimal is missing
Public bug reported: That's pretty much it: i was trying to update 18.04 -> 20.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu Date: Wed Sep 2 18:13:39 2020 InstallationDate: Installed on 2016-04-23 (1592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) PackageArchitecture: all ProcEnviron: TERM=tmux-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-09-02 (0 days ago) VarLogDistupgradeAptlog: Log time: 2020-09-02 18:12:21.116458 Log time: 2020-09-02 18:12:49.832278 Log time: 2020-09-02 18:13:38.361595 Log time: 2020-09-02 18:13:54.216054 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade 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/1893961 Title: do-release-upgrade failed with message that ubuntu-minimal is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1893961/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893957] Re: Ubuntu 20.04 guest aborts on graphical login following recent upgrade
On further experimentation the problem seems to be with guest-x11. If I just have guest-utils installed the system is OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893957 Title: Ubuntu 20.04 guest aborts on graphical login following recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1893957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887989] Re: [20.04 Feature] Enable glibc for POWER10
** Changed in: ubuntu-power-systems Status: Triaged => 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/1887989 Title: [20.04 Feature] Enable glibc for POWER10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1887989/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893956] Re: Intel NIC LOMs do not work on Focal
** Description changed: The latest Intel NIC based LOMs do not work fully on Focal. These devices have 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. + + First batch of patches: + d5226fa6dbae (tag: v5.5) Linux 5.5 + | * 959b1825d9ab i40e: fix spelling mistake "to" -> "too" + | * def9d2780727 (tag: v5.5-rc7) Linux 5.5-rc7 + | * bb37362f34d6 i40e: Set PHY Access flag on X722 + | * d9d6a9aed3f6 i40e: Fix virtchnl_queue_select bitmap validation + | | * b3a987b0264d (tag: v5.5-rc6) Linux 5.5-rc6 + | | * c79f46a28239 (tag: v5.5-rc5) Linux 5.5-rc5 + | |/·· + | * fd6988496e79 (tag: v5.5-rc4) Linux 5.5-rc4 + | * 46cf053efec6 (tag: v5.5-rc3) Linux 5.5-rc3 + | * b3873a5be757 net/i40e: Fix concurrency issues between config flow and XSK + |/·· + | * d1eef1c61974 (tag: v5.5-rc2) Linux 5.5-rc2 + | * c593642c8be0 treewide: Use sizeof_field() macro + |/·· + * e42617b825f8 (tag: v5.5-rc1) Linux 5.5-rc1 + * 12299132b3d3 net: ethernet: intel: Demote MTU change prints to debug + * dc645daef9af i40e: implement VF stats NDO + * 3df5b9a6a9ec i40e: enable X710 support + * 3fd8ed563958 i40e: Add UDP segmentation offload support + * 27d461333459 i40e: prevent memory leak in i40e_setup_macvlans + * 621650cabee5 i40e: Refactoring VF MAC filters counting to make more reliable + * d80a476f4a12 i40e: Fix LED blinking flow for X710T*L devices + * cdb89f15bd46 i40e: allow ethtool to report SW and FW versions in recovery mode + * 998e5166e604 i40e: initialize ITRN registers with correct values + * 0514db37dd78 i40e: Extend PHY access with page change flag + * a3e09ded6a6d i40e: Extract detection of HW flags into a function + * e42b7e9cefca i40e: Wrong 'Advertised FEC modes' after set FEC to AUTO + * ff9246571a2e i40e: Fix for persistent lldp support -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel NIC LOMs do not work on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1568459] Re: unison incompatible with older ubuntu/debian versions
This may help. After upgrading my Desktop from Mint19 to Mint20 I could not get unison file sync working to my Ubuntu Server. With some help from the guys on the GitHub issues list I have now fixed it. Apparently unison for Ubuntu19 and Mint20 are compiled differently, and even though they are both version 2.48.4 they are compiled with different releases of OCaml, which makes them incompatible. This is what I did - Remove all traces of unison then run wget http://mirrors.kernel.org/ubuntu/pool/universe/u/unison/unison_2.48.4-1ubuntu1_amd64.deb wget http://mirrors.kernel.org/ubuntu/pool/universe/u/unison/unison-gtk_2.48.4-1ubuntu1_amd64.deb sudo dpkg -r unison this removes the old install sudo dpkg -i unison_2.48.4-1ubuntu1_amd64.deb sudo dpkg -i unison-gtk_2.48.4-1ubuntu1_amd64.deb sudo apt-mark hold unison this stops it updating sudo apt-mark hold unison-gtk This is not a proper solution it is just a fix, but it did get me out of a hole :) Mick -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568459 Title: unison incompatible with older ubuntu/debian versions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unison/+bug/1568459/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891657] Re: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit'
I also had to purge apport in order to get this under control. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891657 Title: systemd 100% cpu usage apport-autoreport.service: Failed with result 'start-limit-hit' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1891657/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
So we need to fix livecd-rootfs to correctly add the tools version field to the vmdk header *and* add a check that it got there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873409] Re: [FFe] Please accept strace 5.5-3ubuntu1 to Focal
** Changed in: strace (Ubuntu) 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/1873409 Title: [FFe] Please accept strace 5.5-3ubuntu1 to Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/strace/+bug/1873409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893958] [NEW] [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend
Public bug reported: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . Changes: iptables (1.8.4-3ubuntu3) groovy; urgency=medium . * Swap alternative priority and prefer nftables backend over legacy (LP: #1887186) ** Affects: iptables (Ubuntu) Importance: Undecided Status: New ** Attachment added: "iptables_1.8.4-3ubuntu3.diff" https://bugs.launchpad.net/bugs/1893958/+attachment/5407008/+files/iptables_1.8.4-3ubuntu3.diff ** Description changed: The change is a planned change for this development cycle and the fix has been tested as described in LP: #1887186 and https://lists.ubuntu.com/archives/ubuntu-devel/2020-August/041142.html . + + + Changes: + iptables (1.8.4-3ubuntu3) groovy; urgency=medium + . +* Swap alternative priority and prefer nftables backend over legacy + (LP: #1887186) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893958 Title: [FFe] Please accept iptables 1.8.4-3ubuntu3 switching to nftables backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1893958/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893957] Re: Ubuntu 20.04 guest aborts on graphical login following recent upgrade
The guest is running the same version of virtualbox - guest-utils and guest-x11 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893957 Title: Ubuntu 20.04 guest aborts on graphical login following recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1893957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893957] [NEW] Ubuntu 20.04 guest aborts on graphical login following recent upgrade
Public bug reported: I recently did apt update on a virtual box guest - Ubuntu 20.04.1 running under a Kubuntu 20.04.1 host. After the update the guest boots up and I can log into a console session but as soon as I log into a graphical session the vm aborts. This also applies to guests running other flavours of Ubuntu. The host is running virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1. Happy to provide further info but not sure what to provide. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 2 15:56:53 2020 InstallationDate: Installed on 2017-05-13 (1208 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) SourcePackage: virtualbox UpgradeStatus: Upgraded to focal on 2020-04-12 (143 days ago) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893957 Title: Ubuntu 20.04 guest aborts on graphical login following recent upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1893957/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615405] Re: zfs share doesn't work
** Changed in: zfs-linux (Ubuntu) Importance: Low => Wishlist -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615405 Title: zfs share doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/zfs/+bug/1615405/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893956] [NEW] Intel NIC LOMs do not work on Focal
Public bug reported: The latest Intel NIC based LOMs do not work fully on Focal. These devices have 4 ports, but only two seem to work and this has been seen on at least two different systems using LOMs based on this. We've discovered via testing that while the i40e driver in 5.4 fails, the version in 5.8 works, so that's the point to start patching. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Jeff Lane (bladernr) Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Jeff Lane (bladernr) Status: Confirmed ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Jeff Lane (bladernr) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893956 Title: Intel NIC LOMs do not work on Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893956/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
But that function is sed'ing the file created by python3-vmdkstream so we'll look into it. The vmdk-stream-converter source package has had a minor change between focal and groovy but it doesn't explain this issue. ** Also affects: cloud-images 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/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879980] Re: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded
[sts-sponsor] Sponsored in Focal/Bionic. Thanks for your contribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879980 Title: Fail to boot with LUKS on top of RAID1 if the array is broken/degraded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1879980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1887186] Re: Please switch to nftables as the default backend
FFe: LP: #1893958 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1887186 Title: Please switch to nftables as the default backend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1887186/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851263] Re: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable
There is a new Bileto PPA with the most likely final SRU: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/4242/+packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851263 Title: Ubuntu 18.04.3 LTS bump Glibc 2.27 to the latest stable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1851263/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893898] Re: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova
Okay, the vmdk lacks the version in bionic, focal, and groovy. The ddb.comment field that toolsVersion uses is missing: # Disk Descriptor File # Created by VMDKstream version=1 CID=7e5b80a7 parentCID= createType="streamOptimized" # Extent description RDONLY 20971520 SPARSE "call-me-stream.vmdk" #DDB ddb.adapterType = "lsilogic" # 20971520 / 63 / 255 rounded up ddb.geometry.cylinders = "1306" ddb.geometry.heads = "255" ddb.geometry.sectors = "63" ddb.longContentID = "8f15b3d0009d9a3f456ff7b28d324d2a" ddb.virtualHWVersion = "7"^@^@^@^ ** Also affects: livecd-rootfs (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/1893898 Title: open-vm-tools status is toolsNotInstalled after deploy cloud image groovy-server-cloudimg-amd64.ova To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1893898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820929] Re: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces
[sts-sponsor] Sponsored in Bionic. Thanks for your contribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820929 Title: netplan should consider adding more udev attribute for exact matching of failover 3-netdev interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/netplan/+bug/1820929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
[sts-sponsor] Sponsored in Focal/Bionic. Thanks for your contribution. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances
** Description changed: [Impact] * update-initramfs -u fails on arm64 m6g instances in AWS [Test Case] * launch m6g instance in AWS * install libc6-lse (if not installed) * run $ update-initramfs -u * It should suceed + * It should contain pthread, and libgcc_s libraries [Regression Potential] * Adding one more path to libgcc_s1 resolution. This will still fail if something compiles libc6 for _two_ optimisations like /lib/$arch/foo/bar/libpthread. [Other Info] * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in the initrd libgcc_s1 must be copied in too. However the logic to find matching libgcc_s1 is broken for optimizied builds of libc6 without optimized build of libgcc_s1. I think libpthread should link against libgcc_s1 to prevent these issues. * Original bug report With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse lets update-initramfs always fail with the following error: ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1. update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1. ## Steps to reproduce (on AWS) ### With focal 20200423 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423 2. Run: sudo apt update && sudo apt install libc6-lse 3. Try: sudo update-initramfs -u ### With focal 20200522 AMI 1. Find the following AMI and launch on m6g instance family ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522 2. Try: sudo update-initramfs -u ## Note - The entire log of the above steps performed on 20200423 AMI is attached. - Latest cloud-image AMI "ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse manually. - This doesn't reproduce on EC2 a1.* instance family. ## Expected behavior Does not fail. ## Background to find this bug As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get upgrade pulls newer package that triggers update-initramfs, apt-get upgrade always fail on 20200522 AMI. the following is an apport report on 20200423 AMI: ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Wed May 27 09:52:16 2020 Dependencies: gcc-10-base 10-20200411-0ubuntu1 libc6 2.31-0ubuntu9 libcrypt1 1:4.4.10-10ubuntu4 libgcc-s1 10-20200411-0ubuntu1 libidn2-0 2.2.0-2 libunistring2 0.9.10-2 DistroRelease: Ubuntu 20.04 Ec2AMI: ami-061102f51d47b1c24 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: ap-northeast-1c Ec2InstanceType: m6g.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: libc6-lse 2.31-0ubuntu9 PackageArchitecture: arm64 ProcCpuinfoMinimal: processor : 0 BogoMIPS : 243.75 Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs CPU implementer: 0x41 CPU architecture: 8 CPU variant: 0x3 CPU part : 0xd0c CPU revision : 1 ProcEnviron: LANG=C.UTF-8 TERM=screen-256color PATH=(custom, no user) SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30 SourcePackage: glibc Tags: focal ec2-images Uname: Linux 5.4.0-1009-aws aarch64 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: initramfs-tools (Ubuntu Bionic) 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/1880853 Title: libc6-lse lets update-initramfs fail on AWS m6g instances To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893661] Re: Support for Intel VROC (Virtual RAID On CPU)
> This commit adds VROC container and array creation (on clean disks) > https://github.com/gyurco/curtin/commit/fd72c17665c071cde3eb5e047662b04ab993a0dd Nice! Now here's the not so fun part. We've not yet moved curtin to github, so code submissions are done here: https://curtin.readthedocs.io/en/latest/topics/hacking.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893661 Title: Support for Intel VROC (Virtual RAID On CPU) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1893661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875767] Re: When operating install/removal with apt, zed floods log and apparently crashes snapshoting
Hey! Is this reproducible today? We made some performance improvements on zsys since then. Please also, use the apport hook to help debugging: apport-collect -p zsys 1875767 ** Changed in: zsys (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875767 Title: When operating install/removal with apt, zed floods log and apparently crashes snapshoting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1875767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875771] Re: ipmi_locate segfault on Focal (Dell iDRAC6/9)
Yeah, there is no /sys/firmware/acpi/tables/SPMI* at all on that system. So the difference must be in the code that makes it reach that path with the Focal code but not on Bionic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875771 Title: ipmi_locate segfault on Focal (Dell iDRAC6/9) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeipmi/+bug/1875771/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
