As I have multiple profiles, I chose to simply delete all Cache
directories
$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
Looking at mesa git staging/23.0 it looks like 78a75e0d2 and 4c986c58b
may also be required.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2006669
Title:
Asynchronous wait
The above referenced commits are committed into mesa 23.0.0. I see
references to backports of this onto stable, but I'm not familiar enough
with mesa as a project just yet.
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: New
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2006669
Title:
Asynchronous wait on fence ... timed out
(hint:intel_atomic_commit_ready [i915])
ver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: mesa (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
S
Closing this ticket where I can as there's no update for 5 years. Plus
mir has been supplanted by wayland.
** Changed in: mesa (Ubuntu)
Status: New => Won't Fix
** Changed in: mir (Ubuntu)
Status: Triaged => Won't Fix
** Changed in: mir
Status: Triaged => Fix Released
--
So where are we on this folks?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991975
Title:
dev file system is mounted without nosuid or noexec
Status in linux package
Alright so that means we either need to push a change to remove noexec
from the kernel init code, or we go ahead with noexec, and give people
on option to remount with exec should they want sgx functionality. I do
think the nosuid flag does still provide some benefit even if we decide
not to
In case anyone is curious conversation is on-going on the kernel-team mailing
list
https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
@juliank, is this an aws system? If not there's a good chance that you
are using an initramfs to mount the filesystems. That's definited in
either /etc/init.d/udev or directly out of the init that lives in the
initramfs.
--
You received this bug notification because you are a member of Ubuntu
Here is a workaround for this issue in case anyone finds this in the
future.
Copy remount_dev.service to /etc/systemd/system
sudo chown root:root /etc/systemd/system/remount_dev.service
sudo systemctl daemon-reload
sudo systemctl enable remount_dev.service
Still I think the kernel patch should
** Information type changed from Private Security to Public Security
** Summary changed:
- dev file system is mounted without nosuid
+ dev file system is mounted without nosuid or noexec
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Description changed:
+ [ SRU TEMPLATE ]
+ [ Impact ]
+
+ * nosuid, and noexec bits are not set on /dev
+ * This has the potential for nefarious actors to use this as an avenue for
attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more
discussion around this.
+ *
** Changed in: linux (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: systemd (Ubuntu Jammy)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Jammy)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Looks like Kees already found this years ago.
https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/
Looks like it was accepted as commit 28f0c335dd4a1 in 5.17. So I think
we should apply this patch and the corresponding set
CONFIG_DEVTMPFS_SAFE=y at least for the
I was hoping to work around this in /etc/init.d/udev, but it looks like that
gets redirected to systemctl via
. lib/lsb/init-functions
** Description changed:
This is similar to
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.
I discovered that my ec2 instances
So far I've only tested focal AWS images, but this may likely exist
elsewhere as well.
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1991975
Title:
dev file system is mounted
Public bug reported:
This is similar to
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new.
I discovered that my ec2 instances based off of Canonical supplied AMI
ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the
nosuid option.
We (Indeed) were recently hit by mawk posix non-compliance as well. For
all the reasons stated above, I would also like to see mawk replaced
with gawk in main. I'd also like to see the mawk dependencies in the
ubuntu-meta packages replaced with gawk. For that reason I'm opening a
separate
Hey thanks for the fix, I've been on vacation, and didn't have a chance
to look at this further.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1839589
Title:
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1839589
Title:
pulseaudio FT
Public bug reported:
pulseaudio fails to build from source on Eoan
I was attempting to put together a patchset for LP#1839580, but it
appears as if the packages are currently failing to build from source.
Not sure how they built the first time around.
Here's my ppa's buildlog, for a source
Upstream merge request.
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/merge_requests/143
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1839580
Title:
Public bug reported:
LucidSound LS31 only outputs mono sound.
The usb vendor:prod = 2f12:0109.
The fix is incoming.
** Affects: pulseaudio (Ubuntu)
Importance: Undecided
Assignee: Dave Chiluk (chiluk)
Status: In Progress
** Changed in: pulseaudio (Ubuntu)
Status: New
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
I have tested bionic and cosmic myself, but I'd like to hear from a user
or two. I have experienced the low-volume issue, but that appears to be
correctable by launching alsamixer. All in all it's a better experience
than before imho.
--
You received this bug notification because you are a
I uploaded these changes for bionic and cosmic. Just waiting on sru
approval now.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio -
I uploaded the changes to disco this morning.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1758736
Title:
[USB-Audio - SteelSeries Arctis 7, playback] No stereo
** Description changed:
+ [Impact]
+
+ * User is only able to get mono audio from steelseries headsets because
+ they provide both a stereo and mono output. PA selects the mono output
+ by default.
+
+ * This should be backported to stable releases because this fix is
+isolated to code
I uploaded test packages for cosmic and disco to my ppa today. If
someone with the headset could test either of those as well that would
be awesome. I should be getting a headset here soon to test with.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** Changed in: pulseaudio (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: pulseaudio (Ubuntu Disco)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in
I'm pretty sure you need to adjust the "chat mix" knob on your headset
as the audio will now be playing through a separate audio device on the
headset. Basically previously it was using the mono "chat"/mono output
on the headphones. Now with the ppa it's primarily using the
"game"/stereo output.
@Kaj Printz Madsen
I know you opened this a long time ago, but is there any chance you
could test the ppa for me?
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Looking at pulseaudio upstream, it looks like 12.2 has
15386a710c1500f70085a6312fb4d84be4d254c9 and
c7fe78c9f73ded2c3428666722ec9c1af4b82812
but not
83675b3745c64bd738400eae44eb4daa195ed88a
fe6a9a8f59932f29cc77eac2a7e2c6bd07c8c7d0
3454c19f3c277d5d0099f17e7ebf5d2005afa4b0
Bionic will needs all
Basically what I did was backport all the required Arctis stuff that
seemed to be required in order to get my lucid sound headphones working.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
Can someone on this bug please test the packages from
https://launchpad.net/~chiluk/+archive/ubuntu/lp1758736
on Bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: pulseaudio (Ubuntu)
Importance: Undecided => Low
** Also affects: pulseaudio (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: pulseaudio (Ubuntu
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to curl in Ubuntu.
https://bugs.launchpad.net/bugs/1754294
Title:
After last updated libcurl3 on libcurl4, some apps are removed.
Status in curl package
Same thing in bionic
# journalctl -u systemd-hostnamed
-- Logs begin at Wed 2018-02-28 16:43:47 UTC, end at Wed 2018-02-28 16:44:28
UTC. --
Feb 28 16:44:03 bionic systemd[1]: systemd-hostnamed.service: Failed to reset
devices.list: Operation not permitted
Feb 28 16:44:03 bionic systemd[1]:
Verified kind of still exists with ubuntu 17.10 amd64 (daily) (20180227)
# journalctl -u systemd-hostnamed.service
-- Logs begin at Wed 2018-02-28 16:38:35 UTC, end at Wed 2018-02-28 16:39:16
UTC. --
Feb 28 16:38:51 pants systemd[1]: systemd-hostnamed.service: Failed to reset
devices.list:
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1670959
Title:
systemd-resolved using 100% CPU
Status in dnsmasq package in Ubuntu:
Confirmed
Sponsored artful.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned in bluetooth.conf and README
Status in bluez package
** Also affects: bluez (Ubuntu Artful)
Importance: Low
Status: New
** Tags removed: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
** Tags added: indeed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1458204
Title:
removing kernels should not require a restart afterward
Status in
Please try the latest hwe stack by. I'm using kabylake + the hwe stack
without issue at the moment.
sudo apt install --install-recommends linux-generic-hwe-16.04 xserver-
xorg-hwe-16.04
More info is available here.
https://wiki.ubuntu.com/Kernel/LTSEnablementStack
I'm also closing the
Just so you know I'm waiting for zesty release before uploading this. I
don't want to risk causing issues on the release media. Additionally
policy is to only push high priority bug fixes for the few weeks leading
up to release.
--
You received this bug notification because you are a member of
** Tags added: sts-sponsor-chiluk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1674680
Title:
Deprecated rfcomm.conf still mentioned
Status in bluez package in Ubuntu:
** Also affects: bluez (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu Yakkety)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in
Uploading jpg a second time so it's obvious, and not missed in the maas
of auto-uploaded logs.
** Attachment added: "Awesome example of decorator corruption."
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-367/+bug/1660388/+attachment/4810973/+files/corruption.jpg
--
You
Public bug reported:
After switching back from another user or after lock screen I
occasionally get corruption. This usually takes a few weeks after a
restart to reproduce. Might be related to nvidia drivers or mesa, or
compiz, or something else. Experienced this before recent update to
mesa
@jan-huebner
Please educate yourself about the stable release process and development process
https://wiki.ubuntu.com/StableReleaseUpdates
https://wiki.ubuntu.com/UbuntuDevelopment
A regression was discovered in another component. This is the reason
for the delay. This is very uncommon, but
@Lukasz
Looking good so far. Appears resolved with 1.10.6-1ubuntu3.2.
Thanks,
Dave.
** Tags removed: verification-needed
** Tags added: verification-done
** Tags removed: verification-done
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member
** Description changed:
[Impact]
- * On Xenial after installing lvm2, you must reboot before you are able to
run vgcreate.
- * The package installer should be starting lvmetad.service.
- * $ sudo vgcreate localvg
- /run/lvm/lvmetad.socket: connect failed: No such file or directory
-
** Changed in: initramfs-tools (Ubuntu)
Status: New => Invalid
** Changed in: maas-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
So apparently this is a feature of the dell-branded usb-c devices.
Please see the knowledge base.
http://www.dell.com/support/article/us/en/04/SLN301147
I've heard back from our contacts at dell, and the issue you are seeing
is apparently resolved via a firmware update.
--
You received this
Another thought is that the pxe firmware of the usb-c device was missed
in the rebranding process by dell. This is actually quite likely in my
opinion.
Either way we need to engage Dell in order to remedy this.
--
You received this bug notification because you are a member of Ubuntu
Touch
, and possibly also
the firmware of the usb-c device?
Thanks,
Dave Chiluk
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1639202
Title:
Cannot enlist/commission machines
Alright so the problem at present appears to be that the machine is pxe
booting off of a nic with a mac address that is not showing up after the
kernel boots.
The way the boot works is the bios/efi launches a pxe network stack.
This typically makes a dhcp request. The DHCP server responds with
One of my collegues informed me that maas 2.1 is meant to use
https://images.maas.io/ephemeral-v3/daily/
Instead of the ephemeral-v2 images.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
1. So this indicates to me that the kernel is unable to control the usb
device. When you mentioned earlier that you were able to investigate
the usb-c device with a 16.04.1 machine, what exact kernel version was
that machine running. uname -a output should be sufficient.
2. Can you similarly
>From the initramfs shell can you provide me the output for
ls -la /sys/class/net/*
and
cat /sys/class/net/*/address
I have a feeling you'll only see lo and enx847beb55c195. Specifially I'm
looking for the device name that matches your BOOTIF mac address. However if
it's showing up please
If the device is not being detected I have a feeling there may be
something going wrong with udev.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1639202
Title:
So from the best I can determine it looks like configure_networking out
of scripts/functions of the initramfs is failing to properly bring up
the network device. I'm going through the process now to figure out
what logic might actually be stopping it from functioning. I'll let you
know more when
s output and am able to
investigate the initramfs.
Thanks
** Changed in: maas
Status: Incomplete => Invalid
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
I spoke too soon still exists in Yakkety.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi networks after re-enabling wifi
Status
With my recent update to Yakkety I no longer seem to be experiencing
this issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1589401
Title:
cannot view wifi
Regression tracked via bug #1631474
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1628306
Title:
network booting fails for iscsi root if no ip is set
Status in
** Description changed:
[Impact]
* 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp
* Regression-updates
* The fix better parses the ip= command line argument.
[Test Case]
* Create a machine that boots using an nfsroot.
I tested maas's command line as well.
/proc/cmdline from a maas pxe boot is
BOOT_IMAGE=ubuntu/amd64/hwe-y/yakkety/daily/boot-kernel nomodeset
iscsi_target_name=iqn.2004-05.com.ubuntu:maas:ephemeral-ubuntu-amd64-hwe-y-yakkety-daily
iscsi_target_ip=192.168.1.5 iscsi_target_port=3260
** Description changed:
[Impact]
- * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+ * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
ip=dhcp or ip=:eth0:dhcp
- * Regression-updates
+ * Regression-updates
- * The fix better parses the ip=
I have uploaded a new version of initramfs-tools to my ppa, I would
again appreciate testing on this. Notably I fixed an bug that was
causing all_netbootable_devices to be tried instead of the interface
specified on the command line.
I also now handle the case where ip=:bootif , which really
** Patch added: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759968/+files/lp1631474.yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Updated debdiff to handle ip=:bootif use case.
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4759967/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Patch removed: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff
** Patch removed: "lp1631474.xenial.debdiff"
*** This bug is a duplicate of bug 1631474 ***
https://bugs.launchpad.net/bugs/1631474
I'd really appreciate if you tested the ppa available in bug 1631474,
and reported back.
I don't have access to a full nfsroot environment so this would be very
helpful. Also,
Please move back to the
** Description changed:
+ [Impact]
+
+ * 0.122ubuntu8.3 of initramfs-tools no longer correctly processed
+ ip=dhcp or ip=:eth0:dhcp
+
+ * Regression-updates
+
+ * The fix better parses the ip= command line argument.
+
+ [Test Case]
+
+ * Create a machine that boots using an nfsroot.
** Patch added: "lp1631474.yakkety.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757084/+files/lp1631474.yakkety.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I fixed up the comment, and the changelog comment and resubmit the
debdiff.
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757083/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you
** Patch removed: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Patch added: "lp1631474.xenial.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1631474/+attachment/4757065/+files/lp1631474.xenial.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I created a PPA with a proposed solution to this issue. If I could get
some testing with this ppa I would appreciate it. Additionally if you
test the ppa please report back and include your /proc/cmdline in your
comment.
Thank you,
Dave Chiluk
--
You received this bug notification because you
Woops I forgot to include the PPA
https://launchpad.net/~chiluk/+archive/ubuntu/lp1631474
I will remove this ppa when the package hits -proposed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
.
** Changed in: initramfs-tools (Ubuntu)
Importance: Undecided => High
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** This bug has been marked a duplicate of bug 1631474
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Dave Chiluk (chiluk)
** Changed in: initramfs-tools (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ini
Dediff from 8.2 to 8.3.
http://launchpadlibrarian.net/286956415/initramfs-tools_0.122ubuntu8.2_0.122ubuntu8.3.diff.gz
** Tags added: cpc sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1631474
Title:
No networking with initramfs-tools 0.122ubuntu8.3 and ip=dhcp boot
I actually also tested this on recent cloud-images of yakkety, and I'm
seeing the same thing. That may be a separate issue though as reboot
does not fix it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in
I just installed yakkety, and got a similar result. All of the cloud-
images and maas images have lvm2 already built in, so this would not be
seen there.
$ sudo vgcreate localvg
Command failed with status code 5.
I installed yakkety like this.
#!/bin/bash
virt-install \
--connect
Public bug reported:
[Impact]
* On Xenial after installing lvm2, you must reboot before you are able to run
vgcreate.
* The package installer should be starting lvmetad.service.
* $ sudo vgcreate localvg
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING:
@smoser
Did you commit your changes to the xenial cloud-init as well? I'm not
sure where xenial images grab cloud init for themselves, but I assume
out of the xenial archives. Am I missing something here?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
For those affected by this in xenial, I have created a PPA with fips
removed from the openssl binaries.
See it here.
https://launchpad.net/~chiluk/+archive/ubuntu/openssl+nofips
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
This needs to be resolved in Xenial as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1594748
Title:
CRYPTO_set_mem_functions() is broken
Status in OpenSSL:
@Joy
It looks like the upstream bug has been rejected. Do you know what the
resolution for this issue was? Can you work with upstream to figure out
what's going on?
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1594748
Title:
CRYPTO_set_mem_functions() is broken
Status in OpenSSL:
Unknown
Status in openssl
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1612294
Title:
Boot messages in /var/log/syslog are out of order and with mostly
"useless" timestamp
Public bug reported:
On boot, early kernel boot messages get displayed out of order with
userspace services starting. for example.
_
Aug 8 21:13:55 ubuntu systemd[1]: Started LVM2 metadata daemon.
Aug 8 21:13:55 ubuntu systemd[1]:
Personally I think we should modify MNTTAB in zfs-linux to point to
/proc/self/mounts. This may not be completely straightforward *(there
are a number of places that point to /etc/mnttab directly, or have logic
around it and /proc/mounts), but it should be doable. I like this
solution most
Public bug reported:
[Impact]
* zfs services fail on firstboot if zfs-utils is integrated into the
deployment image.
* Output from systemd -
sudo systemctl --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
● zfs-import-scan.service loaded failed failed Import ZFS pools by device
scanning
●
1 - 100 of 192 matches
Mail list logo
