Hi,
setting up Alpine makes small advances.
However, I can't get xfce4-terminal or roxterm to show the paths in tabs
or the window title bars. More annoying is, that gtk settings in
~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini are seemingly ignored.
In the beginning there were some strange dbus issues, but the Alpine
Wiki provided a solution. Maybe I'm missing something related to gtk
configuration, font configuration and icon theme configuration, too.
Yesterday: https://i.imgur.com/snfkRiZ.png
Today: https://i.imgur.com/KqyQKdM.png
Regards,
Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat Jun 3, 2023 at 7:19 PM CEST, Ralf Mardorf wrote:
> Hi,>> setting up Alpine makes small advances.>> However, I can't get xfce4-terminal or roxterm to show the paths in tabs> or the window title bars.
this is a shell thing, see e.g. https://forum.xfce.org/viewtopic.php?id=13948
tl;dr: the shell outputs magic the terminal displays as the title. some put pwd,
others anything, ..
busybox ash does not send anything so you get some default (number?).
> More annoying is, that gtk settings in> ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini are seemingly ignored.
they're not, those paths work. though of course some configuration is also found
in env vars, obscure gsettings, ..
arch has them documented somewhat comprehensively https://wiki.archlinux.org/title/GTK
what you're trying to do is probably just incorrect or unsupported, but there's
nothing special in packaging there (to save you some time hunting), just the
usual configuration locations.
>> In the beginning there were some strange dbus issues, but the Alpine> Wiki provided a solution. Maybe I'm missing something related to gtk> configuration, font configuration and icon theme configuration, too.>> Yesterday: https://i.imgur.com/snfkRiZ.png> Today: https://i.imgur.com/KqyQKdM.png>> Regards,> Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat, 2023-06-03 at 19:26 +0200, alice wrote:
> busybox ash does not send anything so you get some default
Thank you,
that explains it.
> > More annoying is, that gtk settings in> > ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini are seemingly ignored.> > they're not, those paths work. though of course some configuration is also found> in env vars, obscure gsettings, ..> arch has them documented somewhat comprehensively https://wiki.archlinux.org/title/GTK
I don't experience such issues with my Arch install.
On Arch Linux
• rocketmouse@archlinux ~
$ echo $XDG_CONFIG_HOME
• rocketmouse@archlinux ~
$
the variable isn't set. I'll take a look if the variable is set by my
Alpine install, if I have some time again to experiment with Alpine.
Regards,
Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat Jun 3, 2023 at 7:38 PM CEST, Ralf Mardorf wrote:
> On Sat, 2023-06-03 at 19:26 +0200, alice wrote:> > busybox ash does not send anything so you get some default>> Thank you,>> that explains it.>> > > More annoying is, that gtk settings in> > > ~/.gtkrc-2.0 and ~/.config/gtk-3.0/settings.ini are seemingly ignored.> > > > they're not, those paths work. though of course some configuration is also found> > in env vars, obscure gsettings, ..> > arch has them documented somewhat comprehensively https://wiki.archlinux.org/title/GTK>> I don't experience such issues with my Arch install.>> On Arch Linux>> • rocketmouse@archlinux ~ > $ echo $XDG_CONFIG_HOME>> • rocketmouse@archlinux ~ > $>> the variable isn't set. I'll take a look if the variable is set by my> Alpine install, if I have some time again to experiment with Alpine.
pretty much nothing requires it to be set, and just defaults to ~/.config
for a simple verification, you can strace a process and see
access("/home/you/.config/gtk-3.0/settings.ini", F_OK) = 0
this really isn't the root of the issue most likely. what options are you
setting exactly? what do you want them to do?
>> Regards,> Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
Hi,
at least one of the GTK programs, IIRC Pluma, doesn't use Papirus icons.
The icons used by Pluma are probably HighContrast icons. While I'm on
Arch Linux used to Xed [1], Pluma is installed on Arch, too. On Arch
Pluma does use the same icons as other apps (there it's Sardi-Mono-
Papirus-Colora-Havelock).
• rocketmouse@archlinux ~
$ cat /mnt/m1.alpine/home/mountainmouse/.gtkrc-2.0
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 11"
• rocketmouse@archlinux ~
$ cat /mnt/m1.alpine/home/mountainmouse/.config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 11"
• rocketmouse@archlinux ~
$ /bin/ls /mnt/m1.alpine/usr/share/themes/
Albatross Artwiz-boxed Bear2 Clearlooks Clearlooks-3.4 Clearlooks-
Olive Default Emacs Mikachu Natura Numix Onyx Onyx-Citrus
Orang Raleigh Syscrash adw-gtk3 adw-gtk3-dark
• rocketmouse@archlinux ~
$ /bin/ls /mnt/m1.alpine/usr/share/icons/
Adwaita Faenza HighContrast Papirus Papirus-Dark Papirus-Light
breeze breeze-dark ePapirus ePapirus-Dark hicolor
• rocketmouse@archlinux ~
$ /bin/ls /mnt/m1.alpine/usr/share/fonts/
100dpi 75dpi awesome cyrillic dejavu encodings font-awesome
inconsolata ipafont misc noto vollkorn
On Arch and Alpine I manually edit files, but also use helper apps.
Those apps are different:
• rocketmouse@archlinux ~
$ /bin/ls /mnt/m1.alpine/usr/bin/{obcon,lxappear}* /usr/bin/{obcon,lxappear}*
/bin/ls: cannot access '/mnt/m1.alpine/usr/bin/lxappear*': No such file or directory
/mnt/m1.alpine/usr/bin/obconf-qt /usr/bin/lxappearance /usr/bin/obconf
FWIW both Arch and Alpine are using plain openbox, no DE at all. On
Alpin I did neither manually edit Qt configs, nor did I run a helper
such as qt5ct.
On Arch Linux I'm running gtk3-nocsd,
https://github.com/ZaWertun/gtk3-nocsd .
Regards,
Ralf
[1] If I have some time, I might take a look at how to build packages
for Alpine. Among other I'm missing https://github.com/linuxmint/xed by
the Alpine repositories. It provides more or less the look and feel of
Pluma or the old (not the new) Gedit, but Xed is lightweight.
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat Jun 3, 2023 at 9:37 PM CEST, Ralf Mardorf wrote:
> Hi,>> at least one of the GTK programs, IIRC Pluma, doesn't use Papirus icons.> The icons used by Pluma are probably HighContrast icons. While I'm on> Arch Linux used to Xed [1], Pluma is installed on Arch, too. On Arch> Pluma does use the same icons as other apps (there it's Sardi-Mono-> Papirus-Colora-Havelock).
this seems to be one of those weird cases:
$ gsettings set org.gnome.desktop.interface icon-theme Papirus
appears to work for pluma, but nothing else does.
i don't know when the config file is read over the interface and how that
interacts, but that seems to work..
iirc, it does not persist across reboot (might be wrong), but it does seem to
work ok.
>> • rocketmouse@archlinux ~ > $ cat /mnt/m1.alpine/home/mountainmouse/.gtkrc-2.0> gtk-theme-name="Albatross"> gtk-icon-theme-name="Papirus"> gtk-font-name="DejaVuSans 11"> > • rocketmouse@archlinux ~ > $ cat /mnt/m1.alpine/home/mountainmouse/.config/gtk-3.0/settings.ini> [Settings]> gtk-theme-name="Albatross"> gtk-icon-theme-name="Papirus"> gtk-font-name="DejaVuSans 11"> > • rocketmouse@archlinux ~ > $ /bin/ls /mnt/m1.alpine/usr/share/themes/> Albatross Artwiz-boxed Bear2 Clearlooks Clearlooks-3.4 Clearlooks-> Olive Default Emacs Mikachu Natura Numix Onyx Onyx-Citrus > Orang Raleigh Syscrash adw-gtk3 adw-gtk3-dark> > • rocketmouse@archlinux ~ > $ /bin/ls /mnt/m1.alpine/usr/share/icons/> Adwaita Faenza HighContrast Papirus Papirus-Dark Papirus-Light > breeze breeze-dark ePapirus ePapirus-Dark hicolor> > • rocketmouse@archlinux ~ > $ /bin/ls /mnt/m1.alpine/usr/share/fonts/> 100dpi 75dpi awesome cyrillic dejavu encodings font-awesome > inconsolata ipafont misc noto vollkorn> > On Arch and Alpine I manually edit files, but also use helper apps.> Those apps are different:> > • rocketmouse@archlinux ~ > $ /bin/ls /mnt/m1.alpine/usr/bin/{obcon,lxappear}* /usr/bin/{obcon,lxappear}*> /bin/ls: cannot access '/mnt/m1.alpine/usr/bin/lxappear*': No such file or directory> /mnt/m1.alpine/usr/bin/obconf-qt /usr/bin/lxappearance /usr/bin/obconf> > FWIW both Arch and Alpine are using plain openbox, no DE at all. On> Alpin I did neither manually edit Qt configs, nor did I run a helper> such as qt5ct.>> On Arch Linux I'm running gtk3-nocsd,> https://github.com/ZaWertun/gtk3-nocsd .>> Regards,> Ralf>> [1] If I have some time, I might take a look at how to build packages> for Alpine. Among other I'm missing https://github.com/linuxmint/xed by> the Alpine repositories. It provides more or less the look and feel of> Pluma or the old (not the new) Gedit, but Xed is lightweight.
done
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat, 2023-06-03 at 22:34 +0200, alice wrote:
> this seems to be one of those weird cases:> $ gsettings set org.gnome.desktop.interface icon-theme Papirus> appears to work for pluma, but nothing else does.> > i don't know when the config file is read over the interface and how that> interacts, but that seems to work..> > iirc, it does not persist across reboot (might be wrong), but it does seem to> work ok.
Hi,
I just remembered that I once set up a workaround for Pluma under Arch,
but it's not related to icons:
• rocketmouse@archlinux ~
$ ls -hAl /pluma
drwxr-xr-x root root 4.0 KB Wed Aug 1 11:03:42 2018 snippets
• rocketmouse@archlinux ~
$ ls -hAl /pluma/snippets/
lrwxrwxrwx root root 51 B Wed Aug 1 11:03:42 2018 global.xml ⇒ /home/rocketmouse/.config/pluma/snippets/global.xml
For some reason Pluma expected a user config in the root directory. I
never sent a bug report.
In my experiences with dconf and gesetting commands, some only work
after initialization via the GUI of the related program. I wrote scripts
to setup programs using the dconf and gsetting commands. It works for
most, but not for all apps.
> > [1] If I have some time, I might take a look at how to build packages> > for Alpine. Among other I'm missing https://github.com/linuxmint/xed by> > the Alpine repositories. It provides more or less the look and feel of> > Pluma or the old (not the new) Gedit, but Xed is lightweight.> > done
Thank you!
Btw. I'm used to the GTK2 versions of
https://aur.archlinux.org/packages/fbpanel
and
https://archlinux.org/packages/extra/x86_64/lxpanel/
but I suspect building packages for those obsolete panels doesn't make
sense.
On Alpine I will take a look at tint2 before considering anything else.
Regards,
Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sat, 2023-06-03 at 22:34 +0200, alice wrote:
> this seems to be one of those weird cases:> $ gsettings set org.gnome.desktop.interface icon-theme Papirus> appears to work for pluma, but nothing else does.
Hi,
no it doesn't and it gets a lot worse...
~ $ ls -hl .config/dconf/
total 4K
-rw-r--r-- 1 mountain mountain 1.9K Jun 4 09:05 user
~ $ gsettings set org.gnome.desktop.interface icon-theme Papirus
~ $ ls -hl .config/dconf/
total 4K
-rw-r--r-- 1 mountain mountain 2.0K Jun 4 10:05 user
~ $ pluma reminder.txt
** (pluma:7425): WARNING **: 10:06:06.004: Could not load theme icon system-file-manager: Icon 'system-file-manager' not present in theme "Papirus"
** (pluma:7425): CRITICAL **: 10:06:37.753: pluma_spell_checker_language_to_key: assertion 'lang != NULL' failed
...the icons don't change. Way more annoying is that changing the font
size by the gtk configs gains absolutely nothing.
~ $ cat .gtkrc-2.0
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 11"
~ $ cat .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 11"
~ $ meld .gtkrc-2.0 .config/gtk-3.0/settings.ini 2>/dev/null
~ $ cat .gtkrc-2.0
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 22"
~ $ cat .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans 22"
JIC I logged out and in, but absolutely no fontsize changed.
~ $ echo $XDG_CONFIG_HOME
~ $ meld .gtkrc-2.0 .config/gtk-3.0/settings.ini 2>/dev/null
~ $ cat .gtkrc-2.0
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name=DejaVuSans-Bold 22"
~ $ cat .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name="Albatross"
gtk-icon-theme-name="Papirus"
gtk-font-name="DejaVuSans-Bold 22"
After logging out and in all fonts are still the same. If I chose those
fonts and sizes by app preferences, e.g. by Pluma's preferences, the
correct font and size are used. It doesn't work for for Titles, Menus,
Toolbars etc. and it was like this already before I launched obconf-qt
for the very first time.
Now for something [off-topic]:
Regarding the Alpine Wiki it's obviously better instead of using wget
[...] and apk add ./path/to/package to use tags:
~ $ cat /etc/apk/repositories
http://mirror.bahnhof.net/pub/alpinelinux/v3.18/main
#http://mirror.bahnhof.net/pub/alpinelinux/latest-stable/main
http://mirror.bahnhof.net/pub/alpinelinux/v3.18/community
#http://mirror.bahnhof.net/pub/alpinelinux/latest-stable/community
@e-test http://mirror.bahnhof.net/pub/alpinelinux/edge/testing
@e-main http://mirror.bahnhof.net/pub/alpinelinux/edge/main
@e-comm http://mirror.bahnhof.net/pub/alpinelinux/edge/community
This works for my install :).
Since xed failes to run, I'm on v3.18 and xed is from testing...
~ $ xed
Error relocating /usr/lib/xed/libxed.so: xapp_dark_mode_manager_new: symbol not found
...and because I need xnumlock and parcellite, I planned to rebuild xed
against installed dependencies from v3.18, if possible. IOW I want to
learn how to build Alpine packages.
Sometimes the Alpine Wiki seems to be ambiguous.
"# abuild-keygen -a -i" - https://wiki.alpinelinux.org/wiki/Creating_an_Alpine_package#Setup_your_system_and_account
I've done this, but it didn't add it to the abuild.conf and I don't
understand how to edit PACKAGER_PRIVKEY=<generated key>. Is it a path?
The file content? I tested this and that but nothing works, e.g.
~ $ id
uid=1000(mountainmouse) gid=1000(mountainmouse) groups=10(wheel),18(audio),23(input),27(video),28(netdev),300(abuild),1000(mountainmouse)
~ $ cd aports/testing/xed/
~/aports/testing/xed $ abuild -r
abuild-sign: ralf-mardorf@riseup.net-647c3651.rsa.pub: File not found
>>> ERROR: xed: all failed
~/aports/testing/xed $ ls -hl /etc/apk/keys/*ralf*
-rw-r--r-- 1 root root 800 Jun 4 08:59 /etc/apk/keys/ralf-mardorf@riseup.net-647c3651.rsa.pub
~/aports/testing/xed $ ls /home/mountainmouse/.abuild/abuild.conf /etc/abuild.conf
ls: /home/mountainmouse/.abuild/abuild.conf: No such file or directory
/etc/abuild.conf
~/aports/testing/xed $ cat /etc/abuild.conf
# defaults are in /usr/share/abuild/default.conf
#
# uncomment line below to enable colors
USE_COLORS=1
# uncomment line below to enable ccache support.
USE_CCACHE=1
# where downloaded files are stored
SRCDEST=/var/cache/distfiles
# uncomment line below to store built packages in other location
# The package will be stored as $REPODEST/$repo/$pkgname-$pkgver-r$pkgrel.apk
# where $repo is the name of the parent directory of $startdir.
REPODEST=$HOME/packages/
# PACKAGER and MAINTAINER are used by newapkbuild when creating new aports for
# the APKBUILD's "Contributor:" and "Maintainer:" comments, respectively.
PACKAGER="Ralf Mardorf <ralf-mardorf@riseup.net>"
#MAINTAINER="$PACKAGER"
# what to clean up after a successful build
CLEANUP="srcdir bldroot pkgdir deps"
# what to cleanup after a failed build
ERROR_CLEANUP="bldroot deps"
# https://wiki.alpinelinux.org/wiki/Abuild_and_Helpers#Setting_up_the_build_environment
#PACKAGER_PRIVKEY=<generated key> in abuild.conf
PACKAGER_PRIVKEY=ralf-mardorf@riseup.net-647c3651.rsa.pub
Regards,
Ralf
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sun, 2023-06-04 at 11:06 +0200, Ralf Mardorf wrote:
> It doesn't work for for Titles, Menus,> Toolbars etc. and it was like this already before I launched obconf-qt> for the very first time.
PS: Changes made with obconf-qt are effective. I found the related
config file (via chroot from my Arch install):
archlinux:~$ grep -i deja -A1 -B1 .config/openbox/rc.xml
<font place="ActiveWindow">
<name>DejaVu Sans</name>
<size>11</size>
--
<font place="InactiveWindow">
<name>DejaVu Sans</name>
<size>11</size>
--
<font place="MenuHeader">
<name>DejaVu Sans</name>
<size>11</size>
--
<font place="MenuItem">
<name>DejaVu Sans</name>
<size>11</size>
--
<font place="ActiveOnScreenDisplay">
<name>DejaVu Sans</name>
<size>11</size>
--
<font place="InactiveOnScreenDisplay">
<name>DejaVu Sans</name>
<size>11</size>
archlinux:~$ grep -i theme -A1 -B1 .config/openbox/rc.xml
</placement>
<theme>
<name>Numix</name>
--
</font>
</theme>
<desktops>
It doesn't affect all fonts.
IMO the ~/.gtkrc-2.0, ~/.config/gtk-3.0/settings.ini issue is still
fishy.
Re: ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
On Sun, 2023-06-04 at 11:44 +0200, Ralf Mardorf wrote:
> archlinux:~$ grep -i deja -A1 -B1 .config/openbox/rc.xml > <font place="ActiveWindow">> <name>DejaVu Sans</name>> <size>11</size>> > It doesn't affect all fonts.
PPS:
The gtk config's "DejaVuSans 22" probably needs to read
"DejaVu Sans 22"?!
I'll have to do a few tests and comparisons with Arch Linux.
I suspect that titles and menus depend on the theme mentioned by rc.xml,
but other widgets depend on the theme mentioned by the gtk config/s.
This is from Arch Linux:
• rocketmouse@archlinux ~
$ grep -i theme -A1 -B1 .config/openbox/rc.xml
</placement>
<theme>
<name>Arc-RM-Cornflower</name>
--
</font>
</theme>
<desktops>
• rocketmouse@archlinux ~
$ cat .config/gtk-3.0/settings.ini
[Settings]
gtk-theme-name=Arc-RM-Cornflower
#gtk-theme-name=Materia-light
#gtk-theme-name=Breeze-Dark
#gtk-theme-name=Adwaita
#gtk-theme-name=Adwaita-dark
#gtk-theme-name=Breeze
gtk-font-name=Cantarell 11
gtk-icon-theme-name=Sardi-Mono-Papirus-Colora-Havelock
gtk-cursor-theme-name=Paper
gtk-cursor-theme-size=0
gtk-toolbar-style=GTK_TOOLBAR_BOTH_HORIZ
gtk-toolbar-icon-size=GTK_ICON_SIZE_LARGE_TOOLBAR
gtk-button-images=1
gtk-menu-images=1
gtk-enable-event-sounds=0
gtk-enable-input-feedback-sounds=0
gtk-xft-antialias=1
gtk-xft-hinting=1
gtk-xft-hintstyle=hintfull
gtk-xft-rgba=rgb
Last month I used several themes by .config/gtk-3.0/settings.ini to
check an issue with meld's view.
[solved] ~/.gtkrc-2.0 ~/.config/gtk-3.0/settings.ini and other pitfalls
Hi,
the issue related to the unrecognised gtk configuration files
_is solved_ by installing the package _lxappearance_ .
While still not there, I get closer to the wanted look and feel:
https://i.imgur.com/BQxqK3l.png
One of my next steps will be changing...
~ $ grep inline_tag.props.draw_spaces /$(apk info -L meld | grep sourceview)
inline_tag.props.draw_spaces = True
...to False, to get rid of the confusing dots, shown by the screenshot.
The off-topic issue related to abuild isn't solved, I'll start a new
thread if it's still necessary after further reading.
Regards,
Ralf