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
The issue seems to be fixed in the final 16.04 release. I downloaded
Xenial today (April 21st 2016, release day) and I cannot reproduce the
issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1553652
I would like to add that the Linux Action Show podcast spoke about this
issue on their episode 413 where they review 16.04. They say they had to
manually partition the drive to workaround this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I also get this bug.
I got it when trying to install 16.04 development branch (files on the
USB thumb drive are from April 16th 2016) over an existing 14.04 HDD.
I then replaced the HDD with a brand new SSD (with no partitions on it)
and installed that same 16.04 version with no issues.
And I
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
** Changed in: upstart (Ubuntu)
Assignee: Ahmad Bin Musa (ahmadbinmusa) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303769
Title:
xubuntu 14.04 service start,stop, does not
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
I have the same problem:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.1 LTS
Release:16.04
Codename: xenial
$ dpkg -l | egrep 'juju|bash'
ii bash 4.3-14ubuntu1.1
amd64
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=95273 and I no longer have
the issue:
BEFORE:
root@trustydhclient:~# lsof -i udp
COMMAND PID
Public bug reported:
Please backport collectd 5.5 or SMART plugin to Trusty.
Reason for the backport:
Only collectd 5.4 is available for Trusty and the SMART plugin [1] (to collect
SMART statistics from disk drives) was added only in collectd 5.5 [2].
Other possible
Hi Andreas,
How is the new Trusty landscape-client version coming along?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1636477
Title:
Update trusty with landscape-client 16.03
To manage
** Description changed:
- Install 14.04.5 hwe-t on a node using maas, then install cpufreqd and
cpufrequtils.
+ Install 14.04.5 hwe-t on a node using maas, then install cpufreqd and
cpufrequtils.
Then run sudo /etc/init.d/loadcpufreq start .
- Fails to start. This happens on an AT
Completed tests from https://wiki.ubuntu.com/LandscapeUpdates:
-upgrade test from previous distribution to the current one. If the
current distribution is an LTS one, the upgrade path from the previous
LTS distro must also be exercised. --> Success (added trusty-proposed to
sources.list before
docker.py
** Affects: sosreport (Ubuntu)
Importance: Undecided
Assignee: David Coronel (davecore)
Status: New
** Affects: sosreport (Ubuntu Trusty)
Importance: Undecided
Assignee: David Coronel (davecore)
Status: New
** Affects: sosreport (Ubuntu Xe
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
** Changed in: sosreport (Ubuntu Trusty)
Assignee: (unassigned) => David Coronel (davecore)
** Changed in: sosreport (Ubuntu Xenial)
Assignee: (unassigned) => David Coronel (davecore)
** Changed in: sosreport (Ubuntu Yakkety)
Assignee: (unassigned) => David Coronel
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
Bugs,
I tested upgrading the new landscape-client on artful, zesty, xenial and
trusty from the current most recent landscape-client version currently
available in each release. I didn't test this particular fix but I
confirm the package upgrade works fine and the client runs fine
afterwards.
--
You
I tested upgrading the new landscape-client on artful, zesty, xenial and
trusty from the current most recent landscape-client version currently
available in each release. I didn't test this particular fix but I
confirm the package upgrade works fine and the client runs fine
afterwards.
--
You
I tested this fix on the new versions of trusty, xenial, zesty and
artful and it works as expected (defaults to no):
Request a new registration for this computer now? [y/N]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested upgrading the new landscape-client on artful, zesty, xenial and
trusty from the current most recent landscape-client version currently
available in each release. I didn't test this particular fix but I
confirm the package upgrade works fine and the client runs fine
afterwards.
--
You
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-failed verification-failed-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732206
Title:
My last comment #5 still stands. My tests show that this fix works for
the cloud image of Ubuntu, but there are use cases where users need the
nvidia drivers for GPU processing but are not running a display manager
on the machine. In such a case, the display-manager.service systemd
service will
Public bug reported:
This is a request to make a change in the hv-kvp-daemon systemd service
which is part of the linux-cloud-tools-common package to ensure the hv-
kvp-daemon service starts before the walinuxagent service. The default
dependencies make hv-kvp-daemon wait until the whole system
I tested this in a VM using the default xenial cloud image (ie. "uvt-kvm
create xenialoem release=xenial").
With the current nvidia-384 384.90-0ubuntu0.16.04.2 package, the nvidia
dkms module doesn't get built after the reboot:
$ sudo apt update
$ sudo touch /tmp/do_not_build_dkms_module
$ sudo
I also confirm the kernel 4.4.0-104.127 in xenial-proposed fixes the
issue. I am able to mount my CephFS filesystem normally. Benjamin also
confirmed the kernel works for him in comments #26 and #27. I am
changing the tag to verification-done-xenial. Thanks!
** Tags removed:
Marked as Fix Released. I tested this on snapd 2.29.4.2~14.04 and works
as expected.
** Changed in: snapd
Status: Fix Committed => Fix Released
** Changed in: snapd (Ubuntu Trusty)
Status: New => Fix Released
** Changed in: snapd (Ubuntu)
Status: New => Fix Released
--
** Also affects: snapd (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/1721518
Title:
Latest snapd in Trusty is broken after reboot because of
Public bug reported:
The nvidia-graphics-drivers (https://github.com/tseliot/nvidia-graphics-
drivers/tree/375-xenial) deferred DKMS feature does not work in xenial.
With upstart, doing a touch of the /tmp/do_not_build_dkms_module file
indicates to defer building the kernel modules, then install
Public bug reported:
The floppy module tries to probe for a floppy device but fails. This
adds on average 7 seconds of boot time to Ubuntu (all versions). It's a
trivial fix to blacklist the module.
$ echo "blacklist floppy" | sudo tee /etc/modprobe.d/blacklist-floppy.conf
$ sudo
The new plan is to remove the floppy device from the GCP kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729673
Title:
Blacklist floppy module to increase boot performance
To manage
Hi Joseph,
I'm able to reproduce Benjamin's original issue with kernel
4.4.0-103-generic #126-Ubuntu:
# mount -t ceph :6789:/ /mnt/mycephfs -o name=admin,secret=
mount error 5 = Input/output error
I don't get this problem with 4.4.0-101-generic #124-Ubuntu. I'm working
with Jay Vosburgh to test
I forgot to mention that I was still able to reproduce the bug with the
kernel you built with a revert of commit ff467fd from
http://kernel.ubuntu.com/~jsalisbury/lp1737033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On the running system after you rollback to the previous kernel, can you
paste your /etc/fstab for the filesystems that failed to mount and the
corresponding lines from mount -v? I assume the issues are with nfshome
and officeshare:
cat /etc/fstab | grep -i -e nfshome -e officeshare -e
** Attachment added: "Screenshot bug 1531150.png"
https://bugs.launchpad.net/landscape-client/+bug/1531150/+attachment/5018292/+files/Screenshot%20bug%201531150.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested this fix on trusty, xenial, zesty and artful. I followed the
test case in the description. I confirm I see the hash-id download and
apt update run messages.
One small note, on artful I get the following:
2017-12-04 14:50:20,311 WARNING [MainThread] Couldn't download hash=>id
database:
I tested a kernel without the following commits from
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1728739 and I was
able to mount the CephFS filesystem successfully:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/commit/?id=f14ca6ac3b198f30ee138f02c3c7d380d165736e
FYI, this patch seems to have introduced a regression, see
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737033
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728739
Title:
Attempt to map
Public bug reported:
Using an Ubuntu Server 16.04-based host with KVM hypervisor installed,
we are unable to launch a vanilla Ubuntu Server 16.04.4 guest with >= 32
PCIe devices. It is 100% reproducible. Using fewer PCIe devices works
fine. We are using the vanilla kvm and qemu packages from the
** Changed in: qemu (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1769053
Title:
Cannot start a guest with more than 1TB of RAM
To manage
** Changed in: qemu (Ubuntu)
Importance: Critical => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage
** Changed in: qemu (Ubuntu)
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To manage
@Khaled El Mously: It's more a feature request.
** No longer affects: qemu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
Not able to passthrough > 32 PCIe devices to a KVM Guest
To
I removed upstream QEMU from this bug pending further analysis and so we
can go through the right channels if this needs to go upstream.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771238
Title:
@Marcelo, I have a reply from Madhuri:
Created By: Madhuri Kaniganti (portal) (07/06/2018 11:40 AM)
Just these two fixes needed:
IB/mlx5: Respect new UMR capabilities
I have confirmation from a user running NFS stress tests on Xenial with
this kernel and has not seen any issues. Changed tag to verification-
done-xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a
Marking bug as invalid as it looks like the root of the issue was with
the user's own module.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755863
Title:
netbooting
Created By: David Coronel (28/05/2018 4:28 PM)
Good day Sam, Jamie,
The kernel 4.4.0-128-generic #154 is now ready for testing by Nvidia:
linux | 4.4.0-128.154 | xenial-proposed | source
linux-image-4.4.0-128-generic | 4.4.0-128.154 | xenial-proposed | amd64, arm64,
armhf, i386, ppc64el, s390x
I have confirmation from the user who reported this that they have
tested the new kernel 4.4.0-128.154 in their test environment for a 24
hours stress test and could not reproduce the issue. I changed the tag
to verification done.
** Tags removed: verification-needed-xenial
** Tags added:
@Tomasz: The d-i based install image is "the traditional installer found
on the alternative downloads page" as you can read from the Download
Ubuntu Server 18.04 page[1][2][3]:
Alternative Ubuntu Server installer
If you require advanced networking and storage features such as; LVM, RAID,
** Description changed:
[Impact]
The docker plugin in sosreport doesn't collect informations for Ubuntu.
In docker.py for the Ubuntu Plugin, the docker command is set to
'docker.io'[1] which seems to be a old workaround that has been
removed[2], thus the docker plugin is no longer
There was a problem with my initial test case. The test case originally
said :
===
# Look in "/path_to_sosreport/sos_commands/docker/" and note that all files are
empty with "0" size.
===
This is incorrect and was caused by installing the docker package which
has
Public bug reported:
[Test case]
1. Ubuntu 16.04, boot to desktop
2. Turn on "Auto-hide the Launcher" from System Settings -> Appearance ->
Behavior
3. Choose reveal location as Left side
4. Adjust the reveal sensitivity to High
5. Try to move the pointer to the defined hot spot(left side) with
I tested Eric's fix on a Digital Ocean droplet with 2 GB Memory and 40
GB Disk with Ubuntu 17.10 upgraded to Bionic with do-release-upgrade -d
(because Bionic images are not available)
==
root@ubuntu-2gb-tor1-01:~# cat /sys/class/dmi/id/sys_vendor
DigitalOcean
I tested Eric's fix on Bionic on t2 and c5 instances:
==
AWS t2 instance with community bionic AMI ubuntu/images-testing/hvm-ssd
/ubuntu-bionic-daily-amd64-server-20180101 (ami-c55c16bf)
ubuntu@ip-172-31-48-172:~$ cat /sys/class/dmi/id/sys_vendor
Xen
ubuntu@ip-172-31-48-172:~$ dpkg
Public bug reported:
Add support for 4/6/8 channel sound in 16.04 LTS kernel for future GPUs.
This commit should be what is needed:
https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git/commit/?id=74ec118152ea494a25ebb677cbc83a75c982ac5f
ALSA: hda - Add missing NVIDIA GPU codec IDs to
I tested the packages in trusty, xenial, zesty and artful. The Docker
plugin runs well and gathers the expected information for Docker:
===
Trusty
root@trustysosreport:/tmp/sosreport-trustysosreport-20180115193757# ls
sos_commands/docker/
docker_images
I tested installing the new package in trusty, xenial, zesty and artful
in LXD containers. I ran sosreport with the -a option and I didn't
notice any errors. Made a few spot checks. LGTM.
===
Trusty
# dpkg -l | grep -i sosreport
ii sosreport 3.5-1~ubuntu14.04.1 amd64 Set of tools
** Attachment added: "highcontrast-icontheme-systemsettings.png"
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1644662/+attachment/5039569/+files/highcontrast-icontheme-systemsettings.png
--
You received this bug notification because you are a member of Ubuntu
Bugs,
It looks like after switching to the HighContrast theme in Appearance,
'Adwaita' is being set as the icon theme in dconf. We think it's not
Adwaita that should be used, but rather the HighContrast icon theme.
You can use the unity-tweak-tool to change the icon theme to
highcontrast and notice
** Attachment added: "aws-c5-xenial.png"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1742531/+attachment/5043540/+files/aws-c5-xenial.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "aws-c5-trusty.png"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1742531/+attachment/5043539/+files/aws-c5-trusty.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "aws-c5-artful.png"
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1742531/+attachment/5043541/+files/aws-c5-artful.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested that the new landscape-client package installs on AWS C5
instances with trusty, xenial and artful and registers in Landscape with
the right information. Attaching screenshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "digitalocean-trusty.png"
https://bugs.launchpad.net/landscape-client/+bug/1743232/+attachment/5043542/+files/digitalocean-trusty.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "digitalocean-xenial.png"
https://bugs.launchpad.net/landscape-client/+bug/1743232/+attachment/5043543/+files/digitalocean-xenial.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I tested that the new landscape-client package installs on Digital Ocean
droplets with trusty, xenial and artful and registers in Landscape with
the right information. Attaching screenshots.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: "digitalocean-artful.png"
https://bugs.launchpad.net/landscape-client/+bug/1743232/+attachment/5043544/+files/digitalocean-artful.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: "The error after pressing Cancel in the OEM mode"
https://bugs.launchpad.net/ubuntu/+bug/1749289/+attachment/5054597/+files/oem-error.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Pressing Cancel during Ubuntu 16.04.3 Server installation after OEM
install and after running oem-config-prepare aborts the installation.
The behaviour is different from a regular Ubuntu 16.04.3 Server
installation (without OEM) where the option at the bottom is "Go Back"
** Attachment added: "The different options between OEM and regular
installation"
https://bugs.launchpad.net/ubuntu/+bug/1749289/+attachment/5054598/+files/oem-vs-regular.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The themes available via the Appearance panel seem to be hardcoded in
the unity-control-center source code:
unity-control-center/panels/appearance/cc-appearance-panel.c:
static gchar *themes_id[] = { "Adwaita", "Ambiance", "Radiance", "HighContrast"
};
static gchar *themes_name[] = { "Adwaita",
*** This bug is a duplicate of bug 1100670 ***
https://bugs.launchpad.net/bugs/1100670
Hi Raymond.
We talked about this issue directly and what you really are hitting is
this bug:
https://bugs.launchpad.net/ubuntu/+source/unity-control-
center/+bug/1100670
The behaviour you are seeing here
** Attachment added: "netboot-pxe-issue.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1750597/+attachment/5059018/+files/netboot-pxe-issue.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
When doing a PXE netboot of Ubuntu Desktop over NFS, the installer adds
the following lines for each network interface to
/etc/network/interfaces (I think this is to keep the root fs available
during the live session):
auto ens3
iface ens3 inet manual
I was able to
** Attachment added: "netboot-pxe-issue-after-workaround.png"
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1750597/+attachment/5059019/+files/netboot-pxe-issue-after-workaround.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have information that the original Desktop team confirmed that
limiting the themes available via the Appearance panel was a design
choice. They decided to create a "whitelist" of themes known to look in
an acceptable way.
I don't think this will change in Unity in the future. I suggest we
close
I also confirm I tested the new gnome-themes-standard and gnome-
accessibility-themes packages from -proposed in artful and xenial and it
fixes the issue with the missing icons.
xenial:
gnome-themes-standard | 3.18.0-2ubuntu2
gnome-accessibility-themes | 3.18.0-2ubuntu2
artful:
I confirm this issue still exists when doing a PXE netboot of Ubuntu
16.04 Desktop and also with a PXE netboot of an Ubuntu 18.04 LTS (Bionic
Beaver) Desktop Daily Build.
I also use the workaround to comment out the all the interfaces in
/etc/network/interfaces except the loopback adapter and the
Public bug reported:
Request to pull this patch from upstream into the next 4.15 kernel
update:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=b2adf22fdfba85a6701c481faccdbbb3a418ccfc
This fixes a regression in SMB 2/3 reconnect detection. The fix has been
I have confirmation from a user who has done verification for this
kernel. Changing to verification-done-bionic.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
This request is to pull in the following patch for NVMe bug from
https://lore.kernel.org/patchwork/patch/974880/ in the linux-gcp kernel:
===
This patch adds full memory barrier into nvme_dbbuf_update_and_check_event
function to ensure that the shadow doorbell is written
** Description changed:
+ [Impact]
+
Pressing Cancel during Ubuntu 16.04.3 Server installation after OEM
install and after running oem-config-prepare aborts the installation.
The behaviour is different from a regular Ubuntu 16.04.3 Server
installation (without OEM) where the option at
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
Bugs, which is subscribed
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
Bugs, which is subscribed to Ubuntu.
Hi Hans. I'd like to be able to reproduce the issue. I tried booting an
Ubuntu 18.04 instance twice in Azure but I couldn't reproduce the issue.
Do you have an idea how I could reproduce this?
This type of error usually happens when your system can't find the
package in its APT sources. Is it
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have confirmation that the kernel in -proposed fixes the issue in
xenial.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
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,
Screenshot of the compizconfig-settings-manager Unity launcher settings
** Attachment added: "compizconfig-settings-manager-launcher.png"
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1743422/+attachment/5037922/+files/compizconfig-settings-manager-launcher.png
--
You received this
Public bug reported:
Impact: linux-azure needs to add support for secure boot to support
Hyper-V Generation 2 Virtual Machines.
Fix: UEFI support needs to be enabled for linux-azure and new signed
package needs to be created it for that.
Testcase: After installing the new linux-azure kernel
@Marcelo, Josh requested that these patches be backported to the 4.13
azure kernel:
"[...]Since 4.13 needs to be the default until the 26th, could we get
them added to the 4.13 kernel?"
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Subscribed Canonical Kernel Distro Team to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763456
Title:
Disable nouveau driver in linux-azure kernel
To manage notifications about this
Public bug reported:
nouveau driver updates causing problems with other kernels with
provisioning on GPU instances in Azure.
This is a request to disable the nouveau driver from the linux-azure
kernel.
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Status: New
--
You
Netbooting Ubuntu Desktop is not a supported installation method for
Ubuntu. The only supported way to install Ubuntu via netboot is with the
Netboot images of Ubuntu[1]. More information in the Ubuntu
documentation[2].
[1] http://cdimage.ubuntu.com/netboot/
[2]
Josh gave this answer to Marcello's question "Just to confirm. It's not
necessary to include these config changes to the 4.13 azure kernel in
xenial, correct?":
--> 'No, this is upcoming new hardware in Azure and I'd prefer to keep
new feature work in 4.15.'
--
You received this bug
I tested the test package for Xenial in ppa:dgadomski/ubiquity-lp1749289
and it gives me a choice instead of failing now. After pressing Cancel
on the first screen, I get:
Your system is not yet configured. Press 'a' to try again, 's' for a recovery
shell, or 'r' to reboot.
[asr]
I did an OEM
1 - 100 of 170 matches
Mail list logo
