Path: csiph.com!pasdenom.info!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!fu-berlin.de!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: eben@gmx.us Newsgroups: linux.debian.user Subject: Re: lightdm errors Date: Tue, 04 Jun 2024 20:10:01 +0200 Message-ID: References: X-Original-To: debian-user@lists.debian.org X-Mailbox-Line: From debian-user-request@lists.debian.org Tue Jun 4 18:04:13 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-7.807 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Ui-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: en-US Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K1:S6dVhQeZYxRgG3Eqwv9xK0HGjnIX8Xf3v323jBtNKpejQHy7ntT yUxRnqYFSs8zfJsDPBDCwQf/kqctpP4sbOawoZYV1QPUAT0Xj2mFHowcmwo6nX2wlrKmznr Wtoo7+qRSHgmqadFy3LudSdyBBInxEzR+9mTp5Yyr++SbjPslQS+D0e2gbQ+BVLORQhpBf7 N66y6JsiRgp78+kjLDkqg== Ui-Outboundreport: notjunk:1;M01:P0:qNDzWMJ9+6g=;mi8XhPnUIlO4NLSA0fdlEQQqeCS VbWFRz1olTIf03WlsPk17OUKoDbuV+3rc305AAgN3z2qYVg5TgmbYJPQyDh5lMD8jxC5J2e4C rvxvtm4rY1d/q1VOPUErMruEbO0e803UfQ/CjIPgswGRXp2EoOJdmedEwxmNeva/wWxXBzKKp dfEID2wOx3ajttQiiBW5+9AmQVqSTx5tjHBx/xFlvM2+h8u71r80R+UIpWHOE3LPa4XjVe+Gv GSweSrZgVxNim2sLYT12cKK9RhGnHhxpmkZ05VemrWjfYVkk7/jGQWuvxh+2+fsJ1q57+wm4O MBimmhEFCUPiupjPeHL2/38V8GuUVy61W3K4lr6q0jq/JvpM8eBTsqTUKN2Bg/2Mu/pcDbGYA TWQ1bjdSKeJdnXf3unTgcMXMJYvaT7zpUUu+p4+9jZEgiPEw3fb8v/QmhbeefwutK+M8hdMZC 680cF0P2L/tKuVT+8IT+zyZThvEtj0zrNQDvRdF60Kxi1BnARkirZ2PsGcXZ5i/V1HOFQeqQL sBWJIbmz/Nup2OtkIFi2l6ThQvOm9W/ogqlp8GyyIxsGRkneJcey0w5USYC8282Yl6MqrDLle 30BZJ/xx9onSCMlztWPeQz1pQdwSrDLYprvaWBHEhg0NoGrxRTdThYJYa92w4RwXb3zpl//6Q ZN+rZ3SUijXxNYTFp/aQrpKDJ4YV+qnPvQ4qfZPZSqQc4TIamOEPj2tOnPtR6r+qT8eiQ9SDR cMyI/FAyALfBvXLFFuTH8Djb6sk/OnkaouKFjP8rr74Yi6Q+vJSWkJGwLSH+aL5G/r7v3R6Ga GbIb4PiEZb3SWwRE9wxItqHjPHy7pvE190h9PpGq9mmU8= X-Mailing-List: archive/latest/811973 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/bbc103c1-e768-4735-9440-3ee358d26dbc@gmx.us Approved: robomod@news.nic.it Lines: 88 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Tue, 4 Jun 2024 14:03:55 -0400 X-Original-Message-ID: X-Original-References: <09b42764-9084-4b81-88c4-6ba401bb00e2@gmx.us> <20240604104422.5a243b6b@hawk.localdomain> Xref: csiph.com linux.debian.user:269930 On 6/4/24 12:44, Charles Curley wrote: > On Tue, 4 Jun 2024 09:55:51 -0400 > Eben King wrote: > >> Jun 04 01:57:07 cerberus lightdm[1547009]: xrandr: cannot find mode >> 1920x1200 >> >> and so on. >> >> I have three monitors on the onboard connectors. The left >> (1920x1080) is tall, the other two (1920x1200) are wide. The default >> situation was that the monitors were in the wrong order, and the left >> one was sideways. I wrote a script which used xrandr to fix this in >> XFCE, though I rarely need it. > > I suggest you use arandr to set things as you wish, then export a > script to automate that setup. Then call the script from your session > manager. > > Or, since you are using XFCE, Applications -> Settings -> Display and > set things up there. I did that a while back, when I set the monitors up this way. They were arranged correctly once I logged in. It's just in lightdm that they were wrong. They are correct now (I actually don't know why, unless it's ignoring the hash mark for that line), but I get those errors, which might be related to it not going into suspend overnight. I modified lightdm's config on 20 May (so says my log), but: eben@cerberus:~$ sudo journalctl | grep xrandr | uniq -c --check-chars=3D6 3015 May 24 21:25:03 cerberus lightdm[2714286]: xrandr: cannot find mo= de 1920x1200 13581 May 25 00:41:10 cerberus lightdm[2823087]: xrandr: cannot find mo= de 1920x1200 14599 May 26 01:35:52 cerberus lightdm[282746]: xrandr: cannot find mod= e 1920x1200 17512 May 27 01:02:53 cerberus lightdm[951063]: xrandr: cannot find mod= e 1920x1200 18670 May 28 00:38:05 cerberus lightdm[1676638]: xrandr: cannot find mo= de 1920x1200 13689 May 29 00:34:24 cerberus lightdm[2413887]: xrandr: cannot find mo= de 1920x1200 14006 May 30 01:52:22 cerberus lightdm[3092520]: xrandr: cannot find mo= de 1920x1200 14376 May 31 01:40:14 cerberus lightdm[3751983]: xrandr: cannot find mo= de 1920x1200 15296 Jun 01 00:58:00 cerberus lightdm[206925]: xrandr: cannot find mod= e 1920x1200 16280 Jun 02 00:00:00 cerberus lightdm[175982]: xrandr: cannot find mod= e 1920x1200 13209 Jun 03 02:25:20 cerberus lightdm[909251]: xrandr: cannot find mod= e 1920x1200 12630 Jun 04 01:56:54 cerberus lightdm[1546837]: xrandr: cannot find mo= de 1920x1200 There are no errors on the 23rd related to xrandr, so I suspect something happened on the 24th. The logged event right before lightdm started acting up was May 24 21:25:01 cerberus dbus-daemon[1362]: [session uid=3D1000 pid=3D1362= ] Activating service name=3D'org.xfce.Xfconf' req> May 24 21:25:01 cerberus dbus-daemon[1362]: [session uid=3D1000 pid=3D1362= ] Successfully activated service 'org.xfce.Xfco> Maybe that dbus update was bad? Or I only updated part of it or something= ? =2D- This message was created using recycled electrons.