> You could detect both parameters to avoid that corner case.
Sure one can check for "splash nomodeset" to avoid the confusion in most
cases, but that wouldn't fix it for "splash $DRIVER.modeset=0" or less
common architectures which might have no primary framebuffer. I guess we
can tell people who
BTW bug 2050743 is making the situation worse on noble. It will be fixed
shortly.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069
Title:
Annoying boot messages interfering with splas
The MUTTER_DEBUG_ENABLE_ATOMIC_KMS worked for me as well, thank you!
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971434
Title:
Display powersave only blanks, but does not turn off
Stat
Brian Murray has proposed merging autopkgtest-cloud:d-a-r-devel-first into
autopkgtest-cloud:master.
Requested reviews:
Canonical's Ubuntu QA (canonical-ubuntu-qa)
For more details, see:
https://code.launchpad.net/~ubuntu-release/autopkgtest-cloud/+git/autopkgtest-cloud/+merge/459753
While it
Thanks for reporting!
** Changed in: auto-package-testing
Status: New => In Progress
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launchpad.net/bugs/2051851
Title:
Error: package does
Known issue, the db is currently incomplete and it's being repopulated
right now. Everything will be back to normal in a couple days I imagine.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Auto Package Testing.
https://bugs.launch
Public bug reported:
I'm currently unable to view the test history of any package using the
web interface, for example:
https://autopkgtest.ubuntu.com/packages/l/linux-nvidia-6.5/jammy/arm64
** Affects: auto-package-testing
Importance: Undecided
Status: New
--
You received this b
You could detect both parameters to avoid that corner case.
Alternatively this is something I feel simpledrm will help you avoid
hitting too.
Otherwise it sounds good to me.
--
You received this bug notification because you are a member of
Canonical's Ubuntu QA, which is subscribed to Ubuntu.
ht
@hui.wang
I have added df -h command to the test and restarted those failing instance,
the free disk space are just 1.9G, I will add a hint with bug 1936305 (No space
left on device) for them this time.
Meanwhile I will discuss with other TNT folks to see if we can bump the disk
size.
--
You r
A new attempt at a kernel patch. While this is pleasingly simple and
reliable in my own testing, it has a bug when "splash" is used at the
same time as there being no primary framebuffer (like with "nomodeset").
I'm not sure if that's a realistic concern and am reluctant to go back
to delays to pap
** Tags added: 5.15 jammy
** Tags added: sru-20240108
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2000901
Title:
aa-logprof complained about libvirt include file not f
After splitting ubuntu_kselftests_ftrace out and run test cases one-by-
one, we can see it's failing with the second test case, ftrace:test.d--
00basic--basic2.tc, on J-intel-iotg-5.15.0-1048.54 with node rizzo.
However I was unable to reproduce this manually on rizzo:
* Passed with running just
** Changed in: linux (Ubuntu Mantic)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/1983357
Title:
test_021_aslr_dapper_libs from
Skia has proposed merging
~hyask/auto-upgrade-testing-specifications:skia/remove_lunar into
auto-upgrade-testing-specifications:main.
Requested reviews:
Canonical Platform QA Team (canonical-platform-qa)
For more details, see:
https://code.launchpad.net/~hyask/auto-upgrade-testing-specificati
Hmm, no plymouthd isn't starting quite early enough in Noble:
2.799s - plymouthd starts
4.080s - first show-splash attempt (rejected because DRM hasn't started yet)
5.290s - found /dev/dri/card0
5.364s - showing splash screen
What this means is that any attempt to fix the bug in plymouthd itself
15 matches
Mail list logo
