Package Details: ttf-ms-win11-auto 10.0.22631.2428-1

Git Clone URL: https://aur.archlinux.org/ttf-ms-win11-auto.git (read-only, click to copy)
Package Base: ttf-ms-win11-auto
Description: Microsoft Windows 11 TrueType fonts
Upstream URL: https://www.microsoft.com/typography/fonts/product.aspx?PID=164
Licenses: custom
Conflicts: ttf-ms-fonts, ttf-tahoma, ttf-vista-fonts
Provides: emoji-font, ttf-font, ttf-ms-fonts, ttf-ms-win11, ttf-tahoma
Submitter: octocorvus
Maintainer: octocorvus (kode54)
Last Packager: kode54
Votes: 64
Popularity: 5.25
First Submitted: 2022-05-06 13:39 (UTC)
Last Updated: 2024-02-12 23:43 (UTC)

Dependencies (3)

Required by (299)

Sources (145)

Pinned Comments

kode54 commented on 2024-02-04 10:43 (UTC) (edited on 2024-02-04 10:45 (UTC) by kode54)

You apparently need to be a member of the disk group to mount a filesystem as an otherwise unprivileged user.

sudo usermod -aG disk $USER

And log out and back in again.

Latest Comments

1 2 3 4 5 6 .. 9 Next › Last »

kode54 commented on 2024-04-08 07:31 (UTC)

@mdjake Yes, unfortunately, the stock build process uses udisks to mount the disk images without root privileges. You can alter the PKGBUILD, but it will have to be built as root somehow.

mdjake commented on 2024-04-08 05:43 (UTC)

Hi!

I've failed to install this package through an ssh connection. However I've managed to install it flawlessly by sitting down in front of my computer and logging into it interactively.

Dingisoul commented on 2024-02-27 04:21 (UTC)

I got this error when update to the newest version 

==> Removing existing $srcdir/ directory...
rm: cannot remove '/home/dingisoul/.cache/yay/ttf-ms-win11-auto/src/mnt/http': Is a directory

==> ERROR: An unknown error has occurred. Exiting...

However, I don't see this rm command in PKGBUILD. Can friends tell me how to fix it. Thanks !!!

jalejotorresm commented on 2024-02-15 19:00 (UTC) (edited on 2024-02-15 19:03 (UTC) by jalejotorresm)

Hi everyone,

I am tryin to update to the latest version of this package but I got the following error message

install: cannot stat 'wingding.ttf': No such file or directory
==> ERROR: A failure occurred in package_ttf-ms-win11-auto().
    Aborting...
 -> error making: ttf-ms-win11-auto-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
ttf-ms-win11-auto - exit status 4

The part of install: cannot stat 'wingding.ttf': No such file or directory appears for other fonts, such as arial.

Any advice on how to get this update completed? I have all deps updated, so I don't think it would be on that side.

UPDATE: Forgot to comment that system is failing to create SymLinks: ln: failed to create symbolic link '/home/jalejotorresm/.cache/yay/ttf-ms-win11-auto/src/' -> '': No such file or directory

Not sure if this could also be impacting the process, any lead is greatly appreciated.

Thank you for all the help.

kode54 commented on 2024-02-12 20:24 (UTC) (edited on 2024-02-12 20:25 (UTC) by kode54)

Huh, I noticed, I don't have it installed, either.

I do have this in my kernel configuration:

CONFIG_UDF_FS=m

gregthwuen commented on 2024-02-12 15:53 (UTC)

That's odd, I don't have udftools installed and have no problems installing.

kode54 commented on 2024-02-12 07:05 (UTC)

I will add it as a make dependency.

silikeite commented on 2024-02-11 23:31 (UTC)

Noting that udftools should be a dependency for this package. Otherwise getting an error that filesystem type udf not configured in kernel.

kode54 commented on 2024-02-11 23:18 (UTC)

@qifei9, it may only work when logged into a desktop environment. I'm not entirely sure. Editing the script may work, but it still requires elevation or disk membership in that case.

kode54 commented on 2024-02-11 23:17 (UTC)

I can't reproduce it with either of those two fonts, though I am using Plasma, not GNOME, and I had a Wayfire desktop before, but it started crashing on login, so I can't figure out what's up with that.

The antialiasing settings may be related to font hinting control, since I remember fonts back in the day having their own rules for not antialiasing certain point sizes, and it was up to the renderer to decide whether to observe those rules.

1 2 3 4 5 6 .. 9 Next › Last »