** Changed in: gnome-control-center
Status: Unknown => New
--
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/1892296
Title:
gnome-control-center cannot change
FWIW, in Ubuntu 20.10 you can't change the resolution of the external
monitor with g-c-c at all, because there is no dropdown for the
resolution, just a label showing the current resolution.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1402
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
I reported it here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1402
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1402
https://gitlab.gnome.org/GNOME/mutter/-/issues/1402
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Rocko,
Please report the issue to the developers at either:
https://gitlab.gnome.org/GNOME/mutter/-/issues
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
and then tell us the new issue ID(s).
--
You received this bug notification because you are a member of Desktop
Packages,
@Daniel: That current mode is from the xrandr.txt when the working
2560x1440 resolution is set. Lionel and I got the 23.98 Hz figure from
monitors.xml that I generated after the 1920x1080 change is applied and
the monitor has no signal. With the monitor receiving no signal in
1920x1080, the
It's not choosing the lowest frequency. Lionel just chose that as a
random example from your xrandr.txt. That same file shows the current
mode is:
2560x1440 (0xbb) 241.500MHz +HSync +VSync *current +preferred
--
You received this bug notification because you are a member of Desktop
Packages,
2560x1440 (0xbb) 241.500MHz +HSync +VSync *current +preferred
h: width 2560 start 2608 end 2640 total 2720 skew0 clock 88.79KHz
v: height 1440 start 1443 end 1448 total 1481 clock 59.95Hz
--
You received this bug notification because you are a member of Desktop
But why does g-c-c choose the lowest frequency refresh instead of the
highest? If I set the resolution to 1920x1080 using xrandr, it chooses
the 60 Hz option:
1920x1080 60.00* 50.0059.9430.0025.0024.00
29.9723.98
which is this modeline:
1920x1080 (0xbc) 148.500MHz
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-control-center (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Thanks,
Looking at your xrandr.txt there is the modeline :
1920x1080 (0xc6) 74.176MHz +HSync +VSync
h: width 1920 start 2558 end 2602 total 2750 skew0 clock 26.97KHz
v: height 1080 start 1084 end 1089 total 1125 clock 23.98Hz
That means the refresh rate
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mutter (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
This is monitors.xml after changing to the (non-working) 1920x1080
configuration. It seems to have chosen a refresh rate of
23.976079940795898 Hz (is that the last option in xrandr's modeline
"1920x1080 60.0050.0059.9430.0025.0024.00
29.9723.98"?).
When I use xrandr to
This is after changing to the (working) 2560x1440 resolution.
** Attachment added: "monitors-2560x1440.xml"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5405199/+files/monitors-2560x1440.xml
--
You received this bug notification because you are a
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
Can you attach the file ~/.config/monitors.xml right after changing the
resolution to 2560x1440 ?
--
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/1892296
Title:
Possibly related: https://gitlab.gnome.org/GNOME/mutter/-/issues/1388
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1388
https://gitlab.gnome.org/GNOME/mutter/-/issues/1388
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Tags added: multimonitor
--
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/1892296
Title:
gnome-control-center cannot change resolution of external monitor
Status in
> it looks like g-c-c has chosen a mode that doesn't actually exist for
xrandr, because none of the modes have an asterisk next to them.
Good point. Please report that as a bug to mutter here:
https://gitlab.gnome.org/GNOME/mutter/issues
--
You received this bug notification because you are
No, that doesn't help - the screen stays blank if I set it to 1920x1080
using g-c-c and then run the set max bpc command.
I also tried setting 1920x1080i using xrandr in case that's what g-c-c
was choosing but it worked fine.
With the 1920x1080 setting chosen in g-c-c (and the monitor
Though the issue seems more likely some kind of bad choice of refresh
rate, or doublescan, or interlacing... I am also reminded that we're
still missing this fix:
https://gitlab.gnome.org/GNOME/mutter/-/issues/275#note_776751
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #275
This reminds me of bug 1890772. Try this:
xrandr --output HDMI-1 --set "max bpc" 8
--
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/1892296
Title:
gnome-control-center
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404256/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
** Attachment added: "xrandr.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404255/+files/xrandr.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
It doesn't work in Wayland, either.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+attachment/5404254/+files/lspci.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Also, do you experience the same problem if you log into 'Ubuntu on
Wayland'?
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
** Changed in: mutter (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Please run the following commands immediately after attempting a
resolution change:
lspci -kv > lspci.txt
xrandr --verbose > xrandr.txt
journalctl -b0 > journal.txt
and then attach the resulting text files here.
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
27 matches
Mail list logo
