We had a problem with our recovery VM switching the disk names so here's
a minor modification from [comment
#16](https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1889509/comments/16)
to first run `lsblk` to check for the correct disk before running `mount
/dev/sdc1`:
$ sudo su -
# lsblk <--
Had a quick chat about it. At the moment cloud-init uses just one
trasaction, thus it's not quite possible to add more units to it, unless
they were already there. Hence we bake networkd as enabled in our cloud-
images.
It would be nice if cloud-init subverted boot a little bit, by diverting
The issue is super small text in all GDM and GNOME Shell elements when
the display is being driven by NVIDIA graphics. The problem is caused by
the patch in the title. If you switch to Intel graphics, the text is
back to normal. If you switch to NVIDIA, the text shrinks down to what
looks like 50%
To maintain a respectful atmosphere, please follow the code of conduct -
http://www.ubuntu.com/project/about-ubuntu/conduct. Bug reports are
handled by humans, the majority of whom are volunteers, so please bear
this in mind. Venting frustration in a bug report isn't fine.
The bug is triaged with
I've confirmed that this is the case. The Pi refreshes the kernel to
179, reboots and tries to run the 179 kernel with the 156 DTBs. We're
not maintaining DTB backwards compatibility, so not a kernel problem.
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Invalid
--
You
** Bug watch added: Debian Bug tracker #966575
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966575
** Changed in: grub2 (Debian)
Importance: Undecided => Unknown
** Changed in: grub2 (Debian)
Status: New => Unknown
** Changed in: grub2 (Debian)
Remote watch: None => Debian
** Changed in: python-taskflow (Ubuntu Groovy)
Status: Triaged => 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/1882900
Title:
[SRU] Missing sqlalchemy-utils dep on ussuri
To
> Bug reports should stick to fact, using wording like 'Snap-mangled'
I'm sorry, that's factually what happened. Should I have worded it Snap-
disfigured, Snap-distorted, Snap-impaired or Snap-wrecked instead?
> isn't appropriate and not a basis for any discussion.
I have **never** had any
Verified xenial/queens (the updated packages got uploaded compared to
the check in comment #45):
lxc launch ubuntu:xenial oslop-xq
Creating oslop-xq
Starting oslop-xq
lxc exec oslop-bq bash
root@oslop-xq:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dolphin (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798857
Title:
Hi! I see a similar issue with the latest (development) netplan, where
some OVS services are triggered via systemd service units (same as
wpa_supplicant service units in the case of WiFi).
On first boot (with cloud-init user.network-config provided [0]) I can
see that the services are not being
OK, I didn't mean to have a guarantee but just a flavour.
I bougth the new GPU, also because in the process of renewing a bit my old
machine, replacing the GPU was quite needed anyhow.
In case it won't work properly I'll give it back, but I'm confident
it'll work.
Thanks for your support.
--- Comment From stefan.haberl...@de.ibm.com 2020-07-31 07:14 EDT---
This is currently not supported.
As of today there is no code in zipl that writes signature entries for a dump
kernel.
This was not part of the initial item.
It might be addressed in the future.
--
You received this
This is really amazing. I still have the same problem.
And yes, it is NOT triaged.
I have Ubuntu 18.04.4 LTS. LibreOffice is version 6.0.7.3.
I would expect some things just work in 21tg century. But obviously, I
am wrong.
Maybe the problem is, that Ubuntu developers does not use encryption
Fix proposed to branch: stable/train
Review: https://review.opendev.org/744125
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled
Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/744127
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled
Fix proposed to branch: stable/queens
Review: https://review.opendev.org/744128
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled
** Package changed: linux (Ubuntu) => cdk
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: cdk
Assignee: Skipper Bug Screeners (skipper-screen-team) => CDK (cdk8s)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug
Fix proposed to branch: stable/stein
Review: https://review.opendev.org/744126
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881771
Title:
neutron-ipset-cleanup fails with Traceback: Unhandled
I have run some additional tests on bionic and focal desktop VMs with
lvm (and lvm+luks) - no boot issues were observed with the -proposed
builds.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
After the rescue via live USB stick one can halt updating of the grub
packages till a proper fix is available. I've done it with "dselect"
(hotkey "H").
*== Opt admingrub-pc amd64 i386 2.02-2ubunt 2.02-2ubunt
*== Opt admingrub-pc-bin amd64 i386 2.02-2ubunt
Public bug reported:
Steps to reproduce:
LXD setup and juju installation are done following these instructions
https://ubuntu.com/kubernetes/docs/install-local
Kubernetes Core bundle is installed as described here
https://jaas.ai/kubernetes-core with
juju deploy cs:bundle/kubernetes-core-1069
I can't be sure that buying a new GPU will solve the problem so that is
at your own risk and expense... But such a new(er) GPU does support
Nvidia's latest drivers. In fact I've been using a GT 1030 in recent
months for my own Nvidia-related work in Ubuntu 20.10. And that card is
roughly 7x more
@maxf So, I think you need to reinstall grub via rescue live cd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error : "symbol 'grub_calloc' not found
To manage
Public bug reported:
Steps to reproduce:
LXD setup and juju installation are done following these instructions
https://ubuntu.com/kubernetes/docs/install-local
Kubernetes Core bundle is installed as described here
https://jaas.ai/kubernetes-core with
juju deploy cs:bundle/kubernetes-core-1069
My resync is working fine again. Thanks for your attention to this bug-
report.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888685
Title:
rsync fails after installing level 3.2.1
To manage
Please tell me in details. How to resolve this issue.
On Fri 31 Jul, 2020, 3:11 PM Sebastien Bacher, <1889...@bugs.launchpad.net>
wrote:
> ** Package changed: ibus-m17n (Ubuntu) => ttf-indic-fonts (Ubuntu)
>
> --
> You received this bug notification because you are subscribed to the bug
>
Just did
apt update
apt upgrade
autoclean etc.
Rebooted into this.
Have 20.04 low latency running on HP Pavillion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error :
Oh Sorry Frank,
I misread the bug title, I thought this was for KVM kernel.
For s390x KVM, the test has been blocked by the MAAS issue, I will change the
status back to confirmed and keep an eye on this when we can test it again.
Thanks
** Changed in: ubuntu-z-systems
Status: Fix
Public bug reported:
10_linux was changed to exit early if / is zfs. That doesn't work if /boot is a
ext4 filesystem which should be detected by the rest of 10_linux.
The result is that grub doesn't create any entries for any kernels and the
system isn't bootable, manual intervention is
I tested an ISO image with bionic-proposed enabled [1] and I can confirm
livecd-rootfs 2.525.45 fixes this bug.
[1] https://people.canonical.com/~ubuntu-archive/cd-build-logs/ubuntu-
server/bionic/daily-live-20200729.1.log
--
You received this bug notification because you are a member of Ubuntu
This bug was fixed in the package livecd-rootfs - 2.525.45
---
livecd-rootfs (2.525.45) bionic; urgency=medium
[ Francis Ginther ]
* Use the linux-raspi-hwe-18.04 kernel for raspi3 classic image builds.
(LP: #1889188)
[ Michael Hudson-Doyle ]
* Backport snap seeding and
This bug was fixed in the package livecd-rootfs - 2.525.45
---
livecd-rootfs (2.525.45) bionic; urgency=medium
[ Francis Ginther ]
* Use the linux-raspi-hwe-18.04 kernel for raspi3 classic image builds.
(LP: #1889188)
[ Michael Hudson-Doyle ]
* Backport snap seeding and
Public bug reported:
I've tried to install openstack/tacker on Ubuntu20.04, but failed
because for gnocchi possibly. Tacker's monitoring depends on ceilometer
and it uses gnocchi. On Ubuntu20.04, devstack installation fails for
duplicated check constraint name in `gnocchi-upgrade` which is an
The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package is now being 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 you
This bug was fixed in the package livecd-rootfs - 2.525.45
---
livecd-rootfs (2.525.45) bionic; urgency=medium
[ Francis Ginther ]
* Use the linux-raspi-hwe-18.04 kernel for raspi3 classic image builds.
(LP: #1889188)
[ Michael Hudson-Doyle ]
* Backport snap seeding and
This bug was fixed in the package livecd-rootfs - 2.525.45
---
livecd-rootfs (2.525.45) bionic; urgency=medium
[ Francis Ginther ]
* Use the linux-raspi-hwe-18.04 kernel for raspi3 classic image builds.
(LP: #1889188)
[ Michael Hudson-Doyle ]
* Backport snap seeding and
Checked our latest proposed based bionic dailies and confirmed that the
right kernel (linux-raspi-5.4*) got pulled in via the build logs:
https://launchpadlibrarian.net/490970026/buildlog_ubuntu_bionic_armhf_raspi3_cpc_BUILDING.txt.gz
** Tags removed: verification-needed
The verification of the Stable Release Update for livecd-rootfs has
completed successfully and the package is now being 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 you
Im considering, as your suggestion in the other post, to buy a new GPU (GeForce
GT 1030) and for example I've seen the following on Amazon, with also Prime so
I would get it tomorrow:
- Gigabyte GT 1030 Low Profile 2G - graphics cards (NVIDIA, GeForce GT 1030,
4096 x 2160 pixels, 1257 MHz, 1506
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
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/1809639
@ianchanning Yes, that's easy enough, but I was actually looking for a
way to prevent that for machines that haven't received the grub update
yet :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thank you for your bug report but to maintain a respectful atmosphere,
please follow the code of conduct - http://www.ubuntu.com/project/about-
ubuntu/conduct. Bug reports are handled by humans, the majority of whom
are volunteers, so please bear this in mind.
Bug reports should stick to fact,
I created a new horizon host on focal and installed openstack-dashboard.
openstack-dashboard:
Installed: 3:18.3.2-0ubuntu0.20.04.1
apache error log showed many errors about missing policy files
admin panel was visible while logged in as non-admin user
I enabled focal-proposed and upgraded
** Changed in: chromium-browser
Status: New => Invalid
** Changed in: chromium-browser (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887804
Title:
@mavink - you only need the one recovery VM - you can attach and detach
all the broken OS disks to that.
Potentially you can script all the steps on the recovery VM, and you can
script all the azure steps using the Azure CLI. You can translate all
the steps I did via the portal to be via the CLI
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889375
Title:
Fix right speaker of HP laptop
To manage
Thanks, it's probably better if you could report it directly to the
software writers on
https://gitlab.gnome.org/GNOME/seahorse/-/issues
** Changed in: seahorse (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I would be curious to see what a fresh install looks like. Because when
you first started reporting these bugs you had disabled the open source
driver in the kernel, didn't have the proprietary driver installed, and
had installed a custom unsupported kernel. So I am still skeptical that
some of
Sorry but there is no recording on how and when the key was change,
could be that you used some configuration interface that includes a such
option. Anyway closing since it's not really a bug in the software
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I would be curious to see what a fresh install looks like. Because when
you first stated reporting these bugs you had disabled the open source
driver in the kernel, didn't have the proprietary driver installed, and
had installed a custom unsupported kernel. So I am still skeptical that
some of
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command, as it will
automatically gather debugging information, in a terminal:
apport-collect 1415502
When reporting bugs in the future please use apport by using 'ubuntu-
bug' and
Ideally that would be reported upstream on
https://github.com/transmission/transmission
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1415502
Title:
Couldn't bind port 51413 on 192.168.1.xxx:
That#s a spin off of the already Fix Released ticket LP 1888654
** Package changed: linux (Ubuntu) => binutils (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Importance: Undecided => High
** Changed in: binutils
** Package changed: ibus-m17n (Ubuntu) => ttf-indic-fonts (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889630
Title:
In Gujarati Font "Pra" is not proper rednder E.g. Prakash world is
Running "sudo dpkg-reconfigure grub-pc" before reboot is not working for
me - prompts for some settings, but doesn't prompt for drives to
install. I'm running Ubunutu 18.04 on AWS EC2 T3 instance. Rebooting
after this still results in the issue.
Post-issue recovery as described by Marin works
I ran into this grub error during boot after upgrading my Desktop Ubuntu
20.04 to Kernel 5.4.0.42.45 and Grub 2.04-1ubuntu26.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub
I installed the OS 3 times in the last two weeks to get rid of the
nvidia problem without any success :-(
I was hoping to find a way to identify in the logs what's going wrong
because a fresh install won't solve the problem.
--
You received this bug notification because you are a member of
I ran into this grub error during boot when upgrading my Desktop Ubuntu
20.04 to Kernel 5.4.0.42.45 and Grub 2.04-1ubuntu26.1.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot
xenial verification:
Tested with 1.66.27+2.02_beta2-36ubuntu3.27 from -proposed.
Boots successfully in BIOS mode.
Timestamps updated in EFI mode.
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial
** Tags removed: verification-needed
** Tags added:
** Package changed: linux (Ubuntu) => etcd-snaps
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Changed in: etcd-snaps
Assignee: Skipper Bug
That's actually good news then. If you can safely wipe the machine and
reinstall then it sounds like a fresh install might eliminate whatever
the cause of the problem is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886908
Title:
Add support for Atlantic NIC firmware v4
To manage
No, your system is not affected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889509
Title:
grub boot error : "symbol 'grub_calloc' not found
To manage notifications about this bug go to:
It was Ubuntu 20.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889541
Title:
Booting Ubuntu with Nvidia-340 gets stuck on a plain purple screen
To manage notifications about this bug go to:
Hey Folks,
Does the -proposed changes get automatically integrated to -updates
after a certain time has passed, or does this require somebody to take
action?
It would be great to have this update rolled out to 18.04 before OVS
2.14 is released in a week or two.
Regards, -Harry
--
You received
I have also attempted to verify xenial (using version
1.66.27+2.02_beta2-36ubuntu3.27), however grub-efi-
amd64-signed_1.66.27+2.02_beta2-36ubuntu3.27 still seems to be
unavailable in -proposed (http://archive.ubuntu.com).
I have manually downloaded it and tested from here [1], however I'll
OK, so the directory being in /home is the culprit, I could reproduce
the issue and found where the problem is. At some point rsync added
ProtectHome=on
option to its service file, /lib/systemd/system/rsync.service. This has been
reverted in upstream git at [1] as it's too restrictive. The
--- Comment From heinz-werner_se...@de.ibm.com 2020-07-31 04:33 EDT---
IBM Bugzilla status-> closed, Fix Released with groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888654
Title:
Public bug reported:
== Comment: #0 - Heinz-Werner Seeck -
2020-07-31 03:28:30 ==
On z13 we have that vector alignment hints are already accepted. This backport
enables GAS to accept such hints not only for target z14 but also for z13.
Since GCCs default target on Ubuntu is z13 for s390x, we
focal verification:
Tested with version 1.142.4+2.04-1ubuntu26.2 from -proposed using the above
test case.
Boots successfully in BIOS mode.
Timestamps updated in EFI mode.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification
@roman-shipovskij, i don't have an installed grub-pc in my system, when
i try to install it i see next:
sudo apt install grub-pc
Чтение списков пакетов… Готово
Построение дерева зависимостей
Чтение информации о состоянии… Готово
Будут установлены следующие дополнительные пакеты:
I don't think your choice of hard drive is causing this problem. And
your kernel log reports no errors with the Crucial SSD...
When it was working 2 weeks ago, was that Ubuntu 20.04 or an older
version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Default Comment by Bridge
** Attachment added: "syslog from etcd node"
https://bugs.launchpad.net/bugs/1889740/+attachment/5397356/+files/etcd_syslog
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
** Tags removed: targetmilestone-inin2004
** Tags added: targetmilestone-inin2010
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888654
Title:
[UBUNTU 20.10] Accept vector alignment hints on z13
This is not failing anymore on KVM kernels.
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because
For the test itself, this can be fixed with
https://github.com/torvalds/linux/commit/cbd965bde74c3d0e53798404fd4b9829a68ccec8
#diff-71290e3874c89695bb4bc63f892d5c93
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
Steps to reproduce:
Clean Z LPAR machine. Ubuntu 18.04.4 is inatalled. Followed official
documentation to install Charmed Kubernetes
https://ubuntu.com/kubernetes/docs/install-local.
Actual results:
Cluster did not start and hang in the follow state:
# juju status
Model
** Also affects: binutils (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: binutils (Ubuntu Groovy)
Importance: Undecided
Assignee: Skipper Bug Screeners (skipper-screen-team)
Status: Fix Released
** No longer affects: binutils (Ubuntu Focal)
--
You
Just run sudo dpkg-reconfigure grub-pc before rebooting:
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/GRUB2SecureBootBypass?WUwbDVmRWk5RCtJZ2IyNUU2SyJ9#Known_issues
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
- TBD
+ [Impact]
+
+ If the socket buffer array of a tap queue is full, a received package
+ needs to be dropped. Currently, the check for the array being full is
+ performed lockless, which might lead to use-after-free errors if the
+ socket buffer array has been
I actually think it must be somehow related to my configuration, because
in my previous installation in the same machine (I had to install a
fresh new Ubuntu around 2 weeks ago after an HDD major crash), I was
able to install nvidia-340 drivers.
The only difference between the old and the new
Thanks, but there is another error relates to snaps please see
attachment ,should I continue and don't bother with this error
** Attachment added: "snap- error"
Tested on an AMD renoir machine,the dmic was detected from ACPI table.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Checked the module name, it is changed. and could be loaded on the
machine.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872383
Title:
blk_update_request error when mount nvme partition
To
Thanks. That's very interesting. I've only ever seen Ubuntu get stuck on
that purple screen when there was a graphics driver bug (it was the
VMware driver last time - bug 1832138). So that makes me think there's a
problem with the nvidia-340 driver, OR it could mean some fallback
codepath in
Hello all! somebody have this issue on Ubuntu 18.04 desktop with
encrypted lvm partition? because i am installed these updates yesterday,
but without reboot. I will glad for your advices about this issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
TBD
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: Incomplete
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1889735
and then change the status of the bug to 'Confirmed'.
If, due to the
bionic-verification:
Tested with version 1.93.19+2.02-2ubuntu8.17 from -proposed using the test case
in the description.
Boots successfully in BIOS mode.
Timestamps were updated in EFI mode.
** Tags removed: sts verification-needed-bionic
** Tags added: verification-done-bionic
--
You
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Changed in: linux (Ubuntu)
Status: Incomplete => 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/1887904
Title:
Random reboots
To manage notifications about this bug go to:
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
** Changed in: freshplayerplugin (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889325
Title:
RM freshplayerplugin groovy release, groovy-proposed
To manage
201 - 300 of 337 matches
Mail list logo
