Font corrupted on Discord after upgrading to 18.04
Clash Royale CLAN TAG#URR8PPP up vote
3
down vote
favorite
The discord's default font (Noto) seems corrupted after upgrade to Ubuntu 18.04 from 17.10.Instead of running update-manager I did it by changing from artful(?) to bionic and I think that this might be a problem.Can i re-install the font?
fonts 18.04
asked Apr 27 at 15:22
tuddyftw
172
add a comment |Â
up vote
3
down vote
favorite
The discord's default font (Noto) seems corrupted after upgrade to Ubuntu 18.04 from 17.10.Instead of running update-manager I did it by changing from artful(?) to bionic and I think that this might be a problem.Can i re-install the font?
fonts 18.04
asked Apr 27 at 15:22
tuddyftw
172
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
The discord's default font (Noto) seems corrupted after upgrade to Ubuntu 18.04 from 17.10.Instead of running update-manager I did it by changing from artful(?) to bionic and I think that this might be a problem.Can i re-install the font?
fonts 18.04
asked Apr 27 at 15:22
tuddyftw
172
The discord's default font (Noto) seems corrupted after upgrade to Ubuntu 18.04 from 17.10.Instead of running update-manager I did it by changing from artful(?) to bionic and I think that this might be a problem.Can i re-install the font?
fonts 18.04
asked Apr 27 at 15:22
tuddyftw
172
asked Apr 27 at 15:22
tuddyftw
172
asked Apr 27 at 15:22
tuddyftw
172
asked Apr 27 at 15:22
tuddyftw
172
172
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50
add a comment |Â
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
It appears to be an issue with libfreetype6 2.8.1. IT has been reported that downgrading to 2.8.0 fixes the issue, but I'd rather avoid messing with core system libraries and just wait for a fix.
Temporary workaround is to open the Chrome inspector in the Discord app with CTRL + SHIFT + I and run in the console document.getElementById("app-mount").style["transform"] = "scaleX(1.0000001)"
This has to be done every time Discord is started.
answered Apr 28 at 18:40
Mathieu Comandon
658610
add a comment |Â
up vote
2
down vote
Update to discord-0.0.5 at http://discordapp.com/
They fixed the issue.
answered May 4 at 16:16
Nectar
7493617
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
It appears to be an issue with libfreetype6 2.8.1. IT has been reported that downgrading to 2.8.0 fixes the issue, but I'd rather avoid messing with core system libraries and just wait for a fix.
Temporary workaround is to open the Chrome inspector in the Discord app with CTRL + SHIFT + I and run in the console document.getElementById("app-mount").style["transform"] = "scaleX(1.0000001)"
This has to be done every time Discord is started.
answered Apr 28 at 18:40
Mathieu Comandon
658610
add a comment |Â
up vote
2
down vote
It appears to be an issue with libfreetype6 2.8.1. IT has been reported that downgrading to 2.8.0 fixes the issue, but I'd rather avoid messing with core system libraries and just wait for a fix.
Temporary workaround is to open the Chrome inspector in the Discord app with CTRL + SHIFT + I and run in the console document.getElementById("app-mount").style["transform"] = "scaleX(1.0000001)"
This has to be done every time Discord is started.
answered Apr 28 at 18:40
Mathieu Comandon
658610
add a comment |Â
up vote
2
down vote
up vote
2
down vote
It appears to be an issue with libfreetype6 2.8.1. IT has been reported that downgrading to 2.8.0 fixes the issue, but I'd rather avoid messing with core system libraries and just wait for a fix.
Temporary workaround is to open the Chrome inspector in the Discord app with CTRL + SHIFT + I and run in the console document.getElementById("app-mount").style["transform"] = "scaleX(1.0000001)"
This has to be done every time Discord is started.
answered Apr 28 at 18:40
Mathieu Comandon
658610
It appears to be an issue with libfreetype6 2.8.1. IT has been reported that downgrading to 2.8.0 fixes the issue, but I'd rather avoid messing with core system libraries and just wait for a fix.
Temporary workaround is to open the Chrome inspector in the Discord app with CTRL + SHIFT + I and run in the console document.getElementById("app-mount").style["transform"] = "scaleX(1.0000001)"
This has to be done every time Discord is started.
answered Apr 28 at 18:40
Mathieu Comandon
658610
answered Apr 28 at 18:40
Mathieu Comandon
658610
answered Apr 28 at 18:40
Mathieu Comandon
658610
answered Apr 28 at 18:40
Mathieu Comandon
658610
658610
add a comment |Â
add a comment |Â
up vote
2
down vote
Update to discord-0.0.5 at http://discordapp.com/
They fixed the issue.
answered May 4 at 16:16
Nectar
7493617
add a comment |Â
up vote
2
down vote
Update to discord-0.0.5 at http://discordapp.com/
They fixed the issue.
answered May 4 at 16:16
Nectar
7493617
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Update to discord-0.0.5 at http://discordapp.com/
They fixed the issue.
answered May 4 at 16:16
Nectar
7493617
Update to discord-0.0.5 at http://discordapp.com/
They fixed the issue.
answered May 4 at 16:16
Nectar
7493617
answered May 4 at 16:16
Nectar
7493617
answered May 4 at 16:16
Nectar
7493617
answered May 4 at 16:16
Nectar
7493617
7493617
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%2f1028825%2ffont-corrupted-on-discord-after-upgrading-to-18-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
I don't think avoiding update-manager is the problem, since I upgraded in the normal way and I have the same issue as you.
– Nectar
Apr 27 at 19:50