[Bug 2041094] Re: application doesn't show its proper icon and name under the dock
This bug was not solved under 23.10 and now it appears in a LTS release come on guys ! and why it is not yet assigned to anyone ??? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041094 Title: application doesn't show its proper icon and name under the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2041094] Re: application doesn't show its proper icon and name under the dock
Why it is not yet solved ? I am on 24.04 LTS Beta and Transmission icon in the dock is not showing correctly ! It is just a gear look a like icon instead of the real Transmission icon !? If Ubuntu wants to gain market share, and users also , this kind of bug should not be there ! ** Attachment added: "Transmission not showing the right icon" https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+attachment/5766885/+files/Capture%20d%E2%80%99%C3%A9cran%20du%202024-04-17%2014-04-18.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2041094 Title: application doesn't show its proper icon and name under the dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/2041094/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2060578] Re: postfix installed during release upgrade to Noble
I went ahead with the postfix installation anyways but when my upgrade is going to be finished how do I remove all of this package ? Complete removal of postfix , how to do it ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2060578 Title: postfix installed during release upgrade to Noble To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2060578/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589669/+files/acpidump.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589667/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589668/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589666/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589665/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589664/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589663/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589660/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589661/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1973378/+attachment/5589662/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1973378 Title: kernel BUG in pci_assign_unassigned_bus_resources To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973378/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1973378] Re: kernel BUG in pci_assign_unassigned_bus_resources
apport information ** Tags added: apport-collected ** Description changed: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro + --- + ProblemType: Bug + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 May 13 14:05 seq + crw-rw 1 root audio 116, 33 May 13 14:05 timer + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.18 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CasperMD5CheckMismatches: ./boot/grub/efi.img + CasperMD5CheckResult: fail + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-14 (241 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd + Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Lsusb-t: + /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M + |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M + |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M + |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M + MachineType: Supermicro SYS-6019U-TR4 + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + LC_CTYPE=C.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash + ProcFB: 0 astdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic
[Bug 1973378] [NEW] kernel BUG in pci_assign_unassigned_bus_resources
Public bug reported: Tried to re-enumerate the device doing: # echo 1 > /sys/bus/pci/devices/\:d8\:00.2/remove # echo "1" > /sys/bus/pci/rescan ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-64-generic 5.4.0-64.72 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 13:58 seq crw-rw 1 root audio 116, 33 May 13 13:58 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Fri May 13 14:04:51 2022 InstallationDate: Installed on 2021-04-01 (407 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A linux-firmware1.187.10 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11DPU dmi.board.vendor: Supermicro dmi.board.version: 1.10 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd10/30/2020:svnSupermicro:pnSYS-6019U-TR4:pvr0123456789:rvnSupermicro:rnX11DPU:rvr1.10:cvnSupermicro:ct1:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: SYS-6019U-TR4 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 14:05 seq crw-rw 1 root audio 116, 33 May 13 14:05 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckMismatches: ./boot/grub/efi.img CasperMD5CheckResult: fail DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-14 (241 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 7: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 1: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: Supermicro SYS-6019U-TR4 Package: linux (not installed) PciMultimedia: ProcEnviron: LC_CTYPE=C.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-64-generic root=/dev/mapper/ubuntu--vg-ubuntu--lv ro console=tty0 console=ttyS0,115200n8 intel_iommu=on iommu=pt maybe-ubiquity ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-64-generic N/A linux-backports-modules-5.4.0-64-generic N/A
[Bug 1971545] Re: r.mimeType undefined ubuntu 22.04
Bug was fixed upstream. https://gitlab.gnome.org/GNOME/sushi/-/merge_requests/31 Could we get an update ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971545 Title: r.mimeType undefined ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1971545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1971545] [NEW] r.mimeType undefined ubuntu 22.04
Public bug reported: "r.mimeType undefined" error when previewing some files and folders in ubuntu 22.04, gnome-sushi 41.1-1 I found a filed bug upstream but I am putting it here as well to track it. Upstream bug: https://gitlab.gnome.org/GNOME/sushi/-/issues/80 ** Affects: gnome-sushi (Ubuntu) Importance: Undecided Status: New ** Description changed: "r.mimeType undefined" error when previewing some files and folders There was already a bug filed upstream, but I am putting it here as well to track it. + + Upstream bug: https://gitlab.gnome.org/GNOME/sushi/-/issues/80 ** Description changed: - "r.mimeType undefined" error when previewing some files and folders + "r.mimeType undefined" error when previewing some files and folders in + ubuntu 22.04, gnome-sushi 41.1-1 There was already a bug filed upstream, but I am putting it here as well to track it. Upstream bug: https://gitlab.gnome.org/GNOME/sushi/-/issues/80 ** Summary changed: - r.mimeType undefined + r.mimeType undefined ubuntu 22.04 ** Description changed: "r.mimeType undefined" error when previewing some files and folders in ubuntu 22.04, gnome-sushi 41.1-1 - There was already a bug filed upstream, but I am putting it here as well - to track it. + I found a filed bug upstream but I am putting it here as well to track + it. Upstream bug: https://gitlab.gnome.org/GNOME/sushi/-/issues/80 ** Bug watch added: gitlab.gnome.org/GNOME/sushi/-/issues #80 https://gitlab.gnome.org/GNOME/sushi/-/issues/80 ** Also affects: gnome-sushi via https://gitlab.gnome.org/GNOME/sushi/-/issues/80 Importance: Unknown Status: Unknown ** No longer affects: gnome-sushi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1971545 Title: r.mimeType undefined ubuntu 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sushi/+bug/1971545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968394] Re: No icons on desktop
Found the culprit. The schemas are correctly installed in /usr/share/glib-2.0/schemas/org.gnome.shell.extensions.ding.gschema.xml but I also have a previous config in ~/.local/share/glib-2.0/schemas/org.gnome.shell.extensions.ding.gschema.xml Simply deleting ~/.local/share/glib-2.0/schemas solves 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/1968394 Title: No icons on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1968394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1968394] Re: No icons on desktop
Same issue here. This is the detailed error information when I open the settings of the extension: The settings of extension d...@rastersoft.com had an error: ``` Error: GSettings key use-nemo not found in schema org.gnome.shell.extensions.ding ``` Stack trace: ``` _checkKey@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:580:23 createCheckedMethod/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:532:30 buildSwitcher@/usr/share/gnome-shell/extensions/d...@rastersoft.com/prefswindow.js:117:54 preferencesFrame@/usr/share/gnome-shell/extensions/d...@rastersoft.com/prefswindow.js:61:15 buildPrefsWidget@/usr/share/gnome-shell/extensions/d...@rastersoft.com/prefs.js:54:29 _init@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:32:44 ExtensionPrefsDialog@resource:///org/gnome/Shell/Extensions/js/extensionPrefsDialog.js:10:4 OpenExtensionPrefsAsync/<@resource:///org/gnome/Shell/Extensions/js/extensionsService.js:129:33 asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:115:22 run@resource:///org/gnome/Shell/Extensions/js/dbusService.js:186:20 main@resource:///org/gnome/Shell/Extensions/js/main.js:22:13 run@resource:///org/gnome/gjs/modules/script/package.js:206:19 start@resource:///org/gnome/gjs/modules/script/package.js:190:8 @/usr/share/gnome-shell/org.gnome.Shell.Extensions:1:17 ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1968394 Title: No icons on desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/1968394/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] Re: awk warnings running prometheus-node-exporter-apt.service
** Description changed: + [Impact] + This bug has minimal impact to users. Warnings are being thrown by the service in its journal; but that seems to be the only issue -- valid results are still being returned by the prometheus collector in the number of packages that need updates for each repository; along with node_reboot_required. + + The bug fix is to clean up the regex to avoid the warnings. + + [Test Plan] + 1) Run /usr/share/prometheus-node-exporter-collectors/apt.sh + 2) Validate that it returns without awk warnings. + + [Where problems could occur] + - An invalid regex might cause repository stats to be returned in the wrong format for parsing by prometheus. + - Invalid regex would still show warnings or errors in awk. + + --- + Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [Impact] This bug has minimal impact to users. Warnings are being thrown by the service in its journal; but that seems to be the only issue -- valid results are still being returned by the prometheus collector in the number of packages that need updates for each repository; along with node_reboot_required. The bug fix is to clean up the regex to avoid the warnings. + This is not applicable elsewhere than in focal; later releases have + stopped installing the service and associated script. + [Test Plan] 1) Run /usr/share/prometheus-node-exporter-collectors/apt.sh 2) Validate that it returns without awk warnings. - [Where problems could occur] + [Where problems could occur] - An invalid regex might cause repository stats to be returned in the wrong format for parsing by prometheus. - Invalid regex would still show warnings or errors in awk. --- Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Changed in: prometheus-node-exporter (Ubuntu) Status: New => Fix Released ** Also affects: prometheus-node-exporter (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: prometheus-node-exporter (Ubuntu Focal) Status: New => Triaged ** Changed in: prometheus-node-exporter (Ubuntu Focal) Importance: Undecided => Low ** Changed in: prometheus-node-exporter (Ubuntu Focal) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions
[Bug 1970422] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583973/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583972/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583971/+files/HookError_ubuntu.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1970422/+attachment/5583970/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1970422] [NEW] awk warnings running prometheus-node-exporter-apt.service
Public bug reported: Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-12-06 (140 days ago) InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) Package: prometheus-node-exporter 0.18.1+ds-2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Tags: focal Uname: Linux 5.4.0-96-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True modified.conffile..etc.cron.daily.apport: [deleted] ** Affects: prometheus-node-exporter (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected focal ** Tags added: apport-collected focal ** Description changed: Every time the prometheus-node-exporter-apt.service service runs; it comes out with awk warnings; the regex used is understood but misparsed: Apr 25 12:06:25 s8mtl1-srs1-prd systemd[1]: Starting Collect apt metrics for prometheus-node-exporter... Apr 25 12:06:25 s8mtl1-srs1-prd bash[1887195]: awk: cmd. line:1: warning: regexp escape sequence `\"' is not a known regexp operator Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: prometheus-node-exporter-apt.service: Succeeded. Apr 25 12:06:29 s8mtl1-srs1-prd systemd[1]: Finished Collect apt metrics for prometheus-node-exporter. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.21 + Architecture: amd64 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-12-06 (140 days ago) + InstallationMedia: Ubuntu-Server 20.04.3 LTS "Focal Fossa" - Release amd64 (20210824) + Package: prometheus-node-exporter 0.18.1+ds-2 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 + Tags: focal + Uname: Linux 5.4.0-96-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1970422 Title: awk warnings running prometheus-node-exporter-apt.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/prometheus-node-exporter/+bug/1970422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Same here with tigerlake on 22.04 freshly updated, with both `intel- media-va-driver` and `intel-media-va-driver-non-free`. Rebuilding `intel-media-va-driver` locally and installing that works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967474] [NEW] Thinkpad X1 Carbon Gen 9 waking up during sleep
Public bug reported: This is apparently caused by "ACPI: PM: s2idle: Cancel wakeup before dispatching EC GPE" which has been reverted in recent kernels (https://www.spinics.net/lists/kernel/msg4274673.html) would be nice to have it reverted here too. ** Affects: linux-oem-5.14 (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/1967474 Title: Thinkpad X1 Carbon Gen 9 waking up during sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1967474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
From https://github.com/intel/media-driver/issues/1366 it looks like a regression with intel-media-va-driver 22.x ** Also affects: intel-media-driver (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/intel/media-driver/issues #1366 https://github.com/intel/media-driver/issues/1366 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-media-driver/+bug/1966571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966571] Re: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed
Not sure if this is filed under the right package (is this a driver/kernel issue ?), but I can reproduce with Intel TigerLake-LP GT2 hardware - it used to work from Ubuntu 20.04 to 21.10, and fails with 22.04 alpha, even from the Live 20220326 ISO. vainfo shows the same thing as original post: libva info: VA-API version 1.14.0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so libva info: Found init function __vaDriverInit_1_14 libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed libva info: va_openDriver() returns 1 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_10 libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed libva info: va_openDriver() returns -1 vaInitialize failed with error code -1 (unknown libva error),exit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966571 Title: libva error: /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so init failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1966571/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore
** Also affects: liferea (Ubuntu) Importance: Undecided Status: New ** Also affects: epiphany-browser (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/1966418 Title: [jammy regression] Evolution does not display message content anymore To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1966418/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964930] Re: Failed to start flatpak document portal service.
I found the culprit, being a 0 byte "documents" file in the flatpak database. I filed an issue in the flatpak github. https://github.com/flatpak/xdg-desktop- portal/issues/369#issuecomment-1068915444 I still don't know if this relates to libxml2, and if it is worth being investigated how that 0 byte file was created. Thanks for reading. ** Bug watch added: github.com/flatpak/xdg-desktop-portal/issues #369 https://github.com/flatpak/xdg-desktop-portal/issues/369 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1964930 Title: Failed to start flatpak document portal service. To manage notifications about this bug go to: https://bugs.launchpad.net/libxml2/+bug/1964930/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1964930] Re: Failed to start flatpak document portal service.
** Bug watch added: github.com/flatpak/xdg-desktop-portal-gtk/issues #107 https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107 ** Also affects: systemd via https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107 Importance: Unknown Status: Unknown ** Project changed: systemd => libxml2 ** Package changed: systemd (Ubuntu) => libxml2 (Ubuntu) ** No longer affects: libxml2 ** Description changed: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. - All my flatpak apps boot a lot slower than usual. + All my flatpak apps boot a lot slower than usual. + + This bug happened with the recent update to libxml2 (one or two days ago ?). + This is not the first time it happened. See: + https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 + + I don't know where to report this, if this is relates to ubuntu or to + the flatpak project. Thanks for looking into this ! + Description: Ubuntu 21.10 Release: 21.10 libxml2: - Installed: 2.9.12+dfsg-4ubuntu0.1 - Candidate: 2.9.12+dfsg-4ubuntu0.1 - Version table: - *** 2.9.12+dfsg-4ubuntu0.1 500 - 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages - 100 /var/lib/dpkg/status - 2.9.12+dfsg-4 500 - 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages + Installed: 2.9.12+dfsg-4ubuntu0.1 + Candidate: 2.9.12+dfsg-4ubuntu0.1 + Version table: + *** 2.9.12+dfsg-4ubuntu0.1 500 + 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages + 100 /var/lib/dpkg/status + 2.9.12+dfsg-4 500 + 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: - Installed: 1.10.2-3ubuntu0.1 - Candidate: 1.10.2-3ubuntu0.1 - Version table: - *** 1.10.2-3ubuntu0.1 500 - 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages - 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages - 100 /var/lib/dpkg/status - 1.10.2-3 500 - 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages - + Installed: 1.10.2-3ubuntu0.1 + Candidate: 1.10.2-3ubuntu0.1 + Version table: + *** 1.10.2-3ubuntu0.1 500 + 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages + 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages + 100 /var/lib/dpkg/status + 1.10.2-3 500 + 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: - Installed: 248.3-1ubuntu8.2 - Candidate: 248.3-1ubuntu8.2 - Version table: - *** 248.3-1ubuntu8.2 500 - 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages - 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages - 100 /var/lib/dpkg/status - 248.3-1ubuntu8 500 - 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages - + Installed: 248.3-1ubuntu8.2 + Candidate: 248.3-1ubuntu8.2 + Version table: + *** 248.3-1ubuntu8.2 500 + 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages + 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages + 100 /var/lib/dpkg/status + 248.3-1ubuntu8 500 + 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.3
[Bug 1964930] [NEW] Failed to start flatpak document portal service.
Public bug reported: Bug desciption: when launching the Calendar app (flatpak version) my system freezes for 2/3 sec, then re-become responsive, then the calendar app launcher like 10 sec after. All my flatpak apps boot a lot slower than usual. Description:Ubuntu 21.10 Release:21.10 libxml2: Installed: 2.9.12+dfsg-4ubuntu0.1 Candidate: 2.9.12+dfsg-4ubuntu0.1 Version table: *** 2.9.12+dfsg-4ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 2.9.12+dfsg-4 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages flatpak: Installed: 1.10.2-3ubuntu0.1 Candidate: 1.10.2-3ubuntu0.1 Version table: *** 1.10.2-3ubuntu0.1 500 500 http://archive.ubuntu.com/ubuntu impish-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/universe amd64 Packages 100 /var/lib/dpkg/status 1.10.2-3 500 500 http://archive.ubuntu.com/ubuntu impish/universe amd64 Packages systemd: Installed: 248.3-1ubuntu8.2 Candidate: 248.3-1ubuntu8.2 Version table: *** 248.3-1ubuntu8.2 500 500 http://archive.ubuntu.com/ubuntu impish-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu impish-security/main amd64 Packages 100 /var/lib/dpkg/status 248.3-1ubuntu8 500 500 http://archive.ubuntu.com/ubuntu impish/main amd64 Packages journalctl -e: mars 15 11:25:09 mathieu-ThinkPad systemd[3226]: app-gnome-gufw-20889.scope: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad systemd[1]: systemd-timedated.service: Deactivated successfully. mars 15 11:25:13 mathieu-ThinkPad dbus-daemon[6461]: [session uid=1000 pid=6461] Activating via systemd: service name='org.freedesktop.port> mars 15 11:25:13 mathieu-ThinkPad systemd[3226]: Starting flatpak document portal service... mars 15 11:25:14 mathieu-ThinkPad xdg-document-portal[21187]: error: Failed to load db from '/home/mathieu/.local/share/flatpak/db/document> mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Main process exited, code=exited, status=2/INVALIDARGUMENT mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: xdg-document-portal.service: Failed with result 'exit-code'. mars 15 11:25:14 mathieu-ThinkPad systemd[3226]: Failed to start flatpak document portal service. sudo dmesg: [ 2380.432314] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.445853] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2380.449934] Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 [ 2513.367108] gnome-calendar[9096]: segfault at 40016 ip 7f8e926037a0 sp 7ffe96506ca8 error 4 in libgobject-2.0.so.0.7000.4[7f8e925db000+31000] [ 2513.367127] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 [ 2739.248107] [UFW BLOCK] IN=wlp3s0 OUT= MAC=a8:6d:aa:ef:af:b5:be:0d:fd:89:d3:3b:08:00 SRC=142.250.200.129 DST=192.168.43.18 LEN=40 TOS=0x00 PREC=0x00 TTL=116 ID=0 DF PROTO=TCP SPT=443 DPT=56418 WINDOW=0 RES=0x00 RST URGP=0 [ 4484.828195] gnome-calendar[20663]: segfault at 40016 ip 7f4c418207a0 sp 7ffc815aff58 error 4 in libgobject-2.0.so.0.7000.4[7f4c417f8000+31000] [ 4484.828209] Code: ff fc 03 00 00 77 33 48 c1 ef 02 48 8d 05 b8 4b 02 00 48 8b 3c f8 48 81 fe fc 03 00 00 76 28 48 83 e6 fc 31 c0 48 85 ff 74 33 47 16 04 74 05 48 85 f6 75 2d 31 c0 c3 66 90 48 83 e7 fc 48 81 This bug happened with the recent update to libxml2 (one or two days ago ?). This is not the first time it happened. See: https://github.com/flatpak/xdg-desktop-portal-gtk/issues/107#issuecomment-454653039 I don't know where to report this, if this is relates to ubuntu or to the flatpak project. Thanks for looking into this ! ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: systemd 248.3-1ubuntu8.2 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Mar 15 11:28:05 2022 MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-35-generic root=UUID=cd963331-afa1-4933-8bc2-5e53bb0b1c24 ro quiet splash vt.handoff=7 SourcePackage: systemd SystemdFailedUnits: Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use systemd-escape?). Unit \xe2\x97\x8f.service could not be found. -- Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 4: Invalid unit name "●" escaped as
[Bug 1586678]
Any news if that feature would be on the roadmap for future releases ? thx! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1586678 Title: Should have better support for GNOME Online Accounts To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1586678/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936833] Re: postinst fails when cloud-init is installed but never ran
Installation is working (wasn't working with the previous version) with ubuntu-advantage-tools_27.2.2~21.10.1_amd64.deb package from -proposed on Impish. Pr�paration du d�paquetage de ubuntu-advantage-tools_27.2.2~21.10.1_amd64.deb ... D�paquetage de ubuntu-advantage-tools (27.2.2~21.10.1) sur (27.2.1~21.10.1) ... Param�trage de ubuntu-advantage-tools (27.2.2~21.10.1) ... Traitement des actions diff�r�es (��triggers��) pour man-db (2.9.4-2)�... mathieu@FRLAPP253:~$ ** Tags added: verification-done-impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936833 Title: postinst fails when cloud-init is installed but never ran To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1936833/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1924850] Re: package usrmerge 24ubuntu3 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1
I filled another bug that maybe related https://bugs.launchpad.net/ubuntu/+bug/1930573 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1924850 Title: package usrmerge 24ubuntu3 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1924850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930573] Re: usrmerge error after upgradingfrom 20.10 to 21.04
May be related to https://bugs.launchpad.net/ubuntu/+source/usrmerge/+bug/1924850 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930573 Title: usrmerge error after upgradingfrom 20.10 to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1930573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930573] [NEW] usrmerge error after upgradingfrom 20.10 to 21.04
Public bug reported: I got the following error after upgrading from 20.10 to 21.04: Setting up usrmerge (24ubuntu3) ... FATAL ERROR: Both /lib/udev/hwdb.bin and /usr/lib/udev/hwdb.bin exist. You can try correcting the errors reported and running again /usr/lib/usrmerge/convert-usrmerge until it will complete without errors. Do not install or update other Debian packages until the program has been run successfully. dpkg: error processing package usrmerge (--configure): installed usrmerge package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: usrmerge Running "sudo dpkg --configure -a", "sudo apt -f install" or "sudo /usr/lib/usrmerge/convert-usrmerge" give exactly the same error. ** Affects: ubuntu Importance: Undecided Status: New ** Tags: hirsute usrmerge -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930573 Title: usrmerge error after upgradingfrom 20.10 to 21.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1930573/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1913396] [NEW] package scummvm 2.1.1+dfsg1-1build1 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer.
Public bug reported: nothing to say ProblemType: Package DistroRelease: Ubuntu 20.04 Package: scummvm 2.1.1+dfsg1-1build1 ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78 Uname: Linux 5.4.0-64-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 AptOrdering: scummvm:amd64: Remove scummvm-data:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jan 23 10:12:18 2021 DpkgHistoryLog: Start-Date: 2021-01-23 10:12:18 Commandline: apt autoremove Requested-By: mathieu (1000) Remove: scummvm:amd64 (2.1.1+dfsg1-1build1), scummvm-data:amd64 (2.1.1+dfsg1-1build1) DpkgTerminalLog: [1mdpkg:[0m erreur de traitement du paquet scummvm (--remove) : Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. [1mdpkg:[0m trop d'erreurs, arrêt ErrorMessage: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. InstallationDate: Installed on 2018-12-13 (775 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: scummvm Title: package scummvm 2.1.1+dfsg1-1build1 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. UpgradeStatus: Upgraded to focal on 2020-10-07 (111 days ago) ** Affects: scummvm (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/1913396 Title: package scummvm 2.1.1+dfsg1-1build1 failed to install/upgrade: Le paquet est dans un état incohérent; vous devriez le réinstaller avant d'essayer de le supprimer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/scummvm/+bug/1913396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912950] [NEW] rsync halts with Permission denied (13) with a sticky dir and only recent kernels
Public bug reported: Looks like rsync should be adapted to a new policy of the Linux kernel. I found a report in the ZFS Github that looks a lot like my problem : https://github.com/openzfs/zfs/issues/10742 But on that page, the suggested solution using /proc/sys/fs/protected_regular doesn't seem to be ideal and instead rsync should be able to figure it out by itself so that users aren't encouraged to keep that security measure turned off (perhaps my idea is bad, but pros and cons have to be figured out). I'm regularly backing up a remote folder on a machine that has a different user list and that folder has sticky bit set, while being root on both sides. I had no error using Ubuntu 18.04 : it started failing just after upgrading to 20.04. If I try to rsync individual files of that folder, I get error 13 in most cases, but if I chmod -t on that folder, I can rsync them, but if I try rsyncing the folder again (by recursion), rsync does chmod +t on it before rsyncing individual files in the folder, and then it fails again. And of course, to work around the problem, rsync would probably have to catch error 13 and retry after doing chmod -t temporarily on the folder, then schedule a chmod +t after this folder is finished syncing, or at cleanup time (Ctrl+c or SIGTERM). ** Affects: rsync (Ubuntu) Importance: Undecided Status: New ** Description changed: Looks like rsync should be adapted to a new policy of the Linux kernel. I found a report in the ZFS Github that looks a lot like my problem : https://github.com/openzfs/zfs/issues/10742 But on that page, the suggested solution using /proc/sys/fs/protected_regular doesn't seem to be ideal and instead rsync should be able to figure it out by itself so that users aren't encouraged to keep that security measure turned off (perhaps my idea is bad, but pros and cons have to be figured out). I'm regularly backing up a remote folder on a machine that has a different user list and that folder has sticky bit set, while being root on both sides. I had no error using Ubuntu 18.04 : it started failing just after upgrading to 20.04. If I try to rsync individual files of that folder, I get error 13 in most cases, but if I chmod -t on that - folder, I can rsync them, but after that, if I try rsyncing the folder - again, rsync does chmod +t on it before rsyncing individual files in the - folder, and then it fails again. And of course, to work around the - problem, rsync would probably have to catch error 13 and retry after + folder, I can rsync them, but if I try rsyncing the folder again (by + recursion), rsync does chmod +t on it before rsyncing individual files + in the folder, and then it fails again. And of course, to work around + the problem, rsync would probably have to catch error 13 and retry after doing chmod -t temporarily on the folder, then schedule a chmod +t after this folder is finished syncing, or at cleanup time (Ctrl+c or SIGTERM). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912950 Title: rsync halts with Permission denied (13) with a sticky dir and only recent kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1912950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1905546] [NEW] Gnome Shell freezes randomly
Public bug reported: Description is almost the same as https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1807534 Ubuntu 18.04.5 LTS, all packages up to date gnome-shell 3.28.4-0ubuntu18.04.3 Sometimes gnome-shell freezes. I can move the mouse pointer, but the rest of the UI is completely frozen and does not react to mouse clicks or keystrokes. If I try to change login session with Ctrl-Alt-F1, I can login but the screen remains black. I generally manage to "unfreeze" gnome-shell by switching to a virtual console and typing "killall -3 gnome-shell" dmesg shows a page allocation failure in gnome-shell, cf attached file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.4-0ubuntu18.04.3 ProcVersionSignature: Ubuntu 5.4.0-54.60~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-54-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 25 11:10:35 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-21 (278 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "extract of dmesg covering 2 gnome-shell freezes" https://bugs.launchpad.net/bugs/1905546/+attachment/5437817/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1905546 Title: Gnome Shell freezes randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1905546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854396] Re: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM
Hi Christian, Thank you for looking into this issue and providing a fix. sorry but I won't have time to test if a build fixes the problem Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854396 Title: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM To manage notifications about this bug go to: https://bugs.launchpad.net/virt-manager/+bug/1854396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903920] Re: Warning message about cryptsetup during boot
We linked to the same discussion on askubuntu.com (I replied you there). My hope when reporting this is that we don't have to do the workaround you described after each kernel update. Did you open another bug report ? In this case, I will mark this one as a duplicate. ** Description changed: I have noticed that since upgrade to 20.04.1 (from 18.04), a warning message appears during boot: "cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping cryptswap1. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5).". AFAICT, there is no problem however. I use ecryptfs to encrypt my home directory but I don't think it's related (since the message is related to swap). This message used to appear during updates under 18.04 but I never paid attention to it. I probably use the same setup since 16.04. Others have reported the problem (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha /fixing-cryptsetup-wating-for-encrypted-source-device-swapfile-error-on- linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read: - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. I have asked the question at https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010 suggested to open a bug report. I have found anything worth in dmesg though. - As I said everything seems fine (boot proceed normally, I can use the + As I said everything seems fine (boot proceeds normally, I can use the computer) but I expect that there is a way to permanently make this warning disappear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2322 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 23:02:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-06 (1405 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 2570p ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=74d77edf-b4b7-4815-865f-b7602f3396b4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-04 (38 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ISB Ver. F.40 dmi.board.name: 17DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 61.21 dmi.chassis.asset.tag: CNU3229ST9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ISBVer.F.40:bd02/01/2013:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029C1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 2570p dmi.product.sku: C9S65EC#ABF dmi.product.version: A1029C1102 dmi.sys.vendor: Hewlett-Packard -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903920 Title: Warning message about cryptsetup during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903920] Re: Warning message about cryptsetup during boot
Here is my /etc/crypttab. ** Attachment added: "crypttab" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+attachment/5433737/+files/crypttab -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903920 Title: Warning message about cryptsetup during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903920/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1903920] [NEW] Warning message about cryptsetup during boot
Public bug reported: I have noticed that since upgrade to 20.04.1 (from 18.04), a warning message appears during boot: "cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping cryptswap1. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5).". AFAICT, there is no problem however. I use ecryptfs to encrypt my home directory but I don't think it's related (since the message is related to swap). This message used to appear during updates under 18.04 but I never paid attention to it. I probably use the same setup since 16.04. Others have reported the problem (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha /fixing-cryptsetup-wating-for-encrypted-source-device-swapfile-error-on- linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read: - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. I have asked the question at https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010 suggested to open a bug report. I have found anything worth in dmesg though. As I said everything seems fine (boot proceed normally, I can use the computer) but I expect that there is a way to permanently make this warning disappear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-53-generic 5.4.0-53.59 ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65 Uname: Linux 5.4.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2322 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 23:02:47 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2017-01-06 (1405 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard HP EliteBook 2570p ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-53-generic root=UUID=74d77edf-b4b7-4815-865f-b7602f3396b4 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-53-generic N/A linux-backports-modules-5.4.0-53-generic N/A linux-firmware1.187.4 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-10-04 (38 days ago) dmi.bios.date: 02/01/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ISB Ver. F.40 dmi.board.name: 17DF dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 61.21 dmi.chassis.asset.tag: CNU3229ST9 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ISBVer.F.40:bd02/01/2013:svnHewlett-Packard:pnHPEliteBook2570p:pvrA1029C1102:rvnHewlett-Packard:rn17DF:rvrKBCVersion61.21:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI dmi.product.name: HP EliteBook 2570p dmi.product.sku: C9S65EC#ABF dmi.product.version: A1029C1102 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: I have noticed that since upgrade to 20.04.1 (from 18.04), a warning message appears during boot: "cryptsetup: WARNING: Option 'size' missing in crypttab for plain dm-crypt mapping cryptswap1. Please read /usr/share/doc/cryptsetup-initramfs/README.initramfs.gz and add the correct 'size' option to your crypttab(5).". AFAICT, there is no problem however. I use ecryptfs to encrypt my home directory but I don't think it's related (since the message is related to swap). This message used to appear during updates under 18.04 but I never paid attention to it. I probably use the same setup since 16.04. Others have reported the problem (https://askubuntu.com/questions/1109463, https://medium.com/@anirudha /fixing-cryptsetup-wating-for-encrypted-source-device-swapfile-error-on- linux-boot-ubuntu-20-04-5483e0dcf9e9). From what I read: - - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. - - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. + - The answers indicate to edit /etc/crypttab and add a value for size but I don't know what value to use. + - It seems that before 20.04, just editing /etc/crypttab was enough but some users say that they need to manually regenerate the initramfs image after each update which is boring. I have asked the question at https://answers.launchpad.net/ubuntu/+question/693615 and @bernard010 suggested to open a bug report. - I have found anything
[Bug 1899296] [NEW] AttributeError when launching calibre
Public bug reported: Since the latest calibre update, the software doesn't want to start anymore. There is a Python traceback when I run it in a terminal Traceback (most recent call last): File "/usr/bin/calibre", line 20, in sys.exit(calibre()) File "/usr/lib/calibre/calibre/gui_launch.py", line 73, in calibre main(args) File "/usr/lib/calibre/calibre/gui2/main.py", line 543, in main listener = create_listener() File "/usr/lib/calibre/calibre/gui2/main.py", line 514, in create_listener return Listener(address=gui_socket_address()) File "/usr/lib/calibre/calibre/utils/ipc/server.py", line 110, in __init__ self._listener._unlink.cancel() AttributeError: 'NoneType' object has no attribute 'cancel' Can you rollback calibre to a previous working version ? Thanks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: calibre 4.99.4+dfsg+really4.12.0-1build1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Oct 10 23:04:11 2020 InstallationDate: Installed on 2019-09-26 (380 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: calibre UpgradeStatus: Upgraded to focal on 2020-05-10 (153 days ago) ** Affects: calibre (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/1899296 Title: AttributeError when launching calibre To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/calibre/+bug/1899296/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893659] [NEW] Can't upgrade from 18.04 to 20.04 with 'do-release-upgrade' tool
Public bug reported: During the process of upgrade, I gave a message which tell me that an error occurred during the computation of the packet dependencies. $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.38 ProcVersionSignature: Ubuntu 5.3.0-53.47~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Mon Aug 31 16:13:32 2020 InstallationDate: Installed on 2020-03-09 (174 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to bionic on 2020-08-31 (0 days ago) mtime.conffile..etc.update-manager.release-upgrades: 2020-08-31T15:20:48.778677 ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893659 Title: Can't upgrade from 18.04 to 20.04 with 'do-release-upgrade' tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1893659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use
I can confirm that this is still happening in 3.36.3 focal fossa. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1616332 Title: gnome-software using hundreds of MB of memory when not in use To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1616332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847361] Re: Upgrade of qemu binaries causes running instances not able to dynamically load modules
Can you backport https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=467d12f5c784289 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847361 Title: Upgrade of qemu binaries causes running instances not able to dynamically load modules To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1847361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1805256] Re: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images
Isn't this fixed by commit 5710a3e09f9? commit 5710a3e09f9b85801e5ce70797a4a511e5fc9e2c Author: Paolo Bonzini Date: Tue Apr 7 10:07:46 2020 -0400 async: use explicit memory barriers When using C11 atomics, non-seqcst reads and writes do not participate in the total order of seqcst operations. In util/async.c and util/aio-posix.c, in particular, the pattern that we use write ctx->notify_me write bh->scheduled read bh->scheduled read ctx->notify_me if !bh->scheduled, sleep if ctx->notify_me, notify needs to use seqcst operations for both the write and the read. In general this is something that we do not want, because there can be many sources that are polled in addition to bottom halves. The alternative is to place a seqcst memory barrier between the write and the read. This also comes with a disadvantage, in that the memory barrier is implicit on strongly-ordered architectures and it wastes a few dozen clock cycles. Fortunately, ctx->notify_me is never written concurrently by two threads, so we can assert that and relax the writes to ctx->notify_me. The resulting solution works and performs well on both aarch64 and x86. Note that the atomic_set/atomic_read combination is not an atomic read-modify-write, and therefore it is even weaker than C11 ATOMIC_RELAXED; on x86, ATOMIC_RELAXED compiles to a locked operation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1805256 Title: qemu-img hangs on rcu_call_ready_event logic in Aarch64 when converting images To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1805256/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
My comment may be irrelevant but as an IntelliJ user on Ubuntu 18.04.4 LTS, I experience the same problem. I've found a workaround by adding the following line in IntelliJ VM Options : -Dsun.java2d.opengl=true Hope this may help someone ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872001/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874307] [NEW] Xserver crashes after resuming from sleep
Public bug reported: I am experiencing frequent Gnome-Shell crashes when resuming from sleep mode. The screen is flickering and Gnome-Shell is creating a new session instead of restoring the old one. After investigation with the Gnome team, we realized that the real issue is the X server crashing: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2495 The log messages suggest that this issue might be related to the Nvidia driver: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) modeset(G0): failed to set mode: No space left on device avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Fatal server error: avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) EnterVT failed for gpu screen 0 avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: Please consult the The X.Org Foundation support avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: at http://wiki.x.org avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: for help. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Please also check the log file at "/home/wenzel/.local/share/xorg/Xorg.1.log" for additional information. avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) avril 22 04:03:25 Strix /usr/lib/gdm3/gdm-x-session[11320]: (EE) Server terminated with error (1). Closing log file. Especially "EnterVT failed for gpu screen 0" ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xserver-xorg-video-nvidia-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 20:34:17 2020 InstallationDate: Installed on 2019-09-26 (209 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** 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/1874307 Title: Xserver crashes after resuming from sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1874307/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849637] Re: nouveau driver spams dmesg with SCHED_ERROR
I added a recording of dmesg output where we can see the nouveau driver crashing. ** Attachment added: "screencast of the nouveau driver crashing" https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+attachment/5342157/+files/nouveau_crash.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849637 Title: nouveau driver spams dmesg with SCHED_ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782703] Re: Unable to download updates from "extensions.gnome.org"
Can we have a status update on this bug ? I'm having quite frequently and I have to the 3 popups everytime. Can we get this fixed before Ubuntu 20.04 release ? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782703 Title: Unable to download updates from "extensions.gnome.org" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1782703/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867538] [NEW] daily build failed install when using ZFS root on top of an existing ZFS root
Public bug reported: Test being done: Install Ubuntu 19.10 and update post reboot. During install select ZFS experimental option Install Ubuntu 20.10 (latest daily build as of 20200315) During install select ZFS experimental option The installed crashed at the screen asking for user's infos ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubiquity 20.04.6 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CasperVersion: 1.441 CurrentDesktop: ubuntu:GNOME Date: Sun Mar 15 14:05:19 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: LANGUAGE=en_CA.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 LC_NUMERIC=C.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubiquity-20.04.6 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867538 Title: daily build failed install when using ZFS root on top of an existing ZFS root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1867538/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Hi Daniel, I had the time to test the latest 20.04 ISO (today), and I cannot repro the bug so far. Regarding the gnome-shell extensions, I cleared my ~/.local/share/gnome- shell/extensions and rebooted. However, i can still trigger the bug. How can I check the list of installed extensions ? If I go to https://extensions.gnome.org/local/ I can see 3 system installed extensions: - Desktop Icons - Ubuntu AppIndicators - Ubuntu Dock Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Hi Daniel, I updated the bug information via apport-collect. I don't have the time to test Ubuntu 20.04 ISO, sorry. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330541/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330543/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
apport information ** Tags added: apport-collected ** Description changed: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome-Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu8.4 + Architecture: amd64 + CurrentDesktop: ubuntu:GNOME + DisplayManager: gdm3 + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2019-09-26 (150 days ago) + InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) + NonfreeKernelModules: nvidia_modeset nvidia + Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 + RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1 + Tags: eoan + Uname: Linux 5.3.0-40-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip docker libvirt lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330540/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330544/+files/ShellJournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330542/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] monitors.xml.txt
apport information ** Attachment added: "monitors.xml.txt" https://bugs.launchpad.net/bugs/1864301/+attachment/5330545/+files/monitors.xml.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] [NEW] Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
Public bug reported: When I open LibreOffce Writer and decides to resize the Style window on the right of the screen (press F11 to toggle this window), Gnome-Shell completely freezes for a few seconds. I already rebooted and it's 100% reproducible. I initially reported this bug on Gnome-Shell Gitlab: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2225#note_715411 You can find more info there (journalctl logs) ** Affects: gnome-shell (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/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864301] Re: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds
System info: Ubuntu 19.10 gnome-shell: 3.34.1+git20191024-1ubuntu1~19.10.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864301 Title: Resizing LibreOffice style window causes Gnome-Shell to freeze for 10 seconds To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1864301/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849637] Re: nouveau driver spams dmesg with SCHED_ERROR
Hi, I tried again to switch on the nouveau driver, to see if there were any updates that had this bug fixed, but still crashing. It crashing random, after a few minutes on the desktop, browsing the web. Here is the new log, we can see a stacktrace. ** Attachment added: "journactl log upon Nouveau driver crash" https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+attachment/5326676/+files/nouveau_crash.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1849637 Title: nouveau driver spams dmesg with SCHED_ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Tags removed: verification-needed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1857630] [NEW] I checked the integrity of my iso file and it was ok, cannot complete install error no 5 input output error
Public bug reported: Trying to install from usb startup key and it keeps crashing at the user naming phase of the installation with an error no 5 input output. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubiquity 19.10.21 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CasperVersion: 1.427 Date: Thu Dec 26 11:48:57 2019 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash --- maybe-ubiquity LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubiquity-19.10.21 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1857630 Title: I checked the integrity of my iso file and it was ok, cannot complete install error no 5 input output error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1857630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Description changed: + [Impact] + Any user attempting to tab-complete from "umount /dev/" when running the bash shell. + + [Test cases] Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined - $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined + + + [Regression potential] + Since it is limited to a single file (/usr/share/bash-completion/completions/umount) and affects only it, as well as given that it currently does not work, I estimate this as a low risk change. Things to look out for as a regression would be if another previously-working completion would fail to work (ie. what if mount stops completing correctly, and works again if the fix is backed out?). + + --- + ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: - + InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: bash-completion (Ubuntu Focal) Status: Incomplete => Invalid ** Also affects: util-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: gawk (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: mawk (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: ubuntu-meta (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: bash-completion (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: bash-completion (Ubuntu Eoan) Status: New => Invalid ** No longer affects: gawk (Ubuntu) ** No longer affects: mawk (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Also affects: util-linux (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/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851322] Re: VPN auto-connect is not working
@Daniel bug reported upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 It seems that today, even manually triggering the VPN connection doesn't work anymore. If you don't set "store password for all users" for the VPN credentials, the connection will fails. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2008 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2008 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN auto-connect is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1786699] Re: grub-install command line options incompatible with Debian
I have an issue with leaving cruft around instead of actively fixing whatever depends on old behavior; months from now, or even years, we'll still have this switch around that does nothing -- that's more confusing for users than actively moving forward. That said, I'll defer to Colin and add the no-op. Are you saying that you otherwise have no issues with the idea of this patch and would consider including it in the Debian package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1786699 Title: grub-install command line options incompatible with Debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1786699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852772] Re: test_updates_interval fails on focal
** Changed in: software-properties (Ubuntu) Status: Triaged => 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/1852772 Title: test_updates_interval fails on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851992] Re: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason)
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851992 Title: Lock screen not locking upon resume (org.gnome.desktop.lockdown disable-lock-screen set to true for some reason) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851992/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854396] Re: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM
@Christian I reported the bug upstream :-) https://bugzilla.redhat.com/show_bug.cgi?id=1779362 ** Bug watch added: Red Hat Bugzilla #1779362 https://bugzilla.redhat.com/show_bug.cgi?id=1779362 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854396 Title: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1854396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
tcmu is a high-impact target that will handle storage requests and potentially allow an attacker to intercept data. I'm concerned by the fact the Debian maintainer felt they had to disable -Werror to make things work on 32-bit; even if that's not necessarily out main focus: it points to potential issues in the code, code that is not necessarily very portable or that might be hard to maintain in the future. I'll let the Security Team give their opinion on it and decide. ** Changed in: tcmu (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: tcmu (Ubuntu) Status: In Progress => New ** Changed in: python-rtslib-fb (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
urwid should have security review. Packaging for it looks fine, but it does handle input, present UI that is used in core places for the OS (such as in the installer, even though that's a snap...) ** Changed in: urwid (Ubuntu) Status: In Progress => New ** Changed in: urwid (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Ubuntu Security Team (ubuntu-security) ** Changed in: tcmu (Ubuntu) Status: New => In Progress ** Changed in: tcmu (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1849637] Re: nouveau driver spams dmesg with SCHED_ERROR
** Also affects: xserver-xorg-video-nouveau (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/1849637 Title: nouveau driver spams dmesg with SCHED_ERROR To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nouveau-firmware/+bug/1849637/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854396] Re: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM
Hi Chritian, thanks for the feedback I can report bugs on Ubuntu, but I would like to avoid being involved into other bugtackers, as it is time consuming. Also, you have more authority and credibility than me to report the bug, so it will be taken seriously from the start. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854396 Title: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1854396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854392] Re: Bluetooth headphones won't use A2DP on reconnect
That's not /really/ helpful anyway. You'd have installed an extra application, for a wholly unrelated issue, and still have to set the profile to A2DP yourself. Alistair, there are messages in your logs that seem to point to a firmware issue: Nov 26 16:56:25 albatross bluetoothd[1010]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107) Furthermore, I see some slightly unusual messages that point to an issue with the firmware (usually) as well: Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 0 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 Nov 26 14:45:14 albatross kernel: Bluetooth: hci0: SCO packet for unknown connection handle 257 It's possible the hardware gets confused by losing the connection that was initially there. I realize this might not be /so/ helpful, but have you also tried with another model of bluetooth headphones, assuming you have something available? Please see if you can attach the full contents of /var/log/syslog after reproducing the issue (with a different model or with the usual Sonys); once you've made sure that it doesn't contain sensitive data. I'd need to know when you started each attempt so we can see exactly how the system reacts to it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854392 Title: Bluetooth headphones won't use A2DP on reconnect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854392/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854396] Re: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM
I've just found a workaround: disable the systray icon. virt-manager's integration with Gnome-Shell systray is the root cause of 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/1854396 Title: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1854396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854396] [NEW] virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM
Public bug reported: Hi, When I start or shutdown a VM via virt-manager, it has the side effect of freeze the Gnome-Shell desktop for 3 seconds. I can move the mouse, but I can't click on anything to get the focus, or drag'n drop a window. (look at the desktop record in the attachments) I have noticed the following line in my journactl when the freeze happens: nov. 28 21:07:38 gnome-shell[3133]: [AppIndicatorSupport-WARN] Attempting to re-register :1.138/org/ayatana/NotificationItem/virt_manager; resetting instead nov. 28 21:07:38 gnome-shell[3133]: [AppIndicatorSupport-WARN] Item :1.138/org/ayatana/NotificationItem/virt_manager is already registered nov. 28 21:07:38 gnome-shell[3133]: [AppIndicatorSupport-WARN] Attempting to re-register :1.138/org/ayatana/NotificationItem/virt_manager; resetting instead nov. 28 21:07:38 gnome-shell[3133]: [AppIndicatorSupport-WARN] Item :1.138/org/ayatana/NotificationItem/virt_manager is already registered nov. 28 21:07:43 gnome-shell[3133]: [AppIndicatorSupport-WARN] Attempting to re-register :1.138/org/ayatana/NotificationItem/virt_manager; resetting instead nov. 28 21:07:43 gnome-shell[3133]: [AppIndicatorSupport-WARN] Item :1.138/org/ayatana/NotificationItem/virt_manager is already registered This is really annoying as I'm starting/stopping VMs frequently in my workflow. Please provide a fix or a workaround. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: virt-manager 1:2.2.1-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 21:05:02 2019 InstallationDate: Installed on 2019-09-26 (63 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virt-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Desktop recording of the bug" https://bugs.launchpad.net/bugs/1854396/+attachment/5308551/+files/virt-manager-freeze-desktop.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854396 Title: virt-manager freezes the whole desktop for 3 seconds when starting/stopping a VM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1854396/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852772] Re: test_updates_interval fails on focal
I see no objection at all; that fix looks obviously correct and does fix the test. ** Changed in: software-properties (Ubuntu) Assignee: (unassigned) => Corey Bryant (corey.bryant) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852772 Title: test_updates_interval fails on focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1852772/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854362] Re: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid
** Changed in: urwid (Ubuntu) Status: New => In Progress ** Changed in: urwid (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854362 Title: [MIR] ceph-iscsi, tcmu, python-configshell-fb, python-rtslib-fb, urwid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceph-iscsi/+bug/1854362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851064] Re: [SRU] Update WALinuxAgent to 2.2.44
** Tags added: block-proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851064 Title: [SRU] Update WALinuxAgent to 2.2.44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1851064/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845289] Re: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi
There are multiple reports of chainload working again with the fix uploaded to eoan-proposed; marking as verification-done for Eoan with 2.04-1ubuntu12.1 ** Tags removed: id-5d978799ba24715c5ddcabc5 verification-needed verification-needed-eoan ** Tags added: id-5d978799ba24715c5ddcabc verification-done-eoan ** Tags removed: id-5d978799ba24715c5ddcabc ** Tags added: id-5d978799ba24715c5ddcabc5 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845289 Title: Grub EFI amd64 no longer start EFI/Microsoft/Boot/bootmgfw.efi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1845289/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852908] [NEW] Reboot button does nothing on login screen
Public bug reported: Hi, When I'm boot my computer and the Gnome Shell login screen appears, if I try to reboot the computer from the menu available in the top right, the button does nothing. I tried clicking multiple times, my computer won't reboot. However, If i'm logged into my desktop, and then ask for a reboot, it works. So either there is a permission issue to reboot on Gnome Shell login screen, or there is a deeper issue here. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 17 13:52:59 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-09-26 (51 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** 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/1852908 Title: Reboot button does nothing on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1852908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852364] [NEW] iwlwifi: Microcode SW error detected
Public bug reported: Hi, I just had an unresponsive Wifi connexion, and checking the dmesg logs gave me this: [53468.634940] iwlwifi :00:14.3: Queue 11 is active on fifo 1 and stuck for 1 ms. SW [0, 15] HW [0, 15] FH TRB=0x0c010b000 [53468.635087] iwlwifi :00:14.3: Microcode SW error detected. Restarting 0x0. [53468.635466] iwlwifi :00:14.3: Start IWL Error Log Dump: [53468.635471] iwlwifi :00:14.3: Status: 0x0080, count: 6 [53468.635475] iwlwifi :00:14.3: Loaded firmware version: 46.6bf1df06.0 [53468.635480] iwlwifi :00:14.3: 0x0084 | NMI_INTERRUPT_UNKNOWN [53468.635484] iwlwifi :00:14.3: 0x22F0 | trm_hw_status0 [53468.635488] iwlwifi :00:14.3: 0x | trm_hw_status1 [53468.635491] iwlwifi :00:14.3: 0x004882DA | branchlink2 [53468.635495] iwlwifi :00:14.3: 0x0047932A | interruptlink1 [53468.635498] iwlwifi :00:14.3: 0x0047932A | interruptlink2 It looks like a iwlwifi firmware crash. See the dmesg log attached. Thanks. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-firmware 1.183.1 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 13 02:54:38 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (47 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "dmesg log" https://bugs.launchpad.net/bugs/1852364/+attachment/5304906/+files/bug_iwl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852364 Title: iwlwifi: Microcode SW error detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1852364/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851725] Re: NetworkManager forgets VPN credentials
Hi Sebastien, I'm not unchecking any option, there is a default selected option for the password field which is "remember this password for this user only". And with this option, NetworkManager doesn't remember the password. With "remember the password for all users" option, NetworkManager works fine, but that's not what I want. (I hope the issue is more clear now) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851725] Re: NetworkManager forgets VPN credentials
I would like to add that if you choose to store the password for all users, then it works, the password is stored by NetworkManager. However, the bug is important because it affects the default option selected for anyone willing to use a VPN connection: store password for the current user. Any Ubuntu user who is trying to use a VPN connection will probably decide to give up because of NetworkManager unability to store the password, despite what the GUI says. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851725] Re: NetworkManager forgets VPN credentials
Hi Sebastien, The only line that pops up when I click apply is the one I already pasted before: nov. 12 00:40:00 NetworkManager[1529]: [1573515600.3387] audit: op="connection-update" uuid="45154b5c- bed9-4904-a090-7d2e0303e27e" name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=23095 uid=1000 result="success" There is no other relevant information in journalctl in my opnion. I could send you a log if you want, but I don't know how to NOT make it publicly available on this Launchpad report. Thanks/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1852002] [NEW] Desktop frozen for 30 seconds after Nvidia driver crash
Public bug reported: Hi, I just experienced a frozen desktop, where I could barely move the mouse, for maybe 30 seconds or more. When the desktop recovered, I looked at dmesg logs to find these lines: [ 461.937702] NVRM: GPU at PCI::01:00: GPU-734060ac-116d-fbbb-1553-d84896b846a4 [ 461.937710] NVRM: Xid (PCI::01:00): 31, pid=275, Ch 002e, intr . MMU Fault: ENGINE HOST0 HUBCLIENT_HOST_CPU faulted @ 0x1_0036d000. Fault is of type FAULT_PTE ACCESS_TYPE_VIRT_READ It looks like a fault from the Nvidia driver. I'm using the tested one "nvidia-driver-435", installed via the GUI tool. Could you report this to Nvidia please ? Thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Nov 10 17:35:12 2019 InstallationDate: Installed on 2019-09-26 (45 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** 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/1852002 Title: Desktop frozen for 30 seconds after Nvidia driver crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1852002/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851725] [NEW] NetworkManager forgets VPN credentials
Public bug reported: Hi, Since recently, I can't import a VPN connection in NetworkManager and store my credentials. NetworkManager will systematically forget the password, despite a log entry confirming that the operation was a success: nov. 07 22:26:52 NetworkManager[1518]: [1573162012.8680] audit: op="connection-update" uuid="3f985155-4e20-4351-88d7-14d5909a2d03" name="at-01.protonvpn.com.udp" args="vpn.secrets" pid=6379 uid=1000 result="success" Please look at the video attached. Please fix. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 7 22:22:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IpRoute: default via 192.168.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev virbr0 scope link metric 1000 linkdown 192.168.0.0/24 dev wlo1 proto kernel scope link src 192.168.0.18 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "NetworkManager forget VPN password" https://bugs.launchpad.net/bugs/1851725/+attachment/5303593/+files/network-manager-vpn-credentials.webm -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851725 Title: NetworkManager forgets VPN credentials To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851725/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1838323] Re: Support Japanese new era "令和 (Reiwa)"
** Description changed: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] Unicode data include REIWA like it includes HEISEI. Reverse-build- depends need a rebuild to include the new data, followed by the following tests to make sure the data is taken into account. + 1) Rebuild reverse-depends of unicode-data; check that they build fine + (ie. no regressions due to unicode-data changes): + + Reverse-Build-Depends + = + * console-data + * courier-unicode + * cyrus-imapd + * fntsample + * fonttools + * gucharmap + * ibus + * julia + * libxmlada + * node-unicode-data + * node-unicode-property-aliases + * node-unicode-property-aliases-ecmascript + * node-unicode-property-value-aliases + * node-unicode-property-value-aliases-ecmascript + * node-unicode-tr51 + * re2 + * safeclib + * slang2 + * utf8proc + * wcwidth + * wine + * wine-development + + + 2) Using gucharmap, verify that the SQUARE ERA NAME REIWA glyph point exists (there may not be a glyph associated as that is font-dependent. + == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - - SQUARE ERA NAME HEISEI: ㍻ - - SQUARE ERA NAME REIWA: 令和 (in a single glyph) + - SQUARE ERA NAME HEISEI: ㍻ + - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. Use fonts-noto-cjk to display the glyph. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1838323 Title: Support Japanese new era "令和 (Reiwa)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unicode-data/+bug/1838323/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851322] Re: VPN auto-connect is not working
I would rather not getting involved into too many bugtrackers, and as a Ubuntu user, remain on Launchpad and provide the required information to let you investigate. Also, as you are a member of Ubuntu teams, you have more authority/credibility than me, so that bug can be taken seriously by Gnome-shell teams. Thanks Sebastien. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN auto-connect is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1851322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851322] Re: VPN auto-connect is not working
Hi Sebastien, I'm using an the OpenVPN plugin. I'm imported an .ovpn config file into NetworkManager and filled my credentials. I found some interesting log messages in journalctl: nov. 05 21:00:58 gnome-shell[2760]: Invalid connection type: vpn nov. 05 21:00:58 gnome-shell[2760]: Invalid connection type: vpn nov. 05 21:00:58 NetworkManager[1485]: [1572984058.4210] vpn-connection[0x55e68ff9c730,50d6326e-03bc-49a9-9f04-40c353cf55b3,"protonvpn.udp.com",0]: Failed to request VPN secrets #3: No agents were available for this request. nov. 05 21:00:58 NetworkManager[1485]: [1572984058.4212] device (wlo1): state change: secondaries -> failed (reason 'secondary-connection-failed', sys-iface-state: 'managed') The error seems to be the "agent" --> Failed to request VPN secrets #3: No agents were available for this request. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851322 Title: VPN auto-connect is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851322] [NEW] VPN auto-connect is not working
Public bug reported: Hi, This is a duplicate of bug: https://bugs.launchpad.net/network-manager/+bug/1718931 It is marked as fixed, but the feature is still broken for me. I configured my Wifi connection to automatically connect to a VPN, but it only works if I manually connect to the Wifi via NetworkManager. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.4-2ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 5 04:07:00 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2019-09-26 (39 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.4 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager Importance: Undecided Status: New ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ** Attachment added: "Video recorded at boot time, right after login, where the Wifi connexion fails because of the VPN auto-connect being broken" https://bugs.launchpad.net/bugs/1851322/+attachment/5302868/+files/vpn-auto-connect.webm ** Also affects: network-manager 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/1851322 Title: VPN auto-connect is not working To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1851322/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847458] Re: EFI chainloader no longer uses shim lock protocol
** Changed in: grub2 (Ubuntu) Status: Incomplete => Invalid ** Changed in: grub2 (Ubuntu Eoan) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847458 Title: EFI chainloader no longer uses shim lock protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848797] Re: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found."
Are the systems getting this set up for dual-booting at all? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848797 Title: After upgrading to 19.10, boot screen shows: "Error: symbol 'grub_file_filters' not found." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1848797/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1847458] Re: EFI chainloader no longer uses shim lock protocol
The code does look like it will chainload via shim: linuxefi_secure_validate() runs, checks that the image is valid against firmware stores and the MokList. Then grub_cmd_chainloader -> (grub_linuxefi_secure_validate() find the image valid) -> grub_secureboot_chainloader_boot() -> handle_image() [ read image header, identify relocations, find entry point, etc.] -> efi_call_2 (entry point) -> Image is started -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1847458 Title: EFI chainloader no longer uses shim lock protocol To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1847458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
