Public bug reported:
I'm trying to disable FIPS from an Ubuntu Pro FIPS 18.04 image in AWS. I
updated to the latest ua client in the daily PPA. I have a prompt to
disable it but it fails:
ubuntu@ip-172-31-60-238:~$ sudo add-apt-repository ppa:canonical-server
/ua-client-daily
ubuntu@ip-172-31-6
wrong project
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1916773
Title:
ua disable fips doesn't work in ua client 27
Status in ifupdown package in Ubuntu:
Invalid
I tested the systemd 229-4ubuntu21.11 package from xenial-proposed in
Ubuntu 16.04 in KVM and also confirm I cannot reproduce the issue with
this updated package:
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.5 LTS
Release:16.04
Codename
I confirm the "toram" workaround from Woodrow allows me to PXE netboot
the most recent Ubuntu 18.04 Desktop amd64 ISO image.
--
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/17
Hi Ivan. Can you post steps to reproduce this issue? Or at least steps
to get a similar environment running to get familiar with this bug? (for
those who are not familiar with HDInsight). Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
Hi Ivan. I'll have to learn about HDInsight then. I was hoping to get a
list of steps I can follow to fast track the learning process. I'll see
what I can do this week. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to s
Hi Ivan,
I launched an Hadoop HDInsight cluster in Azure and I see it runs on 6
nodes (2 head nodes and 4 worker nodes). Are those nodes the kind of
nodes that this issue is about? If so, is there a way I can have access
to those nodes or is it intentionally blocked for Azure users?
In any case,
There is a similar situation where apt-get wants to remove packages when
strict dependencies (equal version number) cannot be met. For example
dovecot-core/dovecot-pop3d/dovecot-imapd.
After installing Ubuntu 16.04.3 LTS from the ISO, install the 3 packages
from the release pocket:
$ sudo apt ins
Hi Ivan, the best way to engage Canonical Support to get assistance with
this issue will be to file a support case on support.canonical.com and
attach an sosreport of the affected system that is collected when the
issue happens. See my previous comment #5 for the details of sosreport.
Please check
I tested friendly-recovery 0.2.31ubuntu2 in Xenial/16.04.3 LTS.
Selecting network Enable networking" from the Recovery Menu now enables
the network and DNS successfully. I can "cat /etc/resolv.conf" vs before
I couldn't. I don't see any issues with dependencies or asking for tty-
ask-password or a
I confirm the workaround works for me:
Before:
root@ubuntu:~# cat /etc/fstab
/dev/mapper/vg00-rootvol / ext4errors=remount-ro 0 1
/dev/mapper/vg00-varvol /varext4defaults0 2
/dev/mapper/vg00-swap noneswapsw 0
I tested the fix from ppa:inaddy/lp1718966 and I am now able to install
snaps on my two test systems without using the /etc/fstab workaround,
one with LVM and one without. Both systems have /var isolated. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seede
I installed isc-dhcp-client-noddns from trusty-proposed and I don't get
the two random extra high ports anymore:
Before:
# dpkg -l | grep isc-dhcp-
ii isc-dhcp-client 4.2.4-7ubuntu12.9 amd64
ISC DHCP client
ii isc-dhcp-common 4.2.4-7ubun
** Changed in: upstart (Ubuntu)
Assignee: Ahmad Bin Musa (ahmadbinmusa) => (unassigned)
--
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/1303769
Title:
xubuntu 14.04 se
I just hit this bug with a fresh install of Ubuntu 14.04.4 Desktop.
Inside Unity, I open a terminal and if I do "service ssh status" I get:
status: Unknown job: ssh
But if I ssh to that box with the same user, the same command works
fine.
The workarounds are to do "sudo service ssh status" or to
I confirm I have the same behavior in Ubuntu 14.04.5 LTS with isc-dhcp-
client version 4.2.4-7ubuntu12.7
I recompiled the isc-dhcp-client with the fix from
http://forums.debian.net/viewtopic.php?f=10&t=95273 and I no longer have
the issue:
BEFORE:
root@trustydhclient:~# lsof -i udp
COMMAND PID
Public bug reported:
I have an issue that is similar to the following bugs:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574347
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1422143
I am running Xenial 16.04.1. I did an apt-get dist-upgrade on July 29th
2016 and rebooted
Public bug reported:
The command "shutdown -r +5" doesn't work in a xenial lxc container. I
found this out by trying to use Landscape to restart a xenial lxc
container and the operation failed. I was told by the Landscape team
that the restart button simply does a "shutdown -r +5".
The problem se
18 matches
Mail list logo
