ok.
I'd like to have a non-base64/non-gzipped way to disable the networking
and I first tried just the /etc/cloud snippet of network disabled, but
that didn't work because I also had ip= on the kernel command line, and
cloud-init still did automatic built-in network discover.
Are the /etc/cloud
Travis has s390x support with Ubuntu bionic.
PPAs have s390x support (just tick in settings) and I have access to Ubuntu
mainframe.
What things should I be bisecting for?
I'd rather not do mono transition without Debian. Note we are on par with
Debian at the moment. Not sure when they are thinki
Note 10.17 is failing to migrate in Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863463
Title:
Firefox 75 requires nodejs >= 10.19
To manage notifications about this bug go to:
https://bu
We did uploads only to fix bugs which are part of the archive-wide transitions.
I.e. unversioned python removal, requiring minimum tls1.2, etc.
None of us wish to touch nodejs.
Note that once nodejs is uploaded all of the node autopkgtests get
triggered, with many of them failing.
maybe it is bes
The system has three disks /dev/sda /dev/sdb /dev/nvme0n1
I'm not sure why, but it appears that /dev/sda has been used for installing the
bootloader, at least a little. I'm not sure why, and whether it is a UI bug or
grub-installer logic.
$ zgrep -e sda -e nvme syslog.gz | grep grub-install
Jan
So, snaps in the snapstore can declare a contact url, where one can file
bug reports.
I don't see these to be exposed on the system, but maybe I don't know
the localhost APIs for that.
I do wonder if there can be some standartesation done, for example, if
the contact url is +filebug on a launchpa
aha, so:
$ snap info --verbose git-ubuntu | grep contact
contact: https://bugs.launchpad.net/usd-importer/+filebug
I wonder, if we can improve apport to actually upload / start filing a
bug report on launchpad, if it points to a launchpad +filebug url?
Can we enforce for contact to be set to s
Public bug reported:
clang seems to default to z10, should that be bumped to z13?
std::string systemz::getSystemZTargetCPU(const ArgList &Args) {
if (const Arg *A = Args.getLastArg(clang::driver::options::OPT_march_EQ)) {
llvm::StringRef CPUName = A->getValue();
if (CPUName == "native"
Public bug reported:
## non262/Intl/RelativeTimeFormat/format.js: rc = 3, run time = 0.050082
non262/Intl/RelativeTimeFormat/format.js:61:3 Error: Assertion failed: got
"this minute", expected "in 0
minutes"
Stack:
@non262/Intl/RelativeTimeFormat/format.js:61:3
TEST-UNEXPECTED-FAIL | non262/In
Public bug reported:
fwsetup LABEL should be "UEFI Firmware Settings"
as per design review with mpt, we want fwsetup menyentry to be more
verbose and more technical, such that there is no ambiguity as to what
it is.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
--
** Changed in: grub2 (Ubuntu Focal)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856424
Title:
please add smbios module to the signed grub2 images
To manag
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
** Also affects: ubuntu-cdimage
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/1864547
Tit
** Changed in: ubuntu-cdimage
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864547
Title:
fwsetup LABEL should be UEFI Firmware Settings
To manage notifications
Public bug reported:
$ ldd /usr/lib/x86_64-linux-gnu/libcoordgen.so.1
linux-vdso.so.1 (0x7ffc0e384000)
libmaeparser.so.1.2 => not found
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x7fb86d1a5000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x0
** Changed in: schroedinger-coordgenlibs (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864569
Title:
i think /usr/lib/x86_64-linux-gnu/libcoordgen.so.1
Public bug reported:
I had to disable a few tests that failed with python3
++ @unittest.expectedFailure
+ def
testEnumerateStereoisomersRandomSamplingShouldBeDeterministicAndPortable(self):
#tests.addTests(doctest.DocTestSuite(EnumerateStereoisomers,
optionflags=doctest.ELLIPSIS))
This may
** Changed in: grub2 (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863994
Title:
do not build (or sign) grubnetx64-installer.efi in Ubuntu
To manage no
The requested package version is in proposed, and will migrate after the
blockage in front of it migrates.
** Changed in: libguestfs (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
Public bug reported:
RM: ftbfs strings vs bytes with new ocmal; dead upstream no reverse
dependencies
** Affects: ocaml-expect (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: ocaml-melt (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: o
** Changed in: openssl (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/1856428
Title:
Disable TLS below 1.2 by default
To manage notifications ab
Public bug reported:
RM coccinelle, again, from focal-proposed
I didn't realize that it's no longer installable:
coccinelle/amd64 unsatisfiable Depends: python-gtk2
coccinelle/amd64 unsatisfiable Depends: python-glade2
coccinelle/arm64 unsatisfiable Depends: python-gtk2
coccinelle/arm64 unsatisf
The browsers will require SECLEVEL=2 from April 2020, the change in
libraries has already landed.
You can override this via command-line, a system config file, or a local
config file + environment variable pointing to it.
On Ubuntu 20.04 LTS:
man SSL_CTX_get_security_level.3ssl
does have:
--
Le
About the server:
- It's certificate is valid for 2 years, and Apple has started to
rejecting any servers for which certificate is valid for more than 13
months.
- It has a SHA1withRSA certificate in its chain, which will be rejected
by all clients soon.
- It supports many weak TLSv1.2 ciphersui
** Also affects: partman-auto (Ubuntu)
Importance: Undecided
Status: New
** Changed in: partman-auto (Ubuntu)
Status: New => 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
partman-auto recipes got adjusted so ESP is now created even under BIOS
boot of ubiquity.
However, it simply is empty at the moment. We should "install" both PC &
UEFI grub onto it, somehow.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
** Changed in: abootimg (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846208
Title:
[MIR] abootimg (dependency of initramfs-tools-ubuntu-core)
To ma
** 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/1853300
Title:
[20.04 FEAT] openCryptoki ep11 token: Enhanced Support
To manage notifications about
** 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/1858792
Title:
[20.04 FEAT] openCryptoki ep11 token: Support for new hardware
To manage notification
*sigh* well, indeed the previous packaging does a lot of work, and
doesn't install anything in the end. Re-uploaded atlas with below
attached patch, which should hopefully install optimized z13 builds in
the right place now.
** Patch added: "fix-install-paths.patch"
https://bugs.launchpad.net/
nested kvm is disabled by default on s390x. One can force-enable that by
booting with kernel cmdline kvm.nested=1 in /etc/zipl.conf and rerun $
sudo zipl; and reboot.
However, I'm confused why this is filed, when this is the expected
default behaviour and has been previously raised and discussed i
** Changed in: glibc (Ubuntu)
Status: New => Fix Committed
** Changed in: ubuntu-z-systems
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821200
Title:
Ma
submitted for consideration to be included in Disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821200
Title:
Mark vx and vxe as important hwcap to be able to provide differently
tuned shared
Mar 29 10:31:45 s1lp15 sudo[1126]: pam_unix(sudo:session): session closed for
user root
Mar 29 10:32:02 s1lp15 sudo[1144]: pam_unix(sudo:account): account ubuntu has
password changed in future
Mar 29 10:32:02 s1lp15 sudo[1144]: ubuntu : TTY=pts/0 ; PWD=/home/ubuntu ;
USER=root ; COMMAND=/usr/s
3.10.3-8ubuntu2 is now published in the same repository, and should be
better. https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/3679/+build/16548143
at least the standard and z13 libraries are now of different size,
meaning are different. Hopefully they are now vector optimized for z13
@manjo as you can see from launchpad and proposed-updates report it has
been synced 17h ago, built and stuck in disco-proposed with autopkgtest
regressions, and awaiting results for many more.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
@Peter
I guess the question is, whether or not, we should be trying to use dasd as a
bcache device at all. Or like create a partition table, and use the partition
as a bcache device then? In that case should the make-bcache fail on the full
dasd device, as shows in the reproducer steps?
If I un
** Changed in: openssl (Ubuntu)
Assignee: (unassigned) => Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1797386
Title:
[SRU] OpenSSL 1.1.1 to 18.04 LTS
To manage notifi
Not sure if blake support is in TLS certificates.
I see many more constants for sha3, than for blake:
https://paste.ubuntu.com/p/gjzTwVTCBX/
did you try to use sha3-512 and did that work?
** Changed in: openssl (Ubuntu)
Status: New => Incomplete
--
You received this bug notification bec
It's funny how long it took them to figure it out, but yes
https://bugzilla.redhat.com/show_bug.cgi?id=1195029#c22
is the right answer. Please use that patch / combination of tagging the
device with tag&wants using udev rule + making the service bind to it.
--
You received this bug notification
Public bug reported:
wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
with
Disabling SSL due to encountered errors
** Affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
** Affects: tzsetup (Ubuntu)
Importance: Undecided
Status: New
** Af
** Also affects: openssl (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: wget (Ubuntu)
** Bug watch added: Debian Bug tracker #926315
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926315
** Also affects: openssl (Debian) via
https://bugs.debian.org/cgi-bin/bu
Public bug reported:
[Impact]
* increase minimum default tls security level from 0 to 1, as is the default
upstream
[Test Case]
* generate 80bits TLS certificate and attempt to use it
* with prior openssl it should work, but with this update it should fail
[Regression Potential]
* This incre
** Also affects: openssl (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: openssl (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: openssl (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you ar
** Changed in: openssl (Ubuntu Disco)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822984
Title:
revert tls security level back to 1
To manage notifications ab
lxd client is usable; the lxd server is not under wsl, so it wouldn't be
possible to complete lxd init under wsl.
do-release-upgrade should be usable under wsl; as it's no different to a
chroot or like something like virtuozzo sans ability to run systemd.
--
You received this bug notification be
But equally, I would not want to keep cosmic more insecure than what
bionic and disco will be. And currently, cosmic is a release regression
w.r.t. bionic GA. Upgrading to newer releases, should not result in
looser acceptance of insecure protocols.
** Description changed:
[Impact]
* increase
Public bug reported:
[Impact]
* linux autopkgtest should only execute either rebuild tests, when triggered
by toolchain.
or execute regression suite when triggered by meta
but never both. As otherwise, it results in false negative results for the
kernel
[Test Case]
* Trigger adt test
Regression in autopkgtest for apport (i386): test log is a false
negative (apport triggered by python-httplib2)
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-bionic/bionic/i386/a/apport/20190402_181336_3284e@/log.gz
has warnings / error as
** Changed in: openssl (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822898
Title:
wget https://geoip.ubuntu.com/lookup fails in mini.iso d-i
To m
** Changed in: openssl (Ubuntu Cosmic)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822984
Title:
revert tls security level back to 1
To manage notifications abo
** Also affects: python3.6 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: python3.6 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: python3.7 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: python3.6 (Ubuntu Bionic)
Also, cryptsetup uses Depends: busybox-static | busybox
and both of those variants have FOLD enabled.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822730
Title:
Disco server install fails to boot
sigh, looks like initramfs-tools-core now depends on busybox-initramfs,
instead of using busybox nor busybox static.
** Changed in: busybox (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Normally one should have plymouth installed, and fold code path
shouldn't be used.
Do you not have plymouth installed, and/or does it not work in you
environment?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Description changed:
[Impact]
* OpenSSL 1.1.1 is an LTS release upstream, which will continue to
receive security support for much longer than 1.1.0 series will.
* OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to be
rapidly adopted due to increased set of sup
h
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813400
Title:
systemctl doesn't respect --dry-run
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/system
@Jurit
Your system should be working normally, and most likely nothing to do
with this bug report. Please open a new bugreport attaching logs to
figure our what is wrong with your installation.
What filesystem types do you use ($ mount)? What are the permissions of
your rootfs? ($ ls -latr /)
--
** Also affects: logrotate (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: logrotate (Ubuntu Cosmic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
@seth
json-c / json-glib / libfastjson are C, rather than CPP.
libjsoncpp may be suitable.
But
json, by default is unreadable garbage. Whilst yaml is actually
readable. I do understand that it is syntactic sugar / nice to have. But
that also makes all the difference. And indeed yaml is fairly st
It's back!
And got maintained for a while, but now broken with new git. Removed
from testing, and imho we should remove it again for now.
** Changed in: git-remote-hg (Ubuntu)
Status: Fix Released => Triaged
** Bug watch added: Debian Bug tracker #915426
https://bugs.debian.org/cgi-bin
** Changed in: valgrind (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811071
Title:
Ubuntu19.04: valgrind does not properly handle the addex instruction
Jan 28 23:50:06 ottawa audit[10278]: AVC apparmor="DENIED" operation="mount"
info="failed flags match" error=-13
profile="lxd-improved-kodiak_"
name="/run/systemd/unit-root/home/" pid=10278 comm="(networkd)" flags="ro,
nosuid, nodev, remount, bind"
Jan 28 23:50:06 ottawa kernel: audit: type=140
Hmmm, but it should be fine if one gets EPERM or like EACCES. Hmmm..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813622
Title:
systemd-resolved, systemd-networkd and others fail to start in lxc
root@improved-kodiak:~# systemctl restart systemd-resolved
Jan 29 00:11:52 improved-kodiak systemd[1]: Bus private-bus-connection:
changing state UNSET → OPENING
Jan 29 00:11:52 improved-kodiak systemd[1]: Bus private-bus-connection:
changing state OPENING → AUTHENTICATING
Jan 29 00:11:52 improve
This is similar to https://github.com/systemd/systemd/issues/10032
But this time around with apparmor, under lxd, on ubuntu
Regression from 1beab8b0d0ff2d7d1436b52d4a0c3d56dc908962
Will be tracing this further now.
** Bug watch added: github.com/systemd/systemd/issues #10032
https://github.com/
$ lxc config set improved-kodiak raw.apparmor 'mount
options=(ro,nodev,remount,bind),
mount options=(ro,nosuid,nodev,remount,bind),
mount options=(ro,nosuid,noexec,remount,strictatime),
mount options=(ro,nosuid,nodev,noexec,remount,bind),'
** Description changed:
This is a regression from 239
Actually more is needed:
$ lxc config set test-v240 raw.apparmor 'mount options=(ro,nodev,remount,bind),
mount options=(ro,nosuid,nodev,remount,bind),
mount options=(ro,nosuid,noexec,remount,strictatime),
mount options=(ro,nosuid,noexec,remount,bind,strictatime),
mount options=(ro,nosuid,nodev,noe
** Changed in: systemd (Ubuntu)
Status: Invalid => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813622
Title:
systemd-resolved, systemd-networkd and others fail to start in lxc
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu Disco)
Assignee: Daniel Axtens (daxtens) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: systemd (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813622
Title:
systemd-resolved, systemd-networkd and others fail to start i
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu Disco)
Assignee: Dan Streetman (ddstreet) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
** Changed in: systemd (Ubuntu Disco)
Status: In Progress => Fix Committed
** Changed in: systemd (Ubuntu Disco)
Assignee: Victor Tapia (vtapia) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: systemd (Ubuntu Disco)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804487
Title:
systemd-resolved has issues when the answer is over 51
Removing block-proposed, although lxd fix is in flight, I have reverted
the relevant commit for now in the systemd in disco-proposed.
The intention is to still ship systemd in disco with that patch in
place, and thus fixed lxd is still needed in v3.9+ and v3.0 series.
** Tags removed: block-propo
Installed system using latest bionic daily, which contains ubiquity
18.04.14.11.
The machine has nvidia graphics drivers, and I opted into installing 3rd party
drivers.
The nvidia drivers got correctly installed, and compiled:
$ find lib/modules -name nvidia.ko
lib/modules/4.15.0-45-generic/upda
Installed system using latest bionic daily, which contains ubiquity
18.04.14.11.
There is no /etc/initramfs-tools/conf.d/resume file created, and
grepping for RESUME= setting, there are none hardcoded.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-don
Installed system using latest bionic daily, which contains ubiquity
18.04.14.11.
There is no /etc/initramfs-tools/conf.d/resume file created, and
grepping for RESUME= setting, there are none hardcoded.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-don
The warning is always there, but the permissions are correctly applied in
cosmic+
So for bionic we will need a chmod +x added in the debian/tests/upstream, or
somewhere like that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
** Changed in: s390-tools (Ubuntu)
Milestone: None => ubuntu-19.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805841
Title:
CPI information about kvm usage is lost during apt upgrade
To man
DEB_BUILD_OPTIONS=custom builds are not supported, and one has to
investigate manually why tuning to a custom current build-time machine
fails.
Also DEB_BUILD_OPTIONS=custom packages are not suitable to be shipped in
the Ubuntu archive, as they do not gain unique arch qualified names to
be coinsta
Note that DEB_BUILD_OPTIONS=custom builds are not something that is
suitable to run on our buildds and to ship in the archive for everyone.
As the package name clash there, and the build would be for the buildd,
rather than for a particular tuning level.
--
You received this bug notification beca
In unapproved queue
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799208
Title:
dbginfo.sh does not complete on Ubuntu 16.04(.5)
To manage notifications about this bug go to:
https://bugs.launchpa
Public bug reported:
$ /snap/bin/gnome-calculator
cannot read mount namespace identifier of pid 1: Permission denied
$ /snap/bin/lxc list
cannot read mount namespace identifier of pid 1: Permission denied
$ uname -a
Linux ottawa 4.19.0-12-generic #13-Ubuntu SMP Tue Jan 29 00:52:02 UTC 2019
x86
Public bug reported:
in disco proposed with new systemd and v4.19 kernel it appears that
dmsetup / cryptsetup storage either got better or worse.
Devices take very long to activate, and sometimes remain in use during
test clean up.
This leads to udisks autopkgtest failing on ppc64le and systemd'
@jweede
Hm. And is the instance booted with or without initramfs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1771858
Title:
/snap/bin not in default PATH for units, snapd should ship system-
e
Hi,
I cannot reproduce the issue, but it might be relevant how the system is
booted and/or was upgraded.
Can you do the following, please?
sudo systemd-run --unit=check-env /usr/bin/env
sudo journalctl --no-pager -u check-env
cat /etc/systemd/system.conf
cat /proc/cmdline
journalctl -b -k | grep
It fails to build in Debian too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1520033
Title:
ftbfs on s390x
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/
** Attachment added: "mono_5.18.0.240+dfsg-5_s390x.build.gz"
https://bugs.launchpad.net/ubuntu/+source/mono/+bug/1520033/+attachment/5296217/+files/mono_5.18.0.240+dfsg-5_s390x.build.gz
** Changed in: mono (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
cannot reproduce with 20191010 incomplete... / fix released... ?
also see https://lists.freedesktop.org/archives/systemd-
devel/2019-October/043573.html
** Changed in: casper (Ubuntu)
Assignee: Dimitri John Ledkov (xnox) => (unassigned)
--
You received this bug notification because
** Changed in: deja-dup (Ubuntu Eoan)
Assignee: (unassigned) => Dimitri John Ledkov (xnox)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847706
Title:
Deja Dup still tells python-gi (pytho
Public bug reported:
imho lxd group is added to too many products now.
it should only be done for high-level "classic" products like ubuntu-
server-live / ubuntu-desktop / etc.
imho it should not be added to ubuntu-base or buildd.
** Affects: livecd-rootfs (Ubuntu)
Importance: Undecided
Are you installing using UEFI boot or BIOS boot?
At the moment, with UEFI it is not possible to install /boot on RAIDed
device, but it is possible to have / mountpoint on the mdadm raid.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You can control the "magic" bootloader stuff, by using "Make Boot
Device" action in the submenu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847834
Title:
Eaon Ermine Live Server can not create m
Ubuntu Live Server bug reports are tracked in the "subiquity" project,
added bug task for it.
** Also affects: subiquity
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
In Disco:
- .iso from a CD-ROM or USB stick is mounted as whole block device, i.e.
/dev/sr0 /dev/sda
- .iso from a partition on disk (i.e. recovery partition) is mounted as a
partition, i.e. /dev/sda1
- in partman-auto black-list is set on whole block device mounts, i.e. /dev/sr0
/dev/sda
In Eo
So,
I think we should be sensitive to whether or not the device is RO or
not. I.e. if one uses RO actual CDROM it should always be skipped.
Also we should be sensitive to disk size and not offer tiny devices for
install.
And ideally, somehow, we shouldn't offer devices with /cdrom mount for
"who
# If there's only one disk, then preseeding partman-auto/disk is
# unnecessary, and sometimes inconvenient in heterogeneous environments
if [ "$method" ] && [ -z "$disks" ]; then
DEVS="$(get_auto_disks)"
if [ "$(echo "$DEVS" | wc -l)" -eq 1 ]; then
disks="$(cat "${DE
@superm1 i want the OEM image.
Imho, i like mwhudson approach. In general, we do want to prevent
some_device, if installer is running from the device in question. My
change to capture partitions, is because our regular stock installer now
mounts as a partition, rather than a whole disk.
--
You r
I'm slightly interested to know how you can use biggest_free
# Skip devices containing the installation medium
[ -e "$dev/installation_medium" ] && continue
And we have always done that, meaning if one boots from something that
looks like installation_medium it wil
** Also affects: partman-base (Ubuntu)
Importance: Undecided
Status: New
** Patch added: "partman-auto.patch"
https://bugs.launchpad.net/ubuntu/+source/partman-base/+bug/1847944/+attachment/5296982/+files/partman-auto.patch
--
You received this bug notification because you are a me
901 - 1000 of 9094 matches
Mail list logo
