At all startup time with recently installed 22.04.1 LTS screen flashing occurs, only close of the laptop screen stops tyhe flashing and allows to correctly login.

[Labar]

I do remember such BIOS related issues back in 2019
for now I do have the list of the kernel error messages
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: labdom 3949 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2019-07-15 (1130 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
 Bus 001 Device 003: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse
 Bus 001 Device 002: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook N7x0WU
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=ea604268-2faf-42c2-abf5-69e0de92b334 ro quiet splash acpi=force vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-46-generic N/A
 linux-backports-modules-5.15.0-46-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.4
Tags: jammy wayland-session
Uname: Linux 5.15.0-46-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-08-17 (2 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/06/2018
dmi.bios.release: 7.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 7.12
dmi.board.asset.tag: Tag 12345
dmi.board.name: N7x0WU
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.13
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.12:bd09/06/2018:br7.12:efr7.13:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: N7x0WU
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook

[Labar (labdom)]

I do have mp4 file showing the error messages at startup before the flashing ...
Q? I do have a screen capture of the mp4 movie embedded into a gmail.
On which mail address should it be possible to send you the mail.
Regards
labdom

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Libera.chat.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1986976/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Labar (labdom)]

still gathering traces, ready in the next hours ....

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

  apport-collect 1986976

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

apport information

[Labar (labdom)]

chronological information : This kind of problems (flashing screen, during boot, logoff or suspend) occured with 18.04 in July 2019 (at install of my new laptop) - With the software update dated around 21Jan2020 on 18.04 the problems were definitely fixed even with 20.04 install on 6oct2020. Problem was viable (avoiding some features) but I never opened an issue !

current problem arose a few days ago after upgrade to 20.04.1 - I seems to me strictly related to my multi-processor installation.
Boot messages are the folowing N double lines about PR01 up to PR07 symbols
ACPI Error Aborting method \_PR.PR01._CPC due to previous AE-NOT-FOUND 20210730
ACPI BIOS Error could not resolved psparser-529 symbols (and other line numbers in seq)

[Daniel van Vugt (vanvugt)]

Please try adding these kernel parameters:

  i915.enable_dc=0 intel_idle.max_cstate=2

(from bug 1958191)

[Labar (labdom)]

What I did according https://wiki.ubuntu.com/Kernel/KernelBootParameters?_ga=2.33092154.52927536.1661185095-1335890214.1657710128

1. under a terminal : sudo gedit /etc/default/grub
2. insert the parameters as on conversation#25 after the word splash + one space
3. save the file
4. sudo update-grub
5. restart

The "flickering" still occurs !

[Labar (labdom)]

oh sorry I have to rectify.
I was probably too fast to report or I did a cold start in the subsequent tests, no more sure.
But, now the "flickering" does not happen anyway in any scenari oy logout power off, suspend or restart.
Only the restart process is still verbose and shows ACpi Error kind messages (it is viable)
so far,
will continue to try and report within 24 hours
Thanks, anyway

[Daniel van Vugt (vanvugt)]

ACPI errors are theoretically BIOS bugs, not Linux bugs. Although the fact that you can see the messages is bug 1970069.

Since it sounds like the flickering has stopped we can mark this as a duplicate of bug 1958191.

[Labar (labdom)]

confirmed, flickering effect is gone
may be closed