Public bug reported:
In minimal images, rsyslog is not installed by default; this means that
sshguard will fail to start if installed.
** Affects: sshguard (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I have built an image from -proposed and the .tar.xz was included in the
output; verification done.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
This is still present in bionic (gnome-shell 3.28.2-0ubuntu0.18.04.1).
** Changed in: gnome-shell (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/1734759
That change hasn't yet landed in the cosmic archive, so isn't yet
suitable for SRU to bionic.
This new hook will get updated along with all the other tarball
generation when the xattrs change is backported.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached is the debdiff to reintroduce the tarball for bionic.
** Patch added: "bionic-1585233.debdiff"
https://bugs.launchpad.net/cloud-images/+bug/1585233/+attachment/5171264/+files/bionic-1585233.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi shatun,
On Sun, Jul 22, 2018 at 09:15:53AM -, shatun wrote:
> Any chance this will be assigned and fixed any time soon?
This work is in-progress at the moment; you can see the artifacts are
now being produced for cosmic[0]. The next step is a backport to
bionic, which I would anticipate
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Dan Watkins (daniel-thewatkins)
** Changed in: livecd-rootfs (Ubuntu)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
In live-build/functions, clean_loops calls `unset backing_img`; if you
call clean_loops again, the "if [ -n "${backing_img}" ]; then" line then
causes the script to exit if you're running with `set -u`.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
I believe the attached patch does the trick; I'll submit it as a branch
once my current branch has landed.
** Patch added: "1775472.patch"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1775472/+attachment/5149495/+files/1775472.patch
--
You received this bug notification
Public bug reported:
We have explicit release gating in place, which can be relaxed now that
linux-kvm will exist in non-LTS releases.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
Status: New
--
You received this bug
I can confirm that the new module isn't signed at all:
$ hexdump -Cv /lib/modules/4.15.0-22-generic/updates/dkms/vboxdrv.ko | tail -n
100 | pastebinit
http://paste.ubuntu.com/p/BFSg9DsqR8/
Contrast with a previous kernel that was installed when virtualbox was
last upgraded:
$ hexdump -Cv
term.log for installation of my current kernel:
https://paste.ubuntu.com/p/3TVVFpFSNX/
term.log from the last time I see virtualbox DKMS stuff happening:
https://paste.ubuntu.com/p/7f7p6t48pn/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
At my last reboot, I was prompted to enable SecureBoot, so I did.
When I booted, however, I noticed that the virtualbox service failed to
start because it couldn't load its kernel module. If I attempt the same
thing, I see that there's an issue with keys:
$ sudo modprobe
I suspect fixing
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1771858 would fix
this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1772107
Title:
/snap/bin is not in path when executing
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
We've only seen this on m1.small instances, but we haven't tested
exhaustively (we do know, though, that m3.large is fine).
The command used to create the instance was:
aws --profile=china --region=cn-north-1 ec2 run-instances --key-
name=Odd_Bloke --image-id=ami-8fcd13e2 --security-groups
Public bug reported:
We're observing the following panic on boot when trying to boot an
m1.small in cn-north-1 (which is a region in AWS China):
[2.271681] Hardware name: Xen HVM domU, BIOS 3.4.3.amazon 11/11/2016
[2.271681] RIP: 0010:__xen_evtchn_do_upcall+0x24/0x80
[2.271681] RSP:
The -updates version produces the same content as the -proposed version
for non-minimized builds.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
I have just performed two livefs builds using the proposed version (i.e.
2.408.30), one with the minimized subproject and one without.
In the minimized image, /etc/default/locale contains "LANG=C.UTF-8". In
the non-minimized image, it contains "# File generated by update-
locale".
This looks
I'm going to perform verification of this now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759003
Title:
cloud-init fails for minimal images (can't find locale-gen)
To manage notifications
As we have preseeded snaps in bionic, we'll want this SRU'd there (at
least).
** 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.
If we consider iproute2 to be essential to a functioning Ubuntu then,
you know... ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770395
Title:
Missing dependency on iproute2
To manage
I don't think we need to make a change in the minimal cloud images; this
(and similar bugs) should be fixed in the packages that have the bug.
(Leaving this open for cloud-images so we can ensure that we handle
rolling out the fix once it's in the lxd packaging.)
--
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"
There isn't currently a systemd target that indicates that snapd has
completed its preseeding, so cloud-init can't be ensuring that they are
available like that. Does cloud-init do something specific to confirm
that pre-seeding has been completed before the user script point?
(Note that
This bug is effectively just tracking the upstream Python 3 work
landing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1766292
Title:
samba-tool depends on Python 2
To manage notifications about
Ideally, we would be able to configure the images to specify whether or
not they should block on preseeded snaps. We have some cases where
command-line utilities are installed (and so we should block) but others
where only a daemon is started (where there is limited utility in
blocking).
--
You
Public bug reported:
With some cloud software being moved to snaps, cloud-init needs to
ensure that snaps have been preseeded before user scripts are run, as
those user scripts may rely on the software within the snap being
available for use.
** Affects: cloud-images
Importance: Undecided
Public bug reported:
On VMs launched in Azure, /dev/vmbus/hv_fcopy doesn't exist, so hv-
fcopy-daemon fails to start. This means that boot is degraded by
default:
$ systemctl list-units --failed --no-legend
hv-fcopy-daemon.service loaded failed failed Hyper-V File Copy Protocol Daemon
$
Public bug reported:
As Ubuntu images now all ship with Python 3 only, this is what causes
Python 2 to be included when samba is installed.
(We are, specifically, seeing this issue in the Azure cloud images.)
** Affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
You
Public bug reported:
This is for consistency with the behaviour of `snap prepare-image`.
(This would also avoid writing out more than a single model assertion,
which would be an error anyway.)
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Status: New
--
You received
Public bug reported:
If you unthinkingly run it as a regular user, you get an oblique error
message:
$ unminimize
This system has been minimized by removing packages and content that are
not required on a system that users do not log into.
This script restores the content and packages that are
** Information type changed from Private to Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1759412
Title:
mutt crashed with SIGSEGV in tcache_get()
To manage notifications about this bug go
I've built images from -proposed and confirmed that the behaviour as as
expected.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Attached a xenial MP after it was pointed out to me that we have a
branch for xenial's livecd-rootfs.
** Branch linked: lp:~daniel-thewatkins/livecd-rootfs/minimized-skips-
xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've tested both the attached bionic branch and the attached xenial
debdiff from a PPA.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757223
Title:
ubuntu-cpc: Don't build minimized artifacts that
Attached debdiff that addresses this in xenial.
** Patch added: "1757223.debdiff"
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1757223/+attachment/5085243/+files/1757223.debdiff
** Branch linked: lp:~daniel-thewatkins/livecd-rootfs/minimized-skips
--
You received this bug
Nominated for xenial; minimized images are only produced for
{xenial,bionic}, so that's sufficient.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757223
Title:
ubuntu-cpc: Don't build minimized
ecd-rootfs (Ubuntu)
Importance: Undecided
Assignee: Dan Watkins (daniel-thewatkins)
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/1757223
Title:
ubuntu-cpc: Don't build
Public bug reported:
I'm seeing this in syslog via the serial port:
Mar 20 15:02:42 ubuntu cloud-init[817]: Traceback (most recent call last):
Mar 20 15:02:42 ubuntu cloud-init[817]: File
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 655, in
status_wrapper
Mar 20 15:02:42
** Changed in: cloud-images
Status: In Progress => 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/1755965
Title:
util.subp regression: no longer accept commands as string
To
I'm keeping an eye on the build system to ensure we get a good daily
out.
** Also affects: cloud-images
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => In Progress
** Changed in: cloud-images
Assignee: (unassigned) => Dan Watkins (
$ snap info
snap2.32+18.04~pre5
snapd 2.32+18.04~pre5
series 16
ubuntu 18.04
kernel 4.15.0-12-generic
$ snap run --strace spotify
error: exit status 1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm seeing this with the Spotify snap using snapd 2.32+18.04~pre5 on
bionic; the Slack snap launches fine.
** Summary changed:
- Can run any snap on ubuntu 18.04
+ Can't run snaps on Ubuntu 18.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
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
** Also affects: linux-kvm (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/1566468
Title:
systemd-modules-load.service: Failing due to missing
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
** Changed in: cloud-images
Status: In Progress => 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/1747426
Title:
Vagrant <2.x can no longer fetch box metadata from Hashicorp
To
I can't remember the exact details, but I believe that this change was
landed to support a CloudStack deployment that didn't support SSH keys
at all. In my ignorance of the broader CloudStack ecosystem, I assumed
that this was true of all CloudStack deployments, so setting it in the
data source
$ 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
Bugs, which is subscribed to Ubuntu.
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1751797
Title:
dns resolution only works
** Changed in: ubuntu
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/1613677
Title:
[needs-packaging] Package GCE's compute-image-packages
To manage
** 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
Bugs, which is subscribed to 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
I performed the following test in each of a xenial and artful container:
* Launch the container
* Enable -proposed for universe
* apt install vagrant
* vagrant box add 'ubuntu/trusty64'
and confirmed that box download started successfully.
** Tags removed: verification-needed
Ah, OK, I missed the 17.10 part of the original report. IIUC, this can
be closed out as it's not an issue in any supported Ubuntu release?
(If not, please do reopen it!)
** Changed in: cloud-images
Status: Incomplete => Won't Fix
** No longer affects: libdate-manip-perl (Ubuntu)
--
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726818
Title:
vagrant artful64 box filesystem too small
To manage notifications about
Does this affect releases more recent than zesty (which is now EOL)?
** Changed in: cloud-images
Status: New => Incomplete
** Changed in: libdate-manip-perl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: cloud-images
Status: New => In Progress
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1746806
Title:
sssd appears
** Changed in: cloud-images
Status: New => In Progress
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747426
Title:
Vagrant <2.x
** Changed in: cloud-images
Status: Incomplete => 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/1626158
Title:
image won't boot after upgrading to yakkety's 4.8 kernel because
On Wed, Feb 14, 2018 at 08:13:11AM -, Po-Hsu Lin wrote:
> So I think the bug status should be Fix Committed now?
I think this is actually fixed now; can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Po-Hsu,
Could you confirm the serial of the image that you are seeing this in?
Are you able to test older serials to determine when we started seeing
the failure?
Thanks,
Dan
** Also affects: cloud-images
Importance: Undecided
Status: New
--
You received this bug notification
Public bug reported:
I have an external monitor in portrait mode, which means that the top of
my external monitor is substantially above my laptop monitor (which has
the top bar). If I move a window by holding Meta and dragging it from
the bottom, and accidentally let go with the window
The attached photo displays what I end up stuck with.
** Attachment added: "20180207_165829.jpg"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1748029/+attachment/5050935/+files/20180207_165829.jpg
** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)
--
You received this bug
** Description changed:
+ [Impact]
+
+ As of February 2nd, the legacy Vagrant Cloud URLs were disabled by
+ Hashicorp[0], meaning that the versions of vagrant in xenial and artful
+ can no longer fetch Vagrant boxes from the global index (which is a
+ fundamental part of Vagrant use).
+
+
+
So this looks like it may not be an issue in trusty, because I believe
that predates Atlas/Vagrant Cloud in their entirety. I'm preparing
patches for xenial/artful.
** Also affects: vagrant (Ubuntu Artful)
Importance: Undecided
Status: New
** Also affects: vagrant (Ubuntu Xenial)
** Summary changed:
- Error downloading box trusty64 metadata
+ Vagrant <2.x can no longer fetch box metadata from Hashicorp
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747426
Title:
Vagrant
It looks like Hashicorp have discontinued the atlas.hashicorp.com API
endpoints used by the version of Vagrant in every Ubuntu release (in
favour of vagrantcloud.com).
I've confirmed that this is fixed in the version of Vagrant in bionic-
proposed:
# vagrant box add 'ubuntu/trusty64'
==> box:
** Also affects: vagrant (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/1747426
Title:
Error downloading box trusty64 metadata
To manage
This continues to be a real pain in day-to-day. Can we please fix this
gnome-terminal regression?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726439
Title:
Link copied with "Copy Link Address"
Added the cloud-images project so we can more easily track this.
** Also affects: cloud-images
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/1746806
As I mentioned in comment #2, this can be worked around. The issue is
that GDM3 assumes that it can get an inotify watch and degrades
ungracefully when it can't.
** Summary changed:
- After a period of locked inactivity, gdm3 no longer lets me unlock my session
["No space left on device"]
+
On Wed, Jan 17, 2018 at 03:32:32PM -, Scott Moser wrote:
> I'm curious why you would use the .vhd file. Is there something
> specific that you wanted from it *other* than the format of the disk
> image?
The VHD contains Hyper-V-specific customisations (such as the
linux-azure kernel), so
I've followed the steps Chris gave above, and have confirmed that the
vagrant user is the default via SSH. The ubuntu user also exists, and
is in the appropriate groups.
** Tags removed: verification-needed verification-needed-xenial
** Tags added: verification-done verification-done-xenial
--
Public bug reported:
The GCE image build process currently installs gce-compute-image-
packages (amongst others) with --no-install-recommends. We would like
to be able to install Recommends, but including libpam-cracklib on the
image would represent a substantial change in behaviour for users.
snapd has migrated to xenial-updates without this change landing;
unfortunately, that makes snapd uninstallable on powerpc (as that's the
only architecture where it isn't statically compiled). snapd is
installed during image builds, so this migration is currently blocking
powerpc cloud images
We've seen a couple of potential regressions in artful, so we should
hold off on this xenial SRU until we've triaged these:
https://bugs.launchpad.net/cloud-images/+bug/1740176
https://bugs.launchpad.net/cloud-images/+bug/1740178
--
You received this bug notification because you are a member of
The latest xenial daily no longer exhibits this issue.
** Changed in: cloud-images
Status: In Progress => 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/1485685
Title:
Users are
** Changed in: cloud-images
Milestone: y-2016-06-02 => None
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573095
Title:
16.04 cloud image hangs at first boot
To manage notifications about
Public bug reported:
This is causing failures in livefs builds:
RUN: /usr/share/launchpad-buildd/slavebin/in-target buildlivefs --backend=lxd
--series=xenial --arch=powerpc LIVEFSBUILD-118850 --project ubuntu-cpc
--datestamp 20171220 --image-format ext4
Reading package lists...
Building
So the reason that this regressed in xenial is that we've changed the
way in which we build images, and the workaround for this was only being
applied to PV images. I'm now building test images with the workaround
applied to HVM and PV images, to confirm that my reasoning is sound.
** Changed
OK, I think this is actually bug 1485685 (i.e. the problem is grub-
legacy-ec2 rather than grub itself), so I'm removing cloud-images from
this bug and we'll track it over there.
** No longer affects: cloud-images
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1485685
Title:
Users are
** Changed in: cloud-images
Status: New => Confirmed
** Changed in: cloud-images
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1009294
Title:
Grub update
** Also affects: cloud-images
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/1009294
Title:
Grub update breaks automated dist-upgrade scripts on AMI
The testing we perform before a daily makes it out in to the world
includes some basic cloud-init validation (basically "touch /some/file"
in user-data, and checking that happened after boot), so it isn't
failing in all cases.
Diffing the two manifests gives a pretty substantial set of changes:
Public bug reported:
I just accidentally hit Meta-P and was extremely confused by the result.
As I only tapped it, I didn't see the on-screen menu, and my displays
were suddenly configured completely differently (both resolution _and_
orientation).
Furthermore, when I used Meta-P to switch back
Public bug reported:
I know that we effectively repackaged xe-guest-utilities between xenial
and artful. As part of that, the previous dependency on xenstore-utils
was dropped.
This is causing some problems for Xen-based partners/customers, who
would like xenstore-utils installed in their
On Fri, Nov 24, 2017 at 10:23:18AM -, Egmont Koblinger wrote:
> Maybe related to bug 1726262?
It certainly sounds similar and, indeed, I can reproduce that on my
external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can reproduce this on 17.10, but only on my external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1726262
Title:
17.10 - flickering overlay patterns in gnome-terminal
To manage
** Summary changed:
- Ghosting when switching tabs with "Use transparency from system theme"
enabled on an external monitor
+ Ghosting with "Use transparency from system theme" enabled on an external
monitor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
Steps to Reproduce:
1) Open gnome-terminal on an external monitor (or move an existing session
there)
2) Open a second tab
3) Produce some output on the current tab
4) Switch to the other tab
Expected Behaviour:
No ghosting.
Actual Behaviour:
The previous content is
Upon further inspection, this isn't actually a tab-switching issue. Hit
Return a bunch of times, and then Ctrl-L; your prompts will ghost
temporarily. Furthermore, my blinking cursor also ghosts from time to
time.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I can't reproduce this locally, or in an lxd container; are you sure you
don't have a weird local Python environment that could be causing the
issue?
** Summary changed:
- gsutil stacktraces on artful
+ gsutil tracebacks on artful
** Summary changed:
- gsutil tracebacks on artful
+ gsutil
On Mon, Nov 06, 2017 at 11:19:10PM -, ruffsl wrote:
> Could the "current" folder in Index of /core/trusty at https://partner-
> images.canonical.com/core/trusty/ be updated to redirect to 20171102
> instead of 20170817, as it is presently? The docker library ubuntu image
> build is I think
On Thu, Oct 26, 2017 at 03:09:12PM -, Kai-Heng Feng wrote:
> They should work, at least at initramfs stage. You can use the keyboard
> to decrypt rootfs proves that.
I can use the keyboard to decrypt the rootfs if it's plugged in after
boot. If it's plugged in before boot, it doesn't work.
On Thu, Oct 26, 2017 at 07:38:58AM -, Kai-Heng Feng wrote:
> What's the output of `lsusb -t` with and without the monitor USB hub?
Without:
/: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/15p, 480M
|__ Port 6:
501 - 600 of 1128 matches
Mail list logo
