You are not logged in.
Hi all,
I recently upgraded my system, and started having some font problems. This comes after having upgraded freetype and needing to uncomment the line in /etc/profile.d/freetype2.sh that allowed me to set the FREETYPE_PROPERTIES variable. The issue I'm having now, it seems, is that my system seems to be ignoring this? I'm not sure exactly what the problem is.
Whenever I type, "echo $FREETYPE_PROPERTIES", I just get a blank line back instead of the variable itself. I tried editing the sudoers file with visudo and adding 'Defaults env_keep += "FREETYPE_PROPERTIES"', but this also doesn't seem to be working.
Any ideas?
Last edited by andronas (2016-10-23 04:21:01)
Offline
Gnome on Wayland, by any chance? It doesn't source /etc/profile.
Offline
Gnome on Wayland, by any chance? It doesn't source /etc/profile.
As far as I know, I'm just running Gnome. I have some wayland software installed, apparently, but I've never set Gnome to run through Wayland manually.
`--> sudo pacman -Ss wayland
extra/kwayland 5.27.0-1 (kf5)
Qt-style Client and Server library wrapper for the Wayland libraries
extra/kwayland-integration 5.8.2-1 (plasma)
Provides integration plugins for various KDE frameworks for the wayland
windowing system
extra/plasma-wayland-session 5.8.2-1
Plasma Wayland session
extra/qt5-wayland 5.7.0-3 (qt qt5)
Provides APIs for Wayland
extra/wayland 1.12.0-1 [installed]
A computer display server protocol
extra/wayland-protocols 1.7-1 [installed]
Specifications of extended Wayland protocols
extra/xorg-server-xwayland 1.18.4-1 (xorg) [installed]
run X clients under wayland
community/glfw-wayland 3.2.1-1
A free, open source, portable framework for graphical application
development (wayland)
community/sway 0.9-1
i3 compatible window manager for Wayland
community/weston 1.12.0-1
Reference implementation of a Wayland compositor
community/wlc 0.0.6-1
Wayland Compositor Library
multilib/lib32-wayland 1.12.0-1 [installed]
A computer display server protocol
Last edited by andronas (2016-10-23 03:59:54)
Offline
Wayland is now the default on Gnome 3.22, so unless you're specifically selecting it on X, you're on Wayland.
Offline
Wayland is now the default on Gnome 3.22, so unless you're specifically selecting it on X, you're on Wayland.
That might be the problem then. How do I fix this issue?
Offline
Bitch and complain to the Gnome devs for breaking things.
Offline
Bitch and complain to the Gnome devs for breaking things.
There's no workaround? As in putting the export statement in another file? Or something?
Offline
There's another thread about it around here, maybe they found a workaround; I don't really know.
Offline
There's another thread about it around here, maybe they found a workaround; I don't really know.
Okay, so the workaround mentioned in this post fixed my problem:
https://bbs.archlinux.org/viewtopic.php … 3#p1661003
After update, my .Xresources was not loaded on startup.
Also using Gnome and GDM.
Uncommented the WaylandEnable=false in /etc/gdm/custom.conf and then the resources was loaded.
Dont know what is going on with Wayland.
Thanks for your recommendation.
Last edited by andronas (2016-10-23 04:10:10)
Offline
Please remember to mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline