[Bug 157050] Re: octave2.9-forge don't works in Gutsy!
I have a temporary workaround for this bug.
Entering these two commands before running any scripts acts as a
workaround for me:
addpath (genpath('/usr/share/octave/site/api-v22/m/octave2.9-forge/'));
addpath (genpath('/usr/share/octave/2.9.12/'));
I tested imread, imagesc, and some other functions. The reason for the
second addpath is because the first addpath obscures some functions
provided by the second addpath. For example, drawnow exists in two
locations:
/usr/share/octave/site/api-v22/m/octave2.9-forge/plot/drawnow.m
(this drawnow is really an empty file and therefore bad)
/usr/share/octave/2.9.12/m/plot/drawnow.m
(this is the drawnow that we actually want)
I was unable to reproduce the imread('3x3.png') error mentioned above,
and I was able to successfully use imread to read an image and imagesc
to then display the image.
--
octave2.9-forge don't works in Gutsy!
https://bugs.launchpad.net/bugs/157050
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hey, is there some transparency into an actual fix here? https://cloud- images.ubuntu.com/focal/20201210/focal-server-cloudimg-amd64.img still has this issue. I still cannot use the cloudimg with libvirt / qemu without modification to workaround this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Thanks for the update @davidkrauser, and very happy that groovy is working out. Is the fix due for focal sometime in the coming weeks or months? Any extra info is appreciated. Also happy holidays and end of year, and thank you all for what you do! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hi! Has any information surfaced about the cloudimg kernel and virtio- scsi? After thinking about this for some time, I propose that the "initrdfail" design isn't ultimately helpful and should be reverted, because: (1) It substantially increases the complexity of grub.cfg, (2) it is not clear that any value is being added (but maybe I am just not aware of the scenarios where it is valuable), and (3) it has the effect of masking legitimate problems (like the ones being discussed in this ticket). More on that here: The actual design intention is to have a kernel that boots correctly on the first try. The cloud images, in fact, should be shipping to boot correctly on the first try. These fail/success/fail/success/etc. boot sequences experienced by myself and @decui are nonsensical and don't really contribute value. A fail/success/fail/success/etc. is not an acceptable workaround, because it breaks things, and it's also just hiding the actual problem: that the kernel hasn't shipped with the right drivers, or the wrong kernel was bundled with an image. These are two definite disadvantages of the "initrdfail" design as it is currently. I'm open to hearing feedback. Thanks, David -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Awesome, thanks for categorizing that for me @vorlon! I was trying hard to find the right home for the issue, but didn't even think of livecd- rootfs :) I still am not too sure about the ultimate value offered by the initramfs fallback. It seems like you would: (a) never want initramfs, or (b) always want initramfs. Whereas the initrdfail mechanism isn't either of those, and it introduces complexity and confusion and potentially masks the actual issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874147] Re: focal-server-cloudimg-amd64.img panics on first boot, cannot open root device
** Also affects: grub2 (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/1874147 Title: focal-server-cloudimg-amd64.img panics on first boot, cannot open root device To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1874147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
This bug may also be affecting focal-server-cloudimg builds at: https://cloud-images.ubuntu.com/focal/. See: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1874147 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hi, this issue needs attention because it renders the cloud images for Ubuntu 20.04 potentially unusable. Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
I don't know how to escalate attention to this issue. Is emailing the author of commit 6a814c759e10feafb40c3669be30aa51eb5ce39b, which seems to have introduced the issue, acceptable? I'm surprised it's not causing more issues. I guess people don't care about the cloud images much? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hey Dan, thanks for getting back. In my case, it's not even my system though: it's Canonical's system; It's a fresh download of a cloudimg from https://cloud-images.ubuntu.com/focal/ which has the issue, so it can't because I didn't build the image right, because I didn't build the image at all. So how would this be able to help? What is the rationale behind the new initrdfail design and 40-force-partuuid.cfg? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Thanks for the information @vorlon. I think that makes sense. What would be the solution for booting focal-server-cloudimg-amd64.img with libvirt (virt-install) (so, not on Azure, as the OP was; so, I think the issue is now fractured into two separate issues with same underlying 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/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874147] Re: virt-install of focal-server-cloudimg-amd64.img panics on first boot, breaking cloud-init
** Summary changed:
- focal-server-cloudimg-amd64.img panics on first boot, cannot open root device
+ virt-install of focal-server-cloudimg-amd64.img panics on first boot,
breaking cloud-init
** Description changed:
- Various Focal cloudimg builds fail on first time ever booting (e.g.
- https://cloud-images.ubuntu.com/focal/20200418/focal-server-cloudimg-
- amd64.img). Here is the failed output:
+ Various Focal cloudimg builds panic on first time ever booting with
+ "Cannot open root device" when booting with virt-install (libvirt).
+
+ E.g.
+ https://cloud-images.ubuntu.com/focal/20200418/focal-server-cloudimg-amd64.img
+
+ Here is the failed output:
[0.00] Linux version 5.4.0-24-generic (buildd@lgw01-amd64-017) (gcc
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC
2020 (Ubuntu 5.4.0-24.28-generic 5.4.30)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic
root=PARTUUID=8a7c6798-57bf-4624-80a0-b896a73939f3 ro console=tty1
console=ttyS0 panic=-1
...
[1.043162] VFS: Cannot open root device
"PARTUUID=8a7c6798-57bf-4624-80a0-b896a73939f3" or unknown-block(0,0): error -6
[1.045238] Please append a correct "root=" boot option; here are the
available partitions:
[1.046921] 0b00 1048575 sr0
- [1.046922] driver: sr
+ [1.046922] driver: sr
[1.048215] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[1.049795] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-24-generic
#28-Ubuntu
[1.051189] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
Ubuntu-1.8.2-1ubuntu1 04/01/2014
[1.052904] Call Trace:
[1.053459] dump_stack+0x6d/0x9a
[1.054158] panic+0x101/0x2e3
[1.054812] mount_block_root+0x23f/0x2e8
- [1.055645] mount_root+0x38/0x3a
+ [1.055645] mount_root+0x38/0x3a
[1.056319] prepare_namespace+0x13f/0x194
[1.057236] kernel_init_freeable+0x231/0x255
[1.058131] ? rest_init+0xb0/0xb0
[1.058834] kernel_init+0xe/0x100
[1.059535] ret_from_fork+0x35/0x40
[1.060327] Kernel Offset: 0x1f80 from 0x8100 (relocation
range: 0x8000-0xbfff)
When booted, the second time, it works!
The issue appears to be a bug in /boot/grub/grub.cfg, pertaining to
"initrdfail." On first ever boot, grub will try to boot *without* an
initrd, which (apparently) makes the kernel unable to mount root.
Relevant section of /boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-aca11948-bdc4-4726-9aca-ead9dcce6a5e' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_gpt
insmod ext2
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root
aca11948-bdc4-4726-9aca-ead9dcce6a5e
else
search --no-floppy --fs-uuid --set=root
aca11948-bdc4-4726-9aca-ead9dcce6a5e
fi
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.4.0-24-generic root=LABEL=cloudimg-rootfs ro
console=tty1 console=ttyS0
initrd /boot/initrd.img-5.4.0-24-generic
else
linux /boot/vmlinuz-5.4.0-24-generic root=LABEL=cloudimg-rootfs ro
console=tty1 console=ttyS0 panic=-1
fi
initrdfail
}
** Description changed:
Various Focal cloudimg builds panic on first time ever booting with
"Cannot open root device" when booting with virt-install (libvirt).
+ After panicing, it reboots, and the second boot succeeds (using initrd
+ on the second try). However, it needs to succeed on the first try
+ without a panic. This breaks the cloud-init NoCloud process which
+ expects the first time booting to succeed.
E.g.
https://cloud-images.ubuntu.com/focal/20200418/focal-server-cloudimg-amd64.img
Here is the failed output:
[0.00] Linux version 5.4.0-24-generic (buildd@lgw01-amd64-017) (gcc
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #28-Ubuntu SMP Thu Apr 9 22:16:42 UTC
2020 (Ubuntu 5.4.0-24.28-generic 5.4.30)
[0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic
root=PARTUUID=8a7c6798-57bf-4624-80a0-b896a73939f3 ro console=tty1
console=ttyS0 panic=-1
...
[1.043162] VFS: Cannot open root device
"PARTUUID=8a7c6798-57bf-4624-80a0-b896a73939f3" or unknown-block(0,0): error -6
[1.045238] Please append a correct "root=" boot option; here are the
available partitions:
[1.046921] 0b00 1048575 sr0
[1.046922] driver: sr
[1.048215] Kernel panic - not syncing: VFS: Unable to mount root fs on
unknown-block(0,0)
[1.049795] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.4.0-24-generic
#28-Ubuntu
[1.051189] Hardware n
[Bug 1870189] Re: initramfs does not get loaded
> These images should likewise be bootable under libvirt with, at most, a boot performance penalty because of the second boot. Well, yes, it does boot on the second boot. Not trying to be contrarian here, but isn't a moot point that booting on the first boot is the de facto way things should work? I.e., a panic/reboot shouldn't be considered the "normal" way to boot on libvirt, or anywhere, for that matter. Furthermore, the panic/reboot breaks the virt-install cloud-init workflow, which expects the first boot to succeed. I mean, that's a solid expectation, right? :) What is the cloudimg designed to boot with, if not libvirt? I think virtio-scsi is being used. Here's the virt-install line, if it helps, virt-install \ -n myvm \ --description '' \ --os-type Linux \ --os-variant ubuntu16.04 \ --disk path=/var/lib/libvirt/images/focal-server-cloudimg-amd64.img,bus=scsi,discard=unmap \ --controller type=scsi,model=virtio-scsi \ --cdrom /var/lib/libvirt/images/nocloud.iso \ --virt-type kvm \ --graphics none \ --ram 1024 \ --vcpus 1 \ --network bridge:guestbr,model=virtio,virtualport_type=openvswitch,target=myvm \ --boot hd Once I do (eventually) get the image to boot through arcane ways, then I can confirm it is loading virtio-scsi: $ lsmod | grep virt virtio_net 53248 0 virtio_scsi24576 2 Virtio-scsi seems like it needs to be compiled into the kernel for this to make sense. Am I missing something here? :) Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Also, this bug is not specific to just Azure. I am using libvirt and experiencing this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
I've traced the issue back to "00_header" and "10_linux" here: https://git.launchpad.net/ubuntu/+source/grub2/tree/debian/patches /ubuntu-add-initrd-less-boot-fallback.patch?h=ubuntu/focal diffstat debian/patches/ubuntu-add-initrd-less-boot-fallback.patch Makefile.am |3 ++ configure.ac | 10 +++ grub-initrd-fallback.service | 12 + util/grub.d/00_header.in | 27 util/grub.d/10_linux.in | 56 +-- This is still an issue. I have to manually patch the cloud images with guestmount after downloading them in order to make them to work. Please advise. Thank you! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874147] Re: focal-server-cloudimg-amd64.img panics on first boot, cannot open root device
Discussing here: https://bugs.launchpad.net/ubuntu/+source/linux- azure/+bug/1870189 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874147 Title: focal-server-cloudimg-amd64.img panics on first boot, cannot open root device To manage notifications about this bug go to: https://bugs.launchpad.net/vmbuilder/+bug/1874147/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
The git commit which introduced the issue seems to be this: commit 6a814c759e10feafb40c3669be30aa51eb5ce39b Author: Mathieu Trudel-Lapierre Date: Tue Jul 16 11:31:29 2019 -0400 Import patches-unapplied version 2.04-1ubuntu1 to ubuntu/eoan-proposed Imported using git-ubuntu import. (at https://git.launchpad.net/ubuntu/+source/grub2/) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
Hmmm, I am not using the ISO, but rather the pre-installed cloudimg, and I am not so sure it is actually fixed. I just tried out the latest one, and can confirm the issue still persists with it: https://cloud-images.ubuntu.com/focal/20200430.1/focal-server-cloudimg- amd64.img Here is the output from booting: [0.00] Linux version 5.4.0-28-generic (buildd@lgw01-amd64-036) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #32-Ubuntu SMP Wed Apr 22 17:40:10 UTC 2020 (Ubuntu 5.4.0-28.32-generic 5.4.30) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606 ro console=tty1 console=ttyS0 panic=-1 ... [0.999771] VFS: Cannot open root device "PARTUUID=be1f3b17-864d-49f8-8249-5fb0edc7e606" or unknown-block(0,0): error -6 [1.001738] Please append a correct "root=" boot option; here are the available partitions: [1.003295] 0b00 1048575 sr0 [1.003295] driver: sr [1.004578] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [1.006119] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-28-generic #32-Ubuntu [1.007522] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.009254] Call Trace: [1.009790] dump_stack+0x6d/0x9a [1.010488] panic+0x101/0x2e3 [1.011137] mount_block_root+0x23f/0x2e8 [1.011931] mount_root+0x38/0x3a [1.012624] prepare_namespace+0x13f/0x194 [1.013443] kernel_init_freeable+0x231/0x255 [1.014319] ? rest_init+0xb0/0xb0 [1.015018] kernel_init+0xe/0x100 [1.015721] ret_from_fork+0x35/0x40 [1.016842] Kernel Offset: 0x1ac0 from 0x8100 (relocation range: 0x8000-0xbfff) Upon reboot, initrdfail will now be set, and therefore it will actually load the initrd on the second reboot. But, because I am trying to configure the machine on the first boot using cloud-init NoCloud, it needs to actually work on the first boot. (Anyways, I think it's a moot point that first time booting should work.) In the above, the "panic=-1" followed by "Cannot open root device" indicates that there is still something amiss, at least with the cloudimg distribution. I can file a different ticket for cloudimg, if it would be more appropriate. Please advise. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1870189] Re: initramfs does not get loaded
I'm actually not sure the best place to file a ticket for the cloudimg distribution. Any recommendation appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1870189 Title: initramfs does not get loaded To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548985] Re: After linux kernel update system won't boot
I get the same or very similar behaviour running Kubuntu 15.10 running under VMWare Fusion on a Mac. After doing a sudo apt-get dist-upgrade the vm fails to boot, getting stuck on the boot logo. Hitting escape right after the machine starts shows me the boot log, and it gets wedged on the line "starting terminate plymouth boot screen", indicating to me that perhaps it is video related. I have reproduced this twice by taking a copy of another VM and performing the same update. Once wedged, no combination of keys has any effect, and I'm unable to boot to a console because I don't get a grub menu on boot (it's in quiet mode by default?). The HD is not encrypted, but one home directory is encrypted with ecryptfs. Being a bit of a noob, I was unable to rollback to previous kernel version (not sure how to do it if I can't get to a console), but I was able to get my data from the volume and provision another VM. I'll try provisioning a fresh VM from 15.10 iso to see if it is easily reproduced, or if there is something particular about my install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548985 Title: After linux kernel update system won't boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1548985] Re: After linux kernel update system won't boot
*** Update I was able to reproduce this issue in a fresh provisioning from the Kubuntu 15.10 ISO, although the boot log now stops at [OK] Started Accounts Service (See screen shot). Steps to reproduce: 1) Create a new VM (VMWare Fusion 8.1.0, although I doubt this matters) 4 cpu cores, 8GB Ram, 60GB disk 2) Install Kubuntu 15.10 from ISO (x64) 3) Install open-vm-tools sudo apt-get install open-vm-tools sudo apt-get install open-vm-tools-desktop 5) Restart 6) Upgrade distribution sudo apt-get update sudo apt-get upgrade 7) Restart. Machine wont complete the boot process, resulting in a black screen ** Attachment added: "Screen Shot 2016-02-25 at 11.29.52 AM.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548985/+attachment/4580500/+files/Screen%20Shot%202016-02-25%20at%2011.29.52%20AM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1548985 Title: After linux kernel update system won't boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1548985/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 762032] Re: alt+tab broken with click-to-focus off
I would like to politely correct the author of post #11, who says this is only "a particular use-case." The author is mistaken to believe that the (well written) steps to reproduction make it sound like this is an obscure use case, whereas this is actually substantial use case, as iterated in post #12. Up until *now*, the ability to have coexistence of ALT-TAB and mouse- hover-focus has been an extremely useful way of choosing where to focus. And, it has been supported quite well in numerous windowing systems, including GNOME. But now it is broken; And it is broken in an obscure way, which necessitates the complex reproduction instructions of this bug report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/762032 Title: alt+tab broken with click-to-focus off To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/762032/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
