On 09/27/2016 10:26 AM, Stefan W. Kleyer wrote:
Stefan:
Thank you for your reply that allows me to work-around the problem.
I got it to work, created a shell-script for it, and created a
desktop launcher to execute that shell-script.
It would be better if there were a way to execute it in the
Stefan:
Thank you for your reply that allows me to work-around the problem.
I got it to work, created a shell-script for it, and created a
desktop launcher to execute that shell-script.
It would be better if there were a way to execute it in the
auto-start processing, but I'm not sure of
On 09/27/2016 02:43 AM, Stefan W. Kleyer wrote:
I had a similar problem with my system. I solved it by forcing xrandr
to use a higher resolution. I'm not sure, if this is a good way, but
it works quite good for me.
1. Open a Terminal and type in "cvt screen_resolution":
$ cvt 1680 1050 60
You
Hi,
I had a similar problem with my system. I solved it by forcing xrandr to
use a higher resolution. I'm not sure, if this is a good way, but it works
quite good for me.
1. Open a Terminal and type in "cvt screen_resolution":
$ cvt 1680 1050 60
You will get something like this (your's could
Den 2016-09-27 kl. 07:29, skrev Aere Greenway:
Lubuntu Users:
One of my machines, running Lubuntu 16.04, has a monitor which has been
working (as long as we can remember on 14.04, and a long time after
upgrading to 16.04) at a resolution of 1680 x 1050 (or something like
that). And it still run
Lubuntu Users:
One of my machines, running Lubuntu 16.04, has a monitor which has been
working (as long as we can remember on 14.04, and a long time after
upgrading to 16.04) at a resolution of 1680 x 1050 (or something like
that). And it still runs with that resolution on Windows 10.
For s
