--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2054827
Title:
[regression] GUI crashed after installed proposed package after mesa
updates
To manage notifications about this bug go to:
Public bug reported:
...
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubiquity 22.04.15
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Public bug reported:
Ubuntu fails to install
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Public bug reported:
During an impish build of ubuntu-cpc images with magic-proxy enabled,
the installation of certain packages tried to reach an internet endpoint
(specifically http://169.254.169.254/latest/meta-data/instance-id -
which appears to be used for EC2 metadata)
The magic-proxy log
** Package changed: ubuntu => network-manager (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1945801
Title:
Netplan doesn't work with DHCP DNS server
To manage notifications about this bug
Public bug reported:
Network/hardware setup:
pihole running on pi4 with local dns entries. Ex. somehost 192.168.1.10
udm pro configured with a manual dhcp name server giving the pihole's ip address
fresh install ubuntu server on a VMware ESXi host using dhcp
Problem:
from the ubuntu server "ping
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
## Conclusion
Due to the completion of Google's testing and my own verification, I am
marking verification-complete for all releases.
## Notes
Testing of the new Google guest agents was primarily performed by
Google themselves. They have given the +1. In addition, these images
have gone through
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Tags removed: verification-done-hirsute
** Tags added: verification-needed-hirsute
** Tags removed: verification-done-bionic verification-done-focal
** Tags added: verification-needed-bionic verification-needed-focal
--
You received this bug notification because you are a member of Ubuntu
** Tags removed: verification-done-bionic verification-done-focal
verification-done-hirsute
** Tags added: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic verification-done-focal
verification-done-hirsute
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-hirsute
** Tags added: verification-done-hirsute
** Tags removed: verification-needed-bionic
Canonical's public cloud team has verified that images built with the
proposed packages pass the same testing that we do on regular GCE
images.
** Tags removed: verification-needed-bionic verification-needed-focal
verification-needed-hirsute
** Tags added: verification-done-bionic
do you mind providing your grub configuration? (I know you said it was
system default in the other bug), but I'd like to compare it against our
fresh VM boot just to see if anything was awry.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I have been looking into why this has been happening on Azure Ubuntu
VMs, but I have not been able to reproduce:
I'm running:
az vm create --name bug-test --resource-group canonical-patviafore
--location southcentralus --image Canonical:0001-com-ubuntu-server-
focal:20_04-lts:20.04.202107200
@abaealter: I'm trying to reproduce the issue on Azure as that will give
us an environment to investigate this bug a bit better, and I was not
able to. Do you mind providing a little more information about your
Azure environment?
Do you have the URN that you are running with (if you don't know
** Tags added: rls-ii-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1938299
Title:
Unable to SSH Into Instance when deploying Impish 21.10
To manage notifications about this bug go to:
Public bug reported:
During cloud builds of riscv64 (impish), we do a u-boot-update inside
our chroot.
With version 4.0.3ubuntu1, the command fails with the following error
message:
/usr/sbin/u-boot-update: line 92: syntax error near unexpected token
`<<<'
We did not see this error with
I have done testing on minimal images built from 2.664.19 livecd-rootfs
and run them through qemu to verify they still boot. I have also tested
cloud-specific images to make sure they do not double boot as part of
this change.
** Tags removed: verification-needed verification-needed-focal
** Tags
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Pat Viafore (patviafore)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1920043
Title:
Latest Focal Minimal disk images f
Commit 4c504f678178104eceaf5b3aae40bcff20863235 needs to be backported
to Focal to 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/1920043
Title:
Latest Focal Minimal disk images from
Public bug reported:
[Impact]
* Minimal images built from livecd-rootfs after March 12th do not boot.
There are no broken images on cloud-images.ubuntu.com, but no further
images will be published until this is fixed. Cloud-specific minimal
images are unaffected, as they do the proper steps in
I have tested the changes in livecd-rootfs 2.664.18. Generic cloud
images (qcow2, kvm, etc) cloud images now boot with an initramfs and
don't have a double boot (tested with QEMU). I've also tested various
cloud images (AWS, Google, Azure, Oracle) that have custom cloud kernels
(which make use of
** Description changed:
- A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
- 20.04 by “do-release-upgrade –d”.
+ [Impact]
+ Generic cloud images will boot without initramfs, fail, and then fall back,
resulting in a double boot performance hit
+
+ [Test Case]
+ Load up cloud
Thank you for doing that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1327801
Title:
Bightness and contrast settings have no effect
To manage notifications about this bug go to:
Ideally, whoever wrote the original patch would be involved, because I
assume his gamma fix was pertinent to some piece of hardware available
to him, just happened to break the Canon LiDE scanners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Just looking at the log, it seems that unused-parameter error is
enabled. I don't know how your pipeline works, but it's not dpkg-
buildpackage, so it makes sense that the default CFLAGS (or CXXFLAGS) is
set.
genesys/low.cpp:636:76: error: unused parameter 'sensor' [-Werror
=unused-parameter]
Sure, I used `dpkg-buildpackage -b``` to build it.
The change was just to remove the offending condition as was suggested:
diff -ur sane-backends-1.0.29.orig/backend/genesys/low.cpp
sane-backends-1.0.29/backend/genesys/low.cpp
--- sane-backends-1.0.29.orig/backend/genesys/low.cpp 2021-02-16
Hi Gunnar,
Perhaps there is a mistake in that report. I certainly witnessed it in
1.0.29 on Ubuntu 20.04 and 20.10. I don't think it was an issue before
that version, and it's unlikely to have been, as the revision that broke
it was put in October 17, 2019; not certain about which specific
I have tracked the issue down to an upstream issue with sane-backends,
with a fix here:
https://gitlab.com/sane-project/backends/-/issues/271
This is not a simple-scan bug.
** Bug watch added: gitlab.com/sane-project/backends/-/issues #271
Here is some debug output when a scan is initiated.
The brightness and contrast values do seem to apply from the front-end:
[+16.68s] DEBUG: scanner.vala:1674: Scanner.scan
("genesys:libusb:001:010", dpi=600, scan_mode=ScanMode.GRAY, depth=2,
type=single, paper_width=2159, paper_height=2794,
Like Michael in #17, I noticed that since around 20.04 my Canon LiDE 35
has no brightness-contrast control, making simple-scan unusable for me.
I've worked around by using other software, but it's starting to bug me
as more stuff needs to be submitted online in today's world.
--
You received
As an update to this bug:
The work to SRU has stalled, as we have found a regression
(https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1902260).
Once a fix is SRU'd to Groovy, I'll pick up the fix and SRU it back to
Focal.
--
You received this bug notification because you are a
Public bug reported:
Once again Apparmor policies are constantly disabled for Firefox.
-I've reported this bug in December, then came a patch, then for the last month
of January - regardless of updates, Firefox profiles are skipped.
- You cannot be serious?
-This is a consistent seccurity
Hi richmbx,
I am currently working this, and currently doing testing to make sure it
has integrated with Focal correctly. I expect it to begin the SRU
process in the next day or so.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've confirmed that this has been fixed in the latest Xenial Vagrant
box.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596
Title:
Xenial & bionic vagrant box disk size is too small
To manage
Version 2.408.65 of livecd-rootfs has fixed this issue.
Test case:
Built a box with the version of livecd-rootfs
vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name xenial-test
vagrant init xenial-test
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk
Public bug reported:
32.0.0.465ubuntu0.20.04.2 removed Flash from my system!
It's not okay to remove plugins the user may be using without their
permission. I need this plugin for work, and now I can't find a good way
to reinstall it.
** Affects: flashplugin-nonfree (Ubuntu)
Importance:
I can't speak for 3D, but seeing as the 2D rendering is still loads
quicker than canvas, the "performance caveat" really isn't.
What should PIXI, or any site, do with this information?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
(In reply to Jeff Gilbert [:jgilbert] from comment #24)
> (In reply to Pat Suwalski from comment #20)
> > (In reply to Jeff Gilbert [:jgilbert] from comment #19)
> > > Honestly at this point I'm tending towards #2.
> > > Websites had the chance to handle this well a
(In reply to Jeff Gilbert [:jgilbert] from comment #19)
> Honestly at this point I'm tending towards #2.
> Websites had the chance to handle this well and they have bungled it, so I
> think we should disable failIfMajorPerformanceCaveat as it stands today.
Are you suggesting PIXI doesn't handle
Although Firefox 84b2 from official binaries worked fine, Firefox 84.0
from official binaries (firefox-84.0.tar.bz2) does not.
Setting ```gfx.webrender.all``` as suggested above *does* work.
This appears to be a capability detection issue.
--
You received this bug notification because you are
Setting gfx.webrender.all as recommended in the upstream bug makes it
work. It seems some detection code is broken.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks
Can anyone point me to where I can find the Firefox 82 debs? They seem
to have disappeared from /var/cache/apt/archives, and I really need
them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905054
The Firefox 84 WebGL section looks a lot like the v83 section:
HW_COMPOSITING
available by default
blocked by env: Acceleration blocked by platform
OPENGL_COMPOSITING
unavailable by default: Hardware compositing is disabled
WEBRENDER
available by default
disabled by env: Not
Despite it working in The Firefox 84 beta, the Ubuntu build that came
out does not work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
To manage
Version 2.525.48 of livecd-rootfs has fixed this issue.
Test case:
Built a box with the version of livecd-rootfs
vagrant box add build.output/livecd.ubuntu-cpc.vagrant.box --name bionic-test
vagrant init bionic-test
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk
Can you guys try the Firefox 84b2 build? I tried it from the tarball and
it worked perfectly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
Firefox 83 Breaks WebGL
To manage
If I were to speculate, someone tried to fix the "blocked by env" errors
in Firefox 82, in the process actually making that statement true with
some kind of fail code. In 84 they may have actually fixed whatever the
root problem reporting that message.
--
You received this bug notification
I can verify that the beta snap works as well, but I thought you said in
comment #2 that is a binary build straight from mozilla.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905054
Title:
It's the "Acceleration blocked by platform" bits that are interesting.
It seems that message is there in v82 where it works and v83 where it
doesn't. The apparmor check seems relevant with that angle, I just want
to make sure that it's not something related to Ubuntu.
If it continues to work in
I just realized that the about:support output above is actually for
Firefox 82, which is odd, because it does work even though the output
suggests it shouldn't.
Here's a lot for Firefox 83.
The relevant section is different once again:
Decision Log
HW_COMPOSITING:
available by default
blocked
I just realized that the about:support output I supplied above is from
firefox 82. I am confused by the HW_COMPOSITING section, when it clearly
works in v82.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Indeed, I downloaded firefox-84.0b4.tar.bz2 and WebGL works correctly in
that build.
On 84, compared to 83 above:
Decision Log
HW_COMPOSITING
available by default
OPENGL_COMPOSITING
available by default
WEBRENDER
available by default
WEBRENDER_QUALIFIED
available by default
Here is the output of about:support. I suspect this is the relevant
part:
Decision Log
HW_COMPOSITING:
available by default
blocked by env: Acceleration blocked by platform
OPENGL_COMPOSITING:
unavailable by default: Hardware compositing is disabled
WEBRENDER:
opt-in by default: WebRender is an
Thanks for the ideas.
drm driver as listed from lsmod:
drm 491520 9 drm_kms_helper,i915
I tried the snap and it behaved the same way, the exact same console
output. The snap was version 83.0-2 via snapcraft.io.
I assume by "xrg" you mean "xorg"? I have not tried under an xorg
Public bug reported:
Upon upgrading from Firefox 82 to to Firefox 83, WebGL stops working.
Ubuntu 20.10 with Wayland.
When I try to launch a webGL game:
Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not
hardware-accelerated.
Specifically Pixi says:
Error: WebGL
This appears to be the same issue or at least related
** Attachment added: "Kernel 5.8.0-25 fails Builds correctly for
5.4.0-52-generic-x86_64"
https://bugs.launchpad.net/ubuntu/+source/r8168/+bug/1889124/+attachment/5432706/+files/make.log
--
You received this bug notification because
Public bug reported:
Hi, I do nknow what to write in here
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ptex-jtex 1.7+1-15
ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
Uname: Linux 5.4.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
Public bug reported:
We have most reliably reproduced this on a Standard_B1s in Azure in the
North Europe region (>80% of the time). Tests in other regions/VM types
do not show this failure as often (<1%). We have reproduced this in
Xenial, Bionic, Focal, and Groovy. We saw an increase of test
Thank you @ianchanning for the recovery notes through the portal.
I'll also add in a few links that might help.
For users looking for general recovery steps :
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass#Recovery
For users looking how to mitigate this before
** Summary changed:
- Elan touchpad fingerprint reader is not recognized by ubuntu 18.10
+ Elan touchpad fingerprint reader is not recognized by ubuntu 18.10 and 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using Ubuntu 20.04 and I have Elan fingerprint reader 04f3:3057 that cannot
work yet.
I hope you can solve the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811368
Title:
Elan touchpad
I have this issue too on Ubuntu 16.04.6 LTS with ppa version ;
I have a second version that I updated directly from Mozilla beta
channel installed in the opt folder that was update from 78.0 b9 and
work without any crash
If this can help
--
You received this bug notification because you are a
We are seeing some failures still in Eoan (not Focal) with tracebacks
involving growpart:
2020-05-29 10:14:29,218 - util.py[DEBUG]: Running module growpart () failed
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 851, in
_run_modules
** Description changed:
[Impact]
Users could not use vagrant boxes as a full computer (or anything requiring
more than 10G of memory). This was a regression from our behavior in 14.04
[Test Case]
vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64
as
** Description changed:
- The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with
- the trusty box.
+ [Impact]
+ Users could not use vagrant boxes as a full computer (or anything requiring
more than 10G of memory). This was a regression from our behavior in 14.04
+
+ [Test Case]
** Merge proposal unlinked:
https://code.launchpad.net/~patviafore/livecd-rootfs/+git/livecd-rootfs/+merge/384634
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596
Title:
Xenial & bionic
** Also affects: cloud-images/bb-series
Importance: Undecided
Status: New
** Also affects: cloud-images/x-series
Importance: Undecided
Status: New
** No longer affects: cloud-images/bb-series
** No longer affects: cloud-images/x-series
--
You received this bug notification
** Changed in: livecd-rootfs (Ubuntu)
Assignee: (unassigned) => Pat Viafore (patviafore)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580596
Title:
Xenial & bionic vagrant box di
This is now fixed, thank you
** Changed in: cloud-images
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876139
Title:
Groovy cloud-images failing during growpart
To
We're wary of fdisk being in a seed for cloud-image, because we want to
make sure we remain consistent with the rest of the distro and bringing
an old package forward with us (say if we as a distro move towards
gdisk).
I'm good with cloud-init depending on fdisk (or sometime in the future,
gdisk)
Yes, we see it on Eoan and blocking tests, so if you could SRU it there,
it'd be much appreciated. We have never seen it on Bionic to my
knowledge.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, we were waiting on a bug regarding dictionary keys being modified
to resolve before we could verify this. We have not seen this in the
past couple of runs in our testing, so I think we're good to proceed.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
We are no longer seeing this issue with the latest images.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063
Title:
[Hyper-V] KVP daemon fails to start on first boot of disco VM
To manage
Nouveau was blacklisted in our images, so I am no longer seeing this
problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841827
Title:
Install of linux-modules-nvidia requires a reboot before
Adding in a passing version of journalctl
** Attachment added: "passing_journalctl_output.txt"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5326024/+files/passing_journalctl_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I'm attaching the output of a failing build
** Attachment added: "failing_journalctl_output.txt"
https://bugs.launchpad.net/cloud-init/+bug/1834875/+attachment/5325941/+files/failing_journalctl_output.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I have tested in Bionic, Xenial and Eoan.
I've done reboot testing, verified that waagent is running, and that
waagent booted with no errors. I have also performed our automated
Azure testing suite on each image.
It looks good from our end.
--
You received this bug notification because you
I can get that going, and will report back on this bug when I have more
information.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1834875
Title:
cloud-init growpart race with udev
To manage
For those looking for a workaround in the meantime, I've found that
lxqt-config-brightness -i and lxqt-config-brightness -d on the command
line are still able to control the screen brightness in my setup.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
I now update the graphic driver and ubuntu 19.10 freezes from the start.
Reboot is necessary.Multiple times until it works.
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Can it be a graphic card issue when i am having the problem -Computer
partially freezes and software updater will not respond. This also
happens at different times.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Converted to question:
I am not sure how I should check that ? I down graded because i was
having problems.
Am 17.12.19 um 08:56 schrieb Kai-Heng Feng:
> Does this issue happen if proprietary Nvidia driver is used instead?
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
i first thought that it is a graphic issue. but update Manager freezes as well.
that does not block ubuntu but but some programs we
hen they freeze do
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-5.3.0-24-generic 5.3.0-24.26
ProcVersionSignature: Ubuntu
I have run our tests and am satisfied with the results. Our tests very
closely matches what mruffell posted.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial images won't reboot
I have re-ran my test cases and the package you provided fixes the
original issue that we saw.
Thank you
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1840686
Title:
Xenial images won't reboot if
I have tested this package in bionic-proposed, and all of my test cases
passed.
Tests cases:
Testing NVIDIA drivers install on non-GPU instance does nothing
Testing NVIDIA drivers install on GPU instance
Specifying different versions for NVIDIA drivers install
--
You received this bug
So after doing a little more digging:
A modprobe -r nouveau will fix this. After issuing this command, an
install does not require a reboot for nvidia-smi to find the driver.
We are planning on blacklisting the module in our cloud images to
address this.
--
You received this bug notification
Public bug reported:
When installing linux-modules-nvidia-418-generic using apt, I expect the
nvidia driver to be available immediately after the install completes.
However, I must reboot before nvidia-smi returns driver information.
AS a side note: sudo udevadm control --reload && sudo udevadm
** Description changed:
CPC team has recently converted Xenial images to use GPT instead of MBR.
However, after booting an instance that has a disk size of 2049 GB or
higher, we hang on the next subsequent boot (Logs indicate it hanging on
"Booting Hard Disk 0".
This works on Bionic,
At first I thought it was related to
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=1e19b01be31fc5264a84d246023ecf29e44949df=25=0=0,
and later I thought it was related to
https://bugs.launchpad.net/bugs/1762748. However, I added the bionic
archives to my Xenial instance and
Public bug reported:
Relevant system information here:
https://pastebin.canonical.com/p/q6XqWt6THQ/
I was expecting that when I installed linux-modules-nvidia-generic-418
that I would get an option to accept or reject a EULA. However, on
installation, no prompt is given to me, and after a
Public bug reported:
CPC team has recently converted Xenial images to use GPT instead of MBR.
However, after booting an instance that has a disk size of 2049 GB or
higher, we hang on the next subsequent boot (Logs indicate it hanging on
"Booting Hard Disk 0".
This works on Bionic, but what makes
1 - 100 of 8827 matches
Mail list logo
