In the VM created in my above comment, I enabled proposed, installed the
new systemd and rebooted. After that, I re-ran:
cd /boot
sudo kexec -l vmlinuz --initrd initrd.img --append
'BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=LABEL=cloudimg-rootfs ro
console=tty1 console=ttyS0'
sudo reboot
Apologies, I completely missed your comment, Nick! I was just able to
reproduce this using uvtool.
To launch the VM (and monitor the console output):
uvt-simplestreams-libvirt sync release=focal arch=amd64
uvt-kvm create firsttest release=focal
virsh console firsttest
Then, within the instance
Thanks Nick, much appreciated!
--
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/1969365
Title:
focal: backport kexec fallback patch
Status in systemd package in Ubuntu:
Thanks for the reply, Nick!
I think it's important enough to land because:
* you cannot execute `kexec` correctly on an Ubuntu 20.04 system without this
patch (it will fall back to performing a full reboot),
* kexec can be used to reduce downtime for critical systems which take a long
time to
I suspect this is something to do with initrd-less boot: it's usually
the initramfs which mounts /dev:
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/init#n40
The comment above that line is:
# Note that this only becomes /dev on the real filesystem if udev's scripts
# are used;
Public bug reported:
It would be great if focal's systemd could have
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
backported to it.
[Impact]
We have observed that kexec'ing to another kernel will fail as the drive
containing the `kexec` binary has been
I would also like to see this change:
* ubuntu-advantage-tools and its dependencies add about 3MB to ubuntu-minimal
installations (checked by installing ubuntu-minimal's Depends in a Docker
container with and without u-a-t)
* it installs a systemd timer which runs (to do nothing, as the service
Public bug reported:
When performing a `do-release-upgrade -d` on my groovy system, I saw:
Setting up python3-software-properties (0.99.8) ...
Failed to byte-compile
/usr/lib/python3/dist-packages/softwareproperties/extendedsourceslist.py:
File
Yep, that's what I've found; cloud-init is just waiting for its later
stages to run, which are blocked by snapd.seeded.service exiting.
** Changed in: cloud-init
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Given that the logind issue is an AppArmor issue and, per my previous
comment, "the two running jobs are systemd-logind.service and
snapd.seeded.service", I suspect that we'll find that snapd is running
into similar sorts of issues. I'll take a quick look now.
--
You received this bug
So I've done a little more testing. On boot, with /sys/power/resume
unset (i.e. 0:0), I see this in the logind debug logs:
Jan 08 09:47:11 surprise systemd-logind[1887]: Sleep mode "disk" is supported
by the kernel.
Jan 08 09:47:11 surprise systemd-logind[1887]: /dev/dm-2: is a candidate
Public bug reported:
# Steps to reproduce
1) Login as a regular user.
2) `sudo systemctl restart systemd-logind`
This boots you back to GDM, as you would expect.
3) Login as a user.
4) Wait a few seconds.
# Expected behaviour
I can continue to use my system normally.
# Actual behaviour
My
And, for clarity, when systemd does hibernate, I haven't had issues
restoring: it's just getting systemd to find the correct swap space to
use that's been the issue.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
On Thu, Jan 07, 2021 at 03:23:36PM -, Dimitri John Ledkov wrote:
> Also, you do disable secureboot as well right? Because with secureboot
> on, even though hybernation image is created, it will be ignored and
> not used upon resume.
Yep, Secure Boot is disabled on this system.
--
You
> So, looking at the systemd code at
https://github.com/systemd/systemd/blob/c5b6b4b6d08cf4c16a871401358faeb5a186c02a/src/shared
/sleep-config.c#L422-L426, perhaps setting /sys/power/resume to the
correct device actually was the workaround/fix?
The confusing part about this is that I don't
I enabled systemd-logind debug logging, and I saw:
Jan 06 17:45:18 surprise systemd-logind[73027]: Got message type=method_call
sender=:1.264 destination=:1.220 path=/org/freedesktop/login1
interface=org.freedesktop.login1.Manager member=CanHibernate cookie=6
reply_cookie=0 signature=n/a
> $ cat /sys/power/resume
> 0:0
This was a red herring. What I have found consistently fixes this is:
$ sudo swapoff /dev/sda2
$ sudo swapon -p 1 /dev/sda2
Hibernate then succeeds. However, this is not how I want my system
configured: I have a small swap partition on my SSD, which I would
Oh, and `free -h`:
totalusedfree shared buff/cache available
Mem: 15Gi 6.0Gi 667Mi 567Mi 9.0Gi 8.8Gi
Swap: 98Gi13Mi98Gi
--
You received this bug notification because you are a member of Ubuntu
/sys/power/image_size represents the required amount of space for the
image; that said, the machine has 16G RAM total, so even if that were
maxed out, it would fit into 97.7G comfortably.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It sounds to me like there's no cloud-init aspect here, so I'm going to
move our tasks to Incomplete (so they'll expire out eventually). Please
do set them back if I've missed something!
** Changed in: cloud-init (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: cloud-init (Ubuntu
One thing I have noticed, is that on boot:
$ cat /sys/power/resume
0:0
I can't test right now, but I _think_ that before the holiday break
setting that to 8:2[0] and restarting systemd-logind meant that
hibernate did then work.
[0] $ ls -l /sys/dev/block/8:2
lrwxrwxrwx 1 root root 0 Jan 5
Public bug reported:
I have plenty of swap space configured in my system:
$ cat /sys/power/image_size
6642229248 # ~ 6.2GiB
$ swapon
NAME TYPE SIZE USED PRIO
/dev/dm-2 partition 980M 0B -2
/dev/sda2 partition 97.7G 0B -3
But when I attempt to hibernate:
$ sudo systemctl
Hi Ian,
I've just launched such a container and I see a bunch of non-cloud-init
errors in the log and when I examine `systemctl list-jobs`, I see that
the two running jobs are systemd-logind.service and
snapd.seeded.service:
root@certain-cod:~# systemctl list-jobs
JOB UNIT
I've just tested, and this doesn't seem to reproduce when launching from
a captured image (with 90-hotplug-azure.yaml restored and `cloud-init
clean` executed). So I think I've exhausted the ways in which I can
attempt to gain more insight into what's happening during the part of
boot where this
(Added cloud-images for visibility.)
** Also affects: cloud-images
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/1902960
Thanks for the explanation, Dan! I was off down a wrong path, I
appreciate the correction.
I've just downloaded the Azure image from cloud-images.u.c and it
includes this in `/etc/netplan/90-hotplug-azure.yaml`:
# This netplan yaml is delivered in Azure cloud images to support
# attaching and
** Changed in: cloud-init (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
OK, I've managed to reproduce this (in a non-Juju launched VM). The
ordering of these journal lines look suspicious to me:
Nov 09 17:41:51.091033 ubuntu systemd[1]: Starting udev Coldplug all Devices...
Nov 09 17:41:51.236309 ubuntu systemd[1]: Finished Load Kernel Modules.
Nov 09
When investigating another issue, I found this line in my journal,
repeated a few times:
nm-dispatcher[3938]: /etc/network/if-up.d/resolved: 12: mystatedir: not
found
Not sure if that's related, but it seems suspicious at least.
--
You received this bug notification because you are a member of
Hey folks,
Thanks for the report! If someone could run `cloud-init collect-logs`
on an affected instance, and upload the produced tarball to this bug, we
can dig into it further. The contents of /etc/netplan would also be
very handy.
(Once attached, please move this back to New.)
Cheers,
On Thu, Oct 01, 2020 at 01:41:46PM -, Dan Watkins wrote:
> > How did resolve/netif get owned by root?
>
> I don't believe I've ever touched it before, so I'm not sure. I haven't
> rebooted since that last comment, I'll do that at some point today to
> check if ownersh
> How did resolve/netif get owned by root?
I don't believe I've ever touched it before, so I'm not sure. I haven't
rebooted since that last comment, I'll do that at some point today to
check if ownership reverts to root.
If it does, what debugging can I perform to determine what's doing it?
--
I've just tested: changing the ownership of /run/systemd/resolve/netif
to systemd-resolve:systemd-resolve resolves (haha) this issue. The
first restart of systemd-resolved after the change did not address it
(because the permissions issue means that the state was not persisted);
on a network
On Thu, Sep 24, 2020 at 09:42:28PM -, Balint Reczey wrote:
> The latest upload (246.6-1ubuntu1) may have fixed this as well.
This happened again just now when I upgraded my system to the new
systemd, so I assume not.
Here's a log snippet of restarting:
Sep 29 09:28:14 surprise systemd[1]:
I haven't been able to reproduce in a lxd container or an EC2 instance;
I don't have a convenient way of testing a different NetworkManager
system, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in
Public bug reported:
Running groovy on the desktop, with the systemd packages that migrated
today(/overnight EDT).
# Steps to reproduce:
1) `systemctl restart systemd-resolved.service`
(This is a minimal reproducer, but I first saw this after an apt upgrade
of systemd.)
# Expected behaviour:
** Changed in: cloud-init (Ubuntu)
Status: Incomplete => Invalid
--
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/1713803
Title:
replacement of resolvconf
Public bug reported:
The crash file I'm using is as-produced by the system (on groovy), and
appears to have an empty value for separator:
$ grep separator /var/crash/_usr_bin_neomutt.1000.crash
separator:
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: apport 2.20.11-0ubuntu42
I'm trying to understand if there is any work still required on this bug
for cloud-init. I've tested two network configurations (in lxd
containers). The first:
version: 2
ethernets:
eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 1337
As this is just a passthrough to netplan,
I've also seen this while running `ubuntu-bug /var/crash/...`.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1884221
Title:
`ubuntu-bug` fails with "UnboundLocalError:
** No longer affects: cloud-init
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1124384
Title:
Configuration reload clears event that others jobs may be waiting on
This doesn't seem to be a curtin bug to me; feel free to disagree (with
reasoning!).
** Changed in: curtin (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
How does this relate to bug 1870346?
--
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/1870410
Title:
wireless does not work on boot on RPi 3s
Status in systemd package in
cloud-init has support for ubuntu-drivers, it's not clear from this bug
what work we would need to do so I've marked our task Incomplete.
** Changed in: cloud-init
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
anon_inode:[eventfd] leaked on vgs invocation inside lxd container
Status in lvm2 package in Ubuntu:
Will post each as separate comments as the others are long:
# ls -lah /proc/self/fd
total 0
dr-x-- 2 root root 0 Apr 9 21:23 .
dr-xr-xr-x 9 root root 0 Apr 9 21:23 ..
lrwx-- 1 root root 64 Apr 9 21:23 0 -> /dev/pts/4
lrwx-- 1 root root 64 Apr 9 21:23 1 -> /dev/pts/4
lrwx-- 1
lxc info:
config:
core.https_address: '[::]:8443'
core.trust_password: true
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
-
Not sure why it would make a difference, but just in case, I can also
reproduce this against a local container (rather than a remote one).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
And I just did a `lxd init --auto` on a fresh EC2 instance and I can
also reproduce it there.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Title:
$ lxc info reproducer
Name: reproducer
Location: none
Remote: https://34.76.172.211:8443
Architecture: x86_64
Created: 2020/04/09 21:22 UTC
Status: Running
Type: container
Profiles: default
Pid: 16441
Ips:
eth0: inet10.160.29.12veth12a00fff
eth0: inet6
Thanks Alasdair, I've added a lxd task.
** Also affects: lxd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871487
Public bug reported:
Steps to reproduce:
$ lxc launch ubuntu-daily:f reproducer
$ lxc shell reproducer
$ vgs
Expected behaviour:
No output (the behaviour on an EC2 instance with no VGs).
Actual behaviour:
Outputs "File descriptor 25 (anon_inode:[eventfd]) leaked on vgs
invocation. Parent
Public bug reported:
And, AFAICT, it isn't present in any LVM manpage:
$ zgrep tags /usr/share/man/man*/*lvm*
/usr/share/man/man5/lvm.conf.5.gz:See \fBtags\fP configuration setting
description below.
/usr/share/man/man7/lvmreport.7.gz:Let's display one one more field in addition
("lv_tags" in
Public bug reported:
When I run `apt update`, I see an AppStream message in the output:
$ sudo apt update
Fetched 42.5 MB in 15s (2,842 kB/s)
Public bug reported:
Steps to reproduce:
1) Install multipass.
2) `multipass launch
http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img
-n reproducer`
3) `multipass shell reproducer`
4) `ubuntu-bug apport` (I also tried `ubuntu-bug cloud-init` and
Public bug reported:
Steps to reproduce:
1) Install multipass.
2) `multipass launch
http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img
-n reproducer`
3) `multipass shell reproducer`
4) `ubuntu-bug cloud-init`
Expected behaviour:
Usual bug reporting
Moved back to New, because this is happening in normal cloud-init
operation.
** Changed in: util-linux (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
Hi Nicklas,
Thanks for the extra info! This sounds like an issue with blkid (and/or
your system), rather than a cloud-init bug. I've added a util-linux bug
task (which is the package that ships blkid), and I'm going to mark the
cloud-init bug task Invalid as I don't believe that there's
Yes, at the time I had an upstream kernel installed. The Nvidia drivers
were installed for _that_ kernel, but I booted onto the most recent
Ubuntu archive kernel instead. DKMS didn't build/install the drivers
for that kernel for some reason, so they weren't available to load, but
that didn't
I fixed this by getting my system to boot with the correct drivers, so I
can't easily do any further testing, I'm afraid.
I'll mark this as Incomplete.
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: New => Incomplete
** Changed in: systemd (Ubuntu)
Status: New =>
/lib/udev/rules.d/71-nvidia.rules is definitely involved in this
somehow; I'm seeing nvidia-persistenced started/stopped repeatedly too,
and that's driven by that rules file.
** Also affects: nvidia-graphics-drivers-440 (Ubuntu)
Importance: Undecided
Status: New
--
You received this
Public bug reported:
I'm seeing these lines repeated:
```
Dec 09 12:01:45 surprise systemd-udevd[731]: nvidia: Process
'/usr/bin/nvidia-smi' failed with exit code 9.
Dec 09 12:01:46 surprise systemd-udevd[731]: nvidia: Process '/sbin/modprobe
nvidia-modeset' failed with exit code 1.
Dec 09
(The system booted up using nouveau, which is why the Nvidia drivers
won't load.)
--
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/1855747
Title:
systemd-udevd appears to
Hi!
I believe this is an issue with ifupdown, rather than cloud-init. As
such, I've added an ifupdown task and marked cloud-init's task as
Invalid. If it's determined that we won't fix this in ifupdown, then
please move the cloud-init task back to New and we can consider working
around this in
Public bug reported:
I'm currently debugging something based on journal output. I,
helpfully, know what kernel was running due to this line:
kernel: Linux version 5.3.0-13-generic (buildd@lgw01-amd64-012) (gcc
version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #14-Ubuntu SMP Tue Sep
24 02:46:08
Public bug reported:
I started seeing this when I booted this morning, and I've seen it in
the 2 reboots since (one for a new kernel, one to capture debug logs).
After modifying /etc/udev/udev.conf to capture debug logging, I see:
$ journalctl -u systemd-udev-settle.service -b0
-- Logs begin at
The lack of events is not the issue. We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.
The problem is that if udev processes the sda1 event first then, at
least some of
I don't think we're looking for a way to wait for udev. For this bug to
present, udev has to have processed all of the available events (i.e.
there's nothing left to wait for), and have done so incorrectly
(probably as a result of its interaction with the Azure kernel, as this
doesn't reproduce
Dan, are you asking for that to get more debugging information, or are
you suggesting that as a fix for this?
(I'm yet to be convinced that this isn't a regression in (the
kernel|src:systemd), so I don't think that we should have to run _any_
additional commands to address this.)
--
You
On Mon, Aug 26, 2019 at 08:58:46AM -, Tobias Koch wrote:
> > (Odds are that whatever causes it to be recreated later in boot would be
> > blocked by cloud-init waiting.)
>
> But that's not happening. The instance does boot normally, the only
> service degraded is cloud-init and there is no
On Mon, Aug 26, 2019 at 03:17:10PM -, Scott Moser wrote:
> If there is a race, or a need to wait, it almost certainly is in cloud-
> utils (growpart).
I would still like us to get a systemd/kernel person to take a look at
this, because I think that the race is somewhere further down than
On Fri, Aug 23, 2019 at 08:23:06PM -, Tobias Koch wrote:
> I may be missing the point, but the symlink in question is eventually
> recreated, does that tell us anything? This here
Yes, this is more supporting evidence that this is a race condition; the
state of the system both before and some
Looking at the comment timestamps, Dan probably didn't see my comment,
but to reiterate: all the events we expect to be processed _are_
processed, the issue is that when they are processed they don't always
end up with the correct partition information.
--
You received this bug notification
[N.B. I wrote the below before I saw Ryan's comment, so there is some
repetition.]
OK, I've spent some time catching up on this properly so I can
summarise: per comment #24, the issue is that when udev processes the
events emitted by the kernel, it (sometimes) doesn't determine the
correct
to be a systemd issue, I'm going to mark the cloud-
init task Invalid. Feel free to move it back to New if you believe this
is a mistake!)
** Changed in: cloud-init
Status: In Progress => Invalid
** Changed in: cloud-init
Assignee: Dan Watkins (daniel-thewatkins) => (unassigned)
--
You re
That certainly is unorthodox! When you say "copied udevadm", what
specifically do you mean? Just the binary, the udev package, ...?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
Hi Seb,
I'm using i3, and something was starting it during session startup (I
have since used im-config to disable it entirely, as it isn't useful for
me). I could reach that UI by right-clicking on the tray icon,
selecting Preferences, switching to the Input Method tab and pressing
the Add
Public bug reported:
When I attempt to add my standard UK keyboard to the layouts ibus knows
about, I cannot do so.
(See the attached image for the list of available layouts.)
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: ibus 1.5.19-4ubuntu1
ProcVersionSignature: Ubuntu
I don't believe this is a curtin issue; I've marked it as Invalid for
curtin. (Please do set it back to New if this is an error!)
** Changed in: curtin
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
I can also confirm that installing linux-modules-extra-5.0.0-8-generic
(which also pulls in crda iw libnl-genl-3-200 wireless-regdb) caused
this problem to no longer appear.
(I'm happy for this to be marked duplicate, but I wonder if there's
still an iptables bug, given that memory allocation is
Jamie, are you using an ISO install or a cloud image for your test? I
was seeing this in a cloud image.
(When we were debugging on IRC, I recall that being a difference that
meant people couldn't reproduce.)
** Changed in: iptables (Ubuntu)
Status: Incomplete => New
--
You received
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1820114/+attachment/5246239/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1820114/+attachment/5246238/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in
apport information
** Tags added: apport-collected
** Description changed:
I hit this error on disco:
```
$ free -h
totalusedfree shared buff/cache
available
Mem: 478Mi98Mi 311Mi 0.0Ki68Mi
366Mi
Public bug reported:
I hit this error on disco:
```
$ free -h
totalusedfree shared buff/cache available
Mem: 478Mi98Mi 311Mi 0.0Ki68Mi 366Mi
Swap:0B 0B 0B
$ sudo iptables -S
iptables
Added linux as there's a suspicion that this is a linux 5.0 regression,
as this only started appearing in our automated testing in the days
since that landed.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to iptables in
Is this still an issue that needs cloud-init work?
** Changed in: cloud-init
Status: New => Incomplete
--
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/1732522
Title:
** Description changed:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to
Public bug reported:
Currently, if an Ubuntu developer (or their code) is attempting to
interact with the precise archive (which is still supported in some form
via ESM) from a machine running bionic or later, they will run in to
issues verifying signatures, because the keys used to sign the
Public bug reported:
I use more than one browser profile, only one of which is logged in to
Launchpad. When using ubuntu-bug to report a bug, it will open the page
in whichever one happened to be focused last. If this browser profile
isn't logged in to Launchpad, it will redirect me to a login
Public bug reported:
This means that software installed via snap isn't transparently
available for units to use. As snaps are first-class citizens in
Ubuntu, we should update the PATH.
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
Public bug reported:
In our testing of cloud images, we intermittently see an error along the
lines of:
May 09 17:59:27 ubuntu setupcon[476]: /bin/setupcon: 809: /bin/setupcon:
cannot open /tmp/tmpkbd.7L3GEu: No such file
This only happens from time-to-time which suggests that it's a race
The attached `systemd-analyze plot` output suggests that console-setup
ran at the same time as the systemd-tmpfiles-setup service, so I wonder
if this is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=846256
** Attachment added: "plot.svg"
On Thu, Mar 08, 2018 at 04:30:30PM -, Scott Moser wrote:
> I'm pretty sure that if you you rm /etc/resolv.conf
> and then just write what ever you want in there, it wont get overritten.
>
> mv /etc/resolv.conf /etc/resolv.conf.dist
> echo "nameserver 8.8.8.8" > /etc/resolv.conf
Apologies, I
Public bug reported:
(Such as during image builds.)
** Affects: systemd (Ubuntu)
Importance: Undecided
Assignee: Dimitri John Ledkov (xnox)
Status: New
** Tags: amd64 apport-bug bionic
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
On Wed, Mar 07, 2018 at 11:42:29PM -, Jason Hobbs wrote:
> Is there a workaround for this? I can just rm /etc/resolv.conf and
> create it with the contents I want, right?
Yep, though you'll need to recreate it every so often as it will be
replaced.
--
You received this bug notification
Oops, removed the rest of my comment when pasting; I'm also seeing this
issue, but on a wireless interface.
--
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/1751797
Title:
$ nmcli device show wlp3s0 | pastebinit
http://paste.ubuntu.com/p/xJ6YjD8WQ9/
$ systemd-resolve --status | pastebinit
http://paste.ubuntu.com/p/bPDMzY3sYh/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Attachment added: "20180222_133958.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751120/+attachment/5060610/+files/20180222_133958.jpg
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
Public bug reported:
My mouse cursor would still move, but I couldn't do anything.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
1 - 100 of 145 matches
Mail list logo
