[Bug 2065447] [NEW] The size of the launcher cannot be changed
Public bug reported: I tried to set the size of the launcher icons to 32, the content of the field changes and shows 32, but the display of the launcher stays at 44. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 10 17:23:54 2024 DistUpgraded: Fresh install DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2024-05-10 (0 days ago) InstallationMedia: Ubuntu-Unity 24.10 "Oracular Oriole" - Daily amd64 (20240510) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic root=UUID=90498115-0564-4a1e-bc6b-cde75ec4bde4 ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu12 version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 oracular reproducible single-occurrence ubuntu ** Description changed: - I tried to set it to 32, the content of the filed changes and stays on - 32, but the display is at 44. + I tried to set the size of the launcher icons to 32, the content of the + field changes and shows 32, but the display of the launcher stays at 44. ProblemType: Bug DistroRelease: Ubuntu 24.10 Package: xorg 1:7.7+23ubuntu3 ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1 Uname: Linux 6.8.0-31-generic x86_64 .tmp.unity_support_test.1: - + ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 10 17:23:54 2024 DistUpgraded: Fresh install DistroCodename: oracular DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) -Subsystem: VMware SVGA II Adapter [15ad:0405] + VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) + Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2024-05-10 (0 days ago) InstallationMedia: Ubuntu-Unity 24.10 "Oracular Oriole" - Daily amd64 (20240510) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: - /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M - |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M - /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p,
Re: [Bug 1910448] Re: 100% CPU-core load for xrdp-chansrv
I can't repeat it, because I don't have that HP dc5850 computer with Ubuntu 20.04 LTS anymore and I'm in the transfer from 23.10 to 24.04 LTS. On Wed, 2024-03-20 at 03:22 +, Lenin wrote: > can you reproduce this? if so lease describe > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910448 Title: 100% CPU-core load for xrdp-chansrv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1910448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058141] Re: Some applications crash the desktop in Unity
The whole issue is related to Virtualbox too, without 3D acceleration all appss crash; with 3D acceleration they work. In 23.10 I use VBox 7.14 and Linux 6.5 everything should work and it works if I use 3D acceleration for the Display. If I don't use it, lollypop; exaile; gthumb crash the desktp, when starting those apps. In 24.04 I use development editions of VBox because of Linux 6.8 everything should work and it works if I use 3D acceleration for the Display. If I don't use it, lollypop; exaile; gthumb crash the desktop, when starting those apps. I tried a new install of Ubuntu Budgie with the same effects, it crashes the desktop, when starting lollypop; exaile; gthumb, but when I use 3D acceleration for the display it works. If I use Ubuntu 24.04 all those apps work as expected: with or without 3D acceleration. In Xubuntu 24.04 Lollypop also works fine, like in Ubuntu. It looks like there is some incompatibilty between some flavors and virtualbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058141 Title: Some applications crash the desktop in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lollypop/+bug/2058141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058141] Re: Some applications crash the desktop in Unity
I have exactly the same problems with Ubuntu Unity 23.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058141 Title: Some applications crash the desktop in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lollypop/+bug/2058141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2058141] [NEW] Some applications crash the desktop in Unity
Public bug reported: If I start lollypop the desktop crashes and I have to login again. This bug report is the first action afterwards. Starting ubuntu-bug and thus firefox I get strange error messages, see annex. It looks like we are in a gtk2/3 chaos again. I have installed the development editions shortly after it has been released and kept it nicely up to date till now. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: lollypop 1.4.37-1 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 17 11:16:39 2024 InstallationDate: Installed on 2023-11-05 (133 days ago) InstallationMedia: Ubuntu-Unity 24.04 "Noble Numbat" - Daily amd64 (20231104) PackageArchitecture: all SourcePackage: lollypop UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lollypop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble third-party-packages ** Attachment added: "starting-bug" https://bugs.launchpad.net/bugs/2058141/+attachment/5756548/+files/starting-bug -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2058141 Title: Some applications crash the desktop in Unity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lollypop/+bug/2058141/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
Trying to install new snaps on the zfs 23.10 fail too: bertadmin@Host-R3:~$ snap install libreoffice error: cannot perform the following tasks: - Download snap "libreoffice" (311) from channel "stable" (no device serial yet) bertadmin@Host-R3:~$ snap install thunderbird error: cannot perform the following tasks: - Download snap "thunderbird" (455) from channel "stable" (no device serial yet) bertadmin@Host-R3:~$ Nothing is wrong with the ext4 24.04 system as long as you don't import rpool, yesterday I worked with it for 4 hours without problems using e.g Xubuntu 22.04 (HDD) instead of 24.04 (rpool) and I moved Ubuntu 16.04 ESM from rpool to the HDD. Everything is wrong with snaps on the zfs 23.10 system after I imported rpool in ext4 24.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
See the same error with snapstore: snap-store 2024/03/15 11:14:50.600339 system_key.go:129: cannot determine nfs usage in generateSystemKey: cannot parse /etc/fstab: expected between 3 and 6 fields, found 7 Content snap command-chain for /snap/snap-store/1113/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
Content of fstab and the swap file lines have 7 items instead of 6, because I added priority, but that has always been like this since many years. The system should use first the nvme swap and only if full the HDD swap :) # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # /dev/disk/by-uuid/6e6abccf-46b7-4915-ac0e-9aaa264965ab none swap sw pri=0 0 0 /dev/disk/by-uuid/7454fc6f-80d7-478e-a67b-84eacf44c40f none swap sw pri=-1 0 0 # Use `zfs list` for current zfs mount info # bpool none defaults 0 0 # Use `zfs list` for current zfs mount info # rpool none defaults 0 0 # Use `zfs list` for current zfs mount info # rpool / defaults 0 0 # Use `zfs list` for current zfs mount info # bpool /boot defaults 0 0 # /boot/efi was on /dev/nvme0n1p1 during curtin installation /dev/disk/by-uuid/C4D7-B106 /boot/efi vfat defaults 0 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
Starting firefox in the terminal gives the following errors: bertadmin@Host-R3:~$ firefox 2024/03/15 10:27:25.066219 system_key.go:129: cannot determine nfs usage in generateSystemKey: cannot parse /etc/fstab: expected between 3 and 6 fields, found 7 update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/local/share/doc /usr/local/share/doc none bind,ro 0 0): cannot open directory "/usr/local/share": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/gimp/2.0/help /usr/share/gimp/2.0/help none bind,ro 0 0): cannot open directory "/var/lib": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/libreoffice/help /usr/share/libreoffice/help none bind,ro 0 0): cannot open directory "/var/lib": permission denied update.go:85: cannot change mount namespace according to change mount (/var/lib/snapd/hostfs/usr/share/xubuntu-docs /usr/share/xubuntu-docs none bind,ro 0 0): cannot open directory "/var/lib": permission denied Content snap command-chain for /snap/firefox/3941/gnome-platform/command-chain/desktop-launch not found: ensure slot is connected bertadmin@Host-R3:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
I tried my ext4 system again. All VMs work fine. However I cannot use Firefox anymore after importing rpool. I exported all zpools and booted my main system again. My main system Ubuntu 23.10 booting from ZFS, the boot worked fine. but two snaps were damaged by the ext 24.04 system after I imported rpool. "firmware-updater" did give an error message, but after removing and installing it again it seems ok. However Firefox is unusable, even after removing it and installing it again, it remain unusable. I will state it very simple, after importing rpool containing the 23.10 zfs system, the ext4 24.04 system get confused about the location of the OS! The 24.04 ext4 system uses and changes stuff in the 23.10 zfs rpool -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056652] Re: Display goes black after time out, even when switched off
There is a crash report from Saturday 9 March, but ubuntu-bug crashes. Saturday I did run the the update around that time and I remember it was a partial upgrade. This screen blanking problem I noticed earlier than Saturday, so I don't expect a relation with the crash report. I did load the crash report in mousepad and saved it as a text file, so I hope, it will be partial useful. ** Attachment added: "_usr_libexec_tracker-extract-3.1000.txt" https://bugs.launchpad.net/ubuntu/+bug/2056652/+attachment/5754758/+files/_usr_libexec_tracker-extract-3.1000.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056652 Title: Display goes black after time out, even when switched off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056652] Re: Display goes black after time out, even when switched off
the file journal.txt ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+bug/2056652/+attachment/5754751/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056652 Title: Display goes black after time out, even when switched off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056652] Re: Display goes black after time out, even when switched off
the file prev-journal.txt ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+bug/2056652/+attachment/5754752/+files/prevjournal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056652 Title: Display goes black after time out, even when switched off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2056652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056652] Re: Display goes black after time out, even when switched off
** Description changed: - I switched of suspend and power-off and blanking of the screen. - The VM screen still goes blank after say some minutes. + In the power settings I switched of suspend and power-off and blanking of the screen. + The VM screen still goes blank after say some minutes and I have to login again. For the settings see screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 9 17:40:38 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) -Subsystem: VMware SVGA II Adapter [15ad:0405] + VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) + Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-11-04 (126 days ago) InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231104) Lsusb: - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub - Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: - /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M - |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M - /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M + /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M + |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=352698a3-5a2b-40d6-8a28-eddaf4035c1b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056652 Title: Display goes black after time out, even when switched off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2056652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056652] [NEW] Display goes black after time out, even when switched off
Public bug reported: I switched of suspend and power-off and blanking of the screen. The VM screen still goes blank after say some minutes. For the settings see screenshots. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 9 17:40:38 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2023-11-04 (126 days ago) InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231104) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Lsusb-t: /: Bus 001.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 001: Dev 002, If 0, Class=Human Interface Device, Driver=usbhid, 12M /: Bus 002.Port 001: Dev 001, Class=root_hub, Driver=xhci_hcd/6p, 5000M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-11-generic root=UUID=352698a3-5a2b-40d6-8a28-eddaf4035c1b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble reproducible single-occurrence ubuntu ** Attachment added: "Screenshot_2024-03-09_17-50-50.png" https://bugs.launchpad.net/bugs/2056652/+attachment/5754402/+files/Screenshot_2024-03-09_17-50-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056652 Title: Display goes black after time out, even when switched off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2056652/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] Re: Ubuntu dual boot mix up from zfs and from ext4
Additional info. After importing rpool I can use the Virtual Machines in rpool, but the issues with the terminal and shutting down remain. I installed a 2nd terminal Tilix and after a warning message I can use it to e.g. export all datapools, but the issues with the standard terminal and shutting down remain. The gnome settings app also has issues after importing rpool. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2056646] [NEW] Ubuntu dual boot mix up from zfs and from ext4
Public bug reported: I dual boot Ubuntu 23.10 from openzfs from nvme (main OS) and from ext4 from HDD (backup OS). In 23.10 everything worked, I could use my datapools on both systems also rpool, The nvme datapool rpool contains the ROOT dataset and 2 datasets with my main VMs. I upgraded the ext4 system to 24.04 (do-release-upgrade -d) and that worked fine. I have 2 other datapools on the HDD and I can use them without any issue after (zpool import -f) on the ext4 system. As soon as I try to import the datapool rpool the problem starts, it gives the following error message: "Broadcast message from systemd-journald@Host-sdb5 (Sat 2024-03-09 12:50:47 AST): systemd[1]: Caught , from our own process." Afterwards it is impossible to use the terminal, it just does not start. However most other applications still work as normal. It is also impossible to shut-down the system from the menu. I have to power off the system with the power button. On reboot I get the following error messages; zfs: module license "CDDL" taints kernel. Disabling lock debugging due to kernel taint zfs: module license taints kernel It seems to load the zfs kernel modules again, why? It is superfluous and wrong, because they are already loaded from ext4 much earlier. Afterward the system is completely confused and hangs. (see the annexed photo) My nvme system does not boot anymore, because it is missing rpool, but it nicely advises in initramfs to use "zpool import -f" and that works. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: ubuntu-release-upgrader-core 1:24.04.7 ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4 Uname: Linux 6.8.0-11-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Mar 9 13:12:08 2024 InstallationDate: Installed on 2023-12-21 (80 days ago) InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to noble on 2024-03-09 (0 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade noble wayland-session ** Attachment added: "20240309_120126.jpg" https://bugs.launchpad.net/bugs/2056646/+attachment/5754353/+files/20240309_120126.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2056646 Title: Ubuntu dual boot mix up from zfs and from ext4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2056646/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
Same for me can't reproduce the bug, try again tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969281] Re: Very slow reception of incremental OpenZFS backup
Let me try a wild guess, it looks like buffer fragmentation related to network/ssh/openZFS. The software might desperately try to defragment many small spaces and that would explain the 100% CPU load during the low speed transfers. If the defragmentation happens in the kernel, it also might explain, why the CPU frequency is not increased. Note that only Conky records that 100% CPU load, while the task manager does not notice anything and has the load below 30% all the time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969281 Title: Very slow reception of incremental OpenZFS backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969281] Re: Very slow reception of incremental OpenZFS backup
The error only occurs on the backup of the large datasets with incremental updates from say 40 GB to 80 GB. Those datasets are around 250 GB and 450 GB and they contain Virtual Machines. On smaller datasets I have no issues and in the begin of the transfers, there are no problems either. The performance get worse over time. Today I also moved one of the datasets to another partition and that local transfer had no problems. So the error is more related to the interface between ssh and OpenZFS. However this dataset has a few VMs and is around 25GB with 2GB to 5GB updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969281 Title: Very slow reception of incremental OpenZFS backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1969281] [NEW] Very slow reception of incremental OpenZFS backup
Public bug reported: Since OpenZFS the reception of incremental backups over ssh are very slow; FreeBSD 13.0 with OpenZFS running on a 2003 Pentium 4 HT 3.0GHz (1.5GB DDR) is faster than Ubuntu 21.10/22.04 with OpenZFS running on my laptop with an i5-2520m (8GB DDR3). FreeBSD runs at 21 MiB/s with a 10% variance; The limit is caused by the load on a P4 CPU thread of >90%; For Ubuntu the transfer speed is between 90 MiB/S and periods of seconds long with 0 MiB/s. A lot of time the transfer speed is in the single digit numbers. The problems occur when one or two of the four i5 cpu threads run at 100%, while the CPU clock remains at 0.83 GHz. So it looks like an integration issue between OpenZFS and the Linux kernel. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: zfsutils-linux 2.1.2-1ubuntu3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 16 14:49:10 2022 InstallationDate: Installed on 2021-10-30 (168 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1969281 Title: Very slow reception of incremental OpenZFS backup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1969281/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
I don't use a wayland session. Also on the first login screen the xorg session has been selected in the menu. I understand vmwgfx is the VMware Linux graphics driver also used by Virtualbox for exposing 3D/OpenGL/3D hardware acceleration to guest virtual machines. Switching off 3D acceleration did not help. Remains the fact that the problem only shows up in Ubuntu 22.04 and not in Ubuntu 22.04; Ubuntu Mate 22.04 nor in any 20.04 version or in Fedora 36 Beta also with Gnome 42. Curious, do you have any cooperation with the VBox maintainers? On Wed, 2022-04-06 at 02:35 +, Daniel van Vugt wrote: > BertN45: The only error that stands out to me in your log is that the > vmwgfx kernel driver keeps logging: > > kernel: [drm:vmw_msg_ioctl [vmwgfx]] *ERROR* Failed to open > channel. > > If that's the problem then it's a bug in the kernel (where the vmwgfx > driver lives) and/or the hypervisor. > > Otherwise the log shows that the Wayland session starts successfully > and > tries to register itself with GDM. And 30 seconds later, GDM starts a > Xorg session. > > ** Tags added: vmwgfx > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
The requested file On Tue, 2022-04-05 at 01:47 +, Daniel van Vugt wrote: > > My first login was with xorg and it failed > > If you could provide a fresh clean log of the issue I would be > interested to see. Please: > > 1. Reboot. > > 2. Reproduce the bug. > > 3. Reboot. > > 4. Run: > > journalctl -b-1 > prevboot.txt > > 5. Attach the resulting text file here. > ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/bugs/1966786/+attachment/5577397/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
My first login was with xorg and it failed, the second login was without the menu to select wayland or xorg, So what is different between running xorg the first time and the second time? Some time ago I had to choose xorg, because DOSBOX and Conky did not run with Wayland in that VM. That was confirmed by many other reports on the internet. I need DOSBOX to play Wolfenstein-3D :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1967570] [NEW] update-manager crashed
Public bug reported: The update manager crashed, after I pressed "Install Now" ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: update-manager 1:0.196.25 ProcVersionSignature: Ubuntu 4.4.0-222.255~14.04.1-generic 4.4.262 Uname: Linux 4.4.0-222-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.29+esm9 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 1 14:33:57 2022 DpkgHistoryLog.txt: DpkgTerminalLog.txt: HWEreplacements: HWEunsupported: InstallationDate: Installed on 2019-01-29 (1158 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: update-manager UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: update-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1967570 Title: update-manager crashed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1967570/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice with VirtualBox Guest Additions
To be clear in my opinion it is not a problem of Virtualbox, since I run over 15 modern Linux distros in Virtualbox VMs and none has the same issue. That is true for Fedora 35 and 36 Beta also with Gnome 42. No problems with Ubuntu 20.04, Xubuntu 22.04; Ubuntu Budgie 22.04, Ubuntu Mate 22.04, Peppermint 11; Linux Mint 20.3 etc etc. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice with VirtualBox Guest Additions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice
Maybe switching from wayland to xorg caused the problem. That menu was only present on the first login screen, so I tried moving back to Wayland. The double login screen remained and I had the old issues again with DOSBOX and Conky :( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice
1. When I reinstalled with "sh autorun.sh", I got two terminals and the first one said: bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ sh autorun.sh # Option “-x” is deprecated and might be removed in a later version of gnome-terminal. # Use “-- ” to terminate the options and put the command line to execute after it. bertadmin@vm-ubuntu-2204:/media/bertadmin/VBox_GAs_6.1.32$ The Second Terminal executed the install as expected, see also attachment. 2. When I uninstalled Virtual box with "sh VBoxLinuxAdditions.run uninstall" the problem disappeared. The boot and login were normal. But the problem reappeared after a reinstall "sh VBoxLinuxAdditions.run". 3. I have upgraded the system from Ubuntu 20.04. After a while I noticed that DOSBOX and Conky did not run anymore with wayland, so I moved back to xorg through the menu in the login screen. According to "the Internet", it is a known issue with Conky and DOSDOX. Maybe switching from wayland to xorg caused the problem, but that menu disappeared from the login screen, so I cant move back to wayland. ** Attachment added: "vbox-issue" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574845/+files/vbox-issue -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] Re: login screen shown twice
I did found the following crash report from yesterday in /var/crash and I think it has already been uploaded automatically. ** Attachment added: "_usr_lib_update-notifier_list-oem-metapackages.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+attachment/5574329/+files/_usr_lib_update-notifier_list-oem-metapackages.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1966786] [NEW] login screen shown twice
Public bug reported: The login screen is shown twice and I have to supply the password twice. The system works normally afterwards. When I select auto-login in the settings still one login screen is shown. gdm.service - GNOME Display Manager Loaded: loaded (/lib/systemd/system/gdm.service; static) Active: active (running) since Mon 2022-03-28 11:47:32 AST; 6min ago Process: 1885 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS) Main PID: 1915 (gdm3) Tasks: 3 (limit: 2291) Memory: 5.0M CPU: 125ms CGroup: /system.slice/gdm.service └─1915 /usr/sbin/gdm3 mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Starting GNOME Display Manager... mar 28 11:47:32 vm-ubuntu-2204 systemd[1]: Started GNOME Display Manager. mar 28 11:47:32 vm-ubuntu-2204 gdm-launch-environment][1921]: pam_unix(gdm-launch-environment:session): session opened for user gdm(uid=125) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: unable to locate daemon control file mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: stashed password to try later in open session mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: pam_unix(gdm-password:session): session opened for user bertadmin(uid=1000) by (uid=0) mar 28 11:47:40 vm-ubuntu-2204 gdm-password][2290]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring mar 28 11:47:57 vm-ubuntu-2204 gdm3[1915]: Gdm: Child process -1937 was already dead. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Mar 28 11:48:17 2022 InstallationDate: Installed on 2020-01-25 (793 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-03-23 (4 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1966786 Title: login screen shown twice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961499] Re: Backup ZFS extremely slow.
I show you a screenshot of the moment the tranfer stalls ** Attachment removed: "Screenshot from 2022-02-19 19-55-54.png" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+attachment/5562212/+files/Screenshot%20from%202022-02-19%2019-55-54.png ** Attachment added: "Screenshot from 2022-02-19 20-33-01.png" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+attachment/5562213/+files/Screenshot%20from%202022-02-19%2020-33-01.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961499 Title: Backup ZFS extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961499] Re: Backup ZFS extremely slow.
I show you a screenshot of the moment the tranfer stalls ** Attachment added: "Screenshot from 2022-02-19 19-55-54.png" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+attachment/5562212/+files/Screenshot%20from%202022-02-19%2019-55-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961499 Title: Backup ZFS extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1961499] [NEW] Backup ZFS extremely slow.
Public bug reported: I weekly backup my stuff to a Pentium 4 HT on FreeBSD 13.0 and to This i5-2520M. FreeBSD on the Pentium is faster than Ubuntu 21.10 on the i5; The Pentium runs constantly at a ~92% CPU load on one thread and it succeeds in transferring the stuff at ~22Mbps. The I5 is slower and sometimes transfers at 80Mbps, but it also stops transferring for many seconds. When it stops transferring one of the CPU threads has a 100% load according to the load measurement of Conky. If I look with the task-manager the load is normal and in the expected range and it never exceeds for any thread more than 70%. All zfs datasets are lz4 compressed on all 3 sides and I use the same send and receive command only the dataset names are different :) The send command is used with the -c parameter. The same situation worked fine with ZFS 0.8. I have the unhappy feeling that the 100% load on one thread is maybe caused by emulation of an instruction not supported by the i5 and that is why conky measures it and the task-manager not. I hope you can find it or maybe 2.1.2 is better, otherwise I might have to move the i5 to FreeBSD too :) :( Here I use a modern 2TB HDD and on the Pentium 4 HDDs in two pools; one with 2 x 3.5"IDE and th other with 2 x 2.5" SATA-1. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Feb 19 19:16:53 2022 InstallationDate: Installed on 2021-10-30 (112 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: zfs-linux UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1961499 Title: Backup ZFS extremely slow. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1961499/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956882] Re: Ubuntu does not boot after upgrade to Linux 5.13-0-23
** Description changed: After the latest upgrade to Linux 5.13.0-23 the disk shows some activity, but the screen remains black and powers off. To be sure I reinstalled Ubuntu from scratch and I have the same error again. My hardware is a Ryzen 3 2200G - I only can boot from Linux 5.13.0-19. + I only can boot from Linux 5.13.0-19. On the precious installation I + could reboot from Linux 5.13.0-22, but -23 failed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 16:11:04 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-09 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956882 Title: Ubuntu does not boot after upgrade to Linux 5.13-0-23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1956882] [NEW] Ubuntu does not boot after upgrade to Linux 5.13-0-23
Public bug reported: After the latest upgrade to Linux 5.13.0-23 the disk shows some activity, but the screen remains black and powers off. To be sure I reinstalled Ubuntu from scratch and I have the same error again. My hardware is a Ryzen 3 2200G I only can boot from Linux 5.13.0-19. On the precious installation I could reboot from Linux 5.13.0-22, but -23 failed. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jan 9 16:11:04 2022 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2022-01-09 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: ubiquity Symptom: installation UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.10.10 wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1956882 Title: Ubuntu does not boot after upgrade to Linux 5.13-0-23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
The latest daily installation ISO of Ubuntu Mate from 2021-11-20 crashes each time during the installation, so I'll have to wait for a new ISO file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954597] Re: Application Indicators in panel missing after weekend updates
see journal file ** Attachment added: "journal" https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1954597/+attachment/5547689/+files/journal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954597 Title: Application Indicators in panel missing after weekend updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1954597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
I have tried some other configuration and added those to the overviews: DT = DeskTop and LT = LapTop. a) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 21.10 -> virt- manger/qemu -> Ubuntu14.04 b0) LT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Mate -> virt-manger/qemu -> Ubuntu14.04 b1) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Mate -> virt-manger/qemu -> Ubuntu14.04 b2) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Mate -> GNOME-BOXES -> Ubuntu14.04 b3) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Mate -> virt-manger/qemu -> Peppermint 10 c1) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Budgie -> GNOME-BOXES -> Ubuntu14.04 c2) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Budgie -> virt-manger/qemu -> Ubuntu14.04 d1) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 -> virtualbox -> Ubuntu14.04 d2) DT -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 -> virt-manger/qemu -> Ubuntu14.04 Only b0 and b1 are very slow, all other configurations work fine. The newest configurations are b0; b2; b3; c2 and d2. b0) I backup my VMs weekly to my laptop and despite the only 8GB of memory, I tried the b1 configuration on my Sandy-Bridge laptop. The result was worse than on the Ryzen, because my laptop CPU (i5-2520M) is 2 to 3 times slower. Without any inputs to the DT the CPU load in idle is 80% caused mainly by compiz and it takes 1 minute to start the terminal. I have addedd that as b0. b3) I also have Peppermint 10 as qcow2 file,so I tried Peppermint. I have added that configuration as b3 and that configuration b3 was fine, I would even call it responsive :) Summary: I only have a problem with the combination Ubuntu Mate 22.04 and Ubuntu 14.04, all other combinations are fine. Maybe the animations in Ubuntu Mate 22.04 and Ubuntu 14.04 do bite each other. I'm downloading the latest Ubuntu Mate 22.04 ISO and I will reinstall configuration b1 from scratch tomorrow, to eliminate any installation problems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1954597] [NEW] Application Indicators in panel missing after weekend updates
Public bug reported: The application indicators in the panel for Whatsie and Caprine are missing after the updates in this weekend, see screenshot. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: XFCE Date: Sun Dec 12 12:26:31 2021 InstallationDate: Installed on 2021-10-28 (44 days ago) InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211026) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade jammy ** Attachment added: "Screenshot_2021-12-12_12-22-59.png" https://bugs.launchpad.net/bugs/1954597/+attachment/5547101/+files/Screenshot_2021-12-12_12-22-59.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1954597 Title: Application Indicators in panel missing after weekend updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1954597/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
Using your syntax: a) PC -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 21.10 -> virt-manger/qemu -> Ubuntu14.04 b) PC -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Mate -> virt-manger/qemu -> Ubuntu14.04 c) PC -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 Budgie -> GNOME-BOXES -> Ubuntu14.04 d) PC -> Ubuntu 21.10 -> Virtualbox 6.1.30 -> Ubuntu 22.04 -> virtualbox -> Ubuntu14.04 only b is slow, a, c and d are fine. If a to b is not a regression, maybe the Mate desktop is the issue. This weekend I will add gnome-boxes to b and virt-manger/qemu to c and d and let's see what happens. In my understanding up to now, kvm is the hypervisor in a,b and c, while the virtual-machine- manager and gnome boxes are used to set-up the configuration parameters used by kvm. I had the idea that qemu is the older hypervisor, that also can take care of CPUs without virtualization support, but that uses kvm for CPUs with virtualization support. Where can I read about the architecture of virt-manager/qemu/kvm and gnome- boxes/qemu?/kvm Do you have other suggestions for tests? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
Forget about the last screenshot, it is difficult to understand, because Ubuntu 14.04 is running in "full screen" mode in the Ubuntu 22.04 windows. Ubuntu added that QEMU/KVM label, I have no clue why. That screenshot has only been added to show the display settings. My description is correct and "Ubuntu 21.10+Virtualbox 6.1.30" run on the bare metal a Ryzen 3 2200G! They are both running on bare metal, since vboxdrv.ko and other vbox modules run in the kernel. The highest level is always Ubuntu 14.04. The intermediate level runs different different configurations like: - Ubuntu Mate 22.04 runs virt-manager/kvm and this one is extremely slow. - Ubuntu Budgie 22.04 runs gnome-boxes/kvm and this one is OK. on this intermediate level I did not mention it, but I also run: - Ubuntu 22.04 runs Virtualbox 6.1.30 and this one is OK. To proof that it is regression I already added: - Ubuntu 21.10 + virt-manager/kvm and this one is OK too. I have no other GPUs, but I have a 2011 HP Elitebook 8460p with integrated graphics and exactly the same VMs. However it will be difficult/impossible to run nested VMs, since it only has 8GB of DDR3. I have switched off 3D acceleration in the bare metal Virtualbox, but that had no effect. I have the feeling that the Compiz and a change in the display stack of virt-manager/kvm do cause the issue, especially since it gets terrible during the animations of Compiz, but also without those animations it is bad. Normally I would move the nested virtualization one level down and install virt-manager/kvm on bare metal, but there I run Ubuntu 21.10 and that release does not have that problem. If you have ideas for other tests? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
A screenshot with the most relevant virt-manager settings is added. I tried again all my nested virtual machines settings. An overview of my configurations: NOK: Ubuntu 21.10+Virtualbox 6.1.30 -> Ubuntu 22.04 Mate with Virt-Manager+KVM -> Ubuntu 14.04 OK : Ubuntu 21.10+Virtualbox 6.1.30 -> Ubuntu 22.04 Budgie with Gnome Boxes -> Ubuntu 14.04 OK : Ubuntu 21.10+Virtualbox 6.1.30 -> Ubuntu 21.10 with Virt-Manager+KVM -> Ubuntu 14.04 All Ubuntu 14.04 are the same VM qcow2 image. Both settings of the virt- manager are exactly the same with respect to the displays. Note that the differences in response times between OK and NOK are higher than a factor 10. ** Attachment added: "Screenshot from 2021-12-08 11-43-43.png" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+attachment/5546319/+files/Screenshot%20from%202021-12-08%2011-43-43.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] Re: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
See 2nd screenshot ** Attachment added: "Screenshot from 2021-12-08 10-18-39.png" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+attachment/5546300/+files/Screenshot%20from%202021-12-08%2010-18-39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953628] [NEW] Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10
Public bug reported: I always run qemu in nested virtualization on top of Virtualbox. It always worked OK till I tried Jammy Jellyfish. Note that Ubuntu 22.04 runs the same configuration much slower that 21.04 and 21.10. The issue is caused by Compiz in Ubuntu 14.04 or by qemu-system-x86 in Ubuntu 22.04 or the compatibility between the two. See the two screenshots. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: qemu-system-x86 1:6.0+dfsg-2expubuntu4 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Wed Dec 8 10:25:40 2021 InstallationDate: Installed on 2021-10-27 (41 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211027) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=06e98806-67da-4b12-847f-de92360fcc5c ro quiet splash SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:sku:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "Screenshot from 2021-12-08 10-24-55.png" https://bugs.launchpad.net/bugs/1953628/+attachment/5546285/+files/Screenshot%20from%202021-12-08%2010-24-55.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953628 Title: Too high CPU load in qemu-system-x86 compared to Ubuntu 21.04/21.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1953628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1953621] [NEW] Virtualbox 6.1.30 missing dependency libvpx6
Public bug reported: Installation of the latest Virtualbox impossible due to missing dependency, see added screenshot. That package can't be loaded with apt. "sudo apt install libvpx6" says: Package libvpx6 is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source. Note that I could install an earlier version of Virtualbox 6.1.29 on an earlier version of Jammy Jellyfish without any issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: virtualbox (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu74 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Dec 8 09:49:55 2021 InstallationDate: Installed on 2021-10-26 (42 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211024) SourcePackage: virtualbox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: virtualbox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session ** Attachment added: "Screenshot from 2021-12-08 09-59-38.png" https://bugs.launchpad.net/bugs/1953621/+attachment/5546279/+files/Screenshot%20from%202021-12-08%2009-59-38.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1953621 Title: Virtualbox 6.1.30 missing dependency libvpx6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1953621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1952836] Re: Suspend not working after update to Linux 5.13.0-22
Agreed happened after the linux upgrade, so I selected dist-upgrade in the ubuntu-bug menu because that seemed closest, since I sometimes used apt dist-upgrade for a normal upgrade too. On Wed, 2021-12-01 at 12:07 +, Chris Guiver wrote: > The release-upgrade to 21.10 occurred 47 days ago, so your issue > (filed > against the release-upgrader tool that moved you to 21.10 from 21.04) > is > unlikely the issue, it's more likely related to a kernel upgrade. > > ** Package changed: ubuntu-release-upgrader (Ubuntu) => linux > (Ubuntu) > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952836 Title: Suspend not working after update to Linux 5.13.0-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1952836] [NEW] Suspend not working after update to Linux 5.13.0-22
Public bug reported: I use suspend frequently, but after the last update of Linux, the restart fails. However it seems to work partly since the disk activity light is showing activities, but the screen remains black and without power. I have to power off the system by pressing the power-off button for 10 seconds. I suspended the system at 1:35 and I will include the /var/log/kern.log I hope it helps. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-release-upgrader-core 1:21.10.8 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Dec 1 01:41:18 2021 InstallationDate: Installed on 2021-10-09 (52 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to impish on 2021-10-14 (47 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade impish third-party-packages wayland-session ** Attachment added: "kern.log" https://bugs.launchpad.net/bugs/1952836/+attachment/5544519/+files/kern.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1952836 Title: Suspend not working after update to Linux 5.13.0-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1952836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950770] [NEW] No permission to destroy snapshot on USERDATA
Public bug reported: For years I destroyed my snapshots as indicated, but in this specific case it does NOT work anymore. See copy of command: bertadmin@Host-R3:~$ zsysctl show Name: rpool/ROOT/ubuntu_57vi20 ZSys: true Last Used: current History: - Name: rpool/ROOT/ubuntu_57vi20@21-linux13-21 Created on: 2021-11-11 22:43:53 - Name: rpool/ROOT/ubuntu_57vi20@211019-proposed13-20 Created on: 2021-10-19 13:52:04 Users: - Name:bertadmin History: - rpool/USERDATA/bertadmin_vz8u5n@21-linux13-21 (2021-11-11 22:43:53) - rpool/USERDATA/bertadmin_vz8u5n@211019-proposed13-20 (2021-10-19 13:52:04) - rpool/USERDATA/bertadmin_vz8u5n@211015-proposed13-19 (2021-10-15 19:06:21) - Name:root History: - rpool/USERDATA/root_vz8u5n@21-linux13-21 (2021-11-11 22:43:53) - rpool/USERDATA/root_vz8u5n@211019-proposed13-20 (2021-10-19 13:52:04) bertadmin@Host-R3:~$ sudo zfs destroy rpool/USERDATA/bertadmin_vz8u5n@211015-proposed13-19 cannot destroy snapshot rpool/USERDATA/bertadmin_vz8u5n@211015-proposed13-19: dataset is busy The snapshots are taken with "zsysctl save". Note that I can destroy the autozsys snapshots without issues in this way. Note that even after the reboot using the recovery entry with the root directory, I can't delete the snapshot and I tried the same with another system booting for an ext4 disk. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: udisks2 2.9.4-1 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: hide-partitions.rules 70-snap.firefox.rules 70-snap.snapd.rules 70-snap.snap-store.rules 60-vboxdrv.rules Date: Fri Nov 12 07:01:41 2021 InstallationDate: Installed on 2021-10-09 (33 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-21-generic root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1 SourcePackage: udisks2 Symptom: storage Title: No permission to access files on storage device UpgradeStatus: Upgraded to impish on 2021-10-14 (28 days ago) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.50 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: udisks2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950770 Title: No permission to destroy snapshot on USERDATA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1950770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950768] [NEW] zfsutils-linux does not allow to report bugs
Public bug reported: I had two datapools on the same HDD (one for VMs and one for archives) and every month scrubbing those datapools started on the same moment in time. The first datapool has been striped with another smaller HDD. I did not like it , so I changed /etc/cron.d/zfsutils line 6 and 7 as follows: FROM: # Scrub the second Sunday of every month. 24 0 8-14 * * root if [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]; then /usr/lib/zfs-linux/scrub; fi TO: # Scrub the second Sunday of every month. 24 0 8-14 * * root if [ $(date +\%w) -eq 0 ] && [ -x /usr/lib/zfs-linux/scrub ]; then /home/bertadmin/b-scrub.sh; fi Ubuntu-bug detected the change, asked whether that zfsutils script should be incorporated and afterwards refused to report the bug, because zfs had been changed and I had to revert the change. After I reverted the change copying zfsutils script back from .zfs/snapshots, the system still refused to report ubuntu-bugs. I did the same change in Ubuntu 21.04 and I never had a problem with it. The original script might be fine for most cases, but is is slowing down the whole scrub process considerably, if you have two datapools on the same HDD. Why ask whether the change should be incorporated and afterwards refuse the report any bugs even when the change has been undone. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 12 06:29:20 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-10-09 (33 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to impish on 2021-10-14 (28 days ago) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.04.19 wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950768 Title: zfsutils-linux does not allow to report bugs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1950768/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1950687] [NEW] Crash in virt manager using virtio 3D-acceleration and OpenGL
Public bug reported: The system was very slow in QXL due to the animation in the Ubuntu 14.04 VM, so I tried to enable 3D acceleration in virt-manager. The result is: Error starting domain: internal error: process exited while connecting to monitor: qemu_gl_create_compile_shader: compile vertex error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile fragment error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile vertex error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES qemu_gl_create_compile_shader: compile fragment error 0:2(10): error: GLSL ES 3.00 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper callback(asyncjob, *args, **kwargs) File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb callback(*args, **kwargs) File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn ret = fn(self, *args, **kwargs) File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in startup self._backend.create() ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: virt-manager 1:3.2.0-3 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu73 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu Nov 11 16:47:57 2021 InstallationDate: Installed on 2021-10-27 (15 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211027) 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 jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950687 Title: Crash in virt manager using virtio 3D-acceleration and OpenGL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1950687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949613] [NEW] Fast flicker of top-panel and ubuntu-dock
Public bug reported: As soon as I use a video or virtual machine in full screen the ubuntu- dock and top-panel start to flicker fast and annoying and break through the video or virtual machine display. It will stop after using the mouse or keyboard a few times. I have the issue on this computer, but also on my laptop a HP Elitebook 8460p with an i5-2520M and Intel HD Graphics 3000 (SNB GT2). Both run Ubuntu 21.10 and the problem occurs in Wayland and Xorg. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Nov 3 12:31:23 2021 InstallationDate: Installed on 2021-10-09 (24 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to impish on 2021-10-14 (20 days ago) ** Affects: ubuntu Importance: Undecided Status: New ** Tags: amd64 apport-bug impish wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949613 Title: Fast flicker of top-panel and ubuntu-dock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1949613/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949252] Re: Ubuntu installed with wrong ZFS partition alignment for 4k HDD
On Friday and Saturday I tried to improve boot times, but I destroyed the installation in the process. I reinstalled the system on ext4, still using zfs for my data. Booting from ext4 solved my issue, I now boot the system in ~40 seconds instead of 4 minutes. I did find out, that it was not a "simple" alignment issue like I thought writing the bug report, so I think you can dump this confusing bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949252 Title: Ubuntu installed with wrong ZFS partition alignment for 4k HDD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1949252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949252] Re: Ubuntu installed with wrong ZFS partition alignment for 4k HDD
** Description changed: Using: Ubuntu 21.10 and OpenZFS 2.0. I did the standard ZFS install of Ubuntu. - I had terrible bad response times from my brand new 2 TB Seagate STM2000M007 HDD, sometimes it takes 5 seconds or so to start the terminal and the system boots in 4 minutes from the HDD. I installed Ubuntu 21.10 on OpenZFS 2.0.6 and that combination on that HDD did cause that awful performance. It is a normal laptop drive at 5400 rpm. Its sequential read/write speeds are ~140MB/s while its seek times are ~13 msec. + I had terrible bad response times from my brand new 2 TB Seagate STM2000M007 HDD, sometimes it takes 5 seconds or so to start the terminal and the system boots in 4 minutes from the HDD. I installed Ubuntu 21.04 on OpenZFS 2.0.2 and upgrade to Ubuntu 21.10 on OpenZFS 2.0.6 and both combinations on that HDD did cause that awful performance. It is a normal laptop drive at 5400 rpm. Its sequential read/write speeds are ~140MB/s while its seek times are ~13 msec. The measurement with gnome disk utility confirmed those values from the specification, the throughput on ZFS was ~120MB/s, but the difference could be caused by the latency of the 10 year old i5-2520M (2C4T; 2.5/3.2GHz). The disk SMART data was OK. Everything seems normal, ashift is set to 12 and the HDD has 4096 Byte physical sectors and 512 Byte logical sectors. All partitions are starting on 2048 boundaries of UEFI. I had been thinking about misalignment, because the throughput as measured by Conky was a factor 2 larger than measured by ZFS itself (zpool iostat). The disk read-out is Disk /dev/sdd: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: 007-1R8174 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F4581F88-2B2E-4C16-8D73-E55EC05CF987 Device Start End Sectors Size Type /dev/sdd1 2048 4095 2048 1M BIOS boot /dev/sdd2 4096 1054719 1050624 513M EFI System /dev/sdd3 1054720 5249023 4194304 2G Linux swap /dev/sdd4 5249024 9443327 4194304 2G Solaris boot /dev/sdd5 9443328 3907029134 3897585807 1.8T Solaris root Many partitions start on the 2048 Byte boundary or a multiple thereof, which means that you have a misalignment and you double the number of IO Operations needed to read/write ZFS records. The last ROOT partitions starts at 4k sector number 2305½. In my opinion a serious bug in the ZFS implementation of Ubuntu, however most people will not have the issue, because they run mostly from 512 Byte aligned SSDs or nvme-SSDs. I think it should be a general rule on 4k HDDs and SSHDs you should align partitions on 4K boundaries. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949252 Title: Ubuntu installed with wrong ZFS partition alignment for 4k HDD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1949252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1949252] [NEW] Ubuntu installed with wrong ZFS partition alignment for 4k HDD
Public bug reported: Using: Ubuntu 21.10 and OpenZFS 2.0. I did the standard ZFS install of Ubuntu. I had terrible bad response times from my brand new 2 TB Seagate STM2000M007 HDD, sometimes it takes 5 seconds or so to start the terminal and the system boots in 4 minutes from the HDD. I installed Ubuntu 21.04 on OpenZFS 2.0.2 and upgrade to Ubuntu 21.10 on OpenZFS 2.0.6 and both combinations on that HDD did cause that awful performance. It is a normal laptop drive at 5400 rpm. Its sequential read/write speeds are ~140MB/s while its seek times are ~13 msec. The measurement with gnome disk utility confirmed those values from the specification, the throughput on ZFS was ~120MB/s, but the difference could be caused by the latency of the 10 year old i5-2520M (2C4T; 2.5/3.2GHz). The disk SMART data was OK. Everything seems normal, ashift is set to 12 and the HDD has 4096 Byte physical sectors and 512 Byte logical sectors. All partitions are starting on 2048 boundaries of UEFI. I had been thinking about misalignment, because the throughput as measured by Conky was a factor 2 larger than measured by ZFS itself (zpool iostat). The disk read-out is Disk /dev/sdd: 1.82 TiB, 2000398934016 bytes, 3907029168 sectors Disk model: 007-1R8174 Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F4581F88-2B2E-4C16-8D73-E55EC05CF987 Device Start End Sectors Size Type /dev/sdd1 2048 4095 2048 1M BIOS boot /dev/sdd2 4096 1054719 1050624 513M EFI System /dev/sdd3 1054720 5249023 4194304 2G Linux swap /dev/sdd4 5249024 9443327 4194304 2G Solaris boot /dev/sdd5 9443328 3907029134 3897585807 1.8T Solaris root Many partitions start on the 2048 Byte boundary or a multiple thereof, which means that you have a misalignment and you double the number of IO Operations needed to read/write ZFS records. The last ROOT partitions starts at 4k sector number 2305½. In my opinion a serious bug in the ZFS implementation of Ubuntu, however most people will not have the issue, because they run mostly from 512 Byte aligned SSDs or nvme-SSDs. I think it should be a general rule on 4k HDDs and SSHDs you should align partitions on 4K boundaries. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Package changed: conky (Ubuntu) => ubiquity (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949252 Title: Ubuntu installed with wrong ZFS partition alignment for 4k HDD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1949252/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
I did run an update of only one file and I did install another application. Rebooting and reverting back to the last snapshot did work as expected. The application has been removed and I could rerun the update again. According to the Internet the next commands would stop all autozsys snapshots systemctl --user stop zsys-user-savestate.timer systemctl --user disable zsys-user-savestate.timer sudo mv /etc/apt/apt.conf.d/90_zsys_system_autosnapshot /etc/apt/apt.conf.d /90_zsys_system_autosnapshot_disabled but I still have collected a lot of autozsys snapshots, see next list rpool/USERDATA/bertadmin_9ykbc6@211015-proposed 2.08M - 177M - rpool/USERDATA/bertadmin_9ykbc6@autozsys_h1yy2t 92K - 176M - rpool/USERDATA/bertadmin_9ykbc6@211017-proposed 84K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_6g35l0456K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_501rmb520K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_jr1n7t488K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_m29pbs480K - 176M - rpool/USERDATA/bertadmin_g64ltk@autozsys_4h79sx356K - 175M - rpool/USERDATA/root_9ykbc6@211015-proposed 72K - 812K - rpool/USERDATA/root_9ykbc6@211017-proposed 0B - 812K - Did I make an error or should I produce another bug-report? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947514] [NEW] Wish to specify the size of the rpool datapool/partition during installation
Public bug reported: I like to be able to specify the size of the rpool partition during installation at the moment I select ZFS, you could ask to specify the size or to use the whole disk. The remainder of the disk could be left empty. I like that feature for the following reasons: - Many users like me will have a SSD and a HDD, limiting the size of the rpool partition will allow them to use part of the SSD as a L2ARC/ZIL for the HDD. - My current laptop HDD is 2TB and a rpool partition of 2TB makes Ubuntu very slow, when after a while the HDD gets fragmented. Due to OS updates the OS gets scattered all over the HDD resulting in considerable longer HDD seek times. A smaller rpool datapool (I would choose say 10GB) would speed up the OS on the HDD. - It would allow us to use the gnome-disk-utility as simple backup of last resort for the EFI, rpool and bpool partitions. For my laptop and desktop I could store those two backups for example on an old 160GB USB HDD. - I don't like to store my VMs in the USERDATA dataset nor in another own dataset in the rpool datapool. However on the desktop I like them on the nvme-SSD, but preferably in an own datapool with own properties. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Oct 17 12:25:05 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- InstallationDate: Installed on 2021-10-09 (7 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: ubiquity Symptom: installation UpgradeStatus: Upgraded to impish on 2021-10-14 (3 days ago) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubiquity-21.04.19 wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947514 Title: Wish to specify the size of the rpool datapool/partition during installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1947514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947461] Re: OpenZFS 2.06 does not send empty snapshots
** Description changed: - Since 2019 I run scripts to incrementally backup my zfs snapshots. In OpenZFS 2.06 it refuses to send empty snapshots. - It is a serious problem because in the end each dataset will have a different last snapshots and I have to do every backup of every dataset by hand or I have to move a dummy file to each dataset before snapshotting it. - - For the details see the screenshot and note that I run on proposed - Ubuntu 21.10 due to issue with zsys :( + CAN BE CANCELLED, MY ERROR ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 13:15:42 2021 InstallationDate: Installed on 2021-10-09 (6 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: zfs-linux UpgradeStatus: Upgraded to impish on 2021-10-14 (2 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Changed in: zfs-linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947461 Title: OpenZFS 2.06 does not send empty snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947461] [NEW] OpenZFS 2.06 does not send empty snapshots
Public bug reported: Since 2019 I run scripts to incrementally backup my zfs snapshots. In OpenZFS 2.06 it refuses to send empty snapshots. It is a serious problem because in the end each dataset will have a different last snapshots and I have to do every backup of every dataset by hand or I have to move a dummy file to each dataset before snapshotting it. For the details see the screenshot and note that I run on proposed Ubuntu 21.10 due to issue with zsys :( ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zfsutils-linux 2.0.6-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Oct 16 13:15:42 2021 InstallationDate: Installed on 2021-10-09 (6 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: zfs-linux UpgradeStatus: Upgraded to impish on 2021-10-14 (2 days ago) modified.conffile..etc.sudoers.d.zfs: [inaccessible: [Errno 13] Permission denied: '/etc/sudoers.d/zfs'] ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish package-from-proposed third-party-packages wayland-session ** Attachment added: "Screenshot from 2021-10-16 13-12-39.png" https://bugs.launchpad.net/bugs/1947461/+attachment/5533505/+files/Screenshot%20from%202021-10-16%2013-12-39.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947461 Title: OpenZFS 2.06 does not send empty snapshots To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947461/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] Re: zfs fails reverting to a previous snapshot on reboot when selected on grub
The change worked on my PC. The difference has been tested with limited changes to my userdata, but I try tomorrow with the next set of updates. The current snapshots are: bertadmin@VM-Xubuntu-2110:~$ zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT bpool/BOOT/ubuntu_q3cgtj@211015-proposed56K - 78.6M - rpool/ROOT/ubuntu_q3cgtj@211015-proposed 54.0M - 3.51G - rpool/ROOT/ubuntu_q3cgtj/srv@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/usr@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/usr/local@211015-proposed 0B - 144K - rpool/ROOT/ubuntu_q3cgtj/var@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/games@211015-proposed 0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/lib@211015-proposed 300K - 33.6M - rpool/ROOT/ubuntu_q3cgtj/var/lib/AccountsService@211015-proposed56K - 100K - rpool/ROOT/ubuntu_q3cgtj/var/lib/NetworkManager@211015-proposed104K - 140K - rpool/ROOT/ubuntu_q3cgtj/var/lib/apt@211015-proposed 0B - 79.6M - rpool/ROOT/ubuntu_q3cgtj/var/lib/dpkg@211015-proposed 256K - 37.9M - rpool/ROOT/ubuntu_q3cgtj/var/log@211015-proposed 416K - 71.3M - rpool/ROOT/ubuntu_q3cgtj/var/mail@211015-proposed0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/snap@211015-proposed0B - 96K - rpool/ROOT/ubuntu_q3cgtj/var/spool@211015-proposed 72K - 112K - rpool/ROOT/ubuntu_q3cgtj/var/www@211015-proposed 0B - 96K - rpool/USERDATA/bertadmin_g64ltk@211015-proposed 1.91M - 177M - rpool/USERDATA/bertadmin_g64ltk@autozsys_6g35l0128K - 176M - rpool/USERDATA/root_g64ltk@211015-proposed 8K - 812K - bertadmin@VM-Xubuntu-2110:~$ That autosys snapshot has been created automatically the first time I did run the next script to create a snapshot: zsysctl save $1 -s zfs list -t snapshot | grep rpool zfs list -t snapshot | grep bpool According to the Internet the next commands would stop all autosys snapshots systemctl --user stop zsys-user-savestate.timer systemctl --user disable zsys-user-savestate.timer sudo mv /etc/apt/apt.conf.d/90_zsys_system_autosnapshot /etc/apt/apt.conf.d /90_zsys_system_autosnapshot_disabled Did I make an error or is it another bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zfs fails reverting to a previous snapshot on reboot when selected on grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
Yesterday evening I upgraded my laptop to Ubuntu 20.10, so today I tried the same on my HP Elitebook 8460p laptop based on an i5-2520M and there conky displayed as I expected. Also I had no flickering of top-bar and Ubuntu dock with VMs or videos in full screen. By the way that flickering also occurs with Xorg in my Ryzen 3 2200G. Maybe we have to spit both issues in 2 bug reports? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
The Weston try out is irrelevant. In Weston Conky refuses to start and gives an error message about the display and it does it all the time. I use transparency and for that, conky requires a compositor, see the following text about that setting: own_window_argb_visual ARGB can be used for real transparency, note that a composite manager is required for real transparency. Weston does not have a compositor, so it does not run at all. I run Ubuntu 21.10 also in a Virtualbox VM since 5 months and there Conky displays normally. Everything is fine.The difference between both installations the Ryzen 3 2200G and the Virtualbox VM are the drivers from AMD or Virtualbox. I have another anomaly, which I did not report yet, when I display a VM or a video in full screen, the top bar and Ubuntu-dock of the Host (Ubuntu 20.10 flicker strongly through the full screen display of e.g. Ubuntu; Windows or videos. Fortunately it stops, when I left and right click with the mouse a few times. That issue is also new since 21.10 and it only happens on the Ryzen and not in a Virtualbox. In general I have issues with the display of stuff at the border of the screen. Both the Ubuntu-dock and Conky use transparency. Again the difference between both systems the Ryzen 3 2200G and the Virtualbox VM are the drivers from AMD or Virtualbox. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947185] Re: GNOME on Wayland does not initially display conky output
I do not expect the error is in conky: 1. The error does not appear, when I login with xorg. The error did not appear in 21.04. 2. The conky window is of course somewhat outside of the standard application windows; It has no windows boundaries, the background of the window is transparent and it is in the bottom right corner. 3. The following bypass in the login script worked; #!/bin/bash sleep 2 conky -d sleep 1 killall conky sleep 1 conky -d The first time the windows is not displayed but conky is started, the second time conky is started and the display is perfect. For conky there is no difference between both starts, for wayland there is probably a difference. The sleep time has no influence, since I also tried the first one with 8 seconds and that did not help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: GNOME on Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/conky/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947187] Re: [amdgpu] Graphics corruption during modal dialog dimming on Xorg
No the gsettings did not help, also not after a reboot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947187 Title: [amdgpu] Graphics corruption during modal dialog dimming on Xorg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1947187] [NEW] Running in xorg unreadable firefox password request
Public bug reported: If I use xorg and Firefox asks for the master password that small window is unreadable and distorted. See the screenshot. If I type in the password blindly everything is working again. The problem does not exist with Wayland, but that one has another issue :( ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 13:14:41 2021 DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2021-10-09 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.50 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu ** Attachment added: "Screenshot from 2021-10-14 13-13-48.png" https://bugs.launchpad.net/bugs/1947187/+attachment/5532922/+files/Screenshot%20from%202021-10-14%2013-13-48.png ** Description changed: If I use xorg and Firefox asks for the master password that small window - is unreadable and distorted. See the screenshot. The problem does not - exist with Wayland, but that one has another issue :( + is unreadable and distorted. See the screenshot. If I type in the + password blindly everything is working again. The problem does not exist + with Wayland, but that one has another issue :( ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 13:14:41 2021 DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: - Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) -Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] + Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) + Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on
[Bug 1947185] [NEW] Wayland does not initially display conky output
Public bug reported: Starting Ubuntu with wayland does not initially display the .conkyrc file. Only after a change in that file, conky restarts the display and .conkyrc is displayed. Conky has been started according to the system monitor. I doubled the time before starting conky, but that did not help. If I change the display to xorg, .conkyrc displays directly as expected. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: libwayland-bin (not installed) ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 12:58:20 2021 DistUpgraded: 2021-10-14 11:46:37,562 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] InstallationDate: Installed on 2021-10-09 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_57vi20@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_57vi20 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: Upgraded to impish on 2021-10-14 (0 days ago) dmi.bios.date: 03/12/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.50 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.50:bd03/12/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ubuntu wayland-session -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1947185 Title: Wayland does not initially display conky output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1947185/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] [NEW] zsys fail during reboot
Public bug reported: After creating a snapshot with: zsysctl save 211012-linux13-19 -s the reboot fails as shown on the screenshot, the other screenshot shows the result of the snapshot. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: zsys 0.5.8 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Tue Oct 12 19:11:43 2021 InstallationDate: Installed on 2021-10-12 (0 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Mounts: Error: [Errno 40] Too many levels of symbolic links: '/proc/mounts' ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_zgtuq6@/vmlinuz-5.13.0-19-generic root=ZFS=rpool/ROOT/ubuntu_zgtuq6 ro quiet splash RelatedPackageVersions: zfs-initramfs 2.0.6-1ubuntu2 zfsutils-linux 2.0.6-1ubuntu2 SourcePackage: zsys SystemdFailedUnits: UpgradeStatus: No upgrade log present (probably fresh install) ZFSImportedPools: NAMESIZE ALLOC FREE CKPOINT EXPANDSZ FRAGCAP DEDUPHEALTH ALTROOT bpool 768M 79.2M 689M- - 0%10% 1.00xONLINE - rpool14G 3.33G 10.7G- - 1%23% 1.00xONLINE - ZFSListcache-bpool: bpool /boot off on on off on off on off - none- - - - - - - - bpool/BOOT noneoff on on off on off on off - none- - - - - - - - bpool/BOOT/ubuntu_zgtuq6 /boot on on on off on off on off - none- - - - - - - - ZSYSJournal: -- Journal begins at Tue 2021-10-12 18:10:37 AST, ends at Tue 2021-10-12 19:11:52 AST. -- -- No entries -- modified.conffile..etc.apt.apt.conf.d.90_zsys_system_autosnapshot: [deleted] ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "Screenshot error message" https://bugs.launchpad.net/bugs/1946808/+attachment/553/+files/Screenshot%20from%202021-10-12%2016-57-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zsys fail during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1946808] Re: zsys fail during reboot
Another screenshot with zfs list - t snapshot and some info in Conky ** Attachment added: "Screenshot from 2021-10-12 19-07-50.png" https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1946808/+attachment/5532237/+files/Screenshot%20from%202021-10-12%2019-07-50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946808 Title: zsys fail during reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1946808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940726] Re: Network-Manager.services are all masked after last update
The third try did succeed using the update manager, that went to a partial update like the first time, but this time it worked. The difference between both times was, that in the update from Wednesday to Thursday, the update of ppp did not happen, it was in the list of updates, but not selected to be updated (v). The next update from Thursday to Friday caused the network to fail afterwards. The problem seems related to some sequence issue in the updates. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940726 Title: Network-Manager.services are all masked after last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1940726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940726] Re: Network-Manager.services are all masked after last update
** Description changed: After the update from Thursday 19-8 to Friday 20-8 the network stopped working. I restored the system to the state of a week ago and retried the update using: - the update manager - apt dist-upgrade The network does not work, because all 3 network-manager.services are masked and thus is it impossible to start them even by hand. - During the install process I saw an error message about a missing file related to inetd. + During the install process I saw an error message about a missing config file related to inetd. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.32.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Aug 20 21:36:40 2021 InstallationDate: Installed on 2021-05-06 (106 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210506) IpRoute: - default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 - 169.254.0.0/16 dev enp0s3 scope link metric 1000 - 192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.126 metric 100 + default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 + 169.254.0.0/16 dev enp0s3 scope link metric 1000 + 192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.126 metric 100 IwConfig: - lono wireless extensions. - - enp0s3no wireless extensions. + lono wireless extensions. + + enp0s3no wireless extensions. NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true RfKill: - + SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME - Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb ethernet 1629509674 vie 20 ago 2021 21:34:34 yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection + NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME + Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb ethernet 1629509674 vie 20 ago 2021 21:34:34 yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: - DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH - enp0s3 ethernet connected full full /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb /org/freedesktop/NetworkManager/ActiveConnection/1 - lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- + DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH + enp0s3 ethernet connected full full /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb /org/freedesktop/NetworkManager/ActiveConnection/1 + lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.32.2 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.32.2 connected started full enabled enabled enabled enabled enabled -- You received this bug notification
[Bug 1940726] [NEW] Network-Manager.services are all masked after last update
Public bug reported: After the update from Thursday 19-8 to Friday 20-8 the network stopped working. I restored the system to the state of a week ago and retried the update using: - the update manager - apt dist-upgrade The network does not work, because all 3 network-manager.services are masked and thus is it impossible to start them even by hand. During the install process I saw an error message about a missing file related to inetd. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: network-manager 1.32.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1 Uname: Linux 5.13.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Aug 20 21:36:40 2021 InstallationDate: Installed on 2021-05-06 (106 days ago) InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210506) IpRoute: default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.126 metric 100 IwConfig: lono wireless extensions. enp0s3no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REALAUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb ethernet 1629509674 vie 20 ago 2021 21:34:34 yes -999 no /org/freedesktop/NetworkManager/Settings/1 yes enp0s3 activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/Wired connection 1.nmconnection nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH enp0s3 ethernet connected full full /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 f23270a0-5ecf-3402-8b63-2441ddf18edb /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.32.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940726 Title: Network-Manager.services are all masked after last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1940726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1936012] [NEW] Mate-Dock completely disappears
Public bug reported: After loading the OS on the first mouse action on the desktop, the mate- dock of munity completely disappears from the desktop. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: mate-dock-applet (not installed) ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Jul 13 21:21:09 2021 InstallationDate: Installed on 2021-05-09 (65 days ago) InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Alpha amd64 (20210508) SourcePackage: mate-dock-applet UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mate-dock-applet (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1936012 Title: Mate-Dock completely disappears To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mate-dock-applet/+bug/1936012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931300] [NEW] Nautilus mounts Google-drive while the Internet is down.
Public bug reported: This bug report is produced with a working internet of course. The problem occurred when my local network was still working fine, but the connection to the Internet was lost due to a failing Ethernet cable from my local network router to the ISP router. I mount the Google Drive at each login as follows: sh -c "rclone --vfs-cache-mode writes mount Google-drive: /media/Google-drive". Always it works fine, except with the failing cable. The Google drive has been shown after 25 seconds of by Nautilus, despite a completely missing connection with the Internet. It took Nautilus 25 seconds to display its window the first time. My Google drive has according to Conky now 1 PiB :) and it is impossible to dismount the Google Drive, for details see the screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: nautilus 1:3.38.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 8 15:35:16 2021 InstallationDate: Installed on 2019-11-30 (556 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: Upgraded to hirsute on 2021-03-24 (75 days ago) usr_lib_nautilus: evince40.1-1 file-roller 3.38.1-1 nautilus-extension-gnome-terminal 3.38.1-1ubuntu1 nautilus-share0.7.3-2ubuntu3 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Screenshot from 2021-06-04 04-56-54.png" https://bugs.launchpad.net/bugs/1931300/+attachment/5503235/+files/Screenshot%20from%202021-06-04%2004-56-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931300 Title: Nautilus mounts Google-drive while the Internet is down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1931300/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929598] Re: Firefox rfuses to start YouTube display
It happened again and it happened while I queued a number of video. The messages displayed were: Sandbox: attempt to open unexpected file /sys/devices/system/cpu/online Sandbox: attempt to open unexpected file /proc/stat Sandbox: attempt to open unexpected file /proc/net/unix Sandbox: attempt to open unexpected file /proc/self/maps Sandbox: attempt to open unexpected file /proc/net/unix (firefox:1428435): GLib-GObject-WARNING **: 23:44:55.801: g_object_get_is_valid_property: object class 'GdkX11DeviceCore' has no property named 'device-id' (firefox:1428435): GLib-GObject-WARNING **: 23:45:21.546: g_object_get_is_valid_property: object class 'GdkX11DeviceCore' has no property named 'device-id' -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929598 Title: Firefox rfuses to start YouTube display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929598] Re: Firefox rfuses to start YouTube display
I almost never use another browser, I use Chromium in a Xubuntu 20.04 Virtual Machine, but exclusively for WhatsApp Web. It is running constantly and I never had this problem, maybe because I never change that site. I have Microsoft Edge in an Ubuntu 20.04 VM just out of curiosity, but I almost never use it. The error occurs occasionally say once or twice per day and it happens in the middle of a session, not directly after start up. I will start up firefox from the terminal and look at error messages, when it occurs. I don't think I ever had this problem in my VMs based on 20.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929598 Title: Firefox rfuses to start YouTube display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929598] [NEW] Firefox rfuses to start YouTube display
Public bug reported: Firefox starts to build the buffer, but is does not display anything. See screenshot. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: firefox 88.0.1+build1-0ubuntu0.21.04.2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bertadmin 4040 F pulseaudio /dev/snd/pcmC1D0p: bertadmin 4040 F...m pulseaudio /dev/snd/controlC0: bertadmin 4040 F pulseaudio BuildID: 20210504152106 CasperMD5CheckResult: unknown Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue May 25 14:25:12 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2019-11-30 (542 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IpRoute: default via 192.168.1.1 dev enp7s0 proto dhcp metric 100 169.254.0.0/16 dev enp7s0 scope link metric 1000 192.168.1.0/24 dev enp7s0 proto kernel scope link src 192.168.1.106 metric 100 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:352 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=88.0.1/20210504152106 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to hirsute on 2021-03-24 (61 days ago) dmi.bios.date: 07/18/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.10 dmi.board.name: B450M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd07/18/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929598 Title: Firefox rfuses to start YouTube display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1929598] Re: Firefox rfuses to start YouTube display
** Attachment added: "Screenshot from 2021-05-25 14-24-40.png" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+attachment/5500303/+files/Screenshot%20from%202021-05-25%2014-24-40.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1929598 Title: Firefox rfuses to start YouTube display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1929598/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path
It happened after a fresh install of Ubuntu 21.04 Beta on ZFS. Only the updates have been run and I was just installing or starting to install the Virtualbox Guest Additions -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820859 Title: nautilus --version segfaults in g_application_impl_get_dbus_object_path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1820859/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1923383] [NEW] Issue with L1ARC for uncompressed datasets
Public bug reported: I have done some testing with Ubuntu 21.04 and OpenZFS. I mostly run Virtual Machines and I noticed a huge difference in performance between the VM disk IO, between the same VM stored on a lz4 compressed dataset and on an uncompressed dataset. The difference in the VM disk throughput is a factor 40 to 90 dependent on the type of disk IO test. My host OS was Ubuntu 21.04 and the Guest has been Windows 7 using ChrystalDiskMark. Looking at the the size of L1ARC that I monitored with Conky, that L1ARC size did not change, when I used the VM on an uncompressed dataset. It only flipped say ~100 MB during running that VM, so it showed 3.26 GB and seconds later 3.15 GB and it always flipped between these two values. The hosts had space enough free to increase the L1ARC. My wild guess was that the L1ARC has not been used, only the small part for uncompressed records. Maybe it is a bug, maybe a feature or maybe something else. I have a detailed description in the next discourse: https://discourse.destinationlinux.network/t/ubuntu-21-04-and-bleeding- edge-openzfs-2-0/3621/3 The interesting part is the third entry and for some context the first and second entries. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: zfsutils-linux 2.0.2-1ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 11 18:34:01 2021 InstallationDate: Installed on 2019-11-30 (498 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: zfs-linux UpgradeStatus: Upgraded to hirsute on 2021-03-24 (18 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1923383 Title: Issue with L1ARC for uncompressed datasets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1923383/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0
I'm using Ubuntu 21.04 Beta and FreeBSD 13.0-RC5 now on my desktop and backup server. I did check it and it works without any issue, even after I changed the setting I used to force compatibility. I changed the 'dnodesize' back to 'auto' from 'legacy'. Legay that I used to force compatibility. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1854982] Re: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0
I'm using Ubuntu 21.04 Beta and FreeBSD 13.0-RC5 now on my desktop and backup server. I did check it and it works without any isue, even after I changed the setting I used to force compatibility. I already added this text to the bug report. On Wed, 2021-04-07 at 13:24 +, Colin Ian King wrote: > ZFS 2.0.x is now the default for Ubuntu Hirsute 21.04. If anyone > would > like to check that this is now compatible with BSD then that would be > useful so we can close this issue. > > ** Changed in: zfs-linux (Ubuntu) >Importance: Undecided => Medium > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1854982 Title: Lost compatibilty for backup between Ubuntu 19.10 and FreeBSD 12.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1854982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921603] Re: The last update detroyed my Ubuntu boot in use since 18.04
It looks that it is a hardware problem. The sshd has a high number of not correctable read errors in the hundreds and the reallocated sector count also >100. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921603 Title: The last update detroyed my Ubuntu boot in use since 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1921603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921603] Re: The last update detroyed my Ubuntu boot in use since 18.04
** Description changed: The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, fortunately I dual boot between zfs and ext4. - My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The system has been upgraded I think through 19.04 and 19.10 to 20.04; The last system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so I thought about HW issues. Without my SSHD and also with another HDD, the system got passed the BIOS. So now I started thinking about boot issues. I downloaded boot-repair and that one repaired the ext4 install, so I was happy for a short moment. + My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The system has been upgraded I think through 19.04 and 19.10 to 20.04; The last system update of 20.04 went wrong, the system did hang in the BIOS screen, so I thought about HW issues. Without my SSHD and also with another HDD, the system got passed the BIOS. So now I started thinking about boot issues. I downloaded boot-repair and that one repaired the ext4 install, so I was happy for a short moment. Did run update-grub, but caused the zfs ubuntu to show up in the boot menu, but the system failed to boot, because it needed bootpool/BOOT, which never existed on this laptop, running update-grub in the ext install had the next result, see: bertadmin@Ubuntu-ext:~$ sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-70-generic Found initrd image: /boot/initrd.img-5.4.0-70-generic cannot open 'bpool/BOOT/mate-1804': dataset does not exist <-- Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804 Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804 cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist <-- Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804@210213-linux43 Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804@210213-linux43 /usr/sbin/grub-probe: error: unknown filesystem. Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda3 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sda4 failed: Device or resource busy Command failed. done This does not make me happy, not at all. Fortunately I have access to all my data through the ext4 installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfs-initramfs (not installed) ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 27 20:07:56 2021 InstallationDate: Installed on 2019-09-09 (565 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921603 Title: The last update detroyed my Ubuntu boot in use since 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1921603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1921603] [NEW] The last update detroyed my Ubuntu boot in use since 18.04
Public bug reported: The last update of Ubuntu 20.04 inc. ZFS destroyed my boot process, fortunately I dual boot between zfs and ext4. My zfs boot is a manual boot, that I used in 2018 with Ubuntu Mate 18.04. The system has been upgraded I think through 19.04 and 19.10 to 20.04; The last system upgrade of 20.04 went wrong, the system did hang in the BIOS screen, so I thought about HW issues. Without my SSHD and also with another HDD, the system got passed the BIOS. So now I started thinking about boot issues. I downloaded boot-repair and that one repaired the ext4 install, so I was happy for a short moment. Did run update-grub, but caused the zfs ubuntu to show up in the boot menu, but the system failed to boot, because it needed bootpool/BOOT, which never existed on this laptop, running update-grub in the ext install had the next result, see: bertadmin@Ubuntu-ext:~$ sudo update-grub Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.4.0-70-generic Found initrd image: /boot/initrd.img-5.4.0-70-generic cannot open 'bpool/BOOT/mate-1804': dataset does not exist <-- Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804 Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804 cannot open 'bpool/BOOT/mate-1804@210213-linux43': dataset does not exist <-- Found linux image: vmlinuz-5.8.0-43-generic in vms/roots/mate-1804@210213-linux43 Found initrd image: initrd.img-5.8.0-43-generic in vms/roots/mate-1804@210213-linux43 /usr/sbin/grub-probe: error: unknown filesystem. Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda3 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sda4 failed: Device or resource busy Command failed. done This does not make me happy, not at all. Fortunately I have access to all my data through the ext4 installation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zfs-initramfs (not installed) ProcVersionSignature: Ubuntu 5.4.0-70.78-generic 5.4.94 Uname: Linux 5.4.0-70-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Mar 27 20:07:56 2021 InstallationDate: Installed on 2019-09-09 (565 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190909) SourcePackage: zfs-linux UpgradeStatus: Upgraded to focal on 2020-05-21 (310 days ago) ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1921603 Title: The last update detroyed my Ubuntu boot in use since 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1921603/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917503] [NEW] Crash during ZFS install
Public bug reported: The installation of Ubuntu 21.04 on ZFS in Virtualbox failed ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubiquity 21.04.9 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CasperVersion: 1.457 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 2 13:40:00 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210301) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.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 hirsute ubiquity-21.04.9 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917503 Title: Crash during ZFS install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1917503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917105] Re: Failed to create swap partition by disk utility and gparted
** Description changed: - I have tried to create a 2 GB swap partition on a GPT disk using both the gnome-disk-utility and gparted. - My system is a Virtualbox VM with the standard vdi file, that I did grow in Virtualbox with 2 GB using the virtual media manager menu. It has been impossible to create any partition in that 2 GB free space using those utilities. Both first promoted to extend the last partition and when I refused and used Apply, they both did give the notorious partitioning error message and nothing changed on the disk. + I have tried to create a 2 GB swap partition on a GPT disk using both the gnome-disk-utility and gparted. + My system is a Virtualbox VM with the standard vdi file, that I did grow in Virtualbox with 2 GB using the virtual media manager menu. It has been impossible to create any partition in that 2 GB free space using those utilities. Both first promoted to extend the last partition and when I refused and used Apply for the new partition, they both did give the notorious partitioning error message and nothing changed on the disk. In the end I added the virtual disk to a Windows 10 VM and I used Windows 10 to create a NTFS partition in that free space. After reloading Xubuntu I used gparted to format the partition to a Linux swap partition and that is what I use now after editing fstab. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-disk-utility 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Feb 27 00:38:38 2021 InstallationDate: Installed on 2020-11-21 (97 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201120) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917105 Title: Failed to create swap partition by disk utility and gparted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1917105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1917105] [NEW] Failed to create swap partition by disk utility and gparted
Public bug reported: I have tried to create a 2 GB swap partition on a GPT disk using both the gnome-disk-utility and gparted. My system is a Virtualbox VM with the standard vdi file, that I did grow in Virtualbox with 2 GB using the virtual media manager menu. It has been impossible to create any partition in that 2 GB free space using those utilities. Both first promoted to extend the last partition and when I refused and used Apply for the new partition, they both did give the notorious partitioning error message and nothing changed on the disk. In the end I added the virtual disk to a Windows 10 VM and I used Windows 10 to create a NTFS partition in that free space. After reloading Xubuntu I used gparted to format the partition to a Linux swap partition and that is what I use now after editing fstab. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-disk-utility 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Uname: Linux 5.10.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu59 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sat Feb 27 00:38:38 2021 InstallationDate: Installed on 2020-11-21 (97 days ago) InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201120) SourcePackage: gnome-disk-utility UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1917105 Title: Failed to create swap partition by disk utility and gparted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1917105/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1910448] [NEW] 100% CPU-core load for xrdp-chansrv
Public bug reported: One of the CPU cores is loaded to 100% by xrdp-chansrv see screenshot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xrdp 0.9.12-1 ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 Uname: Linux 5.4.0-59-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Wed Jan 6 17:01:51 2021 InstallationDate: Installed on 2021-01-05 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: xrdp UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: xrdp (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2021-01-06 17-05-51.png" https://bugs.launchpad.net/bugs/1910448/+attachment/5449829/+files/Screenshot%20from%202021-01-06%2017-05-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1910448 Title: 100% CPU-core load for xrdp-chansrv To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xrdp/+bug/1910448/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1908012] Re: System did not boot anymore after broken cable
Sorry, that is not the same!! I'm connected to a router and a router does give me the IP address, a bridge does not provide you with an IP address, so the system will react differently. As you should have noticed from my description, it goes wrong trying to get a web address resolved after having received my IP address from the router's DHCP. Note that I use TWO routers. the one closest to my desktop gives the IP address (router=192.168.1.1), but both need to be connected to get to the internet. The other one from the ISP has 192.168.0.1. The cable between both routers was broken. It is the configuration I did choose, to get wifi coverage in whole the house. Like I said I have done my part, there is nothing more I can do, since you do not seem to understand the issue. On Mon, 2021-01-04 at 11:30 +, Christian Ehrhardt wrote: > Thank you for your explanations BertN45, > I've taken a VM and tried to replicate your scenario by keeping it > connected to a bridge, but that bridge not connected anywhere else). > That should match your case - but Ubuntu Server as well as Ubuntu > Desktop guests started well in my case. > > So either it must be something special (package installed, > configuration) in your failing Ubuntu systems OR your network issue > was more complex than just "connected to net, but not the internet". > Either way we'd need more details and tries on your end, since you > stated that you won#t come/reply back we are again at what Lucas > mentioned - a not actionable bug. > > Therefore I'm keeping it in incomplete state so that it can auto- > expire > if no further updates happen. > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908577] Re: QEMU crashed after last update
The core dump of virtmanage, first time I generated a core dump. I hope it s OK. ** Attachment added: "_usr_bin_virt-manager.1000.crash" https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908577/+attachment/5445349/+files/_usr_bin_virt-manager.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908577 Title: QEMU crashed after last update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908577/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908577] [NEW] QEMU crashed after last update
Public bug reported:
After the last update QEMU crashed starting Ubuntu 14.04. In older
versions of QEMU it did work correctly.
For the error see my screenshot too.
Text was:
Traceback (most recent call last):
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in cb_wrapper
callback(asyncjob, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
callback(*args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57,
in newfn
ret = fn(self, *args, **kwargs)
File "/usr/share/virt-manager/virtManager/object/domain.py", line 1329, in
startup
self._backend.create()
File "/usr/lib/python3/dist-packages/libvirt.py", line 1234, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: internal error: qemu unexpectedly closed the monitor
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: qemu 1:5.2+dfsg-2ubuntu1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu55
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Dec 17 17:14:11 2020
Dependencies:
InstallationDate: Installed on 2020-11-05 (42 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20201104)
KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
/: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic
root=UUID=f006813e-07c3-453b-81f2-eda88f4d1667 ro quiet splash
SourcePackage: qemu
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias:
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug hirsute qemu
** Attachment added: "Screenshot from 2020-12-17 17-13-24.png"
https://bugs.launchpad.net/bugs/1908577/+attachment/5444672/+files/Screenshot%20from%202020-12-17%2017-13-24.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1908577
Title:
QEMU crashed after last update
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1908577/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908012] Re: System did not boot anymore after broken cable
I detected the problem, due to a hardware error, which has been handled extremely badly. I will explain it very simple: I have a normal network connection with my local network, but the connection to the Internet is missing. Ubuntu boots, but after login the system gets into a loop and only displays a purple or black screen. I did get the system out off the loop by disconnecting its Ethernet cable. This has been my solution till the cable had been repaired. Note that the solution only works for the HOST OS, my Ubuntu VBox VMs had the same problem and looped after login. Like I said the Windows VMs and the Fedora VM did not have that problem, because they handled this Internet missing issue correctly. As ex-OS designer, I solved many issues based on this type of information! I not familiar with the internal design of Linux, but I expect that Ubuntu tries to connect to the Internet after login for e.g livepatch or for a DNS server. In both cases the connection will fail and it looks like Ubuntu keeps trying in an endless loop, while blocking the desktop display function. I think the sh.desktop failing is the problem and it only got resolved after I pulled the Ethernet plug. I guess that sh.desktop needs an Internet function, that is not available. It returns an error and Ubuntu keeps trying for ever. If I pull the Ethernet plug, Ubuntu realizes, that it has to start anyhow. This is my last reaction to my bug-report, solve it or not. I don't care. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1908012 Title: System did not boot anymore after broken cable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1908012/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1908012] [NEW] System did not boot anymore after broken cable
Public bug reported: My system configuration looks as follows: ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop and switched off laptop / backup-server My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is loaded for my communication stuff (email, kde-connect etc). The cable between ISP Router and TP Link Router did go defect. The system did not boot/login any-more and stayed in a loop probably trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1 (the ISP Router). I tried to switch off stuff, disconnect cable and I think it continued the boot after I disconnected the Ethernet cable of the desktop. I will include the corresponding boot log. Most VMs did have the same issue, they did not boot/login any-more. Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9). They booted normally and allowed me to use the non-internet functions. I had the impression that Ubuntu based 20.04 VMs did not boot any-more, however the development editions of 21.04 booted as expected. I updated from 5.4.0.56 to 5.4.0.58 after I repaired the cable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bind9 (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 13 21:51:37 2020 InstallationDate: Installed on 2019-11-30 (379 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: bind9 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: bind9 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bind9 focal ** Attachment added: "bootlog.txt" https://bugs.launchpad.net/bugs/1908012/+attachment/5443315/+files/bootlog.txt ** Description changed: My system configuration looks as follows: ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop and switched off laptop / backup-server My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is loaded for my communication stuff (email, kde-connect etc). The cable between ISP Router and TP Link Router did go defect. The system did not boot/login any-more and stayed in a loop probably trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1 (the ISP Router). I tried to switch off stuff, disconnect cable and I think it continued the boot after I disconnected the Ethernet cable of the desktop. I will include the corresponding boot log. Most VMs did have the same issue, they did not boot/login any-more. - Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.7). + Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9). They booted normally and allowed me to use the non-internet functions. I had the impression that Ubuntu based 20.04 VMs did not boot any-more, however the development editions of 21.04 booted as expected. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bind9 (not installed) ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 13 21:51:37 2020 InstallationDate: Installed on 2019-11-30 (379 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: bind9 UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: My system configuration looks as follows: ISP Router <--> Own TP Link Wifi Router <--> 1 Gbps Switch <---> Desktop and switched off laptop / backup-server My desktop can run upto 50 VBox VMs, but normally only Xubuntu 20.04 is loaded for my communication stuff (email, kde-connect etc). The cable between ISP Router and TP Link Router did go defect. The system did not boot/login any-more and stayed in a loop probably trying to get a connection with the DNS server 1.1.1.1 or 192.168.0.1 (the ISP Router). I tried to switch off stuff, disconnect cable and I think it continued the boot after I disconnected the Ethernet cable of the desktop. I will include the corresponding boot log. Most VMs did have the same issue, they did not boot/login any-more. Exception were the Windows VMs (XP, 10 and 7) and Fedora 33 (Linux 5.9). They booted normally and allowed me to use the non-internet functions. I had the impression that Ubuntu based 20.04 VMs did not boot any-more, however the development editions of 21.04 booted as expected. + I updated from 5.4.0.56 to 5.4.0.58 after I repaired the cable. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bind9
[Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu
The snap with Firefox 84 has the same problem. I tried Ubuntu Studio 20.04, that also uses XFCE and that worked fine and so do the Ubuntu 20.04, Ubuntu Mate 20.04 and Xubuntu 21.04 Dev.Ed. However e.g Ubuntu 18.04 and Xubuntu 18.04 do have the same problem. To be a little more precise. If you select the YouTube video by clicking on its thumbnail, it has that strange behaviour, if you click in e.g. the middle of the progress bar, the same problem repeats itself. The buffer builds up in both cases to say 60 seconds, while the screen remain static on say that first frame and then empties itself in a few milliseconds and that repeats itself many many times :) However if you press the halt button in the left-down corner of the video and afterwards the play button, everything is working as expected. The same happens if you click in the middle of the screen twice as a start and stop action. It only starts correctly, if you start it manually. The automatic start fails and so does the auto repositioning by clicking in the progress bar. I hope this helps. There is probably some "timing issue" in the auto start, maybe forgetting that it should be displaying, because of a multi- threading/locking issue. In my experience this type of seemingly timing issues are often related to not locking shared data/buffers or locking it incorrectly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898656 Title: Firefox not playing YouTube videos in Virtualbox on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1898656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu
All YouTube videos -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898656 Title: Firefox not playing YouTube videos in Virtualbox on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1898656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1869444] Re: Task Manager tab: File systems completely wrong
This is ridiculous, the Ubuntu Task Manager does not display the ZFS partitions, while the Ubuntu Disk Utility does display them and the bug report is cancelled. Even a blind dog can see, that the task manager of Ubuntu misses the code to see the officially supported ZFS partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869444 Title: Task Manager tab: File systems completely wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1869444/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu
Have tried the development edition and had the same problem. I did not report the problem to bugzilla, because after I tried to access bugzilla, Github threatened to withdraw my access next month for some vague reasons, unless I changed my password. On Tue, 2020-11-24 at 16:07 +, Olivier Tilloy wrote: > If you have some time to spare, could you test whether the upstream > builds (which can be downloaded from > https://www.mozilla.org/firefox/download/thanks) are similarly > affected, > and if so, file an upstream bug report at > https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CFirefox ? > > ** Changed in: firefox (Ubuntu) >Status: Incomplete => New > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898656 Title: Firefox not playing YouTube videos in Virtualbox on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1898656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1898656] Re: Firefox not playing YouTube videos in Virtualbox on Xubuntu
The problem is still there, but don't worry, I moved to Chrome :) Yes, the codecs are all there and in the past it all worked fine. The problem is; it plays all frames in the buffer in milli seconds instead of one per 33 msecs (30 Hz). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898656 Title: Firefox not playing YouTube videos in Virtualbox on Xubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1898656/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1869279] Re: zsys clutters up the system and stops system updates.
*** This bug is a duplicate of bug 1876334 *** https://bugs.launchpad.net/bugs/1876334 On Ubutuntu I use: sudo apt purge zsys On Sun, 2020-11-08 at 15:39 +, Julian wrote: > *** This bug is a duplicate of bug 1876334 *** > https://bugs.launchpad.net/bugs/1876334 > > Hi BertN45, > > Have you managed to completely remove zsys from your ubuntu system ? > I'm > interested in doing the same. Could you please document steps to > achieve > it ? > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1869279 Title: zsys clutters up the system and stops system updates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zsys/+bug/1869279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898376] Re: Packages not running anymore after update from sep 26 to oct 03
The problem with Lollypop has been solved, probably by one of the frequent updates of Lollypop. The problem with Firefox remained, so I now use Chromium. If the problems are not solved, I move on to another product. On Sat, 2020-10-31 at 11:48 +, Amr Ibrahim wrote: > ** Changed in: lollypop (Ubuntu) >Status: Incomplete => Invalid > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898376 Title: Packages not running anymore after update from sep 26 to oct 03 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lollypop/+bug/1898376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1897198] Re: Ubuntu Cinnamon 20.10 Linux headers not installed nor updated
I've done the upgrade to Linux 5.8.0-21 and had all the old buggy sympthoms. That all had been caused by the failing of the Virtualbox Guest Additions installation for Linux 5.8.0-21 during the Linux upgrade from 20 to 21. Everything was OK after: - I installed "linux-headers-5.9.0-21-generic" using Synaptic and - reinstalled the Virtualbox Guest Additions. On Wed, 2020-10-07 at 15:36 -0400, Bert Nijhof wrote: > It look like one problem has disappeared, I have a display resolution > at 1920 x 1080 now. > > I don't remember what happened going from 5.8.0-19 to 5.8.0-20, but > synaptic still marks those headers as manually intalled. > - linux-headers-5.8.0-20-generic > - linux-image-generic > So I assumed that the (re-)installation of Virtualbox went wrong, > because those headers were missing and I installed those headers > using > synaptic. I expect, that those headers are installed by default, when > installig or updating Linux. > > I only have Linux Mint 20 VM and I have no problems with it. But that > one still runs Linux 5.4. > I did not have these problems with Ubuntu Cinnamon 20.04 VM running > at > Linux 5.4. > > > > > On Wed, 2020-10-07 at 17:10 +, Joshua Peisach wrote: > > Check this on any other distro with Cinnamon DE: Does this occur > > with > > them too? (Get an unstable ISO like Fedora 33 Beta) > > > > But this is definitely something important. > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1897198 Title: Ubuntu Cinnamon 20.10 Linux headers not installed nor updated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1897198/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
