Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Qubes wrote: Is this normal/expected behavior? As has been discussed in this thread, making changes in `/etc/skel` in a template of an existing VM does not propagate to the VM. However, if you change the VMs template to a different template it seems like `/etc/skel` is copied to `/home/user` when the VM boots, even though it is not a new VM. I don't understand the documentation in this way. I checked this now. This not the case, it was because of a test I was doing with another thread "Injecting configuration files into appVM when it's created/started for the first time". The test I was doing did something unexpected that made it appear as if `/etc/skel` was copied to a VM when the Template changes when in fact it does not. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c5a6598f-137b-db4b-a176-e0377d4a2ff5%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Qubes wrote: Vít Šesták wrote: Perhaps my search terms are just out of whack, but I have had a good look around and I cannot find a system wide location for `~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon Theme for example. It's easy to find. 1. Me: Do you know a system-wide file for ~/.config/qt5ct/qt5ct.conf? ChatGPT: Yes, the system-wide configuration file for ~/.config/qt5ct/qt5ct.conf is typically located at /etc/xdg/qt5ct/qt5ct.conf. This file contains the default settings for I tried `/etc/xdg/qt5ct/qt5ct.conf` and it didn't work. I also tried `/etc/xdg/qt5ct.conf` (just to try my luck) but it also doesn't work. I will try it again just to double check, maybe my midnight oil lamp was already running out of oil when I did try and I made a mess of it. Ok so just to provide feedback, I have tried this again. The default is in fact located at `/etc/xdg/qt5ct/qt5ct.conf`, but it is only applied if `~/.config/qt5ct/qt5ct.conf` does not exist, with caveats. In fact what happens is if `~/.config/qt5ct/qt5ct.conf` does not exist `/etc/xdg/qt5ct/qt5ct.conf` is copied to `~/.config/qt5ct/`. Which kind of solves the problem. If the file exists you can delete it and just close all of you Qt applications and open them again. With the first one that you open it will check if `~/.config/qt5ct/qt5ct.conf` exists and if not make a copy of `/etc/xdg/qt5ct/qt5ct.conf`. This still does not allow a seamless edit to `/etc/xdg/qt5ct/qt5ct.conf` (in the Template) that will just apply to all VMs, but it does make it easier. I had a look at `strings /usr/lib64/libQt5Gui.so.5.15.9|grep '^QT_'` but I don't see a variable name that indicates to me it has anything to do with the path of `qt5ct.conf`. Thank you for the suggestion I have learnt something new today. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c2330fbd-e579-4639-afbe-de396679ff9f%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Is this normal/expected behavior? As has been discussed in this thread, making changes in `/etc/skel` in a template of an existing VM does not propagate to the VM. However, if you change the VMs template to a different template it seems like `/etc/skel` is copied to `/home/user` when the VM boots, even though it is not a new VM. I don't understand the documentation in this way. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cd3a4b52-cb34-be7d-f22b-8dcb9246dff9%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
The file location may vary by your distro, at least ChatGPT tells so. Also strace might help you to check what file locations are accessed: 1. strace -o /tmp/strace.log gnome-terminal 2. grep settings.ini /tmp/strace.log You'll probably want to use a Qt app rather than gnome-terminal, but the way to look for that is the same. Regards, Vít Šesták 'v6ak' On Thursday, May 4, 2023 at 2:31:52 PM UTC+2 Qubes wrote: > > Vít Šesták wrote: > > Perhaps my search terms are just out of whack, but I have had a good > > look around and I cannot find a system wide location for > > `~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon Theme for > > example. > > > > > > It's easy to find. > > > > 1. Me: Do you know a system-wide file for ~/.config/qt5ct/qt5ct.conf? > > ChatGPT: Yes, the system-wide configuration file for > > ~/.config/qt5ct/qt5ct.conf is typically located at > > /etc/xdg/qt5ct/qt5ct.conf. This file contains the default settings for > > I tried `/etc/xdg/qt5ct/qt5ct.conf` and it didn't work. I also tried > `/etc/xdg/qt5ct.conf` (just to try my luck) but it also doesn't work. I > will try it again just to double check, maybe my midnight oil lamp was > already running out of oil when I did try and I made a mess of it. > > > the Qt5 Configuration Tool and is used as a fallback configuration file > > if no user-specific configuration is found. > > > > Note that the location of the system-wide configuration file may vary > > depending on your specific Linux distribution or operating system. You > > can use the locate or find command to search for the file on your system. > > > > 2. Verify by Google by searching "/etc/xdg/qt5ct/qt5ct.conf" (including > > quotes). It seems that this location is real. > > > > Even more frustrating I cannot > > find a list of the environment variables that I can potentially use. I > > only know of the `QT_QPA_PLATFORMTHEME=qt5ct` which I currently use and > > `QT_STYLE_OVERRIDE=` [3][4] which you can set to either `adwaita` or > > `kvantum` However there may be an environment variable one can use to > > set the path to the `qt5ct.conf`, but such a list alludes me. > > > > > > > > 1. Look where it is used: > > sudo grep -rl QT_QPA_PLATFORMTHEME /usr > > /usr/share/doc/qgnomeplatform-qt6/README.md > > /usr/share/doc/gnupg2/NEWS > > /usr/share/doc/qgnomeplatform-qt5/README.md > > /usr/lib64/libQt5Gui.so.5.15.9 > > /usr/lib64/libQt6Gui.so.6.4.3 > > > > 2. Look in the binary: > > strings /usr/lib64/libQt6Gui.so.6.4.3 | grep '^QT_' > > > > Thanks I will check this. > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5371dedc-9fd6-4fd3-b29f-f40ce44a35afn%40googlegroups.com.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Vít Šesták wrote: Perhaps my search terms are just out of whack, but I have had a good look around and I cannot find a system wide location for `~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon Theme for example. It's easy to find. 1. Me: Do you know a system-wide file for ~/.config/qt5ct/qt5ct.conf? ChatGPT: Yes, the system-wide configuration file for ~/.config/qt5ct/qt5ct.conf is typically located at /etc/xdg/qt5ct/qt5ct.conf. This file contains the default settings for I tried `/etc/xdg/qt5ct/qt5ct.conf` and it didn't work. I also tried `/etc/xdg/qt5ct.conf` (just to try my luck) but it also doesn't work. I will try it again just to double check, maybe my midnight oil lamp was already running out of oil when I did try and I made a mess of it. the Qt5 Configuration Tool and is used as a fallback configuration file if no user-specific configuration is found. Note that the location of the system-wide configuration file may vary depending on your specific Linux distribution or operating system. You can use the locate or find command to search for the file on your system. 2. Verify by Google by searching "/etc/xdg/qt5ct/qt5ct.conf" (including quotes). It seems that this location is real. Even more frustrating I cannot find a list of the environment variables that I can potentially use. I only know of the `QT_QPA_PLATFORMTHEME=qt5ct` which I currently use and `QT_STYLE_OVERRIDE=` [3][4] which you can set to either `adwaita` or `kvantum` However there may be an environment variable one can use to set the path to the `qt5ct.conf`, but such a list alludes me. 1. Look where it is used: sudo grep -rl QT_QPA_PLATFORMTHEME /usr /usr/share/doc/qgnomeplatform-qt6/README.md /usr/share/doc/gnupg2/NEWS /usr/share/doc/qgnomeplatform-qt5/README.md /usr/lib64/libQt5Gui.so.5.15.9 /usr/lib64/libQt6Gui.so.6.4.3 2. Look in the binary: strings /usr/lib64/libQt6Gui.so.6.4.3 | grep '^QT_' Thanks I will check this. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/48389e46-b8e0-bf48-bfc0-bafe439dcf05%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Perhaps my search terms are just out of whack, but I have had a good look around and I cannot find a system wide location for `~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon Theme for example. It's easy to find. 1. Me: Do you know a system-wide file for ~/.config/qt5ct/qt5ct.conf? ChatGPT: Yes, the system-wide configuration file for ~/.config/qt5ct/qt5ct.conf is typically located at /etc/xdg/qt5ct/qt5ct.conf. This file contains the default settings for the Qt5 Configuration Tool and is used as a fallback configuration file if no user-specific configuration is found. Note that the location of the system-wide configuration file may vary depending on your specific Linux distribution or operating system. You can use the locate or find command to search for the file on your system. 2. Verify by Google by searching "/etc/xdg/qt5ct/qt5ct.conf" (including quotes). It seems that this location is real. Even more frustrating I cannot find a list of the environment variables that I can potentially use. I only know of the `QT_QPA_PLATFORMTHEME=qt5ct` which I currently use and `QT_STYLE_OVERRIDE=` [3][4] which you can set to either `adwaita` or `kvantum` However there may be an environment variable one can use to set the path to the `qt5ct.conf`, but such a list alludes me. 1. Look where it is used: sudo grep -rl QT_QPA_PLATFORMTHEME /usr /usr/share/doc/qgnomeplatform-qt6/README.md /usr/share/doc/gnupg2/NEWS /usr/share/doc/qgnomeplatform-qt5/README.md /usr/lib64/libQt5Gui.so.5.15.9 /usr/lib64/libQt6Gui.so.6.4.3 2. Look in the binary: strings /usr/lib64/libQt6Gui.so.6.4.3 | grep '^QT_' Regards, Vít Šesták 'v6ak' -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8b0a4074-5a2f-4954-94d4-8bb76861e40en%40googlegroups.com.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Cristian Margine wrote: Most software has a default config location. You can search it on archwiki(qubes is using fedora, but in general the arch wiki list paths that work on all distros as location where the configuration for a program must be placed), ask chatgpt or search on google for the default config location for that program. It might be in /etc or somewhere in /usr/. Perhaps my search terms are just out of whack, but I have had a good look around and I cannot find a system wide location for `~/.config/qt5ct/qt5ct.conf` that controls the Style and Icon Theme for example. I have looked around on Archwiki [1] as well but there is no mention of a global conf file for Qt5. Qt4 on the other hand does support a global conf file [2], `/etc/xdg/Trollech.conf`, which I have tried using but Qt5 does not look at it. Even more frustrating I cannot find a list of the environment variables that I can potentially use. I only know of the `QT_QPA_PLATFORMTHEME=qt5ct` which I currently use and `QT_STYLE_OVERRIDE=` [3][4] which you can set to either `adwaita` or `kvantum` However there may be an environment variable one can use to set the path to the `qt5ct.conf`, but such a list alludes me. I also canot find a system wide location for Krusader configuration file `~/.config/krusaderrc`. From there the need arises to inject files into already running VMs. For future VMs this problem is solved with `/etc/skel` but my problem is with running VMs. [1]: https://wiki.archlinux.org/title/Qt#Configuration_of_Qt_5_applications_under_environments_other_than_KDE_Plasma [2]: https://wiki.archlinux.org/title/Qt#Styles_in_Qt_4 [3]: https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications#Adwaita [4]: https://wiki.archlinux.org/title/Uniform_look_for_Qt_and_GTK_applications#Kvantum -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/8a7a0fa1-9436-553f-6445-738835375fb9%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
On Wed, May 03, 2023 at 04:19:00PM +, Qubes wrote: > > 'unman' via qubes-users wrote: > > On Wed, May 03, 2023 at 12:53:00PM +, Qubes wrote: > > > > > Is there a sane way to update existing `*.conf` files on VMs that are > > > already running? > > > Is there a not-so-labour-intensive way to solve this problem? > > > > Use salt - it's easy to apply to existing qubes, as well as template. > > You can (if you wish) store the config file whole, or just the changes > > that you want to make, as part of the install. > > It also has the advantage of being self documenting. > > > I have looked over salt, albeit briefly, but it definitely does not look > like something that someone with no knowledge of salt can just jump in and > use. You have mentioned this a lot so perhaps the best person here to ask > is you. Can you maybe recommend a salt for 'dummies' guide? > I have some notes at https://github.com/unman/notes which take you through simple steps with many examples of using salt in Qubes. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ZFMc9rIv4VwnBPg7%40thirdeyesecurity.org.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
'unman' via qubes-users wrote: On Wed, May 03, 2023 at 12:53:00PM +, Qubes wrote: Is there a sane way to update existing `*.conf` files on VMs that are already running? Is there a not-so-labour-intensive way to solve this problem? Use salt - it's easy to apply to existing qubes, as well as template. You can (if you wish) store the config file whole, or just the changes that you want to make, as part of the install. It also has the advantage of being self documenting. I have looked over salt, albeit briefly, but it definitely does not look like something that someone with no knowledge of salt can just jump in and use. You have mentioned this a lot so perhaps the best person here to ask is you. Can you maybe recommend a salt for 'dummies' guide? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3ea4f3c0-ec14-a515-1cf2-20eef567bd50%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
On Wed, May 03, 2023 at 12:53:00PM +, Qubes wrote: > Is there a sane way to update existing `*.conf` files on VMs that are > already running? > Is there a not-so-labour-intensive way to solve this problem? Use salt - it's easy to apply to existing qubes, as well as template. You can (if you wish) store the config file whole, or just the changes that you want to make, as part of the install. It also has the advantage of being self documenting. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ZFKNmZMMJjV2eD40%40thirdeyesecurity.org.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Most software has a default config location. You can search it on archwiki(qubes is using fedora, but in general the arch wiki list paths that work on all distros as location where the configuration for a program must be placed), ask chatgpt or search on google for the default config location for that program. It might be in /etc or somewhere in /usr/. --- Original Message --- On Wednesday, May 3rd, 2023 at 3:53 PM, Qubes wrote: > > > > Rusty Bird wrote: > > > Everything in /etc/skel/ on the TemplateVM is copied to /home/user/ on > > VM creation, e.g. /etc/skel/.config/gtk-3.0/settings.ini (although for > > this specific case you could just use /etc/gtk-3.0/settings.ini which > > would also apply to existing VMs, not just newly created ones). > > > Is there a sane way to update existing `*.conf` files on VMs that are > already running? > > For example, I have installed new software in a Template that is used > by several VMs. I would like a default look and feel across all of the > VMs when I use the new software but the software stores its > configuration in `~/.config/...` > > I can put the default configuration in `/etc/skel/.config/...',which > will apply to newly created VMs, but this will not apply to already > created and running VMs. > > Is there a not-so-labour-intensive way to solve this problem? > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/0cf4e184-f257-6937-84b9-dbcf62ba74af%40ak47.co.za. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/SjdM1Aepa5AooGZdsK3xEJskfyyj6BNKHXNMAAUEij2Y24NDnNGQPsleTpYVFYm29hb-1wSCMzfXIOu00Ip4BbSQcPLYv3RvDd_iiSNeZ6k%3D%40cristiioan.me. publickey - cristiioan@cristiioan.me - 0xDAC92D89.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
Rusty Bird wrote: Everything in /etc/skel/ on the TemplateVM is copied to /home/user/ on VM creation, e.g. /etc/skel/.config/gtk-3.0/settings.ini (although for this specific case you could just use /etc/gtk-3.0/settings.ini which would also apply to existing VMs, not just newly created ones). Is there a sane way to update existing `*.conf` files on VMs that are already running? For example, I have installed new software in a Template that is used by several VMs. I would like a default look and feel across all of the VMs when I use the new software but the software stores its configuration in `~/.config/...` I can put the default configuration in `/etc/skel/.config/...',which will apply to newly created VMs, but this will not apply to already created and running VMs. Is there a not-so-labour-intensive way to solve this problem? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0cf4e184-f257-6937-84b9-dbcf62ba74af%40ak47.co.za.
Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Qubes: > I am sure I have read this somewhere here on the list or in the > [documentation](https://www.qubes-os.org/doc/) that it is possible to inject > configuration files into an appVM when it gets created. Can someone maybe > remind me how to do it? > > For example to enable a default dark theme in a VM one does the following: > > mkdir -p .config/gtk-3.0 > vi .config/gtk-3.0/settings.ini > > Then you add the following lines to settings.ini: > > [Settings] > gtk-application-prefer-dark-theme=1 > > The problem here is if you do it in the template the appVM does not inherit > ".config/gtk-3.0/settings.ini" because the appVM gets its own private > storage. It is however a pain to have to manually put it in each appVM. This > is just an example there are many other cases where this is desirable. Everything in /etc/skel/ on the TemplateVM is copied to /home/user/ on VM creation, e.g. /etc/skel/.config/gtk-3.0/settings.ini (although for this specific case you could just use /etc/gtk-3.0/settings.ini which would also apply to existing VMs, not just newly created ones). Rusty -BEGIN PGP SIGNATURE- iQKTBAEBCgB9FiEEhLWbz8YrEp/hsG0ERp149HqvKt8FAmROTJhfFIAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDg0 QjU5QkNGQzYyQjEyOUZFMUIwNkQwNDQ2OUQ3OEY0N0FBRjJBREYACgkQRp149Hqv Kt9e6RAAiExsUJl9d7xyaLd/m7gVX3HuZAVAAVkFDhTU1SU/o0uVs3rhcuMDAmqx /gftDBulJnS6pz30TUN/+C7Qd8GcE2VZ37z6tIsP+VMVVA+cUlNIi8VSsCl7+2ho 2ETt12WjHaGQ3tfhEs9G4ixt3hA7EzXL3qI8ItqE68Yel1oi77R21oAqQbFvPOgy ogAfjIQhmX30esZ9ym5oJZWprzUpPyX3SF1OtgZ5SC84yhPqy1/jOdpxvDNrni3+ ACAMYTBz34nYWS5ioQ6tLEJthFlsswoiKL3R72HRyLhs1gCnVDW/4LNJ0gjJS7jn zJ958zuRw9pnfFobYqk4359tEpEct7GEMuA/DFaiYf5gO3G3iPkuopr1Iu6p3QV9 SulyaL2a32I5cuIuqa4/ryRsF8aPMrtSQbRJFltDmnOWjh58Kf8rYwY6el2aBmMh OQGgg7OODTIS24wRX43VXq51SYRi7d/prB0P/fK9s4twijSZ8yXxbOrulco5Kdgp 2aULUnq2TDQ3ZDh0e/ONWx7Q3S3iR7QiM8W6psTsWBaHw+A7GPYQfHvabvYIyYOI Xh6oRp7PmR9cT0Ojz7QqmAOUB4b6rtjZHXFd3L8oTD+ofmZlHyBXBaFQ+Acbot7n rz49u7CIqoVDrcTc+rFcL20LhM8iSiBeoqzSkF1S7fb7TYKNn7I= =wYrE -END PGP SIGNATURE- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ZE5MmHd1obIbAHvN%40mutt.
[qubes-users] Injecting configuration files into appVM when it's created/started for the first time
I am sure I have read this somewhere here on the list or in the [documentation](https://www.qubes-os.org/doc/) that it is possible to inject configuration files into an appVM when it gets created. Can someone maybe remind me how to do it? For example to enable a default dark theme in a VM one does the following: mkdir -p .config/gtk-3.0 vi .config/gtk-3.0/settings.ini Then you add the following lines to settings.ini: [Settings] gtk-application-prefer-dark-theme=1 The problem here is if you do it in the template the appVM does not inherit ".config/gtk-3.0/settings.ini" because the appVM gets its own private storage. It is however a pain to have to manually put it in each appVM. This is just an example there are many other cases where this is desirable. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/42519b14-5963-a2a8-1fa4-680cc0af425c%40ak47.co.za.
