Hi,
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
I'll downgrade one package after the other, but perhaps somebody could give me a hint what package/s might have caused the new unfavourable look.
One problem is shown here, a dilettante repeated unnecessarily design, e.g. a bar that already separates regions inside a window, became a bar with a cutting line inside the bar:
http://lists.claws-mail.org/pipermail/users/attachments/20160410/7fdca7e7/at...
The list of packages that were upgraded is posted here:
http://lists.claws-mail.org/pipermail/users/2016-April/016236.html
[rocketmouse@archlinux ~]$ grep -v '#' .gtkrc-2.0
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
Regards, Ralf
I've had a similar issue; can't see any highlights hovering over things anymore (i.e. tray icon for pulseaudio or network manager, can't adjust things in pulseaudio window, etc). On Mon, 11 Apr 2016, Ralf Mardorf wrote:
Hi,
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
I'll downgrade one package after the other, but perhaps somebody could give me a hint what package/s might have caused the new unfavourable look.
One problem is shown here, a dilettante repeated unnecessarily design, e.g. a bar that already separates regions inside a window, became a bar with a cutting line inside the bar:
http://lists.claws-mail.org/pipermail/users/attachments/20160410/7fdca7e7/at...
The list of packages that were upgraded is posted here:
http://lists.claws-mail.org/pipermail/users/2016-April/016236.html
[rocketmouse@archlinux ~]$ grep -v '#' .gtkrc-2.0
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
Regards, Ralf
On Mon, 11 Apr 2016 10:17:19 +0930, Stephen wrote:
I've had a similar issue; can't see any highlights hovering over things anymore (i.e. tray icon for pulseaudio or network manager, can't adjust things in pulseaudio window, etc).
In the meantime I noticed all kinds of broken GTK2 and GTK3 apps. My lightdm greeter has serious colour issues, I can't get rid of an Evolution calender password request, all kinds of boxes and Windows, e.g. Roxterm appear on strange positions and with odd sizes etc. pp..
I still had no time to continue downgrading.
On Mon, 11 Apr 2016 11:07:30 +0200, Ralf Mardorf wrote:
Evolution calender password request
This is not related to the GTK2 and GTK3 issues, it's an issue for the new Evolution, caused by Yahoo/Rocketmail.
But I found several other additional issues for GTK2 and GTK3 apps, most likely I'll restore my Arch Linux from a backup and stop upgrading as long as possible, since my production machine is totally broken at the moment. Not only the look is ugly, it's really a broken install.
I'm sure you could tell the difference there.
cheers! mar77i
On Mon, 11 Apr 2016 15:07:56 +0200, Martti Kühne wrote:
I'm sure you could tell the difference there.
Yes, I can, but I don't know against what to file bugs. GTK3 apps default to grotesque window sizes, don't remember region settings inside the windows, became unreadable due to invisible text, e.g. Firefox' "Clear recent history" could be readable or it could be empty, it even is always the same, if I open the dialog. GTK2 apps have font rendering issues and e.g. Claws editor window's subject field doesn't allow to position the cursor at some positions. Since I launch several scripts by a menu inside roxterm, it's breaking my workflow, if the default size is insane small. Perhaps it's a vte3 issue, since it also gets upgraded, OTOH it's based on GTK.
However, even a restless look, by unnecessary lines isn't fun for me, regarding dyslexia letters and words are already moving around and/or shift to coloured bars by my perception, so I really need a clean GUI layout. GUI layouts with all kinds of lines and bars and shadows and light reflex, intrusive colours could stress me. It's not just a matter of taste for me.
You should reckon that within the next days more users will experience issues, they'll consider being serious issues. More people will upgrade, more people will reopen apps or restart their computers. It might take a while before all the drawbacks and regressions rear their ugly heads.
On 2016-04-11 15:56, Ralf Mardorf wrote:
On Mon, 11 Apr 2016 15:07:56 +0200, Martti Kühne wrote:
I'm sure you could tell the difference there.
Yes, I can, but I don't know against what to file bugs. GTK3 apps default to grotesque window sizes, don't remember region settings inside the windows, became unreadable due to invisible text, e.g. Firefox' "Clear recent history" could be readable or it could be empty, it even is always the same, if I open the dialog. GTK2 apps have font rendering issues and e.g. Claws editor window's subject field doesn't allow to position the cursor at some positions. Since I launch several scripts by a menu inside roxterm, it's breaking my workflow, if the default size is insane small. Perhaps it's a vte3 issue, since it also gets upgraded, OTOH it's based on GTK.
However, even a restless look, by unnecessary lines isn't fun for me, regarding dyslexia letters and words are already moving around and/or shift to coloured bars by my perception, so I really need a clean GUI layout. GUI layouts with all kinds of lines and bars and shadows and light reflex, intrusive colours could stress me. It's not just a matter of taste for me.
You should reckon that within the next days more users will experience issues, they'll consider being serious issues. More people will upgrade, more people will reopen apps or restart their computers. It might take a while before all the drawbacks and regressions rear their ugly heads.
You should never update GTK2 or GTK3 before you are sure that the themes and fonts you are using is updated.
Try doing more research on updates before installing them if stability is critical for you
On Mon, 11 Apr 2016 16:01:40 +0200, Qdaxfa wrote:
Try doing more research on updates before installing them if stability is critical for you
Such a disaster never happened for minimalist environments (openbox, jwm with an uncritical theme as Adwaita) within all the years I'm using Arch Linux. This happened for bloated DEs such as Xfce or much more bloated DEs, especially when using exotic fonts and themes. I don't overdo reading changelogs/release notes, but actually I care about such information, I'm not a newbie.
On 11/04/16 15:12, Ralf Mardorf wrote:
On Mon, 11 Apr 2016 16:01:40 +0200, Qdaxfa wrote:
Try doing more research on updates before installing them if stability is critical for you
Such a disaster never happened for minimalist environments (openbox, jwm with an uncritical theme as Adwaita) within all the years I'm using Arch Linux. This happened for bloated DEs such as Xfce or much more bloated DEs, especially when using exotic fonts and themes. I don't overdo reading changelogs/release notes, but actually I care about such information, I'm not a newbie.
It is not unreasonable to assume that at least the basic themes work correctly, even on a rolling release.
I'm with gurnaik on this one... Up until a few days ago, I had done weekly updates on my arch system for the past 3 years without breakage. If doing an update renders your system unusable, that's kind of an issue.. Luckily I have a notebook backup.
On Mon, Apr 11, 2016 at 10:16 AM, gurnaik gurnaikv@gmail.com wrote:
On 11/04/16 15:12, Ralf Mardorf wrote:
On Mon, 11 Apr 2016 16:01:40 +0200, Qdaxfa wrote:
Try doing more research on updates before installing them if stability is critical for you
Such a disaster never happened for minimalist environments (openbox, jwm with an uncritical theme as Adwaita) within all the years I'm using Arch Linux. This happened for bloated DEs such as Xfce or much more bloated DEs, especially when using exotic fonts and themes. I don't overdo reading changelogs/release notes, but actually I care about such information, I'm not a newbie.
It is not unreasonable to assume that at least the basic themes work correctly, even on a rolling release.
On 11 April 2016 at 21:05, D C camenschic@gmail.com wrote:
I'm with gurnaik on this one... Up until a few days ago, I had done weekly updates on my arch system for the past 3 years without breakage. If doing an update renders your system unusable, that's kind of an issue.. Luckily I have a notebook backup.
Well, unusable is slightly exaggerated if it's just about the themes. I agree, the update was pretty annoying. I had to switch back to Adwaita for GTK3, and I really don't like Adwaita. A warning in an announcement would have been nice.
But it is usable, with an (in my opinion) ugly theme.
-- Maarten
My theme was broken as well, but switching to Adwaita worked.
I hope in future at least a warning message would be issued...
On Mon, Apr 11, 2016, 11:42 PM Maarten de Vries maarten@de-vri.es wrote:
On 11 April 2016 at 21:05, D C camenschic@gmail.com wrote:
I'm with gurnaik on this one... Up until a few days ago, I had done
weekly
updates on my arch system for the past 3 years without breakage. If doing an update renders your system unusable, that's kind of an issue..
Luckily I
have a notebook backup.
Well, unusable is slightly exaggerated if it's just about the themes. I agree, the update was pretty annoying. I had to switch back to Adwaita for GTK3, and I really don't like Adwaita. A warning in an announcement would have been nice.
But it is usable, with an (in my opinion) ugly theme.
-- Maarten
On Mon, 11 Apr 2016 19:14:48 +0000, Sajjad Heydari wrote:
My theme was broken as well, but switching to Adwaita worked.
Actually Adwaita, which wasn't upgraded, does look different after the upgrade. I already used Adwaita before the upgrade. Perhaps I could fix the lightdm greeter by switching to Adwaita.
I downgraded the adwaita-icon-theme to get rid of the new, completely different icons.
But as already pointed out, it's not just a broken look, some functionality doesn't work anymore. Evolution upstream fixed several bugs that are related to the GTK changes, 3.20.1 was released today and I build it using ABS. However, Claws still has got issues with the mouse-cursor in the subject line.
[rocketmouse@archlinux ~]$ grep -v '#' .gtkrc-2.0
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
[rocketmouse@archlinux ~]$ cat .config/gtk-3.0/settings.ini [Settings] gtk-theme-name=Adwaita gtk-font-name=FreeSans 12
[rocketmouse@archlinux ~]$ grep theme-name= /etc/lightdm/lightdm-gtk-greeter.conf theme-name=Zen-papero icon-theme-name=GNOME [rocketmouse@archlinux ~]$ wmctrl -m Name: Openbox Class: PID: N/A Window manager's "showing the desktop" mode: OFF
[rocketmouse@archlinux ~]$ grep theme-name= /etc/lightdm/lightdm-gtk-greeter.conf theme-name=Zen-papero icon-theme-name=GNOME
[rocketmouse@archlinux ~]$ sudo pacman -Syu [snip] warning: adwaita-icon-theme: ignoring package upgrade (3.18.0-1 => 3.20-1) [snip] warning: evolution: local (3.20.1-1) is newer than extra (3.20.0-1) warning: evolution-bogofilter: local (3.20.1-1) is newer than extra (3.20.0-1) warning: evolution-data-server: local (3.20.1-1) is newer than extra (3.20.0-2) warning: evolution-spamassassin: local (3.20.1-1) is newer than extra (3.20.0-1) [snip]
Hi,
But I found several other additional issues for GTK2 and GTK3 apps, most likely I'll restore my Arch Linux from a backup and stop upgrading as long as possible, since my production machine is totally broken at the moment. Not only the look is ugly, it's really a broken install.
You use a rolling release and complain about what comes with it. Maybe you should stick with Debian Lenny.
On Mon, 11 Apr 2016 15:31:07 +0200, Bjoern Franke wrote:
But I found several other additional issues for GTK2 and GTK3 apps, most likely I'll restore my Arch Linux from a backup and stop upgrading as long as possible, since my production machine is totally broken at the moment. Not only the look is ugly, it's really a broken install.
You use a rolling release and complain about what comes with it. Maybe you should stick with Debian Lenny.
I don't complain against a rolling release model, I need this model to be able to build recent audio production software. I complain against GTK issues caused by upstream and hoped somebody knows what packages to downgrade.
Ralf Mardorf silver.bullet@zoho.com writes:
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
For me, the recent fontconfig package in testing has changed the way bold fonts are rendered. I have downgraded fontconfig manually since I couldn't find a way to fix this.
With 2.11.94: http://msujith.org/dir/img/before-fontconfig-update.png With 2.11.95: http://msujith.org/dir/img/after-fontconfig-update.png
I use the Greybird theme for gtk2 applications and it seems to be okay. gtk-3.20 has changed theming and so all themes need to be updated. After gtk-3.20, Greybird broke and I had to remove it from gtk-3.0/settings.ini and use the default theme.
https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/
All of this hand-holding is just painful and sometimes I just want to compile Emacs with --with-x-toolkit=lucid and be done. :-)
Sujith
There have been a few bugs reported about the gtk 3.20 theming issues[1]
and in those bugs it mentions that there is a fix upstream that we just have to wait until it trickles down[2]
It seems that 3.20 requires themes to update something (not sure what) and this is the problem
Get on to the people who produce your themes to make them compatible with 3.20
I have found avoiding gtk3 where possible atm is helping. I am using the aur version of firefox that is compiled against gtk2 and it seems to be working better (also less memory so I may actually continue to use it when this is all done)
This is the fun of Arch isn't it? - we are the bug finders!
[1]https://bugs.archlinux.org/task/48853; https://bugs.archlinux.org/task/48855; https://bugs.archlinux.org/task/48783 [2]https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-20&id=6144b2276c729804...
On Mon, Apr 11, 2016 at 11:24 AM, Sujith Manoharan sujith@msujith.org wrote:
Ralf Mardorf silver.bullet@zoho.com writes:
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
For me, the recent fontconfig package in testing has changed the way bold fonts are rendered. I have downgraded fontconfig manually since I couldn't find a way to fix this.
With 2.11.94: http://msujith.org/dir/img/before-fontconfig-update.png With 2.11.95: http://msujith.org/dir/img/after-fontconfig-update.png
I use the Greybird theme for gtk2 applications and it seems to be okay. gtk-3.20 has changed theming and so all themes need to be updated. After gtk-3.20, Greybird broke and I had to remove it from gtk-3.0/settings.ini and use the default theme.
https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/
All of this hand-holding is just painful and sometimes I just want to compile Emacs with --with-x-toolkit=lucid and be done. :-)
Sujith
On Mon, 11 Apr 2016 06:54:20 +0530, Sujith Manoharan wrote:
For me, the recent fontconfig package in testing has changed the way bold fonts are rendered.
I also have a broken font rendering since yesterday and I'm neither using testing nor was fontconfig upgraded yesterday.
[2016-03-29 08:01] [ALPM] upgraded fontconfig (2.11.1-2 -> 2.11.94-1) [2016-03-31 09:27] [ALPM] upgraded lib32-fontconfig (2.11.1-1 -> 2.11.94-1)
On Mon, 11 Apr 2016 12:30:44 +1000, Andrew Ridgway wrote:
I have found avoiding gtk3 where possible atm is helping.
I prefer GTK2 apps over GTK3 apps since a long time ago, that's why I'm using Claws, spacefm-gtk2 and other apps.
Cool, some elements of GTK2 apps use a different font rendering than others and even positioning the mouse cursor is broken for some elements. I would like to report bugs upstream, but I don't know what exactly is the culprit.
On Mon, Apr 11, 2016 at 4:30 AM, Andrew Ridgway ar17787@gmail.com wrote:
There have been a few bugs reported about the gtk 3.20 theming issues[1]
and in those bugs it mentions that there is a fix upstream that we just have to wait until it trickles down[2]
It seems that 3.20 requires themes to update something (not sure what) and this is the problem
Get on to the people who produce your themes to make them compatible with 3.20
I have found avoiding gtk3 where possible atm is helping. I am using the aur version of firefox that is compiled against gtk2 and it seems to be working better (also less memory so I may actually continue to use it when this is all done)
This is the fun of Arch isn't it? - we are the bug finders!
[1]https://bugs.archlinux.org/task/48853; https://bugs.archlinux.org/task/48855; https://bugs.archlinux.org/task/48783 [2]https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-20&id=6144b2276c729804...
Given that the gtk3 devs do not intend to support theming, it would be great if they officially stated so and communicated that theming gtk3 is unwelcome, so that theme authors could spend their time on more fruitful efforts.
As it stands right now, most themes do not work across gtk3 version and you need to match the theme with your distro gtk3 version, which means you cannot shared ~/.themes between two distros or distro branches.
Therefore, I can absolutely understand users' desire to prefer gtk2 builds of applications.
I myself, tried to port my custom gtk2 Raleigh style to gtk3 with some level of success, but it neither looks as nice as gtk2 nor does it behave as performant.
gtk3 since 3.18 or so got much slower as well and for each and every window that is drawn it first shows a black rectangle before the widgets appear.
I've tried communicating the issues upstream, but I was met with replies that boiled down to "use Adwaita".
gtk.org could fix all of this by officially announcing there's no theme support.
On April 14, 2016 at 10:37 AM Carsten Mattner carstenmattner@gmail.com wrote: Given that the gtk3 devs do not intend to support theming
https://blogs.gnome.org/mclasen/2015/11/20/a-gtk-update/
https://blogs.gnome.org/mclasen/2015/12/22/css-boxes-in-gtk/
https://developer.gnome.org/gtk3/stable/chap-css-overview.html
Cheers, Jonathan
On Thu, 14 Apr 2016 16:37:13 +0200, Carsten Mattner wrote:
gtk3 since 3.18 or so got much slower as well and for each and every window that is drawn it first shows a black rectangle before the widgets appear.
Hi Carsten,
I'm using a GTK2 and GTK3 version of Rodent [1], if I open a directory that contains many files, the GTK3 version takes very long, that long, that it is completely unusable, while the GTK2 version works without a performance issue.
OTOH, I notice the performance issue you described for Evolution, but not for the GTK3 version of Roxterm [2], so it seems to depend on the app using GTK3, but not necessarily on GTK3.
Regards, Ralf
[1] # pacman -Qi librfm5|grep Des;pacman -Qi librfm5|grep Depe|cut -d" " -f15 Description : Rodent file manager library gtk3 # systemd-nspawn -q apt-cache showpkg rodent|cut -d" " -f24|grep -v ^$ libgtk2.0-0
[2] # pacman -Q evolution roxterm evolution 3.20.1-1 roxterm 3.3.2-1
On Thu, 14 Apr 2016 19:52:40 +0200, Ralf Mardorf wrote:
On Thu, 14 Apr 2016 16:37:13 +0200, Carsten Mattner wrote:
gtk3 since 3.18 or so got much slower as well and for each and every window that is drawn it first shows a black rectangle before the widgets appear.
[snip] I notice the performance issue you described for Evolution, but not for the GTK3 version of Roxterm [2], so it seems to depend on the app using GTK3, but not necessarily on GTK3.
Oops, I'm mistaken, as soon as a Roxterm window shows a little bit more, e.g. 'Preferences > Edit Current Profile', the black box is shown too.
On Thu, Apr 14, 2016 at 8:23 PM, Ralf Mardorf silver.bullet@zoho.com wrote:
On Thu, 14 Apr 2016 19:52:40 +0200, Ralf Mardorf wrote:
On Thu, 14 Apr 2016 16:37:13 +0200, Carsten Mattner wrote:
gtk3 since 3.18 or so got much slower as well and for each and every window that is drawn it first shows a black rectangle before the widgets appear.
[snip] I notice the performance issue you described for Evolution, but not for the GTK3 version of Roxterm [2], so it seems to depend on the app using GTK3, but not necessarily on GTK3.
Oops, I'm mistaken, as soon as a Roxterm window shows a little bit more, e.g. 'Preferences > Edit Current Profile', the black box is shown too.
With all the stuff Gtk3 is doing, maybe it should be GNOME-exclusive and let everyone else continue using what has been working properly, albeit without HiDPI, if you need that.
I also checked gtk3-widget-factory as found in arch stable (3.20), and Raleigh is totally broken. No custom theme, just selecting Raleigh as theme (engine) and menus are totally broken. I didn't try in GNOME, but I use Gtk3 because apps use it, not because I want GNOME. Of course, this also means I had to port my colour-customization Raleigh theme again, but it's equally broken as the built-in Raleigh theme. I'm not even mentioning that I found no way to configure scrollbar buttons as I do in my gtk2 theme.
Qt5 has a 30MB base overhead for any app (window), but it didn't break randomly from Qt4 to Qt5 for the apps I use it in.
I have no idea what's going with Gtk3, but I never once had such issues with either Gtk1 or Gtk2. Strange new world...
On Mon, Apr 11, 2016 at 06:54:20AM +0530, Sujith Manoharan wrote:
For me, the recent fontconfig package in testing has changed the way bold fonts are rendered. I have downgraded fontconfig manually since I couldn't find a way to fix this.
With 2.11.94: http://msujith.org/dir/img/before-fontconfig-update.png With 2.11.95: http://msujith.org/dir/img/after-fontconfig-update.png
This may be caused by "/etc/fonts/conf.d/10-hinting-slight.conf" which is now shipped with fontconfig-2.11.95. You can override this either system-wide or with a per-user configuration file.
https://wiki.archlinux.org/index.php/font_configuration#Hintstyle https://wiki.archlinux.org/index.php/font_configuration#Fontconfig_configura...
I, personally, just do this:
https://github.com/vain/dotfiles-pub/commit/94da51582297d6dd68397dae59d6b368...
Cheers Peter
Peter Hofmann arch-lists@uninformativ.de writes:
This may be caused by "/etc/fonts/conf.d/10-hinting-slight.conf" which is now shipped with fontconfig-2.11.95. You can override this either system-wide or with a per-user configuration file.
https://wiki.archlinux.org/index.php/font_configuration#Hintstyle https://wiki.archlinux.org/index.php/font_configuration#Fontconfig_configura...
I, personally, just do this:
https://github.com/vain/dotfiles-pub/commit/94da51582297d6dd68397dae59d6b368...
This fixed the issue with bold fonts. Thanks !
Sujith
For what it's worth, I was able to resolve this issue in the end by simply removing + reinstalling my theme (which was Arc). Installing Adwaita also worked.
Removing and reinstalling solved the issue because it rebuilt against Gnome 3.20. I'd only recently switched to Arch, and had therefore wrongly assumed that anything that needed to would be rebuilt against the new Gnome version.
Lesson learned :)
On Mon, 11 Apr 2016, Ralf Mardorf wrote:
Hi,
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
I'll downgrade one package after the other, but perhaps somebody could give me a hint what package/s might have caused the new unfavourable look.
One problem is shown here, a dilettante repeated unnecessarily design, e.g. a bar that already separates regions inside a window, became a bar with a cutting line inside the bar:
http://lists.claws-mail.org/pipermail/users/attachments/20160410/7fdca7e7/at...
The list of packages that were upgraded is posted here:
http://lists.claws-mail.org/pipermail/users/2016-April/016236.html
[rocketmouse@archlinux ~]$ grep -v '#' .gtkrc-2.0
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
Regards, Ralf
On Tue, 12 Apr 2016 14:15:45 +0930 Stephen mailman@tuxcon.com wrote:
For what it's worth, I was able to resolve this issue in the end by simply removing + reinstalling my theme (which was Arc). Installing Adwaita also worked.
Removing and reinstalling solved the issue because it rebuilt against Gnome 3.20. I'd only recently switched to Arch, and had therefore wrongly assumed that anything that needed to would be rebuilt against the new Gnome version.
Everything *in the repos* that needed to was rebuilt against 3.20. The Arc theme is in the AUR, which you have to manage yourself.
Lesson learned :)
Appreciate the clarification - I was not aware that this was the case, but it does make sense. Is this true of fetching updates as well, or only in terms of rebuilding things? Thanks! On Mon, 11 Apr 2016, Doug Newgard wrote:
On Tue, 12 Apr 2016 14:15:45 +0930 Stephen mailman@tuxcon.com wrote:
For what it's worth, I was able to resolve this issue in the end by simply removing + reinstalling my theme (which was Arc). Installing Adwaita also worked.
Removing and reinstalling solved the issue because it rebuilt against Gnome 3.20. I'd only recently switched to Arch, and had therefore wrongly assumed that anything that needed to would be rebuilt against the new Gnome version.
Everything *in the repos* that needed to was rebuilt against 3.20. The Arc theme is in the AUR, which you have to manage yourself.
Lesson learned :)
On Tue, 12 Apr 2016 14:47:16 +0930 Stephen mailman@tuxcon.com wrote:
Appreciate the clarification - I was not aware that this was the case, but it does make sense. Is this true of fetching updates as well, or only in terms of rebuilding things? Thanks!
Please stop top posting.
Yes, it would include updates. AUR helpers can help notify you on updates as well, but you should really understand how the AUR and package building works before relying on a helper.
I'm sorry, but my mail client (mutt) certainly does show these as being threaded under, and not top level replies. I don't know why it would be showing up otherwise for you, because I've replied direct to yours each time.
I have a top level understanding of the process involved with AUR and package building; I have not yet built packages myself though. I'll give that a go next in order to increase my understanding.
Thanks for your time, sorry for the bother. On Tue, 12 Apr 2016, Doug Newgard wrote:
On Tue, 12 Apr 2016 14:47:16 +0930 Stephen mailman@tuxcon.com wrote:
Appreciate the clarification - I was not aware that this was the case, but it does make sense. Is this true of fetching updates as well, or only in terms of rebuilding things? Thanks!
Please stop top posting.
Yes, it would include updates. AUR helpers can help notify you on updates as well, but you should really understand how the AUR and package building works before relying on a helper.
On Tue, 12 Apr 2016 15:40:29 +0930 Stephen mailman@tuxcon.com wrote:
I'm sorry, but my mail client (mutt) certainly does show these as being threaded under, and not top level replies. I don't know why it would be showing up otherwise for you, because I've replied direct to yours each time.
Top posting refers to putting your reply above the quoted text. It's frowned upon on most mailing lists.
On Tue, 12 Apr 2016, Doug Newgard wrote:
On Tue, 12 Apr 2016 15:40:29 +0930 Stephen mailman@tuxcon.com wrote:
I'm sorry, but my mail client (mutt) certainly does show these as being threaded under, and not top level replies. I don't know why it would be showing up otherwise for you, because I've replied direct to yours each time.
Top posting refers to putting your reply above the quoted text. It's frowned upon on most mailing lists.
I apologise, I didn't realise this was the case. I've often read, but never participated in, mailing lists. Is there a list of "common etiquette" that you'd recommend reading? I'd like to avoid embarrassing issues such as this again.
On 04/12/2016 02:23 AM, Stephen wrote:
I apologise, I didn't realise this was the case. I've often read, but never participated in, mailing lists. Is there a list of "common etiquette" that you'd recommend reading? I'd like to avoid embarrassing issues such as this again.
You can google "mailing list etiquette" to see some examples.
The main rules are: - plaintext, not HTML mail - no attachments - wrap lines at 72 characters - post replies inline, below the quote (bottom-posting) - remove extraneous quoted matter, especially nested quotes
On Tue, 12 Apr 2016 03:08:06 -0400, Eli Schwartz wrote:
On 04/12/2016 02:23 AM, Stephen wrote:
I apologise, I didn't realise this was the case. I've often read, but never participated in, mailing lists. Is there a list of "common etiquette" that you'd recommend reading? I'd like to avoid embarrassing issues such as this again.
You can google "mailing list etiquette" to see some examples.
The main rules are:
- plaintext, not HTML mail
- no attachments
Some mailing lists allow small attachments. But it's also common practise to use http://pastebin.com/, http://picpaste.com/ and smlar sites and then just to post links.
- wrap lines at 72 characters
At around 72, <= 80. 72 is the most common used value. When posting snippets of code or command line output, line wrapping should be avoided.
- post replies inline, below the quote (bottom-posting)
- remove extraneous quoted matter, especially nested quotes
In addition:
- If somebody wants to reply to digest, MIME digest should be used, to keep subject and thread of the original posts.
Reply-to headers shouldn't be used, they could break mailing list replies for some MUAs on some mailing lists and we usually should reply to the mailing lists only.
On Tue, Apr 12, 2016 at 10:06 AM, Ralf Mardorf silver.bullet@zoho.com wrote:
Some mailing lists allow small attachments. But it's also common practise to use http://pastebin.com/, http://picpaste.com/ and smlar sites and then just to post links.
If the data is of intermittent use and interest, that might be a good idea, but linking to an external pastebin which can go defunct or the page go missing/removed, I'd advise against a policy like that. You'd get an archived list post which links to something you cannot load anymore.
Unsubscribe On Apr 12, 2016 1:06 AM, "Ralf Mardorf" silver.bullet@zoho.com wrote:
On Tue, 12 Apr 2016 03:08:06 -0400, Eli Schwartz wrote:
On 04/12/2016 02:23 AM, Stephen wrote:
I apologise, I didn't realise this was the case. I've often read, but never participated in, mailing lists. Is there a list of "common etiquette" that you'd recommend reading? I'd like to avoid embarrassing issues such as this again.
You can google "mailing list etiquette" to see some examples.
The main rules are:
- plaintext, not HTML mail
- no attachments
Some mailing lists allow small attachments. But it's also common practise to use http://pastebin.com/, http://picpaste.com/ and smlar sites and then just to post links.
- wrap lines at 72 characters
At around 72, <= 80. 72 is the most common used value. When posting snippets of code or command line output, line wrapping should be avoided.
- post replies inline, below the quote (bottom-posting)
- remove extraneous quoted matter, especially nested quotes
In addition:
- If somebody wants to reply to digest, MIME digest should be used, to keep subject and thread of the original posts.
Reply-to headers shouldn't be used, they could break mailing list replies for some MUAs on some mailing lists and we usually should reply to the mailing lists only.
Unsubscribe
To unsubscribe, use the request address instead of the main one.
On Tue, Apr 12, 2016 at 6:59 AM, Doug Newgard scimmia@archlinux.info wrote:
Everything *in the repos* that needed to was rebuilt against 3.20. The Arc theme is in the AUR, which you have to manage yourself.
So then, for example qtcurve must be rebuilt? Should I file a bug report?
On Tue, 12 Apr 2016 07:43:10 +0200 SanskritFritz sanskritfritz@gmail.com wrote:
On Tue, Apr 12, 2016 at 6:59 AM, Doug Newgard scimmia@archlinux.info wrote:
Everything *in the repos* that needed to was rebuilt against 3.20. The Arc theme is in the AUR, which you have to manage yourself.
So then, for example qtcurve must be rebuilt? Should I file a bug report?
What does qtcurve have to do with gtk3?
Ralf Mardorf wrote:
after the last upgrade GTK2 apps running in an openbox session need more space, they became darker and in some windows even the fonts became less good readable. The reason that I dropped desktop environments was to get rid of chaotic designs and to keep a clear design and now even GTK2 apps in an openbox session became a parody.
...
[rocketmouse@archlinux ~]$ grep -v '#' .gtkrc-2.0
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
Regards, Ralf
My first thought was "Adwaita", and looking at the list of packages, gnome-themes-standard is upgraded. I suspect that Adwaita is the culprit.
Have you tried other GTK themes? Clearlooks-Phenix, or maybe a gtk2-only theme such as Bluecurve?
On my side, I have been using Clearlooks-Phenix and Bluecurve over the past few days. (I recently switched back to Bluecurve.) I haven't noticed any change in GTK2 apps over the past couple days. So, I'm apt to blame Adwaita.
On a side note, I remember a recent GNOME propaganda video said that GNOME had finally standardized their theming API for gtk3? I didn't believe them then, and I certainly don't believe them now after reading this thread.
So, I think this might be a case of GNOME deciding that making the UI elements even bigger is the hip thing to do. (It's just frustrating that GNOME is so eager to break things nowadays.)
If Adwaita really is the culprit, file a bug with GNOME. That's their domain.
I hope this information may be of help, --Kyle
https://aur.archlinux.org/packages/clearlooks-phenix-gtk-theme https://aur.archlinux.org/packages/gtk-bluecurve-engine
On Mon, 11 Apr 2016 22:06:33 -0700, Kyle Terrien wrote:
My first thought was "Adwaita", and looking at the list of packages, gnome-themes-standard is upgraded. I suspect that Adwaita is the culprit.
My mind went blank for a long "moment", I missed that Adwaita is part of this package. Thank you very much :).
$ grep gnome-themes-standard /var/log/pacman.log | grep 2016-04 [2016-04-10 19:57] [ALPM] upgraded gnome-themes-standard (3.18.0-1 -> 3.20-1) [2016-04-12 09:33] [PACMAN] Running 'pacman -U gnome-themes-standard-3.18.0-1-x86_64.pkg.tar.xz' [2016-04-12 09:33] [ALPM] downgraded gnome-themes-standard (3.20-1 -> 3.18.0-1)
Now the old look is back :), this not necessarily means that I also got rid of GTK hiccups.
If Adwaita really is the culprit, file a bug with GNOME. That's their domain.
OTOH, GTK2 apps are affected and the GNOME maintainers likely want to make GTK2 apps look consistent with GTK3 GNOME apps, so that they fit better to the bad design of the GNOME desktop environment. No, I dislike insults from upstream, when reporting an issue. I have given up to report to this kind of upstream, a long time ago.
Ralf Mardorf wrote:
$ grep gnome-themes-standard /var/log/pacman.log | grep 2016-04 [2016-04-10 19:57] [ALPM] upgraded gnome-themes-standard (3.18.0-1 -> 3.20-1) [2016-04-12 09:33] [PACMAN] Running 'pacman -U gnome-themes-standard-3.18.0-1-x86_64.pkg.tar.xz' [2016-04-12 09:33] [ALPM] downgraded gnome-themes-standard (3.20-1 -> 3.18.0-1)
Now the old look is back :), this not necessarily means that I also got rid of GTK hiccups.
:-)
If Adwaita really is the culprit, file a bug with GNOME. That's their domain.
OTOH, GTK2 apps are affected and the GNOME maintainers likely want to make GTK2 apps look consistent with GTK3 GNOME apps, so that they fit better to the bad design of the GNOME desktop environment. No, I dislike insults from upstream, when reporting an issue. I have given up to report to this kind of upstream, a long time ago.
Ugh! Yeah, there probably isn't much a case to be made on their Bugzilla. I imagine that they will justify the change as a feature to "make the geometry of elements match in both GTK2 and GTK3".
The best thing to do at this point is design a GTK3 theme that sucks less (and maintain it when GNOME makes the arbitrary changes to the GTK3 theming API again). Clearlooks-Phenix is good. Perhaps a Bluecurve-Phenix would be fun too.
(Someone really should adjust the attitude of the GNOME devs. I am sick of the crap coming out of GNOME 3 breaking stuff and making other things ugly.)
--Kyle
On 12-04-2016 16:50, Kyle Terrien wrote:
The best thing to do at this point is design a GTK3 theme that sucks less (and maintain it when GNOME makes the arbitrary changes to the GTK3 theming API again). Clearlooks-Phenix is good. Perhaps a Bluecurve-Phenix would be fun too.
I was using clearlooks-phenix but with gtk 3.20 it is quite broken and it hasn't been updated in quite some time. I have no idea if the dev will code a new version for gtk 3.20+.
For now I'm using TraditionalOK from mate-themes, it is quite similar to clearlooks-phenix and most gtk 3.20 bugs should be ironed out.
On 04/12/2016 07:08 PM, Mauro Santos wrote:
I was using clearlooks-phenix but with gtk 3.20 it is quite broken and it hasn't been updated in quite some time. I have no idea if the dev will code a new version for gtk 3.20+.
When launching a GTK3 application with the clearlooks phenix theme, there are several warnings that feature such-and-such has been deprecated and replaced by so-and-so. I've tried applying all the suggested replacements and that got rid of the warnings, but unfortunately it didn't fix the looks :( Downgrading for now and hoping someone who knows more about GTK3 theme will update clearlooks phenix or make some similar clearlooks-like theme for GTK 3.20+
Jerome
Jérôme M. Berger wrote:
On 04/12/2016 07:08 PM, Mauro Santos wrote:
I was using clearlooks-phenix but with gtk 3.20 it is quite broken and it hasn't been updated in quite some time. I have no idea if the dev will code a new version for gtk 3.20+.
When launching a GTK3 application with the clearlooks phenix theme, there are several warnings that feature such-and-such has been deprecated and replaced by so-and-so. I've tried applying all the suggested replacements and that got rid of the warnings, but unfortunately it didn't fix the looks :( Downgrading for now and hoping someone who knows more about GTK3 theme will update clearlooks phenix or make some similar clearlooks-like theme for GTK 3.20+
Jerome
I noticed some of the geometry is slightly different, but I just thought it was gtk3 being libgnome. I don't test gtk3 much (and I don't know that much about gtk theming), so I wasn't aware of the deprecated warnings.
But that's it! After finals end, I am going to look into converting my favorite gtk2 theme (Bluecurve) into gtk3 theme. I am tired of ugly and/or broken gtk3 themes.
Does anyone off the top of his/her head know of any good tools or guides for converting gtk2 themes to gtk3 themes?
--Kyle
On 04/12/2016 09:07 PM, Kyle Terrien wrote:
Does anyone off the top of his/her head know of any good tools or guides for converting gtk2 themes to gtk3 themes?
--Kyle
I don't know very much, but it's all done in CSS nowadays. There are no more programmable theming engines for GTK+ 3, i.e. themes for it can't do as much, but CSS should be simpler.
You should probably take a look at the default themes [1] as an example and possibly the outdated [2] to take a look at how themes can be packaged. And of course [3] for a not fully cleaned-up reference on what is available in GTK+ CSS.
And of course this discussion will probably more fruitful on GNOME developer mailing lists [4].
[1] https://git.gnome.org/browse/gtk+/tree/gtk/theme [2] https://git.gnome.org/browse/gnome-themes-standard/tree/ [3] https://developer.gnome.org/gtk3/unstable/theming.html [4] https://mail.gnome.org/
Florian Pelz wrote:
On 04/12/2016 09:07 PM, Kyle Terrien wrote:
Does anyone off the top of his/her head know of any good tools or guides for converting gtk2 themes to gtk3 themes?
--Kyle
I don't know very much, but it's all done in CSS nowadays. There are no more programmable theming engines for GTK+ 3, i.e. themes for it can't do as much, but CSS should be simpler.
You should probably take a look at the default themes [1] as an example and possibly the outdated [2] to take a look at how themes can be packaged. And of course [3] for a not fully cleaned-up reference on what is available in GTK+ CSS.
And of course this discussion will probably more fruitful on GNOME developer mailing lists [4].
[1] https://git.gnome.org/browse/gtk+/tree/gtk/theme [2] https://git.gnome.org/browse/gnome-themes-standard/tree/ [3] https://developer.gnome.org/gtk3/unstable/theming.html [4] https://mail.gnome.org/
Thank you! I look forward to researching this. --Kyle
After installing fontconfig I didn't notice an issue for Claws, Roxterm, SpaceFM and a few other apps. It was the other way around. For testing purpose I reinstalled the new Adwaita again and the fonts for my GTK2 apps didn't become that disgusting again, as the fonts for GTK3 apps are. However, the new Adwaita is totally broken for GTK2 apps. This can be noticed by users who have a lot of GTK2 apps installed, e.g. spacefm-gtk2, instead of spacefm. For this very reason I stay with the outdated theme. Using the outdated theme seems to have no side effects for GTK3 apps yet.
I don't know if it's related to the GTK things that were upgraded or to fontconfig or to what ever else. Sometimes, but not too seldom I run xfw and very seldom I run xfe. Both don't use the fonts anymore I once upon a time chose. Instead of IIRC monospace, they use exotic fonts nobody ever would chose for this kinds of apps. IOW it's not that monospace was replaced by another kind of monospace, it was replaced by really, really exotic fonts.
It's a PITA that even users who don't use GNOME, KDE or similar crap nowadays get broken environments, because even apps that are not from a bloatware DE break.
Reminds me of Bill Hick talking to people who are in advertising or marketing. "No really, there's no rationalization for what you do, and you are Satan's little helpers, OK?" This seems to fit good to some upstream developers too.
Maybe this is asking for DDoS attacks against GNOME :D.
SICR
I noticed natural scrolling is broken as well. Does anyone has a fix?
On Wed, Apr 13, 2016, 6:53 PM Ralf Mardorf silver.bullet@zoho.com wrote:
After installing fontconfig I didn't notice an issue for Claws, Roxterm, SpaceFM and a few other apps. It was the other way around. For testing purpose I reinstalled the new Adwaita again and the fonts for my GTK2 apps didn't become that disgusting again, as the fonts for GTK3 apps are. However, the new Adwaita is totally broken for GTK2 apps. This can be noticed by users who have a lot of GTK2 apps installed, e.g. spacefm-gtk2, instead of spacefm. For this very reason I stay with the outdated theme. Using the outdated theme seems to have no side effects for GTK3 apps yet.
I don't know if it's related to the GTK things that were upgraded or to fontconfig or to what ever else. Sometimes, but not too seldom I run xfw and very seldom I run xfe. Both don't use the fonts anymore I once upon a time chose. Instead of IIRC monospace, they use exotic fonts nobody ever would chose for this kinds of apps. IOW it's not that monospace was replaced by another kind of monospace, it was replaced by really, really exotic fonts.
It's a PITA that even users who don't use GNOME, KDE or similar crap nowadays get broken environments, because even apps that are not from a bloatware DE break.
Reminds me of Bill Hick talking to people who are in advertising or marketing. "No really, there's no rationalization for what you do, and you are Satan's little helpers, OK?" This seems to fit good to some upstream developers too.
Maybe this is asking for DDoS attacks against GNOME :D.
SICR
It's a PITA that even users who don't use GNOME, KDE or similar crap nowadays get broken environments, because even apps that are not from a bloatware DE break.
FWIW, I'm using a lot of KDE apps in i3WM and don't have any problems. I have the GTK problems of course, but all my QT things behave like I want them to, including the KDE ones.
I do have a minimal KDE environment installed to test every now and then, so I have export XDG_CURRENT_DESKTOP=KDE in my .xinitrc and do my QT5 settings there.
Cheers, Bennett
On Wed, 13 Apr 2016 16:28:38 +0200, Bennett Piater wrote:
It's a PITA that even users who don't use GNOME, KDE or similar crap nowadays get broken environments, because even apps that are not from a bloatware DE break.
FWIW, I'm using a lot of KDE apps in i3WM and don't have any problems. I have the GTK problems of course, but all my QT things behave like I want them to, including the KDE ones.
A misunderstanding, actually there are no new Qt issues on my machine either. An old issue is the font size. Anyway, I very often read about KDE issues, each time KDE is updated. Here all Qt apps, excepted of the font size issue are ok, as long as they are not KDE related. KDE apps tend to use some kind of gvfs equivalent, that for no valid reason wakes up sleeping external green drives again and again and the only way to get rid of it seems to be, to restart the computer after running such an app. To fix this issue for GNOME apps, just replacing the gvfs package with an empty gvfs dummy package does the trick, but I never found out how to solve this issue for KDE apps. However, I don't need to use either KDE or GNOME apps, but I need to use GTK and Qt apps. Actually the only apps I can set up to my needs are GTK2 apps with an outdated GTK theme. Since the Qt apps font size issue only affects menus and not editor windows and similar, I can live with it, but several, not all GTK3 apps are disgusting.
On 13/04/16 15:23, Ralf Mardorf wrote:
After installing fontconfig I didn't notice an issue for Claws, Roxterm, SpaceFM and a few other apps. It was the other way around. For testing purpose I reinstalled the new Adwaita again and the fonts for my GTK2 apps didn't become that disgusting again, as the fonts for GTK3 apps are. However, the new Adwaita is totally broken for GTK2 apps. This can be noticed by users who have a lot of GTK2 apps installed, e.g. spacefm-gtk2, instead of spacefm. For this very reason I stay with the outdated theme. Using the outdated theme seems to have no side effects for GTK3 apps yet.
I don't know if it's related to the GTK things that were upgraded or to fontconfig or to what ever else. Sometimes, but not too seldom I run xfw and very seldom I run xfe. Both don't use the fonts anymore I once upon a time chose. Instead of IIRC monospace, they use exotic fonts nobody ever would chose for this kinds of apps. IOW it's not that monospace was replaced by another kind of monospace, it was replaced by really, really exotic fonts.
It's a PITA that even users who don't use GNOME, KDE or similar crap nowadays get broken environments, because even apps that are not from a bloatware DE break.
Reminds me of Bill Hick talking to people who are in advertising or marketing. "No really, there's no rationalization for what you do, and you are Satan's little helpers, OK?" This seems to fit good to some upstream developers too.
Maybe this is asking for DDoS attacks against GNOME :D.
SICR
Hi Ralf,
What packages have you downgraded to get back to the previous version of adwaita?
Richard.
On 13/04/16 at 04:23pm, Ralf Mardorf wrote:
Reminds me of Bill Hick talking to people who are in advertising or marketing. "No really, there's no rationalization for what you do, and you are Satan's little helpers, OK?" This seems to fit good to some upstream developers too.
Maybe this is asking for DDoS attacks against GNOME :D.
Given most of the drivel you post to this list, I shouldn't be surprised, but this is a new level of inanity…
Show some respect to the people that actually build stuff and contribute, not just endlessly clog mailing lists with their puerile whining.
On Thu, 14 Apr 2016 07:54:09 +1200, Jason Ryan wrote:
Given most of the drivel you post to this list, I shouldn't be surprised, but this is a new level of inanity…
Show some respect to the people that actually build stuff and contribute, not just endlessly clog mailing lists with their puerile whining.
Hi Jason,
instead of passing censure, you could have helped Richard ;).
On Wed, 13 Apr 2016 19:55:02 +0100, Richard Ullger wrote:
What packages have you downgraded to get back to the previous version of adwaita?
Hi Richard,
I downgraded
adwaita-icon-theme (3.20-1 -> 3.18.0-1)
and
gnome-themes-standard (3.20-1 -> 3.18.0-1)
but you unlikely need to downgrade the icon theme too, I just dislike some replaced icons. IOW gnome-themes-standard 3.18.0-1 fixes the GTK2 look.
Regards, Ralf
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I downgraded adwaita-icon-theme (3.20-1 -> 3.18.0-1) gnome-themes-standard (3.20-1 -> 3.18.0-1)
Where I can find out this version? - -- Have a nice day!
~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Thu Apr 14 22:57:23 2016 GMT From: flow@nym.mixmin.net
On Thu, 14 Apr 2016 23:57:23 +0100 (BST), flow wrote:
I downgraded adwaita-icon-theme (3.20-1 -> 3.18.0-1) gnome-themes-standard (3.20-1 -> 3.18.0-1)
Where I can find out this version?
I used https://aur.archlinux.org/packages/downgrade/ IOW downgrade pkgname
I guess https://aur.archlinux.org/packages/downgrader/ is a similar tool
Assumed you didn't tidy up the cache, pacman -U /var/cache/pacman/pkg/pkgname-pkgver-pkgrel-arch.pkg.tar.xz
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I downgraded adwaita-icon-theme (3.20-1 -> 3.18.0-1) and gnome-themes-standard (3.20-1 -> 3.18.0-1)
Me too. Still have yet unwanted font.
adwaita-icon-theme 3.18.0-1 gnome-themes-standard 3.18.0-1
- -- Have a nice day!
~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Sat Apr 16 02:01:28 2016 GMT From: flow@nym.mixmin.net
On Sat, 16 Apr 2016 03:01:28 +0100 (BST), flow wrote:
Still have yet unwanted font.
The rendering of fonts for my GTK2 apps is as wanted.
What do you mean?
Did you get completely wrong font types, or "just" an odd rendering? For what apps? GTK2 and/or GTK3?
My GTK2 apps are ok, some GTK3 apps have blur fonts, I only noticed that xfe and xfw had completely wrong fonts.
For me the upgraded package "fontconfig" seems not to be an issue.
Perhaps "fontconfig" does cause issues for your setup.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, 16 Apr 2016 03:01:28 +0100 (BST), flow wrote:
Still have yet unwanted font.
The rendering of fonts for my GTK2 apps is as wanted.
What do you mean?
Did you get completely wrong font types, or "just" an odd rendering? For what apps? GTK2 and/or GTK3?
Most of GTK2 apps are ok. Got wrong font in seamonkey and qupzilla only since latest upgrade.
My GTK2 apps are ok, some GTK3 apps have blur fonts, I only noticed that xfe and xfw had completely wrong fonts.
For me the upgraded package "fontconfig" seems not to be an issue.
Perhaps "fontconfig" does cause issues for your setup.
[2016-04-10 20:25] [PACMAN] Running 'pacman -Syu' [2016-04-10 20:25] [PACMAN] synchronizing package lists [2016-04-10 20:25] [PACMAN] starting full system upgrade [2016-04-10 20:31] [ALPM] transaction started [2016-04-10 20:31] [ALPM] upgraded glib2 (2.46.2-4 -> 2.48.0-1) [2016-04-10 20:31] [ALPM] upgraded gtk-update-icon-cache (3.18.9-1 -> 3.20.2-1) [2016-04-10 20:31] [ALPM] upgraded harfbuzz (1.2.4-1 -> 1.2.6-1) [2016-04-10 20:31] [ALPM] upgraded libxml2 (2.9.3-1 -> 2.9.3-2) [2016-04-10 20:31] [ALPM] upgraded mesa (11.1.2-1 -> 11.2.0-1) [2016-04-10 20:31] [ALPM] upgraded mesa-libgl (11.1.2-1 -> 11.2.0-1) [2016-04-10 20:31] [ALPM] upgraded pango (1.39.0-1 -> 1.40.0-1) [2016-04-10 20:31] [ALPM] upgraded adwaita-icon-theme (3.18.0-1 -> 3.20-1) [2016-04-10 20:31] [ALPM] upgraded at-spi2-core (2.18.3-1 -> 2.20.0-1) [2016-04-10 20:31] [ALPM] upgraded atk (2.18.0-1 -> 2.20.0-1) [2016-04-10 20:31] [ALPM] upgraded at-spi2-atk (2.18.1-1 -> 2.20.0-1) [2016-04-10 20:31] [ALPM] upgraded icu (56.1-2 -> 57.1-1) [2016-04-10 20:31] [ALPM] upgraded boost-libs (1.60.0-2 -> 1.60.0-4) [2016-04-10 20:31] [ALPM] upgraded dconf (0.24.0-1 -> 0.26.0-1) [2016-04-10 20:31] [ALPM] upgraded colord (1.2.12-1 -> 1.3.2-1) [2016-04-10 20:31] [ALPM] upgraded libxkbcommon (0.6.0-1 -> 0.6.1-1) [2016-04-10 20:31] [ALPM] upgraded json-glib (1.0.4-1 -> 1.2.0-1) [2016-04-10 20:31] [ALPM] installed wayland-protocols (1.3-1) [2016-04-10 20:31] [ALPM] upgraded gsettings-desktop-schemas (3.18.1-1 -> 3.20.0-1) [2016-04-10 20:31] [ALPM] upgraded glib-networking (2.46.1-1 -> 2.48.0-1) [2016-04-10 20:31] [ALPM] upgraded libsoup (2.52.2-1 -> 2.54.0.1-1) [2016-04-10 20:31] [ALPM] upgraded gtk3 (3.18.9-1 -> 3.20.2-1) [2016-04-10 20:31] [ALPM] upgraded cogl (1.22.0-1 -> 1.22.0+11+g81ab4a3-1) [2016-04-10 20:31] [ALPM] upgraded clutter (1.24.2-1 -> 1.26.0-1) [2016-04-10 20:31] [ALPM] upgraded clutter-gtk (1.6.6-1 -> 1.8.0-1) [2016-04-10 20:31] [ALPM] upgraded poppler (0.41.0-1 -> 0.42.0-1) [2016-04-10 20:31] [ALPM] upgraded cups-filters (1.8.3-1 -> 1.8.3-2) [2016-04-10 20:31] [ALPM] upgraded gcr (3.18.0-1 -> 3.20.0-1) [2016-04-10 20:32] [ALPM] upgraded glibmm (2.46.3-1 -> 2.48.1-1) [2016-04-10 20:32] [ALPM] upgraded gnome-keyring (1:3.18.3-1 -> 1:3.20.0-1) [2016-04-10 20:32] [ALPM] upgraded gnome-themes-standard (3.18.0-1 -> 3.20-1) [2016-04-10 20:32] [ALPM] upgraded gobject-introspection-runtime (1.46.0-1 -> 1.48.0-1) [2016-04-10 20:32] [ALPM] upgraded gstreamer (1.6.3-1 -> 1.8.0-1) [2016-04-10 20:32] [ALPM] upgraded gst-plugins-base-libs (1.6.3-1 -> 1.8.0-1) [2016-04-10 20:32] [ALPM] upgraded gst-plugins-bad (1.6.3-6 -> 1.8.0-2) [2016-04-10 20:32] [ALPM] upgraded gst-plugins-base (1.6.3-1 -> 1.8.0-1) [2016-04-10 20:32] [ALPM] upgraded yelp-xsl (3.18.1-1 -> 3.20.0-1) [2016-04-10 20:32] [ALPM] upgraded gtk-doc (1.24-1 -> 1.25-1) [2016-04-10 20:32] [ALPM] upgraded pangomm (2.38.1-2 -> 2.40.0-1) [2016-04-10 20:32] [ALPM] upgraded gtkmm3 (3.18.0-2 -> 3.20.0-1) [2016-04-10 20:32] [ALPM] upgraded gvfs (1.26.3-1 -> 1.28.0-1) [2016-04-10 20:32] [ALPM] upgraded harfbuzz-icu (1.2.4-1 -> 1.2.6-1) [2016-04-10 20:32] [ALPM] upgraded lib32-icu (56.1-2 -> 57.1-1) [2016-04-10 20:32] [ALPM] upgraded lib32-harfbuzz (1.2.4-1 -> 1.2.4-2) [2016-04-10 20:32] [ALPM] upgraded libcanberra (0.30-5 -> 0.30-6) [2016-04-10 20:32] [ALPM] upgraded libcanberra-pulse (0.30-5 -> 0.30-6) [2016-04-10 20:32] [ALPM] upgraded libcdr (0.1.2-1 -> 0.1.2-2) [2016-04-10 20:32] [ALPM] upgraded libe-book (0.1.2-4 -> 0.1.2-5) [2016-04-10 20:32] [ALPM] upgraded libmspub (0.1.2-4 -> 0.1.2-5) [2016-04-10 20:32] [ALPM] upgraded libpeas (1.16.0-1 -> 1.18.0-1) [2016-04-10 20:32] [ALPM] upgraded libvisio (0.1.5-1 -> 0.1.5-2) [2016-04-10 20:32] [ALPM] upgraded raptor (2.0.15-3 -> 2.0.15-4) [2016-04-10 20:32] [ALPM] upgraded libreoffice-still (5.0.5-2 -> 5.0.5-3) [2016-04-10 20:32] [ALPM] upgraded libsynctex (2015.37497-10 -> 2015.37497-11) [2016-04-10 20:32] [ALPM] upgraded libxkbcommon-x11 (0.6.0-1 -> 0.6.1-1) [2016-04-10 20:32] [ALPM] upgraded openttd (1.5.3-1 -> 1.6.0-1) [2016-04-10 20:32] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew [2016-04-10 20:32] [ALPM] upgraded pacman-mirrorlist (20160404-1 -> 20160410-1) [2016-04-10 20:32] [ALPM] upgraded pcsclite (1.8.15-1 -> 1.8.16-1) [2016-04-10 20:32] [ALPM] upgraded poppler-glib (0.41.0-1 -> 0.42.0-1) [2016-04-10 20:32] [ALPM] upgraded qt4 (4.8.7-7 -> 4.8.7-8) [2016-04-10 20:32] [ALPM] upgraded qt5-base (5.6.0-2 -> 5.6.0-3) [2016-04-10 20:32] [ALPM] upgraded qt5-webkit (5.6.0-2 -> 5.6.0-4) [2016-04-10 20:33] [ALPM] upgraded texlive-bin (2015.37497-10 -> 2015.37497-11) [2016-04-10 20:33] [ALPM-SCRIPTLET] >>> texlive: updating the filename database... [2016-04-10 20:33] [ALPM] upgraded vte-common (0.42.5-1 -> 0.44.0-1) [2016-04-10 20:33] [ALPM] upgraded webkit2gtk (2.10.9-1 -> 2.12.0-2) [2016-04-10 20:33] [ALPM] upgraded webkitgtk (2.4.10-1 -> 2.4.10-2) [2016-04-10 20:33] [ALPM] transaction completed - -- Have a nice day!
~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Sat Apr 16 22:04:17 2016 GMT From: flow@nym.mixmin.net
On Sat, 16 Apr 2016 23:04:17 +0100 (BST), flow wrote:
Most of GTK2 apps are ok. Got wrong font in seamonkey and qupzilla only since latest upgrade. [ALPM] upgraded qt5-base (5.6.0-2 -> 5.6.0-3) [2016-04-10 20:32] [ALPM] upgraded qt5-webkit (5.6.0-2 -> 5.6.0-4) [2016-04-10 20:33]
Qupzilla shouldn't be affected by the GTK-debacle.
Here Qupzilla and any other Qt app always used and still use wrong font sizes. I don't know how to handle Qt5 fonts. I don't care, because qtconfig-qt4, resp. .config/Trolltech.conf already had no affect at all.
[rocketmouse@archlinux ~]$ grep font .config/Trolltech.conf font="FreeSans,12,-1,5,50,0,0,0,0,0" fontPath=@Invalid() [rocketmouse@archlinux ~]$ qtconfig qtconfig qtconfig-qt3 qtconfig-qt4 [rocketmouse@archlinux ~]$ pacman -Q qupzilla qt5-base qt5-webkit qupzilla 1.8.9-2 qt5-base 5.6.0-3 qt5-webkit 5.6.0-4
On my machine the Qupzilla font is the wanted FreeSans or a very similar font, just the size is much too small, but always was much to small.
How did you select what font Qupzilla and other Qt apps should use?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Sat, 16 Apr 2016 23:04:17 +0100 (BST), flow wrote:
Most of GTK2 apps are ok. Got wrong font in seamonkey and qupzilla only since latest upgrade. [ALPM] upgraded qt5-base (5.6.0-2 -> 5.6.0-3) [2016-04-10 20:32] [ALPM] upgraded qt5-webkit (5.6.0-2 -> 5.6.0-4) [2016-04-10 20:33]
Qupzilla shouldn't be affected by the GTK-debacle.
What about seamonkey?
Here Qupzilla and any other Qt app always used and still use wrong font sizes. I don't know how to handle Qt5 fonts. I don't care, because qtconfig-qt4, resp. .config/Trolltech.conf already had no affect at all.
How did you select what font Qupzilla and other Qt apps should use?
qtconfig , font
- -- Have a nice day!
~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Sun Apr 17 16:37:08 2016 GMT From: flow@nym.mixmin.net
On Sun, 17 Apr 2016 17:37:08 +0100 (BST), flow wrote:
On Sat, 16 Apr 2016 23:04:17 +0100 (BST), flow wrote:
Most of GTK2 apps are ok. Got wrong font in seamonkey and qupzilla only since latest upgrade. [ALPM] upgraded qt5-base (5.6.0-2 -> 5.6.0-3) [2016-04-10 20:32] [ALPM] upgraded qt5-webkit (5.6.0-2 -> 5.6.0-4) [2016-04-10 20:33]
Qupzilla shouldn't be affected by the GTK-debacle.
What about seamonkey?
Here Qupzilla and any other Qt app always used and still use wrong font sizes. I don't know how to handle Qt5 fonts. I don't care, because qtconfig-qt4, resp. .config/Trolltech.conf already had no affect at all.
How did you select what font Qupzilla and other Qt apps should use?
qtconfig , font
I don't have seamonky installed, but it seems to be a GTK2 app. If gtkrc-2.0 doesn't do the job, I don't know what to do.
[rocketmouse@archlinux ~]$ cat .gtkrc-2.0 # Auto-written by gtk2_prefs. Do not edit.
gtk-theme-name = "Adwaita" style "user-font" { font_name="FreeSans 12" } widget_class "*" style "user-font"
Regarding qt5 I have no idea, and as already pointed out, I don't care, since just the font size always was and still is annoying here, but the font type is ok.
Did you read man pages and wikis?
[rocketmouse@archlinux ~]$ ls -l /usr/bin/qtconfig* lrwxrwxrwx 1 root root 9 Dec 6 02:34 /usr/bin/qtconfig -> qtchooser lrwxrwxrwx 1 root root 25 Apr 22 2015 /usr/bin/qtconfig-qt3 -> /usr/lib/qt3/bin/qtconfig lrwxrwxrwx 1 root root 25 Apr 9 09:34 /usr/bin/qtconfig-qt4 -> /usr/lib/qt4/bin/qtconfig [rocketmouse@archlinux ~]$ pacman -Qo /usr/bin/qtchooser /usr/bin/qtchooser is owned by qtchooser 53-2 [rocketmouse@archlinux ~]$ pacman -Qi qtchooser Name : qtchooser Version : 53-2 [snip] Required By : qmidiroute qt5-base Optional For : qt3 qt4 [snip]
[rocketmouse@archlinux ~]$ pacman -Si seamonkey [snip] Depends On : [snip] gtk2 [snip]
"GTK+ and Qt If you have GTK+ and Qt applications, their looks might not exactly blend in very well. If you wish to make your GTK+ styles match your Qt styles please read Uniform look for Qt and GTK applications. Configuration of Qt apps under environments other than KDE Unlike Qt4, Qt5 doesn't ship a qtconfig utility to configure fonts, icons or styles. Instead, it will try to use the settings from the running DE. In KDE or GNOME this works well, but in other less popular DEs or WM it can lead to missing icons in Qt5 applications. One way to solve this is to fake the running desktop environment by setting XDG_CURRENT_DESKTOP=KDE or GNOME, and then using the corresponding configuration application to set the desired icon set. Another solution is provided by the qt5ct package, which provides a DE independent Qt5 QPA and a configuration utility. After installing the package, run qt5ct to set an icon theme, and set the environment variable QT_QPA_PLATFORMTHEME="qt5ct" so that the settings are picked up by Qt applications." - https://wiki.archlinux.org/index.php/qt#GTK.2B_and_Qt
On Sat, 16 Apr 2016 23:04:17 +0100 (BST), flow wrote:
Got wrong font in [snip] qupzilla only since latest upgrade.
[rocketmouse@archlinux ~]$ cat /etc/profile.d/qt5ct.sh #!/bin/sh export QT_QPA_PLATFORMTHEME="qt5ct" [rocketmouse@archlinux ~]$ pacman -Q qt5ct qt5ct 0.22-1
By running qt5ct I can chose the wanted font and size.
On Tue, 19 Apr 2016 00:50:02 +0200, Ralf Mardorf wrote:
On Sat, 16 Apr 2016 23:04:17 +0100 (BST), flow wrote:
Got wrong font in [snip] qupzilla only since latest upgrade.
[rocketmouse@archlinux ~]$ cat /etc/profile.d/qt5ct.sh #!/bin/sh export QT_QPA_PLATFORMTHEME="qt5ct" [rocketmouse@archlinux ~]$ pacman -Q qt5ct qt5ct 0.22-1
By running qt5ct I can chose the wanted font and size.
The regular fonts are a little bit bold and I'm mitaken, I get a very similar font, but a few letters differ, e.g. the "F" and "E".
On 04/16/2016 04:01 AM, flow wrote:
Still have yet unwanted font.
Can you use gnome-tweak-tool to change the font and font hinting? I have never tried using it on a non-GNOME desktop, so I'm not sure this helps. There are no problems on my Adwaita-themed GNOME; Raleigh is broken for me too, but it has always been ugly [1].
[1] https://blogs.gnome.org/mclasen/2014/06/13/a-new-default-theme-for-gtk/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 04/16/2016 04:01 AM, flow wrote:
Still have yet unwanted font.
Can you use gnome-tweak-tool to change the font and font hinting? I have
gnome-tweak-tool won't to run here.
never tried using it on a non-GNOME desktop, so I'm not sure this helps. There are no problems on my Adwaita-themed GNOME; Raleigh is broken for me too, but it has always been ugly [1].
- -- Have a nice day!
~~~ This PGP signature only certifies the sender and date of the message. It implies no approval from the administrators of nym.mixmin.net. Date: Sat Apr 16 22:14:17 2016 GMT From: flow@nym.mixmin.net
arch-general@lists.archlinux.org