2022-04-21 16:54:47 |
Daniel LaSalle |
bug |
|
|
added bug |
2022-04-21 16:54:47 |
Daniel LaSalle |
attachment added |
|
monitors.xml https://bugs.launchpad.net/bugs/1969815/+attachment/5582155/+files/monitors.xml |
|
2022-04-21 17:01:38 |
Daniel LaSalle |
description |
I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible) and only use wifi.
For the tower: this is the dual-screen portrait system I have been opening up defects for months now. After reboot everything went well until TTY7 tried displaying but never did.
What happened is that both of my screens started blinking blank for =<1 second . Within 1 second both screens went from being full dark/energy saver mode back to (what seems to me) a X black background with only the mouse cursor floating around.
Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2 would show a login prompt that within =<1 second, the screens tilted and changed mode again and only a cursor symbol(_) was at the top-hand-left side blinking.
That behavior held true for all TTYs.
Both of my screens are the same model and use HDMI.
Solution was: unplug one of the two monitor and automagically jammy's login screen popped up.
If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re-back again at the jammy login having lost my working session.
I have attached my ~/.config/monitors.xml |
I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end-user experience)
For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken.
The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated.
Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left.
That behavior held true for all TTYs.
Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK.
Solution was: unplug one of the two monitor and automagically jammy's login screen popped up.
If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re-back again at the jammy login having lost the current session that I had.
Both of my screens are the same model and both use HDMI.
I have attached my ~/.config/monitors.xml |
|
2022-04-21 17:02:08 |
Daniel LaSalle |
summary |
22.04-machine rendered totally useless because of dual-screen (post-install) |
22.04-machine rendered totally useless because of (portrait(?)) dual-screen (post-install) |
|
2022-04-22 09:20:49 |
Martin Wimpress |
bug task added |
|
xorg-server (Ubuntu) |
|
2022-04-22 09:21:01 |
Martin Wimpress |
bug task added |
|
marco (Ubuntu) |
|
2022-04-22 09:21:08 |
Martin Wimpress |
bug task deleted |
ubuntu-mate |
|
|
2022-04-26 06:35:00 |
Daniel van Vugt |
summary |
22.04-machine rendered totally useless because of (portrait(?)) dual-screen (post-install) |
Dual screens started blinking from blank to another type of blank for =<1 second each state |
|
2022-04-26 06:35:57 |
Daniel van Vugt |
marco (Ubuntu): status |
New |
Incomplete |
|
2022-04-26 06:36:07 |
Daniel van Vugt |
xorg-server (Ubuntu): status |
New |
Incomplete |
|
2022-04-26 06:36:11 |
Daniel van Vugt |
bug |
|
|
added subscriber Daniel van Vugt |
2022-04-26 11:37:44 |
Daniel LaSalle |
attachment added |
|
lspci https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1969815/+attachment/5583941/+files/lspci.txt |
|
2022-04-27 01:50:49 |
Daniel van Vugt |
tags |
jammy |
jammy radeon |
|
2022-04-27 01:51:11 |
Daniel van Vugt |
summary |
Dual screens started blinking from blank to another type of blank for =<1 second each state |
[radeon] Dual screens started blinking from blank to another type of blank for =<1 second each state |
|
2022-04-27 11:51:24 |
Daniel LaSalle |
attachment added |
|
result of journalctl -b0 > journal.txt https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1969815/+attachment/5584373/+files/journal.txt |
|
2022-04-28 01:55:54 |
Daniel van Vugt |
marco (Ubuntu): status |
Incomplete |
New |
|
2022-04-28 01:55:56 |
Daniel van Vugt |
xorg-server (Ubuntu): status |
Incomplete |
New |
|
2022-05-05 02:18:41 |
Daniel van Vugt |
bug task added |
|
linux (Ubuntu) |
|
2022-05-05 02:30:08 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
2022-05-05 13:05:21 |
Daniel LaSalle |
tags |
jammy radeon |
apport-collected jammy radeon |
|
2022-05-05 13:05:22 |
Daniel LaSalle |
description |
I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end-user experience)
For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken.
The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated.
Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left.
That behavior held true for all TTYs.
Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK.
Solution was: unplug one of the two monitor and automagically jammy's login screen popped up.
If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re-back again at the jammy login having lost the current session that I had.
Both of my screens are the same model and both use HDMI.
I have attached my ~/.config/monitors.xml |
I've just updated to 22.04 on 3x boxes: 2x laptops and 1x tower. Laptops went well as they are standard running wifi (note to self: next time upgrade one using a USB docking station+as many externally attached devices as possible should prove in a quite pleasurable end-user experience)
For the tower: this is the dual-screen portrait system I have been opening up defects for months now. Same config too. Anyways, after I rebooted the overall booting process happened pretty well until TTY7 tried kicking it and totally failed doing so hence rendered my system totally broken.
The behavior of my screens is that they started blinking from blank to another type of blank for =<1 second each state. But during one of those states there seemed to be Wayland as I could just see the mouse cursor fly around when activated.
Accessing other TTYs was also impossible as even though pressing CTRL+ALT+F2|F3|etc would indeed display a login prompt that within that same blinking instant that it had altered back to only that blinking cursor symbol(_) at the top-hand-left.
That behavior held true for all TTYs.
Pressing the power button did showed up the UM symbol alongside standard shutdown routine happened OK.
Solution was: unplug one of the two monitor and automagically jammy's login screen popped up.
If I replug that 2nd monitor while I am inside a working TTY7 session then the same (original) problem happens in which I cannot use any of the screens and when I re-unplug one of the two screens again I am re-back again at the jammy login having lost the current session that I had.
Both of my screens are the same model and both use HDMI.
I have attached my ~/.config/monitors.xml
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC1: dd 3464333 F.... pulseaudio
/dev/snd/controlC0: dd 3464333 F.... pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
DistroRelease: Ubuntu 22.04
HibernationDevice: RESUME=UUID=88228def-1fb1-4fc3-964c-3106218355eb
InstallationDate: Installed on 2020-08-29 (613 days ago)
InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
IwConfig:
lo no wireless extensions.
enp7s0 no wireless extensions.
tun0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: xorg-server
PackageArchitecture: amd64
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-25-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
RelatedPackageVersions:
linux-restricted-modules-5.15.0-25-generic N/A
linux-backports-modules-5.15.0-25-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu1
RfKill:
Tags: jammy
Uname: Linux 5.15.0-25-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/02/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5809
dmi.board.asset.tag: Default string
dmi.board.name: TUF X470-PLUS GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5809:bd12/02/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFX470-PLUSGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer |
|
2022-05-05 13:05:23 |
Daniel LaSalle |
attachment added |
|
AlsaInfo.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587000/+files/AlsaInfo.txt |
|
2022-05-05 13:05:25 |
Daniel LaSalle |
attachment added |
|
CRDA.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587001/+files/CRDA.txt |
|
2022-05-05 13:05:27 |
Daniel LaSalle |
attachment added |
|
CurrentDmesg.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587002/+files/CurrentDmesg.txt |
|
2022-05-05 13:05:30 |
Daniel LaSalle |
attachment added |
|
Dependencies.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587003/+files/Dependencies.txt |
|
2022-05-05 13:05:31 |
Daniel LaSalle |
attachment added |
|
Lspci.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587004/+files/Lspci.txt |
|
2022-05-05 13:05:33 |
Daniel LaSalle |
attachment added |
|
Lspci-vt.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587005/+files/Lspci-vt.txt |
|
2022-05-05 13:05:36 |
Daniel LaSalle |
attachment added |
|
Lsusb.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587006/+files/Lsusb.txt |
|
2022-05-05 13:05:38 |
Daniel LaSalle |
attachment added |
|
Lsusb-t.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587007/+files/Lsusb-t.txt |
|
2022-05-05 13:05:44 |
Daniel LaSalle |
attachment added |
|
Lsusb-v.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587008/+files/Lsusb-v.txt |
|
2022-05-05 13:05:45 |
Daniel LaSalle |
attachment added |
|
PaInfo.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587009/+files/PaInfo.txt |
|
2022-05-05 13:05:46 |
Daniel LaSalle |
attachment added |
|
ProcCpuinfoMinimal.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587010/+files/ProcCpuinfoMinimal.txt |
|
2022-05-05 13:05:49 |
Daniel LaSalle |
attachment added |
|
ProcEnviron.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587011/+files/ProcEnviron.txt |
|
2022-05-05 13:05:50 |
Daniel LaSalle |
attachment added |
|
ProcInterrupts.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587012/+files/ProcInterrupts.txt |
|
2022-05-05 13:05:52 |
Daniel LaSalle |
attachment added |
|
ProcModules.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587013/+files/ProcModules.txt |
|
2022-05-05 13:05:54 |
Daniel LaSalle |
attachment added |
|
PulseList.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587014/+files/PulseList.txt |
|
2022-05-05 13:05:55 |
Daniel LaSalle |
attachment added |
|
UdevDb.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587015/+files/UdevDb.txt |
|
2022-05-05 13:05:57 |
Daniel LaSalle |
attachment added |
|
WifiSyslog.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587016/+files/WifiSyslog.txt |
|
2022-05-05 13:06:00 |
Daniel LaSalle |
attachment added |
|
acpidump.txt https://bugs.launchpad.net/bugs/1969815/+attachment/5587017/+files/acpidump.txt |
|
2022-05-05 13:07:07 |
Daniel LaSalle |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|