** Attachment added: "journalctl -b0 from successful screen activation"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5270412/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter
This time I turned off the displayed, unplugged it, then left it
unplugged while I rebooted. After rebooting and logging in, I turned on
the display and plugged it in. Attached is the dmesg from this boot.
** Attachment added: "dmesg from functional boot"
This is still 100% reproducible. I have attached the dmesg below.
** Attachment added: "dmesg from 2019/06/06"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5269157/+files/dmesg.txt
--
You received this bug notification because you are a member of Desktop
I did plug/unplug the monitor because if I do that enough times is
generally resolves the problem until the next time I reboot. It has not
done so this time. I also tried a new cable, but that does not fix the
problem either.
--
You received this bug notification because you are a member of
It seems unlikely to be a cable or signal problem since I can eventually
coax it into working, and it continues working until I reboot. If it
were a cable problem or something about the signal I would have to
physically modify the connection to create and/or correct the problem.
Since the mere act
** Attachment added: "output of xrandr > xrandr.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267692/+files/xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in
I tried that and it didn't fix the problem. I am attaching the output of
some of those files again for further data.
** Attachment added: "dmesg output ( on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267690/+files/dmesg.txt
--
You received this
** Attachment added: "output of journalctl -b0 > journal.txt (on Wayland)"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267691/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Attachment added: "output of xrandr > xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267344/+files/xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "output of lspci -k"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267341/+files/lspcik.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "output of journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267343/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in
** Attachment added: "dmesg output"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267342/+files/dmesg.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Attachment added: "Image of the screen corruption"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1830792/+attachment/5267340/+files/IMG_20190528_160705.jpg
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell
Public bug reported:
On my system I have two display: one in landscape, and one in portrait.
The landscape display is fine, but the portrait display is corrupted. If
I unplug the display from the computer for some time and then plug it
back in it will occasionally fix the problem.
Once the
To reproduce it, try switching the order of your displays. For example,
make the display on port 0 be on the right of the display on port 1
(instead of the "natural" order of 0=left, 1=right.) I also notice that
changing the orientation of the primary display to "portrait right"
causes problems,
Yes, they are very similar.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1825004
Title:
Ubuntu loses display settings on reboot, corrupts displays
Status in gnome-shell
Public bug reported:
I have two displays, one on display port, and one on VGA. The display
port display is a Seiki Pro 40" display in landscape at 3840x2160. The
VGA is an HP 24" display in portrait at 1920x1200.
If I boot with either display by itself, everything works fine. If I
plug in the
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
I can confirm that it's not fixed. Rebooting has become a major problem
for me because it loses my display settings, corrupts the displays, and
I spend 20 minutes fixing everything.
--
You received this
I can also confirm this problem. It happens to me in Unity on a
repeatable basis: whenever I click the mouse on the desktop to draw a
selection, everything freezes momentarily. It doesn't happen when
resizing or moving windows, just when I click on the desktop. However,
it does happen if I try to
19 matches
Mail list logo
