** No longer affects: resolvconf (Ubuntu Trusty)
** No longer affects: resolvconf (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu Trusty)
** No longer affects: systemd (Ubuntu Xenial)
** No longer affects: systemd (Ubuntu)
** No longer affects: systemd (Ubuntu Cosmic)
** No longer
*** This bug is a duplicate of bug 1821663 ***
https://bugs.launchpad.net/bugs/1821663
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1821663, so it is being marked as such. Please
Not sure if recent updates have fixed the issue, but problem has not
appeared after several sleep and awake events. I will ensure to post
details and try the above edit if problem recurs.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
It is yet unclear what the root cause of this issue is - libpam, crypt,
passwd and sudo seem like primary suspects. The 256 character password
is hashed to a value which still allows a TTY login to succeed. Also,
passwd run by a different user in the context of the affected user
(using sudo) still
Booted up a Ubuntu 14.04 LTS box & followed test procedure.
Same result - steps followed fine until I once 256 char password was
entered, I was unable to `sudo whoami` (password was not accepted)
OS: Ubuntu 14.04.6 LTS x86_64
Host: HP Compaq dc7700 Small Form Factor
Kernel: 3.13.0-168-generic
Although the gnome-bluetooth "fix" sounds like a workaround. So re-
adding a bluez task.
** Also affects: bluez (Ubuntu)
Importance: Undecided
Status: New
** Also affects: gnome-bluetooth (Ubuntu Ee-series)
Importance: Undecided
Status: New
** Also affects: bluez (Ubuntu
And the gnome-bluetooth fix was released in 3.28.2.
** Package changed: bluez (Ubuntu) => gnome-bluetooth (Ubuntu)
** Changed in: gnome-bluetooth (Ubuntu)
Status: Fix Committed => Fix Released
** Also affects: gnome-bluetooth (Ubuntu Disco)
Importance: Medium
Status: Fix
Looks like the upstream fix is gnome-bluetooth, not bluez?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1791405
Title:
bluetooth always in discoverable mode (security
now this begs the question why does kernel module i915 not auto load anymore?
i.e. the newer iso's since mid-march ..??? what got yanked out that would cause
this ??
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm
okay .. thought about this for a bit i915 compiled as module by default
in kernel sources.. lets force it to load..
added module i915 to /etc/modules to force loading .. it is the only
entry ..
reboot into the problem install .. and no problems .. lightdm starts and stays
going.
no flicker or
Hello!
I just wanted to chime in: My co-worker and I ran into this exact
problem. The `traceroute6` command was giving us "sendto: Invalid
argument", and we did not have the `traceroute` package installed. It
was only by finding this Launchpad bug that we became aware of the
problem, after
An upload of openssl to bionic-proposed has been rejected from the
upload queue for the following reason: "Should not introduce a delta to
downgrade to OPENSSL_TLS_SECURITY_LEVEL=0 as part of this SRU".
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
The attachment "Fix to identify virtualization type correctly in Xenial
on PowerPC" seems to be a debdiff. The ubuntu-sponsors team has been
subscribed to the bug report so that they can review and hopefully
sponsor the debdiff. If the attachment isn't a patch, please remove the
"patch" flag
I followed Tom's REPRODUCTION test, and got exactly what Tom said I would.
I can confirm the issue with 256 character passwords.
(I used `wc` to count characters in my buffer)
I could set the 256 character password (I used it with a backspace to
enter the old password, so it was only 1
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pam (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
Steve Langasek has pointed out that I missed the point of the bug.
I'm not comfortable with OPENSSL_TLS_SECURITY_LEVEL=0 in bionic. (Or,
indeed, in cosmic either.)
We shipped 18.04 LTS with OPENSSL_TLS_SECURITY_LEVEL=1, correct? I don't
recall seeing more than a handful of complaints about
ppc64el, s390x and riscv64 packages are built on arm64, s390x and
riscv64 packages are built on ppc64el
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic
verification-done-cosmic
--
You
A test package is available in PPA:
https://launchpad.net/~manjo/+archive/ubuntu/lp1764628/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764628
Title:
incorrect
Please review and consider this debdiff to Xenial. It fixes the issue
reported here.
== Before Patch ==
ubuntu@P8lpar4:~$ lscpu
Architecture: ppc64le
Byte Order:Little Endian
CPU(s):128
On-line CPU(s) list: 0-127
Thread(s) per core:8
Core(s) per
Please review and consider this debdiff to Xenial. It fixes the issue
reported here.
== Before the patch ==
ubuntu@P8lpar3:~$ lscpu
Architecture:ppc64le
Byte Order: Little Endian
CPU(s): 128
On-line CPU(s) list: 0-127
Thread(s) per core: 8
Core(s) per socket: 1
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
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debconf (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to debconf in Ubuntu.
I'm slightly concerned about raising the TLS minimums in our next LTS
release without some exposure to it in the 19.10 release. But this plan
sounds better than waiting until 20.10 to raise the minimums -- and
19.10 may be too soon to take the step.
But we don't have to decide on 19.10 defaults
@bdmurray The second fallback when debug is on, but the apt error is shown as a
warning even when debug mode is not enabled:
...
WARNING:root:package test3-package upgradable but fails to be marked for
upgrade (E:Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held
The internal VMware bug 2319367 I created was closed as a duplicate of
bug 2275007
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client
Hello errors.ubuntu.com, or anyone else affected,
Accepted apport into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.10-0ubuntu13.3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Wise, or anyone else affected,
Accepted gtk+3.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Anthony, or anyone else affected,
Accepted gtk+3.0 into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.22.30-1ubuntu3 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Wise, or anyone else affected,
Accepted gtk+3.0 into cosmic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.4-0ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
This is Workstation and Player 15 I do not have ability to test on ESXi
I am using VMnet8
On 4/2/19 1:30 PM, John Savanyo wrote:
> Can someone clarify, what VMware products is this know to affect
> (vSphere/ESXi or Workstation/Fusion) and what versions? Also what
> virtual NIC is used in the VM?
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/1503773
Title:
Drop ondemand init script
I've recently found that while pairing with this pen does not work,
"merely" connecting to the pen does work. That is:
# This command fails
$ echo -e "scan on\npair \nscan off" | bluetoothctl
# But this command works
$ echo -e "scan on\nconnect \nscan off" | bluetoothctl
Looking through the
Public bug reported:
Upon an upgrade to disco, now when anything access the audio output I
get a loud pop. Happens with a browser (firefox and chrome), spotify,
etc. It's independent of the application.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
Can someone clarify, what VMware products is this know to affect
(vSphere/ESXi or Workstation/Fusion) and what versions? Also what
virtual NIC is used in the VM?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in
I created internal VMware bug 2319367 to track looking into this.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client broken pipe
I tried to get the ondemand script dropped in 2015 #1503773, Got Nacked.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor
I've just built and installed the master branch of gnome-bluetooth
(commit b4edf6a8) and didn't see any behavioral change. Since it isn't
even possible to pair through bluetoothctl, I wasn't particularly
hopeful that an update to gnome-bluetooth would fix things.
--
You received this bug
This is fixed in perl 5.28.1-6, now in the disco release pocket.
** Changed in: perl (Ubuntu Disco)
Status: Confirmed => Fix Released
** Changed in: ubuntu-power-systems
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
FYI the QEMU change merged in the following pull request changed to
return an EPERM errno for the thread affinity syscalls:
commit 12f067cc14b90aef60b2b7d03e1df74cc50a0459
Merge: 84bdc58c06 035121d23a
Author: Peter Maydell
Date: Thu Mar 28 12:04:52 2019 +
Merge remote-tracking branch
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.10
---
unattended-upgrades (1.1ubuntu1.18.04.10) bionic; urgency=medium
* do_auto_remove() is successful unless a commit() operation fails
(LP: #1795696)
* Compare apt.package.Version objects and not the
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.3
---
unattended-upgrades (1.5ubuntu3.18.10.3) cosmic; urgency=medium
* Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting
This bug was fixed in the package apparmor - 2.13.2-9ubuntu4
---
apparmor (2.13.2-9ubuntu4) disco; urgency=medium
* debian/tests/control and debian/tests/compile-policy: don't test
thunderbird since the Ubuntu packaging doesn't ship a profile
-- Jamie Strandboge Wed, 27 Mar
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.10
---
unattended-upgrades (1.1ubuntu1.18.04.10) bionic; urgency=medium
* do_auto_remove() is successful unless a commit() operation fails
(LP: #1795696)
* Compare apt.package.Version objects and not the
This bug was fixed in the package unattended-upgrades -
1.5ubuntu3.18.10.3
---
unattended-upgrades (1.5ubuntu3.18.10.3) cosmic; urgency=medium
* Compare apt.package.Version objects and not the versions' string
representation. (LP: #1820888)
This prevented adjusting
This bug was fixed in the package unattended-upgrades -
1.1ubuntu1.18.04.10
---
unattended-upgrades (1.1ubuntu1.18.04.10) bionic; urgency=medium
* do_auto_remove() is successful unless a commit() operation fails
(LP: #1795696)
* Compare apt.package.Version objects and not the
This bug was fixed in the package apparmor - 2.13.2-9ubuntu4
---
apparmor (2.13.2-9ubuntu4) disco; urgency=medium
* debian/tests/control and debian/tests/compile-policy: don't test
thunderbird since the Ubuntu packaging doesn't ship a profile
-- Jamie Strandboge Wed, 27 Mar
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
The verification of the Stable Release Update for unattended-upgrades
has completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that
(In reply to Michel Dänzer from comment #8)
> Mesa doesn't really need explicit thread affinity at all. All it wants is
> that certain sets of threads run on the same CPU module; it doesn't care
> which particular CPU module that is. What's really needed is an API to
> express this affinity
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Bionic)
Status: New => Triaged
** Changed in: apport (Ubuntu Bionic)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of
** Also affects: apport (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed in: apport (Ubuntu Bionic)
Status: New => Triaged
** Changed in: apport (Ubuntu Bionic)
Importance: Undecided => High
--
You received this bug notification because you are a member of
Confirmed. The setting can be changed in the "Region & Languague" panel:
gnome-control-center region
(cog icon next to "Input Sources" section)
But this doesn't actually change the corresponding gsetting:
$ gsettings get org.gnome.desktop.input-sources per-window
false
** Package
No need to re-test these; it's already been included in bionic/cosmic
and bug comments are a side-effect of the changelogs for the upload with
this backport.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added: verification-done-bionic
Some how part of this fix got lost in Cosmic.
** Changed in: apport (Ubuntu Bionic)
Status: New => Fix Released
** Changed in: apport (Ubuntu Cosmic)
Status: New => In Progress
** Changed in: apport (Ubuntu Cosmic)
Assignee: (unassigned) => Brian Murray (brian-murray)
--
@mathew-hodson It's in git, and will make it's way in in a future
release
--
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/1821308
Title:
apt-get upgrade ignores pinning
*** This bug is a duplicate of bug 1820860 ***
https://bugs.launchpad.net/bugs/1820860
** This bug has been marked a duplicate of bug 1820860
The issue was due to aptdaemon bug #1811694 not software-properties
** Changed in: software-properties (Ubuntu)
Importance: Undecided => Low
** Changed in: software-properties (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
okay after rebooting via grub installed by sda1 .. as before .. red
flash (no plymouth) lightdm briefly displays login screen .. then
underline cursor then blank screen.
attached is zl10-boot2-xorg.0.log xorg.0.log.old is now the already
uploaded zl10-xorg.0.log above
a crashing time is
iso april 2 2019 tested .. adding xorg.0.log & xorg.0.log.old files from
first boot into fresh install .. There was a 1 to 2 second flicker in
lightdm appearing then blanking and then reappearing on first boot ..
have not yet rebooted into this from grub as installed by sda1 .. wanted
to save
the " surprise log file " not expected on a first boot .. with normal
xorg startup should not exist ..
** Attachment added: "zl10-xorg.0.log.old -- first boot (inital xorg-server
start which flickered lightdm?)"
That has been fixed in bluez upstream but there has been no new version
since
** Package changed: gnome-bluetooth (Ubuntu) => bluez (Ubuntu)
** Changed in: bluez (Ubuntu)
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch
> None of the packages which you are having an issue with are ones from
the official Ubuntu archive
What about these? Why is libcurl3 even in Bionic as a conflicting
package if nothing was supposed to use it?
$ apt-cache rdepends libcurl3
libcurl3
Reverse Depends:
libcurl-openssl1.0-dev
*** This bug is a security vulnerability ***
You have been subscribed to a public security bug:
Excerpt from a similar report
(https://bugzilla.redhat.com/show_bug.cgi?id=1602985) :
Opening the Bluetooth settings will make the device discoverable again,
but does not make the device
** Tags added: bionic
** Tags added: comic ui
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1822768
Title:
libgtk window resize problem
Status in gtk+3.0 package in
Public bug reported:
Ubuntu 19.04
The option to apply different input source for each window doesn't work
(it automatically reset itself)
However, I manually change org.gnome.desktop.input-sources.per-window
and it works.
** Affects: ibus (Ubuntu)
Importance: Undecided
Status:
Confirmed that pcc-cpufreq *can* be used in preference to intel_pstate
even on a CPU that supports intel_pstate if the firmware tables are
setup to request such. One such server is an E5-2630 v3 HP DL360 G9
(shuckle).
On the default "dynamic" firmware setting you get driver=pcc-cpufreq +
Public bug reported:
Bash pre-4.4.20 has a bug in its PID hash table that causes spin-loops
when spawning sub processes and waiting for them. There is a fix:
https://ftp.gnu.org/gnu/bash/bash-4.4-patches/bash44-020
Our application started being affected (locking up) by this since
migrating from
Has this been solved in newer versions of ubuntu?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/604572
Title:
Parse error when running "...display"-Tools
Status in lvm2
Thanks for above. I had the same issue while creating physical volume as
below.
pvcreate /dev/sda4
deleting /etc/lvm/cache/.cache solved issue!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 in Ubuntu.
Just to be prepared I added an MP for this at [1].
But I agree to cjwatson that we should (if possible) either revert this in
Buster+Disco or none of them to not split up the behavior of different releases
even more.
Never the less, one might want to peek at the change and or play with the PPA
** Merge proposal linked:
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/365396
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
FYI - Up for discussion in the scope of Debian-Buster at [1].
[1]: https://lists.debian.org/debian-devel/2019/04/msg00010.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Changed in: openssh (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1822370
Title:
19.04 beta openssh-client broken pipe
Status
--- Comment From heinz-werner_se...@de.ibm.com 2019-04-02 07:38 EDT---
IBM Bugzilla status -> closed, Fix Released with Disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Public bug reported:
An app using libgtk-3 as GUI-lib shows strange behaviour since on ubuntu 18.04
an later.
The problem is, that a not resizeable window not sets its correct size, when it
shows up a second and all further times - but the first time, the size is
correct.
In that window a gtk
I filed this bug at Debian as well => https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=926229
** Bug watch added: Debian Bug tracker #926229
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926229
** Also affects: openssh (Debian) via
A minimal example program to reproduce the behaviour.
In the example a click on "show subwindow" opens a second window, in which a
component is inserted at showing up. On the first time all is ok like shown in
the left part of the screenshot. But if you close the second (sub) window and
open
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pam in Ubuntu.
https://bugs.launchpad.net/bugs/1822736
Title:
Passwords longer than 255 characters break
This bug was fixed in the package linux - 4.15.0-47.50
---
linux (4.15.0-47.50) bionic; urgency=medium
* linux: 4.15.0-47.50 -proposed tracker (LP: #1819716)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
-
Ok, it's really late for such a big landing and I'm worried it might
complicate things, but seeing that all the packages are ready and that
it's all well-coordinated by two people, I'll approve this FFe. Please
be sure to proceed as soon as possible not to block the release.
** Changed in:
Just give me a poke once you perform the uploads. I can then do a quick
NEW review of the pyqt5webengine package.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
Could you please try installing the previous mutter version by
downloading the .deb files from here:
https://launchpad.net/ubuntu/+source/mutter/3.32.0-1/+build/16489975
and then install them all.
** Tags added: nvidia
** Package changed: wayland (Ubuntu) => mutter (Ubuntu)
** Changed in:
Public bug reported:
To try the new support for EGLStreams and Wayland I have directly tried some
programs to see how this performs. Unfortunately there are multiple problems:
Chrome does not use GPU hardware acceleration anymore (I get huge CPU spikes
while scrolling on normal pages).
Also
Hello Matthias, or anyone else affected,
Accepted binutils into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.30-21ubuntu1~18.04.1 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Hello Matthias, or anyone else affected,
Accepted binutils into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/binutils/2.31.1-6ubuntu1.1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: gnome-shell
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu.
https://bugs.launchpad.net/bugs/1796251
Title:
gnome-shell crashed with SIGSEGV in
Something I was not previously aware of that informs this a bit more, is
that in some BIOS modes (apparently HP uses this extensively, unsure
about Dell and others) you get a "Collaborative Power Control" mode,
which sets the scaling_driver to pcc-cpufreq (as opposed to cpufreq) and
is some weird
(as context to this information, apparently this particularly bad
performance experienced with 'powersave' happens when the BIOS power
control is set to the default, and goes away when in the BIOS you set
power management to 'os control' - so there is some additional
information needed to
See also LP: #1732696 and LP: #1579278.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1806012
Title:
set-cpufreq: 'powersave' governor configuration sanity on ubuntu
** Tags added: disco
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1822730
Title:
Disco server install fails to boot using encrypted partitions
Status in busybox
Just to add some more detail to this bug; for the impacted deployment we
actually ended up re-configuring the power regulator settings via the
BIOS to delegate to the OS for control; after a reboot we've just stuck
with the default ondemand behaviour and performance has been
consistent/better than
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
unattended-upgrades. This problem was most recently seen with package version
1.5ubuntu3.18.10.3, the problem page at
https://errors.ubuntu.com/problem/7551745f47e60a92582dfa16b5ae7f1c0383d5f7
Colin was so kind to also find this reference [1] in Debian.
Which asks about the same revert, but not yet for it affecting VMWare - instead
it seems it also conflicts with "iptables -m tos" as well.
I'll bring it up with VMWare, but if also conflicting with some iptables
options that would be
Until resolved - as a landing page (I'll put that in the description as well):
The summary for the workarounds for now is:
You can configure your /etc/ssh/ssh_config permanently
Host *
IPQoS lowdelay throughput
Or per command via:
$ ssh -o IPQoS=throughput user@host
---
Per the other bugs
@Frank - that is good for you and thanks for confirming my assumptions.
But it is unfortunate for openssh :-/
** Bug watch added: github.com/hashicorp/vagrant/issues #10730
https://github.com/hashicorp/vagrant/issues/10730
--
You received this bug notification because you are a member of
I don't want to revert this as that just takes the pressure off VMware;
ultimately this is their bug that they need to fix.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #1017
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1017
** Also affects: gnome-shell via
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1017
Importance: Unknown
Status: Unknown
** Changed in: gdk-pixbuf
Public bug reported:
Performing a fresh Disco (daily build from 2019-03-31) server install
with / mounted from LVM over dm-crypt (over mdadm), the boot fails just
after asking the encrypted partition passphrase with the following
error:
/scripts/local-top/cryptroot: line 1: fold: not found
** Changed in: linux-signed-hwe (Ubuntu)
Status: New => Invalid
** Changed in: initramfs-tools
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.
1 - 100 of 101 matches
Mail list logo
