On 06/23/2017 11:47 AM, JPlews wrote:
On 23/06/17 14:46, Richard Owlett wrote:I had cause to re-read bug <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859564> titled "arandr: doesn't detect when I unplug an external screen" Depending on how the phrasing of the problem is read it cause could be a hardware related issue or have an underlying cause in common with my bug <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865535> titled "arandr: Does not use applied settings on reboot". Is it correct to send the same email to both bug reports? I intend to add the model information of my laptop to my report.
Your reply is OFF-TOPIC.I was EXPLICITLY asking what should be down when two bug reports focusing on different problems may have a common underlying cause.
I would suggest that those bugs are invalid and should be closed, arandr makes no attempt to monitor anything, it is simply a command builder and arrangement UI for xrandr, and xrandr describes itself "primitive command line interface to RandR extension" Don't know exactly where the problem lies, but it's probably MATE and the monitors.xml file, as soon as something isn't present at the correct time this gets changed and persists, so if you correct it for one session it just takes forgetting to switch your external display on for it to change again automatically and persist, requiring another GUI based fix... I saw you made an xrandr command, you could try that in LightDM or just add it to the MATE startup items, or bind it to a keyboard shortcut. Regards