It does seam similar to that GNOME bug.
I am using the 23.04, so I guess I will be able to test the fix soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/2038656
Public bug reported:
Preconditions:
- Having an access to a actual http(s) proxy would allow to perform test with
actual network traffic, but the bug is reproducible without it.
Steps to reproduce:
1. Go to Settings -> Network -> Proxy
2a. Switch on the proxy
2b. Change proxy configuration to
I switched back to Wayland and 2 external monitors today and the flicker
seems to be gone (Ubuntu 23.04 with current updates).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/2023647
Public bug reported:
Preconditions:
- Connect external monitor (not sure if necessary)
- Have a Google Chrome o Microsoft Edge installed (did not test it with
Chromium and Firefox)
- Have access to at least 2 Gmail accounts to be able to use Meet (did not yet
experience it with other
Added Daniel van Vugt to subscribers as he was explicitely interested in
this issue
** Description changed:
Preconditions:
- Connect external monitor (not sure if necessary)
- Have a Google Chrome o Microsoft Edge installed (did not test it with
Chromium and Firefox)
+ - Have access to at
I suspected this should go to AMD Kernel team. Lots of people
complaining about changes AMD has been making for some time.
Can you redirect this error, or should I report it somewhere else?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
My optimism was to early. Journal dump attached. Took it after
unplugging one of the monitors and waiting few flickers for desktop to
stabilize.
Btw, were should I report that Slack crashes when I right click inside?
:D
** Attachment added: "journal_wayland.txt"
I don't know what changed but I switched back to Wayland a few days ago
and cannot repoduce any glitches I suffered. Is this the week I stop
regretting buying a laptop on AMD chipset?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
I'll try to find some time during the weekend to reproduce it with
Wayland. I am using this PC for work during the week and Wayland keeps
crashing with entire session whenever I am in a videocall. :)
--
You received this bug notification because you are a member of Desktop
Packages, which is
As requested attaching a result of a journalctl -b0 command.
This happened after renaming monitor.xml and monitor.xml~ so
unfortunaltely that does not help.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023647/+attachment/5679605/+files/journal.txt
Public bug reported:
This happens whenever screen goes blank after inactivity with external
monitors.
When there is only one external monitor after few cycles the system
recovers from the bug.
When there are more than one monitors the system almost never recovers
until unplugging extra monitor,
11 matches
Mail list logo
