Setting same gtk/openbox theme in both 64 bit native and 32 bit chroot environment
up vote
2
down vote
favorite
I'm running Arch Linux and have setup a 32bit chroot environment inside a 64bit native install per their wiki instructions.
I've installed the Zukitwo and Zukitwo-Openbox themes via the Arch Linux AUR, which install to /usr/share/themes/Zukitwo.
I'm setting my theme via obconf (for openbox) and lxappearance (for gtk apps). For some reason, when setting gtk theme with lxappearance in the 64bit native environment, my 32bit chroot apps default to the Raleigh theme (looks like Win 3.1). If I enter the chroot and use lxappearance to set the same theme (which I've installed in the chroot as well), the 64bit native environment applications switch to Raleigh theme.
Since this should just be making changes to, as far as I know, ~/.config/gtk-3.0/settings.ini, why might my theme not be consistent between the two environments?
Here is the script that starts the 32bit chroot at boot (removed stop case to minimize post length):
#!/bin/bash
dirs=(/dev /dev/pts /dev/shm /tmp /home)
case $1 in
start)
for d in "${dirs[@]}"; do
mount -o bind $d /opt/arch32/$d
done
mount -t proc none /opt/arch32/proc
mount -t sysfs none /opt/arch32/sys
;;
stop) [... removed ...]
esac
/home gets mounted, so the two should just be bound in the chroot and they're sharing the same home directory, right? (Using diff on settings.ini in ~/.config/gtk-3.0/settings.ini and /opt/arch32/home/username/.config/gtk-3.0/settings.ini reveals no differences.)
arch-linux openbox theme gtk3
add a comment |
up vote
2
down vote
favorite
I'm running Arch Linux and have setup a 32bit chroot environment inside a 64bit native install per their wiki instructions.
I've installed the Zukitwo and Zukitwo-Openbox themes via the Arch Linux AUR, which install to /usr/share/themes/Zukitwo.
I'm setting my theme via obconf (for openbox) and lxappearance (for gtk apps). For some reason, when setting gtk theme with lxappearance in the 64bit native environment, my 32bit chroot apps default to the Raleigh theme (looks like Win 3.1). If I enter the chroot and use lxappearance to set the same theme (which I've installed in the chroot as well), the 64bit native environment applications switch to Raleigh theme.
Since this should just be making changes to, as far as I know, ~/.config/gtk-3.0/settings.ini, why might my theme not be consistent between the two environments?
Here is the script that starts the 32bit chroot at boot (removed stop case to minimize post length):
#!/bin/bash
dirs=(/dev /dev/pts /dev/shm /tmp /home)
case $1 in
start)
for d in "${dirs[@]}"; do
mount -o bind $d /opt/arch32/$d
done
mount -t proc none /opt/arch32/proc
mount -t sysfs none /opt/arch32/sys
;;
stop) [... removed ...]
esac
/home gets mounted, so the two should just be bound in the chroot and they're sharing the same home directory, right? (Using diff on settings.ini in ~/.config/gtk-3.0/settings.ini and /opt/arch32/home/username/.config/gtk-3.0/settings.ini reveals no differences.)
arch-linux openbox theme gtk3
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in~/should work just fine as the chroot will see the same theme in/usr/share/themes. Silly, silly, silly.
– Hendy
May 20 '13 at 21:35
add a comment |
up vote
2
down vote
favorite
up vote
2
down vote
favorite
I'm running Arch Linux and have setup a 32bit chroot environment inside a 64bit native install per their wiki instructions.
I've installed the Zukitwo and Zukitwo-Openbox themes via the Arch Linux AUR, which install to /usr/share/themes/Zukitwo.
I'm setting my theme via obconf (for openbox) and lxappearance (for gtk apps). For some reason, when setting gtk theme with lxappearance in the 64bit native environment, my 32bit chroot apps default to the Raleigh theme (looks like Win 3.1). If I enter the chroot and use lxappearance to set the same theme (which I've installed in the chroot as well), the 64bit native environment applications switch to Raleigh theme.
Since this should just be making changes to, as far as I know, ~/.config/gtk-3.0/settings.ini, why might my theme not be consistent between the two environments?
Here is the script that starts the 32bit chroot at boot (removed stop case to minimize post length):
#!/bin/bash
dirs=(/dev /dev/pts /dev/shm /tmp /home)
case $1 in
start)
for d in "${dirs[@]}"; do
mount -o bind $d /opt/arch32/$d
done
mount -t proc none /opt/arch32/proc
mount -t sysfs none /opt/arch32/sys
;;
stop) [... removed ...]
esac
/home gets mounted, so the two should just be bound in the chroot and they're sharing the same home directory, right? (Using diff on settings.ini in ~/.config/gtk-3.0/settings.ini and /opt/arch32/home/username/.config/gtk-3.0/settings.ini reveals no differences.)
arch-linux openbox theme gtk3
I'm running Arch Linux and have setup a 32bit chroot environment inside a 64bit native install per their wiki instructions.
I've installed the Zukitwo and Zukitwo-Openbox themes via the Arch Linux AUR, which install to /usr/share/themes/Zukitwo.
I'm setting my theme via obconf (for openbox) and lxappearance (for gtk apps). For some reason, when setting gtk theme with lxappearance in the 64bit native environment, my 32bit chroot apps default to the Raleigh theme (looks like Win 3.1). If I enter the chroot and use lxappearance to set the same theme (which I've installed in the chroot as well), the 64bit native environment applications switch to Raleigh theme.
Since this should just be making changes to, as far as I know, ~/.config/gtk-3.0/settings.ini, why might my theme not be consistent between the two environments?
Here is the script that starts the 32bit chroot at boot (removed stop case to minimize post length):
#!/bin/bash
dirs=(/dev /dev/pts /dev/shm /tmp /home)
case $1 in
start)
for d in "${dirs[@]}"; do
mount -o bind $d /opt/arch32/$d
done
mount -t proc none /opt/arch32/proc
mount -t sysfs none /opt/arch32/sys
;;
stop) [... removed ...]
esac
/home gets mounted, so the two should just be bound in the chroot and they're sharing the same home directory, right? (Using diff on settings.ini in ~/.config/gtk-3.0/settings.ini and /opt/arch32/home/username/.config/gtk-3.0/settings.ini reveals no differences.)
arch-linux openbox theme gtk3
arch-linux openbox theme gtk3
edited Nov 26 at 0:52
Rui F Ribeiro
38.3k1475127
38.3k1475127
asked May 6 '13 at 17:10
Hendy
19115
19115
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in~/should work just fine as the chroot will see the same theme in/usr/share/themes. Silly, silly, silly.
– Hendy
May 20 '13 at 21:35
add a comment |
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in~/should work just fine as the chroot will see the same theme in/usr/share/themes. Silly, silly, silly.
– Hendy
May 20 '13 at 21:35
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to
/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in ~/ should work just fine as the chroot will see the same theme in /usr/share/themes. Silly, silly, silly.– Hendy
May 20 '13 at 21:35
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to
/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in ~/ should work just fine as the chroot will see the same theme in /usr/share/themes. Silly, silly, silly.– Hendy
May 20 '13 at 21:35
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f74891%2fsetting-same-gtk-openbox-theme-in-both-64-bit-native-and-32-bit-chroot-environme%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Commenting to bump... please let me know if you have any further questions as I'd really love to get this resolved and will provide any additional information required!
– Hendy
May 20 '13 at 21:21
Looks like I can't answer my own question as I don't have enough rep on this site yet. Bottom line is I'm an idiot and didn't have exactly the same themes installed. I had a different Zukitwo/Zukitwo-ob theme installed in the chroot despite swearing that wasn't the case. Easiest way may be to just install to 64bit env and then copy to
/path/to/chroot/usr/share/themes/. Then, as I thought, the .config, residing in~/should work just fine as the chroot will see the same theme in/usr/share/themes. Silly, silly, silly.– Hendy
May 20 '13 at 21:35