Secondary monitor config not working

Bug #1880418 reported by Jon Atkinson on 2020-05-24
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxqt-config (Ubuntu)

Bug Description

Older HP laptop
using displayport to HDMI cable to use a larger secondary monitor

I need to go to ->preferences-> Monitor Settings
in order to get the 2 displays to sync

I see DP-1 and eDP-1
DP-1 (the laptop) will display fine

eDP-1 the extended monitor's config

The position does not start in the default, thus I have to change this to default in order for things to look similar. (I would expect the baseline config for "Position" on eDP-1 to be "default" and the rest of the parameters to be "auto"


Things now appear and behave as expected

(The configuration change that I have made does not appear to save via the "monitor settings" tool. I have not explored finding the appropriate config file and manually making the needed changes. What happens is that I need to repeat going into monitor settings each and every time after I have to reboot the machine for a patch; for my secondary display to work as desired.)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lxqt-config 0.14.1-0ubuntu3
Uname: Linux 5.6.14-050614-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Sun May 24 11:58:16 2020
InstallationDate: Installed on 2019-11-04 (202 days ago)
InstallationMedia: Lubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
 PATH=(custom, no user)
SourcePackage: lxqt-config
UpgradeStatus: Upgraded to focal on 2020-04-28 (26 days ago)

Revision history for this message
Jon Atkinson (720jon-atkinson) wrote :
Revision history for this message
Jon Atkinson (720jon-atkinson) wrote :

lxrandr is the program that is launched.

Revision history for this message
Jon Atkinson (720jon-atkinson) wrote :

it appears that if I use the following:
   >lxqt-sudo lxrandr,
the configuration will save.

Sadly the man page for lxrandr provides no real assistance and after some investigating came across the lxqt-sudo information in the LUBUNTU manual. And the xorg randr via thinkwiki, I was able to assemble the information needed. Suggestion to provide a notification when lxrandr is used via the gui to run it manually in the other fashion. Additionally, there is nothing in the LUBUNTU manual that explains the lxranr interface.

As well the lxqt-sudo write up in the manual could provide an expansion as to when it could be/should be used.

I would extrapolate that bug 1860918 could possible be resolved using lxqt-sudo if the end use knew what to use with this. I did not find a quick 'about' button to identify the mouse and keyboard config app's name.

Revision history for this message
Jon Atkinson (720jon-atkinson) wrote :

What I have seen with this bug and others is that there is a permissions issue within the lxqt environment. I as a user would want the ability to save and have a separate profile for "my user" using lxqt, rather than having to use sudo and elevated permissions to save the desired changes, no. Doing so now fixes the change for everyone, rather than an individual user. Thus the user who filed the bug where he make the modification to make his mouse left-handed and it works until he reboots and has to make the change again as the user-level change was not saved as expected. Thus this bug as well fits into that category. So what I dislike is that these bugs are coded as one-off, as they effect just one user. I disagree. These bugs affect everyone and there are many left-handed people. Many do not want to got to the time and trouble of filing a bug and following up with it. Or just accept that something does not work as expected and make the needed modification on an as needed basis; as they know that is what they need to do in order for them to function. In my case I identified the bug, identified a work around, as well identified the root source. It would be nice that someone collect these like bugs and classify them accordingly; then fix the underlying permissions or missing mechanism to have a user level config file problem in either the current and/or future versions. Else document the work around for all to find more readily.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers