[solved] fontconfig-infinality ignored?

Hey,
Im trying to configure the fonts for my system to look nice, but so far they all look pretty ugly. Im using freetype-infinality from AUR (and also fontconfig-infinality), but no matter what rendering style I select, the fonts all keep looking the same, except when I select "Win98" (which, oddly enough, actually looks best).
As a screenshot says more, here it is: http://ompldr.org/vY3BqZA
In the top right corner, you can see some test text rendered with pango-view in linux, infinality, osx (EDIT: sorry, not osx, but win7, but it is the same with osx and osx2) and win98-styles, respectively. The first three all look exactly the same with some nasty red edges and the last one is "crusty" as hell. This cannot be right, can it?
Do I have to execute some additional tool or am I missing something else? Any ideas?
Last edited by foggy (2012-02-10 15:44:10)

Fixed it by installing the git version and regenerating the font cache. I also set dpi to 96 in ~/.Xresources as suggested by the README (RTFM I guess).
Looks nice now.

Similar Messages

Installing fontconfig-infinality from AUR

Hello guys!
It is probably the dumbest question ever, but I'm new to Arch and I am kind of stack here, so please help.
I'm trying to install the infinality fonts on my system, 'cause the default ones look awful for me. According to Font Configuration wiki page I have to install 3 packages: freetype2-infinality, which I've installed without any problems following Arch User Repository wiki page, lib32-freetype2-infinality and fontconfig-infinality. The last two packages I'm not able install, because the command makepkg -S doesn't generate any *.tar.xz file, which I supposed to install with pacman -S command.
Please, give me an advice on how to install these packages.
Thanks in advance and sorry for my bad English.
Last edited by stee1rat (2013-10-22 13:20:48)

karol wrote:
stee1rat wrote:Thanks for your answers, guys!
I've found out about yaourt to update AUR packages.
There are some other helpers you might like even better https://wiki.archlinux.org/index.php/AUR_Helpers
BTW, I use cower, which just downloads the srcpackage tarball (the *src.tar.gz) and unpacks it for you. It also provides some amaingly fast and efficient search functionality, has basic dependency resolution (it can download the srcpackage and any other AUR srcpackages it depends on), and is capable of updates. On top of all that awesomeness, it is written in C, so it it super snappy, and it maintained by falconindy, who is an Arch dev.
When I get lazy, as we all do, I use meat-git. Really using meat is actually using cower, but it is just a bash wrapper that also builds the packages for you. I mostly use it if I have serveral AUR packages that need updating.

[solved]makepkg -e ignoring the -e?

Trying to build a package that includes curl/types.h which has been removed from the curl package, but every time I comment out the include and run makepkg -e it re-extracts from the source file and overwrites my changes anyway. I thought the entire point of the -e option was to use the existing src/ directory as-is? That's what it says it does with makepkg --help:
$ makepkg --help
makepkg (pacman) 4.0.3
Usage: /usr/bin/makepkg [options]
Options:
-A, --ignorearch Ignore incomplete arch field in PKGBUILD
-c, --clean Clean up work files after build
-d, --nodeps Skip all dependency checks
-e, --noextract Do not extract source files (use existing src/ dir)
-f, --force Overwrite existing package
-g, --geninteg Generate integrity checks for source files
-h, --help Show this help message and exit
-i, --install Install package after successful build
-L, --log Log package build process
<snip>
Last edited by biltong (2012-10-20 15:49:20)

