Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#48108 - After upgrade gtk applications' fonts get messed up when unlocking from xscreensaver

Attached to Project: Arch Linux
Opened by Oto Magaldadze (ottoshmidt) - Tuesday, 09 February 2016, 17:59 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 10 February 2016, 22:56 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the latest upgrade I get gtk application fonts messed up
when I unlock the screen from xscreensaver lock. No other gui
applications, like chromium, get affected.
Most likely, it's due to some changes in underlying libraries
but not sure.


Additional info:
* xscreensaver 5.34-1



Steps to reproduce:
1. Lock screen with xscreensaver (try screensavers set to random)
2. Recover from lock
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 10 February 2016, 22:56 GMT
Reason for closing:  Fixed
Comment by Doug Newgard (Scimmia) - Tuesday, 09 February 2016, 23:35 GMT
After what upgrade, specifically?
Comment by Oto Magaldadze (ottoshmidt) - Wednesday, 10 February 2016, 08:25 GMT
After

[code]$ pacman -Syy[/code]
[code]$ pacman -Su[/code]

I don't know what was the previous version of xscreensaver installed on my system.
Comment by Oto Magaldadze (ottoshmidt) - Wednesday, 10 February 2016, 08:49 GMT
Ahm, my bad, turns out xscreensaver is not the culprit.
It happens after recovering from sleep, even if xscreensaver is not launched at all.
Comment by Doug Newgard (Scimmia) - Wednesday, 10 February 2016, 15:39 GMT
So again, after what upgrade, specifically? What packages were upgraded when this started to happen?
Comment by Oto Magaldadze (ottoshmidt) - Wednesday, 10 February 2016, 21:50 GMT
I don't even know how to track upgraded packages post factum.

Anyway, after upgrading these packages:
nvidia-libgl 361.28-1
nvidia-utils 361.28-1

The problem is gone.

Loading...