[Bug 1729305] Re: CouchDB service fails to start
Also, if you're so inclined, I now have CouchDB 1.7.0 test packages for Artful here: https://launchpad.net/~jderose/+archive/ubuntu/couchdb-1.7.0 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729305 Title: CouchDB service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1729305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1729305] Re: CouchDB service fails to start
Devin, Thanks for the bug report! CouchDB 1.6.x doesn't work with the Erlang 20.0.4 packages in Artful. I've been working on CouchDB 2.1 packages for Artful for internal use at System76, but it's a much different beast in many ways and also has upstream packaging changes that make it very difficult (if not impossible) to get it into Ubuntu as an official package (even just in universe). However, the just announced CouchDB 1.7.0 RC is promising: https://lists.apache.org/thread.html/30162c3c859cf0dc66d489ae416a2e0e4f2fedecdf892b62c484abc7@%3Cdev.couchdb.apache.org%3E I'm currently testing it. Assuming I don't hit any deal breakers, I'm going to try and get this package into Bionic, and might also be able to get it released in Artful as the current CouchDB 1.6.0 package isn't usable in Artful (as you know). If you happen to spend any time testing 1.7.0, please let me know what your experience is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1729305 Title: CouchDB service fails to start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/couchdb/+bug/1729305/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1663299] [NEW] 16.04.2: `linux-signed-image-generic-hwe-16.04` is autoremovable after UEFI install
Public bug reported: Steps to reproduce: 1) Fresh UEFI install using 20170209 16.04.2 daily ISO (sha1sum: 93378778ba193f6fbcac222a8d60a4bae52c94e8) 2) Reboot into install and run `sudo apt-get autoremove` Thanks! ** Affects: debian-installer (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/1663299 Title: 16.04.2: `linux-signed-image-generic-hwe-16.04` is autoremovable after UEFI install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1663299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1621507] Re: initramfs-tools configure_networking() fails to dhcp ipv6 addresses
Mathieu, Okay, just finished testing with xenial-proposed, no issues found. Things are working as expected for my use-case (with no adjustments on my end), so at least for the corners that my particular use-cases covers, this proposed package seems regression free. I tested PXE booting into a "diskless" read-only Ubuntu server environment (using syslinux as the bootloader). Tested in both BIOS and UEFI mode. Sorry it took me a bit to do this follow-up testing! Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1621507 Title: initramfs-tools configure_networking() fails to dhcp ipv6 addresses To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1621507/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Steve, I'm not sure whether it was a truly representative test, but it works fine with latest Xenial daily desktop ISO under QEMU + OVMF, and these dailies do have xenial-proposed enabled. (I'm testing the 2016 ISO, sha1sum 0ed4db8dad7142837ce9175e2b9617c4dd93a326.) I recall that d-i needed to be rebuilt for a new shim to be properly represented in an ISO... has this happened yet? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Mathieu, I tested your PPA package with Xenial: with no config changes on my end, it's working as expected from my use case. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637985] Re: Install Fail - Attempt to configure apt to install additional packages from CD
FYI, same thing is happening with the latest Zesty server ISO (see attached). ** Attachment added: "Screenshot from 2016-10-31 14-32-09.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770253/+files/Screenshot%20from%202016-10-31%2014-32-09.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637985 Title: Install Fail - Attempt to configure apt to install additional packages from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1637985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1637985] Re: Install Fail - Attempt to configure apt to install additional packages from CD
Attaching tarbal of /var/log from lp:1638086 ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1637985/+attachment/4770249/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1637985 Title: Install Fail - Attempt to configure apt to install additional packages from CD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1637985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638086] Re: Zesty: An attempt to configure apt to install additional packages from the CD failed
*** This bug is a duplicate of bug 1637985 *** https://bugs.launchpad.net/bugs/1637985 Attaching tarball of /var/log ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+attachment/4770250/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638086 Title: Zesty: An attempt to configure apt to install additional packages from the CD failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1638086] [NEW] Zesty: An attempt to configure apt to install additional packages from the CD failed
Public bug reported: The current Zesty daily desktop ISO can't be installed, fails with error message in bug title. Please see attached screenshot. I tried both "Install Ubuntu" and an OEM install, both fail. ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2016-10-31 11-59-34.png" https://bugs.launchpad.net/bugs/1638086/+attachment/4770232/+files/Screenshot%20from%202016-10-31%2011-59-34.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638086 Title: Zesty: An attempt to configure apt to install additional packages from the CD failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1638086/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Okay, tested 0.122ubuntu8.5 from xenial-proposed, and it fixes the issue for my use-case. But I'm not changing verification-needed to verification-done yet as I don't know if it fixes the use case of the original reporter. @scotte - can you please confirm whether this fixes things for you? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632767] Re: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
@jbicha hmm, I didn't experience this with the final Ubuntu desktop 16.10 ISOs... what was your experience with the final 16.10 Ubuntu GNOME ISOs? But I also don't think this is happening with perfect determinism either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Oh, and to be clear, I have no problem with this change in Yakkety. It's just starting to feel a bit too invasive in my opinion for Xenial. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@martin - I tested the proposed package, and it's workable, but there are behavior changes still compared to prior to when this regression was introduced (in particular, the boot is a lot slower when there are mulitple NICs but only one will be configured, even when I use "ip=:eth0:dhcp"). @scott - I think I agree with you. Considering this is an SRU for the LTS, I'd prefer that as little behavior change be introduced as possible. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
Attaching a tarbal of everything i have in /var/log, not sure it's useful (not my "ephemeral" environment is read-only with /var/log on a tmpfs, so it's mostly empty). Also here's my exact /proc/cmdline from within the booted ephemeral environment: BOOT_IMAGE=vmlinuz-4.4.0-42-generic initrd=initrd.img-4.4.0-42-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 BOOTIF=01-80-fa-5b-36-f5-86 ** Attachment added: "log.tgz" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4760012/+files/log.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@chiluk - I tested the latest package in your PPA, but something seems slightly wonky for my use case. Networking seems to come up correctly, but it takes longer than it should and I see warnings like this repeated several times: ip: ether "dev" is duplicate, or "permanent" is garbage -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1632767] [NEW] yakkety: desktop ISO fails to reboot after install: Failed deactivating swap
Public bug reported: The 20161012.1 yakkety desktop ISO fails to reboot after the install completes (see attached screenshot). Tested on QEMU in BIOS and UEFI mode, which is where the screenshot is from. Same thing is seemingly happening on hardware (reboot hangs), although I don't see this particular debugging output on hardware. The systemd related logging might be a red haring... I'm not sure this is actually a systemd bug, just that it seems the correct starting point. Thanks! ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-10-12 06-14-05.png" https://bugs.launchpad.net/bugs/1632767/+attachment/4759958/+files/Screenshot%20from%202016-10-12%2006-14-05.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1632767 Title: yakkety: desktop ISO fails to reboot after install: Failed deactivating swap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1632767/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
@chiluk - the package in your PPA fixes it from my use case, thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1631474] Re: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option
As asked by chiluk on IRC, here's my PXE boot configuration (well, representative one anyway, the exact kernel version will obviously change): DEFAULT ubuntu LABEL ubuntu LINUX vmlinuz-4.4.0-36-generic APPEND initrd=initrd.img-4.4.0-36-generic root=/dev/nfs nfsroot=10.17.76.1:/var/lib/tribble/ephemeral ip=dhcp ro nomodeset net.ifnames=0 IPAPPEND 2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1631474 Title: No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
So far I haven't encountered this again... so might have been a fluke with the state of Yakkety for a brief period, phase of the moon, or whatever. But if I do encounter it again, I'll collect as many details as I can. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
I'm back to testing u-s-d started under systemd, and I found some serious wackiness observing `sudo journalctl -f` when I use the brigtness up/down hotkeys. The attached "wacky-journalctl.txt" file has the output of `sudo journalctl -f` during which I used the brightness hotkeys *twice*, and you'll see a slew interesting things happening *each* time I press a hot key. For example, this is a small excerpt of what I'm seeing for every hotkey press: Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Created slice User Slice of root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Starting User Manager for UID 0... Oct 06 10:44:50 jason-Gazelle-Professional systemd[1]: Started Session 1 of user root. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: pam_unix(systemd-user:session): session opened for user root by (uid=0) Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Paths. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Timers. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Listening on D-Bus User Message Bus Socket. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Sockets. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Reached target Basic System. Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Starting Run Click user-level hooks... Oct 06 10:44:50 jason-Gazelle-Professional systemd[4805]: Started D-Bus User Message Bus. Oct 06 10:44:50 jason-Gazelle-Professional dbus-daemon[4839]: Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.service' ** Attachment added: "wacky-journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756139/+files/wacky-journalctl.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
`sudo forkstat -D 4` when u-s-d is started under systemd and I press the brightness up hotkey. ** Attachment added: "with-systemd.txt" https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756099/+files/with-systemd.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626651 Title: brightness keys are handled slower in Yakkety than Xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626651] Re: brightness keys are handled slower in Yakkety than Xenial
Okay, an interesting hint is that this problem seems to be fixed if
u-s-d is started under the Upstart user session instead of the systemd
user session.
If anyone wants to try this, just comment out these three lines in
/etc/X11/Xsession.d/00upstart:
if [ "${1#*.target}" != "$1" ]; then
export
XDG_CONFIG_DIRS="/usr/share/upstart/systemd-session:$XDG_CONFIG_DIRS"
fi
I'm attaching the result of me starting u-s-d under Upstart, running
`sudo forkstat -D 4`, and then pressing the brightness up key.
(I'll attach the same from under systemd next comment.)
>From talking to Martin Pitt on IRC, sounds like switching u-s-d back to
being started by Upstart might not be viable, but hopefully this at
least helps narrow the search.
** Attachment added: "with-upstart.txt"
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1626651/+attachment/4756098/+files/with-upstart.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1626651
Title:
brightness keys are handled slower in Yakkety than Xenial
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1626651/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
And I sanity checked the server ISO on the same slew of UEFI hardware... no issues found. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Okay, the 20161005.1 ISOs seem to have done the trick. Tested the desktop and server ISOs under QEMU+OVMF, plus tested the desktop ISO on a slew of UEFI hardware. No issues encountered shim-wise. I'll test the server ISO on UEFI hardware shortly, but there are a few other things I need to finish up first. Big thanks to everyone who helped on this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Oops, I attached the wrong screenshot, here's the correct one. ** Attachment added: "Screenshot from 2016-10-05 12-06-26.png" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755346/+files/Screenshot%20from%202016-10-05%2012-06-26.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
** Attachment removed: "Screenshot from 2013-11-11 11:45:50.png" https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Yeah, I can do this, assuming I can reproduce it again. This is on my work machine, so I had to just kill `fwupd` so I could get on with my work in the meantime :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] Re: fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
One other useful detail. There are actually 2 fwupd processes running, both started by PID 1: ps -ef | grep fwupd root 2823 1 99 11:41 ?01:35:03 /usr/lib/x86_64-linux-gnu/fwupd/fwupd root 4712 1 0 11:44 ?00:00:00 /usr/lib/x86_64-linux-gnu/fwupd/fwupd But it's only process "2823" that's chewing up all the CPU. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630711] [NEW] fwupd using 200% CPU, but status of systemd services is "inactive (dead)"
Public bug reported: Just hit this, haven't yet dug into details or tried to reproduce it. I booted up a nearly up-to-date Yakkety desktop, noticed my fans were running like crazy, and looking at top shows `fwupd` is the culprit (see attached screenshot). I don't know much about fwupd, but I'm guessing it's probably run through systemd services. Interestingly, `systemctl status` show "inactive (dead)" for the two service files installed by `fwupd`: fwupd.service fwupd-offline-update.service I also checked `fwupdate-cleanup.service` from the `fwupdate` package, and it likewise shows "inactive (dead)". So I'm not exactly sure how this fwupd process was started, why it's still running. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: fwupd 0.7.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-19.21-generic 4.8.0-rc8 Uname: Linux 4.8.0-19-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Oct 5 12:15:10 2016 SourcePackage: fwupd UpgradeStatus: Upgraded to yakkety on 2016-10-03 (1 days ago) ** Affects: fwupd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Screenshot from 2013-11-11 11:45:50.png" https://bugs.launchpad.net/bugs/1630711/+attachment/4755311/+files/Screenshot%20from%202013-11-11%2011%3A45%3A50.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630711 Title: fwupd using 200% CPU, but status of systemd services is "inactive (dead)" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1630711/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630341] Re: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices
Thanks for the feedback, Robie! I believe the underlying problem was this kernel bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1628336 The /dev/nbd0p1, etc, partition devices were never getting creating automatically after connecting the device, no matter how long you waited. So you had to call partprobe, whereas on Xenial and older you didn't. And you bring up some good points about my scripts being fragile unless I do some sort of polling or using inotify (although in practice I haven't had problems with this). But I agree this shouldn't really be treated as a bug, should be marked invalid. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630341 Title: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1630341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Hmmm, today's yakkety-desktop-amd64.iso (sha1:494bc027be3d29c494eb17d057dcc51cdfc6f50b) is seemingly still using the broken shim package? I'm guessing there's something special about how the shim package gets onto the ISO as it doesn't seem to be listed in yakkety-desktop- amd64.manifest? But for whatever reason, I'm still getting the same exception when debugging with `-serial stdio`: X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - RIP - 7E64D5BA, CS - 0038, RFLAGS - 00010202 ExceptionData - RAX - AFAFAFAFAFAFAFAF, RCX - 7F1C5820, RDX - 7F1C5820 RBX - 7F132198, RSP - 7FB1BA40, RBP - 7FB1BAF0 RSI - 7E6DBD9A, RDI - 7E62CFBA R8 - 0004, R9 - , R10 - 0020 R11 - 0002, R12 - 7EEB34B8, R13 - 7EEB34C0 R14 - 7FB33620, R15 - 7EDD6018 DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 8033, CR2 - , CR3 - 7FABA000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 7FAA8698 0047, LDTR - IDTR - 7F5E4018 0FFF, TR - FXSAVE_STATE - 7FB1B6A0 Find PE image (No PDB) (ImageBase=7E62D000, EntryPoint=7E64A000) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1630341] [NEW] yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices
Public bug reported: On Ubuntu 12.10 through Ubuntu 16.04, something like this worked with 100% reliability in my experience: sudo modprobe nbd sudo qemu-nbd -c /dev/nbd0 /my/vm/image.qcow2 sudo mount /dev/nbd0p1 /mnt But on Yakkety, this *almost* always fails because the /dev/nbd0p1 device doesn't exist by the time the `sudo mount /dev/nbd0p1 /mnt` command is run. I found an existing Debian bug about this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 Unfortunately, I feel the bug reporter got the brush off there, but I can confirm that `qemu-nbd` previously worked exactly as the bug reporter claims (on Ubuntu anyway, not sure about Debian). I have automated tooling that has done this exact thing many thousands of times on Ubuntu 12.10 through 16.04 without issue. Although in defense of the Debian maintainer, my hunch is this behavior change likely isn't the result of changes in the `qemu-img` package itself. A curiosity of note is that although this usually fails on Yakkety, it did work for me a few times (in my testing thus far, I'd say it succeeds less than 5% of the time). I haven't yet found a way to reproduce these successful cases, nor have I yet spotted any pattern in the cases in which it works vs. cases in which it doesn't work. On Yakkety I can *mostly* work-around this by calling `sudo partprobe /dev/nbd0` prior to trying to mount the device: sudo modprobe nbd sudo qemu-nbd -c /dev/nbd0 /my/vm/image.qcow2 sudo partprobe /dev/nbd0 sudo mount /dev/nbd0p1 /mnt At first I thought this was a 100% reliable solution on Yakkety, but it still sometimes fails. I haven't had as much time testing this yet, but I'd say it probably succeeds 80% of the time or so, fails the remaining 20%. I hate to say it, but on the surface this feels like a systemd bug as I've encountered systemd + qemu-nbd problems in the past: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1435428 Plus whenever I hear of "weird problems mounting or unmounting devices" plus "non-determinism"... systemd comes to mind :P So my hunch is this isn't actually a `qemu-img` bug. My best guess is systemd, but it could also be the Linux 4.4 vs 4.8 kernel or something else I haven't thought of. Still, without stronger evidence, to me it seems `qemu-img` is the best package to initially file this bug against. Also, I'm not yet sure how best to debug this, but the most helpful logging I've found thus far is in /var/log/syslog. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: qemu-utils 1:2.6.1+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 Uname: Linux 4.8.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity:Unity7 Date: Tue Oct 4 10:44:58 2016 KvmCmdLine: COMMAND STAT EUID RUID PID PPID %CPU COMMAND kvm-irqfd-clean S< 0 0 18420 2 0.0 [kvm-irqfd-clean] MachineType: System76, Inc. Serval WS ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic.efi.signed root=UUID=4b57bce3-eed0-426b-adfe-4f7a834e2ddf ro net.ifnames=0 quiet splash vt.handoff=7 SourcePackage: qemu UpgradeStatus: Upgraded to yakkety on 2016-10-03 (0 days ago) dmi.bios.date: 06/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.03.03RSY2 dmi.board.asset.tag: Tag 12345 dmi.board.name: Serval WS dmi.board.vendor: System76, Inc. dmi.board.version: serw8-17g dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: Serval WS dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.03.03RSY2:bd06/09/2015:svnSystem76,Inc.:pnServalWS:pvrserw8-17g:rvnSystem76,Inc.:rnServalWS:rvrserw8-17g:cvnSystem76,Inc.:ct9:cvrServalWS: dmi.product.name: Serval WS dmi.product.version: serw8-17g dmi.sys.vendor: System76, Inc. ** Affects: qemu (Ubuntu) Importance: Undecided Status: New ** Affects: qemu (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug yakkety ** Bug watch added: Debian Bug tracker #824553 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 ** Also affects: qemu (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=824553 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630341 Title: yakkety: behavior change in `qemu-nbd -c $DEV $FILENAME`: doesn't automatically create partion devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1630341/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] Re: yakkety server: fails to detect and mount CD-ROM
Ah, sorry, I forgot to follow up on this. Yes, the bug has been fixed for about a week now (but I was on vacation). Is it better to mark this as Fix Released instead? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Mathieu - I was on vacation last week, so I wasn't in the loop on IRC. What's the current status of this? Does it seem feasible that the fixed shim package can be signed (and FFE'd) in time for 16.10? Or are we already at the point where reverting to the shim 0.8-0ubuntu2 package from Xenial (with whatever needed version trickery) is the only realistic hope for fixing this? If there's anything I can do to help, please don't hesitate to ask! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] Re: yakkety server: fails to detect and mount CD-ROM
** Summary changed: - yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode) + yakkety server: fails to detect and mount CD-ROM ** Description changed: The latest yakkety server amd64 daily (20160921.1, sha1sum b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount the CD-ROM. Please see attached screenshot. - I found this testing under QEMU (BIOS mode), not yet sure whether it - effects hardware. But I'll be testing on hardware shortly. + I confirmed that this is happening on physical hardware when booting the + server installer from a USB stick (I tested in both UEFI and BIOS mode, + both fail). + + This also happens under QEMU in BIOS mode. I can't test under QEMU in + UEFI mode because of lp:1624096 + + Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1626622] [NEW] yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode)
Public bug reported: The latest yakkety server amd64 daily (20160921.1, sha1sum b3e9f59397389bf23390f4869d3aef46de5d105c) fails to detect and mount the CD-ROM. Please see attached screenshot. I found this testing under QEMU (BIOS mode), not yet sure whether it effects hardware. But I'll be testing on hardware shortly. ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: yakkety ** Attachment added: "Screenshot from 2016-09-22 09-29-46.png" https://bugs.launchpad.net/bugs/1626622/+attachment/4746306/+files/Screenshot%20from%202016-09-22%2009-29-46.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1626622 Title: yakkety server: fails to detect and mount CD-ROM (QEMU, BIOS mode) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1626622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@@Mathieu yeah, if you can get me a custom ISO with an updated shim package (doesn't need to be signed, I'm not using secure boot), then I'll giving a thorough testing under QEMU and on all the UEFI hardware I have access too (6 different laptops, 3 different desktops). Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Laszlo - darn, no luck. Following your recommendations, PXE booting is no longer attempted, but I still end up at Shell> and the installer doesn't launch. I'm attaching the isolated test script I'm using ATM. If I try it with the latest Yakkety desktop daily ISO, I hit the above hardware exception (as expected because of the issue in `shim`). However, if I try it with the same ISO modified to include /EFI/BOOT/fallback.efi, it goes directly to Shell> rather than launching the installer. Please let me know if you spot any goofs in my script or can think of anything else to try. (Note: my test script doesn't have any -net devices at all, but my image mastering tools do, so that's why I know that PXE booting wasn't being tried any more.) @Mathieu - under the assumption that there is more to this than just the issue in `shim`, or at least that the presence of fallback.efi can't fully work-around it, do you have any suggestions as to where I should go looking for other things that have changed between the Yakkety and Xenial ISOs, things that might be interacting with the `shim` bug in odd ways? Also, I should make it clear why this bug is critical to System76: our imaging mastering tools use QEMU + OVMF to create our UEFI images, so this is something we absolutely need to find some solution for in order to ship 16.10. Because (most likely) we'll need 16.10 to initially ship Kaby Lake :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
Oops, forgot to attach my test script :P ** Attachment added: "test-yakkety-guest.sh" https://bugs.launchpad.net/ubuntu/+source/shim/+bug/1624096/+attachment/4745643/+files/test-yakkety-guest.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Laszlo - thank you very much for the detailed explanation! Sounds like your tips, plus /EFI/BOOT/fallback.efi being present on the ISO, should be enough for me to work-around this issue. I'll let you know how it goes. Thanks again! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: backport (or rebase to) fix eliminating a double-close in shim
@Mathieu - I've been doing some quick experiments with fallback.efi on the ISO, and I'm not sure that alone will fix things. The problem is that when fallback.efi is present, the installer isn't launching. Instead, OVMF tries to PXE boot (which in my test environment fails because I don't have the needed DHCP/TFTP setup), then OVMF falls back to Shell> I tried adding /EFI/BOOT/fallback.efi to both the latest Yakkety daily ISO and the 16.04.1 ISO. In both cases, the installer doesn't boot, I end up at Shell> So although fallback.efi can work around the X64 Exception in the Yakkety version of shim, it still doesn't give you a bootable installer. If there's something obvious I'm missing, please let me know! Also, do you have any idea why this faulty shim code path is taken when running under QEMU + OVMF, but does not seem to be taken when running on physical hardware? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: backport (or rebase to) fix eliminating a double-close in shim To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-cd/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
@Laszlo - awesome, thanks! Do you happen to know what version introduced 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/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] Re: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
@Laszlo - thanks for the debugging tips! I'm getting the same result that you are. I found a possibly related opensuse bug: https://lists.opensuse.org/opensuse-bugs/2016-01/msg00965.html -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1624096] [NEW] yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode
Public bug reported: Sometime after August 25th (or so) something changed in the Yakkety ISOs that make them no longer boot under QEMU in UEFI mode. However, the ISOs do work fine still on the physical UEFI hardware I've tested (3 different systems). I'm not sure about other VM solutions like Virtual Box, etc., as I haven't tested under anything other than QEMU. But under QEMU, UEFI mode installs are definitely broken. You get stuck in the OVMF firmware with the following text on the screen (see attached screenshot): Boot Failed. EFI Floppy Boot Failed. EFI Floppy 1 Thus far I've only tested with a Xenial host, so I'm not sure whether this problem exists with a Yakkety host + Yakkety guest. This problem also doesn't seem to be the result of any changes in QEMU (and related) in Xenial. With a Xenial host, you can still do UEFI mode installs fine under QEMU when the guest is using the 16.04.1 ISOs, and likewise when the guest is using the latest Xenial daily (16.04.2 WIP) ISOs. So the problem seems to be only when using a Yakkety guest in UEFI mode. Note this problem effects both Yakkety desktop and server ISOs (when installing under QEMU in UEFI mode). Finally, on the off chance it might be helpful to anyone who comes across this bug report, I wrote a blog post a while back on how to use QEMU in UEFI mode on a Xenial (or newer) host: http://blog.system76.com/post/139138591598/howto-qemu-w-ubuntu-xenial- host-uefi-guest Thanks! ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: yakkety ** Attachment added: "Screenshot from 2016-09-14 11-48-54.png" https://bugs.launchpad.net/bugs/1624096/+attachment/4741575/+files/Screenshot%20from%202016-09-14%2011-48-54.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1624096 Title: yakkety: desktop and server ISOs wont boot under QEMU in UEFI mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1624096/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604173] Re: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect
Brain, Strange. So I just tried the upgrade again, and after the upgrade completed, I: 1) Clicked "Reboot Now" (which did nothing, same as yesterday) 2) Ran `sudo reboot` - it worked, but seemed to hang for some time before doing anything (it hung for maybe 20 seconds or so) I'm not sure how clicking "Reboot Now" first might be interacting with then running `sudo reboot`. I wonder if I tried `sudo reboot` first if it would do nothing. I'll try that tomorrow if I have time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604173 Title: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1604173] [NEW] Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect
Public bug reported: After doing a 14.04 to 16.04 upgrade, clicking "Reboot Now" has no effect. update-manager simply closes. However, I could then reboot fine using the indicator or the power button, which kinda suggests the problem is in update-manager rather than in the general state of such an upgraded but not yet rebooted system. In the 3 test upgrades I did, this was reproducible 100% of the time. Steps I used to reproduce: 1) Fresh install of 14.04.4 2) Run updates and reboot 3) Launch update-manager with `update-manager -d` 4) Start upgrade, let it complete 5) Once upgrade is completed, click "Reboot Now" on the shown dialogue FYI, thus far I've only tested on a UEFI system, haven't had time to test a BIOS system (and I wont likely have time to test on a BIOS system). But I wouldn't expect this to behave differently on a BIOS system. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubuntu-release-upgrader-core 1:16.04.14 ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13 Uname: Linux 4.4.0-31-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Mon Jul 18 15:42:56 2016 InstallationDate: Installed on 2016-07-18 (0 days ago) InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 (20160217.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to xenial on 2016-07-18 (0 days ago) VarLogDistupgradeTermlog: ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1604173 Title: Clicking "Reboot Now" after 14.04-->16.04 upgrade has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1604173/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1599900] Re: compiz crashed with SIGSEGV in ccsObjectGetInterface_()
FYI, I seem to be hitting this same bug (under qemu) with the xenial daily ISO as well (which have xenial-proposed enabled by default). Will this be fixed in Xenial also? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1599900 Title: compiz crashed with SIGSEGV in ccsObjectGetInterface_() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1599900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
@Marco: thanks for the FYI! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Here's another screenshot that shows the SegvAnalysis. In my testing thus far, this failure (assuming it's related to this unity/nux change) only seems to happen when trying to install under qemu. I tried -vga qxl, -vga std, and -vga virtio... none of them yield a working installation. Compiz always fails to start. ** Attachment added: "Screenshot from 2016-07-13 10-56-41.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1598770/+attachment/4700300/+files/Screenshot%20from%202016-07-13%2010-56-41.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598770] Re: Unity in low-graphics mode has animations and unneeded redraws
Possibly as a result of this change, unity/compiz is failing to start when trying to install from the latest 16.04.1 daily ISO under qemu (xenial-desktop-amd64.iso 20160713, sha1sum c9b1ad9b1044c4e68684395daa3f85e016491c3a). I attached a screenshot as I couldn't file a bug from within the qemu VM (apport doesn't seem able to launch firefox). ** Attachment added: "Screenshot from 2016-07-13 10-36-40.png" https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1598770/+attachment/4700286/+files/Screenshot%20from%202016-07-13%2010-36-40.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598770 Title: Unity in low-graphics mode has animations and unneeded redraws To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1598770/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597876] Re: installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]
Also attaching a screenshot, just so folks don't think I'm making this up :P ** Attachment added: "screenshot.png" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+attachment/4692953/+files/screenshot.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597876 Title: installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597876] [NEW] installing/upgrading packages containing systemd services results in prompt for cryptoswap passphrase [xenial]
Public bug reported:
This is an extremely odd bug that requires a very specific scenario to
reproduce:
1) You need to be using an ecryptfs-style cryptoswap partition (as would
be setup when you choose "Encrypt my home directory" during the
installation)
2) The underlying physical swap partition used for the cryptoswap needs
to be on a GPT partitioned drive
3) The GUID specific bit 63 ("no auto mounting") must *not* be set on
the underlying physical swap partition
In this scenario, installing/upgrading/reinstalling seemingly *any*
package with a systemd service will result in the user getting *twice*
prompted for a passphrase to unlock their cryptoswap partition. If
upgrades are performed using the graphical Software Updater, the user
wont be aware of this issue unless they've expanded the details,
resulting in the Software Updater hanging indefinitely.
For example, if you have the needed setup, you can easily reproduce this
bug with:
sudo apt-get install --reinstall whoopsie
After which you'll encounter something like this:
(Reading database ... 177827 files and directories currently installed.)
Preparing to unpack .../whoopsie_0.2.52.1_amd64.deb ...
Please enter passphrase for disk primary (cryptswap1) on none!
Unpacking whoopsie (0.2.52.1) over (0.2.52) ...
Preparing to unpack .../libwhoopsie0_0.2.52.1_amd64.deb ...
Unpacking libwhoopsie0:amd64 (0.2.52.1) over (0.2.52) ...
Processing triggers for systemd (229-4ubuntu6) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for libc-bin (2.23-0ubuntu3) ...
Setting up libwhoopsie0:amd64 (0.2.52.1) ...
Setting up whoopsie (0.2.52.1) ...
Please enter passphrase for disk primary (cryptswap1) on none!
Processing triggers for libc-bin (2.23-0ubuntu3) ...
(You can just hit enter each time the "Please enter passphrase for..."
prompt comes up.)
For some background: in modern systemd times, ecryptfs-style cryptoswaps
are broken when the underlying physical GPT swap partition does not have
bit 63 set:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1447282
During the boot the user is erroneously prompted for a passpharase to
unlock the cryptoswap (you can hit enter for an empty passphrase, or
enter any passphrase you want... either way, nothing seems to actually
be done with it). After the boot completes, the underlying physical swap
partition will be mounted normally (ie, you wont actually be using
encrypted swap... so a false sense of security, which is of course
concerning).
Although lp:1447282 has been fixed for the most common hardware
configurations, it's still possible for users to encounter this problem
in the real-word: ecryptfs-setup-swap currently fails to set bit 63 when
the physical GPT swap partition is on an NVMe or MMC drive:
https://bugs.launchpad.net/ecryptfs/+bug/1597154
So one way to reproduce this is to install Ubuntu 16.04 onto an NVMe
drive and choose "Encrypt my home directory" during the installation.
To make debugging this easier without requiring an NVMe drive (and
especially so it's easier to debug in a UEFI VM), I'm attaching a script
that will unset bit 63 on the underlying GPT swap partitions used by any
ecryptfs-style cryptoswaps that are present.
If you run my script:
sudo python3 unset-bit-63.py
And then reboot, you should now be able to reproduce this bug.
Even though fixing lp:1597154 will mean users shouldn't encounter
(during normal real-world usage) this strange behavior when
installing/upgrading/reinstalling packages that contain systemd
services, I have a strong hunch that the fact this can happen at all
indicates something is quite wonky in either systemd itself or in the
Debian/Ubuntu specific systemd trigger handling.
Thanks!
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "unset-bit-63.py"
https://bugs.launchpad.net/bugs/1597876/+attachment/4692952/+files/unset-bit-63.py
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1597876
Title:
installing/upgrading packages containing systemd services results in
prompt for cryptoswap passphrase [xenial]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597876/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
@diwic - I agree, there have been problems in multiple places causing this. Yesterday I sorted out one of them. If you have swap on a GPT partitioned NVMe or MMC drive, ecryptfs-setup-swap isn't correctly marking the partition as non-auto-mounting, which leads the the user erroneously being prompted to enter a passphrase to unlock the swap partition. I filed a bug about this and have a merge proposal ready for review: https://bugs.launchpad.net/ecryptfs/+bug/1597154 This bug has been present in ecryptfs-utils since the original GPT auto mounting issues was fixed, but not that long ago in 16.04 it didn't result in being erroneously being prompted to enter a passphrase to unlock the swap partition. Some some recent-ish behavior change elsewhere has re-exposed this (I'm guessing a change in systemd). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1447282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588077] Re: Ubiquity crash with Yakkety 20160601 daily amd64 ISO
Same result when I use "Try Ubuntu without installing" and "Install Ubuntu". Happens with both UEFI and BIOS installs. A quick glance at `JournalErrors.txt` confirms that the crash is happening during "Configure time zone...": Jun 01 15:59:03 hostname /plugininstall.py[6642]: Exception during installation: Jun 01 15:59:03 hostname /plugininstall.py[6642]: Traceback (most recent call last): Jun 01 15:59:03 hostname /plugininstall.py[6642]: File "/usr/share/ubiquity/plugininstall.py", line 1778, in Jun 01 15:59:03 hostname /plugininstall.py[6642]: install.run() Jun 01 15:59:03 hostname /plugininstall.py[6642]: File "/usr/share/ubiquity/plugininstall.py", line 78, in wrapper Jun 01 15:59:03 hostname /plugininstall.py[6642]: func(self) Jun 01 15:59:03 hostname /plugininstall.py[6642]: File "/usr/share/ubiquity/plugininstall.py", line 204, in run Jun 01 15:59:03 hostname /plugininstall.py[6642]: self.configure_plugins() Jun 01 15:59:03 hostname /plugininstall.py[6642]: File "/usr/share/ubiquity/plugininstall.py", line 570, in configure_plugins Jun 01 15:59:03 hostname /plugininstall.py[6642]: self.run_plugin(plugin) Jun 01 15:59:03 hostname /plugininstall.py[6642]: File "/usr/share/ubiquity/plugininstall.py", line 547, in run_plugin Jun 01 15:59:03 hostname /plugininstall.py[6642]: "Plugin %s failed with code %s" % (plugin.NAME, ret)) Jun 01 15:59:03 hostname /plugininstall.py[6642]: ubiquity.install_misc.InstallStepError: Plugin timezone failed with code 2 But not that the Ubiquity timezone selection screen is working fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588077 Title: Ubiquity crash with Yakkety 20160601 daily amd64 ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1588077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588077] Re: Ubiquity crash with Yakkety 20160601 daily amd64 ISO
For me the installer is crashing when the status beneath the progress bar says, "Configuring time zone...". (See attached screenshot.) Note this was a UEFI install in OEM mode. I know this crash is likewise occurring with BIOS installs in OEM mode. Will try a normal install next. ** Attachment added: "Screenshot from 2016-06-01 16-32-00.png" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1588077/+attachment/4674807/+files/Screenshot%20from%202016-06-01%2016-32-00.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588077 Title: Ubiquity crash with Yakkety 20160601 daily amd64 ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1588077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1447282] Re: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs)
Any chance this can get fixed in Xenial in time for 16.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/1447282 Title: Does not use encrypted swap when using GPT partitioning + encrypted home directory (ecryptfs) To manage notifications about this bug go to: https://bugs.launchpad.net/ecryptfs/+bug/1447282/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
On a whim, I just checked in on this with the 20160601 Xenial daily amd64 ISO (sha1sum e07c8b4df1fc71a487fafb309bd318041a65774f), and everything works great: http://cdimages.ubuntu.com/xenial/daily-live/pending/ So seems things are on track for this not being a problem in the 16.04.1 release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1588077] [NEW] Ubiquity crash with Yakkety 20160601 daily amd64 ISO
Public bug reported: No other details at this time, will add more as I have more info. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: ubiquity 16.10.1 ProcVersionSignature: Ubuntu 4.4.0-23.41-generic 4.4.10 Uname: Linux 4.4.0-23-generic x86_64 ApportVersion: 2.20.1-0ubuntu4 Architecture: amd64 CasperVersion: 1.376 Date: Wed Jun 1 15:59:13 2016 InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity initrd=/casper/initrd.lz quiet splash --- oem-config/enable=true LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160601) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ubiquity-16.10.1 ubuntu yakkety -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1588077 Title: Ubiquity crash with Yakkety 20160601 daily amd64 ISO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1588077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583879] Re: apt-get update hangs indefinitely, appstreamcli using 100% CPU
Also, the graphical Ubuntu Software Updater is likewise hanging indefinitely. And I've confirmed this on 3 different systems so far. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583879 Title: apt-get update hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1583879] [NEW] apt-get update hangs indefinitely, appstreamcli using 100% CPU
Public bug reported: Just ran `sudo apt-get update`, which is hanging indefinitely after the downloads complete, the last CLI output from which is: Fetched 733 kB in 1s (399 kB/s) Looking at `top` suggests `appstreamcli` is the culprit as it's pegged at near 100% CPU usage: 100 0.1 18:29.02 appstreamcli If I kill the hung `sudo apt-get update` process with Control+C, the `appstreamcli` process goes away. Retrying `sudo apt-get update` has the same result. On a whim I also tried `sudo apt update`, but it seems to have the same problem. It hangs indefinitely and running it results in an `appstreamcli` process consuming 100% CPU. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: appstream 0.9.4-1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 19 20:53:40 2016 SourcePackage: appstream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: appstream (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1583879 Title: apt-get update hangs indefinitely, appstreamcli using 100% CPU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1583879/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580232] Re: "Download updates while installing" does not download updates
** Description changed: Ubiquity (as shipped on the 16.04 amd64 desktop ISO) does not download updates while installing when you've checked "Download updates while installing". Same result with both BIOS and UEFI installs (although UEFI installs - aways download the latest kernel, whether or not you've checked - "Download updates while installing"). + away download the latest kernel, whether or not you've checked "Download + updates while installing"). Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 10 09:39:08 2016 InstallationDate: Installed on 2016-05-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580232 Title: "Download updates while installing" does not download updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Okay, seems that "Download updates while installing" has no effect with the Ubiquity version on the 16.04 ISOs. I filed a bug against Ubiquity for this, would appreciate if someone could confirm my findings: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1580232] [NEW] "Download updates while installing" does not download updates
Public bug reported: Ubiquity (as shipped on the 16.04 amd64 desktop ISO) does not download updates while installing when you've checked "Download updates while installing". Same result with both BIOS and UEFI installs (although UEFI installs aways download the latest kernel, whether or not you've checked "Download updates while installing"). Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 10 09:39:08 2016 InstallationDate: Installed on 2016-05-10 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1580232 Title: "Download updates while installing" does not download updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1580232/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576726] Re: [SRU]network-manager
@seb128... I'll try to get some better debug info soon. Interestingly, it only seem to happen with Intel 7260 WiFi cards (and not, for example, with Intel 8260 WiFi cards). So I'm not sure whether what we're seeing is actually a problem with network-manager. I'm now kinda thinking it's more likely a kernel issue, especially as other's haven't seen this problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576726 Title: [SRU]network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1576726] Re: [SRU]network-manager
With this proposed package, System76 is seeing network-manager crash upon the first resume from suspend. Anyone else experiencing this? I'll be looking into this more today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1576726 Title: [SRU]network-manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1576726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572793] Re: Ubiquity no longer prompts to join available WiFi networks
Confirmed this fix in the proposed packaged, everything seems shiny. I confirmed that after an OEM install, enabling proposed, updating, and finally clicking "Prepare for shipping to user", Ubiquity behaves as expected during the first-run user config: 1) When not connected to Ethernet and you have WiFi hardware available, Ubiquity again prompts you to join a WiFi network, and if you do, ubi- timezone will correctly guess your timezone 2) When connected to Ethernet, Ubiquity will not prompt you to join a WiFi network, and ubi-timezone will use the Ethernet connection to guess your timezone 3) When not connected to Ethernet and you decline to join a WiFi network, Ubiquity still works as expected (but ubi-timezone understandably can't guess your timezone) Only thing I can't test is a fresh install as that can't really be done properly without a remastered ISO. But as this fix really matters for OEM installs and eventually for the 16.04.1 ISOs, I feel it's safe to mark this as "verification-done". ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572793 Title: Ubiquity no longer prompts to join available WiFi networks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" + ** Note: "Download updates while installing Ubuntu" doesn't currently + seem to be working. If after installing 16.04 on effected Skylake + hardware you find that Unity/Compiz is broken, switch to a VT with + Control+Alt+F1, login, and then run: + + sudo apt-get update + sudo apt-get dist-upgrade + + You should see the `libllvm3.8` package get updated. After a reboot, + Unity/Compiz should be working. + == In detail == The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Hmm, I just tried this on Skylake hardware, and "Download updates while installing" isn't doing the trick. Could be that "Download updates while installing" is broken on the 16.04 ISOs, or this could be a result of the phased updates done by the Ubuntu Software Updater and related components that use the same code paths. So after installing Ubuntu 16.04, Unity/Compiz was broken. I had to switch to a VT with Control+Alt+F1, login, and then run: sudo apt-get update sudo apt-get dist-upgrade Which gave me the updated libllvm3.8 package. Then after a reboot, everything is shiny and working. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" == In detail == - The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which + The Ubuntu 16.04 desktop ISOs include libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Abhinav, Sounds like you're encountering a different bug, or perhaps your ISO file is corrupted. Have you verified the checksum of your download? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: [Description updated to reflect state of 16.04 release ISO] == In summary == If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or possibly other GPUs that likewise require use of the llvmpipe opengl software fallback), a work-around is needed to install Ubuntu 16.04 desktop. To work-around this, you'll need to: 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu without installing") 2) Check "Download updates while installing Ubuntu" - ** Note the above work-around wont work till - llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. - == In detail == The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which has a bug that results in invalid JIT code generation when using the mesa llvmpipe opengl software fallback on Skylake CPUs. When you encounter this bug, Unity/Compiz will fail to start, and you'll see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 libllvm3.8 1:3.8-2ubuntu3 fixes this issue, but the fix did not make it - onto the 16.04 release ISO. It will be included on the 16.04.1 ISO. + onto the 16.04 release ISOs. It will be included on the 16.04.1 ISOs. ** Changed in: system76 Status: Fix Committed => 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/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: - Currently it's impossible to install from xenial-desktop-amd64.iso on a - wide range of hardware with Nvidia GPUs. + [Description updated to reflect state of 16.04 release ISO] - The problem is invalid opcode(s) when using llvmpipe (the software - opengl fallback, used when using Unity with the Nouveau driver). The - result is that compiz crashes over and over; Upstart will continue to - restart compiz till it gives up. To confirm whether this bug is - happening, switch to a VT and check dmesg, in which you'll see something - like: + == In summary == + + If you have an Intel Skylake (6th gen) CPU and an NVIDIA GPU (or + possibly other GPUs that likewise require use of the llvmpipe opengl + software fallback), a work-around is needed to install Ubuntu 16.04 + desktop. + + To work-around this, you'll need to: + + 1) Choose "Install Ubuntu" in the pre-boot menu (rather than "Try Ubuntu + without installing") + + 2) Check "Download updates while installing Ubuntu" + + ** Note the above work-around wont work till + llvm-toolchain-3.8 1:3.8-2ubuntu3 lands in xenial-updates (it's currently only in xenial-proposed). FIXME: update description once this happens. + + == In detail == + + The Ubuntu 16.04 desktop ISOs includes libllvm3.8 1:3.8-2ubuntu1, which + has a bug that results in invalid JIT code generation when using the + mesa llvmpipe opengl software fallback on Skylake CPUs. + + When you encounter this bug, Unity/Compiz will fail to start, and you'll + see something like this in dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 - A workable solution seems to be to re-build mesa against llvm-3.6-dev, - libclang-3.6-dev (rather that 3.8). This would get us a working Xenial - ISO for the effected hardware. Post 16.04 release, this could be - revisited, and mesa in Xenial could possibly switch back to llvm 3.8 - once this issue is resolved. - - I have mesa test packages built against llvm 3.6 here: - - https://launchpad.net/~jderose/+archive/ubuntu/mesa/+packages - - I couldn't test the installation without a re-spun ISO, but I did - confirm that after updating to the mesa packages in my PPA, I could - again use Unity. So I'm pretty sure this will fix installing from the - ISO as well. - - My hunch is that llvm 3.8 is generating invalid code during its JIT - compilation for llvmpipe, but it could also be the result of memory - corruption. Either way, building mesa against llvm 3.6 seems to be quick - the fix. - - Note this is a regression from 14.04.4 and 15.10, both of which install - fine on the hardware effected by this bug. - - For concrete examples of System76 hardware effected by this: - - 1) All Skylake laptops with 970m, 980m, and 980gtx GPUs - - 2) All Skylake and Haswell-E desktops with 970gtx and 980gtx GPUs - (although strangely, things seem to work with when you connect to a - monitor over HDMI, but always fails when connecting to a monitor over - DisplayPort) - - Note that none of the above failed tested scenarios are using Optimus: - all are using discrete GPU configurations. - - In my testing thus far on the effected hardware, the install always - fails if you choose "Try Ubuntu without installing". The install usually - seems to work when you choose "Install Ubuntu", but even this 2nd - scenario sometimes fails (and when it does, you'll see the same "trap - invalid opcode" bits in dmesg). - - Also note that so far I've only tested amd64, haven't tested i386. - - I suspect there is some deeper weirdness here, but at this point - System76 is just trying to make sure we have a Xenial ISO from which - customers can re-install Ubuntu. - - Old description - === - Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. - - For example, from dmesg: - - [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 - [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 - [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 - - This definitely effects hardware we've tested with NVIDIA 970m and 980m - GPUs (when using the nouveau driver), and probably effects others as - well. - - Although strangely, with some NVIDIA 900 series hardware we're not - seeing this bug when using the nouveau driver. This will be investigated - further. - - In the current state, it's not possible to install Xenial on effected - hardware using recent daily desktop amd64 ISOs. - - Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in - Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from - ppa:canonical-x/x-staging. (The later test was done with the System76 - imaging system using an image with ppa:canonical-x/x-staging and - nvidia-361 pre-installed, then removing nvidia-361 and rebooting).
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Just confirmed on Skylake hardware that llvm-toolchain-3.8 from proposed fixes this issue on Skylake hardware using llvmpipe. Thanks! ** Changed in: system76 Status: Triaged => Fix Committed ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
After further investigating, it seems this bug doesn't effect Haswell-E after all, sorry about the confusion. Will continue to report back as we learn more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
I can confirm that tjaalton's above test packages fix the problem on a Skylake laptop with an i7-6700 CPU and an Nvidia 970m GPU when using the nouveau driver. I installed libllvm3.8_3.8-2ubuntu1.1_amd64.deb from a VT then rebooted, and now I have working Unity again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1572615] [NEW] xenial 20160419: oem-config-gtk not installed after OEM install
*** This bug is a duplicate of bug 1572436 *** https://bugs.launchpad.net/bugs/1572436 Public bug reported: The `oem-config-gtk` package is not installed after doing an OEM install from the Xenial 20160419 daily desktop ISO (sha1sum 8965fb3673631e1161b4656f2c95b593ac302eb2). This is true on both BIOS and UEFI systems. Post-install, you can work around this on a BIOS system with: sudo apt-get install ubiquity-frontend-gtk oem-config-gtk Or on a UEFI system with: sudo apt-get install grub-efi ubiquity-frontend-gtk oem-config-gtk So this isn't a deal breaker, but it's also a bug I've never seen in any final release ISO over the past 3 years (although it has happened from time to time in daily ISOs during the dev cycle). Thanks! ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** This bug has been marked a duplicate of bug 1572436 "Prepare for OEM install" icon and oem-config-prepare missing on desktop -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1572615 Title: xenial 20160419: oem-config-gtk not installed after OEM install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1572615/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
Oh, and another bit of information: our laptops all use embedded Display Port for their connection to the internal screen, and in this case, this bug always manifests. So at least in our testing so far, both eDP and DP seem to be effected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
So there seems to be a curious pattern with this bug (which might provide an important hint): on desktop systems with 970 GTX or 980 GTX cards, this bug always seems to happen when connected to a monitor over DisplayPort, but does *not* seem to happen when connected to a monitor over HDMI. We'll investigate this more carefully as soon as there's a new Xenial daily build available (with the 4.4.0-18-generic kernel). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
** Changed in: xorg-server (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/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Correction: this is fixed as of 1.18.3-1ubuntu2. 1.18.3-1ubuntu1 still had this problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
I'm no longer having this problem as of 1.18.3-1ubuntu1. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563505] Re: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO )
David, thanks for providing more information! In terms of looking for issues related to the NVMe driver, this is probably the best approach: dmesg | grep -i nvme And then see if there is anything suspicious in the resulting output. In term of the CPU performance being dramatically different between AC and battery, in my experience with the intel_pstate CPU frequency scaling driver, the performance should be the same. But we'll double- check our findings on this as there could have always been regressions or changes in Stable Release Updates (SRUs) in Ubuntu since we last thoroughly tested this aspect. Would you say Firefox is the primary application you're using when you encounter this issue? Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563505 Title: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO ) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1563505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This definitely effects hardware we've tested with NVIDIA 970m and 980m GPUs (when using the nouveau driver), and probably effects others as well. - Although strangely, with some NVIDIA hardware we're not seeing this bug - when using the nouveau driver. This will be investigated further. + Although strangely, with some NVIDIA 900 series hardware we're not + seeing this bug when using the nouveau driver. This will be investigated + further. In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support: /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] Re: xenial: invalid opcode when using llvmpipe
** Description changed: Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 - This certainly effects hardware with NVIDIA 970m and 980m GPUs, and - possibly others. + This definitely effects hardware we've tested with NVIDIA 970m and 980m + GPUs (when using the nouveau driver), and probably effects others as + well. - In the current state, it's not possible to install Xenial on such + Although strangely, with some NVIDIA hardware we're not seeing this bug + when using the nouveau driver. This will be investigated further. + + In the current state, it's not possible to install Xenial on effected hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support: /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). ** Also affects: system76 Importance: Undecided Status: New ** Changed in: system76 Status: New => Triaged ** Changed in: system76 Assignee: (unassigned) => Jason Gerard DeRose (jderose) ** Changed in: system76 Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1564156] [NEW] xenial: invalid opcode when using llvmpipe
Public bug reported: Currently Unity on Xenial is unusable when the llvmpipe software fallback is used, at least on certain hardware. For example, from dmesg: [ 2092.557913] traps: compiz[10155] trap invalid opcode ip:7efc940030d4 sp:7ffccd914ea0 error:0 [ 2093.109485] traps: compiz[10192] trap invalid opcode ip:7f38ac01a0d4 sp:7ffe5ed737e0 error:0 [ 2093.718863] traps: compiz[10212] trap invalid opcode ip:7fe6900010d4 sp:7ffd55804020 error:0 This certainly effects hardware with NVIDIA 970m and 980m GPUs, and possibly others. In the current state, it's not possible to install Xenial on such hardware using recent daily desktop amd64 ISOs. Note this problem exists both when run against mesa 11.1.2-1ubuntu2 in Xenial proper, and when run against mesa 11.2.0~rc4-1ubuntu0.1 from ppa:canonical-x/x-staging. (The later test was done with the System76 imaging system using an image with ppa:canonical-x/x-staging and nvidia-361 pre-installed, then removing nvidia-361 and rebooting). I'm kinda shooting in the dark here, but I did my best to rule out the kernel as a variable: (1) I built and installed the 4.4.0-16 kernel on 15.10, rebooted, and had no problems. (2) On Xenial I tried the 4.5 and 4.6rc1 mainline builds, but they don't fix the problem. I'm not sure the underling bug is in compiz, but I'm filing it against compiz anyway because that's where the dmesg output is pointing me. Other likely culprits include nux, mesa, maybe even llvm, and probably others I'm not thinking of :) Also, I'm positive llvmpipe is being used when this invalid opcode is trapped because I added this to /etc/X11/Xsession.d/50_check_unity_support: /usr/lib/nux/unity_support_test -p > /tmp/compiz-debug.log That way I could figure out what renderer was being used from a VT (as the X session is darn near unusable in this state). ** Affects: compiz (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/1564156 Title: xenial: invalid opcode when using llvmpipe To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1564156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508865] Re: oem-config: networking not enabled during user config
Mathieu, Everything seems solid with this fix. I confirmed that: 1. When plugged into Ethernet, the NM applet is show, networking is enabled, and ubi-timezone correctly guesses your timezone 2. When *not* plugged into Ethernet but you have WiFi hardware, the NM applet is shown, oem-config prompts you to join a WiFi network, and, if you do, ubi-timezone correctly guesses your timezone 3. When not plugged into Ethernet and you have WiFi hardware but choose *not* to connect to any WiFi network, everything still works as expected (understandably, ubi-timezone can't guess your timezone in this case) Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508865 Title: oem-config: networking not enabled during user config To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1508865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563505] Re: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO )
One other thing... in the future if you encounter any issues, please use the System76 support system. Log into your System76 account, then go to support and created a ticket. You'll tend to get a much quicker response there. Our engineers do their best to keep tabs on System76 related bugs on Launchpad, but it all depends on how busy we are with other things. In contrast, our support team will always be able to give you the time and attention you deserve :D -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563505 Title: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO ) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1563505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563505] Re: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO )
Thanks for the bug report, sorry to hear you're having issues! Sounds like you're having multiple (and perhaps unrelated issues), so let's first focus on the keyboard and mouse not working. If you could please provide a bit more information to help us narrow this down: (1) You used the word "unresponsive"... is the problem that the keyboard and mouse/trackpad don't work at all, or just that they are very slow to respond? In other words, in the condition you're describing, does it seem like your lemu6 is freezing or just that it gets extremely sluggish? (2) You said that this condition usually takes several days to manifest... can you provide more details on what you're doing during this time? For example, do you suspend/resume during this time? Are there any particular applications that you tend to have open throughout these two days? (3) You tagged this with "nvme"... do you have reason to believe this is related to nvme? For example, have you noticed anything in dmesg or other logs that suggest the nvme driver might be to blame? (4) Any noteworthy changes you've made to your system that might introduce variables we don't have in our internal testing? For example, have you installed any servers or other background services that run continuously? Have you installed any software from PPAs or other 3rd party sources? At first glance, this sounds more like a software problem (likely a memory leak somewhere) rather than a hardware problem. More information will help us narrow down the cause. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563505 Title: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO ) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1563505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1563505] Re: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO )
** Changed in: system76 Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1563505 Title: unresponsive lemu6 . . . NVMe SSD ( samsung SSD 950 PRO ) To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1563505/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508865] Re: oem-config: networking not enabled during user config
Mathieu, thanks a million for fixing this! I'll test it ASAP! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508865 Title: oem-config: networking not enabled during user config To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1508865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561685] Re: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Okay, I just tried this on an Intel GPU system, and it has the same problem. Arrow keys are broken with 1.18.2-2ubuntu0.1, but work fine with 1.18.1-1ubuntu4. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title: x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1561685/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1561685] [NEW] x-staging: 1.18.2-2ubuntu0.1 host breaks arrow keys on qemu guest
Public bug reported: This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow keys on qemu guests. Actually, I'm not sure it breaks the arrow keys on the guest in all scenarios, but it at least breaks them in the pre-boot menu when trying to install a qemu VM from an ISO. For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop- amd64.iso (in BIOS-mode): 1) I hit shift to get to the menu, hit enter to choose English (both of which work) 2) Nothing happens when I hit the down arrow key to try and select "Install Ubuntu" 3) I hit F4 (which works) to open the Mode selector, but then nothing happens when I hit the down arrow to try and select "OEM install (for manufactures)" After I downgraded xserver-common, xserver-xorg-core to the 1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again (which is how I narrowed this bug down to xorg-server). I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the x-staging PPA (which I had been using for several weeks), so it seems that 1.18.2-2ubuntu0.1 introduced this regression. Note that this issues seems to break all the arrow keys, not just the down arrow key. If I hit shift to get to the menu, none of the arrow keys do anything if I try to select a different language. Or if hit enter to choose English and then hit F3 to open the Keymap selector, none of the arrow keys work for selecting a different Keymap. As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4, 15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode. In all six scenarios, the arrow keys don't work. Same problem with the server amd64 ISOs (although I only tried BIOS-mode in this case). Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and the result is the same: the arrow keys don't work. One final note is that the arrow keys work fine when used with any other application on the host. qemu is the only place I've found any issues. Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using the nvidia-361 proprietary driver. Later today I'll test this with Nouveau, and will also try this on an Intel GPU system. But as this seems related to keyboard input rather than the GPU driver, my hunch is the result will be the same. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Description changed: This is an odd one. 1.18.2-2ubuntu0.1 (on the host) breaks the arrow keys on qemu guests. Actually, I'm not sure it breaks the arrow keys on the guest in all scenarios, but it at least breaks them in the pre-boot menu when trying to install a qemu VM from an ISO. For example, if I try to install a qemu VM from ubuntu-14.04.4-desktop- amd64.iso (in BIOS-mode): 1) I hit shift to get to the menu, hit enter to choose English (both of which work) 2) Nothing happens when I hit the down arrow key to try and select "Install Ubuntu" 3) I hit F4 (which works) to open the Mode selector, but then nothing happens when I hit the down arrow to try and select "OEM install (for manufactures)" After I downgraded xserver-common, xserver-xorg-core to the 1.18.1-1ubuntu4 packages in Xenial proper, everything works fine again (which is how I narrowed this bug down to xorg-server). I also didn't have this problem when using 1.18.2-1ubuntu0.3 from the x-staging PPA (which I had been using for several weeks), so it seems that 1.18.2-2ubuntu0.1 introduced this regression. Note that this issues seems to break all the arrow keys, not just the down arrow key. If I hit shift to get to the menu, none of the arrow keys do anything if I try to select a different language. Or if hit enter to choose English and then hit F3 to open the Keymap selector, none of the arrow keys work for selecting a different Keymap. As far as the guest goes, I've tried the desktop amd64 ISO for 14.04.4, 15.10, and the latest Xenial daily, all in both BIOS-mode and UEFI-mode. In all six scenarios, the arrow keys don't work. Same problem with the server amd64 ISOs (although I only tried BIOS-mode in this case). Normally I use '-vga qxl', but I also tried '-vga std' on a whim, and the result is the same: the arrow keys don't work. - One final note is that the arrow keys work find when used with any other + One final note is that the arrow keys work fine when used with any other application on the host. qemu is the only place I've found any issues. Oh, and in case it's relevant, I have an NVIDIA 970m GPU and am using the nvidia-361 proprietary driver. Later today I'll test this with Nouveau, and will also try this on an Intel GPU system. But as this seems related to keyboard input rather than the GPU driver, my hunch is the result will be the same. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1561685 Title:
[Bug 1554099] Re: Changing what action for security updates unusable
Yup, I can also confirm that it seems fixed in the 20160323 daily ISO. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554099] Re: Changing what action for security updates unusable
Yup, I can also confirm that it seems fixed in the 20160323 daily ISO (tested yesterday). Will test today's shortly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554099] Re: Changing what action for security updates unusable
I'm still seeing this bug on a fresh install from today's daily ISO (20160321, sha1sum 4773a2328eb4470761e1c37174d5d3cad5b6219d). But I'm no longer seeing it on my upgraded existing install from a few months back. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554099] Re: Changing what action for security updates unusable
Same is happening with latest Ubuntu (Unity) Xenial daily ISO (sha1sum 8e06dd499bfe357ebbad44c827d8428d70baacf4). I attached a screenshot of the same problem under Unity. This bug has been around for a few weeks or so, although I'm not exactly sure when it was introduced. ** Attachment added: "Screenshot from 2016-03-07 14-34-51.png" https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+attachment/4591889/+files/Screenshot%20from%202016-03-07%2014-34-51.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554099 Title: Changing what action for security updates unusable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1554099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1554194] [NEW] /home/oem and oem user are not removed by oem-config-firstboot
Public bug reported: Sometime recently during Xenial development, oem-config has become quite broken. It seems the underlying problem is that the "oem" user and the "/home/oem" folder aren't getting removed by oem-config-firstboot. Steps to reproduce: 1) Do an OEM-mode install from the latest Xenial daily ISO 2) Click "Prepare for shipping to end user" 3) No matter what option you choose during the user firstrun config (automatic login, require password to login, or require password to login plus encrypt home directory), the "oem" user and the "/home/oem" folder will still exists, and the user will get logged into the "oem" account after completing the firstrun config. Note that the oem-config* packages seem to be removed okay... just the "oem" user itself isn't getting removed. Thanks! ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: ubiquity (not installed) ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Mar 7 14:33:12 2016 InstallationDate: Installed on 2016-03-07 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1554194 Title: /home/oem and oem user are not removed by oem-config-firstboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1554194/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1085766] Re: /var/log/upstart/ureadahead.log contains garbage
This problem seems to exist currently on both 15.10 and Xenial -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1085766 Title: /var/log/upstart/ureadahead.log contains garbage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1085766/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1508865] Re: oem-config: networking not enabled during user config
Just to clarify what the behaviour is with 14.04.4, what the behaviour used to be up till 15.10. After an OEM install and clicking "Prepare for shipping to end user", on the next boot 14.04.4 will: 1. Automatically enabled wired networking when connected over Ethernet, or 2. When not connected over Ethernet and you have WiFi hardware, the 2nd screen/page will be a prompt to join a WiFi network When you get to the timezone page/screen, networking is enabled if you're on Ethernet or have WiFi hardware available and connected to a WiFi network. When networking is enabled, Ubiquity will use this to guess your timezone based on IP address. When networking is not available, the timezone will always be initially set to the default of US/Eastern. Currently on 14.04.4 the nm applet is always shown (well, is always shown when you have at least some networking hardware available... not sure what it does when there is no networking hardware). Although I swear that right before 15.10 was released, 14.04.3 would only show the nm applet when you had WiFi hardware available but weren't on Ethernet... but I could be mistaken about that. With up-to-date 15.10 or Xenial, this is the behaviour: 1. The nm applet is never shown 2. When on Ethernet, networking is not enabled; when not on Ethernet but you have WiFi hardware available, you are not prompted to join a WiFi network 3. After the language and keyboard selection screen, Ubiquity always goes directly to the timezone selection screen; as networking is not enabled, Ubiquity can't guess your timezone, so the timezone will always be set to the default of US/Eastern -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1508865 Title: oem-config: networking not enabled during user config To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1508865/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