That is not a vcs build. There is an svn version of littleblackbox available, but this is for one of the versioned releases.
That PKGBUILD really does need some TLC though. It should not try to re-extract the source tarball in the build function, this is what is causing your problems.
Here's a modified version that solves that issue:
pkgname=littleblackbox
pkgver=0.1.3
pkgrel=1
pkgdesc="security/penetration testing tool, search in a collection of thousands of private SSL keys extracted from various embedded devices"
arch=(any)
url="http://code.google.com/p/littleblackbox/wiki/FAQ"
license=('MIT')
depends=('openssl' 'libpcap' 'sqlite3')
source=('https://littleblackbox.googlecode.com/files/littleblackbox-0.1.3.tar.gz')
md5sums=('7ddc140beda3f98c34db644b01fc4d84')
build() {
cd $pkgname-$pkgver
rm -f bin/$pkgname 2>/dev/null
cd src
make distclean
./configure
make
package() {
cd $srcdir/$pkgname-$pkgver
install -m755 -d ${pkgdir}/usr/bin $pkgdir/usr/share/doc/$pkgname \
$pkgdir/usr/share/licenses/$pkgname $pkgdir/usr/share/$pkgname
install -m755 bin/$pkgname ${pkgdir}/usr/bin
install -m644 bin/lbb.db $pkgdir/usr/share/$pkgname
ln -s /usr/share/$pkgname/lbb.db $pkgdir/usr/bin/lbb.db
install -m644 docs/LICENSE $pkgdir/usr/share/$pkgname
install -m644 docs/{FAQ,README,submission.txt} $pkgdir/usr/share/doc/$pkgname
msg "done"
# vim:set ts=2 sw=2 et:
Last edited by Trilby (2012-10-20 11:46:31)

[SOLVED] Fontconfig warning: "local.conf"

Hello Folks,
every software I run from the terminal shows me a long list of the same message, before to run.
Here an example:
skype
Fontconfig error: "local.conf", line 82: invalid attribute 'target'
Fontconfig error: "local.conf", line 85: invalid attribute 'target'
Fontconfig warning: "local.conf", line 181: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 194: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 213: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 229: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 291: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 426: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 530: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 544: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 558: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 614: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 628: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 635: invalid attribute 'name'
Fontconfig warning: "local.conf", line 229: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 291: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 426: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 530: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 544: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 558: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 614: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 628: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 635: invalid attribute 'name'
Fontconfig warning: "local.conf", line 642: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 656: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 663: invalid attribute 'name'
Fontconfig error: "local.conf", line 687: invalid attribute 'name'
Fontconfig error: "local.conf", line 706: invalid attribute 'name'
Fontconfig error: "local.conf", line 730: invalid attribute 'name'
Fontconfig warning: "local.conf", line 742: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 749: invalid attribute 'name'
Fontconfig warning: "local.conf", line 756: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 776: invalid attribute 'name'
Fontconfig warning: "local.conf", line 799: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 806: invalid attribute 'name'
Fontconfig warning: "local.conf", line 813: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 833: invalid attribute 'name'
Fontconfig error: "local.conf", line 879: invalid attribute 'name'
Fontconfig warning: "local.conf", line 903: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 916: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 931: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 943: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 959: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 966: invalid attribute 'name'
Fontconfig warning: "local.conf", line 973: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 992: invalid attribute 'name'
Fontconfig error: "local.conf", line 1009: invalid attribute 'name'
Fontconfig error: "local.conf", line 1026: invalid attribute 'name'
Fontconfig warning: "local.conf", line 1290: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 1293: invalid attribute 'target'
Fontconfig warning: "local.conf", line 1316: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1524: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig error: "local.conf", line 1527: invalid attribute 'target'
Fontconfig warning: "local.conf", line 1537: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1654: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1871: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1905: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1937: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "local.conf", line 1985: Having multiple values in <test> isn't supported and may not work as expected
How could I solve it?
Last edited by Astroarch (2014-09-11 17:56:30)

Then , I solved deleting the file and reinstalling fontconfig.
Byt he way, I do not post in the forum to be joked, if you mean to answer in such a way, better do not post at all.
Thanks
Last edited by Astroarch (2014-09-11 17:56:07)

[SOLVED]"fontconfig conflicts with fontconfig-ubuntu" and other issues

Almost every program I have has stopped working. If I run a program from a terminal (one of the virtual terminals, gnome-terminal wont work either), they either complain about not being able to find libpng or libjpeg. I read the news posting about these and some forum posts, but none of them mentioned people having problems. What I understood from reading is that I just need to update my system.
This is where the problem lies. I cannot run "pacman -Syu" as usual. When I do, I get the following error:
fontconfig conflicts with fontconfig-ubuntu. Remove fontconfig-ubuntu?
If I answer yes, I get:
error: failed to prepare transaction (could not satisfy dependencies)
:: kdelibs: requires phonon
:: cairo-ubuntu: requires fontconfig-ubuntu>=2.6.0
:: libxft-ubuntu: requires fontconfig-ubuntu
If I answer no, I get:
error: unresolvable package conflicts detected
error: failed to prepare transaction (conflicting dependencies)
:: fontconfig: conflicts with fontconfig-ubuntu
Either way, nothing is upgraded. How can I resolve this, as well as the libpng/libjpeg issue? I cleaned my cache and tried re-installing them, but it didn't help.
Last edited by DWilliams (2010-02-11 00:35:07)

DWilliams wrote:
Surgat_ wrote:
Or you can check AUR, get the latest pkgbuilds and rebuild your -ubuntu (or -lcd) packages. After installing them, the update should go flawlessly.
Also, if you have KDE installed you should check the news frontpage to see the KDE 4.4 announcement
Alright I installed fontconfig-ubuntu from the AUR and that resolved my initial conflict. It started complaining about gtk-qt-engine and kdelibs and they weren't depended on by anything so I just removed them (I assume I can re-install them later) and now my system upgrade is underway. Hopefully things will be fixed when it finishes.
Does anyone know what caused this and whether I can avoid similar issues in the future?
It happens because you are using a modified version of fontconfig (the ubuntu one). When a new version of fontconfig reaches [extra], pacman tries to update fontconfig (because fontconfig-ubuntu provides fontconfig, and fontconfig from [extra] is newer than the version you have installed) and finds that it conflicts with fontconfig-ubuntu.
The way to go is the one that you have followed: when there is an update in fontconfig, update your fontconfig-ubuntu package to the latest in AUR (hopefully the same version as the new one in [extra], else you'll have to wait or modify the PKGBUILD) and then update the rest of the system.

[SOLVED] Crontab entry ignored

I'm running cronie. My root crontab has an entry to run tarsnap every night, which is ignored.
The tarsnap line works when run in a terminal and the other entries work as well.
I tested it by altering the time to make it run immediately but nothing happens - no reported errors as far as I can see.
Here is my root crontab:
# backup /etc nightly
30 3 * * * rsync -a /etc/ /databackup/etc
# Correct clock each morning
00 5 * * * rdate -ncv uk.pool.ntp.org ; hwclock --hctosys
# update mlocate database each morning
00 4 * * * updatedb --prunepaths '/tmp /proc /mnt /var/tmp /databackup'
# tarsnap backup
00 3 * * * /usr/bin/tarsnap --exclude /home/ac/.mozilla --exclude /home/ac/.cache -c -f arcadiabackup-`date +%y%m%d` /home/ac
MAILTO=me@mydomain
Last edited by acampbell (2014-06-24 14:16:17)

WorMzy wrote:
Are you sure that cronie is running?
# systemctl status cronie.service
Yes.
Also, please use code tags.
Don't know what you mean by this.
Anyway, I found a work-around: I made a bash script in /root and that runs the command without problems.
Last edited by acampbell (2014-06-24 14:18:24)

[solved]Fontconfig problems (Ugly GTK Apps)

So I just installed the LCD filter patched packages on my new comp, but I'm trying to determine why some of my GTK apps still look really bad..
Firefox looks great, but pretty much any other app looks like crap, the fonts are barely readable. Below is my font configuration..
My .fonts.conf
<?xml version="1.0"?>
<fontconfig>
<match target="font" >
<edit mode="assign" name="rgba"><const>rgb</const></edit>
<edit mode="assign" name="hinting"><bool>true</bool></edit>
<edit mode="assign" name="hintstyle"><const>hintslight</const></edit>
<edit mode="assign" name="antialias"><bool>true</bool></edit>
<edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit>
</match>
</fontconfig>
/etc/fonts/conf.d directory:
# ls -l /etc/fonts/conf.d
lrwxrwxrwx 1 root root 30 Mar 3 16:01 10-autohint.conf -> ../conf.avail/10-autohint.conf
lrwxrwxrwx 1 root root 32 Mar 3 16:01 10-lcd-filter.conf -> ../conf.avail/10-lcd-filter.conf
lrwxrwxrwx 1 root root 35 Mar 3 16:01 10-sub-pixel-rgb.conf -> ../conf.avail/10-sub-pixel-rgb.conf
lrwxrwxrwx 1 root root 42 Mar 3 16:01 29-replace-bitmap-fonts.conf -> ../conf.avail/29-replace-bitmap-fonts.conf
lrwxrwxrwx 1 root root 27 Mar 3 16:01 45-latin.conf -> ../conf.avail/45-latin.conf
lrwxrwxrwx 1 root root 31 Mar 3 16:01 49-sansserif.conf -> ../conf.avail/49-sansserif.conf
lrwxrwxrwx 1 root root 26 Mar 3 16:02 50-user.conf -> ../conf.avail/50-user.conf
lrwxrwxrwx 1 root root 27 Mar 3 16:02 60-latin.conf -> ../conf.avail/60-latin.conf
I feel like I'm missing one, but I've attempted to link all the configurations from conf.avail and it still doesn't look good. Anyone?
Edit: Heres a screenshot:
Last edited by brenix (2010-03-04 04:39:30)

Hey there.
When I first installed arch, x11, xmonad, and gtk, the fonts looked like crap on my screen too. I ran over a ~/.Xdefaults setup that included:
! Xft settings ---------------------------------------------------------------
Xft.dpi: 96
Xft.antialias: true
Xft.rgba: rgb
Xft.hinting: true
Xft.hintstyle: hintslight
After restarting X, the ugly fonts were gone. I also switched the fonts used in gtk (using lxappearance) to the microsoft cleartype fonts (yeah yeah freedom hater). Don't forget you have to source ~/.Xdefaults from ~/.xinitrc like so:
# make sure the X Defaults gets loaded
xrdb ~/.Xdefaults
Also note, lxappearance is a great app for changing gtk+ themes.

[SOLVED] FontConfig Update and Anti-Aliasing

After doing upgrade of fontconfig exactly like explained on news here;
http://www.archlinux.org/news/fontconfi … -required/
Font became too thin, I think anti-aliasing is working wrong now. I've even added this:
https://wiki.archlinux.org/index.php/Fo … igurations
Also, my appearance settings is:
Default Font: Sans / Size: 10
Rendering: Enabled anti-aliasing
Hinting: Full
Sub-pixel order: None
DPI: Custom DPI setting 96
Here is few examples:
ArchLinux.org -- http://i.imgur.com/O7ZEC.png
Google.com -- http://i.imgur.com/TaY5S.png
Slashdot.org -- http://i.imgur.com/U8Oto.png
Digg.com -- http://i.imgur.com/TtgsM.png
Is there anyhting else I can do to fix this ?
Last edited by TuxLyn (2012-09-08 04:41:23)

My fonts were also looking bad after the upgrade (the same as in your screenshots), what I did:
mv .fontconfig .config/fontconfig
mv .fonts.conf .config/fontconfig/fonts.conf
mkdir .config/fontconfig/conf.d
ln -s /etc/fonts/conf.avail/10-sub-pixel-rgb.conf .config/fontconfig/conf.d ## Though this wasn't really necessary.
Moved all cache files from .config/fontconfig (formerly ~/.fontconfig) to ~/.cache, as suggested in the wiki.
And I copied this in my fonts.conf (.config/fontconfig/fonts.conf), examples you can also find in the wiki:
<?xml version='1.0'?>
<!DOCTYPE fontconfig SYSTEM 'fonts.dtd'>
<fontconfig>
<match target="font" >
<edit mode="assign" name="autohint"> <bool>true</bool></edit>
<edit mode="assign" name="hinting"> <bool>false</bool></edit>
<edit mode="assign" name="lcdfilter"> <const>lcddefault</const></edit>
<edit mode="assign" name="hintstyle"> <const>hintslight</const></edit>
<edit mode="assign" name="antialias"> <bool>true</bool></edit>
<edit mode="assign" name="rgba"> <const>rgb</const></edit>
</match>
<match target="font">
<test name="pixelsize" qual="any" compare="more"><double>15</double></test>
<edit mode="assign" name="lcdfilter"><const>lcdlight</const></edit>
<edit mode="assign" name="hintstyle"><const>hintnone</const></edit>
</match>
<match target="font">
<test name="weight" compare="more"><const>medium</const></test>
<edit mode="assign" name="hintstyle"><const>hintnone</const></edit>
<edit mode="assign" name="lcdfilter"><const>lcdlight</const></edit>
</match>
<match target="font">
<test name="slant" compare="not_eq"><double>0</double></test>
<edit mode="assign" name="hintstyle"><const>hintnone</const></edit>
<edit mode="assign" name="lcdfilter"><const>lcdlight</const></edit>
</match>
<match target="font">
<edit name="antialias" mode="assign"><bool>true</bool></edit>
<edit name="hinting" mode="assign"><bool>true</bool></edit>
<edit name="hintstyle" mode="assign"><const>hintfull</const></edit>
<edit name="lcdfilter" mode="assign"><const>lcddefault</const></edit>
<edit name="rgba" mode="assign"><const>rgb</const></edit>
</match>
</fontconfig>
Now my fonts look like before, and Chromium looks even better, thanks to one of the examples found.

[SOLVED] ALSAPCM value ignored

If i do "export ALSAPCM=pulse" or "export ALSAPCM=pulseout"
nothing changes, and mplayer and aplay will continue to use the default PCM.
Isnt' ALSAPCM environment variable supposed to select the default pcm at runtime?
What am i missing?
Thanks.
Gozer ~ # aplay -L |head -n 10
null
Discard all samples (playback) or generate zero samples (capture)
pulse
PulseAudio Sound Server
pulseout
Default ALSA Output (currently PulseAudio Sound Server)
default:CARD=Intel
HDA Intel, ALC1200 Analog
Default Audio Device
sysdefault:CARD=Intel
Gozer ~ # cat .asoundrc
pcm.pulseout {
type pulse
fallback "sysdefault"
hint {
show on
description "Default ALSA Output (currently PulseAudio Sound Server)"
ctl.pulseout {
type pulse
fallback "sysdefault"
Edit: My fault.
Adding this to .asoundrc solved.
pcm.!default {
type plug
slave.pcm {
@func getenv
vars [ ALSAPCM ]
default "dmix"
Last edited by kokoko3k (2014-09-05 07:00:59)

These are environment variables, that are already in place:
Alsa wiki wrote:Variable name # Definition
ALSA_CARD # pcm.default pcm.hw pcm.plughw ctl.sysdefault ctl.hw rawmidi.default rawmidi.hw hwdep.hw
ALSA_CTL_CARD # ctl.sysdefault ctl.hw
ALSA_HWDEP_CARD # hwdep.default hwdep.hw
ALSA_HWDEP_DEVICE # hwdep.default hwdep.hw
ALSA_PCM_CARD # pcm.default pcm.hw pcm.plughw
ALSA_PCM_DEVICE # pcm.hw pcm.plughw
ALSA_RAWMIDI_CARD # rawmidi.default rawmidi.hw
ALSA_RAWMIDI_DEVICE # rawmidi.default rawmidi.hw
That configuration file butchers the default setup. There is nothing wrong with that if you know how to get multiple sound sources and capture working again. If you do not, use something less restrictive for default value like 'dmix:CARD' or preferably an asym pcm or the [whole] original pcm.default as slave.
Edit: I see you changed it to dmix, good move. Changed format of the quote.
Last edited by emeres (2014-09-04 12:32:17)

[SOLVED] [freetype2-infinality] Weird letter spacing

I just installed freetype2-infinality 2.4.12-2 from AUR and noticed that every e (saw a few times; not permanent) and m letter has additonal space after them.
So far I've tried only Sans, since I'm using Openbox.
Why is it so and how can I remove this useless spacing feature?
Last edited by opt mode (2013-08-26 09:34:48)

The infinality patchset works quite well, but as with everything in Arch, it still requires you to configure it. So you are going to probably have to read up on how to properly adjust infinality. There is an application that allows you to make adjustments and view in real time what the various configurations will do to the fonts. I think it is the grip-git package in the AUR.
FWIW, I too ahve struggled with fonts in the past, and I never had the patience or will to really learn how to do them properly. So now I just use bohoomil's infinality-ultimate repository. There is a long thread about it, and I believe that there is a reference to it in the wiki as well. It requires no work, and results in fantastic fonts.

[SOLVED] Expiration time ignored in libnotify

Greetings everyone.
I'm using LXDE on Arch and wanted to do some custom notifications. I first installed notification-daemon, visited the Arch Wiki on the subject then tried this in a bash script:
#! /bin/bash
notify-send "New Mail" "From: $1\nSubject: $2" -t 60000
That popped up the notification just fine, but the expire-time parameter (-t 60000) was completely ignored as the notification disappeared after 5 seconds. Thinking it was just a notify-send problem, I decided to compile the example program (with the addition of notify_notification_set_timeout) in C:
#include <libnotify/notify.h>
void main () {
notify_init ("Hello world!");
NotifyNotification * Hello = notify_notification_new ("Hello world", "This is an example notification.", "dialog-information");
notify_notification_set_timeout(Hello, NOTIFY_EXPIRES_NEVER);
notify_notification_show (Hello, NULL);
notify_uninit ();
This worked, however the notification bubble is still disappearing after five seconds. Just for good measure, I even substituted NOTIFY_EXPIRES_NEVER with 60000 and this also was ignored.
I can't seem to find anything on the forums by searching (or through my favorite search engine) about timeout problems. Can anyone shed some light on this?
Thanks!
Last edited by willbprog127 (2011-12-01 23:32:42)

falconindy wrote:This is dependent on the sink that handles notifications, not libnotify itself.
Thanks for that. What can I do, then, to change this behavior? How can I identify what the sink is?

[SOLVED] Laptop action ignore close lid settings

I run gnome 3.4.2 and my laptop goes to sleep even though I set the laptop lid close action to "blank." I used gnome-tweak
Last edited by tancrackers (2012-10-14 07:04:19)

Are you using systemd? https://wiki.archlinux.org/index.php/Sy … th_systemd

[SOLVED]: Weird font issues with infinality-bundle on upgrade

Ive been using the infinality-bundle for some time with no problem until a recent update, and it seems like all my fonts got replaced with stranger ones. Below is a screenshot of my font problem and a snippet from my pacman.log.
[2013-10-15 18:56] [ALPM-SCRIPTLET] If you have been using freetype2-infinality from the AUR,
[2013-10-15 18:56] [ALPM-SCRIPTLET] the runtime file that came with it has been saved as
[2013-10-15 18:56] [ALPM-SCRIPTLET] /etc/profile.d/infinality-settings.sh.pacsave and the new
[2013-10-15 18:56] [ALPM-SCRIPTLET] one was installed in its place. You can manually delete
[2013-10-15 18:56] [ALPM-SCRIPTLET] infinality-settings.sh.pacsave as it is not needed anymore.
[2013-10-15 18:56] [ALPM-SCRIPTLET]
[2013-10-15 18:56] [ALPM-SCRIPTLET] If you are using [multilib], please install/upgrade
[2013-10-15 18:56] [ALPM-SCRIPTLET] lib32-freetype2-infinality-ultimate, too.
[2013-10-15 18:56] [PACMAN] upgraded freetype2-infinality-ultimate (2.5.0.1-5 -> 2.5.0.1-7)
[2013-10-15 18:56] [ALPM-SCRIPTLET] Removing redundant symlinks ...
[2013-10-15 18:56] [ALPM-SCRIPTLET] Done.
[2013-10-15 18:56] [ALPM-SCRIPTLET] Updating font cache...
[2013-10-15 18:56] [ALPM-SCRIPTLET] Done.
[2013-10-15 18:56] [PACMAN] upgraded fontconfig-infinality-ultimate (2.10.95-2 -> 2.11.0-3)
Last edited by cmm7825 (2013-10-15 23:42:36)

The recent Infinality update requires a uninstall/install of fontconfig. I posted the same problem here:
https://bbs.archlinux.org/viewtopic.php?id=171240
Last edited by mixer (2013-10-15 23:40:03)

[SOLVED]Infinality - blurry font

After installing arch new with old /home I installed under Xfce the following
freetype2-git-infinality lib32-freetype2-git-infinality freetype2-infinality
and the font got blurry.
On firefox it's looking ugly as well, here're some examples:
krusader, http://imgur.com/jbxuC
libreoffice, http://imgur.com/vEapa - menu shows only rectangles
Installed xf86-video-ati 1:7.0.0-1 and xorg-server 1.13.0-4.
.xlog shows the following errors
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-non-tt-fonts.conf", line 483: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-tt-fonts.conf", line 262: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-monospace-rendering.conf", line 27: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 21: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 50: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 31: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 102: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 119: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 138: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 158: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-non-tt-fonts.conf", line 483: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-tt-fonts.conf", line 262: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-monospace-rendering.conf", line 27: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 21: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 50: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 31: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 102: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 119: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 138: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 158: Having multiple values in <test> isn't supported and may not work as expected
QGtkStyle was unable to detect the current GTK+ theme.
(bootstrap.c:60) [mowgli_init]: mowgli_init() is a deprecated function, provided only for backwards compatibility with Mowgli-1. You should remove it if you no longer support using Mowgli-1.
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-non-tt-fonts.conf", line 483: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/60-group-tt-fonts.conf", line 262: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-monospace-rendering.conf", line 27: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 21: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/62-tt-traced-bitmap-rendering.conf", line 50: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 16: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 31: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 102: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 119: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 138: Having multiple values in <test> isn't supported and may not work as expected
Fontconfig warning: "/etc/fonts/infinality/conf.d/80-selective-rendering-inf-win-lin.conf", line 158: Having multiple values in <test> isn't supported and may not work as expected
.xsession-errors
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not works as expected
Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 39: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 56: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 66: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple values in <test> isn't supported and may not works as expected
Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/45-latin.conf", line 75: Having multiple <family> in <alias> isn't supported and may not works as expected
Fontconfig warning: "/etc/fonts/conf.d/53-monospace-lcd-filter.conf", line 10: Having multiple values in <test> isn't supported and may not works as expected
xfsettingsd: Another instance took over. Leaving...
TIA
Last edited by CTheGreatDevaluation (2012-12-07 17:50:59)

theDOC wrote:
I have problems with freetype2-git-infinality, too, so I installed stable + fontconfig-infinality-git to get rid of the fontconfig warnings:
fontconfig-infinality-git
freetype2-infinality
lib32-freetype2-infinality
That's working for me, thx Doc!

[SOLVED]Dependency cycle detected

Just activated the multilib repositories. After that i tried to to install Infinality Bundle for 32-bit but confronted with a dependency cycle warning. What is this?:
# pacman -S infinality-bundle-multilib
:: There are 3 members in group infinality-bundle-multilib:
:: Repository infinality-bundle-multilib
1) lib32-cairo-infinality-ultimate 2) lib32-fontconfig-infinality-ultimate
3) lib32-freetype2-infinality-ultimate
Enter a selection (default=all): 3
resolving dependencies...
looking for conflicting packages...
warning: dependency cycle detected:
warning: lib32-harfbuzz will be installed before its lib32-freetype2-infinality-ultimate dependency
Packages (13) lib32-bzip2-1.0.6-2 lib32-expat-2.1.0-2 lib32-gcc-libs-4.9.2-3
lib32-glib2-2.42.1-1 lib32-glibc-2.21-2 lib32-harfbuzz-0.9.38-1 lib32-icu-54.1-1
lib32-libdbus-1.8.16-1 lib32-libffi-3.2.1-1 lib32-libpng-1.6.16-1
lib32-pcre-8.36-1 lib32-zlib-1.2.8-1 lib32-freetype2-infinality-ultimate-2.5.5-2
Total Download Size: 14.17 MiB
Total Installed Size: 58.59 MiB
:: Proceed with installation? [Y/n]
Last edited by Paingiver (2015-03-01 14:48:14)

EscapedNull wrote:
Paingiver wrote:True dependency cycle? What does that means?
It means that these two packages, directly or indirectly, are mutually dependent. Normally pacman installs dependencies of packages before the package itself, but this creates a catch-22 when packages depend on each other. In these cases, pacman is allowed to temporarily ignore (--assume-installed) one of the mutually dependent packages to install the other, as long as it is sure that both of them can be installed within the same pacman invocation. At least that's my understanding.
Great explanation. thanks. Marking as solved.

[solved] fontconfig-infinality ignored?

Similar Messages

Maybe you are looking for