[Bug 1796917] Re: cloud-init fails to run on latest cosmic minimal image
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (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/1796917 Title: cloud-init fails to run on latest cosmic minimal image To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796917/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
https://github.com/lxc/lxd/issues/4656 ** Bug watch added: LXD bug tracker #4656 https://github.com/lxc/lxd/issues/4656 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816214] Re: Thinks logical volume is not mounted because it's not using /dev/mapper/vg-* path
After some more playing around, I realized that I was slightly off in my
initial analysis. It's not /etc/fstab that it obtains the /dev/vg/*
references from, but lvdisplay:
$ sudo lvdisplay --config 'log{command_names=0}' -c -a
WARNING: Device /dev/mapper/sda5_crypt has size of 1950040760 sectors which
is smaller than corresponding PV size of 1950302578 sectors. Was device resized?
One or more devices used as PVs in VG vg have changed sizes.
/dev/vg/root:vg:3:1:-1:1:83886080:10240:-1:0:-1:253:1
/dev/vg/swap:vg:3:1:-1:2:17301504:2112:-1:0:-1:253:2
/dev/vg/home:vg:3:1:-1:1:429916160:52480:-1:0:-1:253:3
/dev/vg/music:vg:3:1:-1:1:205832192:25126:-1:0:-1:253:4
/dev/vg/documents:vg:3:1:-1:1:209715200:25600:-1:0:-1:253:5
/dev/vg/pictures:vg:3:1:-1:1:167772160:20480:-1:0:-1:253:6
/dev/vg/downloads:vg:3:1:-1:1:41943040:5120:-1:0:-1:253:7
/dev/vg/video:vg:3:1:-1:1:209715200:25600:-1:0:-1:253:8
/dev/vg/vm:vg:3:1:-1:1:146800640:17920:-1:0:-1:253:9
/dev/vg/git:vg:3:1:-1:1:41943040:5120:-1:0:-1:253:10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816214
Title:
Thinks logical volume is not mounted because it's not using
/dev/mapper/vg-* path
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system-config-lvm/+bug/1816214/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1816214] [NEW] Thinks logical volume is not mounted because it's not using /dev/mapper/vg-* path
Public bug reported: I have a volume group named 'vg'. /dev/mapper/vg-* and /dev/vg/* are symlinks to the same devicemapper entries: $ ls -l /dev/vg lrwxrwxrwx 1 root root 7 Feb 14 21:44 documents -> ../dm-5 lrwxrwxrwx 1 root root 7 Feb 14 21:44 downloads -> ../dm-7 lrwxrwxrwx 1 root root 8 Feb 14 21:44 git -> ../dm-10 lrwxrwxrwx 1 root root 7 Feb 14 21:44 home -> ../dm-3 lrwxrwxrwx 1 root root 7 Feb 14 21:44 music -> ../dm-4 lrwxrwxrwx 1 root root 7 Feb 14 21:44 pictures -> ../dm-6 lrwxrwxrwx 1 root root 7 Feb 14 21:44 root -> ../dm-1 lrwxrwxrwx 1 root root 7 Feb 14 21:44 swap -> ../dm-2 lrwxrwxrwx 1 root root 7 Feb 14 21:44 video -> ../dm-8 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vm -> ../dm-9 $ ls -l /dev/mapper total 0 crw--- 1 root root 10, 236 Feb 14 21:44 control lrwxrwxrwx 1 root root 7 Feb 14 21:44 sda5_crypt -> ../dm-0 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-documents -> ../dm-5 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-downloads -> ../dm-7 lrwxrwxrwx 1 root root 8 Feb 14 21:44 vg-git -> ../dm-10 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-home -> ../dm-3 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-music -> ../dm-4 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-pictures -> ../dm-6 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-root -> ../dm-1 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-swap -> ../dm-2 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-video -> ../dm-8 lrwxrwxrwx 1 root root 7 Feb 14 21:44 vg-vm -> ../dm-9 /etc/fstab contains /dev/vg versions: /dev/vg/music /home/swissj74/musicext4 defaults,discard,relatime 1 2 /dev/vg/documents /home/swissj74/documentsext4 defaults,discard,relatime 1 2 /dev/vg/pictures/home/swissj74/pictures ext4 defaults,discard,relatime 1 2 /dev/vg/downloads /home/swissj74/downloadsext4 defaults,discard,relatime 1 2 /dev/vg/video /home/swissj74/videoext4 defaults,discard,relatime 1 2 /dev/vg/vm /home/swissj74/vm ext4defaults,discard,relatime 1 2 /dev/vg/git /home/swissj74/git ext4defaults,discard,relatime 1 2 However, something changed in some Ubuntu version since xenial (this is bionic LTS), and despite the fstab entries, the actual mounts in /proc/mounts are the /dev/mapper paths according to the kernel: /dev/mapper/vg-home on /home type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-pictures on /home/swissj74/pictures type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-vm on /home/swissj74/vm type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-documents on /home/swissj74/documents type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-downloads on /home/swissj74/downloads type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-git on /home/swissj74/git type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-music on /home/swissj74/music type ext4 (rw,relatime,discard,data=ordered) /dev/mapper/vg-video on /home/swissj74/video type ext4 (rw,relatime,discard,data=ordered) system-config-lvm reads /proc/mounts, looks for the /dev/vg entries from fstab, concludes the volumes are not mounted, and throws an error on any operation: "Logical volume is not mounted but is in use. Please close all applications using this device (eg iscsi)" It appears that when checking for whether a volume is mounted, system-config-lvm should, for each volum it's operating on: 1. Resolve symlinks from /etc/fstab until it reaches the real block device 2. Resolve any symlinks in /proc/mounts until the real block devices are reached 3. If the block device from 1 is contained in the set from 2, then it's considered mounted. Although, I might suggest abandoning this approach and using lsblk or findmnt instead. ** Affects: system-config-lvm (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/1816214 Title: Thinks logical volume is not mounted because it's not using /dev/mapper/vg-* path To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-lvm/+bug/1816214/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275740] Re: Installer fails when preseeding 'partman-partitioning/confirm_resize'
For clarification, Ubuntu 18.04 runs into the same issue. Also, there's a typo in the above but the overall message is correct. d-i partman-auto/automatically_partition *select* Guided - resize /dev/nvme0n1p4 and use freed space -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275740 Title: Installer fails when preseeding 'partman-partitioning/confirm_resize' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1275740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1275740] Re: Installer fails when preseeding 'partman-partitioning/confirm_resize'
I'm currently attempting to dualboot Ubuntu 18.10 with Windows 10 using a preseed. The windows environment is loaded via task sequence and leaves 50% of the disk as a blank partition (partition 4). I'm then attempting to take that partition, delete/resize it, and install Ubuntu according to my encrypted lvm partition map. Upon setting: d-i partman-partitionning/confirm_resize boolean true d-i partman-auto/disk string /dev/nvme0n1p4 d-i partman-auto/automatically_partition string Guided - resize /dev/nvme0n1p4 and use freed space d-i partman-auto/method string crypto I experience the aforementioned loop. Other solutions attempted: I'm also playing with the idea of having the 4th partition be just empty space but upon setting d-i partman-auto/init_automatically_partition select biggest_free d-i partman-auto/method string crypto is ignored so while the partitions get created according to my recipe, they don't get encrypted. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1275740 Title: Installer fails when preseeding 'partman-partitioning/confirm_resize' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/partman-auto/+bug/1275740/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1815409] Re: 18.04 Vagrant Box long boot time
Hello Dan, Ubuntu is a great system! I use it almost exclusively for my development. Always looking for a way to give back. I know just opening a bug is not the most help so whatever way I can assist I am more than happy to do. Yes it was the latest from VirtualBox upstream. I am running on a Windows 10 host. I can open a bug with VirtualBox as well but based on my usage other cloud-images are working fine. It seems to be the Ubuntu cloud-image because a fresh install with the ISO worked fine. Again if there are any more details I can provide please let me know. Kind regards, Coury On Tue, Feb 12, 2019 at 11:00 AM Dan Watkins wrote: > Hi Coury, > > Thanks for filing this bug, and for using Ubuntu! Could you clarify > what platform you're using when you're seeing these issues? If the host > isn't Ubuntu, then you'll need to file a bug with whoever provided you > with that version of Virtualbox (presumably Virtualbox upstream?). > > > Thanks! > > Dan > > ** Also affects: virtualbox (Ubuntu) >Importance: Undecided >Status: New > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1815409 > > Title: > 18.04 Vagrant Box long boot time > > Status in cloud-images: > New > Status in virtualbox package in Ubuntu: > New > > Bug description: > Running in VirtualBox 6.0.4r128413 > With Vagrant 2.2.3 > > The Ubuntu images here: > https://app.vagrantup.com/ubuntu/boxes/bionic64 > https://app.vagrantup.com/ubuntu/boxes/xenial64 > > Have an incredibly long boot time. Vagrant times out waiting and I > have not waited long enough to see it finish 45 min max. > > Retrieving an ISO file from the Ubuntu server 18.04 download page and > spinning up a VM from that worked successfully. > > Using other vagrant boxes for other distos centos 7 specifically were > able to boot as well. > > Dropping back down to VirtualBox 5.2.26 successfully let both images > build. > > I am not a server admin so I do not have a detailed log at the moment > but whatever information is needed I will assist in gathering. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cloud-images/+bug/1815409/+subscriptions > -- Kind Regards, Coury Richards Cell (330)569-4274 coury.richa...@gmail.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815409 Title: 18.04 Vagrant Box long boot time To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1815409/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1565029] Re: bcache doesn't register/recognize devices on s390x
This still fails on s390x. I've an LPAR with 18.04 and kernel 4.15.0-39-generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1565029 Title: bcache doesn't register/recognize devices on s390x To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1565029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815254] Re: Azure multiple ips prevent access to metadata service
ip addr show output: https://paste.ubuntu.com/p/3gHdFzkrrQ/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815254 Title: Azure multiple ips prevent access to metadata service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815254] [NEW] Azure multiple ips prevent access to metadata service
Public bug reported: On an instance with a single interface and many private address, the "primary" address, is not used for outgoing communication as the source_ipaddr in packets; this prevents communicating with the IMDS service. Example metadata: https://paste.ubuntu.com/p/2y2NBck6VJ/ Generated netplan yaml: https://paste.ubuntu.com/p/Zn9tgYzTMb/ ** Affects: cloud-init (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/1815254 Title: Azure multiple ips prevent access to metadata service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1815254/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815051] Re: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries
** Also affects: cloud-init (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: cloud-init (Ubuntu Bionic) 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/1815051 Title: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1815051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1815051] Re: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries
** Also affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1815051 Title: Bionic netplan render invalid yaml duplicate anchor declaration for nameserver entries To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1815051/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1782008] Re: Unable to force delete a volume
For clarity, the above referenced change landed, but was reverted due to a regression. This bug is still open. https://review.openstack.org/#/c/583139/ ** Changed in: charm-cinder Status: Fix Released => Won't Fix ** Changed in: charm-cinder Status: Won't Fix => New ** Changed in: charm-cinder Milestone: 18.08 => 19.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1782008 Title: Unable to force delete a volume To manage notifications about this bug go to: https://bugs.launchpad.net/charm-cinder/+bug/1782008/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1779156] Re: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy'
This is still around. Scott wrote up a script to handle cleaning this up. https://gist.github.com/smoser/2c78cf54a1e22b6f05270bd3fead8a5c -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1779156 Title: lxc 'delete' fails to destroy ZFS filesystem 'dataset is busy' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1779156/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1813698] Re: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.
I am unsure how to close it On Tue, Feb 5, 2019 at 2:52 AM Faustin <1813...@bugs.launchpad.net> wrote: > Hi Ryan, > problem is that without more information, I am unable to try to reproduce > this. > > Anyway, if the problem is resolved, I invite you to close this bug > report. > > Regards, > Faustin > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813698 > > Title: > package mariadb-server-10.1 (not installed) failed to install/upgrade: > trying to overwrite '/usr/bin/myisam_ftdump', which is also in package > mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > > Status in mariadb-10.1 package in Ubuntu: > Incomplete > > Bug description: > just passing this along > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: mariadb-server-10.1 (not installed) > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > Date: Mon Jan 28 20:27:33 2019 > ErrorMessage: trying to overwrite '/usr/bin/myisam_ftdump', which is > also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > InstallationDate: Installed on 2018-11-11 (78 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, > 3.6.7-1~18.04 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2.1 >apt 1.6.6ubuntu0.1 > SourcePackage: mariadb-10.1 > Title: package mariadb-server-10.1 (not installed) failed to > install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is > also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1813698/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813698 Title: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1813698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
...until I said that. Now it's doing it again on 18.04 on VZW. I'll try to see under what circumstances it does and does not happen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
It's not doing it right now on either 17.10 or 18.04, on either Optimum Online or VZW via hotspot. :-| -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
Note that this does not appear to be a detected MTU, but a server- provided MTU (if there is indeed 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/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
I don't use OpenConnect on MacOS -- I'm using the real Pulse Secure software version 5.2.5 (869). Before 18.04, it seemed that they worked identically well. One thing I did not consider, but will be able to test for: all of these problem scenarios occurred connected to an iPhone via wireless in hotspot mode on iOS 12.1.x. I should compare this to my home setup (Optimum Online) to make sure it wasn't something in the iOS hotspot or on VZW that changed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] Re: VPN does not work with MTU of 1400
I'm not absolutely certain, but I'm fairly sure. The behavior changed when I installed 18.04, which was relatively recently compared to its release date. For a couple of months, I'd try to use it for a few months, remember it was wonky, and need to get work done before the end of the train trip. Finally was on a longer one the other day where I went hunting for the solution. I can't be sure what the MTU was set to back when it was working/on 17.10 (I suppose I'll find out by installing that version), but the fact remains that the MTU that /does/ work with the MacOS version does not work with OpenConnect on 18.04. I'm not sure what could be different between the two. Anyway, will followup. If there's any useful output to provide, let me know. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814502] [NEW] VPN does not work with MTU of 1400
Public bug reported: After installing 18.04, I started to have VPN problems that were very erratic. Some things worked, some did not (including parts of out JIRA install's website work but not others). I traced this to MTU. The problem goes away if I set my MTU on the VPN interface to 1358. However, when I connect with openconnect -vvv, I see that the server side sets 1400. Additionally, 1400 works fine on the Mac version of Pulse Secure. I can't figure out what is going on or what could be different. This worked fine in 17.10. I am running 18.04 with all of the updates as of this week. ** Affects: openconnect (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/1814502 Title: VPN does not work with MTU of 1400 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1814502/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814162] [NEW] Xorg freeze
Public bug reported: When I lock my machine on the latest ubuntu version 4.15.0-44-generic, it turns my display completely black and unresponsive. This is only when I have my dock (with external displays in). After it freezes however, removing the dock has no effect. Booting back into 4.15.0-43-generic has fixed the problem so this is a regression bug. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jan 31 14:25:01 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:081c] InstallationDate: Installed on 2018-10-17 (106 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude 7490 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.2 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.2:bd11/26/2018:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic freeze third-party-packages ubuntu -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814162 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814162] Re: Xorg freeze
Sorry I realized this bug is misleading with the version listed, the bug is for version: 4.15.0-44-generic. I am booted into 43 to fix the problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814162 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1814162/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1813698] Re: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.
I don't even know what triggered it, it was random. bugzilla offered to post so I did if you can't use any of the info then I guess I wasted 30 seconds of my time cheers RyRy On Wed, Jan 30, 2019 at 2:01 AM Faustin <1813...@bugs.launchpad.net> wrote: > Hi Ryan, > Thank you for taking the time to report this bug and helping to make > Ubuntu better. Unfortunately, we cannot work on this bug because your > description didn't include enough information. You may find it helpful to > read "How to report bugs effectively" > http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful > if you would then provide a more complete description of the problem. > > We have instructions on debugging some types of problems at > http://wiki.ubuntu.com/DebuggingProcedures. > > At a minimum, we need: > 1. The specific steps or actions you took that caused you to encounter the > problem. > 2. The behavior you expected. > 3. The behavior you actually encountered (in as much detail as possible). > Thanks! > > ** Changed in: mariadb-10.1 (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1813698 > > Title: > package mariadb-server-10.1 (not installed) failed to install/upgrade: > trying to overwrite '/usr/bin/myisam_ftdump', which is also in package > mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > > Status in mariadb-10.1 package in Ubuntu: > Incomplete > > Bug description: > just passing this along > > ProblemType: Package > DistroRelease: Ubuntu 18.04 > Package: mariadb-server-10.1 (not installed) > ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 > Uname: Linux 4.15.0-44-generic x86_64 > ApportVersion: 2.20.9-0ubuntu7.5 > Architecture: amd64 > Date: Mon Jan 28 20:27:33 2019 > ErrorMessage: trying to overwrite '/usr/bin/myisam_ftdump', which is > also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > InstallationDate: Installed on 2018-11-11 (78 days ago) > InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 > (20180725) > Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, > 3.6.7-1~18.04 > PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, > 2.7.15~rc1-1 > RelatedPackageVersions: >dpkg 1.19.0.5ubuntu2.1 >apt 1.6.6ubuntu0.1 > SourcePackage: mariadb-10.1 > Title: package mariadb-server-10.1 (not installed) failed to > install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is > also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1813698/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813698 Title: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1813698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812925] Re: No OSDs has been initialized in random unit with "No block devices detected using current configuration"
I've recreated an VM instance that uses the curtin config attached to this bug. I can recreate the additional registrations and delete/create of the dname symlinks to the bcache devices by simply running 'udevadm trigger' in a loop, and watching, dname directory with inotifywatch (inotifywait -mr /dev/disk/by-dname). During a 'udevadm trigger', I can observer 10 DELETE operations (bcache0..9), and then 10 CREATE operations (bcache0..9). The symlinks appear almost immediately. Next, I increased the IO load on the system by spinning up fio against several of the bcacheN devices; This increased the time between removal and creation, but only in the order of milliseconds. I've not been able to induce a state such that only some of the bcache* symlinks are missing; so we're still looking for what else is going on in the system such that we've got pending uevents that need to be processed. Do we have any insight into the program using the dname symlinks? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812925 Title: No OSDs has been initialized in random unit with "No block devices detected using current configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
I believe it's supposed to say Fix Committed, not Fix Released. The change was a mistake -- see down in the thread. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813663] Re: External monitors does not work anymore 4.15.0-44
Do we know the full extent of this bug? I reverted to kernel 4.15.0-43, which resolved the issue on my tablet. But I noticed my desktop having some trouble this morning (weird file copy errors, reporting my printer was not accepting jobs and some unusual wifi cut- offs). I'll switch back to 4.15.0-43 on my desktop as well to see if that solves the problem there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813663 Title: External monitors does not work anymore 4.15.0-44 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813663/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813814] [NEW] please include systemd journal if present
Public bug reported: 1. # lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 2. # apt-cache policy sosreport sosreport: Installed: 3.6-1ubuntu0.18.04.2 Candidate: 3.6-1ubuntu0.18.04.2 Version table: *** 3.6-1ubuntu0.18.04.2 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.5-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 3. sosreport includes the entire systemd journal 4. sosreport only includes some journalctl command outputs On systems with a systemd journal, there is a binary database which includes all of the system journal events for all previous boots as well as the current one. The current collection is not comprehensive: ./sos_commands/systemd/journalctl_--list-boots ./sos_commands/logs/journalctl_--no-pager_--catalog_--boot_-1 ./sos_commands/logs/journalctl_--disk-usage ./sos_commands/logs/journalctl_--no-pager_--catalog_--boot If we include the entire journal, then further queries can be run against the journal offline. The journal may be in /run/log/journal (for ephemeral journal mode, like in Xenial) or in /var/log/journal (persistent mode, like in Bionic and newer). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: sosreport 3.6-1ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Tue Jan 29 17:42:38 2019 Dependencies: python3-six 1.11.0-2 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: sosreport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sosreport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813814 Title: please include systemd journal if present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sosreport/+bug/1813814/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812925] Re: No OSDs has been initialized in random unit with "No block devices detected using current configuration"
After looking at the journal I can conclude a few things. 1) the bcache devices are found and rules run and change events emitted fairly early during boot [8.873909] ubuntu kernel: bcache: bch_journal_replay() journal replay done, 673 keys in 35 entries, seq 724 [8.875099] ubuntu kernel: i40e :5e:00.3 eth3: NIC Link is Up, 10 Gbps Full Duplex, Flow Control: RX/TX [8.894272] ubuntu kernel: bcache: bch_cached_dev_attach() Caching sdi3 as bcache8 on set ab6e6820-99ba-4438-9df5-3f0f02fe8515 [8.908230] ubuntu kernel: bcache: bch_cached_dev_attach() Caching sdi4 as bcache7 on set ab6e6820-99ba-4438-9df5-3f0f02fe8515 [8.919554] ubuntu kernel: bcache: register_cache() registered cache device nvme0n1p1 [8.976751] ubuntu kernel: bcache: bch_journal_replay() journal replay done, 0 keys in 2 entries, seq 41 2) After Cold Plug (which happens very early after rootfs is mounted and the systemd-udevd.service is started; we see a repeat of the registration (which will re-emit the change event which exports the CACHED_UUID/CACHED_LABEL values from the kernel to userspace for the bcache rules to run and generate symlinks in /dev/bcache/by-uuid (and dname rules, which also depend on the same values in the ENV when the rules run). [ 13.320515] ubuntu systemd[1]: Started udev Coldplug all Devices. ... [ 14.405166] ubuntu kernel: bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) [ 14.405280] ubuntu kernel: bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) (skipping the additional ones) 3) Quite some time after the system is up and running, we see repeat registrations which are the result of something invoking udevadm trigger. [ 837.100772] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdb: device already registered (emitting change event) [ 837.117295] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdd: device already registered (emitting change event) [ 837.120357] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdh: device already registered (emitting change event) [ 837.122496] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sde: device already registered (emitting change event) [ 837.122765] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdf: device already registered (emitting change event) [ 837.132009] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) [ 837.160226] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) [ 837.177862] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/nvme0n1p3: device already registered [ 837.178724] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/nvme0n1p1: device already registered [ 837.195827] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) [ 837.196084] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdh: device already registered (emitting change event) [ 837.196107] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sda1: device already registered (emitting change event) [ 837.196351] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdb: device already registered (emitting change event) [ 837.196601] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sde: device already registered (emitting change event) [ 837.198407] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdd: device already registered (emitting change event) [ 837.199699] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdf: device already registered (emitting change event) [ 837.199733] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) [ 837.207026] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) [ 837.208943] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdd: device already registered (emitting change event) [ 837.209058] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdh: device already registered (emitting change event) [ 837.209697] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sde: device already registered (emitting change event) [ 837.209788] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) [ 837.212004] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdb: device already registered (emitting change event) [ 837.213403] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdf: device already registered (emitting change event) [ 841.815986] ln-sv-ostk01 kernel: bcache: register_bcache() error /dev/sdi4: device already registered (emitting change event) [ 841.816737] ln-sv-ostk01 kernel: bcache:
[Bug 1813795] Re: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel
apport information ** Tags added: apport-collected bionic ** Description changed: I have a Dell 5290 2-in-1 tablet that has been running Ubuntu 18.04 successfully for several months. Today I upgraded the kernel from 4.15.0-43 to 4.15.0-44. The tablet functions normally until it is plugged into its docking station, then the screen freezes. Technically, the screen flickers a few times, then goes blank, leaving only the frozen mouse pointer. The system is still running, though as I can ssh into my tablet. sudo reboot will not reboot the tablet, but sudo reboot -f will. When I force the tablet to load 4.15.0-43, the tablet functions normally. i.e. even when I plug it into its docking station, it continues to perform properly. It's only with 4.15.0-44 that it freezes. - As you can see from the linked question and forum thread, this appears - to be affecting many Dell tablets and laptops. It also appears clear - that the bug is not present in 4.15.0-43. + As you can see from the linked question and forum thread, this appears to be affecting many Dell tablets and laptops. It also appears clear that the bug is not present in 4.15.0-43. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: rybu 1971 F pulseaudio + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=35ab6535-9677-4ec9-9b70-33d75778947f + InstallationDate: Installed on 2018-11-09 (81 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: Dell Inc. Latitude 5290 2-in-1 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-44-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-44-generic N/A + linux-backports-modules-4.15.0-44-generic N/A + linux-firmware 1.173.3 + Tags: bionic + Uname: Linux 4.15.0-44-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 08/27/2018 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.4.3 + dmi.board.name: 0M27Y3 + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 32 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.4.3:bd08/27/2018:svnDellInc.:pnLatitude52902-in-1:pvr:rvnDellInc.:rn0M27Y3:rvrA00:cvnDellInc.:ct32:cvr: + dmi.product.family: Latitude + dmi.product.name: Latitude 5290 2-in-1 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233745/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233755/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233746/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233750/+files/Lsusb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233757/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233756/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233751/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233753/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233759/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233754/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233758/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233748/+files/IwConfig.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233752/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233747/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1813795/+attachment/5233749/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] Re: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel
Forum thread: https://askubuntu.com/questions/1113743/after-most-recent-kernel- update-4-15-0-44-generic-my-tablet-freezes-whenever-p Launchpad question: https://answers.launchpad.net/ubuntu/+question/678174 Let me know if there are any things I should look for in log files. Would be happy to include them, but not certain what to look for. Should be easy to find as I can log into the frozen tablet by ssh. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813795] [NEW] Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel
Public bug reported: I have a Dell 5290 2-in-1 tablet that has been running Ubuntu 18.04 successfully for several months. Today I upgraded the kernel from 4.15.0-43 to 4.15.0-44. The tablet functions normally until it is plugged into its docking station, then the screen freezes. Technically, the screen flickers a few times, then goes blank, leaving only the frozen mouse pointer. The system is still running, though as I can ssh into my tablet. sudo reboot will not reboot the tablet, but sudo reboot -f will. When I force the tablet to load 4.15.0-43, the tablet functions normally. i.e. even when I plug it into its docking station, it continues to perform properly. It's only with 4.15.0-44 that it freezes. As you can see from the linked question and forum thread, this appears to be affecting many Dell tablets and laptops. It also appears clear that the bug is not present in 4.15.0-43. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813795 Title: Dell tablet crashes when plugged into docking station with 4.15.0-44 kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813795/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1813698] [NEW] package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04
Public bug reported: just passing this along ProblemType: Package DistroRelease: Ubuntu 18.04 Package: mariadb-server-10.1 (not installed) ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Mon Jan 28 20:27:33 2019 ErrorMessage: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 InstallationDate: Installed on 2018-11-11 (78 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.6.6ubuntu0.1 SourcePackage: mariadb-10.1 Title: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mariadb-10.1 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1813698 Title: package mariadb-server-10.1 (not installed) failed to install/upgrade: trying to overwrite '/usr/bin/myisam_ftdump', which is also in package mysql-client-5.7 5.7.25-0ubuntu0.18.04.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mariadb-10.1/+bug/1813698/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811117] Re: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves'
The committed fix did not completely resolve the issue. ** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/362352 ** Changed in: curtin Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811117] Re: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves'
Thanks for the confirmation. The commit 81bf02ed was not sufficient to fix the issue. We'll be landing an additional change to ensure that partitions on bcache devices are recognized as partitions (not as actual bcache devices) as shutting them down is handled differently. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812925] Re: No OSDs has been initialized in random unit with "No block devices detected using current configuration"
I spent time looking at a udev debug log and I can confirm that during a
cold plug of the storage subsystem the bcache symlinks (kernel
(/dev/bcache/by-{uuid/label}, dname (/dev/disk/by-dname/)) will be
removed due to how the bcache driver works (it binds a backing and a
cache device) and when they aren't bound, then the symlinks have no
reference in the kernel and udev removes them.
The total time for a cold plug to settle was on the order of several
minutes. The system will do a cold plug very early after transitioning
from initramfs to rootfs; there is nothing that *forces* udev to settle;
it will over time ,however, if the charms are running before udev has
settled all of the uevents from the kernel, it's possible to find that
bcache related symlinks are not yet processed.
I believe we're waiting on capturing the entire system journal
(/var/log/journal/*) from a failing boot and then we'd like to confirm
at what point do the ceph charms start interacting with the system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812925
Title:
No OSDs has been initialized in random unit with "No block devices
detected using current configuration"
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1811117] Re: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves'
On Mon, Jan 28, 2019 at 9:31 AM Gábor Mészáros wrote: > it's affecting one of our customer deployments, running on xenial. I'm > curious if it's planned to release the fix on xenial, and when. > There's a related bug that's also being looked at to confirm if this resolves issues for them. https://bugs.launchpad.net/curtin/+bug/1796292 I've updated the PPA with one additional fix for dealing with bcache devices which have partitions. I'd like confirmation from QA (and/or field) that it addresses the issue. With that in-place we can start the SRU (and yes back to Xenial). > > ** Tags added: 4010 field-hige > > ** Tags removed: field-hige > ** Tags added: field-high > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/187 > > Title: > Failed deployment: FileNotFoundError: [Errno 2] No such file or > directory: '/sys/class/block/bcache0/bcache0p1/slaves' > > To manage notifications about this bug go to: > https://bugs.launchpad.net/curtin/+bug/187/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/187 Title: Failed deployment: FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/block/bcache0/bcache0p1/slaves' To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/187/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1812925] Re: No OSDs has been initialized in random unit with "No block devices detected using current configuration"
Looking at the syslog and kern.log, the kernel has emitted the change events which trigger the bcache rules, for all 12 devices, each time. So what remains to understand is whether udevd ran the hook (69-bcache.rules) and I see no reason it wouldn't. % grep kernel.*register_bcache /tmp/bcache-syslog.raw | head -n 13 Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478597] bcache: register_bcache() error /dev/sdh: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478608] bcache: register_bcache() error /dev/sdg: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478673] bcache: register_bcache() error /dev/sdb: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478684] bcache: register_bcache() error /dev/sde: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478695] bcache: register_bcache() error /dev/sdc: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.478843] bcache: register_bcache() error /dev/sdf: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.492735] bcache: register_bcache() error /dev/sdd: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.522047] bcache: register_bcache() error /dev/nvme0n1p3: device already registered Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.529593] bcache: register_bcache() error /dev/sda1: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.537218] bcache: register_bcache() error /dev/nvme0n1p1: device already registered Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.537606] bcache: register_bcache() error /dev/sdi4: device already registered (emitting change event) Jan 22 14:37:54 ln-sv-ostk08 kernel: [ 14.557305] bcache: register_bcache() error /dev/sdi3: device already registered (emitting change event) I didn't find the actual systemd journal (/run/log/journal/) in the sosreport, so we cannot see much of the udevd logging. It's likely that one will need to enable udevd verbose debugging and reproduce and capture to see what may be going on there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1812925 Title: No OSDs has been initialized in random unit with "No block devices detected using current configuration" To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1799779] Re: LXD module installs the wrong ZFS package if it's missing
Looking closer at Ubuntu releases: -- Xenial -- 'zfs' meta package is present, and wants to install: Note, selecting 'zfsutils-linux' instead of 'zfs' The following package was automatically installed and is no longer required: libfreetype6 Use 'sudo apt autoremove' to remove it. The following additional packages will be installed: binutils cpp cpp-5 dkms fakeroot gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libfakeroot libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpx0 libnvpair1linux libquadmath0 libtsan0 libubsan0 libuutil1linux libzfs2linux libzpool2linux linux-libc-dev make manpages-dev spl spl-dkms zfs-dkms zfs-doc zfs-zed Suggested packages: binutils-doc cpp-doc gcc-5-locales gcc-multilib autoconf automake libtool flex bison gdb gcc-doc gcc-5-multilib gcc-5-doc libgcc1-dbg libgomp1-dbg libitm1-dbg libatomic1-dbg libasan2-dbg liblsan0-dbg libtsan0-dbg libubsan0-dbg libcilkrts5-dbg libmpx0-dbg libquadmath0-dbg glibc-doc make-doc default-mta | mail-transport-agent samba-common-bin nfs-kernel-server zfs-initramfs The following NEW packages will be installed: binutils cpp cpp-5 dkms fakeroot gcc gcc-5 libasan2 libatomic1 libc-dev-bin libc6-dev libcc1-0 libcilkrts5 libfakeroot libgcc-5-dev libgomp1 libisl15 libitm1 liblsan0 libmpc3 libmpx0 libnvpair1linux libquadmath0 libtsan0 libubsan0 libuutil1linux libzfs2linux libzpool2linux linux-libc-dev make manpages-dev spl spl-dkms zfs-dkms zfs-doc zfs-zed zfsutils-linux -- bionic -- No 'zfs' meta package present, 'zfsutils-linux' offers to install The following additional packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed Suggested packages: zfs-modules | zfs-dkms nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: libnvpair1linux libuutil1linux libzfs2linux libzpool2linux zfs-zed zfsutils-linux -- cosmic -- No 'zfs' meta package present, but has a reference to it in the archive. $ sudo apt install zfs Reading package lists... Done Building dependency tree Reading state information... Done Package zfs is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'zfs' has no installation candidate 'zfsutils-linux' offers: $ sudo apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-4.18.0-13-lowlatency linux-modules-4.18.0-13-lowlatency os-prober zfs-zed Suggested packages: multiboot-doc grub-emu xorriso desktop-base fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools linux-headers-4.18.0-13-lowlatency nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-4.18.0-13-lowlatency linux-modules-4.18.0-13-lowlatency os-prober zfs-zed zfsutils-linux -- disco -- No 'zfs' meta package but has references in the archive, like cosmic. $ sudo apt install zfs Reading package lists... Done Building dependency tree Reading state information... Done Package zfs is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Package 'zfs' has no installation candidate The 'zfsutils-linux' package offers the following: $ sudo apt install zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-4.18.0-11-lowlatency linux-modules-4.18.0-11-lowlatency os-prober zfs-zed Suggested packages: multiboot-doc grub-emu xorriso desktop-base fdutils linux-doc-4.18.0 | linux-source-4.18.0 linux-tools linux-headers-4.18.0-11-lowlatency nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libnvpair1linux libuutil1linux libzfs2linux libzpool2linux linux-image-unsigned-4.18.0-11-lowlatency linux-modules-4.18.0-11-lowlatency os-prober zfs-zed zfsutils-linux -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1799779 Title: LXD module installs the wrong ZFS package if it's
[Bug 1718699] Re: curtin fails to setup bcache when unclean bcache from previous install exists
Please attach curtin verbose logs and your curtin config. https://discourse.maas.io/t/getting-curtin-debug-logs/169 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718699 Title: curtin fails to setup bcache when unclean bcache from previous install exists To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1718699/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site
** Description changed: I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to public Wifi hotspots without wifi security, that require login through a web page. I don't know if this is reproducible on arbitrary public networks, or only on the few I tried. The solution was as follows: - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll need root or sudo). - Add the following lines as recommended by Guruprasad (https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/): [connectivity] uri=http://network-test.debian.org/nm response=NetworkManager is online interval=300 - Restart the network manager with service network-manager restart (will need sudo or root again). This is a very annoying and unnecessary default behavior it seems. Maybe a good idea to fix it. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 31 22:48:21 2018 IfupdownConfig: - # interfaces(5) file used by ifup(8) and ifdown(8) - auto lo - iface lo inet loopback + # interfaces(5) file used by ifup(8) and ifdown(8) + auto lo + iface lo inet loopback InstallationDate: Installed on 2018-02-18 (41 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218) IpRoute: - default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 - 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 - 169.254.0.0/16 dev wlp1s0 scope link metric 1000 + default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 + 10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 600 + 169.254.0.0/16 dev wlp1s0 scope link metric 1000 NetworkManager.state: - [main] - NetworkingEnabled=true - WirelessEnabled=true - WWANEnabled=true + [main] + NetworkingEnabled=true + WirelessEnabled=true + WWANEnabled=true ProcEnviron: - LANGUAGE= - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + LANGUAGE= + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: - DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH - wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 - lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- + DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH + wlp1s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 SuedtirolSpot_1 c4464785-b548-4655-b06b-48a0aec06a87 /org/freedesktop/NetworkManager/ActiveConnection/3 + lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.10.6 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.10.6 connected started full enabled enabled enabled enabled enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760349 Title: Cannot log in to public open Wifi connection because not being redirected to login site To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1760349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229472/+files/PulseList.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229473/+files/RfKill.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229474/+files/UdevDb.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229475/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229471/+files/ProcModules.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229469/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229468/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229467/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229465/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229470/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229466/+files/Lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] Re: Alienware m15 takes very long to boot Ubuntu
apport information ** Tags added: apport-collected xenial ** Description changed: - Alienware m15 takes a long time to boot. Attached are the dmesg and - lspci prints. + Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. + --- + ApportVersion: 2.20.1-0ubuntu2.18 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ryan 2452 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=5dc51b23-d69d-4ced-8925-6821465b020d + InstallationDate: Installed on 2018-12-25 (21 days ago) + InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) + IwConfig: + wlp112s0 no wireless extensions. + + enp111s0 no wireless extensions. + + lono wireless extensions. + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 0bda:5765 Realtek Semiconductor Corp. + Bus 001 Device 003: ID 8087:0025 Intel Corp. + Bus 001 Device 002: ID 187c:0550 Alienware Corporation + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Alienware Alienware m15 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-43-generic root=UUID=b62227a1-0ff3-4fdb-9ef6-200fcc8a3a00 ro "acpi_osi=Windows 2015" acpi=noirq pci=biosirq debug ignore_level + ProcVersionSignature: Ubuntu 4.15.0-43.46~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-43-generic N/A + linux-backports-modules-4.15.0-43-generic N/A + linux-firmware 1.157.21 + Tags: xenial + Uname: Linux 4.15.0-43-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 12/20/2018 + dmi.bios.vendor: Alienware + dmi.bios.version: 1.3.3 + dmi.board.name: 0CNR45 + dmi.board.vendor: Alienware + dmi.board.version: A00 + dmi.chassis.type: 10 + dmi.chassis.vendor: Alienware + dmi.chassis.version: Not Specified + dmi.modalias: dmi:bvnAlienware:bvr1.3.3:bd12/20/2018:svnAlienware:pnAlienwarem15:pvr1.3.3:rvnAlienware:rn0CNR45:rvrA00:cvnAlienware:ct10:cvrNotSpecified: + dmi.product.family: Alienware + dmi.product.name: Alienware m15 + dmi.product.version: 1.3.3 + dmi.sys.vendor: Alienware ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229463/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229464/+files/CRDA.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811869] [NEW] Alienware m15 takes very long to boot Ubuntu
Public bug reported: Alienware m15 takes a long time to boot. Attached are the dmesg and lspci prints. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: TJ (tj) Status: New ** Attachment added: "errorlogs.txt" https://bugs.launchpad.net/bugs/1811869/+attachment/5229375/+files/errorlogs.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811869 Title: Alienware m15 takes very long to boot Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1811869/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
On Mon, Jan 14, 2019 at 1:55 PM Thiago Martins wrote: > @Ryan, > > The working XML file is attached here, with 2048 MB of RAM. > > NOTE: This XML was created using Virt-Manager, then, MaaS took it over > after being "refreshed". > Thanks! If you drop the section (which is what tells libvirt to boot via UEFI) does your VM still work? hvm /usr/share/OVMF/OVMF_CODE.fd /var/lib/libvirt/qemu/nvram/vunft-1_VARS.fd Note that MAAS boots UEFI images with grub2[1], not pxeboot/ipxe/seabios; so I think we can narrow down the error to the non-uefi case which may help find the issue. 1. http://images.maas.io/ephemeral-v3/daily/bootloaders/uefi/amd64/20181123.0/ > > Cheers! > Thiago > > ** Attachment added: "vunft-1.xml" > > https://bugs.launchpad.net/maas/+bug/1797581/+attachment/5229030/+files/vunft-1.xml > > -- > You received this bug notification because you are subscribed to qemu in > Ubuntu. > https://bugs.launchpad.net/bugs/1797581 > > Title: > Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to > kernel panic > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
@Thiago, Can you attach your guest XML that's working successfully with 2048MB? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Also here is my git branch in case you prefer to view the merge commit directly: https://salsa.debian.org/openldap-team/openldap/tree/ubuntu/merge-2.4.47 ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811630] [NEW] Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
Public bug reported: Hello, I have prepared the merge of openldap 2.4.47+dfsg-2. This will probably be the version released in Debian buster unless any release critical bugs show up. I made changes in Debian to how the contrib modules are built. I made the same changes for nssov in this merge and tested it with the current nss/pam-ldapd. I also added its man page which doesn't seem to have been included before. I performed a test build in a PPA: https://launchpad.net/~rtandy/+archive/ubuntu/openldap2.4.47 Please consider sponsoring this update. Thank you! ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
** Attachment added: "openldap_2.4.47+dfsg-2ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+attachment/5228960/+files/openldap_2.4.47+dfsg-2ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811630] Re: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main)
** Attachment added: "openldap_2.4.47+dfsg-2ubuntu1.dsc" https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+attachment/5228959/+files/openldap_2.4.47+dfsg-2ubuntu1.dsc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811630 Title: Please merge openldap 2.4.47+dfsg-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1811630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
Per https://wiki.ubuntu.com/QATeam/PerformingSRUVerification I had added the procedure and results to the description: TEST CASE: 1. Enable -proposed 2. apt-get install mountall=2.53ubuntu1 3. update-initramfs -k all -u 4. Reboot VERIFICATION DONE Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. ** Changed in: mountall (Ubuntu Trusty) Status: Incomplete => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811279] [NEW] probert --network throws stacktrace
Public bug reported: 1. Disco 2. probert (0.0.14.2build1) 3. probert --network produces json output 4. probert --network dumps stack trace root@rharper-d1:~# probert --network Traceback (most recent call last): File "/usr/bin/probert", line 62, in main() File "/usr/bin/probert", line 56, in main p.probe() File "/usr/lib/python3/dist-packages/probert/prober.py", line 41, in probe getattr(self, fn)() File "/usr/lib/python3/dist-packages/probert/prober.py", line 54, in probe_network results = network.probe() File "/usr/lib/python3/dist-packages/probert/network.py", line 332, in probe 'ip' : l.ip, AttributeError: 'NetworkInfo' object has no attribute 'ip' Here's the ip configuration of the container: root@rharper-d1:~# ip a 256: eth6@if257: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:bd:5e:86 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:febd:5e86/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:febd:5e86/64 scope link valid_lft forever preferred_lft forever 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 258: eth7@if259: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:db:a8:ed brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fedb:a8ed/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fedb:a8ed/64 scope link valid_lft forever preferred_lft forever 244: eth0@if245: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:1b:e4:66 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet 10.109.225.128/24 brd 10.109.225.255 scope global dynamic eth0 valid_lft 3572sec preferred_lft 3572sec inet6 fd42:1b7e:739f:50c0:216:3eff:fe1b:e466/64 scope global dynamic mngtmpaddr noprefixroute valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fe1b:e466/64 scope link valid_lft forever preferred_lft forever 246: eth1@if247: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:f5:ec:4b brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fef5:ec4b/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fef5:ec4b/64 scope link valid_lft forever preferred_lft forever 248: eth2@if249: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:29:f2:19 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fe29:f219/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fe29:f219/64 scope link valid_lft forever preferred_lft forever 250: eth3@if251: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:74:b2:c5 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fe74:b2c5/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fe74:b2c5/64 scope link valid_lft forever preferred_lft forever 252: eth4@if253: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:cd:dc:a9 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fecd:dca9/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fecd:dca9/64 scope link valid_lft forever preferred_lft forever 254: eth5@if255: mtu 1500 qdisc noqueue state UP group default qlen 1000 link/ether 00:16:3e:50:c4:a7 brd ff:ff:ff:ff:ff:ff link-netnsid 0 inet6 fd42:1b7e:739f:50c0:216:3eff:fe50:c4a7/64 scope global dynamic mngtmpaddr valid_lft 3590sec preferred_lft 3590sec inet6 fe80::216:3eff:fe50:c4a7/64 scope link valid_lft forever preferred_lft forever ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: probert 0.0.14.2build1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 Date: Thu Jan 10 20:16:28 2019 ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=C.UTF-8 SourcePackage: probert UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: probert (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco uec-images -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811279 Title: probert --network throws stacktrace To manage notifications about this bug go to:
[Bug 1811279] Re: probert --network throws stacktrace
Building probert from git tip (HEAD = 8b56d73068ec1f293d3db3b0b44966ede9ed1c94) works fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811279 Title: probert --network throws stacktrace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/probert/+bug/1811279/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1265898]
I had this problem, disabling drawing tabs in titlebar did work. I know this isn't supported ootb for Thunderbird, but we should consider addressing this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1265898 Title: thunderbird doesn't remember maximized window state in Ubuntu Gnome To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1265898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809994] [NEW] netplan reparses wifi when bridge member is listed before definition
Public bug reported:
1) # lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04
2) # apt-cache policy netplan.io
netplan.io:
Installed: 0.36.3
Candidate: 0.40.1~18.04.3
Version table:
0.40.1~18.04.3 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
*** 0.36.3 100
100 /var/lib/dpkg/status
0.36.1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
3) netplan generate creates configuration for a bridge with single
member and wifi accesspoint
4) netplan generate returns error, "Duplicate access point SSID"
# netplan --debug generate
DEBUG:command generate: running ['/lib/netplan/generate']
** (generate:5321): DEBUG: 20:44:08.972: Processing input file
//etc/netplan/50-cloud-init.yaml..
** (generate:5321): DEBUG: 20:44:08.972: starting new processing pass
** (generate:5321): DEBUG: 20:44:08.972: recording missing yaml_node_t enp5s0
** (generate:5321): DEBUG: 20:44:08.973: wlp6s0: adding wifi AP
'palisades-guest'
** (generate:5321): DEBUG: 20:44:08.973: starting new processing pass
** (generate:5321): DEBUG: 20:44:08.973: wlp6s0: adding wifi AP
'palisades-guest'
Error in network definition //etc/netplan/50-cloud-init.yaml line 18 column 16:
wlp6s0: Duplicate access point SSID 'palisades-guest'
% cat /etc/netplan/50-cloud-init.yaml
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
bridges:
mybridge:
interfaces: [enp5s0]
dhcp4: true
ethernets:
enp5s0:
dhcp4: no
wifis:
wlp6s0:
dhcp4: true
optional: true
access-points:
"mywifi":
password: "mypass"
version: 2
Note, if I move the ethernet definition of enp5s0 before the bridge,
netplan can parse it.
This appears to be related to parse.c:add_missing_node() which tags it
is missing a definition and then reparses. This then attempts to parse
wifis a second time and runs into a condition check that's meant to
prevent duplicate SSIDs.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: netplan.io 0.36.3
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Fri Dec 28 20:40:57 2018
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: netplan.io
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: netplan.io (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic uec-images
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809994
Title:
netplan reparses wifi when bridge member is listed before definition
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1809994/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809938] Re: delta syncrepl generates reqMod Attribute 'colon' with emtpty value
** Changed in: openldap (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809938 Title: delta syncrepl generates reqMod Attribute 'colon' with emtpty value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1809938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1809938] [NEW] delta syncrepl generates reqMod Attribute 'colon' with emtpty value
Hello Mario, This was an intentional change by OpenLDAP developers, in order to fix a replication bug that could cause providers and consumers to lose sync. Please see the upstream issue for the full details: http://www.openldap.org/its/?findid=6545 I confirm this behaviour on a producer running 2.4.45 or later. I confirm the "Invalid attribute" error (and failure to replicate) on a consumer running 2.4.42, but after upgrading the same to 2.4.45, everything works. I think in this case all I can recommend is to run the same version on your consumers as on your provider. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809938 Title: delta syncrepl generates reqMod Attribute 'colon' with emtpty value To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1809938/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809840] [NEW] Creating slideshow of large number of images fails due to inode exhaustion in default /tmp
Public bug reported: Creating a DVD image with several thousand (4000+) images fails, with this in the final log line: Error while writing video frame: Operation not permitted After much useless debugging and wasted time, I found: Filesystem Inodes IUsed IFree IUse% Mounted on udev998714 621 9980931% /dev tmpfs 1006983119410057891% /run /dev/mapper/ubuntu-root 53043200 646110 523970902% / tmpfs 1006983 3710069461% /dev/shm tmpfs 1006983 610069771% /run/lock tmpfs 1006983 1810069651% /sys/fs/cgroup /dev/loop0 35 35 0 100% /snap/canonical-livepatch/50 /dev/loop112691269 0 100% /snap/gnome-calculator/260 /dev/loop515981598 0 100% /snap/gnome-characters/139 /dev/loop6 12783 12783 0 100% /snap/core/5742 /dev/loop2 31 31 0 100% /snap/canonical-livepatch/49 /dev/loop7 27345 27345 0 100% /snap/gtk-common-themes/818 /dev/loop8 12783 12783 0 100% /snap/core/5662 /dev/loop9 12810 12810 0 100% /snap/core/6130 /dev/loop3 35 35 0 100% /snap/canonical-livepatch/54 /dev/loop4 747 747 0 100% /snap/gnome-system-monitor/57 /dev/loop10 27631 27631 0 100% /snap/gnome-3-26-1604/74 /dev/loop11 17201720 0 100% /snap/gnome-logs/45 /dev/sda459520 303 592171% /boot /dev/sda10 0 0 - /boot/efi AFS 2147483647 0 21474836470% /afs tmpfs 1006983 1006983 0 100% /run/user/1000 Note the last line. DVDStyler should statfs() on encoding failure to help the user triage simple problems like "out of disk space" and "out of inodes" instead of bubbling opaque FFmpeg error messages to the user. ** Affects: dvdstyler (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/1809840 Title: Creating slideshow of large number of images fails due to inode exhaustion in default /tmp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dvdstyler/+bug/1809840/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Description changed: [Impact] - * udev block nodes without a devname will crash mountall, resulting in + * udev block nodes without a devname will crash mountall, resulting in an unbootable system (emergency root shell) - * While this is not likely to happen in a matched distro/kernel + * While this is not likely to happen in a matched distro/kernel environment (it was discovered while needing to run a bionic 4.15 kernel on trusty), it is possible. - * The code in try_udev_device() assumes a block subsystem will always + * The code in try_udev_device() assumes a block subsystem will always have a devname; the SRU patches explicitly check for a devname and return if null. [Test Case] - * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install + * HPE DL385 Gen10, Samsung a822 NVMe controller, trusty install - * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not + * Kernels <4.15 (or possibly 4.14) do not expose nvme0c33n1 and do not trigger the bug. Tested on 4.13, 4.4 and 3.13. - * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, + * Kernel 4.15 exposes nvme0c33n1 in udev but does not have a devname, mountall crash ensues. [Regression Potential] - * Patch might ignore legitimate block devices on existing + * Patch might ignore legitimate block devices on existing installations. Unlikely, since the logic path for null devname leads directly to a program crash. [Other Info] - - * Additional context for Canonical employees: PS4.5 is a trusty backend cloud, but we now have Gen10 hardware incoming (this was discovered while adding new nova-compute hardware). Older kernels are not usable because Gen10 requires ilorest, which requires a >4.4 kernel (at least artful 4.13 is known good). So trusty+4.15 is the only viable combination for continued support of the cloud while adding new hardware. This is done via apt pinning of bionic for the kernel packages, and, mountall notwithstanding, is working fine so far. + + * Additional context for Canonical employees: PS4.5 is a trusty backend + cloud, but we now have Gen10 hardware incoming (this was discovered + while adding new nova-compute hardware). Older kernels are not usable + because Gen10 requires ilorest, which requires a >4.4 kernel (at least + artful 4.13 is known good). So trusty+4.15 is the only viable + combination for continued support of the cloud while adding new + hardware. This is done via apt pinning of bionic for the kernel + packages, and, mountall notwithstanding, is working fine so far. + + TEST CASE: + 1. Enable -proposed + 2. apt-get install mountall=2.53ubuntu1 + 3. update-initramfs -k all -u + 4. Reboot + + VERIFICATION DONE + Rebooted successfully on affected Gen10 systems. Confirmed no regression on unaffected systems. Original description: Running bionic's 4.15 kernel on trusty on an HPE DL385 Gen10 results in a device node for the NVMe controller, /devices/pci:40/:40:03.1/:43:00.0/nvme/nvme0/nvme0c33n1 which itself does not have a devname. When mountall gets to it: fsck_update: updating check priorities try_mount: /srv/nova/instances waiting for device try_udev_device: ignored /dev/loop5 (not yet ready?) try_udev_device: ignored /dev/loop6 (not yet ready?) try_udev_device: ignored /dev/loop1 (not yet ready?) try_udev_device: ignored /dev/loop0 (not yet ready?) try_udev_device: block (null) (null) (null) and then crashes, leaving the boot at an emergency root shell. A successful scan looks like this for comparison: try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sdb (null) (null) try_udev_device: block /dev/sda (null) (null) try_udev_device: block /dev/nvme0n1 ed56e3a9-60f7-4636-85a2-b53137b598e7 (null) try_udev_device: block /dev/bcache0 756cb2c6-b999-4905-a021-c2e688e81a86 instances The debdiffs check for a null devname in try_udev_device() and will not attempt to process it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807077] Re: [SRU] mountall crashes on udev node with missing devname
** Tags removed: verification-needed verification-needed-trusty ** Tags added: verification-done verification-done-trusty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807077 Title: [SRU] mountall crashes on udev node with missing devname To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1807077/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1615871]
I experience bad performance with accelerated compositing mode on using WebkitGTK+ 2.22.5 on Fedora 29 with Intel Iris 540 (Skylake mobile) graphics. Turning it off makes pretty much everything faster, but particularly Facebook, which is nearly unusable with accelerated compositing on. Also, when playing videos or scrolling through a site like Facebook, the laptop becomes hot and the fan goes full blast, which does not happen with accelerated compositing off. Would this bug be the issue I'm experiencing, or should I file a new bug about this? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1615871 Title: Poor performance with WebKit on yakkety with Intel modesetting enabled To manage notifications about this bug go to: https://bugs.launchpad.net/webkit-open-source/+bug/1615871/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808882] [NEW] false positive on tcpd
Public bug reported: This has apparently been a thing since at least 16.04 Install a clean version of Ubuntu, install chkrootkit, run a check. tcpd will report as infected. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chkrootkit 0.52-1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Mon Dec 17 18:30:29 2018 InstallationDate: Installed on 2018-12-05 (12 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: chkrootkit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: chkrootkit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808882 Title: false positive on tcpd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chkrootkit/+bug/1808882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
One other oddity in the xml is the cgroup construction in the "bad" case. /machine > > > To manage notifications about this bug go to: > https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 74747] Re: Default sources.list file has source packages enabled by default
This bug is believed to be fixed in cloud-init in version 18.5. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/74747 Title: Default sources.list file has source packages enabled by default To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/74747/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798424] Re: Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in
This bug is believed to be fixed in cloud-init in version 18.5. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1798424 Title: Xenial Azure: Make generation of network config from IMDS hotplug scripts configurable opt-in To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1798424/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798117] Re: juju sends "network" top level key to user.network-config in lxd containers
This bug is believed to be fixed in cloud-init in version 18.5. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: cloud-init 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/1798117 Title: juju sends "network" top level key to user.network-config in lxd containers To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1798117/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1806015] Re: bcache: performance regression without tuning under bionic
I confirmed that the underlying block devices (SAS, NVME) perform the same on the 4.4 and 4.15 kernels. Roughly 170 IOP/s direct to the SAS device and 570 IOP/s direct to the bcache infront of the SAS device. The block scheduler has no effect, due to the use of O_DIRECT. I can reproduce the sysbench difference in performance on 4.15 versus 4.4. The tuning helps though, only disabling sequential_cutoff really matters as this enables bcache to also cache reads; in general the faster reads allow additional writes. During testing, I believe the core issue we're seeing between 4.4 and 4.15 is around two things: 1) ext4 fs on bionic + enable metadata_csum by default on the filesystems, which will result in additional latency and IO as the csum is calculated and then embedded into the journal 2) fsync performance on 4.15 is measurably slower than on 4.4, even without csum_metadata enabled -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1806015 Title: bcache: performance regression without tuning under bionic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806015/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807978] [NEW] vmtest: iscsi tests failing on cosmic/disco
Public bug reported: TestIscsiBasic and other Iscsi tests on Cosmic/Disco are failing in vmtest on jenkins. - looked some at curtin at iscsi failures cosmic, disco - 604 was first fail like this. cosmic 20181204 disco 20181129 https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-amd64/604/consoleFull 602 PASSED and did run disco cosmic 20181114 disco 20181109 - seems likely tied to open-iscsi upload https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1755858 or https://bugs.launchpad.net/ubuntu/+source/open-iscsi/+bug/1802354 I want to revert iscsi and see if it fixes. ** Affects: curtin (Ubuntu) Importance: Undecided Status: New ** Tags: curtin-vmtest -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807978 Title: vmtest: iscsi tests failing on cosmic/disco To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807978/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807617] [NEW] w3m won't use feh to open images
Public bug reported: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now w3m opens Firefox (a private window) or sometimes GIMP (GIMP for some png files - but not always, apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: w3m (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic feh w3m ** Description changed: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now - w3m opens Firefox of GIMP (GIMP for png files, apparently), instead. + w3m opens Firefox (a private window) of GIMP (GIMP for png files, + apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: It seems that, even though the option is set to use feh to open images, w3m will use just about any application *but* feh to do so. When I set the option to "feh", it originally used my DE's image viewer (eye of MATE). I specifically set my "Preferred Applications" to use feh as its image viewer, and no change. I then uninstalled eom completely, and now - w3m opens Firefox (a private window) of GIMP (GIMP for png files, - apparently), instead. + w3m opens Firefox (a private window) or sometimes GIMP (GIMP for some + png files - but not always, apparently), instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: w3m 0.5.3-36build1 ProcVersionSignature: Ubuntu 4.15.0-42.45-lowlatency 4.15.18 Uname: Linux 4.15.0-42-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: MATE Date: Sun Dec 9 16:46:09 2018 InstallationDate: Installed on 2018-12-05 (4 days ago) InstallationMedia: Ubuntu-MATE 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: w3m 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/1807617 Title: w3m won't use feh to open images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/w3m/+bug/1807617/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1807216] Re: Release 18.2
** Changed in: curtin (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1807216 Title: Release 18.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1807216/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764210] Re: unmount: disabled causes installation failure to exit silently
This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin 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/1764210 Title: unmount: disabled causes installation failure to exit silently To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1764210/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775622] Re: failure if target provided in config and directory already exists.
This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin 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/1775622 Title: failure if target provided in config and directory already exists. To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1775622/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1775630] Re: fails to install with fsimage source file:///foo.squashfs
This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin 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/1775630 Title: fails to install with fsimage source file:///foo.squashfs To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1775630/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764602] Re: installing over lvm install as done by d-i fails
This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin 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/1764602 Title: installing over lvm install as done by d-i fails To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1764602/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800153] Re: [2.5] Failed to deploy ppc64el when partition table is GPT
This bug is believed to be fixed in curtin in version 18.2. If this is still a problem for you, please make a comment and set the state back to New Thank you. ** Changed in: curtin 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/1800153 Title: [2.5] Failed to deploy ppc64el when partition table is GPT To manage notifications about this bug go to: https://bugs.launchpad.net/curtin/+bug/1800153/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
