HiDPI scaling issues on Ubuntu 16.04
Clash Royale CLAN TAG#URR8PPP up vote
1
down vote
favorite
I am using Ubuntu 16.04 with an HiDPI monitor (3840x2160). Following an update earlier this week (which also broke the unity desktop) the display scaling now resets to 1 when resuming from sleep. I was hoping that this would get corrected in the upgrade from 16.04.3 to 16.04.4 but that is not the case. When the unity desktop broke I ran the following commands which eventually corrected the issue of the missing launcher and top panel:
sudo apt clean
sudo apt autoclean
sudo apt install -f
sudo apt install -f unity
sudo apt install -f ubuntu-desktop
sudo reboot
When I realized that display scaling was resetting to 1 after resuming from sleep, I tried the following commands:
cd .cache
mv compizconfig-1 compizconfig-1_old
reboot
and
sudo apt install --reinstall unity-settings-daemon
reboot
However, neither of these approaches worked. Is this issue affecting anyone else? Is there a way to prevent the display scaling from changing everytime the computer is inactive long enough to go to sleep?
Update: (7 March 2018) I can't tell if this is truly a duplicate of the issue in Ubuntu 17.04 as indicated by david6. The problem with the scaling is the same, but only when using the AMD 17.50 drivers. When using the kernel's amdgpu driver the problem does not exist. Is this the same issue? Note using the latest AMD drivers released today (17.50-552542) does not fix the issue.
16.04 unity amdgpu amdgpu-pro
asked Feb 23 at 21:16
Mark Maurer
737
add a comment |Â
up vote
1
down vote
favorite
I am using Ubuntu 16.04 with an HiDPI monitor (3840x2160). Following an update earlier this week (which also broke the unity desktop) the display scaling now resets to 1 when resuming from sleep. I was hoping that this would get corrected in the upgrade from 16.04.3 to 16.04.4 but that is not the case. When the unity desktop broke I ran the following commands which eventually corrected the issue of the missing launcher and top panel:
sudo apt clean
sudo apt autoclean
sudo apt install -f
sudo apt install -f unity
sudo apt install -f ubuntu-desktop
sudo reboot
When I realized that display scaling was resetting to 1 after resuming from sleep, I tried the following commands:
cd .cache
mv compizconfig-1 compizconfig-1_old
reboot
and
sudo apt install --reinstall unity-settings-daemon
reboot
However, neither of these approaches worked. Is this issue affecting anyone else? Is there a way to prevent the display scaling from changing everytime the computer is inactive long enough to go to sleep?
Update: (7 March 2018) I can't tell if this is truly a duplicate of the issue in Ubuntu 17.04 as indicated by david6. The problem with the scaling is the same, but only when using the AMD 17.50 drivers. When using the kernel's amdgpu driver the problem does not exist. Is this the same issue? Note using the latest AMD drivers released today (17.50-552542) does not fix the issue.
16.04 unity amdgpu amdgpu-pro
asked Feb 23 at 21:16
Mark Maurer
737
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41
add a comment |Â
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am using Ubuntu 16.04 with an HiDPI monitor (3840x2160). Following an update earlier this week (which also broke the unity desktop) the display scaling now resets to 1 when resuming from sleep. I was hoping that this would get corrected in the upgrade from 16.04.3 to 16.04.4 but that is not the case. When the unity desktop broke I ran the following commands which eventually corrected the issue of the missing launcher and top panel:
sudo apt clean
sudo apt autoclean
sudo apt install -f
sudo apt install -f unity
sudo apt install -f ubuntu-desktop
sudo reboot
When I realized that display scaling was resetting to 1 after resuming from sleep, I tried the following commands:
cd .cache
mv compizconfig-1 compizconfig-1_old
reboot
and
sudo apt install --reinstall unity-settings-daemon
reboot
However, neither of these approaches worked. Is this issue affecting anyone else? Is there a way to prevent the display scaling from changing everytime the computer is inactive long enough to go to sleep?
Update: (7 March 2018) I can't tell if this is truly a duplicate of the issue in Ubuntu 17.04 as indicated by david6. The problem with the scaling is the same, but only when using the AMD 17.50 drivers. When using the kernel's amdgpu driver the problem does not exist. Is this the same issue? Note using the latest AMD drivers released today (17.50-552542) does not fix the issue.
16.04 unity amdgpu amdgpu-pro
asked Feb 23 at 21:16
Mark Maurer
737
I am using Ubuntu 16.04 with an HiDPI monitor (3840x2160). Following an update earlier this week (which also broke the unity desktop) the display scaling now resets to 1 when resuming from sleep. I was hoping that this would get corrected in the upgrade from 16.04.3 to 16.04.4 but that is not the case. When the unity desktop broke I ran the following commands which eventually corrected the issue of the missing launcher and top panel:
sudo apt clean
sudo apt autoclean
sudo apt install -f
sudo apt install -f unity
sudo apt install -f ubuntu-desktop
sudo reboot
When I realized that display scaling was resetting to 1 after resuming from sleep, I tried the following commands:
cd .cache
mv compizconfig-1 compizconfig-1_old
reboot
and
sudo apt install --reinstall unity-settings-daemon
reboot
However, neither of these approaches worked. Is this issue affecting anyone else? Is there a way to prevent the display scaling from changing everytime the computer is inactive long enough to go to sleep?
Update: (7 March 2018) I can't tell if this is truly a duplicate of the issue in Ubuntu 17.04 as indicated by david6. The problem with the scaling is the same, but only when using the AMD 17.50 drivers. When using the kernel's amdgpu driver the problem does not exist. Is this the same issue? Note using the latest AMD drivers released today (17.50-552542) does not fix the issue.
16.04 unity amdgpu amdgpu-pro
16.04 unity amdgpu amdgpu-pro
asked Feb 23 at 21:16
Mark Maurer
737
asked Feb 23 at 21:16
Mark Maurer
737
edited Mar 7 at 16:44
asked Feb 23 at 21:16
Mark Maurer
737
asked Feb 23 at 21:16
Mark Maurer
737
asked Feb 23 at 21:16
Mark Maurer
737
737
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41
add a comment |Â
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
1
down vote
I have a partial solution to my problem. I had been using the amdgpu Adrenalin edition driver (17.50-511655). Uninstalling the driver fixes the problem. But reinstalling either the amdgpu or amdgpu-pro version of the driver results in the scaling issue. Looks like I need to use the standard amdgpu driver in the kernel until AMD releases an update to their driver.
answered Feb 23 at 22:19
Mark Maurer
737
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
I have a partial solution to my problem. I had been using the amdgpu Adrenalin edition driver (17.50-511655). Uninstalling the driver fixes the problem. But reinstalling either the amdgpu or amdgpu-pro version of the driver results in the scaling issue. Looks like I need to use the standard amdgpu driver in the kernel until AMD releases an update to their driver.
answered Feb 23 at 22:19
Mark Maurer
737
add a comment |Â
up vote
1
down vote
I have a partial solution to my problem. I had been using the amdgpu Adrenalin edition driver (17.50-511655). Uninstalling the driver fixes the problem. But reinstalling either the amdgpu or amdgpu-pro version of the driver results in the scaling issue. Looks like I need to use the standard amdgpu driver in the kernel until AMD releases an update to their driver.
answered Feb 23 at 22:19
Mark Maurer
737
add a comment |Â
up vote
1
down vote
up vote
1
down vote
I have a partial solution to my problem. I had been using the amdgpu Adrenalin edition driver (17.50-511655). Uninstalling the driver fixes the problem. But reinstalling either the amdgpu or amdgpu-pro version of the driver results in the scaling issue. Looks like I need to use the standard amdgpu driver in the kernel until AMD releases an update to their driver.
answered Feb 23 at 22:19
Mark Maurer
737
I have a partial solution to my problem. I had been using the amdgpu Adrenalin edition driver (17.50-511655). Uninstalling the driver fixes the problem. But reinstalling either the amdgpu or amdgpu-pro version of the driver results in the scaling issue. Looks like I need to use the standard amdgpu driver in the kernel until AMD releases an update to their driver.
answered Feb 23 at 22:19
Mark Maurer
737
answered Feb 23 at 22:19
Mark Maurer
737
answered Feb 23 at 22:19
Mark Maurer
737
answered Feb 23 at 22:19
Mark Maurer
737
737
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1009161%2fhidpi-scaling-issues-on-ubuntu-16-04%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
thank you david6 for the comments. the bug report in LaunchPad now reflects that Ubuntu 16.04 is affected. Still seems odd that this problem only exists with the AMD 17.50 drivers and not the kernel's amdgpu driver.
– Mark Maurer
Mar 5 at 22:01
It affects me with Nvidia drivers (and 16.04). I'm running the pearl script (from the possible duplicate above).
– david6
Mar 6 at 8:04
@MarkMaurer If the duplicate candidate doesn't resolve your issue, can you clarify that in the question itself?
– Amanda
Mar 6 at 16:41