[SOLVED] No Verdana font in Google Docs - Errors with ttf-mscorefonts-installer
Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
No Verdana font in Google Docs - Errors with ttf-mscorefonts-installer
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
Code:
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
the key here is update-notifier-common.
have you tried installing it? what kind of errors does that give?
have you searched ubuntu forums regarding the errors you see?
also, you might need to first fix broken packages each time after you get an error like that.
Yes, I did try installing this. It gives more weird errors that I don't quite understand:
Code:
root@coredusk:/home/coredusk# apt-get install update-notifier-common
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package update-notifier-common is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'update-notifier-common' has no installation candidate
root@coredusk:/home/coredusk#
This link basically tells me to install another system and only then upgrade to make this work, I think. Which is, not an option I'm really hyped for at the moment.
Installed older version .tar.xz from here, installed a C compiler - -
Now I'm stuck at this installation:
Code:
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#
Did those apt-get update and upgrades all the time haha
I'm glad to inform you guys that the problem has been solved.
Solution provided by arochester here
Somehow there was a problem with my sources.list getting an Ubuntu repository, not Debian.
Even though I installed Debian Jessie from a disc. It's very unclear to me how this happened, but I'm still very new to Linux (loving it besides this issue btw).
Glad you were able to fix the problem. If you would, please mark this thread as "SOLVED" by clicking on "Thread Tools" directly above your initial post. Thanks!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.