[Bug 1284196] Re: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot
I've reset this from "Won't Fix" to "Confirmed" because I believe Filofel's analysis merits another look at the issue. ** Changed in: ubiquity (Ubuntu) Status: Won't Fix => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1284196 Title: Install to 3TB disk fails with "attempt to read or write outside of disk" error on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1284196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1962470] Re: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations
I've tried to reproduce this problem in a VirtualBox VM, with no succcess. My suspicion is that there's been a regression somewhere (most likely in GRUB 2 or the Linux kernel) that's causing partial incompatibility with the older UEFI version used on your motherboard, Michael. I say "partial incompatibility" because the installer medium *IS* booting, which would not be the case if the incompatibility were 100% complete. (The installer medium uses GRUB 2 and the Linux kernel, just as does the installed system.) Most of your reports don't clearly distinguish between the boot mode (EFI/UEFI vs. BIOS/CSM/legacy) and the partition table type (GPT vs. MBR). Although EFI-mode booting is generally associated with GPT, and BIOS-mode booting with MBR, the two are not completely linked; it is possible to boot in BIOS mode from a GPT disk or in EFI mode from an MBR disk. At least one of your tests (the one with both an ESP and a BIOS Boot Partition) was probably a BIOS-mode installation to a GPT disk. It's imperative that you understand and report BOTH your boot mode AND your partition table type for understanding this problem. Your boot mode can be determined by looking at /sys/firmware. If that directory has a subdirectory called "efi", then you've booted in EFI mode; if not, then you've booted in BIOS mode (there can be other causes, but not in most normal Ubuntu boots). Your partition table type can be determined by examining the partition table with parted or gdisk. The parted utility, when asked to show the partition table (with its "p" command), shows "Partition Table: gpt" or "Partition Table: msdos", for GPT and MBR, respectively. Using gdisk, you can type "sudo gdisk -l /dev/sda" (changing the device filename, as necessary) and look at the "MBR" and "GPT" lines under "Partition table scan." If the former reads "protective" and the latter reads "present", then the disk is a GPT disk; if the former reads "MBR only" and the latter reads "not present", then the disk is an MBR disk. (Other combinations denote a Hybrid MBR, which should be avoided; or some type of disk damage.) I suggest you post more information on your motherboard's firmware. You can get this from dmesg output soon after booting. Try "sudo dmesg | grep -i EFI". Typically, the EFI version will show up in the first line or two of output, as in: $ sudo dmesg | grep -i EFI [0.00] efi: EFI v2.70 by American Megatrends If you get nothing, then either the computer has been running for too long (the information will eventually scroll out) or it's been booted in BIOS mode. For diagnostic purposes, you might try booting in some way other than GRUB 2. Several other EFI boot loaders exist, including ELILO, SYSLINUX, and the kernel stub loader (which requires a boot manager such as rEFInd, systemd-boot, or even GRUB 2, although I believe the stock Ubuntu configuration of GRUB 2 doesn't use the stub loader). The kernel stub loader is built into the standard Ubuntu kernel. The easiest way to test booting with it is likely to be to install rEFInd (from the Ubuntu refind package); however, rEFInd does not directly support booting from XFS, so you'll need to do this from an ext4fs-based installation (or XFS for root [/] and ext4fs for /boot). ELILO and SYSLINUX will require more configuration effort -- and ELILO is pretty much a dead project at this point, AFAIK, although it could still provide useful diagnostic information. Both also require copying the kernel to the ESP. (See https://www.rodsbooks.com/efi-bootloaders/ for introductory information on using all of these tools.) Whatever you try, if you can get the computer to boot in EFI mode via a method other than GRUB 2, then it's likely that the problem is in GRUB 2; but if alternative boot loaders fail, then the problem is more likely to be in the kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1962470 Title: Jammy Live installer not producing booting gpt partition table / EFI partition hard drive installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1962470/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965302] Re: Text-mode console is unavailable in Jammy
This problem disappeared for me when I upgraded my kernel from 5.15.0-22-generic to 5.15.0-23-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1965302 Title: Text-mode console is unavailable in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1965302] [NEW] Text-mode console is unavailable in Jammy
Public bug reported: I recently updated a system from Focal to Jammy pre-release, and I've found that the text-mode console (obtained by hitting Ctrl+Alt+F1) is blank. It still seems to accept keyboard input; I can log in "blind" and enter commands that have effects, but I see nothing on the screen. By "nothing," I mean it's completely blank. I also see no kernel or systemd boot messages when I set verbose boot mode by removing the "quiet splash" options. The UEFI firmware's display continues to work, as does the display of my boot manager (rEFInd). Note that kernel options gathered by "ubuntu-bug linux" included with this bug report may include a "vga" option, but I don't normally boot with it; I was trying various options to try to recover my console, and that was the latest change I tried that had no effect. My normal kernel options are: ro root=/dev/mapper/seeker-u2204 quiet splash The text-mode console worked fine with Focal. I tried booting with the Focal kernel (vmlinuz-5.4.0-104-generic) post-upgrade, but it crashed with a kernel panic, complaining that it couldn't read the root filesystem. The kernel version that's currently installed is 5.15.0-22-generic. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-22-generic 5.15.0-22.22 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: rodsmith 1462 F pulseaudio /dev/snd/controlC2: rodsmith 1462 F pulseaudio /dev/snd/controlC0: rodsmith 1462 F pulseaudio /dev/snd/controlC1: rodsmith 1462 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Thu Mar 17 08:48:13 2022 HibernationDevice: RESUME=UUID=bf49b324-f388-409c-a93f-d24901a24b60 InstallationDate: Installed on 2014-06-21 (2825 days ago) InstallationMedia: Mythbuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: MSI MS-7793 ProcFB: ProcKernelCmdLine: ro root=/dev/mapper/hostname-u2204 initrd=\initrd.img-5.15.0-22-generic vga RelatedPackageVersions: linux-restricted-modules-5.15.0-22-generic N/A linux-backports-modules-5.15.0-22-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/20/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V3.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G43 (MS-7793) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV3.9:bd04/20/2015:br4.6:svnMSI:pnMS-7793:pvr2.0:rvnMSI:rnA88X-G43(MS-7793):rvr2.0:cvnMSI:ct3:cvr2.0:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7793 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy 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/1965302 Title: Text-mode console is unavailable in Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931243] Re: FTBFS in Impish on s390x
I've now released GPT fdisk version 1.0.8, which incorporates this bug fix, as well as a new feature in gdisk and sgdisk that enables correcting partition names that have already been corrupted by the bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931243 Title: FTBFS in Impish on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1931243] Re: FTBFS in Impish on s390x
I'm the author of GPT fdisk, and I intend to release a version 1.0.8 with this fix within a day or two. The only major change since 1.0.7 is the MR linked by Christian above. If patching earlier versions of GPT fdisk, then the following commit should be included, too: https://sourceforge.net/p/gptfdisk/code/ci/86dd5fea351a5a55bea26b7622eb85ebd6075a60/ This commit fixes a matching problem on reading data. If both are uncorrected, then it looks like it's working, but the partition name is written in the wrong byte order on big-endian systems; and if one fix is applied without the other, then a partition name written by GPT fdisk will appear garbled when read back by GPT fdisk, and there may be compatibility problems with other programs. This affects only big-endian systems. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1931243 Title: FTBFS in Impish on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931243/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1909369] Re: linux-headers-5.10.3-051003-generic is not supported
I can confirm that the PPA described in post #2, above, works on a MacBook Air 6,2. Please get this fixed prior to Hirsute's final release! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1909369 Title: linux-headers-5.10.3-051003-generic is not supported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1909369/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1916962] [NEW] WiFi stopped working on hirsute with bcmwl
Public bug reported: I own a MacBook Air 6,2 on which I've installed several versions of Ubuntu. I recently updated to the hirsute (21.04) pre-release, but WiFi has stopped working. Some web searching suggested re-installing the bcmwl-kernel-source package, which produced the following output: $ sudo apt-get install --reinstall bcmwl-kernel-source [sudo] password for rodsmith: Reading package lists... Done Building dependency tree... Done Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded. Need to get 1,546 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://nessus.rodsbooks.com/ubuntu hirsute/restricted amd64 bcmwl-kernel-source amd64 6.30.223.271+bdcom-0ubuntu7 [1,546 kB] Fetched 1,546 kB in 1s (1,810 kB/s) (Reading database ... 342396 files and directories currently installed.) Preparing to unpack .../bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb ... Removing all DKMS Modules Done. Unpacking bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) over (6.30.223.271+bdcom-0ubuntu7) ... Setting up bcmwl-kernel-source (6.30.223.271+bdcom-0ubuntu7) ... Loading new bcmwl-6.30.223.271+bdcom DKMS files... Building for 5.10.0-14-generic Building for architecture x86_64 Building initial module for 5.10.0-14-generic Error! Bad return status for module build on kernel: 5.10.0-14-generic (x86_64) Consult /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) I'm attaching the /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/make.log file referenced above. Some more information: $ lsb_release -rd Description:Ubuntu Hirsute Hippo (development branch) Release:21.04 $ apt-cache policy bcmwl-kernel-source bcmwl-kernel-source: Installed: 6.30.223.271+bdcom-0ubuntu7 Candidate: 6.30.223.271+bdcom-0ubuntu7 Version table: *** 6.30.223.271+bdcom-0ubuntu7 500 500 http://nessus.rodsbooks.com/ubuntu hirsute/restricted amd64 Packages 100 /var/lib/dpkg/status $ lshw -C network WARNING: you should run this program as super-user. *-network UNCLAIMED description: Network controller product: BCM4360 802.11ac Wireless Network Adapter vendor: Broadcom Inc. and subsidiaries physical id: 0 bus info: pci@:03:00.0 version: 03 width: 64 bits clock: 33MHz capabilities: bus_master cap_list configuration: latency=0 resources: memory:b060-b0607fff memory:b040-b05f *-network description: Ethernet interface physical id: 2 bus info: usb@2:1 logical name: enx00051bb07d68 serial: 00:05:1b:b0:7d:68 size: 1Gbit/s capacity: 1Gbit/s capabilities: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=ax88179_178a driverversion=5.10.0-14-generic duplex=full ip=172.24.125.22 link=yes multicast=yes port=MII speed=1Gbit/s WARNING: output may be incomplete or inaccurate, you should run this program as super-user. (Note that the Ethernet device is a plug-in USB adapter; it's not a stock part of the laptop.) ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Attachment added: "make.log file referenced in the package installation failure message." https://bugs.launchpad.net/bugs/1916962/+attachment/5467261/+files/make.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1916962 Title: WiFi stopped working on hirsute with bcmwl To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1916962/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
I'm the original bug reporter, and in that context (of MAAS deployments), this fix does nothing helpful -- it literally does not change the original observed problem in any way. Thus, I'm marking this verification-failed-focal. (I've not tested under other Ubuntu versions.) ** Tags added: verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
I may have installed it incorrectly, but what I've got is not working. It boots fine with Secure Boot disabled, but it shuts down with the same message about a compromised system as the stock GRUB. What I did to test: 1) Installed grub-efi-amd64-signed (version 1.142.10+2.04-1ubuntu26.8) 2) Copied /usr/lib/grub/x86_64-efi-signed/grubnetx64.efi.signed to /var/lib/maas/boot-resources/snapshot-20210121-195440/bootloader/uefi/amd64/grubx64.efi 3) Booted a test node with Secure Boot disabled; it was fine. 4) Enabled Secure Boot and tried again; it failed. If I've got the wrong package, I can try again. Please advise. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
I agree with Seth Arnold; assuming that the user won't make a mistake is a recipe for disaster. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466150] Re: grub-install breaks when ESP is on raid
@Georg Sauthoff wrote: > Can you name _one_ UEFI implementation that actually does write to an ESP? Offhand, I don't know of an EFI that will write to the ESP automatically; HOWEVER, there are cases when it can happen because of user actions and/or EFI applications' operation. For instance: * The EFI shell includes multiple commands that can write to the ESP when the user executes them -- file copies, file renames, a built-in text editor, etc. * The rEFInd boot manager includes options to store rEFInd-specific variables on the ESP, as well as to create screen shots. The older rEFIt can also create screen shots. * There's a whole Python implementation for EFI, so in theory, users could run Python scripts that write to the EFI. Assuming that the user knows enough to not do these things seems like an unwise assumption, IMHO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466150 Title: grub-install breaks when ESP is on raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1466150/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
*** This bug is a duplicate of bug 1900668 *** https://bugs.launchpad.net/bugs/1900668 It turns out that "normal" does work, although I could swear it didn't work earlier. Perhaps I mis-typed the command. In any event, I'm marking this bug report as a duplicate now. ** This bug has been marked a duplicate of bug 1900668 MAAS PXE Boot stalls with grub 2.02 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
Ah, I thought the fact that "net_bootps" returned a different error meant this was a different bug; but if that's a typo, then perhaps not. Also, typing "normal" (as in comment #5 there) doesn't work. Still, it does look like it's likely a duplicate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] Re: Network boot from MAAS sometimes fails at "grub>" prompt
** Attachment added: "Diagnostics at the "grub>" prompt" https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+attachment/5435180/+files/iKVM_capture%20%281%29.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904588] [NEW] Network boot from MAAS sometimes fails at "grub>" prompt
Public bug reported: On SOME (but not all) boots via MAAS, GRUB hangs at the "grub>" prompt. This happens about 10% or 20% of the time on affected servers (at least ostwald and meitner, two Supermicro servers). The MAAS rackd.log file shows that the node has requested and received GRUB: 2020-11-17 10:08:47 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 10.1.10.82 2020-11-17 10:08:47 provisioningserver.rackdservices.tftp: [info] bootx64.efi requested by 10.1.10.82 2020-11-17 10:08:50 provisioningserver.rackdservices.tftp: [info] grubx64.efi requested by 10.1.10.82 On a failed boot, the process then stops; the node does not request grub.cfg, as happens normally. Watching the console, I see several notices that read "error: Couldn't send network packet." (See attached screen shot.) At the grub> prompt, net_ls_addr shows the expected IP address, and net_ls_routes shows a routing table; however, net_bootps results in an error message stating "can't find command `net_bootps`" (see second attached screen shot.) Once the system is hung, typing "exit" at the "grub>" prompt causes the server to try the next boot option, which usually works (booting via another network interface, in the case of our servers). As noted, this problem occurs on a minority of boots. It can affect reboots after deployment, and if it occurs during deployment, it can prevent deployment because the server will hang at the "grub>" prompt. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New ** Tags: hwcert-server ** Attachment added: "Screen shot showing GRUB complaint about not being able to send packets" https://bugs.launchpad.net/bugs/1904588/+attachment/5435179/+files/iKVM_capture.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904588 Title: Network boot from MAAS sometimes fails at "grub>" prompt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1904588/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1675091] Re: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev
** Changed in: checkbox-support (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1675091 Title: Mellanox MT27500 Family [ConnectX-3] 40G NIC not being detected by udev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox-support/+bug/1675091/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1890803] Re: Groovy amd64 / arm64 / PowerPC deployment seems not working
FWIW, I tried a deployment on an AMD64-architecture server using an ASRock MT-C224 motherboard (one of the experimental Orange Box v3 nodes in 18T), and it failed. I can provide additional logs if required. I have not attempted to install any of the branches associated with this bug report. (I'm not entirely sure how I'd do so.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890803 Title: Groovy amd64 / arm64 / PowerPC deployment seems not working To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1890803/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
As I said, the EFI/foo/grubx64.efi is taken from MAAS. It's presumably netboot-enabled, but can't seem to find its config file, hence the need for the manual entry in steps 9-11. Note that I'm not a MAAS developer, so my understanding of its internals is limited. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1825755] Re: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files
FWIW, I'm having this problem, too, specifically with the icons files, as noted in comment #12, on my mirror running on Ubuntu 18.04. Oddly, some installations using my mirror are fine with this, whereas others complain. Applying the patch linked in comment #12 fixed it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825755 Title: apt-mirror in all versions (including disco and last from github) doesn't mirror Commands-* files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt-mirror/+bug/1825755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
I've managed to create a procedure that duplicates this problem without the involvement of MAAS, except for one file pulled from MAAS. The procedure is awkward, but it reproduces the problem. Here's the procedure: 1) Ensure that Secure Boot is enabled. 2) Install Ubuntu. (I used 20.04 LTS server.) 3) Retrieve shimx64.efi from a MAAS server (/var/lib/maas/boot-resources/current/grubx64.efi). I'm appending a copy of the file I used to this bug report. 4) sudo mkdir /boot/efi/EFI/foo 5) sudo cp /boot/efi/EFI/ubuntu/shimx64.efi /boot/efi/EFI/foo/ 6) Copy the grubx64.efi retrieved from step #3 to /boot/efi/EFI/foo. 7) sudo efibootmgr -c -l \\EFI\\foo\\shimx64.efi -L "Secondary GRUB" 8) Reboot. A grub> prompt should appear, from shimx64.efi in the EFI/foo directory on the ESP. 9) Type "set root='(hd0,gpt1)'" 10) Type "chainloader /EFI/ubuntu/shimx64.efi" 11) Type "boot". The messages noted in the initial bug report should appear and the system should halt. Note that some disk references may need to be adjusted on some systems -- (hd0,gpt1) is the ESP, and the efibootmgr command assumes the ESP is /dev/sda1 from within Ubuntu. Interestingly, substituting grubx64.efi for shimx64.efi in step #10 results in a successful boot, which may be a simple workaround from within MAAS -- if MAAS's configuration is changed to bypass the second shimx64.efi, it may work better. ** Attachment added: "grubx64.efi from a MAAS server" https://bugs.launchpad.net/maas/+bug/1865515/+attachment/5380059/+files/grubx64.efi -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1865515] Re: Chainbooting from grub over the network to local shim breaks chain of trust
Unfortunately, capella in 1SS is not currently accessible by our team. You can test on jehan in 18T, though; I'm sending you an e-mail with details. I don't know what you mean by "remote artifacts" and "local artifacts." The steps to reproduce the problem is simply to enable Secure Boot and attempt to deploy the server; it will fail as described in the initial 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/1865515 Title: Chainbooting from grub over the network to local shim breaks chain of trust To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1865515/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1330021] Re: custom installation on GPT partitioned disks refers to Primary & Logical partitions
This problem still exists in Ubuntu 20.04 Desktop. Selecting either "primary" or "logical" partition types works fine, but the distinction is meaningless for GPT, and asking for the partition type could be confusing to users who aren't expecting it -- they might not understand the difference or they might be misled into thinking that the partition table is of the MBR type, when in fact it's GPT. ** Changed in: ubiquity (Ubuntu) Status: Expired => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1330021 Title: custom installation on GPT partitioned disks refers to Primary & Logical partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1330021/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328497/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] xdpyinfo.txt
apport information ** Attachment added: "xdpyinfo.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328508/+files/xdpyinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328494/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] XorgLogOld.txt
apport information ** Attachment added: "XorgLogOld.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328505/+files/XorgLogOld.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328500/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] DpkgLog.txt
apport information ** Attachment added: "DpkgLog.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328490/+files/DpkgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] UnitySupportTest.txt
apport information ** Attachment added: "UnitySupportTest.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328503/+files/UnitySupportTest.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] upstart.unity-panel-service.log.txt
apport information ** Attachment added: "upstart.unity-panel-service.log.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328507/+files/upstart.unity-panel-service.log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] LightdmLog.txt
apport information ** Attachment added: "LightdmLog.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328492/+files/LightdmLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328498/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] XorgLog.txt
apport information ** Attachment added: "XorgLog.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328504/+files/XorgLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328496/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328499/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328489/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] xserver.devices.txt
apport information ** Attachment added: "xserver.devices.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328509/+files/xserver.devices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] xserver.outputs.txt
apport information ** Attachment added: "xserver.outputs.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328510/+files/xserver.outputs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] LightdmDisplayLog.txt
apport information ** Attachment added: "LightdmDisplayLog.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328491/+files/LightdmDisplayLog.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Re: Unity doesn't start in focal
apport information
** Tags added: apport-collected focal third-party-packages ubuntu
** Description changed:
My system has been upgraded through several Ubuntu versions, and I'm now
(15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa).
I've been using Unity on this system since Ubuntu's installation years
ago, and it's worked fine, including when I first installed the pre-
release Ubuntu 20.04 a week or two ago. I updated packages on 13 Feb or
14 Feb, however. Now, when I log in, I get nothing but a blank screen --
no window manager or desktop environment appears to be running. I'm able
to open a Terminal by right-clicking on the (black) desktop and
selecting "run from Terminal" from the list of options, and I can then
start icewm -- but I need to use the "--replace" option because icewm
thinks a window manager IS running, even though the windows have no
widgets or other ways to control them. (I've been using X since pre-
Linux days, so I know what X without a window manager looks like, and to
all appearances, this is it.)
$ lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
$ apt-cache show ubuntu-unity-desktop | grep Version
Version: 0.2
$ apt-cache show unity | grep Version
Version: 7.5.0+20.04.20200211-0ubuntu1
+ ---
+ ProblemType: Bug
+ .tmp.unity_support_test.0:
+
+ ApportVersion: 2.20.11-0ubuntu16
+ Architecture: amd64
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: focal
+ DistroRelease: Ubuntu 20.04
+ DistroVariant: ubuntu
+ DkmsStatus:
+ fwts-efi-runtime-dkms, 20.01.00, 5.4.0-12-generic, x86_64: installed
(WARNING! Diff between built and installed module!)
+ fwts-efi-runtime-dkms, 20.01.00, 5.4.0-14-generic, x86_64: installed
(WARNING! Diff between built and installed module!)
+ virtualbox, 6.1.2, 5.4.0-14-generic, x86_64: installed
+ GraphicsCard:
+ Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16]
(rev 09) (prog-if 00 [VGA controller])
+Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:3978]
+ GsettingsChanges:
+ b'org.compiz.core' b'active-plugins' b"['core', 'composite', 'opengl',
'place', 'regex', 'resize', 'session', 'snap', 'vpswitch', 'wall', 'animation',
'compiztoolbox', 'fade', 'grid', 'imgpng', 'mousepoll', 'move', 'scale',
'workarounds', 'expo', 'ezoom', 'switcher', 'unityshell']"
+ b'com.canonical.Unity' b'minimize-count' b'37'
+ b'com.ubuntu.user-interface' b'scale-factor' b"{'HDMI-1': 8, 'eDP1': 8,
'HDMI1': 8, 'eDP-1': 8}"
+ b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
+ InstallationDate: Installed on 2017-10-23 (845 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
(20160420.1)
+ MachineType: LENOVO 20289
+ MonitorsUser.xml:
+
+
+ Package: unity 7.5.0+20.04.20200211-0ubuntu1
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: \\vmlinuz-5.4.0-14-generic ro root=/dev/hostname/zesty
initrd=\initrd.img-5.4.0-14-generic
+ ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
+ Tags: third-party-packages focal third-party-packages third-party-packages
ubuntu
+ Uname: Linux 5.4.0-14-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 09/04/2013
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: 7CCN32WW
+ dmi.board.asset.tag: No Asset Tag
+ dmi.board.name: Plum 5A
+ dmi.board.vendor: LENOVO
+ dmi.board.version: 31900058STD
+ dmi.chassis.asset.tag: No Asset Tag
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: Lenovo IdeaPad U530 Touch
+ dmi.modalias:
dmi:bvnLENOVO:bvr7CCN32WW:bd09/04/2013:svnLENOVO:pn20289:pvrLenovoIdeaPadU530Touch:rvnLENOVO:rnPlum5A:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadU530Touch:
+ dmi.product.family: IDEAPAD
+ dmi.product.name: 20289
+ dmi.product.sku: LENOVO_MT_20289
+ dmi.product.version: Lenovo IdeaPad U530 Touch
+ dmi.sys.vendor: LENOVO
+ upstart.unity7.log: WARN 2018-03-10 16:53:55 unity :0 compiz: Fatal
IO error 4 (Interrupted system call) on X server :0.
+ version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
+ version.libdrm2: libdrm2 2.4.100-4
+ version.libgl1-mesa-dri: libgl1-mesa-dri 19.3.3-1ubuntu1
+ version.libgl1-mesa-glx: libgl1-mesa-glx 19.3.3-1ubuntu1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
+ xserver.bootTime: Sat Feb 15 14:00:36 2020
+ xserver.configfile: default
+ xserver.errors:
+
+ xserver.logfile: /var/log/Xorg.0.log
+ xserver.version: 2:1.20.7-2ubuntu1
+
[Bug 1863422] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328502/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328493/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328501/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328495/+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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] Xrandr.txt
apport information ** Attachment added: "Xrandr.txt" https://bugs.launchpad.net/bugs/1863422/+attachment/5328506/+files/Xrandr.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863422] [NEW] Unity doesn't start in focal
Public bug reported: My system has been upgraded through several Ubuntu versions, and I'm now (15 Feb 2020) on a pre-release version of Ubuntu 20.04 (Focal Fossa). I've been using Unity on this system since Ubuntu's installation years ago, and it's worked fine, including when I first installed the pre- release Ubuntu 20.04 a week or two ago. I updated packages on 13 Feb or 14 Feb, however. Now, when I log in, I get nothing but a blank screen -- no window manager or desktop environment appears to be running. I'm able to open a Terminal by right-clicking on the (black) desktop and selecting "run from Terminal" from the list of options, and I can then start icewm -- but I need to use the "--replace" option because icewm thinks a window manager IS running, even though the windows have no widgets or other ways to control them. (I've been using X since pre- Linux days, so I know what X without a window manager looks like, and to all appearances, this is it.) $ lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 $ apt-cache show ubuntu-unity-desktop | grep Version Version: 0.2 $ apt-cache show unity | grep Version Version: 7.5.0+20.04.20200211-0ubuntu1 ** Affects: unity (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/1863422 Title: Unity doesn't start in focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1863422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1861593] [NEW] package mythtv-common 2:30.0+fixes.20190817.5cde0578d8-0ubuntu3 failed to install/upgrade: installed mythtv-common package post-installation script subprocess returned error exit s
Public bug reported: Permissions problem creating file in /tmp. I worked around it by temporarily removing the sticky bit on /tmp; this enabled the package to install, but is obviously unacceptable in a release package. This occurred on upgrading a MythTV frontend box from Eoan to Focal development. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: mythtv-common 2:30.0+fixes.20190817.5cde0578d8-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sat Feb 1 16:11:43 2020 ErrorMessage: installed mythtv-common package post-installation script subprocess returned error exit status 2 InstallationDate: Installed on 2017-10-23 (831 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Installed_mythtv_dbg: 2:30.0+fixes.20190817.5cde0578d8-0ubuntu3 MythTVDirectoryPermissions: total 0 drwxr-xr-x 2 root root 6 Jan 9 10:48 videos Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 3.7.5-1ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.8 SourcePackage: mythtv Title: package mythtv-common 2:30.0+fixes.20190817.5cde0578d8-0ubuntu3 failed to install/upgrade: installed mythtv-common package post-installation script subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mythtv (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861593 Title: package mythtv-common 2:30.0+fixes.20190817.5cde0578d8-0ubuntu3 failed to install/upgrade: installed mythtv-common package post-installation script subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mythtv/+bug/1861593/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851316] Re: Failures of stack stressor in stress-ng 0.10.07 (in Eoan)
If this is the same fix that Colin posted earlier and that I tested, then it's fine; I reported my test results in post #11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851316 Title: Failures of stack stressor in stress-ng 0.10.07 (in Eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/stress-ng/+bug/1851316/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843063] Re: lshw -json output invalid in Eoan
I've tested the PPA in the application that originally prompted my bug report, and it's working fine. Will this be merged into Ubuntu's version of lshw before 20.04 is released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1843063 Title: lshw -json output invalid in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848556] Re: qemu-img check failing on remote image in Eoan
I managed to check the PPA version just now, and it's working fine. Thanks for the quick fix! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848556 Title: qemu-img check failing on remote image in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1848556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1848556] Re: qemu-img check failing on remote image in Eoan
I tried qemu from git, but I get an "unknown protocol" error when I try to access an image via HTTP: $ ./qemu-img check http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img qemu-img: Could not open 'http://10.193.37.117/cloud/eoan-server-cloudimg-amd64.img': Unknown protocol 'http' Is there a development library or ./configure option I need to use to add this support? I didn't see anything obvious in the ./configure output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1848556 Title: qemu-img check failing on remote image in Eoan To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1848556/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1844663] [NEW] sosreport run via sudo creates root-owned files in the user's home directory
Public bug reported: On a fresh Ubuntu 18.04 server installation, running sosreport creates root-owned files in ~/.config. Specifically, I'm using the following command: sudo sosreport --batch --tmp-dir /tmp/ Prior to running this command, ~/.config did not exist. After running the command, ~/.config exists and is owned by root, with a lxd subdirectory: $ sudo ls -lR .config .config: total 4 drwxr-x--- 2 root root 4096 Sep 19 12:16 lxc .config/lxc: total 8 -rw-r--r-- 1 root root 188 Sep 19 12:16 config.yml -rw--- 1 root root 5 Sep 19 12:16 cookies This root ownership of ~/.config and ~/.config/lxd causes problems for subsequent programs run without sudo. $ apt-cache policy sosreport sosreport: Installed: 3.6-1ubuntu0.18.04.3 Candidate: 3.6-1ubuntu0.18.04.3 Version table: *** 3.6-1ubuntu0.18.04.3 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.5-1ubuntu3 500 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages I've reported this bug upstream: https://github.com/sosreport/sos/issues/1787 ** Affects: sosreport (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/1844663 Title: sosreport run via sudo creates root-owned files in the user's home directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1844663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1843063] [NEW] lshw -json output invalid in Eoan
Public bug reported:
Beginning with Ubuntu 19.10 (Eoan) pre-release versions, the "lshw
-json" output appears to be invalid, and can't be parsed with either
Python's json library or the jq stand-alone command:
$ sudo lshw -json | jq .
parse error: Expected separator between values at line 25, column 8
The Python json library reports "Expecting ',' delimiter: line 25 column
8 (char 718)".
The first offending snippet looks like this:
"capabilities" : {
"smbios-2.7" : "SMBIOS version 2.7",
"dmi-2.7" : "DMI version 2.7",
"smp" : "Symmetric Multi-Processing",
"vsyscall32" : "32-bit processes"
}{
"id" : "core",
"class" : "bus",
Note the "}{" line. In pre-Eoan versions of Ubuntu, the equivalent
snippet looks like this:
"capabilities" : {
"smbios-2.7" : "SMBIOS version 2.7",
"dmi-2.7" : "DMI version 2.7",
"vsyscall32" : "32-bit processes"
},
"children" : [
{
"id" : "core",
"class" : "bus",
It looks like the new version is dropping the ', "children" : [' part.
On the offending system:
$ lsb_release -rd
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10
$ apt-cache policy lshw
lshw:
Installed: 02.18.85-0.3
Candidate: 02.18.85-0.3
Version table:
*** 02.18.85-0.3 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status
** Affects: lshw (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/1843063
Title:
lshw -json output invalid in Eoan
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1843063/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819994] Re: cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu
I've tested this on three nodes on two MAAS servers (my own home MAAS server and maastiff, our MAAS server in the certification lab), using both 18.04 and 19.04. It looks good to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819994 Title: cloud-init selects sysconfig netconfig renderer if network-manager is installed on Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1819994/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1828255] [NEW] It's too easy to accidentally delete a container rather than a snapshot
Public bug reported:
The command to delete a container is:
lxc delete {container}/{snapshot}
Unfortunately, if the "/" is omitted, this command deletes {container}
without any sort of prompting. It would be very helpful to add a
prompt/verification when deleting the entire container to avoid mishaps.
Don't ask me how I know that they happen.
** Affects: lxc (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/1828255
Title:
It's too easy to accidentally delete a container rather than a
snapshot
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1828255/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1591352] Re: Ubiquity copies efi boot information to wrong ESP
*** This bug is a duplicate of bug 1396379 *** https://bugs.launchpad.net/bugs/1396379 ** This bug has been marked a duplicate of bug 1396379 installer uses first EFI system partition found even when directed otherwise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1591352 Title: Ubiquity copies efi boot information to wrong ESP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1591352/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762940] Re: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode
This looks to me as if Ubuntu (the kernel, Wayland, and/or the X server, depending on when the problem occurs) is delivering a video mode that the display device can't handle. (With VGA, the display should deliver its capabilities to the computer via EDID, but this doesn't always work correctly.) Thus, the first question is what that "display device" is. The screen shots look like a remote KVM of some sort. Is that the BMC's built-in screen-sharing tool, a network-accessible KVM hardware device (like a Raritan or Avocent), or something else? If possible, I recommend testing in person with a plain monitor plugged directly into the computer, at least as a diagnostic procedure. If that works, then it's likely that the issue is either a matter of a restrictive set of video modes in the remote-access tool, miscommunication between the remote- access tool and the kernel/Wayland/X, or both. Also, if a physical monitor is plugged into the server while it's being accessed remotely, it's conceivable that the kernel/Wayland/X is taking its cues about video mode from the physical monitor rather than from the remote-access tool, thus creating a mismatch. If the problem is caused by the remote access tool, or by an interaction between that and the kernel/Wayland/X, then updating the remote access tool's firmware may fix the problem. Note that the video mode used can vary depending on the kernel version, X vs. Wayland, EFI vs. BIOS boot mode, and other factors. Such variables likely explain why earlier kernels worked but newer ones don't. As a workaround, it might be possibly to forcibly reconfigure the system to use a video mode that will work with the display device. Unfortunately, there are a lot of different ways to do this, depending on the subsystem involved. For instance: * Kernel parameters can set the kernel's video mode. Unfortunately, there are a lot of possibilities even here, including, but not limited to: * nomodeset * video=vga16fb:off * vga16fb.modeset=0 * video=efifb:width:640,height:480 * Try Googling "kernel video mode setting" or something similar for additional possibilities. * X configuration * If you can get X working, even temporarily, you can use the GUI setup tools to change the resolution. * The xrandr tool can be used to probe and set video options; see https://www.x.org/wiki/Projects/XRandR/ * I've not kept up with text-mode (manual) X configuration, but you may be able to find some documentation on how to get it to change video mode. Start here: https://help.ubuntu.com/community/VideoDriverHowto#Xorg.conf.d * Wayland configuration * I'm even less of an expert on this, so I suggest you try Googling "wayland set resolution" or something similar. Finally, note that Ubuntu server certification doesn't cover display devices, so this is NOT a certification blocker. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762940 Title: Ubuntu 18.04 d-i install screen becomes blurry on Huawei server in EFI boot mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1762940/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] Re: Slic3r screen shows no build plate area in Bionic beta
The easiest workaround seems to be to use the slic3r-prusa package rather than the slic3r package. This changes the Slic3r version to be Prusa's fork, which might or might not be your preference; but at least the slic3r-prusa version's display works as expected. Note that the binary name changes from slic3r to slic3r-prusa3d with the package change, too. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
*** This bug is a duplicate of bug 1437353 *** https://bugs.launchpad.net/bugs/1437353 ** This bug has been marked a duplicate of bug 1437353 UEFI network boot hangs at grub for adapter 82599ES 10-Gigabit SFI/SFP+ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported
FWIW, I've run into what I believe to be this bug with MAAS 2.4 and Bionic, minus the juju aspect -- I'm unable to deploy when nodes must rely on a proxy for PPA access. It works without PPAs or when I enable NAT so that the nodes can retrieve the GPG keys without using a proxy. ** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1089389 Title: juju bootstrap fail behind a proxy when a gpg key must be imported To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1770789] [NEW] package kdevelop-data 4:5.2.1-1ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/kdevappwizard/templates/cmake_qt5guiapp.tar.bz2', which is also in package kapptem
Public bug reported: I don't know; I got an automated error report after updating from Xenial to Bionic. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: kdevelop-data 4:5.2.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Fri May 11 21:55:10 2018 ErrorMessage: trying to overwrite '/usr/share/kdevappwizard/templates/cmake_qt5guiapp.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1 InstallationDate: Installed on 2014-05-02 (1471 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2 apt 1.6.1 SourcePackage: kdevelop Title: package kdevelop-data 4:5.2.1-1ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/kdevappwizard/templates/cmake_qt5guiapp.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1 UpgradeStatus: Upgraded to bionic on 2016-09-03 (615 days ago) ** Affects: kdevelop (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1770789 Title: package kdevelop-data 4:5.2.1-1ubuntu4 failed to install/upgrade: trying to overwrite '/usr/share/kdevappwizard/templates/cmake_qt5guiapp.tar.bz2', which is also in package kapptemplate 4:15.12.3-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdevelop/+bug/1770789/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
This may be a duplicate of bug #1437353. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767018] Re: NO test plan for 18.04 server certification
** Also affects: checkbox (Ubuntu) Importance: Undecided Status: New ** Changed in: grub2 (Ubuntu) Status: New => Invalid ** Changed in: checkbox (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767018 Title: NO test plan for 18.04 server certification To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/checkbox/+bug/1767018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1766338] Re: package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1
My bug #1766637, regarding recent MAAS deployments of Bionic, has been marked a duplicate of this one. The MAAS logs in that bug seem to indicate that there's a problem accessing /sys/firmware/efi: Setting up shim (13-0ubuntu2) ... Setting up libefivar1:amd64 (34-1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Setting up sbsigntool (0.6-3.2ubuntu2) ... Setting up libefiboot1:amd64 (34-1) ... Processing triggers for man-db (2.8.3-2) ... Setting up mokutil (0.3.0-0ubuntu5) ... Setting up secureboot-db (1.1) ... Can't access efivars filesystem at /sys/firmware/efi/efivars, aborting For me, the problem is recent -- deployments done a week ago succeeded fine, but today they're failing. (I've done no deployments in the past few days, so I'm not sure exactly when the problem began.) ** Tags added: hwcert-server -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1766338 Title: package shim-signed 1.34.4+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1766338/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1736116] Re: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox
This version did NOT fix the problem for me; VirtualBox is still hanging the computer with 4.13-series kernels. $ dpkg -s kbuild | grep Version Version: 1:0.1.9998svn2814+dfsg-2~ubuntu16.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1736116 Title: [SRU] Host with kernel 4.13 freezes when starting a VM with VirtualBox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kbuild/+bug/1736116/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733662] Re: System hang with Linux kernel due to mainline commit 24247aeeabe
I've tested kernel 4.13.0-38-generic #43-Ubuntu from artful-proposed and the problem does not occur with that kernel. ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733662 Title: System hang with Linux kernel due to mainline commit 24247aeeabe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1733662/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1754909/+attachment/5075507/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] Re: Slic3r screen shows no build plate area in Bionic beta
** Attachment added: "Screen shot showing the problem" https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+attachment/5075508/+files/slic3r.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1754909/+attachment/5075505/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1754909/+attachment/5075506/+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/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1754909/+attachment/5075504/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754909] [NEW] Slic3r screen shows no build plate area in Bionic beta
Public bug reported: After upgrading from Ubuntu 16.04 to the latest Bionic build (as of 10 March 2018), I tried launching Slic3r, and it did run; however, the Plater view shows no boundary for the build plate. I'm attaching a screen shot to show the problem (with a 20mm test cube loaded). The printer I'm using is a delta printer with a round build plate, and its boundaries should be visible in the Plater. Note that the build plate boundary IS shown in the 2D tab, but not in the 3D, Preview, or Layers tabs. This worked fine on the same computers under 16.04. (I've verified this issue on two computers -- a MacBook Air and a Lenovo Ideapad U530.) Here's some version information, from the Lenovo (but both computers have up-to-date software): $ lsb_release -rd Description:Ubuntu Bionic Beaver (development branch) Release:18.04 $ $ apt-cache policy slic3r slic3r: Installed: 1.2.9+dfsg-9 Candidate: 1.2.9+dfsg-9 Version table: *** 1.2.9+dfsg-9 500 500 http://nessus.rodsbooks.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.19.6-1ubuntu2 Candidate: 2:1.19.6-1ubuntu2 Version table: *** 2:1.19.6-1ubuntu2 500 500 http://nessus.rodsbooks.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -a Linux bram 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2017-10-23 (138 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Package: slic3r 1.2.9+dfsg-9 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo _MarkForUpload: True ** Affects: slic3r (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected bionic ** Tags added: apport-collected bionic ** Description changed: After upgrading from Ubuntu 16.04 to the latest Bionic build (as of 10 March 2018), I tried launching Slic3r, and it did run; however, the Plater view shows no boundary for the build plate. I'm attaching a screen shot to show the problem (with a 20mm test cube loaded). The printer I'm using is a delta printer with a round build plate, and its boundaries should be visible in the Plater. Note that the build plate boundary IS shown in the 2D tab, but not in the 3D, Preview, or Layers tabs. This worked fine on the same computers under 16.04. (I've verified this issue on two computers -- a MacBook Air and a Lenovo Ideapad U530.) Here's some version information, from the Lenovo (but both computers have up-to-date software): $ lsb_release -rd Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 $ $ apt-cache policy slic3r slic3r: Installed: 1.2.9+dfsg-9 Candidate: 1.2.9+dfsg-9 Version table: *** 1.2.9+dfsg-9 500 500 http://nessus.rodsbooks.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status $ apt-cache policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.19.6-1ubuntu2 Candidate: 2:1.19.6-1ubuntu2 Version table: *** 2:1.19.6-1ubuntu2 500 500 http://nessus.rodsbooks.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status $ uname -a Linux bram 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux + --- + ApportVersion: 2.20.8-0ubuntu10 + Architecture: amd64 + CurrentDesktop: Unity:Unity7:ubuntu + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2017-10-23 (138 days ago) + InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) + Package: slic3r 1.2.9+dfsg-9 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 + Tags: bionic + Uname: Linux 4.15.0-10-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo + _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754909 Title: Slic3r screen shows no build plate area in Bionic beta To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/slic3r/+bug/1754909/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1748901] Re: System hang with Virtualbox & kernel 4.13.0-32-generic
Sorry it's taken me so long to get back to you; the affected system is
my main work computer, so I can't just go rebooting it constantly, and
I've been busy with other things.
In any event, I'm afraid I haven't had much luck with these newer
kernels. The bottom line is that to get the VirtualBox modules
installed, I need the linux-headers-{version}-generic package, and for
these newer kernels, that package depends on libssl1.1 or greater; but
the 16.04 I'm using ships with libssl1.0, and I'm unwilling to upgrade
that package and risk far greater (and worse) problems or a return to
the old "dependency hell" issues of the 1990s.
If I get the chance, I may try installing bionic on a removable drive
and try to reproduce the problem in that way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748901
Title:
System hang with Virtualbox & kernel 4.13.0-32-generic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748901/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
Andres, the fragments you're seeing in the pcap file look like GRUB code to me. Keep in mind that's just a raw capture of EVERYTHING that passed over the MAAS server's local interface for the time during which I was booting the node, so that includes the GRUB binary that was passed from the MAAS server to the node, and even a few interactions with unrelated machines. You'd need to use wireshark or something similar to properly decode it. As noted in my comment #9, above, it looks to me like ARP responses from the MAAS server are getting lost by the node AFTER GRUB has been (presumably successfully, although I've not tried to analyze the tcpdump results to verify this) delivered to the node. This could be a GRUB bug, a Quanta firmware bug, or a bug in how the two interact with each other. Then too, my knowledge of how they all interact is limited, so my conclusion may be in error. As to the rest, both Jeff and I tried completely disabling each of the machine's two network ports (they're 10Gbps fiber connections, FWIW). In some of my own tests, I tried typing "exit" at the "grub>" prompt. When both ports were enabled, this resulted in a second boot attempt, presumably one from each device. The TFTP request log snippet you've quoted looks consistent with one of those runs. Other EFI machines do work fine; I deployed two yesterday, for instance. (They were both Quanta machines, but a different model.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
I've perused the tcpdump output. It looks like jehan is requesting TFTP data (GRUB) from weavile (the MAAS server), and that goes OK; then there's a LONG string of exchanges like this (copied from the wireshark summary screen): 6399109.865912 QuantaCo_f2:96:c5 Broadcast ARP 60 Who has 10.1.10.2? Tell 10.1.10.164 6400109.865935 HewlettP_f5:69:f1 QuantaCo_f2:96:c5 ARP 42 10.1.10.2 is at 48:0f:cf:f5:69:f1 This goes on for about 31 seconds, according to the time stamps. The mapping of IP addresses and MAC addresses looks correct (weavile is 10.1.10.2 and 48:0f:cf:f5:69:f1; jehan is a8:1e:84:f2:96:c5 and a8:1e:84:f2:96:c6, using whatever IP address weavile gives it, which does seem to be 10.1.10.164 on this run. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
Oh, this was all with Secure Boot disabled, as far as I can tell. (I see no Secure Boot options in the server's setup screens.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1752687] Re: Quanta D52B-1U unable to PXE-boot in EFI mode
Here's a tcpdump capture of a commissioning attempt. I don't know what you mean by "full console log." The original bug report includes a full capture of the IPMI SOL console, and there is no "logs" tab in the MAAS web UI for the node. ** Attachment added: "tcpdump capture of an EFI-mode commissioning attempt." https://bugs.launchpad.net/maas/+bug/1752687/+attachment/5066419/+files/commission-jehan.pcap.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1752687 Title: Quanta D52B-1U unable to PXE-boot in EFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1752687/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
Jeff, The Cisco C-240 M4 (boldore) that originally produced this bug seems to have been returned to OIL, so I can't test with it, at least not quickly; however, I did just run a test with feebas, a Cisco C220 M4. I was able to deploy Ubuntu 16.04 and boot it with Secure Boot enabled, and verified SB was enabled on the deployed system, by using the workaround in post #36. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
The workaround in #36 is now working for me on my home network, too. Perhaps when I tested it in December (comment #39) I had different software versions; or maybe I didn't correctly reproduce the changes in comment #36. I did a diff on what you posted in #48, Jeff, and it exactly matches what I'm using, and what Andres put on weavile, so I don't think your result is caused by an error in your configuration file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747889] Re: (Acer Aspire V3-372) System not booting after update
I've recently encountered this on an HP ProBook 6470b. This system doesn't seem to be able to "remember" its BootOrder variable; typing "sudo efibootmgr" returns results similar to this: BootCurrent: Timeout: 0 seconds No BootOrder is set; firmware will attempt recovery Boot* ubuntu Boot0001* ubuntu Boot0002* ubuntu Boot0003* ubuntu Boot0004* ubuntu Boot0005* ubuntu Boot0006* ubuntu It appears that every time the system reboots, fbx64.efi adds a new "ubuntu" entry; but because the system is amnesiac about BootOrder, those entries are never added. (Note that the "no BootOrder is set; firmware will attempt recovery" message appears after every reboot and even after a power off and reboot. It's running the latest firmware, which is rather elderly [2012].) Rather than reboot, it would be better if fbx64.efi would launch the boot entry that it adds. It would also be good if fbx64.efi could check for existing entries that match what it wants rather than blindly add a new one; as it is, on a system like my HP, sooner or later the NVRAM will fill up if the user walks away while the system is in its reboot loop, and of course this will cause additional problems, possibly including a "Samsung brick" type of scenario. I don't know if this HP has a buggy firmware or failing NVRAM. (I bought it used and so I don't know how it worked when new.) I've seen EFI flakiness on other systems as they age; one four-year-old laptop I own can't accept ANY NVRAM changes, for instance. Both this HP ProBook and that other four-year-old laptop are perfectly functional otherwise. Having a way to work around such minor hardware failures as systems age is desirable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747889 Title: (Acer Aspire V3-372) System not booting after update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1747889/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1711203] Re: Deployments fail when Secure Boot enabled
Mathieu, the workaround of chainloading GRUB rather than shim that you suggested in comment #36 does not work; see my comment #39. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1711203 Title: Deployments fail when Secure Boot enabled To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1711203/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
Every other system I've run through this round has shown the same failure on this test. I suspect it's simply a very high false alarm rate, as Jeff suggests, so I'm closing this out as "invalid." ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056222/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056224/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
>From Jeff Lane via e-mail: > Hi. I can’t see the details right now because I’m on my phone and away from > my desk. That said, > that check is very basic, it fails on any call traces. > > Stress-ng might trigger some call traces if it triggers the OOM Killer which > is fine, and > should be expected during the memory tests. More troubling would be kernel > panics. > > That check is VERY new and fairly trigger happy. It will definitely need some > refinement. > > Point is, take it with a grain of salt and expect a lot of false positives > from that check > for now. Most of the call traces are indeed on stress-ng, so this may not be a problem at all. It might be best if somebody from the kernel team can check the results just to be sure, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056226/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056223/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056227/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056225/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056217/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056218/+files/JournalErrors.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056220/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Card0.Codecs.codec.3.txt
apport information ** Attachment added: "Card0.Codecs.codec.3.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056216/+files/Card0.Codecs.codec.3.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
apport information ** Tags added: apport-collected uec-images ** Description changed: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.4.0-116-generic. + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.15 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D3', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + Card0.Amixer.info: Error: [Errno 2] No such file or directory + Card0.Amixer.values: Error: [Errno 2] No such file or directory + DistroRelease: Ubuntu 16.04 + IwConfig: Error: [Errno 2] No such file or directory + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic root=UUID=8dc86bcc-d6d5-4f11-b76e-c0b218a705c7 ro + ProcVersionSignature: User Name 4.4.0-116.140-generic 4.4.98 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-116-generic N/A + linux-backports-modules-4.4.0-116-generic N/A + linux-firmware 1.157.16 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial uec-images + Uname: Linux 4.4.0-116-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video + _MarkForUpload: True + dmi.bios.date: 09/10/2015 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: RKPPT10H.86A.0043.2015.0910.1015 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: D53427RKE + dmi.board.vendor: Intel Corporation + dmi.board.version: G87971-403 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0043.2015.0910.1015:bd09/10/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-403:cvn:ct3:cvr: ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056214/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056219/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056221/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1749818/+attachment/5056215/+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/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] Re: Call Trace messages in syslog with 4.4.0-116 kernel
** Attachment added: "Output of "sudo lspci -vnvn"" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+attachment/5056108/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749818] [NEW] Call Trace messages in syslog with 4.4.0-116 kernel
Public bug reported: In doing regression testing of the 4.4.0-116 kernel with the server certification tools, the miscellanea/call-trace-check test failed on one system. (Maybe more, too; this was the first system to finish the tests.) This test simply looks for the string "Call Trace" in /var/log/syslog, and there are 44 such call traces. The system being tested was an Intel NUC DC53427HYE. The complete test results are available here: https://certification.canonical.com/hardware/201508-19150/submission/127493/ I'm attaching the syslog file to this bug report, along with other requested data $ cat /proc/version_signature Ubuntu 4.4.0-116.140-generic 4.4.98 $ lsb_release -rd Description:Ubuntu 16.04.3 LTS Release:16.04 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "/var/log/syslog from affected system" https://bugs.launchpad.net/bugs/1749818/+attachment/5056107/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749818 Title: Call Trace messages in syslog with 4.4.0-116 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749818/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
