[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
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 accepted by your display should be : 74.176MHz / (2750 x 1125) = 23.9760808081 Hz Due to floating point error, in monitors.xml you get 23.976079940795898 Hz Maybe the issue comes from this ? -- 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 gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1892296] Re: gnome-control-center cannot change resolution of external monitor
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: gnome-control-center cannot change resolution of external monitor Status in gnome-control-center package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: g-c-c is unable to change the resolution on my external 2560x1440 monitor to 1920x1080 - when I try, the monitor turns off. However, the command "xrandr --output HDMI-1 --mode 1920x1080" does successfully change the resolution. xrandr for the monitor shows: HDMI-1 connected 2560x1440+0+0 (normal left inverted right x axis y axis) 597mm x 336mm 2560x1440 59.95*+ 1920x1080 60.0050.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1600x1200 60.00 1280x1024 75.0260.02 1280x960 60.00 1360x768 60.02 1280x720 60.0050.0059.94 1024x768 75.0370.0760.00 800x600 75.0060.32 720x576 50.00 720x576i 50.00 720x480 60.0059.94 720x480i 60.0059.94 640x480 75.0060.0059.94 720x400 70.08 I tried changing the resolution to 1600x1200 using g-c-c and this did work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.4-0ubuntu1 Uname: Linux 5.8.1-050801-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 20 11:28:08 2020 InstallationDate: Installed on 2019-07-01 (415 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2019-12-08 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1892296/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1827328] Re: ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
Also observed on Ubuntu 18.04.3, with kernel 5.0.0-37-generic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to modemmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1827328
Title:
ModemManager does not honor blacklisted ttys (ID_MM_DEVICE_IGNORE)
Status in modemmanager package in Ubuntu:
Confirmed
Bug description:
In Ubuntu 19.04 (and likely earlier) Modem Manager is installed with
filter policy 'strict' as opposed to 'default', which actually makes
Modem Manager _less_ strict regarding explicitly blacklisted ttys (see
man modemmanager).
This means that ttys, that are explicitly blacklisted from Modem
Manager by using ENV{ID_MM_DEVICE_IGNORE}="1" in its udev rule is
still opened and probed by Modem Manager although it should not.
This is a common cause of problems and frustrations for people working
with actual serial devices, e.g. within embedded development (e.g.
Arduino and the like). See https://nick.zoic.org/art/failed-to-set-
dtr-rts-systemd-modemmanager/ for an example.
A proposed solution is to change the following line in:
/lib/systemd/system/ModemManager.service
from:
ExecStart=/usr/sbin/ModemManager --filter-policy=strict
to:
ExecStart=/usr/sbin/ModemManager --filter-policy=paranoid
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: modemmanager 1.10.0-1 [modified:
lib/systemd/system/ModemManager.service]
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 2 15:35:58 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-26 (340 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: Upgraded to disco on 2019-04-18 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1827328/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
