[Bug 1927029] Re: ua attach command fails

There's no collect-logs for the installed cloud-init version: $ cloud-init collect-logs usage: cloud-init [-h] [--version] [--file FILES] [--debug] [--force] {init,modules,query,single,dhclient-hook} ... cloud-init: error: invalid choice: 'collect-logs

[Bug 1927029] Re: ua attach command fails

More info, instance is an empty directory, and there's instances too, with the subdirs below: $ ls -al /var/lib/cloud total 36 drwxr-xr-x 9 root root 4096 Feb 12 2017 . drwxr-xr-x 52 root root 4096 May 3 23:46 .. drwxr-xr-x 2 root root 4096 May 14 2019 data drwxr-xr-x 2 root root 4096 Oct 14

[Bug 1927029] Re: ua attach command fails

$ cat /var/lib/cloud/data/result.json { "v1": { "datasource": null, "errors": [ "[Errno 21] Is a directory: '/var/lib/cloud/instance'", "[Errno 21] Is a directory: '/var/lib/cloud/instance'", "[Errno 21] Is a directory: '/var/lib/cloud/instance'", "[Errno 21] Is a directory: '/var/

[Bug 1927911] Re: Update intel-microcode to latest upstream release 20210216 for CVE fixes for xeon platforms

** Also affects: intel-microcode (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: intel-microcode (Ubuntu Impish) Importance: Undecided Status: New ** Also affects:

[Bug 1927029] Re: ua attach command fails

I uploaded it to this Gist: https://gist.githubusercontent.com/atrepca/dede1e2f4b894a444d6ac0f0abeaf5dd/raw/e5877b08940773e01e5ef93596f31ede49cb69e0 /ubuntu-advantage.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.lau

[Bug 1927029] Re: ua attach command fails

Trying again... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-a

[Bug 1927029] Re: ua attach command fails

I can't seem to be able to attach, ok to post the full log here? It's 1342 lines. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about

[Bug 1920180] Re: Can't detect intel wifi 6235

Updates: the patch was not included in kernel 5.13-rc1 yet but I sent a follow-up email and let's see how this goes. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920180 Title: Can't detect intel w

[Bug 1927029] Re: ua attach command fails

Attaching the full ubuntu-advantage.log file too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://bugs.lau

[Bug 1927029] Re: ua attach command fails

snap --version: $ snap --version snap2.49.2 snapd 2.49.2 series 16 ubuntu 16.04 kernel 4.4.0-145-generic Tried the steps here: $ sudo ua disable livepatch Livepatch is not currently enabled See: sudo ua status Unexpected error(s)

[Bug 1927911] [NEW] Update intel-microcode to latest upstream release 20210216 for CVE fixes for xeon platforms

Public bug reported: Intel released microcode 20210216 which should be incorporated into the various Ubuntu releases as a security update. ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubunt

[Bug 1927004] Re: [MIR] fence-agents

Lucas - thanks for the heads up, I have marked this CVE-2019-10153 as not-affected for focal+ in the Ubuntu CVE Tracker - https://git.launchpad.net/ubuntu-cve- tracker/commit/?id=2b90bcddc25956d0c037e6119460f2778ee64c0a -- You received this bug notification because you are a member of Ubuntu Bugs

[Bug 1927029] Re: ua attach command fails

1. Correct. It's 10 EC2 instances of different types, and using a few different Xenial AMIs: - ami-e1fe2281 20160921 - ami-a9d276c9 20161020 - ami-7ac6491a 20170307 To make it more confusing, other instances using these same AMIs are fine. 2. It was installed following the steps here: https://d

[Bug 1865838] Re: no error displayed on failed fingerprint authentication

** Changed in: oem-priority Assignee: Alex Tu (alextu) => Andy Chi (andch) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865838 Title: no error displayed on failed fingerprint authenticat

[Bug 1912050] Re: Use after free in libgetdata v0.10.0 may lead to arbitrary code execution

This is now public at https://bugzilla.redhat.com/show_bug.cgi?id=1956348 so marking it public here too. ** Bug watch added: Red Hat Bugzilla #1956348 https://bugzilla.redhat.com/show_bug.cgi?id=1956348 ** Information type changed from Private Security to Public Security -- You received this

[Bug 1927029] Re: ua attach command fails

dmesg has a ton of audit messages, no errors of any kind. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1927029 Title: ua attach command fails To manage notifications about this bug go to: https://

[Bug 1927029] Re: ua attach command fails

snap info canonical-livepatch: $ snap info canonical-livepatch name: canonical-livepatch summary: Canonical Livepatch Client publisher: Canonical✓ store-url: https://snapcraft.io/canonical-livepatch contact: sn...@canonical.com license: unset description: |

[Bug 1927029] Re: ua attach command fails

This is happening with more than one instance, it's 10+ 16.04 servers that were all launched around the same time. I'm running the Ansible code again to get an exact count, and look for any similarities. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subsc

[Bug 1927029] Re: ua attach command fails

> Is this a persistent issue or does it eventually resolve with retries? Persistent issue, doesn't go away. > Did this happen early in the machine uptime, perhaps in cloud-init? This is not during the boot process, the instance has been up for a while, I just installed ubuntu-advantage-tools and

[Bug 1927029] Re: ua attach command fails

$ sudo ua enable livepatch One moment, checking your subscription first Unable to configure Livepatch: Failed running command '/snap/bin/canonical-livepatch config remote-server=https://livepatch.canonical.com' [exit(1)]. Message: 2021/05/04 15:18:29 error executing config: Livepatchd error: Cou

[Bug 1927029] Re: ua attach command fails

$ sudo snap logs canonical-livepatch.canonical-livepatchd 2021-05-03T23:52:02Z canonical-livepatch.canonical-livepatchd[8596]: 2021/05/03 23:52:02 Couldn't setup system logger. 2021-05-03T23:52:02Z systemd[1]: snap.canonical-livepatch.canonical-livepatchd.service: Main process exited, code=exite

[Bug 1927029] [NEW] ua attach command fails

Public bug reported: ua attach command fails with: $ sudo ua attach $TOKEN Enabling default service esm-infra Updating package lists UA Infra: ESM enabled A reboot is required to complete install. Enabling default service livepatch Unable to configure Livepatch: Failed running command '/snap/bin

[Bug 1827690] Re: [19.04][stein] barbican-worker is down: Requested revision 1a0c2cdafb38 overlaps with other requested revisions 39cf2e645cba

** Changed in: charm-barbican Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1827690 Title: [19.04][stein] barbican-worker is down: Requested revision 1

[Bug 1926820]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Reviewing your dmesg attachment to this bug report it seems that there may be a problem with your hardware. I'd recommend performing a back up and then investigating the situation. Measures you might take include

[Bug 1926820] Re: package libseccomp2:amd64 2.4.3-1ubuntu3.20.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privile

[Bug 1874808]

e now changed slightly, could you please re-state the current: - steps to reproduce - actual behavior - expected behavior as well as any other details that you believe are relevant to pin down this bug. ¡Gracias! Alex -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly

It is possible udev rules are broken. You might be able to identify source of this power button events by checking keyboard scancode (with evtest) and/or workaround this by removing the power button assignment or assigning it to something else == get scancode == * run "sudo apt install evtes" *

[Bug 1926817] [NEW] kube-controller-manager crashes due to 5 duplicate certs in ca.crt

Public bug reported: On Kubernetes deployments with cert_manager_api enabled, the certificate container fails to come up because there are five duplicate public certificates in /etc/kubernetes/certs/ca.crt, this causes the service to crash: Apr 30 23:44:21 k8s-prod-24e2ug52zqb4-master-0 bash[1536

[Bug 1926527] Re: "Power off" dialog appears when any three keyboard keys are pressed quickly

You can run "sudo showkey" to monitor what keys are generated. When I press my power button keycode 116 press and release are generated (see keycode # on https://github.com/torvalds/linux/blob/master/include/uapi/linux/input- event-codes.h). $ sudo showkey kb mode was ?UNKNOWN? [ if you are trying

[Bug 1926257] Re: Keys not working on laptop

Did you also observe the same issue on Ubuntu 21.04 as well? ** Summary changed: - Keys not working on laptop + Keys not working on Lenovo ideapad 530S -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1

[Bug 1926257] Re: Keys not working on laptop

Please be more specific what some keys are -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1926257 Title: Keys not working on Lenovo ideapad 530S To manage notifications about this bug go to: https:/

[Bug 1874808]

¡Hola u661513, Jani! Hope these lines find you well. Are you still seeing this bug on the current version of Firefox available at https://www.mozilla.org/firefox/new/ ? Please let us know. ¡Gracias! Alex -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1926101] [NEW] package linux-modules-nvidia-460-5.8.0-50-generic 5.8.0-50.56~20.04.1+1 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

Public bug reported: Just pops up constantly ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-nvidia-460-5.8.0-50-generic 5.8.0-50.56~20.04.1+1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_

[Bug 1925397] [NEW] podman can't find runc

Public bug reported: So, I saw in the dependencies for the podman package ( on ubuntu's repos ) that it lets you install crun or runc. I remembered on my system that it defaulted to crun, but when I went to start a container on podman it was looking for runc by default ( https://imgur.com/Z8aqLwN

[Bug 1923150] Re: unexpected error pop-up after 'apt install nvidia-driver-455'

It seems still an issue if a user installed Focal by 20.04.1 before then he buy and then plug-in a new Nvidia card to his PC then install nvidia driver. The user will still get this error. The version(2.0.4) of fixed apt not in focal-security, so user not updated apt manually will still get the pr

[Bug 1923697] Re: touchpad don't work

Your bug description talked about vi, not touchpad isn't usually related to vi. Could you please confirm whether the bug is vi-related. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923697 Title:

[Bug 1922754] Re: Make AMD gpus choose YCbCr420 encoding automatically when required for 4k 60Hz output

@matombo, You will want to take a look at https://wiki.ubuntu.com/KernelTeam/KernelUpdates for how to send SRUs to Ubuntu kernel. An example will be LP:1923000 (you can add SRU template to this bug), cover page: https://lists.ubuntu.com/archives/kernel- team/2021-April/119154.html & patch: https:

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

similarly for xenial there is only one failure for libseccomp autopkgtests which is systemd/i386 - https://people.canonical.com /~ubuntu-archive/proposed- migration/xenial/update_excuses.html#libseccomp - and this looks reasonably flaky in recent history https://autopkgtest.ubuntu.com/packages/s/sy

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

libseccomp on bionic looks good from what I can see on https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#libseccomp - can this please migrate now? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu

[Bug 1891682] Re: [MIR] sane-airscan

No, thanks again for your work in addressing these (sorry I didn't realise you were blocked on me responding) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891682 Title: [MIR] sane-airscan To mana

[Bug 1793444] Re: Request to support software raid devices, vroc raid also need this

** Tags added: intel originate-from-1922657 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793444 Title: Request to support software raid devices, vroc raid also need this To manage notifications a

[Bug 1920180] Re: Can't detect intel wifi 6235

For references, the patch was sent and can be viewed @ https://www.spinics.net/lists/stable/msg452937.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920180 Title: Can't detect intel wifi 6235

[Bug 1922545] Re: gnome-system-monitor fails to launch

Can you try to run on xorg instead of wayland? ** Summary changed: - Fails to launch + gnome-system-monitor fails to launch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922545 Title: gnome-syste

[Bug 1908818] Re: pure packaging of libnss3

@paelzer - we just got another duplicate of this filed for nss in groovy - is the server team working on a fix for this for groovy? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908818 Title: pure

[Bug 1922553] Re: libnss3 package contains invalid library paths

*** This bug is a duplicate of bug 1908818 *** https://bugs.launchpad.net/bugs/1908818 ** This bug has been marked a duplicate of bug 1908818 pure packaging of libnss3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bug

[Bug 1921423] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1

Hi, Thanks for your reply!! Your solution was effective. I worked, unlocked the file and then I chmoded it!! Best regards, Alex Leandro Rosa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921423

[Bug 1915945] Re: package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: installed sudo package post-installation script subprocess returned error exit status 1

Hi, thanks for answering. The output of the command lsattr -l /etc/sudoers is Extents. By the way, I appreciate your help but I got the problem solved by the commands: chattr -i /etc/sudoers and then chmod!! Best regards!! -- You received this bug notification because you are a member of Ubun

[Bug 1922546] [NEW] can't upgrade from vers 18 to ver 20.04

Public bug reported: upgrade from 18 to 20 does not complete system comment: propbably other software ppa-purge does not find any problems updates are still working (everything is fine in vers 18) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.42 ProcVe

[Bug 1922279] [NEW] package libpam-systemd:amd64 245.4-4ubuntu3.5 failed to install/upgrade: пакунок знаходиться у поганому стані; потрібно перевстановити його до початку налаштування

Public bug reported: libpam-systemd:amd64 E: Sub-process /usr/bin/dpkg returned an error code (1) Description:Ubuntu 20.04.2 LTS Release:20.04 How to fix this Bug Thanks ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libpam-systemd:amd64 245.4-4ubuntu3.5 ProcVersionSigna

[Bug 1922111] Re: acpitz-acpi-0 wrong temperature

Data from acpitz (acpi thermalzone) are from BIOS. The peak values you are seeing can be the results of BIOS/EC sampling mechanism, i.e. instantaneous values instead of average values. The must be fixed in BIOS/EC firmware not in OS; however, you can disable acpitz by kernel parameter "thermal.off

[Bug 1274613] Re: module-bluetooth-discover does not load on login

I still have this problem :( module-bluetooth-discover module initialization failed. It's instructed to load in /etc/pulse/default.pa, but is not loaded when the system is started up. It's also not able to be manually loaded. Help!! D: -- You received this bug notification because you are a mem

[Bug 1922012] [NEW] FTBFS: john fails to compile for hirsute on s390x with LTO

Public bug reported: >From https://launchpadlibrarian.net/530627861/buildlog_ubuntu-hirsute- s390x.john_1.8.0-4_BUILDING.txt.gz gcc DES_fmt.o DES_std.o DES_bs.o DES_bs_b.o MD5_fmt.o MD5_std.o BF_fmt.o BF_std.o bench.o best.o common.o config.o formats.o math.o memory.o miscnl.o params.o path.o s

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

For the focal autopkgtest failures above: docker.io/19.03.8-0ubuntu1.20.04.2 (arm64) systemd/245.4-4ubuntu3.5 (ppc64el) The docker.io/arm64 failed due to network issues in the test infrastructure: + lxc launch ubuntu-daily:focal/arm64 docker -c security.nesting=true Creating docker Error: Failed

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

The systemd/229-4ubuntu21.29 (i386) test looks very flaky - this seems to fail more often than not looking at https://autopkgtest.ubuntu.com/packages/s/systemd/xenial/i386 - and the tests which failed for the libseccomp 2.5.1-1ubuntu1~16.04.1 run (boot- and-services and boot-smoke) also failed for

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

Regarding the failing autopkgtests from bionic reported in comment #28: - the containerd and chrony ones on s390x are transient failures due to networking issues in the test infrastructure so should hopefully pass on a re-run. - I can't reproduce the flatpak/amd64 failure locally so I assume th

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

Tested for libseccomp as follows: cat

[Bug 1891810] Re: Backport 2.5.1 to fix missing openat2 syscall, causing problems for fuse-overlayfs in nspawn containers

The fix for systemd's LP: #1918696 is not in the systemd xenial SRU since, as noted in that bug, systemd in xenial doesn't include upstream commit 469830d1426a91e0897c321fdc8ee428f0a750c1 which reworked the code to switch from seccomp_rule_add to seccomp_rule_add_exact. In this case systemd could h

[Bug 1918696] Re: libseccomp 2.5.1 will break unit tests on ppc

Yes this is not needed for xenial since that version of systemd is not new enough to be affected by this issue (see the bug description for more details). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/

[Bug 1921717] UdevDb.txt

apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481943/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title: As

[Bug 1921717] acpidump.txt

apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481945/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1921717] WifiSyslog.txt

apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481944/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Ti

[Bug 1921717] RfKill.txt

apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481942/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title: As

[Bug 1921717] PulseList.txt

apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481941/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Titl

[Bug 1921717] ProcModules.txt

apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481940/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717

[Bug 1921717] ProcInterrupts.txt

apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481939/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/192

[Bug 1921717] ProcEnviron.txt

apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481938/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717

[Bug 1921717] ProcCpuinfoMinimal.txt

apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481937/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/

[Bug 1921717] ProcCpuinfo.txt

apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481936/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717

[Bug 1921717] Lsusb-v.txt

apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481935/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title:

[Bug 1921717] Lsusb-t.txt

apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481934/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title:

[Bug 1921717] Lsusb.txt

apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481933/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title: Asus

[Bug 1921717] Lspci-vt.txt

apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481932/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title:

[Bug 1921717] Lspci.txt

apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481931/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title: Asus

[Bug 1921717] IwConfig.txt

apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481930/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title:

[Bug 1921717] CurrentDmesg.txt

apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481929/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717

[Bug 1921717] CRDA.txt

apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481928/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title: Asus G

[Bug 1921717] AlsaInfo.txt

apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1921717/+attachment/5481927/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Title:

[Bug 1921717] Re: Asus GX701LV | ALC294 | Speakers don't work on 20.04

AND + /dev/snd/controlC1: alex 2061 F pulseaudio + /dev/snd/controlC0: alex 2061 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: KDE + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-09-11 (199 days ago) + InstallationMedia: Kubuntu 20.04.1 LT

[Bug 1921717] Re: Asus GX701LV | ALC294 | Speakers don't work on 20.04

** Attachment added: "alsa-info-5.11.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921717/+attachment/5481924/+files/alsa-info-5.11.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/19

[Bug 1921717] [NEW] Asus GX701LV | ALC294 | Speakers don't work on 20.04

/dev/snd/controlC1: alex 2061 F pulseaudio /dev/snd/controlC0: alex 2061 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-11 (199 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal F

[Bug 1921717] Re: Asus GX701LV | ALC294 | Speakers don't work on 20.04

** Attachment added: "alsa-info.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921717/+attachment/5481923/+files/alsa-info.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921717 Tit

[Bug 1919411] Re: External Keyboard and Mouse not working

When you preferred to "External", did you mean USB keyboard and mouse? There were weird errors such as below in the bug description. You may want to live boot to 20.10 (or any versions) and verify whether USB devices work, especially the system was upgraded from 18.04 to 20.10. Lsusb: Error: comm

[Bug 1919411] Re: External Keyboard and Mouse not working

** Summary changed: - bug + External Keyboard and Mouse not working -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1919411 Title: External Keyboard and Mouse not working To manage notifications abo

[Bug 1921504] Re: Ubuntu 20.04 Install

Since you have a Broadcom wifi, you will want to check the driver in "Software & Update" and "Additional Driver" tab. ** Summary changed: - Ubuntu 20.04 Install + Ubuntu 20.04 no wifi (Broadcom) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed t

[Bug 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers

** Changed in: libseccomp (Ubuntu Xenial) Status: Confirmed => In Progress ** Changed in: libseccomp (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: libseccomp (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: libseccomp (Ubuntu Groovy) St

[Bug 1818881] Re: ath10k_pci crashing

It can be reproduced on XPS 19 9380 + Ubuntu 20.04 + 5.8.0-45-generic. It's happening for a while on 20.04, I'm not sure the issue start from which version of kernel or firmware. $ apt list linux-firmware Listing... Done linux-firmware/focal-updates,focal-updates,now 1.187.10 all [installed,auto

[Bug 1867668] Re: Visual artifacts in Gnome Shell when using the old 'intel' Xorg driver

I have my minipc server Gigabite Brix 4105 and the monitor is not connected to it. Installed Ubuntu Desktop 12.04.2. I control it from my PC using VNC and no visual artifacts. This is done through 20-intel.conf Section "Device" Identifier "intelgpu0" Driver "intel" Option "VirtualHea

[Bug 1921535] [NEW] package u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 failed to install/upgrade: installed u-boot-rpi:arm64 package post-installation script subprocess returned error exit status

*** This bug is a duplicate of bug 1914711 *** https://bugs.launchpad.net/bugs/1914711 Public bug reported: sowed-up during system updating ProblemType: Package DistroRelease: Ubuntu 20.10 Package: u-boot-rpi:arm64 2020.10+dfsg-1ubuntu0~20.10.1 Uname: Linux 5.4.73v64 aarch64 ApportVersion: 2

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

@david, I am also watching the bugzilla 201753. I am also looking forward seeing a better solution -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917203 Title: AMD-Vi: Unable to read/write to IOMMU

[Bug 1921423] [NEW] package sudo 1.8.31-1ubuntu1.2 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script post-installation retornou erro do status de saída 1

n reason of the many errors that started happening when updating this machine. I can't stop this machine now, and I don't want to run the risk of trying to use the installation software to try to repair it. If you have any idea on how to chmod the file, I'll be grateful. Best regar

[Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

Problem has NOT been fixed for my setup either: - Kernel: 5.9.6-050906-generic - OS: Ubuntu 20.04.1 LTS - Machine: Custom built PC? - Headset: Apple Airpods pro I was able to have a workaround by following this answer and setting up ofono: https://askubuntu.com/a/1236379/295477. However, I expect

[Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

*** This bug is a duplicate of bug 1871794 *** https://bugs.launchpad.net/bugs/1871794 Problem has NOT been fixed for my setup either: - Kernel: 5.9.6-050906-generic - OS: Ubuntu 20.04.1 LTS - Machine: Custom built PC? - Headset: Apple Airpods pro I was able to have a workaround by following

[Bug 1920180] Re: Can't detect intel wifi 6235

It will take a while for a patch to be merged, so you will lose wifi 6235 if you update to newer kernels. There are processes to merge a patch. A normal process is like below: 1. a patch is sent to upstream (cc to stable kernel) 2. it gets reviewed and merged by a maintainer, and is included in n

[Bug 1920180] Re: Can't detect intel wifi 6235

I will update status here if there is any -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1920180 Title: Can't detect intel wifi 6235 To manage notifications about this bug go to: https://bugs.launch

[Bug 1920180] Re: Can't detect intel wifi 6235

** Changed in: linux (Ubuntu) Status: Fix Committed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchp

[Bug 1920180] Re: Can't detect intel wifi 6235

Please give the test kernel (https://people.canonical.com/~alexhung/LP1920180/) a try. It adds a new id to iwlwifi as below. If it works, a patch will be sent to upstream and stable kernels which will be picked up by Ubuntu kernel later. $ git diff drivers/net/wireless/intel/iwlwifi/pcie/drv.c dif

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

I also tried to increase the msleep, (retry = 5) - msleep(20); + msleep(40); The same result on #7. I am not sure whether this applies to my AMD Ryzen 5 2500U. Update: If the system is powered off for long time (i.e. 5+ mins), the patch will work. In any case, it seem

[Bug 1917203] Re: AMD-Vi: Unable to read/write to IOMMU perf counter

I did some tests with retry, based on latest mainline kernel today 1. change retry to 10 2. install kernel and reboot/poweroff 3. on the first boot after install, regarding of reboot or poweroff, the patch works 4. after second boot (reboot or poweroff), it always fails -- You received this bug

[Bug 1891682] Re: [MIR] sane-airscan

I reviewed sane-airscan 0.99.24-1 as checked into hirsute. This shouldn't be considered a full audit but rather a quick gauge of maintainability. sane-airscan is a package that provides a sane backend which supports driverless network-connected scanners. - CVE History: - No CVE history, this i

[Bug 1891810] Re: Missing openat2 syscall, causes problems for fuse-overlayfs in nspawn containers

** Patch added: "libseccomp_2.5.1-1ubuntu1~20.04.1.debdiff" https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1891810/+attachment/5476578/+files/libseccomp_2.5.1-1ubuntu1~20.04.1.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

<    3   4   5   6   7   8   9   10   11   12   >