[Bug 1256730] Re: /usr/share/initramfs-toos/hooks/cryptroot does not honour the CRYPTSETUP variable
If you run into this make sure when you are mounting and repairing in a chroot via `cryptsetup open /dev/whatever mapper-name` that the `mapper- name` matches what you have in your `/etc/crypttab`. You can get this by booting from the LiveCD and manually mounting the encrypted partition. Or try something like the script below which was tested on 18.04, but may work for earlier versions as hopefully the APIs haven't changed much for things like critical boot path. https://gist.github.com/dragon788/e777ba64d373210e4f6306ad40ee0e80 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1256730 Title: /usr/share/initramfs-toos/hooks/cryptroot does not honour the CRYPTSETUP variable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1256730/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
Per the above the flag appears to work, and it appears that setting the cap still does the automatic detection when the system memory is equal to or less than the cap. For example I hardcoded 16384 per above to handle swap for our 32GB RAM laptops, and on our 16GB RAM laptops it knows the system RAM is less and correctly set the actual swap size to 16GB not 32GB. I'm still not super enthusiastic that this change was applied globally as the default, especially considering it is much easier to throw away an essentially ephemeral cloud compute instance that was the use case for changing the default in the first place, and those would be much easier to customize and test with a flag than every enterprise using Ubuntu for laptops having to scratch their head and hopefully learn about and add this new flag. It gets even more challenging now that there are laptops with 64 or 128GB of RAM available or coming out soon which overlaps or exceeds many consumer or business desktops so they may need to do model detection to figure out if it is a desktop or laptop and increase the cap accordingly. I really hope the error message is improved when attempting to `systemctl hibernate` when there isn't a large enough swap partition, and I also hope that the Hibernation wiki page(s) are updated to let folks installing 18.04 know that unless they customize the partitions on install or resize them after the fact, they will be unable to hibernate their shiny new laptop and will have to settle for suspending or completely powering off instead. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
It can also depend whether you have a discrete GPU or not, as sometimes those don't properly power off and eat a lot more battery when running and possibly when suspended. I frequently take my laptop home in case the on-call phone rings, and if I suspend on a Thursday/Friday and I don't pull it out of my bag and plug it in, if it is a holiday weekend I may pull it out and have the battery at 10% or less, which doesn't last long once you get on VPN and have the CPU crunching away at encryption, and having a fully encrypted disk also eats more battery (and makes it harder to do the LVM resize mentioned above). I'm testing the above mentioned flag and it does appear to at least create the correctly sized partition, though I'm not sure whether for a 32GB RAM system simply doubling 16384 is the right route or if I need to add a little more space for overhead in order to hibernate correctly if the RAM is full or close to full capacity when attempting to hibernate. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
I wonder if it is an opinion that the number of companies using Ubuntu on laptops might be reduced starting with 18.04 considering the amount of extra effort to write a completely custom partman recipe with a larger swap (or assuming the answer above works in the preseed to actually get the old behavior of 100% or so) in order to use hibernation to conserve battery life, since suspend still tends to run a battery down fairly quickly, and those that don't have access to power now have to shut down their machines completely losing their working state rather than being able to quickly hibernate and resume. It makes me sad that rather than reuse a preseed that has worked across multiple previous releases of Ubuntu without alteration I now have to come up with a partman recipe to handle whether I need an EFI partition or not as well as how large to make each individual partition including the swap. I feel like introducing a new recipe or at least making it opt-in for the change rather than automatically breaking existing preseeds for everyone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1091793] Re: Quirk for 2-button mouse Cirque Corporation 9925 AG Touch
I've got a 4 button model, the GP410U-5021, it also identifies as a 9925 AG Touch. Bus 001 Device 012: ID 0488:0281 Cirque Corp. Device Descriptor: bLength18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass0 (Defined at Interface level) bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 8 idVendor 0x0488 Cirque Corp. idProduct 0x0281 bcdDevice4.80 iManufacturer 1 Cirque Corporation iProduct2 9925 AG Touchpad iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 34 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xa0 (Bus Powered) Remote Wakeup MaxPower 20mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber0 bAlternateSetting 0 bNumEndpoints 1 bInterfaceClass 3 Human Interface Device bInterfaceSubClass 1 Boot Interface Subclass bInterfaceProtocol 2 Mouse iInterface 3 USB HID Device Descriptor: bLength 9 bDescriptorType33 bcdHID 1.11 bCountryCode 33 US bNumDescriptors 1 bDescriptorType34 Report wDescriptorLength 54 Report Descriptors: ** UNAVAILABLE ** Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes3 Transfer TypeInterrupt Synch Type None Usage Type Data wMaxPacketSize 0x000d 1x 13 bytes bInterval 10 Device Status: 0x (Bus Powered) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1091793 Title: Quirk for 2-button mouse Cirque Corporation 9925 AG Touch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1091793/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1351267] Re: partman-auto prefers to give disk to swap, leaving root too small
Did this somehow get enabled by default? There is a recently opened issue where on 18.04 a previously working preseed with the partman- auto/recipe select atomic is creating a tiny 1GB swap on systems with 16GB-32GB of RAM, preventing the ability to hibernate. https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1767299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1351267 Title: partman-auto prefers to give disk to swap, leaving root too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
Possibly related to changes for this "bug"? https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1351267 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767299] Re: Ubuntu 18.04 Installer creates swap partition too small
Just discovered I'm having the same issue. I used `d-i partman- auto/choose_recipe select atomic` for the install along with `d-i partman-auto-lvm/guided_size string max`. I can dump all the partman parameters here if that helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767299 Title: Ubuntu 18.04 Installer creates swap partition too small To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1767299/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1215262] Re: Automatically Disconnect When Switching Between VPNs
I'm not entirely certain the graphical representation you are seeing is due to any limitation in Network Manager. While I agree there should be a disconnect all option for VPNs, I'm able to see and select multiple VPNs to connect to in the UI, and in some cases I would NOT like to have it force disconnect one connection to connect to another. What you may be seeing is a common issue where if you don't specify the name of the adapter to use (defaults to 'tun') then it trips over itself reusing the same name over and over for each connection. Simply changing the device name (it will create it when necessary as long as you have enough permissions) will allow you to have multiple connections and activate them at the same time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1215262 Title: Automatically Disconnect When Switching Between VPNs To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1215262/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1347726] Re: ubuntu14.04 installation hang on "The installer has detected that the following disks have mounted partitions"
I was running into the same issue and finally by luck happened upon a set of slides that allowed me to automate this and there was an accompanying code repository with the full preseed file. https://github.com/uweplonus/adia- install/blob/master/initrd/preseed.cfg#L3 Many people suggest using `preseed/early_command umount /media/*` but this hasn't worked for quite some time due to the timing of when the preseed portion runs compared to the partitioning. The correct way to do this is to add the following anywhere in your preseed file that is referenced by the boot command. ```d-i partman/early_command string \ USBDEV=$(list-devices usb-partition | sed "s/\(.*\)./\1/");\ BOOTDEV=$(list-devices disk | grep -v "$USBDEV" | head -1);\ debconf-set partman-auto/disk $BOOTDEV;\ debconf-set grub-installer/bootdev $BOOTDEV; \ umount /media; ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1347726 Title: ubuntu14.04 installation hang on "The installer has detected that the following disks have mounted partitions" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1347726/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1628659] Re: "d-i partman/unmount_active boolean true" not working
I was running into the same issue and finally by luck happened upon a set of slides that allowed me to automate this and there was an accompanying code repository with the full preseed file. https://github.com/uweplonus/adia- install/blob/master/initrd/preseed.cfg#L3 Many people suggest using `preseed/early_command umount /media/*` but this hasn't worked for quite some time due to the timing of when the preseed portion runs compared to the partitioning. The correct way to do this is to add the following anywhere in your preseed file that is referenced by the boot command. ```d-i partman/early_command string \ USBDEV=$(list-devices usb-partition | sed "s/\(.*\)./\1/");\ BOOTDEV=$(list-devices disk | grep -v "$USBDEV" | head -1);\ debconf-set partman-auto/disk $BOOTDEV;\ debconf-set grub-installer/bootdev $BOOTDEV; \ umount /media; ``` -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1628659 Title: "d-i partman/unmount_active boolean true" not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/preseed/+bug/1628659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1667750] Re: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13
Patrick, I definitely like your script as a quick workaround (as even 100Mb/s is better than our busy wireless), and I'm trying to make it a little more generic. If you run `udevadm info -e | grep -A 10 '^P.*enx'` what does it show for ID_MODEL_ID and ID_NET_DRIVER and ID_NET_NAME? My system reports 8153 and 8152 and enp14s0u1u2 respectively for the TB16 and the TB15. The only difference when testing with a Dell D59GG USB-C ethernet adapter was the ID_NET_NAME changed because it wasn't going through the ASMedia USB hub anymore. Using the ID_NET_NAME may be a better way to identify the device as the MAC address changes per host (my MAC was the same when connected to the TB15 and TB16 and the USB-C adapter thanks to some previous kernel patches that have gone upstream integrating the host fixed MAC, but the ID_NET_NAME should be the same for all the docks (and hopefully a low probability to overlap with USB2/USB3 gigabit ethernet adapters commonly in use). The fixed MAC is nice as it keeps the same IP if I change between docks or the USB-C within our LAN. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1667750 Title: xhci_hcd: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1667750/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697395] Re: Thunderbolt devices don't work if connected during boot
I wonder if we need to sleep a second between the unbind and the rebind? I still haven't restarted but I will test that while monitoring with `journalctl -xf` in another terminal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697395 Title: Thunderbolt devices don't work if connected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1697395] Re: Thunderbolt devices don't work if connected during boot
Kai-Heng, did you run the command as root? Otherwise you may want to `sudo su` and run the loop or "prime" your sudo by running `sudo echo` (to get prompted for you password once) and then use the same loop but instead of `> /path/to/file` use `| tee /path/to/file` and see if you get different results. I will bookmark this to test after my next restart, as I'm seeing the same issue on boot, and I don't know that changing the system hardware test from Automatic to Thorough or Quick in the BIOS will make a difference. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1697395 Title: Thunderbolt devices don't work if connected during boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1697395/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
