[Bug 1890061] Re: MATE Focal "amplified" sound controls do not sync with keyboard buttons
** Tags added: jammy -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890061 Title: MATE Focal "amplified" sound controls do not sync with keyboard buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmatemixer/+bug/1890061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Documentation is horribly insufficient in this regard. To quote the link given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware enablement). It means that from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months through to summer of 2022". The words "from 20.04.2 release Ubuntu Desktop will gain new major kernel versions every 6 months" speak volumes, sadly incorrect volumes. 20.04.2 is not even due for release until next month but we've been getting HWE kernel updates for a couple of weeks already! All of the following documentation needs serious updating and must include methods to remain on the GA kernel if one wishes: The first, also from the release notes, states clearly "Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4": https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Updated_Packages None of these have been updated to adequately reflect the change to opt- out of HWE rather than opt-in if using original (20.04) or first point release (20.04.1) installation media as had always been the case previously. https://wiki.ubuntu.com/Kernel/LTSEnablementStack https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack https://ubuntu.com/kernel/lifecycle -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
*** This bug is a duplicate of bug 1910709 *** https://bugs.launchpad.net/bugs/1910709 ** This bug has been marked a duplicate of bug 1910709 DKMS linux-headers-5.8.0-34-generic update brokes nvidia-340 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Upgrading to nvidia-opencl-icd-340:amd64 (340.108-0ubuntu2, 340.108-0ubuntu5.20.04.1) from focal-proposed solves this problem. See bug #1910709. I came to this conclusion after testing the focal-daily (20210116) and finding that nvidia-340 installed just fine. Since LTS daily builds always have the proposed repos enabled it was just a matter of parsing what packages were available in proposed. Probably OK to mark this fix released but I'll leave that decision up to one of the devs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
I changed the package name from "meta" to just linux to get apport- collect to work. Hope that's OK. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
apport information ** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lance 829 F pulseaudio + /dev/snd/controlC1: lance 829 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-15 (0 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. Latitude E6510 + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-38-generic N/A + linux-backports-modules-5.8.0-38-generic N/A + linux-firmware1.187.2 + Tags: focal + Uname: Linux 5.8.0-38-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/12/2017 + dmi.bios.release: 4.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.name: 0N5KHN + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6510 + dmi.product.version: 0001 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt"
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Even if that were the only consideration, which it's not, how do you explain the fact that 20.04.2 has not yet been released? >From my daily driver: lance@lance-desktop:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.1 LTS Release:20.04 Codename: focal And yes, so far it's fairly easy to change from 'linux-generic- hwe-20.04' to 'linux-generic', then reboot selecting the latest 5.4 kernel and then purging all of the 5.8 bits and pieces. But once the anticipated HWE X stack drops (which will likely solve most X related issues) it's a real mess. Of course the 20.04 Beta images are archived at old-release so that's an option - just keep installing from a Beta image for the next 4+ years. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Hardware specs can't hurt. ** Attachment added: "hw.txt" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453595/+files/hw.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Also may be helpful. ** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453586/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
Looks helpful to me. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453585/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
I clearly did something wrong based on the lack of attachments to this and I can't get apport-collect to work so I'll attach a few on my own but I sure could use some help :^) ** Attachment added: "media-info" https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+attachment/5453584/+files/media-info -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.8/+bug/1912032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I filed bug #1912032 concerning the failure of nvidia drivers to install during a fresh installation of Ubuntu 20.04.1 because when download updates is selected it auto-updates to a 5.8 series kernel during installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I updated the bug description to better explain why I believe this is a bug, but I left the original content below the break. ** Description changed: Beginning about January 8th Focal users that installed Focal using either the Ubuntu 20.04 or 20.04.1 installation media began getting updated to the 5.8 series linux kernel. Those who had installed using the Ubuntu Focal Beta were not effected. This is because Focal Beta was properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images were built with ‘linux-generic-hwe-20.04‘. This can be easily verified by looking at the iso manifest: https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- amd64.manifest Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be downloaded here: https://old-releases.ubuntu.com/releases/20.04/ The expected behavior is for Ubuntu Focal users to remain on the 5.4 series kernel unless they install with 20.04.2 or later images as indicated here: https://wiki.ubuntu.com/Kernel/LTSEnablementStack While not entirely updated it says “if one wants to remain on the original GA (General Availability) stacks, the options [include]; Install from a previous 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point release and update”. Jump just below that to the Focal specific notes and it says “The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop”. Since 20.04.2 is not even due for release until next month it makes no sense for updates to the 5.8 series kernel to be occurring unless the focal-proposed repos are enabled even if HWE protocols had been changed. It’s also worth noting that thankfully no accompanying HWE X stack is yet available in the repos. I say thankfully because my efforts at - downgrading the X stack in 16.04 and 18.04 were always successful! But + downgrading the X stack in 16.04 and 18.04 were never successful! But the lack of a matching X stack may explain the many complaints on the forums about broken graphics??? It’s also worth noting that even the release notes say that “Ubuntu 20.04 LTS is based on the long-term supported Linux release series 5.4“. https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are supposed to be supported with the 5.4 series kernel for the entire 5 year life span: https://ubuntu.com/kernel/lifecycle The other flavors’ 20.04 and 20.04.1 images were all built correctly with ‘linux-generic’ with the possible exception of Ubuntu Studio which uses a kernel stack I’m not familiar with. I’m also uncertain about Ubuntu server because I’m simply not familiar with it. Original bug description below: ## Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
I added the packaging tag because this was a packaging error in the 20.04 and 20.04.1 images. ** Tags added: packaging ** Description changed: + Beginning about January 8th Focal users that installed Focal using + either the Ubuntu 20.04 or 20.04.1 installation media began getting + updated to the 5.8 series linux kernel. Those who had installed using + the Ubuntu Focal Beta were not effected. This is because Focal Beta was + properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images + were built with ‘linux-generic-hwe-20.04‘. This can be easily verified + by looking at the iso manifest: + + https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop- + amd64.manifest + + Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be + downloaded here: + + https://old-releases.ubuntu.com/releases/20.04/ + + The expected behavior is for Ubuntu Focal users to remain on the 5.4 + series kernel unless they install with 20.04.2 or later images as + indicated here: + + https://wiki.ubuntu.com/Kernel/LTSEnablementStack + + While not entirely updated it says “if one wants to remain on the + original GA (General Availability) stacks, the options [include]; + Install from a previous + 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point + release and update”. + + Jump just below that to the Focal specific notes and it says “The + 20.04.2 and newer point releases will ship with an updated kernel and X + stack by default for the desktop”. Since 20.04.2 is not even due for + release until next month it makes no sense for updates to the 5.8 series + kernel to be occurring unless the focal-proposed repos are enabled even + if HWE protocols had been changed. + + It’s also worth noting that thankfully no accompanying HWE X stack is + yet available in the repos. I say thankfully because my efforts at + downgrading the X stack in 16.04 and 18.04 were always successful! But + the lack of a matching X stack may explain the many complaints on the + forums about broken graphics??? + + It’s also worth noting that even the release notes say that “Ubuntu + 20.04 LTS is based on the long-term supported Linux release series 5.4“. + + https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel + + Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are + supposed to be supported with the 5.4 series kernel for the entire 5 + year life span: + + https://ubuntu.com/kernel/lifecycle + + The other flavors’ 20.04 and 20.04.1 images were all built correctly + with ‘linux-generic’ with the possible exception of Ubuntu Studio which + uses a kernel stack I’m not familiar with. I’m also uncertain about + Ubuntu server because I’m simply not familiar with it. + + Original bug description below: + + ## + Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Unfortunately apport-collect just says "no additional info collected" (see pic added). I presume because 'ubuntu-meta' is not an installed package? I struggled a bit trying to decide what the best way was to report a bug like this because it's not actually a bug in the kernel itself, it's just that I believe the 5.8 series kernel should not be installed without specific user action to do so. That had been the case in the past. LTS installs using the original iso or the first point release iso would remain on the original GA (General Availability) throughout the duration of the 5 year support cycle. In fact I see the HWE Wiki has been updated to say "The 20.04.2 and newer point releases will ship with an updated kernel and X stack by default for the desktop": https://wiki.ubuntu.com/Kernel/LTSEnablementStack And 20.04.2 is not due for release until early February. It's worth mentioning that LTS point releases are frequently delayed by a week or two if bugs are encountered. Anyway I would expect an installation performed with 20.04.2 media to include the HWE kernel. You'll also notice that they do say "kernel and X stack" and as mentioned above the HWE X stack is not yet even in the repos! I will probably be testing the 20.04.2 daily build very soon and I'll then report a bug against 'linux-generic-hwe-20.04' making note that the accompanying X stack is missing. And yes, this does effect only Ubuntu Desktop because as mentioned above I checked some of the other flavors manifests. Only the Ubuntu isos have the HWE version of kinux-generic installed. ** Attachment added: "Screenshot from 2021-01-14 19-45-49.png" https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+attachment/5453132/+files/Screenshot%20from%202021-01-14%2019-45-49.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1911614] [NEW] Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic
Public bug reported: Just as the title says, the 20.04 and 20.04.1 images use the HWE version of linux-generic resulting in upgrades to the 5.8 series kernel. This seems to effect Ubuntu only, or I should say I checked the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list linux-generic. Also HWE is not truly complete without the accompanying HWE Xstack. I checked all the documentation I could find and this was clearly not intentional. In fact the manifest for Ubuntu Focal Beta still used linux-generic, so this got messed up some time between April 3, 2020 and April 23, 2020. Here's just one example of the documentation for kernel support in Focal LTS: https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle Installations performed with 20.04 and 20.04.1 media were supposed to remain on the 5.4 series kernel throughout Focal's 5 year lifespan as had been the case since HWE was introduced. The first step in fixing this needs to be stopping fresh installs of Focal using the 20.04 and 20.04.1 media from immediately upgrading to the 5.8 series kernel. It might be a little tricky to revert users from 5.8 to 5.4, but there have been reports of breakage, particularly concerning Broadcom wifi drivers and some graphics problems. But the graphics problems could also be exacerbated by the lack of the matching HWE Xstack? At any rate it's a bug. ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1911614 Title: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742193] Re: nemo-desktop does not show background on GNOME FlashBack session
Thanks Alberts. I'd been trying to figure that out for some time now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742193 Title: nemo-desktop does not show background on GNOME FlashBack session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nemo/+bug/1742193/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900217] Re: Groovy install on non-efi hardware ends with grub install error
Bad on me - I didn't realize we now needed an EFI System partition on ALL installations. ** Changed in: ubiquity (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/1900217 Title: Groovy install on non-efi hardware ends with grub install error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1900217] [NEW] Groovy install on non-efi hardware ends with grub install error
Public bug reported: Fairly simple install on non-efi Dell Latitude E6400. Just selected "something else" and used an existing partition for /. Another OS is already installed next to it (on sda3 I think). Installation ended with a grub install warning. Not sure what will happen when I reboot but I was offered the opportunity to file this bug report so I did. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubiquity 20.10.12 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.455 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 17 00:02:54 2020 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201016.4) ProcEnviron: LANGUAGE=en_US.UTF-8 PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 LC_NUMERIC=C.UTF-8 RebootRequiredPkgs: linux-image-5.8.0-23-generic linux-base SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubiquity-20.10.12 ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1900217 Title: Groovy install on non-efi hardware ends with grub install error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Although not intentionally so, this now works fine on both the E6400 and E6510 laptops. Both initial boots, and subsequent boots. Just works perfect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Worst case scenario on those older Latitude laptops a DVD still works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
http://cdimage.ubuntu.com/ubuntu/daily-live/20201016.1/groovy-desktop- amd64.manifest still shows casper 1.452 Is that correct or is the manifest just not updated? It's still not working on the Dell latitude E6510 and E6400 previously mentioned. On the E6510 I tried both legacy and UEFI modes and no go in either (USB not even detected). The E6400 does not offer UEFI as an option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1899308] Re: failure to boot groovy daily (again)
Also seems to effect Dell Latitude E6400 with C2D CPU's and an E6510 with i7 M620 CPU laptops using 20201015 Ubuntu image created with Startup Disk Creator in 20.04. The same USB with the same image works OK in my old Intel Desktop so I'm reasonably certain it's hardware specific. Typical behavior for these Latitude laptops is needing to press F12 while the BIOS screen is displayed and a boot menu will be displayed. Doesn't matter if you have USB set as first boot option in BIOS - sort of a buggy BIOS I guess, but in this case the USB is not even recognized with a recent 20.10 Live USB inserted. If I go ahead and boot into an installed Ubuntu system on one of these effected systems with the USB still inserted a message is displayed saying: "Error mounting /dev/sdb3 at /media/lance/Ubuntu 20.10 amd64: Command-line `mount -t "iso9660" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,iocharset=utf8,mode=0400,dmode=0500" "/dev/sdb3" "/media/lance/Ubuntu 20.10 amd64"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb3, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so. If in fact that USB drive is at fault it's odd that it will boot in my old desktop computer, but I will try a different drive just to be certain. I'm really at a loss as what else to try at this point. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1899308 Title: failure to boot groovy daily (again) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1899308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890061] Re: MATE Focal "amplified" sound controls do not sync with keyboard buttons
** Tags added: ubuntu-mate -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890061 Title: MATE Focal "amplified" sound controls do not sync with keyboard buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmatemixer/+bug/1890061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890061] [NEW] MATE Focal "amplified" sound controls do not sync with keyboard buttons
Public bug reported: I probably have the package wrong but I was grabbing at straws :^) Just recently testing Ubuntu MATE 20.04.1 release candidates and I notice that you can increase volume beyond 100% by opening Sound Settings, and once you've done that you can also increase beyond 100% using the volume "widget" in indicator-applet, but I've tested on three different sets of hardware and the volume buttons on the keyboards fail to increase beyond 100%. In fact if you're above 100% and try to bump the volume down slightly it will drop all the way to 100% and can't be increased beyond that without access to the "volume widget" so if you're viewing videos in full screen you first have to exit full screen and then readjust above 100%. So it's kind of a show-stopper for those using the OS on an HTPC. This had effected Ubuntu Bionic but was fixed in 18.10 and remains fixed in Focal - see bug #1817625. I've no idea what they changed to achieve that. Testing Focal live sessions only it seems that this same Focal bug also effects Kubuntu and Xubuntu, but they were only tested in live sessions whereas I've tested Ubuntu MATE as an installed OS. As mentioned above in Ubuntu this now does work poroperly, and also works properly using the flashback session but you must either first set "above 100%" in the Ubuntu interface or go to dconf-editor > com.ubuntu.sound, which I did also try in MATE but to no avail. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libmatemixer0 1.24.0-1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Aug 2 17:45:16 2020 InstallationDate: Installed on 2020-07-31 (2 days ago) InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200730) SourcePackage: libmatemixer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libmatemixer (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/1890061 Title: MATE Focal "amplified" sound controls do not sync with keyboard buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmatemixer/+bug/1890061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan
Sorry I lumped so much text into one box. I must have been asleep at the wheel. I was just setting up another of these today with 18.04.1 and it's also effected but I know Xenial worked fine out-of-box so I'm just guessing (with inadequate studying) that the change to GNOME as default resulted in slightly different dependencies? It is indeed a low priority bug, or I'm almost hesitant to call it a true bug since apparently it effects a very limited number of older laptops. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845898 Title: Unable to set touchpad Edge Scrolling in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan
Sorry for the delay. I performed a fresh install of 20191014 last night, then updated it this AM so we'd be working with an out-of-box experience. After the update and a reboot I opened System Settings > Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to- click to off while also changing Edge Scrolling to ON. Opening Test Your Settings indicates that the changes were applied correctly but immediately after closing System Settings the Edge Scrolling setting reverts to off. That can be verified both by the touchpad behavior and reopening the Mouse & Touchpad settings UI. The other settings changes "stick" as they should. lance@lance-e6400:~$ journalctl -b 0 -- Logs begin at Mon 2019-10-14 22:46:09 CDT, end at Tue 2019-10-15 15:42:44 CDT Oct 15 15:33:49 lance-e6400 kernel: microcode: microcode updated early to revisi Oct 15 15:33:49 lance-e6400 kernel: Linux version 5.3.0-18-generic (buildd@lcy01 Oct 15 15:33:49 lance-e6400 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0 Oct 15 15:33:49 lance-e6400 kernel: KERNEL supported cpus: Oct 15 15:33:49 lance-e6400 kernel: Intel GenuineIntel Oct 15 15:33:49 lance-e6400 kernel: AMD AuthenticAMD Oct 15 15:33:49 lance-e6400 kernel: Hygon HygonGenuine Oct 15 15:33:49 lance-e6400 kernel: Centaur CentaurHauls Oct 15 15:33:49 lance-e6400 kernel: zhaoxin Shanghai Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x8 Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SS Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Enabled xstate features 0x3, contex Oct 15 15:33:49 lance-e6400 kernel: BIOS-provided physical RAM map: Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0009f000-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0010-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04d400-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04f400-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xf800-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfec0-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed18000-0x000 Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed2-0x000 For the rest of this I attached a Logitech M317 mouse. Here's the requested output with out-of-box settings: lance@lance-e6400:~$ sudo libinput list-devices [sudo] password for lance: Device: Video Bus Kernel: /dev/input/event8 Group:1 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Power Button Kernel: /dev/input/event1 Group:2 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Lid Switch Kernel: /dev/input/event0 Group:3 Seat: seat0, default Capabilities: switch Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: Sleep Button Kernel: /dev/input/event2 Group:4 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: HID 413c:8157 Kernel: /dev/input/event4 Group:5 Seat: seat0, default Capabilities: keyboard Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none Disable-w-typing: n/a Accel profiles: n/a Rotation: n/a Device: HDA Intel Dock Mic Kernel: /dev/input/event9 Group:6 Seat: seat0, default Capabilities: Tap-to-click: n/a Tap-and-drag: n/a Tap drag lock:n/a Left-handed: n/a Nat.scrolling:n/a Middle emulation: n/a Calibration: n/a Scroll methods: none Click methods:none
[Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing
** Tags added: eoan gnome-panel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1845898] [NEW] Unable to set touchpad Edge Scrolling in Eoan
Public bug reported: After installing the Eoan Beta on a Dell Latitude E6400 attempting to set touchpad Edge Scrolling was unsuccessful. It actually seemed to work as long as the System Settings window was left open but as soon as the window is closed the Edge Scrolling setting reverts to off. I did however find that simply installing the package 'xserver-xorg- input-synaptics' solves the problem. In fact it adds the additional setting option of Two Finger Scrolling to the control center UI. I'm not sure if that package should be installed by default or not? Steps to reproduce are simple: (1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with an incorporated touchpad). (2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & Touchpad. (3) Select Edge Scrolling and you'll notice the "button" turn green. Close System Settings. (4) Reopen System Settings and you'll see Edge Scrolling has turned off again. (5) Install 'xserver-xorg-input-synaptics' and then reboot. (6) Repeat the above steps and you'll find that setting Edge Scrolling is successful even after closing System Settings. Additionally you'll find that a new Two Finger Scrolling option has been added to the UI. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.0.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Sep 29 22:15:09 2019 InstallationDate: Installed on 2019-09-30 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1845898 Title: Unable to set touchpad Edge Scrolling in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
I will follow up ASAP. The plot continues to thicken. I tried a different set of hardware today with a B43 chipset and it didn't seem to be effected. But that board has only DVI and VGA outputs whereas the effected board with a G43 chipset has DVI and HDMI. I'd been using HDMI so now I ran another range of tests using DVI on the effected board and was unable to reproduce. So this appears to effect a very selective subset of 10 to 12 year old hardware. Must be Intel X4500 graphics with HDMI connection and possibly only the G43 chipset. So it's the absolute corneriest of corner issues I've ever encountered. And the workaround couldn't be any simpler - just remove the "quiet splash" boot parameter and all seems well (both boot to and logout to gdm3 screen). BTW ASAP may be rather slow in coming because I have a few medical procedures scheduled in the next few weeks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
Sadly /var/crash is empty, and errors.ubuntu.com + whoopsie-id just displays a blank page. Also applying the workaround from bug 994921 does not result in creating a crash report. I started testing Ubuntu Disco 20190416 tonight and knowing what I know now I can say with certainty that the easiest way to reproduce this bug (on effected hardware) is to perform a fresh install choosing NOT to auto-login. Then the first boot will be OK but each subsequent boot will produce a black screen - that is the gdm3 login screen never appears and it's not possible to enter a TTY. But once "quiet splash" is removed via grub the system boots as it should. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input
Based on those most recent results I ran "dpkg-reconfigure grub-pc" and removed "quiet splash". Now it boots to the gdm3 screen every time. So maybe something to do with how plymouth hands off the boot process to gdm3? Or how quickly that hand off is completed? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: With AutomaticLogin enabled, logging out lands me on a black screen that's unresponsive to any keyboard input To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
This was tricky but I finally got a successful boot (following several failed boots) using gdm3 by selecting the kernel with "e" from grub and then removing 'quiet splash'. So I hope this is more helpful. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256203/+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/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
Method used to collect this info: (1) Fresh installed 20190413.2 choosing not to auto-login. (2) Rebooted after install and surprisingly gdm3 appeared as it should so I booted to desktop and just rebooted. (3) That reboot failed as had been the previous case - just a black screen, totally unresponsive. (4) Performed a hard reboot with the reset button on the PC, entered recovery from grub menu, then installed lightdm, and rebooted. (5) Collected info as instructed. So there are a total of 3 boots. The first was successful - no problems. The second booted to a black screen instead of displaying gdm3 screen. Third boot was performed using lightdm. ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256045/+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/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
As requested. Definitely C2D era board (Intel DG43GT) running a Pentium Dual Core. ** Attachment added: "lspcik.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+attachment/5256044/+files/lspcik.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
Slight change in behavior testing a fresh install of 20190413.2 - if installed with auto-login switched on logout did load and give the expected choices of Ubuntu and Ubuntu w/Wayland. But if auto-login is turned off I still get a black screen on reboot. I suspect that gdm3 is not even loading because I've tried blindly opening a tty, logging in as root, and sudo reboot but nothing happens. Once again just installing lightdm (I haven't tried the old unity- greeter) gives me a working machine. By looking at the changelog nothing has changed in gdm3 so I'm unsure why the logout behavior would have improved with a 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/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824672] [NEW] Disco "check disc for defects" appears not to function
Public bug reported: Just testing the 20190413.2 image and after selecting "check disc for defects" the Ubuntu splash screen appears very briefly, no testing text is displayed, and a "no errors found" message appears in under one minute. As recently as 20190326.2 the test ran as expected displaying "scrolling" text on screen before completing and reporting a pass or fail so I doubt this was an intentional change but I could be mistaken. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: syslinux 3:6.04~git20171011.af7e95c3+dfsg1-6 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CasperVersion: 1.403 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 13 23:43:46 2019 LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: syslinux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: syslinux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824672 Title: Disco "check disc for defects" appears not to function To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslinux/+bug/1824672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
This does appear to be hardware related because I encounter no problem on a box with Intel G41 graphics but the X4500 is a no-go with gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
I found that turning auto-login off resulted in booting to a black screen so after unsuccessfully trying the nomodeset boot option I installed 'lightdm-gtk-greeter' and 'lightdm' from recovery mode which gives me a working system. I had encountered no problems with desktop behavior but this box has Intel GMA X4500 graphics (old-ish I know) so I wonder if it could be related to bug #1727356? Having installed 'gnome-shell-extensions' package from the repos I'm able to boot and run all three available sessions - Ubuntu, Ubuntu w/Wayland, and "Classic" with no apparent issues as long as I use lightdm instead of gdm3. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] Re: Ubuntu Disco boots to or logs out to black screen
** Summary changed: - Ubuntu Disco logs out to black screen + Ubuntu Disco boots to or logs out to black screen -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco boots to or logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1824588] [NEW] Ubuntu Disco logs out to black screen
Public bug reported: Just testing Disco and wanted to see what login options are available after adding 'gnome-shell-extensions' and found that logging out lands me on a black screen that's unresponsive to any keyboard input. I'll test on some slightly different hardware soon. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 12 16:18:56 2019 InstallationDate: Installed on 2019-04-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1824588 Title: Ubuntu Disco logs out to black screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
** Description changed: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases - the sound above 100%. Neither the slider in the sound settings UI or the - keyboard volume hot keys will increase the sound above 100%. + the sound above 100%. The slider in the sound settings UI will not + increase the sound above 100%. The keyboard hot-keys are also effected + in the flashback session, but NOT the default Ubuntu session. - So, in use as an HTPC, if you're streaming content in full screen and - have the sound set above 100%, when a blaring loud commercial comes on - and you turn the volume down with the keyboard hot keys you can't use - the keyboard hot-keys to return to that over-amplified state. + So if using the flashback session, in use as an HTPC, if you're + streaming content in full screen and have the sound set above 100%, when + a blaring loud commercial comes on and you turn the volume down with the + keyboard hot keys you can't use the keyboard hot-keys to return to that + over-amplified state. In the default Ubuntu session the hot-keys + function as expected. I'm attaching a screenshot. A logout is necessary for the over- amplification setting to take effect so the steps to reproduce are as follows: (1) Open System Settings > Sound (2) Toggle Over-Amplification to On (3) logout and then log back into the default session (this is required) (4) Open System Settings > Sound and toggle the volume slider to the left, then all the way to the right. (5) Click on the volume icon in the top panel and you'll see that it's only at about 66% - obviously the two should "sync" but do not ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center 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/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
One more difference between the default and flashback sessions is that the keyboard hot-keys DO work in the default Ubuntu session, but NOT in the flashback session. So that makes this even a lower priority, and passes part of the responsibility onto the flashback devs. ** Tags added: gnome-panel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
** Description changed: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases the sound above 100%. Neither the slider in the sound settings UI or the keyboard volume hot keys will increase the sound above 100%. So, in use as an HTPC, if you're streaming content in full screen and have the sound set above 100%, when a blaring loud commercial comes on and you turn the volume down with the keyboard hot keys you can't use the keyboard hot-keys to return to that over-amplified state. - I'm attaching a screenshot and I'll also update this with a full step by - step process to reproduce the bug. Either a reboot or logout is required - for the changes to take effect after switching over-amplification on (or - maybe off too). I just need to rinse-n-repeat a few times to be sure so - you won't have to waste time trying to reproduce. + I'm attaching a screenshot. A logout is necessary for the over- + amplification setting to take effect so the steps to reproduce are as + follows: + + (1) Open System Settings > Sound + (2) Toggle Over-Amplification to On + (3) logout and then log back into the default session (this is required) + (4) Open System Settings > Sound and toggle the volume slider to the left, then all the way to the right. + (5) Click on the volume icon in the top panel and you'll see that it's only at about 66% - obviously the two should "sync" but do not ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: gnome-control-center 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/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider
Actually only a logout is necessary for the UI and volume slider to respond to the amp change. So I'll add steps to reproduce. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider
Actually this specific issue effects the default Ubuntu session as well. I did a fresh install of 18.04.2, installed updates, rebooted, and checked it out to be sure. Then I filed bug #1817625 so one or the other needs to be marked a duplicate (and changed back to "new" rather than "invalid"). I just wanted to collect all the logs so you could see I'm not pulling your leg about the default Ubuntu session being effected. I had not realized that the default Ubuntu session had a UI for over- amplification whereas flashback session does not. Since it can be set via dconf I'm unlikely to file a new bug report just for that. I should however check to be sure flashback doesn't "break" things in a default session. I just got lazy yesterday and filed this bug report from my workhorse PC rather than using my friends new HTPC. I'm going to rinse-n-repeat the steps to reproduce this in that unmolested install of Bionic. It seems that either a reboot or logout is needed after selecting over-amplification = on. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817625] [NEW] Bionic "amplified" sound controls do not sync with volume slider
Public bug reported: This is intentionally a duplicate of bug #1817485 to collect info on a fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's default session is also effected. I just wanted to collect all pertinent logs to prove that this was in fact an unmolested install. As in the previously filed bug report once over-amplification is switched on only the volume slider in the top panel actually increases the sound above 100%. Neither the slider in the sound settings UI or the keyboard volume hot keys will increase the sound above 100%. So, in use as an HTPC, if you're streaming content in full screen and have the sound set above 100%, when a blaring loud commercial comes on and you turn the volume down with the keyboard hot keys you can't use the keyboard hot-keys to return to that over-amplified state. I'm attaching a screenshot and I'll also update this with a full step by step process to reproduce the bug. Either a reboot or logout is required for the changes to take effect after switching over-amplification on (or maybe off too). I just need to rinse-n-repeat a few times to be sure so you won't have to waste time trying to reproduce. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 25 14:25:01 2019 InstallationDate: Installed on 2019-02-25 (0 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2019-02-25 14-18-10.png" https://bugs.launchpad.net/bugs/1817625/+attachment/5241665/+files/Screenshot%20from%202019-02-25%2014-18-10.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817625 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider
Bionic no longer displays allow above 100% in the sound settings UI. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1817485] [NEW] Bionic "amplified" sound controls do not sync with volume slider
Public bug reported: I'm just setting up my first Bionic HTPC and I notice that if you select allow-amplified-volume in dconf that change only applies to the volume slider, not to the sound control UI. This results in the volume hot-keys not controlling sound above 100%. So if you're watching video content in full screen you must ESC, then use the volume slider, and then go back to full screen. It makes for an unwieldy process so using a different DE becomes a temptation. You can see what I'm talking about in the attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Sun Feb 24 14:10:03 2019 InstallationDate: Installed on 2018-01-28 (391 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages ** Attachment added: "Screenshot from 2019-02-24 14-27-44.png" https://bugs.launchpad.net/bugs/1817485/+attachment/5241405/+files/Screenshot%20from%202019-02-24%2014-27-44.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1817485 Title: Bionic "amplified" sound controls do not sync with volume slider To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816687] [NEW] Bionic pavucontrol fails to set default device if usb sink or source exists
Public bug reported: Just as the title says, if a usb sound card is in use pavucontol's settings are ignored. This appears to be an unintended result of the changes made to address bug #1702794. Specifically if you now look at /etc/pulse/default.pa you'll find this section: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif So you must comment out those three lines in order for pavucontrol device default settings to be respected if a usb sound card is plugged in at reboot or startup. It's not a big deal but I hadn't run across this in the past and couldn't find an existing bug report. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pavucontrol 3.0-4 ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Feb 19 21:05:18 2019 InstallationDate: Installed on 2018-01-28 (387 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pavucontrol UpgradeStatus: Upgraded to bionic on 2018-08-15 (188 days ago) ** Affects: pavucontrol (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1816687 Title: Bionic pavucontrol fails to set default device if usb sink or source exists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pavucontrol/+bug/1816687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489147] Re: Booting live Wily image results in black screen with or without random text
Wily is long past EOL. If anyone is still experiencing this bug with a supported version it would probably be best to open a new 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/1489147 Title: Booting live Wily image results in black screen with or without random text To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
Will we be able to push a patch into gnome-panel 1:3.26 in Bionic since it's an LTS supported until 2023? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing
It seems to me that the most sensible approach would be to just remove the Computer button from the Places menu. Then you'd just open Home and select Other Locations. I think that would be more in keeping with the latest Nautilus redesign. I'm not at all sure but we may want to do likewise with the Network button in the Places menu because it's now also accessible via Home -> Other Locations. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
Sorry to take so long getting back to this. Disabling "show weather" and "show temp" helps reduce that dead space but it must be done after each boot or reboot because the settings don't "stick". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754200] [NEW] Ubiquity crashed while installing Lubuntu Bionic
Public bug reported: Just performing a manual partitioning install using Lubuntu Bionic 20180306.1 amd64 and the installer crashed and generated this report. The only thing I did that may be "odd" is creating a SWAP partition during installation. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubiquity 18.04.3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.389 Date: Wed Mar 7 18:28:04 2018 InstallCmdLine: file=/cdrom/preseed/lubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- JournalErrors: Error: command ['journalctl', '-b', '--priority=err', '--lines=1000'] failed with exit code 1: Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. No journal files were opened due to insufficient permissions. LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) 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 bionic lubuntu ubiquity-18.04.3 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754200 Title: Ubiquity crashed while installing Lubuntu Bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1754200/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen
This may or may not be worth mentioning but the reason I totally purged lightdm was just using dpkg to change to gdm3 returns an error: lance@lance-conroe:~$ sudo dpkg-reconfigure gdm3 [sudo] password for lance: gdm.service is not active, cannot reload. invoke-rc.d: initscript gdm3, action "reload" failed. Of course I could also have run sudo dpkg-reconfigure lightdm and accomplished the same thing. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749481 Title: Wrong session marked as selected in session dropdown on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1749481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen
I tested again this AM beginning with a fresh install of 20180227, applying updates, and then installing gnome-panel. During installation I chose to auto-login so after initially logging out and selecting flashback w/metacity I still booted the default DE. But that was expected behavior based on prior testing of Bionic. So I rebooted, then tried logging out again and selecting flashback w/metacity and still I just get the default DE. Next I opened the Users window and turned auto-login off, rebooted and selected flashback w/metacity but still I just get the default DE. Those initial results from last night were based on a slightly older install where I had been using lightdm with the unity greeter, but I purged lightdm and then autoremoved all leftover depends. Clearly that didn't give me a clean enough install to produce a reliable result. Bottom line = it's not fixed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749481 Title: Wrong session marked as selected in session dropdown on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1749481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749481] Re: Wrong session marked as selected in session dropdown on login screen
Works properly to boot both the flashback w/metacity and GNOME Classic sessions now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749481 Title: Wrong session marked as selected in session dropdown on login screen To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/1749481/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743621] Re: GUFW does not appear in any Artful flashback session menus
I'm not sure if there may be any regression potential but bug 1295783 may be worth a look. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743621 Title: GUFW does not appear in any Artful flashback session menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1743621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743621] Re: GUFW does not appear in any Artful flashback session menus
** Tags added: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743621 Title: GUFW does not appear in any Artful flashback session menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1743621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
** Tags added: bionic gnome-applets -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743686] [NEW] File system folder in nautilus Artful/Bionic flashback session does nothing
Public bug reported: Go to Places > Computer, left-click to open "Files", then select File System either by double-click or right-click + open and nothing happens. If you go Places > Home > Other locations and select Computer the file system opens as expected. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Jan 16 21:54:39 2018 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']" InstallationDate: Installed on 2018-01-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful bionic nautilus ** Tags added: bionic nautilus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1743686 Title: File system folder in nautilus Artful/Bionic flashback session does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1743686/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1743621] [NEW] GUFW does not appear in any Artful flashback session menus
Public bug reported: Just testing in Artful and I see that the GUFW UI does not appear anywhere in the flashback session. It's not a big deal because you can launch it by pressing Alt + F2 and searching for GUFW. I'm just hoping to get things polished in Bionic. It does appear properly in Ubuntu's standard GNOME shell session. With the changes to the Settings UI it may be best to simply add it to the System Tools > Preferences menu. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gufw 17.10.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Jan 16 12:09:30 2018 InstallationDate: Installed on 2018-01-16 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gui-ufw UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gui-ufw (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful gnome-panel 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/1743621 Title: GUFW does not appear in any Artful flashback session menus To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gui-ufw/+bug/1743621/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] Re: Standard clock applet is oversized in Artful
Second screenshot. ** Attachment added: "Screenshot from 2017-12-12 15-23-53.png" https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+attachment/5021860/+files/Screenshot%20from%202017-12-12%2015-23-53.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1737836] [NEW] Standard clock applet is oversized in Artful
Public bug reported: In Artful if the standard clock applet is used there is a dead-space to the left of it. In my first screenshot you can see the dead-space between the indicator-applet and the clock applet. In the second screenshot you can see I've moved the clock applet to the left and the same dead-space exists between it and the inhibit-applet. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-panel 1:3.24.1-1ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: GNOME-Flashback:GNOME Date: Tue Dec 12 15:19:25 2017 GsettingsChanges: b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']" b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']" InstallationDate: Installed on 2017-12-11 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful ** Attachment added: "Screenshot from 2017-12-12 15-23-24.png" https://bugs.launchpad.net/bugs/1737836/+attachment/5021856/+files/Screenshot%20from%202017-12-12%2015-23-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/1737836 Title: Standard clock applet is oversized in Artful To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1616511] [NEW] Gray text displayed on black background during auto-resize install
Public bug reported: While testing Ubuntu GNOME Yakkety beta 1 candidates I noticed that the auto-resize "slider" displays gray text on a black background which makes it quite hard to read. I'm attaching a screenshot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubuntu-gnome-desktop 0.67 ProcVersionSignature: Ubuntu 4.4.0-9134.53-generic 4.4.15 Uname: Linux 4.4.0-9134-generic i686 ApportVersion: 2.20.3-0ubuntu7 Architecture: i386 CasperVersion: 1.378 CurrentDesktop: GNOME Date: Wed Aug 24 10:17:31 2016 LiveMediaBuild: Ubuntu-GNOME 16.10 "Yakkety Yak" - Alpha i386 (20160823) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-gnome-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-gnome-meta (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 yakkety ** Attachment added: "Screenshot from 2016-08-24 14-38-43.png" https://bugs.launchpad.net/bugs/1616511/+attachment/4727075/+files/Screenshot%20from%202016-08-24%2014-38-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/1616511 Title: Gray text displayed on black background during auto-resize install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-gnome-meta/+bug/1616511/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1584509] Re: hybrid CDs/DVDs not mounted in xenial
If you have util-linux - 2.27.1-6ubuntu3.1 this should be fixed. Have you updated Lubuntu since installing? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1584509 Title: hybrid CDs/DVDs not mounted in xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1584509/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
"This is because you didn't first upgrade update-manager." I figured something like that. I was convinced that it must have been an error on my part after repeating several more tests with no issue. Chalk that up to either too little (or too much) coffee. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498059] Re: hwe-support-status should be included in newer releases
After running several additional tests I think we're good to go, unless Brian Murray thinks the date mentioned in comment #39 is worth changing. I suppose technically the lts-xenial packages may have been available that soon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498059 Title: hwe-support-status should be included in newer releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1498059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611982] Re: HWE upgrade from vivid to xenial removes support for r128 and mach64
I've run several tests and it looks good to me, so I think we're good to go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611982 Title: HWE upgrade from vivid to xenial removes support for r128 and mach64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati-lts-xenial/+bug/1611982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
I've run several more tests today and all seems well. I can only assume that the failure in comment #17 was an error on my part. So I think we're good to go. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
I have no idea why I had that previous failure. I've since run two more tests. One was a repeat test beginning with a fresh install of Ubuntu GNOME 14.04.3 i386 (just like above) and it worked fine. I ran another test beginning with a fresh install of Ubuntu GNOME 14.04.2 amd64 and it also worked just fine. I'm going to run one additional test beginning with 14.04.4 just to be sure, but I think that one failure must have been a fluke - or something I did wrong. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
I still encountered a failure beginning with Ubuntu GNOME Trusty i386 w/Vivid HWE. There was a kernel upgrade prior to performing the HWE upgrade (most recent prior updates performed on 2016-08-07 followed by installing update-manager from proposed): Start-Date: 2016-08-13 09:58:41 Commandline: apt-get dist-upgrade Install: linux-headers-3.19.0-66:i386 (3.19.0-66.74~14.04.1, automatic), linux-headers-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic), linux-image-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic), linux-image-extra-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic) Upgrade: nautilus-data:i386 (3.10.1-0ubuntu9.9, 3.10.1-0ubuntu9.11), modemmanager:i386 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), initramfs-tools:i386 (0.103ubuntu4.3, 0.103ubuntu4.4), linux-generic-lts-vivid:i386 (3.19.0.65.47, 3.19.0.66.48), libmm-glib0:i386 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), firefox:i386 (47.0+build3-0ubuntu0.14.04.1, 48.0+build2-0ubuntu0.14.04.1), libgd3:i386 (2.1.0-3ubuntu0.2, 2.1.0-3ubuntu0.3), libdrm-intel1:i386 (2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), avahi-autoipd:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libcurl3:i386 (7.35.0-1ubuntu2.6, 7.35.0-1ubuntu2.8), oxideqt-codecs-extra:i386 (1.15.8-0ubuntu0.14.04.1, 1.16.5-0ubuntu0.14.04.1), grub-common:i386 (2.02~beta2-9ubuntu1.11, 2.02~beta2-9ubuntu1.12), libdrm-radeon1:i386 (2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), nautilus:i386 (3.10.1-0ubuntu9.9, 3.10.1-0ubuntu9.11), isc-dhcp-client:i386 (4.2.4-7ubuntu12.4, 4.2.4-7ubuntu12.5), grub-pc:i386 (2.02~beta2-9ubuntu1.11, 2.02~beta2-9ubuntu1.12), libnaut ilus-extension1a:i386 (3.10.1-0ubuntu9.9, 3.10.1-0ubuntu9.11), libavahi-common-data:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libxrandr2:i386 (1.4.2-1, 1.5.0-1~trusty1), libavahi-client3:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libdrm2:i386 (2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), base-files:i386 (7.2ubuntu5.4, 7.2ubuntu5.5), language-pack-gnome-en:i386 (14.04+20150219, 14.04+20160720), libavahi-common3:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libdrm-nouveau2:i386 (2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), language-pack-en:i386 (14.04+20150219, 14.04+20160720), linux-libc-dev:i386 (3.13.0-92.139, 3.13.0-93.140), avahi-utils:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), grub2-common:i386 (2.02~beta2-9ubuntu1.11, 2.02~beta2-9ubuntu1.12), avahi-daemon:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), grub-pc-bin:i386 (2.02~beta2-9ubuntu1.11, 2.02~beta2-9ubuntu1.12), libavahi-gobject0:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libcurl3-gnutls:i386 (7.35.0-1ubuntu2.6, 7.35.0 -1ubuntu2.8), libavahi-glib1:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), language-pack-en-base:i386 (14.04+20150219, 14.04+20160720), initramfs-tools-bin:i386 (0.103ubuntu4.3, 0.103ubuntu4.4), firefox-locale-en:i386 (47.0+build3-0ubuntu0.14.04.1, 48.0+build2-0ubuntu0.14.04.1), isc-dhcp-common:i386 (4.2.4-7ubuntu12.4, 4.2.4-7ubuntu12.5), linux-headers-generic-lts-vivid:i386 (3.19.0.65.47, 3.19.0.66.48), linux-image-generic-lts-vivid:i386 (3.19.0.65.47, 3.19.0.66.48), language-pack-gnome-en-base:i386 (14.04+20150219, 14.04+20160720), libavahi-core7:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1) End-Date: 2016-08-13 10:31:06 I didn't see anything odd in hwe-support-status so accepted the upgrade: Start-Date: 2016-08-13 11:02:05 Commandline: aptdaemon role='role-commit-packages' sender=':1.82' Install: xserver-xorg-input-synaptics-lts-xenial:i386 (1.8.2-1ubuntu3~trusty1, automatic), libgl1-mesa-dri-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 (1.1.0-1~trusty1, automatic), linux-headers-4.4.0-34-generic:i386 (4.4.0-34.53~14.04.1, automatic), libgles2-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), xserver-xorg-video-qxl-lts-xenial:i386 (0.1.4-3ubuntu3~trusty1, automatic), xserver-xorg-video-savage-lts-xenial:i386 (2.3.8-1ubuntu3~trusty1, automatic), xserver-xorg-video-trident-lts-xenial:i386 (1.3.7-1build2~trusty1, automatic), xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-r128-lts-xenial:i386 (6.10.0-1build2~trusty1, automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~tru sty1, automatic), xserver-xorg-video-nouveau-lts-xenial:i386 (1.0.12-1build2~trusty1, automatic), xserver-xorg-input-wacom-lts-xenial:i386 (0.32.0-0ubuntu3~trusty1, automatic), linux-generic-lts-xenial:i386 (4.4.0.34.24), xserver-xorg-video-openchrome-lts-xenial:i386 (0.3.3+git20160310-1~trusty1, automatic), xserver-xorg-input-all-lts-xenial:i386 (7.7+13ubuntu3~trusty2), xserver-xorg-video-neomagic-lts-xenial:i386 (1.2.9-1build2~trusty1, automatic), xserver-xorg-video-vesa-lts-xenial:i386 (2.3.4-1build2~trusty1, automatic),
[Bug 1498059] Re: hwe-support-status should be included in newer releases
I tested an Ubuntu server w/Utopic HWE install tonight and all seemed to go well: hwe-support-status --show-all-unsupported linux-image-3.16.0-77-generic linux-image-generic-lts-utopic linux-headers-generic-lts-utopic linux-image-extra-3.16.0-30-generic linux-generic-lts-utopic linux-image-3.16.0-30-generic linux-image-extra-3.16.0-77-generic hwe-support-status --show-replacements linux-image-generic-lts-xenial linux-generic-lts-xenial hwe-support-status --verbose WARNING: Security updates for your current Hardware Enablement Stack ended on 2016-08-04: * http://wiki.ubuntu.com/1404_HWE_EOL To upgrade to a supported (or longer-supported) configuration: * Upgrade from Ubuntu 14.04 LTS to Ubuntu 16.04 LTS by running: sudo do-release-upgrade OR * Switch to the current security-supported stack by running: sudo apt-get install linux-image-generic-lts-xenial linux-generic-lts-xenial and reboot your system. The applicable bits from apt.history: Start-Date: 2016-08-12 21:36:06 Commandline: apt-get install update-manager-core Upgrade: update-manager-core:amd64 (0.196.14, 0.196.18), python3-update-manager:amd64 (0.196.14, 0.196.18) End-Date: 2016-08-12 21:36:11 Start-Date: 2016-08-12 21:53:36 Commandline: apt-get install linux-image-generic-lts-xenial linux-generic-lts-xenial Install: linux-headers-4.4.0-34-generic:amd64 (4.4.0-34.53~14.04.1, automatic), linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53~14.04.1, automatic), linux-headers-4.4.0-34:amd64 (4.4.0-34.53~14.04.1, automatic), linux-generic-lts-xenial:amd64 (4.4.0.34.24), thermald:amd64 (1.4.3-5~14.04.4, automatic), linux-headers-generic-lts-xenial:amd64 (4.4.0.34.24, automatic), linux-image-extra-4.4.0-34-generic:amd64 (4.4.0-34.53~14.04.1, automatic), linux-image-generic-lts-xenial:amd64 (4.4.0.34.24) End-Date: 2016-08-12 22:11:44 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498059 Title: hwe-support-status should be included in newer releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1498059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498059] Re: hwe-support-status should be included in newer releases
One thing that jumped out at me on an Lubuntu test tonight was the "will become available on 2016-07-21" date: WARNING: Security updates for your current Hardware Enablement Stack ended on 2016-08-04: * http://wiki.ubuntu.com/1404_HWE_EOL There is a graphics stack installed on this system. An upgrade to a configuration supported for the full lifetime of the LTS will become available on 2016-07-21 and can be installed by running 'update-manager' in the Dash. I don't know if that's worth changing or not? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498059 Title: hwe-support-status should be included in newer releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1498059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1611982] Re: HWE upgrade from vivid to xenial removes support for r128 and mach64
I'm going to test Ubuntu GNOME w/Vivid stack tomorrow but tonight I ran a Lubuntu w/Utopic HWE upgrade and I think all looks fine: sudo /usr/lib/update-notifier/update-motd-hwe-eol shows: WARNING: Security updates for your current Hardware Enablement Stack ended on 2016-08-04: * http://wiki.ubuntu.com/1404_HWE_EOL There is a graphics stack installed on this system. An upgrade to a configuration supported for the full lifetime of the LTS will become available on 2016-07-21 and can be installed by running 'update-manager' in the Dash. The same appears if I run hwe-support-status --verbose. Then: lance@lance-desktop:~$ hwe-support-status --show-all-unsupported xserver-xorg-video-cirrus-lts-utopic xserver-xorg-input-evdev-lts-utopic xserver-xorg-video-all-lts-utopic xserver-xorg-video-radeon-lts-utopic xserver-xorg-video-tdfx-lts-utopic xserver-xorg-input-synaptics-lts-utopic xserver-xorg-video-savage-lts-utopic linux-generic-lts-utopic xserver-xorg-video-fbdev-lts-utopic xserver-xorg-input-mouse-lts-utopic xserver-xorg-video-openchrome-lts-utopic xserver-xorg-input-vmmouse-lts-utopic xserver-xorg-input-all-lts-utopic libegl1-mesa-lts-utopic xserver-xorg-input-wacom-lts-utopic libxatracker2-lts-utopic libopenvg1-mesa-lts-utopic libgl1-mesa-dri-lts-utopic libglapi-mesa-lts-utopic xserver-xorg-video-mach64-lts-utopic libgl1-mesa-glx-lts-utopic xserver-xorg-video-siliconmotion-lts-utopic linux-image-extra-3.16.0-30-generic xserver-xorg-video-r128-lts-utopic xserver-xorg-video-vmware-lts-utopic xserver-xorg-video-intel-lts-utopic xserver-xorg-video-nouveau-lts-utopic xserver-xorg-video-vesa-lts-utopic xserver-xorg-video-neomagic-lts-utopic xserver-xorg-lts-utopic xserver-xorg-video-modesetting-lts-utopic xserver-xorg-video-trident-lts-utopic linux-image-extra-3.16.0-77-generic xserver-xorg-core-lts-utopic xserver-xorg-video-sisusb-lts-utopic xserver-xorg-video-ati-lts-utopic linux-image-3.16.0-30-generic libgbm1-lts-utopic linux-image-generic-lts-utopic libegl1-mesa-drivers-lts-utopic linux-headers-generic-lts-utopic xserver-xorg-video-mga-lts-utopic libwayland-egl1-mesa-lts-utopic linux-image-3.16.0-77-generic And: hwe-support-status --show-replacements linux-image-generic-lts-xenial xserver-xorg-lts-xenial libgl1-mesa-glx-lts-xenial linux-generic-lts-xenial libwayland-egl1-mesa-lts-xenial At that point I went ahead and re-enabled proposed so I could test the HWE upgrade via GUI and I think all went well. Afterwards: lance@lance-desktop:~$ apt-cache policy xserver-xorg-video-r128-lts-xenial xserver-xorg-video-r128-lts-xenial: Installed: 6.10.0-1build2~trusty1 Candidate: 6.10.0-1build2~trusty1 Version table: *** 6.10.0-1build2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status lance@lance-desktop:~$ apt-cache policy xserver-xorg-video-mach64-lts-xenial xserver-xorg-video-mach64-lts-xenial: Installed: 6.9.5-1build2~trusty1 Candidate: 6.9.5-1build2~trusty1 Version table: *** 6.9.5-1build2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status lance@lance-desktop:~$ apt-cache policy xserver-xorg-video-ati* lance@lance-desktop:~$ apt-cache policy xserver-xorg-video-ati* xserver-xorg-video-ati-lts-utopic-dbg: Installed: (none) Candidate: 1:7.4.0-2ubuntu2~trusty1 Version table: 1:7.4.0-2ubuntu2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages xserver-xorg-video-ati-dbg: Installed: (none) Candidate: 1:7.3.0-1ubuntu3.1 Version table: 1:7.3.0-1ubuntu3.1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 1:7.3.0-1ubuntu3 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages xserver-xorg-video-ati-lts-saucy-dbg: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 3:5 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages xserver-xorg-video-ati-lts-wily: Installed: (none) Candidate: 1:7.5.0+git20150819-0ubuntu1~trusty1 Version table: 1:7.5.0+git20150819-0ubuntu1~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages xserver-xorg-video-ati-lts-trusty: Installed: (none) Candidate: 3:6 Version table: 3:6 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages xserver-xorg-video-ati-lts-vivid: Installed: (none) Candidate: 1:7.5.0-1ubuntu2~trusty1 Version table: 1:7.5.0-1ubuntu2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages xserver-xorg-video-ati-lts-vivid-dbg: Installed: (none) Candidate: 1:7.5.0-1ubuntu2~trusty1 Version table: 1:7.5.0-1ubuntu2~trusty1 0 500 http://us.archive.ubuntu.com/ubuntu/
[Bug 1611982] Re: HWE upgrade from vivid to xenial removes support for r128 and mach64
So I'd want to check for the presence of xserver-xorg-video-r128-lts- xenial and xserver-xorg-video-mach64-lts-xenial after the HWE upgrade? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1611982 Title: HWE upgrade from vivid to xenial removes support for r128 and mach64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati-lts-xenial/+bug/1611982/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498059] Re: hwe-support-status should be included in newer releases
> is there some other metapackage which I need to install in order to get > libwayland-egl1-mesa-lts-xenial and libwayland-egl1-mesa-lts-xenial:i386 to appear in the replacements > list? I think the devs are trying to figure that out in bug #1610434. For some reason libwayland-egl1-mesa-lts-xenial doesn't get installed when upgrading from an older HWE to the lts-xenial stack. I hadn't tested on multiarch but it does affect both amd64 and i386. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498059 Title: hwe-support-status should be included in newer releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1498059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
I need to wipe these failed HWE upgrades to make space for more testing so I'm attaching apt logs from one in case they may be helpful to the X-Swat team. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/xorg-lts-xenial/+bug/1610434/+attachment/4716384/+files/history.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial
And term.log ** Attachment added: "term.log" https://bugs.launchpad.net/ubuntu/+source/xorg-lts-xenial/+bug/1610434/+attachment/4716385/+files/term.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1498059] Re: hwe-support-status should be included in newer releases
Re bug #1610434 - the HWE upgrade process fails to install libwayland- egl1-mesa-lts-xenial on Ubuntu GNOME so it boots to a blank black screen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1498059 Title: hwe-support-status should be included in newer releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1498059/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Reboot after Ubuntu GNOME Trusty HWE upgrade freezes @ Restoring resolver state
I'm pretty sure I figured this out. The HWE upgrade process fails to install libwayland-egl1-mesa-lts-xenial. If I do so from TTY (or recovery mode) and reboot all seems well! ** Summary changed: - Reboot after Ubuntu GNOME Trusty HWE upgrade freezes @ Restoring resolver state + Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa- lts-xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1610434] Re: Reboot after Ubuntu GNOME Trusty HWE upgrade freezes @ Restoring resolver state
This hardware is also affected running either the nouveau or nvidia drivers: AMD Sempron Processor LE-1250 @ 2.2 GHz nVidia C61 [GeForce 7025 / nForce 630a] (rev a2) nVidia MCP61 High Definition Audio (rev a2) nVidia MCP61 Ethernet (rev a2) 2GB DDR2 RAM -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1610434 Title: Reboot after Ubuntu GNOME Trusty HWE upgrade freezes @ Restoring resolver state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1610434/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
