[Bug 2062972] Re: ntfs partition does not mount
Fresh Ubuntu 24.04 install here. Tried to mount my NFTS partition and I get the same error attached. ** Attachment added: "Screenshot from 2024-04-29 21-21-25.png" https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/2062972/+attachment/5772674/+files/Screenshot%20from%202024-04-29%2021-21-25.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062972 Title: ntfs partition does not mount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/2062972/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060745] Re: nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)
It seems to be an upstream issue: https://github.com/NetworkBlockDevice/nbd/issues/156 ** Bug watch added: github.com/NetworkBlockDevice/nbd/issues #156 https://github.com/NetworkBlockDevice/nbd/issues/156 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060745 Title: nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2060745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060745] [NEW] nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble)
Public bug reported: [ Impact ] NBD users who want to use /etc/nbdtab will face issues when trying to start the NBD Client. Trying to use the `systemd` service also doesn't work. [ Test Plan ] Inside a Noble VM (not a container): # apt update # apt install -y nbd-client nbd-server # modprobe nbd # truncate -s 1T /vol-0.img # cat > /etc/nbd-server/conf.d/exports.conf << _EOF_ [vol0] exportname = /vol-0.img _EOF_ # systemctl restart nbd-server.service Verify that NBD is working properly: # nbd-client localhost /dev/nbd0 -name vol0 It should work. To clean it up: # nbd-client -d /dev/nbd0 Now, trigger the problem: # cat >> /etc/nbdtab << _EOF_ nbd0 localhost vol0 _EOF_ # nbd-client nbd0 You should see the error: # nbd-client nbd0 Error: Socket failed: Connection refused Further attempts with `systemd` also fail: # systemctl restart nbd@nbd0 Job for nbd@nbd0.service failed because the control process exited with error code. See "systemctl status nbd@nbd0.service" and "journalctl -xeu nbd@nbd0.service" for details. And the logs: # journalctl -u nbd@nbd0.service -n 25 Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed) Apr 09 21:56:17 noble-nbd-1 systemd[1]: Starting nbd@nbd0.service - NBD client connection for nbd0... Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Socket failed: Connection refused Apr 09 21:56:17 noble-nbd-1 nbd-client[5698]: Error: Socket failed: Connection refused Apr 09 21:56:17 noble-nbd-1 nbd_client[5698]: Exiting. Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Main process exited, code=exited, status=1/FAILURE Apr 09 21:56:17 noble-nbd-1 systemd[1]: nbd@nbd0.service: Failed with result 'exit-code'. Apr 09 21:56:17 noble-nbd-1 systemd[1]: Failed to start nbd@nbd0.service - NBD client connection for nbd0. ** Affects: nbd (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/2060745 Title: nbd-client fails to connect when using /etc/nbdtab on Ubuntu 24.04 (Noble) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2060745/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057717] Re: dpkg linux-image-6.5.0-25-generic ever returns error
I run the command 'apport-collect 2057717', the answer: "Package linux- signed-hwe-6.5 not installed and no hook available, ignoring" ~$ apport-collect 2057717 Package linux-signed-hwe-6.5 not installed and no hook available, ignoring -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057717 Title: dpkg linux-image-6.5.0-25-generic ever returns error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.5/+bug/2057717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2057717] [NEW] dpkg linux-image-6.5.0-25-generic ever returns error
Public bug reported: English: /etc/kernel/postinst.d/zz-update-grub: /usr/sbin/grub-probe: error: Failed to get canonical path from "rpool/ROOT/ubuntu_o2pu7m". run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-6.5.0-25-generic (--configure): the installed subprocess, from the linux-image-6.5.0-25-generic package, the post-installation script returned exit status 1 error Errors were found during processing of: linux-image-6.5.0-25-generic E: The subprocess /usr/bin/dpkg returned an error code (1) Pt-BR: /etc/kernel/postinst.d/zz-update-grub: /usr/sbin/grub-probe: erro: falha ao obter o caminho canónico de "rpool/ROOT/ubuntu_o2pu7m". run-parts: /etc/kernel/postinst.d/zz-update-grub exited with return code 1 dpkg: erro ao processar o pacote linux-image-6.5.0-25-generic (--configure): o subprocesso instalado, do pacote linux-image-6.5.0-25-generic, o script post-installation retornou erro do status de saída 1 Erros foram encontrados durante o processamento de: linux-image-6.5.0-25-generic E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.5.0-25-generic 6.5.0-25.25~22.04.1 ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8 Uname: Linux 6.5.0-17-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_6_5_0_17_17_generic_101 zfs ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 21:42:34 2024 InstallationDate: Installed on 2022-07-12 (609 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pt_BR.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/2057717 Title: dpkg linux-image-6.5.0-25-generic ever returns error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2057717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2055294] Re: /usr/lib/grub/grub-multi-install fails on noble-daily
Hi! I was `do-release-upgrade -d` an Ubuntu 22.04 to Ubuntu 24.04 to test and got bitten by this bug too! lol The command `/usr/lib/grub/grub-multi-install --target=x86_64-efi` returns 10, causing `dpkg --configure grub-efi-amd64-signed` to fail. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2055294 Title: /usr/lib/grub/grub-multi-install fails on noble-daily To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/2055294/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot
** Description changed: The `systemd` service for starting the NBD Clients on boot isn't working. ### Steps to Reproduce: 0. Install NBD - apt install nbd-server nbd-client - - 1. Prepare an NBD server with a disk image to share. For instance: - truncate -s 1T /vol-0.img - - - 2. Configure the NBD server by adding the following to `/etc/nbd-server/conf.d/exports.conf`: + 2. Configure the NBD server by adding the following to `/etc/nbd- + server/conf.d/exports.conf`: - [vol0] exportname = /vol-0.img - - 3. Configuring the client connection in `/etc/nbdtab`: Contents of `/etc/nbdtab`: - nbd0 localhost vol0 - - 4. Enable it on `systemd`: - systemctl enable nbd@nbd0 - Here's what I see: - # systemctl enable nbd@nbd0 Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service → /lib/systemd/system/nbd@.service. Unit /lib/systemd/system/nbd@.service is added as a dependency to a non-existent unit dev-nbd0.device. - - 5. Add `nbd` auto-load to system'd boot: echo nbd > /etc/modules-load.d/nbd.conf - 6. Reboot - sudo reboot - - 7. The service not coming up on the system's boot. Look: After rebooting the system, the NBD clien for `nbd0` isn't running (but it's enabled on systemd). - - root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 + root@demo-nbd-test:~# systemctl status nbd@nbd0 ○ nbd@nbd0.service - NBD client connection for nbd0 Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) Active: inactive (dead) Docs: man:nbd-client - Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed) + Feb 21 22:54:22 demo-nbd-test systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed) - But if you try to start it again. It'll work: - - root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0 - root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 + root@demo-nbd-test:~# systemctl start nbd@nbd0 + root@demo-nbd-test:~# systemctl status nbd@nbd0 ● nbd@nbd0.service - NBD client connection for nbd0 Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago Docs: man:nbd-client Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, status=0/SUCCESS) Main PID: 1096 (code=exited, status=0/SUCCESS) CPU: 4ms - Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client connection for nbd0... - Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 3145728MB - Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0 - Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client connection for nbd0. + Feb 21 22:57:37 demo-nbd-test systemd[1]: Starting NBD client connection for nbd0... + Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Negotiation: ..size = 3145728MB + Feb 21 22:57:37 demo-nbd-test nbd-client[1096]: Connected /dev/nbd0 + Feb 21 22:57:37 demo-nbd-test systemd[1]: Finished NBD client connection for nbd0. - So this forces me to have the following `/etc/rc.local` file as a workaround: - #!/bin/bash sleep 6 systemctl start nbd@nbd0 - Make it executable: - chmod +x /etc/rc.local - Reboot again, it'll be started on next boot! I don't think that the `/etc/rc.local` should be part of this procedure... =P NOTE: Don't need to run `update-initramfs -k all -u`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054616 Title: The systemd service for NBD Client doesn't come up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot
** Description changed: The `systemd` service for starting the NBD Clients on boot isn't working. ### Steps to Reproduce: 0. Install NBD -``` -apt install nbd-server nbd-client -``` + - + apt install nbd-server nbd-client + - + 1. Prepare an NBD server with a disk image to share. For instance: -```bash -truncate -s 1T /vol-0.img -``` + + - + truncate -s 1T /vol-0.img + - + 2. Configure the NBD server by adding the following to `/etc/nbd-server/conf.d/exports.conf`: -``` -[vol0] -exportname = /vol-0.img -``` + + - + [vol0] + exportname = /vol-0.img + - + 3. Configuring the client connection in `/etc/nbdtab`: Contents of `/etc/nbdtab`: -``` -nbd0 localhost vol0 -``` + - + nbd0 localhost vol0 + - + 4. Enable it on `systemd`: -```bash -systemctl enable nbd@nbd0 -``` + - + systemctl enable nbd@nbd0 + - Here's what I see: - ``` + - # systemctl enable nbd@nbd0 Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service → /lib/systemd/system/nbd@.service. Unit /lib/systemd/system/nbd@.service is added as a dependency to a non-existent unit dev-nbd0.device. - ``` + - + 5. Add `nbd` auto-load to system'd boot: - ``` - echo nbd > /etc/modules-load.d/nbd.conf - ``` + echo nbd > /etc/modules-load.d/nbd.conf + 6. Reboot -``` -sudo reboot -``` + - + sudo reboot + - + 7. The service not coming up on the system's boot. Look: After rebooting the system, the NBD clien for `nbd0` isn't running (but it's enabled on systemd). - ``` + - root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 ○ nbd@nbd0.service - NBD client connection for nbd0 - Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) - Active: inactive (dead) -Docs: man:nbd-client + Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) + Active: inactive (dead) + Docs: man:nbd-client Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed) - ``` + - But if you try to start it again. It'll work: - ``` + - root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0 root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 ● nbd@nbd0.service - NBD client connection for nbd0 - Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) - Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago -Docs: man:nbd-client - Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, status=0/SUCCESS) -Main PID: 1096 (code=exited, status=0/SUCCESS) - CPU: 4ms + Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) + Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago + Docs: man:nbd-client + Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, status=0/SUCCESS) + Main PID: 1096 (code=exited, status=0/SUCCESS) + CPU: 4ms Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client connection for nbd0... Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 3145728MB Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0 Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client connection for nbd0. - ``` + - So this forces me to have the following `/etc/rc.local` file as a workaround: - ``` + - #!/bin/bash sleep 6 systemctl start nbd@nbd0 - ``` + - Make it executable: - ``` + - chmod +x /etc/rc.local - ``` + - Reboot again, it'll be started on next boot! I don't think that the `/etc/rc.local` should be part of this procedure... =P NOTE: Don't need to run `update-initramfs -k all -u`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054616 Title: The systemd service for NBD Client doesn't come up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot
I've updated the description to include all the steps necessary to reproduce the issue on Ubuntu 22.04 (Cloud Image - Server Minimal install). This seems to be a `systemd` thing! lol ** Description changed: The `systemd` service for starting the NBD Clients on boot isn't working. ### Steps to Reproduce: + + 0. Install NBD + +``` +apt install nbd-server nbd-client +``` 1. Prepare an NBD server with a disk image to share. For instance: ```bash truncate -s 1T /vol-0.img ``` 2. Configure the NBD server by adding the following to `/etc/nbd-server/conf.d/exports.conf`: ``` [vol0] exportname = /vol-0.img ``` 3. Configuring the client connection in `/etc/nbdtab`: Contents of `/etc/nbdtab`: ``` nbd0 localhost vol0 ``` 4. Enable it on `systemd`: ```bash systemctl enable nbd@nbd0 ``` - 5. The service not coming up on the system's boot. Look: + Here's what I see: + + ``` + # systemctl enable nbd@nbd0 + Created symlink /etc/systemd/system/dev-nbd0.device.requires/nbd@nbd0.service → /lib/systemd/system/nbd@.service. + Unit /lib/systemd/system/nbd@.service is added as a dependency to a non-existent unit dev-nbd0.device. + ``` + + 5. Add `nbd` auto-load to system'd boot: + + ``` + echo nbd > /etc/modules-load.d/nbd.conf + ``` + + 6. Reboot + +``` +sudo reboot +``` + + 7. The service not coming up on the system's boot. Look: After rebooting the system, the NBD clien for `nbd0` isn't running (but it's enabled on systemd). ``` root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 ○ nbd@nbd0.service - NBD client connection for nbd0 - Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) - Active: inactive (dead) - Docs: man:nbd-client + Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) + Active: inactive (dead) +Docs: man:nbd-client Feb 21 22:54:22 cephao-1-ceph-osd-1 systemd[1]: nbd@nbd0.service: Dependency Before=dev-nbd0.device ignored (.device units cannot be delayed) ``` - Then, after a restart, it works: + But if you try to start it again. It'll work: ``` - root@cephao-1-ceph-osd-1:~# systemctl restart nbd@nbd0 + root@cephao-1-ceph-osd-1:~# systemctl start nbd@nbd0 root@cephao-1-ceph-osd-1:~# systemctl status nbd@nbd0 ● nbd@nbd0.service - NBD client connection for nbd0 - Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) - Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago - Docs: man:nbd-client - Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, status=0/SUCCESS) - Main PID: 1096 (code=exited, status=0/SUCCESS) - CPU: 4ms + Loaded: loaded (/lib/systemd/system/nbd@.service; enabled; vendor preset: enabled) + Active: active (exited) since Wed 2024-02-21 22:57:37 UTC; 2s ago +Docs: man:nbd-client + Process: 1096 ExecStart=//sbin/nbd-client nbd0 (code=exited, status=0/SUCCESS) +Main PID: 1096 (code=exited, status=0/SUCCESS) + CPU: 4ms Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Starting NBD client connection for nbd0... Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Negotiation: ..size = 3145728MB Feb 21 22:57:37 cephao-1-ceph-osd-1 nbd-client[1096]: Connected /dev/nbd0 Feb 21 22:57:37 cephao-1-ceph-osd-1 systemd[1]: Finished NBD client connection for nbd0. ``` So this forces me to have the following `/etc/rc.local` file as a workaround: ``` #!/bin/bash - systemctl restart nbd@nbd0 + sleep 6 + systemctl start nbd@nbd0 ``` - If this is not the proper way of automatically starting a `nbd0` NBD - client, please, let me know! Perhaps documentation should be more clear. + Make it executable: - Interesting reference: - https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054470 + ``` + chmod +x /etc/rc.local + ``` + + Reboot again, it'll be started on next boot! + + I don't think that the `/etc/rc.local` should be part of this + procedure... =P + + NOTE: Don't need to run `update-initramfs -k all -u`. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054616 Title: The systemd service for NBD Client doesn't come up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04
Oops, wrong bug report. Ignore my previous message. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054470 Title: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot
I'm testing on Ubuntu 22.04.4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054616 Title: The systemd service for NBD Client doesn't come up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054616] Re: The systemd service for NBD Client doesn't come up on boot
Hi Mitchell, No worries at all! I forgot to mention another step I took: ``` echo nbd > /etc/modules-load.d/nbd.conf ``` Otherwise it won't load the module on boot. Perhaps there's also a need to `update-initramfs -k all -u`, not 100% sure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054616 Title: The systemd service for NBD Client doesn't come up on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nbd/+bug/2054616/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2054470] Re: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04
Hi Sergio, Thank you for taking the taking to troubleshoot this! I forgot to mention another step I took: ``` echo nbd > /etc/modules-load.d/nbd.conf ``` Perhaps there's also a need to `update-initramfs -k all -u`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2054470 Title: NBD Client Fails to Parse /etc/nbdtab Correctly on Ubuntu 22.04 and 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/nbd/+bug/2054470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-BR] Como resolver a vulnerabilidade TCP Sequence Number Approximation Based Denial of Service
Bom dia pessoal! Tudo bem? Preciso de ajuda para resolver a vulnerabilidade "TCP Sequence Number Approximation Based Denial of Service. Encontrei o link https://ubuntu.com/security/CVE-2004-0230, mas fiquei em dúvida. A instalação do Quagga vai resolver a vulnerabilides? Se alguém tiver alguma outra saída para resolver essa vuln, ficarei muito grato. Obrigado. -- Thiago Silveira -- Mais sobre o Ubuntu em português: http://www.ubuntu-br.org/comece Lista de discussão Ubuntu Brasil Histórico, descadastramento e outras opções: https://lists.ubuntu.com/mailman/listinfo/ubuntu-br
[Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
No, I'm using Ubuntu 20.04.4 LTS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Hey, how can I try this test kernel (5.18.0-3)? I've downloaded the three files in the link above but I can't install any of them, I'm always receiving the "unmet dependencies" warning. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962369] [NEW] package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status
Public bug reported: I've only did the cmd "sudo apt-get install mysql-server" ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Feb 26 12:55:27 2022 ErrorMessage: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 InstallationDate: Installed on 2022-02-17 (9 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Logs.var.log.daemon.log: MySQLConf.etc.mysql.conf.d.mysql.cnf: [mysql] MySQLConf.etc.mysql.conf.d.mysqldump.cnf: [mysqldump] quick quote-names max_allowed_packet = 16M MySQLConf.etc.mysql.my.cnf: Error: [Errno 40] Muitos níveis de links simbólicos: '/etc/mysql/my.cnf' MySQLVarLibDirListing: ['performance_schema', 'ib_logfile1', 'ib_logfile0.bak', '#ib_16384_0.dblwr', 'ib_buffer_pool', 'ibdata1', 'ib_logfile0.old', 'test', 'aria_log_control', 'ib_logfile0', 'ib_logfile1.bak', 'auto.cnf', 'binlog.index', 'ib_logfile1.old', '#ib_16384_1.dblwr', 'aria_log.0001', 'debian-5.7.flag', 'mysql', 'multi-master.info'] ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.13.0-30-generic root=UUID=ce25e500-abe2-495b-a90b-a84be235ae2a ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: mysql-8.0 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mysql-8.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962369 Title: package mysql-server-8.0 8.0.28-0ubuntu0.20.04.3 failed to install/upgrade: o subprocesso instalado, do pacote mysql-server-8.0, o script post-installation retornou erro do status de saída 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-8.0/+bug/1962369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hello Juerg, Em quinta-feira, 20 de janeiro de 2022, às 12:32:48 -03, Juerg Haefliger escreveu: > If you want this fixed in Ubuntu I need to know what series are > affected. Hirsute goes EOL at the end of the month. Are Impish and/or > Jammy working or affected as well? I upgraded to Impish a while ago. I haven’t seen “retry page fault” messages in a long while (I don’t think it’s related to the distro upgrade, but not sure) so I’d say this particular bug is fixed at least for me (I have a Picasso GPU). Which is not to say that things are rosy, unfortunately. But the other issues I see don’t cause any message to appear in dmesg so it’s hard to search for existing bug reports about them or open a new one. The following is off-topic for this bug report, but I’ll mention anyway, hope you’ll bear with me: One thing I noticed is that things did get rosy when I did two things: 1. Switched from Xorg to Wayland. 2. Switched Firefox to use Wayland as well. This led me to the conclusion that the bugs that plague my machine are triggered by something that Firefox does when it uses X (both “natively” or via XWayland). For some reason, when it uses Wayland it doesn’t trigger these GPU bugs. Another thing that might be relevant is that I have tons of tabs open (probably more than 200) distributed in 27 open windows. Perhaps I’m stressing some kind of resource limit in the driver or firmware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hello, I’d just like to report that I haven’t seen this problem in a while. The last time I see the “retry page fault” messages in my log was on August 9. I’ve been using the ‘amdgpu/picasso*‘ files from linux-firmware commit c46b8c364b82 (“ice: update package file to 1.3.26.0”) so apparently this particular problem was recently fixed. Which isn’t to say that I’m having a trouble-free amdgpu experience, unfortunately. Every week or so my laptop comes back from sleep with the screen and keyboard frozen (I can still ssh into it), but now the error is: kernel: [drm:drm_atomic_helper_wait_for_flip_done [drm_kms_helper]] *ERROR* [CRTC:67:crtc-0] flip_done timed out But it seems to be a separate problem from the one reported in this particular launchpad issue. I’ll see if I can find a more appropriate launchpad issue and post the details there. Thank you all for your help and support with this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
miliar “retry page fault” problem, which is what
made me look in dmesg.
The amdgpu/picasso* files are the same as in linux-firmware ‘main’ branch
as of today: commit 168452ee695b ("Merge tag 'iwlwifi-fw-2021-07-19' of
git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/linux-firmware into
main”). The kernel is Ubuntu’s 5.11.0-25-generic.
The full log is attached. Hope this helps.
Regards,
Thiago.
¹ I suggest trying to reproduce with the following steps:
1. Grab a laptop with a Picasso integrated GPU.
2. Install Kubuntu 21.04 on it.
3. Install and use Firefox from Flathub:
https://www.flathub.org/apps/details/org.mozilla.firefox
4. Log into KDE and run the above Firefox.
5. With the laptop on battery power (I have the impression that the bug is
easier to trigger that way), suspend and restore the machine a few times.
** Attachment added: "dmesg-refcount-underflow.log"
https://bugs.launchpad.net/bugs/1928393/+attachment/5515846/+files/dmesg-refcount-underflow.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928393
Title:
linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
retry page fault"
To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em segunda-feira, 12 de julho de 2021, às 15:12:19 -03, Alex Deucher escreveu: > Does the latest firmware in the firmware git tree help? > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.g > it/log/amdgpu I updated the picasso* files from commit: d79c26779d45 amdgpu: update vcn firmware for green sardine for 21.20 And I still see the issue. It took a while to reproduce: I updated the firmware (and ran `update-initramfs -u -k all` to get it into the initramfs) on July 12 and had the laptop turned on since then (closing the lid to put it to sleep), and today I saw the problem again. The full dmesg is attached. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1928393/+attachment/5511525/+files/dmesg.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
** Changed in: linux (Ubuntu) Status: Fix Released => 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
Hey, I've tested the kernel as suggested by Hui Wang (5.8.0-60-generic) and now my touchpad is working normally. Thanks! I couldn't install the latest kernel as suggested by Po-Hsu Lin because I was getting errors with unmet dependecies in one of the .deb files, even after installing the other two. As requested, I'm uploading the dmesg. ** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+attachment/5506525/+files/dmesg.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932528] Re: Touchpad stopped working after using as a tablet
** Description changed: Hi Everyone. So my touchpad has stopped working now out of the blue. I have a Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday. It was working perfectly, but it has stopped working as soon as I got into tablet mode. This laptop has the ability to fold its keyboard, so I did that and turn the laptop in 90 degrees (which the screen also turned due to the gyroscope). When we do this, its normal that the cursor disapears so we can you use only the touchscreen as a tablet, however when I turned back to a laptop the touchpad hasn't worked ag=0ain. I have rebooted the system, but still not signs of it. I have executed "cat /proc/bus/input/devices", but didn't find anything related to the touchpad, as the result shows below, so I think it's a kernel issue, right? Any thought how I could fix this? Thank you! I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=5986 Product=0535 Version=3653 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core
Re: [Bug 1928113] Re: Please enable firewalld support in libvirtd
Em quinta-feira, 17 de junho de 2021, às 10:07:39 -03, Christian Ehrhardt escreveu: > The dependencies already are (and would stay) > iptables (>= 1.8.1-1) | firewalld > from Package: libvirt-daemon-system. > This is very much the same in Debian where we have kept it enabled. > Therefore I can enable the support in libvirt without pushing anything > into main that isn't supposed to be there. > > Thanks for the ping here, working on this as part of libvirt 7.4 This is excellent news! Thanks for working on this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928113 Title: Please enable firewalld support in libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1928113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em quinta-feira, 17 de junho de 2021, às 00:45:30 -03, Thiago Jung Bauermann escreveu: > > > I think it may be related to a change in mesa. Specifically mesa > > > commit > > > 820dec3f7c7. For more info see > > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 > > > > I’ll run with Mario’s build of Mesa with that patch backported. > > Thanks, Mario! > > I’m running with the Mesa build from Mario’s PPA now. If I don’t see any > issue within two weeks, I think it will be possible to say that the bug > is gone, or at least much harder to hit. > > I can’t use my reproducer in this case, because I can’t change the Mesa > version inside the flatpak image. I just had this bug happen again spontaneously, while running with Mesa from Mario’s PPA. So this bug isn’t fixed by the patch mentioned by Alex. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932028] Re: missing version dependency on distro-info
Hi, I also see this problem with fresh installed Xenial. It's interesting to see that it's a bit tricky to reproduce this problem. I have to upgrade "ubuntu-advantage-tools" shortly after installing Xenial. Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1932028 Title: missing version dependency on distro-info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1932028/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1932528] Re: Touchpad stopped working after using as a tablet
** Description changed: Hi Everyone. So my touchpad has stopped working now out of the blue. I have a Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday. It was working perfectly, but it has stopped working as soon as I got into tablet mode. This laptop has the ability to fold its keyboard, so I did that and turn the laptop in 90 degrees (which the screen also turned due to the gyroscope). When we do this, its normal that the cursor disapears so we can you use only the touchscreen as a tablet, however when I turned back - to a laptop the touchpad hasn't worked again. + to a laptop the touchpad hasn't worked ag=0ain. I have rebooted the system, but still not signs of it. I have executed "cat /proc/bus/input/devices", but didn't find anything related to the touchpad, as the result shows below, so I think it's a kernel issue, right? Any thought how I could fix this? Thank you! - - I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= - H: Handlers=event0 + H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= - H: Handlers=kbd event1 + H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= - H: Handlers=kbd event2 + H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= - H: Handlers=sysrq kbd event3 leds + H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= - H: Handlers=rfkill kbd event5 + H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= - H: Handlers=mouse0 event4 + H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=5986 Product=0535 Version=3653 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9 U: Uniq= - H: Handlers=kbd event6 + H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10 U: Uniq= - H: Handlers=event7 + H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= - H: Handlers=event8 + H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= - H: Handlers=kbd event9 + H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= - H: Handlers=event10 + H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= - H: Handlers=event11 + H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= - H: Handlers=event12 + H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= - H:
[Bug 1932528] [NEW] Touchpad stopped working after using as a tablet
Public bug reported: Hi Everyone. So my touchpad has stopped working now out of the blue. I have a Lenovo Yoga 3 Pro 1370, and I installed Ubuntu yesterday. It was working perfectly, but it has stopped working as soon as I got into tablet mode. This laptop has the ability to fold its keyboard, so I did that and turn the laptop in 90 degrees (which the screen also turned due to the gyroscope). When we do this, its normal that the cursor disapears so we can you use only the touchscreen as a tablet, however when I turned back to a laptop the touchpad hasn't worked ag=0ain. I have rebooted the system, but still not signs of it. I have executed "cat /proc/bus/input/devices", but didn't find anything related to the touchpad, as the result shows below, so I think it's a kernel issue, right? Any thought how I could fix this? Thank you! I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product= Version= N: Name="Ideapad extra buttons" P: Phys=ideapad/input0 S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/input/input6 U: Uniq= H: Handlers=rfkill kbd event5 B: PROP=0 B: EV=13 B: KEY=81000800100c03 4430 0 2 B: MSC=10 I: Bus=0018 Vendor=03eb Product=8a10 Version=0100 N: Name="ATML1000:00 03EB:8A10" P: Phys=i2c-ATML1000:00 S: Sysfs=/devices/pci:00/INT3433:00/i2c-1/i2c-ATML1000:00/0018:03EB:8A10.0001/input/input8 U: Uniq= H: Handlers=mouse0 event4 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=5986 Product=0535 Version=3653 N: Name="Lenovo EasyCamera: Lenovo EasyC" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/input/input9 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input10 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card1/input11 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input12 U: Uniq= H: Handlers=kbd event9 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input13 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input14 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input15 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input16 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel HDMI HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:03.0/sound/card0/input17 U: Uniq= H: Handlers=event14 B: PROP=0 B: EV=21 B: SW=140 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.13 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Jun 18 08:09:23 2021 InstallationDate: Installed on 2021-06-18 (0 days ago) InstallationMedia:
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
I was finally able to spend a bit of time on this. Unfortunately, there’s not much to report back. Em terça-feira, 8 de junho de 2021, às 15:13:36 -03, Thiago Jung Bauermann escreveu: > Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu: > > Can you narrow down which specific firmware file causes the problem? > > Ok, I will try. I don’t think I can narrow down which firmware file causes the problem, because I don’t have a last known good version. All firmware files that I tested (Ubuntu versions 1.190.5, 1.197 and latest linux-firmware.git) immediately trigger the bug when I try the only reliable reproducer I know (i.e., running flatpak’s com.github.quaternion package). Since it can take several days for the bug to happen if I just use the machine normally, it would take weeks to narrow down which of the picasso_* files is more stable relative to the others. And even then, I wouldn’t be sure about it. > > I think it may be related to a change in mesa. Specifically mesa > > commit > > 820dec3f7c7. For more info see > > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 > > I’ll run with Mario’s build of Mesa with that patch backported. > Thanks, Mario! I’m running with the Mesa build from Mario’s PPA now. If I don’t see any issue within two weeks, I think it will be possible to say that the bug is gone, or at least much harder to hit. I can’t use my reproducer in this case, because I can’t change the Mesa version inside the flatpak image. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931715] [NEW] Notebook touchpad not working - does not appear on "cat /proc/bus/input/devices"
Public bug reported: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.8 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1931715/+attachment/5504104/+files/devices -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931715 Title: Notebook touchpad not working - does not appear on "cat /proc/bus/input/devices" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.8/+bug/1931715/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1598 https://gitlab.freedesktop.org/drm/amd/-/issues/1598 ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #920 https://gitlab.freedesktop.org/drm/amd/-/issues/920 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Thanks for your input. Em terça-feira, 8 de junho de 2021, às 10:30:24 -03, Alex Deucher escreveu: > Can you narrow down which specific firmware file causes the problem? Ok, I will try. Also, is it possible and/or worthwhile trying to bisect firmware versions from the linux-firmware repo? How coupled is the firmware with the kernel driver? E.g., can I try using firmware files from 1 year ago with current kernel and Mesa? > We haven't been able to repro this. One thing that’s a bit “fishy” about my machine is that it doesn’t seem to have a good clock: [0.211436] TSC synchronization [CPU#0 -> CPU#1]: [0.211436] Measured 3304683447 cycles TSC warp between CPUs, turning off TSC clock. [0.211436] tsc: Marking TSC unstable due to check_tsc_sync_source failed … [0.252117] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0 [0.252117] hpet0: 3 comparators, 32-bit 14.318180 MHz counter [0.253970] clocksource: Switched to clocksource hpet … [0.580451] Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line Could this bug be related to that? > I think it may be related to a change in mesa. Specifically mesa commit > 820dec3f7c7. For more info see > https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 I’ll run with Mario’s build of Mesa with that patch backported. Thanks, Mario! > ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #4866 >https://gitlab.freedesktop.org/mesa/mesa/-/issues/4866 Other upstream issues that look similar: https://gitlab.freedesktop.org/drm/amd/-/issues/1598 https://gitlab.freedesktop.org/drm/amd/-/issues/920 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em quarta-feira, 26 de maio de 2021, às 16:46:14 -03, Thiago Jung Bauermann escreveu: > But perhaps the upstream version is not too bad? I take this back. I've been running with the upstream picasso* files since Wednesday, and I just had two freezes in less than one hour. linux-firmware 1.190.5 is the only version which contains picasso* files that are stable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Over the weekend I was finally able to revert back to the previous versions of the org.freedesktop.Platform and org.freedesktop.Platform.GL.default flatpak runtimes. It turns out that the `flatpak history` command wasn't necessay for the rollback. Em sexta-feira, 14 de maio de 2021, às 13:14:22 -03, Seth Forshee escreveu: > Before we revert we should see if newer firmware fixes the issue, and > make sure we are only changing the specific firmware files for your > hardware. > > I think your hardware is the "Picasso" series. Can you try the > following? If you are unsure about any of the following steps, let me > know and I can provide you with test packages to install instead. > > Save all files matching /lib/firmware/amdgpu/picasso* from linux- > firmware 1.190.5. Reinstall 1.197, then overwrite the picasso firmware > files with the ones you saved. Reboot, and confirm that the issues you > see with 1.197 are fixed. If they are not fixed, then there's no need to > proceed as we haven't found the correct firmware files which are causing > your issues. I did that exactly that, and I was able to run for 4 days without any retry page fault error. This makes me confident that the 1.190.5 firmware doesn't have the bug, and also that the amdgpu/picasso* files are the relevant ones. > Then please download the picasso firmware files from here: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-> > firmware.git/tree/amdgpu > > Use the "plain" link next to each file to download the file. Overwrite > the files in /lib/firmware/admgpu with these files, reboot, and see if > you continue to have problems. I also did that, using the files from commit 55d964905a2b. More recent commits in that repo didn't touch the amdgpu directory so they're still the most recent firmware files for my hardware. Unfortunately I still saw the retry page fault message on dmesg with it, and very soon after boot (IIRC it happened while running the sddm login manager, before I log in). On the bright side, it didn't have any advert effect on my computer and I just noticed hours later because I specifically grepped for it. So perhaps the latest firmware has a less nasty version of the bug? And just to double-check the baseline reference, I also ran with pristine linux-firmware 1.197, the version which made my machine so unstable. I had a somewhat different experience this time. The bug still happened, but only after 20h of uptime. And the symptom was "just" a visual glitch while scrolling inside Firefox, not a complete freeze of the display and keyboard, as I was experiencing originally. Perhaps if I rebooted and insisted on using it again I would experience worse effects. But I thought that was enough to confirm that 1.197 is still bad. So I'm not sure what to make of all this. I still wasn't able to pinpoint exactly what triggers the worst manifestation of the bug. But of the three versions of linux-firmware I used (1.190.5, 1.197 and upstream), 1.197 is still the one where things are worse so IMHO the picasso files need to come from one of the other two versions. 1.190.5 is the rock solid one, so I think it's the safest bet. But perhaps the upstream version is not too bad? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908429] Re: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal conn
I'm having this problem on a machine that uses google chrome, the gnome calculator and a corporate software. It's vanilla Ubuntu 20.04. Syslog reaches 50g and the machine stops working (disk full). Exact same message as reported. Any way to stop the log until the problem is resolved? gnome-shell: 3.36.7-0ubuntu0.20.04.1 google-chrome-stable: 90.0.4430.93-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908429 Title: gnome-shell fills syslog: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. The offending callback was SourceFunc(). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1908429/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Em sábado, 15 de maio de 2021, às 11:24:17 -03, Thiago Jung Bauermann
escreveu:
> Unexpectedly, 1.197 is now reliable too! I have been running it for about
> half a day (which is more than what was possible before) and it is fine.
After 4 days of stability I just had the retry page fault problem again,
with stock linux-firmware 1.197 and kernel 5.11.0-17-generic.
> The only thing that changed was that flatpak's org.freedesktop.Platform
> and org.freedesktop.Platform.GL.default were updated, not sure if
> yesterday or the day before.
>
> This is relevant because I use Firefox from flathub.
>
> I'm suspecting that the instability comes from the combination of linux-
> firmware 1.197 + a particular version of some userspace component (Mesa I
> guess) that was in org.freedesktop.Platform{,.GL.default}.
So apparently the flatpak update made the problem less likely to happen,
but it still does.
> I'll try reverting the flatpak update to see if I can get back to the
> unstable state to confirm the hypothesis.
Life got in the way and I wasn't able to do this yet.
With it taking 4 days to reproduce the problem with the current stack, I
think it still makes sense to revert the flatpak update.
Unfortunately "flatpak history" seems to be broken on my system:
$ flatpak history
error: appstream2/x86_64 is not application or runtime
I'll try using ostree directly. I don't think I'll be able to do it today,
but hopefuly within the next couple of days.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928393
Title:
linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
retry page fault"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
The latest upstream firmware is stable, so I reverted back to 1.197 so that
I could test only the picasso* files.
Before doing that, I decided to run for a while with pristine linux-
firmware 1.197 to double-check that the bug happens quickly.
Unexpectedly, 1.197 is now reliable too! I have been running it for about
half a day (which is more than what was possible before) and it is fine.
The only thing that changed was that flatpak's org.freedesktop.Platform and
org.freedesktop.Platform.GL.default were updated, not sure if yesterday or
the day before.
This is relevant because I use Firefox from flathub.
I'm suspecting that the instability comes from the combination of linux-
firmware 1.197 + a particular version of some userspace component (Mesa I
guess) that was in org.freedesktop.Platform{,.GL.default}.
I'll try reverting the flatpak update to see if I can get back to the
unstable state to confirm the hypothesis.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1928393
Title:
linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
retry page fault"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Hello Seth, Thank you for the quick and detailed response. Em sexta-feira, 14 de maio de 2021, às 13:14:22 -03, Seth Forshee escreveu: > Before we revert we should see if newer firmware fixes the issue, and > make sure we are only changing the specific firmware files for your > hardware. Ok, sounds good. > I think your hardware is the "Picasso" series. Can you try the > following? If you are unsure about any of the following steps, let me > know and I can provide you with test packages to install instead. Thanks for the offer. It's not a problem getting the files from git and overwrite them manually. > Save all files matching /lib/firmware/amdgpu/picasso* from linux- > firmware 1.190.5. Reinstall 1.197, then overwrite the picasso firmware > files with the ones you saved. Reboot, and confirm that the issues you > see with 1.197 are fixed. If they are not fixed, then there's no need to > proceed as we haven't found the correct firmware files which are causing > your issues. Ah, ok. This morning I went ahead and overwrote the whole of /lib/firmware/ amdgpu/ with the files from the latest commit of the upstream linux- firmware git repo you mention below. It's been only a little over 2 hours, but my impression is that the latest firmware does solve the problem. If no retry page fault happens by the end of the day, then I think it's safe to say that it fixes the issue. So at the end of the day (or earlier if I get a retry page fault) I'll do the procedure you mention to use firmware 1.197 and only overwrite the picasso* files to confirm if those are the ones that need to be changed. I don't know much about GPUs, but from looking at Wikipedia¹ I think my model is a "Vega 10". Should I overwrite the vega10* files as well? ¹ https://en.wikipedia.org/wiki/Radeon_RX_Vega_series#Picasso_(2019)_2 > Then please download the picasso firmware files from here: > > https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-> firmware.git/tree/amdgpu > > Use the "plain" link next to each file to download the file. Overwrite > the files in /lib/firmware/admgpu with these files, reboot, and see if > you continue to have problems. > > ** Changed in: linux-firmware (Ubuntu) >Importance: Undecided => High Thanks! > > ** Changed in: linux-firmware (Ubuntu) >Status: New => Incomplete > > ** Changed in: linux-firmware (Ubuntu) > Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
This is the dmesg of an instance where I was able to continue using the laptop despite the GPU bug (in the case of the dmesg I attached previously, I had to ssh in to the machine to turn it off). Notice that there are two instances of the retry page fault, one of them right within 15 minutes of the machine being turned on. There was no suspend/resume event this time. The laptop was turned on the whole time. ** Attachment added: "This GPU bug didn't involve suspend/resume and didn't freeze the screen." https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+attachment/5497260/+files/dmesg-4-didnt-freeze-screen.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928393] [NEW] linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Public bug reported: After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent and severe GPU instability. When this happens, I see this error in dmesg: [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 pid 1236) [20061.061103] amdgpu :03:00.0: amdgpu: in page starting at address 0x80401000 from client 27 [20061.061135] amdgpu :03:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00101031 [20061.061147] amdgpu :03:00.0: amdgpu: Faulty UTCL2 client ID: TCP (0x8) [20061.061157] amdgpu :03:00.0: amdgpu: MORE_FAULTS: 0x1 [20061.061167] amdgpu :03:00.0: amdgpu: WALKER_ERROR: 0x0 [20061.061174] amdgpu :03:00.0: amdgpu: PERMISSION_FAULTS: 0x3 [20061.061183] amdgpu :03:00.0: amdgpu: MAPPING_ERROR: 0x0 [20061.061189] amdgpu :03:00.0: amdgpu: RW: 0x0 I'll attach a couple of full dmesgs that I collected. Many of the times when this happens, the screen and keyboard freeze irreversibly (I tried waiting for more than 30 minutes, but it doesn't help). I can still log in via ssh though. When there's no freeze, I can continue using the computer normally, but the laptop fans keep running are always running and the battery depletes fast. There's probably something on a permanent loop either in the kernel or in the GPU. This bug happens several times a day, rendering the machine so unstable as to be almost unusable. It is a severe regression and I'm aghast that it passed AMD's Quality Assurance. After downgrading back to linux-firmware 1.190.5, the machine is back to the previous, mostly-reliable state. Which is to say, this bug is gone, I'm just left with the other amdgpu suspend bug I've learned to live with since I bought this computer. Please revert the amdgpu firmware in this package as soon as possible. This is unbearable. Relevant information: Ubuntu version: 21.04 Linux kernel: 5.11.0-17-generic x86_64 CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Picasso (rev c1) Laptop model: Lenovo Ideapad S145 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Attachment added: "This GPU bug happened after the machine resumed from sleep." https://bugs.launchpad.net/bugs/1928393/+attachment/5497259/+files/dmesg-3.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1928393/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1928113] Re: Please enable firewalld support in libvirtd
Hello Christian, Thank you for your quick and thorough response! Em quarta-feira, 12 de maio de 2021 08:12:17 -03 você escreveu: > Hi Thiago, > the problem is that firewalld isn't in main and thereby not fully > supported which means that libvirt (that is in main) can not depend on > it - see [1] for some details. Ah, I wasn't aware of that. Thanks for pointing out. > Ubuntu's choice for this usually us UFW, but there is no UFW backend for > libvirt. I had a(n admittedly quick) look at UFW and I had the impression that it aimed for simpler use cases than firewalld, and wasn't sure it would meet my needs. This is why I went with firewalld. But perhaps it would have solved my use case, I don't know. > So the issue here is that today Ubuntus libvirt can't work with firewalld > installed. To be able to work we'd need to promote firewalld wich might > be unwanted for many other reasons. There might be a way in between if I > can manage to get firewalld support built-in in a way that has no > runtime dependency to firewalld from any of the packages in main. But I > can't promise this will work out. Yes, that would be awesome! > I'll give it a try when I merge the next libvirt version and if it fails > we need to reconsider getting firewalld promoted to main. Thank you! > If the latter > also would be refused we'd at least want to make it fail more gracefully > which might be tricky - e.g. a conflicts between libvirtd<->firewalld > won't help you at all and you could have valid use cases for both just > not everything would work. At least for me in particular, a conflicts would be worse than the current situation because I was able to get libvirt network going with the workaround I mentioned earlier. If all else fails, an alternative which would already help someone else in a similar situation is to change the error message that libvirt shows about firewalld to mention the workaround of adding a zone attribute to the bridge node in the network XML definition. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928113 Title: Please enable firewalld support in libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1928113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928113] Re: Please enable firewalld support in libvirtd
More information I should have mentioned earlier: The impact of this bug is that libvirt can't start the default network: bauermann@popigai:~$ virsh -c qemu:///system net-start default error: Failed to start network default error: internal error: firewalld is set to use the nftables backend, but the required firewalld 'libvirt' zone is missing. Either set the firewalld backend to 'iptables', or ensure that firewalld has a 'libvirt' zone by upgrading firewalld to a version supporting rule priorities (0.7.0+) and/or rebuilding libvirt with --with-firewalld-zone bauermann@popigai:~$ echo $? 1 The workaround is to add a zone="trusted" attribute to the bridge node of the network XML definition: default d20d5db0-4a01-4422-8bcb-8b582d019356 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928113 Title: Please enable firewalld support in libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1928113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1928113] [NEW] Please enable firewalld support in libvirtd
Public bug reported: I use the firewalld package to manage my firewall configuration. I just installed the libvirt-daemon set of packages (see below) and libvirtd registers this error in the journal: libvirtd[1063]: internal error: firewalld is set to use the nftables backend, but the required firewalld 'libvirt' zone is missing. Either set the firewalld backend to 'iptables', or ensure that firewalld has a 'libvirt' zone by upgrading firewalld to a version supporting rule priorities (0.7.0+) and/or rebuilding libvirt with --with-firewalld-zone Looking at the firewalld status there is indeed no 'libvirt' zone so the problem reported is real. As I understand it, the 'iptables' firewalld backend has been deprecated a couple of years ago in favor of the 'nftables' backend, so setting the backend to a deprecated one isn't a good solution. In the libvirt package's debian/rules I see: WITH_FIREWALLD= -Dfirewalld=disabled So firewalld support is indeed disabled in Ubuntu. Could you please enable it? This is on Ubuntu 21.04. Relevant package versions: firewalld0.9.3-2ubuntu1 libvirt-daemon 7.0.0-2ubuntu2 libvirt-daemon-config-network7.0.0-2ubuntu2 libvirt-daemon-config-nwfilter 7.0.0-2ubuntu2 libvirt-daemon-driver-qemu 7.0.0-2ubuntu2 libvirt-daemon-system7.0.0-2ubuntu2 libvirt-daemon-system-systemd7.0.0-2ubuntu2 ** Affects: libvirt (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/1928113 Title: Please enable firewalld support in libvirtd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1928113/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed
I'm thinking about this.. Maybe, this is by design! Right? The way it's today, the options used during the Packer builds, for example, don't end up on the image! Sounds like a good idea actually. Gonna take a look at "debian-installer/add-kernel-opts"! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581796 Title: grub-installer ignores grub2/linux_cmdline_default in preseed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 581796] Re: grub-installer ignores grub2/linux_cmdline_default in preseed
I was so annoyed that my "presseded" installations of Ubuntu 20.04 Legacy ISO Server with Packer were ending up with a black screen that only "ALT + Arrow Right" was bringing the `tty1` back to life... Then, I realized that the "Packer builds were adding" the "quiet splash" to the /etc/default/grub file, no matter what I did to pressed regular options, and this problem brought me to this... 11 years old bug report!!! Wht?! So, the workaround proposed on comment #1 worked like a charm, and finally, my Packer builds produces awesome server images with a nice verbose boot that goes straight to tty1! It looks like that won't be fixed since Canonical is moving to the new subiquity, Cloud-Init based `autoinstall`. Kinda sad. I don't like the new "Live Server" install media, legacy is way, way better. Thank you Mathieu! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/581796 Title: grub-installer ignores grub2/linux_cmdline_default in preseed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/581796/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1922081] Re: best-place-to-buy-pain-relief-tablet
** Package changed: ubuntu => null-and-void ** Changed in: null-and-void Status: New => Invalid ** Information type changed from Public to Private Security -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1922081 Title: best-place-to-buy-pain-relief-tablet To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/1922081/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1842417] Re: Ubiquity needs support for fscrypt
I do want home-based encryption but, what about the new `systemd-homed`? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1842417 Title: Ubiquity needs support for fscrypt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1842417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1882993] Re: Package needs newer version with v2 encryption policy
I can't wait for it! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882993 Title: Package needs newer version with v2 encryption policy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1882993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
*** This bug is a duplicate of bug 1877109 *** https://bugs.launchpad.net/bugs/1877109 Here it worked, editing the file "~/snap/opera/105/.config/fontconfig" /home/thiago/.XXX conf.d /snap/opera/105/gnome-platform/etc/fonts/fonts.conf fontconfig /var/snap/opera/common/fontconfig or delete the ".fonts" folder from the home. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command
I totally agree with this! The Additional Drivers doesn't work if your Netplan uses rendered: networked. Then, the command line is useless too... How does it work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818746 Title: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818746] Re: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command
Never mind... Just `ubuntu-drivers install` did the trick.. LOL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818746 Title: `ubuntu-drivers list` output doesn't bear any relation to the input to the install command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818746/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages
Never mind... Just `ubuntu-drivers install` did the trick.. LOL -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818749 Title: `ubuntu-drivers install --gpgpu` could have more informative error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1818749] Re: `ubuntu-drivers install --gpgpu` could have more informative error messages
I totally agree with this! The Additional Drivers doesn't work if your Netplan uses rendered: networked. Then, the command line is useless too... How does it work? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1818749 Title: `ubuntu-drivers install --gpgpu` could have more informative error messages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1818749/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
I actually changed the value os `os_distro` from just "coreos" to "fedora-coreos" and it worked! I mean, I'm not seeing this error anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1902293] Re: fixed_network_name still exists in drivers except heat
I'm facing the very same problem with OpenStack Ansible, branch `stable/ussuri`, on Ubuntu 20.04.1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1902293 Title: fixed_network_name still exists in drivers except heat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/magnum/+bug/1902293/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks
I found the quick "fix"... "Double check that `security_driver = "none"` is uncommented in `/etc/libvirt/qemu.conf` and issue `sudo systemctl restart libvirt-bin` to restart the daemon." https://github.com/dmacvicar/terraform-provider-libvirt/commit/22f096d9 Doesn't sound good. But it worked! lol -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1677398 Title: Apparmor prevents using storage pools and hostdev networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1677398] Re: Apparmor prevents using storage pools and hostdev networks
Hey guys,
I'm trying to play with Terraform and it's failing too! Ubuntu 20.04.1.
Guide:
https://fabianlee.org/2020/02/22/kvm-terraform-and-cloud-init-to-create-
local-kvm-resources/
NOTE: I'm using the latest "terraform-provider-libvirt-0.6.3" binary for
Ubuntu 20.04.
The "terraform apply" fails with:
Error: Error creating libvirt domain: virError(Code=1, Domain=10,
Message='internal error: process exited while connecting to monitor:
2020-11-17T01:55:34.375538Z qemu-system-x86_64: -blockdev
{"driver":"file","filename":"/var/lib/libvirt/images/simple-os_image
","node-name":"libvirt-2-storage","auto-read-
only":true,"discard":"unmap"}: Could not open '/var/lib/libvirt/images
/simple-os_image': Permission denied')
The generated XML looks just like the one from comment #39!
As you guys can see, the path is "normal". The file permissions are
accessible to Libvirt users/groups. The QEMU host is working normally
with virt-manager.
Any quick fix!?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1677398
Title:
Apparmor prevents using storage pools and hostdev networks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1677398/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903800] [NEW] nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build
Public bug reported: It showed a problem and I was setted to this page. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.4.0-53-generic Date: Wed Nov 11 01:38:52 2020 InstallationDate: Installed on 2020-10-15 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageVersion: 450.80.02-0ubuntu0.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903800 Title: nvidia-dkms-450 450.80.02-0ubuntu0.20.04.2: nvidia kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-450/+bug/1903800/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1868587] Re: Module 'pg_autoscaler' has failed: division by zero
I'm seeing this on the latest Ubuntu 20.04.1, fully upgraded. Ceph version 15.2.3-0ubuntu0.20.04.2. The `ceph status` is "HEALTH_ERR", Module 'pg_autoscaler' has failed: division by zero, 1 daemons have recently crashed. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1868587 Title: Module 'pg_autoscaler' has failed: division by zero To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1868587/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903370] Re: Error: Failed to use network worked after reboot.
** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903370 Title: Error: Failed to use network worked after reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1903370/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)
Never mind! Found it at https://images.linuxcontainers.org! No more snapd!! Wheee!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878674 Title: apt purge snapd fails in LXD (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)
Thanks Johan! But this procedure failed too. I'll try the images without snapd! But, currently, I'm using an image called just "focal", which comes with this creepy snapd. I can't find an image called "ubuntu/focal/cloud"... Which source are you using for your images? I'm using "https://cloud- images.ubuntu.com/releases" simplestreams. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878674 Title: apt purge snapd fails in LXD (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly
Any news about this?! The vim is still very bad on Ubuntu 20.04. Any recommendation for a better /etc/vim/* ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767314 Title: Ubuntu Bionic vi/vim not working correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1767314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878674] Re: apt purge snapd fails in LXD (on amd64)
I can also confirm this too! Here is a list of problems that I'm seeing with snap inside LXD containers: https://askubuntu.com/questions/1288779/the-snapd-package-fails-to- upgrade-inside-of-ubuntu-20-04-lxd-container At first, "apt update ; apt full-upgrade" fails... Then, I thought, let's remove this `snapd` thing. Nop, doesn't work either! Here is the error when I try `apt remove --purge snapd` inside of an LXD Container: https://pastebin.com/TTj4Z4Jp Johan, do you mind sharing how are you removing snapd out from your containers? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878674 Title: apt purge snapd fails in LXD (on amd64) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1878674/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected
I have Nvidia card and this error happened after marking the option to install 3rd party drivers. Once before I installed without 3rd party drivers and I could finish the installation after boot but nothing happened after I can`t even open the tty to try solve the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871268 Title: Installation fails when "Install Third-Party Drivers" is selected To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/1871268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 @dgoosens I updated my kernel to 5.6.10-050610-generic but still 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/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[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 Same issue here. Ubuntu 20.04 LTS and Ubuntu 18.04 LTS JBL Reflect Flow Dell Latitude 3400 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878194 Title: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893511] [NEW] espeak cannot find voice file for mbrola-br2
Public bug reported: I tried to use the package mbrola-br2 with espeak, but it seems like it is not working properly. Trying the command: espeak -s 100 -v 'mb-br2' teste ... results in the following error message: Failed to read voice 'mb-br2' There are other 3 packages for brazilian portuguese voices: mbrola-br1, mbrola-br3 and mbrola-br4, and all the others are working just fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mbrola-br2 2.021+repack2-4 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 CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 11:56:30 2020 InstallationDate: Installed on 2020-08-03 (25 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: mbrola-br2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mbrola-br2 (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/1893511 Title: espeak cannot find voice file for mbrola-br2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mbrola-br2/+bug/1893511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891811] [NEW] doesnt recognize the trackpad
Public bug reported: cat /proc/bus/input/devices doesnt show touchpad ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 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.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thiago 1569 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 16 13:41:16 2020 InstallationDate: Installed on 2020-08-15 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp1s0f0 no wireless extensions. usb0 no wireless extensions. lono wireless extensions. MachineType: Apple Inc. Macmini6,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=d1b99b69-6ce5-4c95-80ca-69c1e70dff35 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 286.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-031AEE4D24BFF0B1 dmi.board.vendor: Apple Inc. dmi.board.version: Macmini6,1 dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-031AEE4D24BFF0B1 dmi.modalias: dmi:bvnAppleInc.:bvr286.0.0.0.0:bd06/10/2020:svnAppleInc.:pnMacmini6,1:pvr1.0:rvnAppleInc.:rnMac-031AEE4D24BFF0B1:rvrMacmini6,1:cvnAppleInc.:ct16:cvrMac-031AEE4D24BFF0B1: dmi.product.family: Macmini dmi.product.name: Macmini6,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (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/1891811 Title: doesnt recognize the trackpad To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891811/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1891245] Re: In 20.04.1 all gtk2 apps starts 25 seconds
Not a bug in Launchpad itself. Moving it to Ubuntu. ** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1891245 Title: In 20.04.1 all gtk2 apps starts 25 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1891245/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)
** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886215 Title: Strange Apple keyboard behaviour (Spanish layout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1886215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1884353] Re: Ubuntu 20.04 partial upgrade failure
** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1884353 Title: Ubuntu 20.04 partial upgrade failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1884353/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1853369] Re: [19.10] Boot hangs at "loading initial ramdisk"
same problem with my dell, only work in 16.04 04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853369 Title: [19.10] Boot hangs at "loading initial ramdisk" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1853369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879691] Re: docker cannot read disk, after last kernel update
** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879691 Title: docker cannot read disk, after last kernel update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1879691/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1879385] Re: Unable to star files and folders in Dropbox folder in Ubuntu 20.04
** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1879385 Title: Unable to star files and folders in Dropbox folder in Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1879385/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878238] Re: performing an update fails in ubuntu 20.04
Moving it to Ubuntu distribution, rather than Launchpad. ** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1878238 Title: performing an update fails in ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1878238/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877428] Re: Graphical glitches
Moving this bug to Ubuntu distribution. ** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877428 Title: Graphical glitches To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1877428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874873] Re: Please cleanup obsolete signed artefacts from the archive
Sending this to Ubuntu distribution, instead of Launchpad project. ** Project changed: launchpad => ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874873 Title: Please cleanup obsolete signed artefacts from the archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1874873/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873103] [NEW] The hugepages package isn't available on Focal repos anymore
Public bug reported: Hello, Since a few weeks ago, the hugepages packages isn't available from Focal repositories anymore! --- root@focal-1:~# apt install hugepages Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package hugepages --- This was working before! It looks like that it must be recompiled against libhugetlbfs0-2.22-1! Thanks! Thiago ** Affects: libhugetlbfs (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/1873103 Title: The hugepages package isn't available on Focal repos anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhugetlbfs/+bug/1873103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Maybe related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1766857 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
This is also happening on bare-metal machines as well! It starts to happen after installing the "linux-cloud-tools-generic- hwe-18.04" package. Also, Ubuntu 20.04 has the same problem. 20.04 slow boot stops for 1:30 min heree: --- A start job is running for /sys/dev…misc/vmbus!hv_kvp (13s / 1min 30s) --- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867142] [NEW] bluetooth device does not apear in lsusb or lspci
Public bug reported: Not able to pair a bluetooth device in ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ilegra0247 1514 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:51:26 2020 InstallationDate: Installed on 2020-01-29 (42 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e65185c6-9a25-4b6e-aac1-efe7e6330450 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0T0MC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/11/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0T0MC0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867142 Title: bluetooth device does not apear in lsusb or lspci To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867142/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Terry, Ubuntu 18.04.4 with Kernel 5.3.0-40-generic, running on QEMU, takes more than 1:30 minutes to boot, it stops here for a while: --- [ *] A start job is running for sys-devi…\x21hv_kvp.device (51s / 1min 30s) --- I'm using the following image to build my QEMU VMs: http://uec-images.ubuntu.com/releases/18.04/release/ubuntu-18.04-server- cloudimg-amd64.img Cheers! Thiago -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
I'm seeing this problem with Ubuntu 18.04.4 with HWE Kernel, fully upgraded. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
4.15.0-54-generic did work great in the past we moved to 5.3.0-28-generic and this bug is notable... funny enough one of our machines was able to recover... both have the very same OS version Distributor ID: Ubuntu Description:Ubuntu 18.04.4 LTS Release:18.04 Codename: bionic 5.3.0-28-generic maybe a downgrade de to Ubuntu 18.04.2 is a "solution" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
4.15.0-54-generic is bug free 5.3.0-28-generic has the bug funny enough one of our machines was able to recover... both have the very same OS version Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic 5.3.0-28-generic maybe a downgrade de to Ubuntu 18.04.2 is a "solution" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
hey guys, we create our namespace using ip netns add. Each nameSpace has it's ipv6 and ipv4. We notice that the ipv6 ping continues to report, but the namespace at /run/netns does not exist anymore. is it possible to find the namespace using the ipv6 info? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711407 Title: unregister_netdevice: waiting for lo to become free To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
(In reply to Harald Sitter from comment #7)
> Thanks.
>
> With that in mind we cannot really support spaces while also following the
> smb URI format [1]. I suppose we'll just have to deviate a bit iff the
> workgroup name contains a space by using a variant of the notation that
> stuffs the workgroup into the userinfo `smb://work group;@/` and then
> translate that back to an smb URI for libsmbclient again. Means the urls
> wont be portable but at least navigation within our tech works.
>
> [1] https://www.iana.org/assignments/uri-schemes/prov/smb
You may need the user info for the actual user name that is being used
to search that work group. I would recommend using the path or query
component instead:
smb://userwg;user:password@/browsed_workgroup
smb://userwg;user:password@/?=search=browsed_workgroup
This searches the workgroup named "browsed_workgroup" with the user
"userwg\user".
The query has the added benefit a server inside the workgroup is a
proper sub-URL:
smb://userwg;user:password@server/share/folder/file.txt?search=browsed_workgroup
That is,
QUrl wg("smb://user@/?search=WG");
QUrl relative("/share/folder/file.txt");
qDebug() << wg.resolved(relative); //
"smb://user@/share/folder/file.txt?search=WG"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/340106
Title:
Dolphin & Konqueror do not support browsing workgroups with spaces in
their name
To manage notifications about this bug go to:
https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 340106]
QUrl's behaviour is intentional. The hostname component of the URL has to be a valid hostname. Do not store anything in that component that is not a hostname. Like a workgroup name. Store that elsewhere. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/340106 Title: Dolphin & Konqueror do not support browsing workgroups with spaces in their name To manage notifications about this bug go to: https://bugs.launchpad.net/kde-baseapps/+bug/340106/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849720] Re: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0)
Hi I've faced a similar problem on Debian. My system is a Ryzen 1700 and I use windows and OSX VMs for work, and after I upgraded to Debian 10 I started getting random host freezes some time after booting the VMs. Strangely, I have a linux VM with almost identical config as the Windows 10 one and it doesn't cause a host crash. Since my processor is a rather troublesome one (I had hardware bugs in the past, which were worked around in the kernel), I assumed this to be another such case, especially since the bug didn't occur if I disabled SMT on the BIOS. However, since my system was very stable under Debian 9, I spent quite a few hours trying to root out what change could have cause it, and at least in my specific case (which I'm not sure is the same reported here), was traced back to a certain libvirt commit, more specifically this one: https://github.com/libvirt/libvirt/commit/3527f9dde67460e9f2d50ce52b8dade8c0848e86 So a suggestion to anyone affected: try to explicitly disable seccomp by setting `seccomp_sandbox = 0` in /etc/libvirt/qemu.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849720 Title: KVM with e1000e and WinGuest Host OS on kernel 5.3 (ok with 5.0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847228] Re: Installer crashes at partitioning stage
The ZFS option crashed the installer, I'll try again today! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847228 Title: Installer crashes at partitioning stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1847228/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813662] Re: Cannot build VM
I'm creating a file:
/etc/kernel/postinst.d/fix-damn-bug-759725 with:
---
#/bin/sh
# https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725
set -e
version="$1"
if [ -z "$version" ]; then
exit 0
fi
exec dpkg-statoverride --update --add root root 0644 "/boot/vmlinuz-${version}"
---
As a workaround to BUG 759725 that MUST be fixed by Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813662
Title:
Cannot build VM
To manage notifications about this bug go to:
https://bugs.launchpad.net/libguestfs/+bug/1813662/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813662] Re: Cannot build VM
BUG https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725 is super, ultra annoying and useless! :-@ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813662 Title: Cannot build VM To manage notifications about this bug go to: https://bugs.launchpad.net/libguestfs/+bug/1813662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 759725] Re: The kernel is no longer readable by non-root users
ROLL BACK THIS DAMN CHANGE!!! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760068] Re: Wrong resolution at unlock screen
I solved it in Desktop Settings, by changing the Window Manager from "Xfwm4 + Compositing" to "Compiz". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760068 Title: Wrong resolution at unlock screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1760068/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1771185] Re: Secondary monitor not connecting in 18.04 LTS
I have similar problem. imac 27" with Ubuntu 18.04 LTS, 4.18.0-25-generic Thunderbolt display VGA compatible controller: NVIDIA Corporation GK104M [GeForce GTX 775M Mac Edition] (rev a1) Sometimes, after logging in, both screens are on. After shutdown, the second screen sometimes is off. Then, I have to restart and it could or couldn't work. Looks like random behavior. It would be good to have the second screen on since the boot startup. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771185 Title: Secondary monitor not connecting in 18.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1771185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)
Hey guys! This is an awesome version of QEMU and I can use Virgil 3D (vGPU within QEMU Guests works ok) with the native Linux `radeon` driver. However, if I try to install the AMDGPU-19.03 drivers, it completely breaks QEMU! AMDGPU-19.30: https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-navi- linux It breaks QEMU on Ubuntu 18.04.2 + Stein UCA Repo!!! I also tried the previous AMDGPU versions, same results. Here is the error after installing amdgpu: https://paste.ubuntu.com/p/35Mtqrsd3n/ How to repeat: Here is what I do: 1- Install Ubuntu 18.04.2 (with HWE for Kernel and XOrg); 2- Enable UCA with `sudo add-apt-repository cloud-archive:stein`; 3- Install `qemu-vkm`, `virt-manager`, and etc; 4- You'll be able to create a QEMU Guest using Virgil 3D using the Linux `radeon` module! It's awesome. 5- Install AMDGPU-19.30 (or any other previous version), for an even more awesome QEMU? Let's see! 6- No deal, after installing AMDGPU drivers, no more QEMU! Any idea about how to fix this? Is this an amdgpu limitation? Any idea if QMEU with Virgil 3D with it someday (or this isn't in the master plan)? Cheers! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540692 Title: Enable the VirtIO GPU 3D (Virgil) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1575053] Re: Please move the "$HOME/snap" directory to a less obtrusive location
Purged snap until it's fixed! Snap seems to be a great idea but I don't want it trash my home. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1575053 Title: Please move the "$HOME/snap" directory to a less obtrusive location To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1575053/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540692] Re: Enable the VirtIO GPU 3D (Virgil)
Unfortunately, the text console is just black. But both Ubuntu desktops are working! The regular one, and the one based on "Wayland". Which is huge anyway! Any idea about how to fix the text-only black console? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540692 Title: Enable the VirtIO GPU 3D (Virgil) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1540692/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
