Public bug reported:
Binary package hint: firefox-3.0
after returning from sleep/hibernate firefox flash video player tears up
or breaks apart constantly. This happens even if I quit firefox, then
return. I must reboot to get a steady flash youtube, etc.
ProblemType: Bug
Architecture: i386
Date:
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/18703637/Dependencies.txt
** Attachment added: "ExtensionSummary.txt"
http://launchpadlibrarian.net/18703638/ExtensionSummary.txt
** Attachment added: "profiles.ini.txt"
http://launchpadlibrarian.net/18703639/profiles
Today I tried to boot kernel 6.8.0-51 again, and it was successful. So,
for me the problem disappeared. I am not sure why. One of the recent
updates (while using kernel 6.8.0-49) was xwayland. Maybe this update
solved the problem.
--
You received this bug notification because you are a member of
The same bug affects me. I use a Lenovo ThinkPad T14 Gen 2 AMD laptop,
with Ryzen 5 PRO 5650U processor.
Ubuntu 22.04 fails to boot after the update (by the Software Updater
application) on Friday 2024-12-20 to kernel Linux 6.8.0-50-generic on my laptop.
A black screen with blinking cursor appear
I can confirm that kernel 6.8.0-51 does not solve the problem. I now
allowed Software Updater to update the kernel to version 6.8.0-51 . The
laptop is unable to boot with the new kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Since the kernel update to 6.8.0-57-generic the problem is almost solved
for me. I have booted the laptop many times, and each time the system
ends up with a black screen.
But every time, I am able to do CTRL-ALT-F2 followed by CTRL-ALT-F1
(meaning: switching to console and back to GUI) and the GU
After booting successfully on 2025-01-24, I booted the laptop many
times, and indeed, it sometimes fails and sometimes succeeds. In fact,
booting (now using the 6.8.0-52 kernel) fails more often than it
succeeds. On average, I estimate, it takes ~5 boot attempts before a
successful one happens. In
I now get the message that an update for "516 -> 20241101" is ready, and
after choosing to install it, it requests a reboot. During reboot, the
update does not happen. After reboot the update is offered again, just
like what happened previously.
Where do these version numbers come from? Why did th
This is still happening for me. The message appears after every reboot, on the
next update check.
I use Ubuntu 22.04 , and the "Secure Boot dbx Configuration Update" is for 502
-> 20241101 .
After installing, a message appears that one has to reboot for this,
with options [Not now / Restart]. Cl
** Tags added: boot secure
** Tags removed: boot secure
** Tags added: secure-boot
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2114672
Title:
Repeated failed install of secure boot dbx configurat
Same problem here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/880657
Title:
stuck retrieving emails from IMAP
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+sou
11 matches
Mail list logo
