No Verdana font in Google Docs - Errors with ttf-mscorefonts-installer

CoredusK's picture

Forums: 

I'm really new to Linux, and I've been Googling and searching on this for hours, can't seem to find a solution.

When I go to Google Docs, both in Chrome and in Firefox, the Verdana font isn't listed.
Google search results display in a bit of a weird font as well.

Can't install ttf-mscorefonts-installer ~ a very weird error which I can't seem to resolve

root@coredusk:/etc/apt/sources.list.d# apt-get install ttf-mscorefonts-installer
Reading package lists... Done
Building dependency tree      
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
ttf-mscorefonts-installer : Depends: update-notifier-common (>= 0.119ubuntu2) but it is not installable
E: Unable to correct problems, you have held broken packages.

Trying to install with Synapse gives the same error.

I used a command that I found somewhere (don't remember which one) to show my 'held packages', which didn't give results.
I'm running XFCE v4.10, Installed Debian 8

Halp!

wops

CoredusK's picture

Sources.list

#

# deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 NETINST Binary-1 20160123-18:59]/ jessie main

#deb cdrom:[Debian GNU/Linux 8.3.0 _Jessie_ - Official amd64 NETINST Binary-1 20160123-18:59]/ jessie main

deb http://ftp.be.debian.org/debian/ jessie main
deb-src http://ftp.be.debian.org/debian/ jessie main

deb http://security.debian.org/ jessie/updates main
deb-src http://security.debian.org/ jessie/updates main

# jessie-updates, previously known as 'volatile'
deb http://ftp.be.debian.org/debian/ jessie-updates main
deb-src http://ftp.be.debian.org/debian/ jessie-updates main
~                                                                              
~       

sources.list.d

coredusk@coredusk:/etc/apt$ ls -a sources.list.d
.   google-chrome-beta.list  google-chrome-unstable.list  nodesource.list
..  google-chrome.list       multiverse.list

"Unable to correct problems,

arochester's picture

"Unable to correct problems, you have held broken packages"

First, try, as Root: apt-get -f install

root@coredusk:/home/coredusk#

CoredusK's picture


root@coredusk:/home/coredusk# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@coredusk:/home/coredusk# apt-get install ttf-mscorefonts-installer
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
ttf-mscorefonts-installer : Depends: update-notifier-common (>= 0.119ubuntu2) but it is not installable
E: Unable to correct problems, you have held broken packages.
root@coredusk:/home/coredusk#

Sad

This seems to be the problem

CoredusK's picture

This seems to be the problem.

I'm having issues manually installing this now though (sorry, I'm still a noobie :x)

root@coredusk:/home/coredusk/Downloads/update-notifier-3.160# ./configure && make && make install
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... no
checking for mawk... mawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking dependency style of gcc... gcc3
checking for library containing strerror... none required
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking whether gcc understands -c and -o together... (cached) yes
checking dependency style of gcc... (cached) gcc3
checking how to run the C preprocessor... gcc -E
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ANSI C header files... yes
checking for pkg-config... no
./configure: line 5947: --variable: command not found
configure: error: glib-compile-schemas not found.
root@coredusk:/home/coredusk/Downloads/update-notifier-3.160#

You've got an Ubuntu

arochester's picture

You've got an Ubuntu Repository.

Debian is normally: main contrib non-free
Ubuntu is normally: main restricted universe multiverse

In sources.list.d you have: multiverse.list
and it is feeding Ubuntu packages into your system

I'm not certain that I can advise you with certainty about this. I would:
1) Delete the multiverse.list
2) Change your sources list to include contrib and non-free (e.g. http://linuxgeekar.blogspot.co.uk/2015/05/things-to-do-after-installing-... ... the section "Update the Source List)
3) Do, as Root, in a Terminal, one-by-one:
apt-get update
apt-get upgrade
apt-get dist-upgrade
apt-get autoremove

...as a newbie you do not need source code. You could disable the lines starting deb-src by putting a # at the beginning of those lines.

Then try to install the font again.

OMG

CoredusK's picture

My God! Thank you so much! That did it!

I really thought this was a lost and weird case, learned alot now Smile
Chrome font is fine and Google docs show the Verdana font now!

Thanks a bunch <3