I've reproduced the original problem then been running proposed kernels
in bionic and focal now for at least 2 hours, and problem seems fixed:
root@machine-1:~# uname -r
4.15.0-176-generic
root@machine-1:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
Marking verification done.
ubuntu@machine-0:~$ dpkg -l evdi-dkms | grep ^ii
ii evdi-dkms 1.9.1-1ubuntu4~20.04.2 all Extensible Virtual
Display Interface driver kernel module
ubuntu@machine-0:~$ uname -r
5.15.0-23-generic
** Tags removed: verification-needed
** Tags added:
Would it be possible to give brief instructions on how to install the
latest 5.15 kernel in focal to assist in verification? There are libssl3
and libc6 dependencies which it's not obvious how to install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Just going through old cases - any update on this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878957
Title:
Upgrade profile with "security" enabled marks kernel packages as
manually
Customer has asked again for a further update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903776
Title:
Changed ubuntu-keyring paths breaks upgrade to focal.
To manage notifications about this
The customer is asking if there's an update?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903776
Title:
Changed ubuntu-keyring paths breaks upgrade to focal.
To manage notifications about this
Public bug reported:
Install appears ok, the installation of boot loader failed.
I am trying Boot-Repair, will do so after this reboot.
Installing from live.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic
Tried it out on a juju controller in lxd works fine
Tried it on a bionic cluster (bundles made with stsstack-bundles
generate-bundle.sh and no options) - first time I ran through it go stuck on
nova-compute and I had to ctrl+c. Ran again, no issues.
Have tried --upload with --all-logs and no
Hi Andres,
Thank you for that, and thank you to the reporter - I actually spent
quite a bit of time struggling with this today, and the bug report and
reference to shim-signed pointed me in the right direction.
Cheers,
John.
--
You received this bug notification because you are a member of
So, the reason the suggested workaround doesn't work is because this
file is extracted from a copy of the package which is downloaded on the
fly by /usr/lib/python2.7/dist-packages/provisioningserver/boot/uefi.py
On line 146, you need to change shim.efi.signed to shimx64.efi.signed to
reflect the
I should correct myself, the package name where the .py file resides is
actually python-maas-provisioningserver
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1713795
Title:
[1.9] Unable to install
When you had the nvidia drivers installed, can you confirm how you
installed them?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697556
Title:
Computer freezes after login - 4.10.0-22-generic
To
Well, I'm running 4.10.0-33-generic, and although sometimes I have to
login twice, and it has frozen on a couple of occasions, it's pretty
much okay. So I'm not sure what exactly is different about my combo than
yours, except maybe the firmware version I'm running on the 9560.
--
You received
Well, I'm using 4.10.0.28 and nvidia-381 on my XPS 15 9560 and I'm able
to login.
I did update to the latest BIOS version too though (1.34), so maybe that
had an effect, IDK.
It did complain about a plymouthd crash, and I got it to send a report,
so don't know if that will help.
Additionally, using "net.ipv6.conf.lo.disable_ipv6 = 0" to enable ipv6
just for loopback works around the problem, and lsof -i does show epmd
using ipv6 despite specifying only the ipv4 loopback in
ERL_EPMD_ADDRESS.
lsof -i |grep epmd
epmd 30418rabbitmq3u IPv4 458312 0t0
Just to let you know about a possibly interesting edge case which *may*
be related to this bug - if I use "ipv6.disable=1" to disable ipv6,
"export ERL_EPMD_ADDRESS=127.0.0.1" works as expected, if I use
"net.ipv6.conf.all.disable_ipv6 = 1" via sysctl to disable ipv6, I get
"epmd: failed to bind
@AvitarX LZO compression is not a red herring. It only appears to happen
if you have a separate btrfs file-system from root AND you have balanced
it (must be some difference between the way the root filesystem and home
filesystems are checked on boot).
So steps to reproduce are:-
1. Fresh
I tried to get a full backtrace with gdb, It doesn't look right. Perhaps
someone might be able to tell me what I've missed? I did follow the
instructions on debugging Xorg, apport didn't put anything in /var/crash
so that's why I used gdb from another machine instead.
I've not done a backtrace
To work around the problem I've installed libssh-4 from Debian Sid. This
might help someone else seeing as nothing is happening on getting the
update into Maverick.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Lads can we get something done on this. Remmina is a very nice unified
remote access client but SSH is so slow on it with this bug it's
unusable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/663777
Removing indicator-applet-session worked for me. It says it's a clone
maybe that has something to do with it.
--
Battery indicator applet appears in two places
https://bugs.launchpad.net/bugs/569996
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
+1
This issue stops Lucid LXC containers booting after upgrade.
Any chance we can get this patch in, seeing as LXC is supposed to be the
supported containerisation going forward?
--
LXC containers stop working with the newest version of the package
https://bugs.launchpad.net/bugs/632764
You
Ok so, change the name and lets get this sorted once and for all.
--
IMAP/POP3+SSL/TLS are disabled
https://bugs.launchpad.net/bugs/44335
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
My 2 cents worth:-
1. From a purely productive point of view, having the minimize, maximize
and close buttons near the menus saves having to move the mouse pointer
to the opposite side of the screen under certain circumstances.
Personally I would rather waste untold seconds of my life enjoying a
I can confirm that the proposed update works in Jaunty after reboot.
--
zabbix_agentd will not start after reboot
https://bugs.launchpad.net/bugs/96644
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I second that.
On Wed, 2009-07-29 at 21:38 +, Aidan Fitzpatrick wrote:
I agree re removing this package or replacing it with another until this
is fixed. It is insecure and I cannot see why many would use it without
SSL. With SSL it's great, but if we have to repackage ourselves each
Scratch that, I just had to end and restart the existing mail-
notification binary i.e. sudo killall mail-notification and then
restart from the preferences menu and the options appeared. Thanks for
the solution guys.
--
IMAP/POP3+SSL/TLS are disabled
https://bugs.launchpad.net/bugs/44335
You
Hi Andrew and Patrick,
I can report that both of you methods work in that you get a package to
install at the end, however I still have the SSL options greyed out
after installation, any ideas?
--
IMAP/POP3+SSL/TLS are disabled
https://bugs.launchpad.net/bugs/44335
You received this bug
28 matches
Mail list logo
