Thank you Seb, I had the issue reported in this bug in a WeWork today
(first time connecting since updating to Jammy) and the package in
-proposed resolved the issue for me as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Promotion from -proposed sure would be nice. I see verification has
been done but a update excuses shows an netplan.io regression[1]. I'm
not sure if the test is flaky but I see that seb retried it a few
times[2] last week and it failed consistently, so maybe not.
I'm just curious if there's any
Public bug reported:
Could you add some clarifying output in the postinst around pypy3compile
failures to give context to an end user? The errors as they stand don't
indicate that this is pyp3 specific and can be concerning (they also
give the impression that QA isn't catching basic python bugs w
Public bug reported:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the session login screen.
$ lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
$ loginctl
This looks to be around the time of the issue where I disabled a VPN
connection (from syslog):
Mar 8 14:11:54 splat gnome-shell[677801]: **
Mar 8 14:11:54 splat gnome-shell[677801]:
Clutter:ERROR:../clutter/clutter/clutter-stage.c:3785:on_device_actor_reactive_changed:
assertion failed: (!clut
As a workaround for anyone, you can use nmcli to bring up a VPN
connection.
Run `nmcli c` to get a list of connections, once you have the name you
can enable it with `nmcli c up $name` or disable it with `nmcli c down
$name`.
--
You received this bug notification because you are a member of Ubun
@3v1n0 (Marco Trevisan) has pointed out
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1651 as a
possible fix
** Description changed:
When I click on a VPN connection in the Gnome top bar to enable or
disable the connection the entire desktop session crashes and dumps me
at the sess
FYI, if a user has a 22.04 install where they have explicitly removed
snapd/firefox this will add them back. Not sure if this was a
consideration in the fix/testing.
Also, the apt resolver is pulling in snapd while holding ubuntu-desktop
back during staging which made finding the cause of the sna
Dimitri, I thought we looked into plymouth and it was doing additional
setup during boot that caused us to leave it in the image. I wish I
could recall what all that way. Anyhow, if that has changed we'd be
open to it. Can you make the description a lot more descriptive and
discuss 'why' we want
** Also affects: apt (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1759440
Title:
Docker trusty image is very slow
Statu
I'll mention this here because I believe it's related, if not please
correct me and I'll file a separate bug. When cron jobs are run
/snap/bin is not in the path.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubu
Public bug reported:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
$ ubuntu-bug coreutils
*** Collecting problem information
The collected information can be sent to the developers to improv
** Description changed:
Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:
- $ ubuntu-bug coreutils
+ $ ubuntu-bug coreutils
- *** Collecting problem information
+ *** Collecting probl
Brian, the hack doesn't seem workable. Touching channel.ini would then
flag all images as being supported, which isn't true. It's unclear what
knock-on effects we would have touching this file (i.e. what other tools
see it and take different code-paths). The existence of the file
indicates that
** Tags added: id-5b1fe4c2babaab7ab6fd5d37
--
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/1775219
Title:
incorrectly reports package as unsupported if apt cache is empty
S
** Also affects: coreutils (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to coreutils in Ubuntu.
https://bugs.launchpad.net/bugs/1775291
Title:
'df /dev/sda1' (rootfs) ret
Public bug reported:
For installations that don't have netcat-openbsd somewhere in the seed
then any package/user that installs 'netcat' will get 'netcat-standard'
from universe rather than 'netcat-openbsd' from main. (One example is
the ubuntu-fan package that recommends netcat)
Suggested action
This issue crops up on the Bionic minimal cloud images which don't have
netcat-openbsd installed by default (it is in the Xenial image). When
docker.io is installed with recommends it pulls in netcat-standard (via
ubuntu-fan).
--
You received this bug notification because you are a member of Ubu
Public bug reported:
The shipped initrd doesn't match the compression that you'd get if you
update the initrd on bionic:
# A clean bionic cloud-image
$ file /boot/initrd.img-4.13.0-17-generic
/boot/initrd.img-4.13.0-17-generic: LZMA compressed data, streamed
# Update the initramfs (notice the de
Maybe it's this change in the linux source package:
linux (4.11.0-1.6) artful; urgency=low
* Miscellaneous Ubuntu changes
- [Debian] Use default compression for all packages
I'll check with the kernel team. But I thought if the kernel package
was changing which compression was used then i
My understanding had been incorrect and this is not an issue in this
package at all. The initramfs present in the cloud-image at first boot
is created by live-build with lzma compression. Subsequent kernel
installs that produce a new initramfs or updates to an existing
initramfs will be compresse
** Changed in: initramfs-tools (Ubuntu)
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.
https://bugs.launchpad.net/bugs/1792189
Title:
linux-firmware does not depend
Action plan:
Stage 1 - Configure lxc-net at boot rather than at install.
* This addresses the network failure for 15.10 containers started on 15.10
hosts (patch above in comment #6)
Stage 2 - Start lxc-net through systemd on the first launch of an LXC container.
* This mitigates the unroutable
The cloud-image builder picked up the change and is building images.
They are with the LP buildds now. I will update this bug once
publication completes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://
Cloud image downloads for amd64, i386, and ppc64el are available @ http
://cloud-images.ubuntu.com/proposed/wily/20151024/
The amd64 image is also available in canonistack lcy02 region as
lp1509414/wily-proposed
--
You received this bug notification because you are a member of Ubuntu
Touch seede
Cloud images build from proposed are available.
Next action:
- Verification of proposed package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed
Cloud images build from proposed are available.
Next action:
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1509414
Title:
pre-installed lxc in cloud image produces broken lx
Be aware in your testing that the lxd-net's service can come up slowly
depending on the speed of your cloud instance. Without the bridge
(lxcbr0) the container's networking will function prior to that service
starting; watch out for this false positive in your testing.
--
You received this bug no
My testing with the cloud image containing the proposed package has been
successful.
Just a note again that the test case detailed in the description is fine
with the understanding that network testing needs to ensure the lxc-net
service has started lxcbr0 or a false positive is possible (per comm
Séphane,
When this was added to the cloud seed we changed this from "users that
install LXC will loose connectivity to a 10.0.x.0/24 network" to "all
cloud users do not have connectivity to a 10.0.x.0/24 network at boot"
and the cause/effect will not be as clear to an end user. This had come
up i
I agree that this shuffling around is not pretty, but we need a solution
that makes 10.0.0.0/16 routable in cloud images where lxc/lxd are not in
use as had prior to http://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-
seeds/ubuntu.wily/revision/2360
The current situation conflicts with how clouds
Public bug reported:
Wily:
# python3 -c 'from pytz import country_names
for item in country_names.items():
print(item)'
Traceback (most recent call last):
File "", line 2, in
File "/usr/lib/python3.4/_collections_abc.py", line 497, in __iter__
for key in self._mapping:
File "/usr/lib/
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
drat, wrong bug. I meant to put that in bug #1473533
** No longer affects: tzdata (Ubuntu)
** This bug has been marked a duplicate of bug 1473533
CountryNameDict function trying to parse UTF-8 iso3166
*** This bug is a duplicate of bug 1473533 ***
https://bugs.launchpad.net/bugs/1473533
This affects precise, trusty, and vivid. Please backport this low-risk
fix for those releases. Thank you.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Last good test for EC2 occurred on June 9th with serial 20150608
https://jerff.canonical.com/job/NG_Test-EC2/376/
Ben is trying out:
wily server daily 20150608ebs-ssd amd64 us-east-1
ami-6f9e7404hvm
--
You received this bug notification because you are
So the it's just udev and systemd changes here. utlemming took the
working 20150608 ami, booted, upgraded, and rebooted and the instance
didn't survive the reboot.
This affects HVM only, PV is unaffected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded pack
Here are the package changes between the last working and first failing
builds:
20150608 good
20150610 bad
$ diff manifest-amd64-daily-20150608.txt manifest-amd64-daily-20150610.txt
101c101
< iso-codes 3.57-1
---
> iso-codes 3.58-1
248c248
< libpam-systemd:amd64 219-10ubuntu1
---
> libpam-systemd
Public bug reported:
add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul.
Issues:
- Using the presence of cloud-init to flag an image as a cloud image is
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
- Using the presence of EC2 metadata source is
** Tags added: cloud-images
--
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/1724623
Title:
Update ubuntu cloud info
Status in apport package in Ubuntu:
New
Bug descripti
I just learned that this doesn't need changes in cloud-init, or
shouldn't. I was target this to ubuntu-meta for ifupdate to be removed
from the seed in 17.10. From that we should just switch to netplan like
magic. ;) I'll let the owners of the other affected packages close
their own bits of this
Public bug reported:
I'm seeing a console-setup.service failure quite regularly in testing
where the temp file that should have been created can't be found.
This is a regular xenial cloud image.
19:51:13 systemd-tmpfiles[485]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate
line for path "/var/log
** Attachment added: "journal"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1824227/+attachment/5254776/+files/journal
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to console-setup in Ubuntu.
https://bugs.l
I have built cosmic, bionic, and xenial images in GCE with the packages
from -proposed and tested that console setup is functioning correctly
with the change. Thanks. I will be marking each of the releases as
tested.
** Tags removed: verification-needed verification-needed-bionic
verification-n
This would be an issue for the package, I will close the track for
cloud-images.
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch se
Public bug reported:
A user creates an ssh key and specifies it on the cmdline with 'ssh -i
new_key user@host'. The connection fails with the message "Too many
authentication failures" displayed to the user.
This would lead the user to believe that they failed to put the public
portion of the ne
** Summary changed:
- explicit key offered after all agent keys, auth fails before explicit key used
+ explicit key offered after all agent keys, auth can fail before explicit key
used
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1872485
Title:
virtualbox-guest-utils fails to install on 20.04
Status in apt package in Ubuntu:
New
systemd-timesyncd is conflicting with virtualbox-guest-utils but
virtualbox-guest-utils isn't providing time-daemon... debian/control in
virtualbox contains:
Package: virtualbox-guest-utils
Architecture: amd64 i386
Depends: adduser,
pciutils,
virtualbox-guest-dkms (= ${source:Ver
Public bug reported:
I am looking at the addition of 'Include /etc/ssh/sshd_config.d/*conf'
for use in Ubuntu cloud images. I wanted to add a config file and see
if I had done things correctly. I assumed that the files were sourced
lexographically (based on use of glob() in readconf.h) so that I
Drat, I see that now in sshd_config. I think I tried searching for
"first" and maybe by that point I was just looking at sshd's man page.
Okay, well then this is fine for me It's documented and stable. We
can comfortably make this change for cloud-images. Thanks Colin!
** Changed in: openss
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
https://bugs.launchpad.net/bugs/1875882
Title:
debconf attempts interactive configuration; breaks
** Description changed:
For installations that don't have netcat-openbsd somewhere in the seed
then any package/user that installs 'netcat' will get 'netcat-standard'
from universe rather than 'netcat-openbsd' from main. (One example is
the ubuntu-fan package that recommends netcat)
+ I
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kmod in Ubuntu.
https://bugs.launchpad.net/bugs/1866012
Title:
depmod ERROR during Setting up linux-modules-5.4.0-17-generic
Status in kmod package i
Public bug reported:
The 2nd display (attached to DVI) has stopped being detected but is used
by bios and grub (output ceases once the spinning boot animation
starts). I was away for a week but it was working prior to leaving.
I've notices that Xorg.0.log shows DVI-D-0 disconnected where the 2nd
The log shows "open /dev/dri/card0: No such file or directory" but it
does exist:
$ ls -l /dev/dri/card0
crw-rw+ 1 root render 226, 0 Mar 9 06:12 /dev/dri/card0
Unplugging the display from DVI-D-0 and plugging it back in does not
result in showing up in xrandr output.
--
You received this
Attaching the 2nd display via DisplayPort rather than DVI allows me to
use it again, so I happen to have a solution, but not everyone may be so
lucky.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bug
I tested the vivid package. 1:4.1.5.1-1.1ubuntu3 recreated the issue
but in 1:4.1.5.1-1.1ubuntu4 --force works.
Requesting SRU of fixes from bug #1436937 back to Trusty/Utopic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed t
Public bug reported:
Running from today's (201610907) daily yakkety livecd I can boot to the
desktop if only using the laptop's LCD (ThinkPad x230, intel graphics).
Attaching a 1920x1080 LCD via miniDP extends the desktop but windows
moved around produce a trail of windows that persist even after
** Summary changed:
- xorg hall-of-mirrors on external display
+ No X on boot with external monitor connected
** Description changed:
- Running from today's (201610907) daily yakkety livecd I can boot to the
- desktop if only using the laptop's LCD (ThinkPad x230, intel graphics).
- Attaching a
** Attachment added: "moving a window across the display"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1631519/+attachment/4757009/+files/ezgif.com-video-to-gif%20%282%29.gif
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
The attached gif tries to show the effect of moving a window across the
screen. Not captured in the low-framerate gif is that the trails of the
window are flickering and moving (compiz cpu usage is high when this
happens). Hitting WIN+w to display windows and then drop back to the
desktop clears
A monitor attached to the Thinkpad x230 via the docking station DVI port
is fine (boots to X and no crazy window trails). This is seen when
attaching a monitor via DP on the dock or mDP from the laptop. I was
using an mDP to HDMI cable or a DP to DualLink-DVI adapter to connect
monitors when I fo
Still failing with http://cdimage.ubuntu.com/daily-live/20161008
/yakkety-desktop-amd64.iso (Yakkety Final)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1631519
Title:
No X
I have tried two monitors of different brands and a random television. The
resolution selected is 1920x1080.
On Mon, Oct 10, 2016 at 7:19 PM, Mathieu Trudel-Lapierre <
mathieu...@gmail.com> wrote:
> Could you please try with a different monitor or share more of the
> details of how you are using
Also, the bug was opened with the system running BIOS version 2.57:
dmi.bios.version: G2ET97WW (2.57 )
I have upgraded to the latest version and recreated there as well:
Version: G2ETA7WW (2.67 )
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
These are working with 16.04 perfectly, I updated to 16.10 and had to
restore from backups to get back to 16.10. Then I booted from the live-
cd to capture this bug.
Scenarios:
1. mDP to HDMI cable connected to a 1080p monitor (Dell E248Wfp); that is the
simple example and they all fail with th
Running the recreate.sh script with util-linux 2.28.1-1ubuntu1 results
in a failure when growpart attempts to write the new partition table and
update the kernel indicating that the partition table was not cleared
from the kernel when we ran 'kpartx -s -v -d /dev/loop0'
In this case we have run:
k
Running the recreate.sh script with util-linux 2.28-5ubuntu2 gives us a
successful run.
** Attachment added: "success.output"
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1618525/+attachment/4730930/+files/success.output
--
You received this bug notification because you are a me
Public bug reported:
In the move from 2.28-5ubuntu2 and 2.28.1-1ubuntu1 of util-linux we see
a regression when asking kpartx to remove kernel partition mappings
where the appear to remain.
Context: We create and modify disk images heavily. The example recreate
creates a 2GB disk image with a sin
Public bug reported:
IMPACT: wget is not usable in the default configuration for LXD
containers in Xenial
Summary: A scoped zone address in the form [%http://[fe80::1%eth0]:13128'.
$ lxc exec test -- wget http://www.google.com
Error parsing proxy URL http://[fe80::1%eth0]:13128: Invalid IPv6 num
RFC 4007 : https://www.ietf.org/rfc/rfc4007.txt
Discussion upstream :
http://lists.gnu.org/archive/html/bug-wget/2009-06/msg0.html
Attaching a POC patch from upstream mailing list to demonstrate the fix,
but it is hackish.
** Attachment added: "Naive-IPv6-zone-identifier-implementation-for-H
Public bug reported:
A user can not delete themselves using the command 'sudo userdel -rf
', this is common in cloud tools that clean up running images
prior to capture. A quick test shows that this worked from Precise
(didn't look back further) to Raring and stopped working with Saucy.
Here's a
72 matches
Mail list logo