subject:"\[qubes\-users\]"


Qubes wrote:

Qubes wrote:

Qubes wrote:

Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0 
date and time updates as soon as my computer gets net connectivity, 
but my appVMs can take a loong time before their date and time 
also update. Is there any explanation for this and maybe a way to 
fix it?


Ok I can sync it manually in the appVM using `sudo qvm-sync-clock`. 
So the question is how can I set it to run more frequently in the appVM?


Update: When my computer wakes from sleep the appVMs never update 
their time. The only way is to manually run `sudo-qvm-sync-clock` or 
reboot the VM. Why do I see this behavior? I am sure date and time 
should sync everywhere automatically. Without the need, which looks to 
be the only solution currently, to create a small script that is 
executed at VM startup and it goes into a loop and runs 
`sudo-qvm-sync-clock` every 30 seconds.


  This is a serious problem, VMs don't sync their time on 4.2. Can 
anybody provide meaningful input?



Is there nothing I can do here?

Is it just me and my system or are you also seeing 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/a9005303-c449-b4c8-73b7-43305243ef95%40ak47.co.za.

Re: [qubes-users] qubes HCL report HP_EliteBook 845 G8

2023-05-04 Thread Boryeu Mao

Am having occasional crashing after lid-closing suspend with Rysen-powered
Dell Inspiron…  will try xfce button then lid closing.  Many thanks for the
hint.

On Thursday, May 4, 2023, haaber  wrote:

> Dear all,
>
> Update of my HCL report: suspend to memory via xfce button works fine,
> but often sys-net is dead at wake-up. No harm: a simple qvm-start
> sys-net resolves that quickly, in particular, sys-firewall takes it
> easy.  Only lid-closing is more delicate: it hangs/crashes often -- so I
> decided close lid *after*  "suspend to memory" via xfce button only.
>
> best, Bernhard
>
> --
> 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/ms
> gid/qubes-users/073859e0-3338-2ff5-5994-c6b796d01a27%40web.de.
>

-- 
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/CAOBBCnasPOh21tmUztd_g72BfMUdJMTgv2M3%2B1XYqDXOr0%2BpQw%40mail.gmail.com.

Re: [qubes-users] qubes HCL report HP_EliteBook 845 G8

2023-05-04 Thread Sven Semmler


updated, might take a few minutes until visible

/Sven

--
https://keys.openpgp.org/vks/v1/by-fingerprint/DA5975C9ABC40C833B2F620B2A632C537D744BC7

--
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/80a9884e-89a7-bb5f-d84a-29f5538b309c%40SvenSemmler.org.

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.

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.

Re: [qubes-users] Colourful prompt

Qubes wrote:

'unman' via qubes-users wrote:

On Thu, May 04, 2023 at 05:01:38AM -0700, Andrew David Wong wrote:

On 5/3/23 4:02 AM, Qubes wrote:
I have noticed on Fedora, the cli prompt itself is not colourful
although the rest of the output is. Is there a way to get the prompt
itself in colour as well? The prompt on Debian is in colour, it
makes it easier to find things when the prompt is in colour aswell.

Since this is not a Qubes-specific question, you might have better
luck searching the web for how to do this in Fedora (or Linux in
general) or asking in a Fedora (or general Linux) venue.

I wonder if this *is* Qubes specific, as it is stated that the Debian
prompt is in color. (Implicit, I think, is the suggestion that the color
matches the window decorations.)
OP - is that what you see? That the prompt is consistent with the window
decoration set by Qubes?

No the colour of the prompt does not follow the window decoration, I was
wondering if this isn't maybe a problem only on Fedora on Qubes and not
Fedora in general. I don't have a Fedora standalone I can check on. I
just found it odd that the prompt on Debian would be in colour (Green,
and it is real easy to find in between a lot of other output) and on
Fedora it is the same colour as the text you type. But as I was
re-reading my reply here I just had another look over and I just
discovered that the prompt on some of the Fedora VMs is in colour, also
a bright green, and some of them are default text colour. So in essense
it doesn't have anything to do with Qubes. I am a little confused though
because I can swear some of the VMs that I previously check where the
prompt was the default text colour now has a colourful prompt. (head
scratch head scratch)

It must be because of a dependency that gets installed along the way
because booting the vanilla Fedora-37 template it does not have a
colourful prompt. I don't install anything specific for this myself.
Glad we cleared that up :-)

Re: [qubes-users] The NovaCustom NV41 Series laptop is Qubes-certified!


Leo28C wrote:
On Wed, May 3, 2023 at 5:12 AM Andrew David Wong <mailto:a...@qubes-os.org>> wrote:


nor can we control whether physical hardware is modified (whether
maliciously or otherwise) *en route* to the user.


Actually you could:

1) Laminate product with `warranty void if removed` stickers of various 
brands and types
2) Send PGP-signed high-res photo of sticker placement to buyer before 
shipping
3) Buyer receives product and compares sticker placement to the photo to 
verify integrity



This is a great idea, you should contact Nova and propose it to them.

--
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/c28ae291-97e6-a918-68de-e6e7f6dc5e44%40ak47.co.za.

Re: [qubes-users] Colourful prompt


'unman' via qubes-users wrote:

On Thu, May 04, 2023 at 05:01:38AM -0700, Andrew David Wong wrote:

On 5/3/23 4:02 AM, Qubes wrote:

I have noticed on Fedora, the cli prompt itself is not colourful although the 
rest of the output is. Is there a way to get the prompt itself in colour as 
well? The prompt on Debian is in colour, it makes it easier to find things when 
the prompt is in colour aswell.



Since this is not a Qubes-specific question, you might have better luck 
searching the web for how to do this in Fedora (or Linux in general) or asking 
in a Fedora (or general Linux) venue.


I wonder if this *is* Qubes specific, as it is stated that the Debian
prompt is in color. (Implicit, I think, is the suggestion that the color
matches the window decorations.)
OP - is that what you see? That the prompt is consistent with the window
decoration set by Qubes?



No the colour of the prompt does not follow the window decoration, I was 
wondering if this isn't maybe a problem only on Fedora on Qubes and not 
Fedora in general. I don't have a Fedora standalone I can check on. I 
just found it odd that the prompt on Debian would be in colour (Green, 
and it is real easy to find in between a lot of other output) and on 
Fedora it is the same colour as the text you type. But as I was 
re-reading my reply here I just had another look over and I just 
discovered that the prompt on some of the Fedora VMs is in colour, also 
a bright green, and some of them are default text colour. So in essense 
it doesn't have anything to do with Qubes. I am a little confused though 
because I can swear some of the VMs that I previously check where the 
prompt was the default text colour now has a colourful prompt. (head 
scratch head scratch)


I do see this in .bashrc on Debian and there is nothing of it in .bashrc 
on Fedora. There is in fact a lot of stuff in .bashrc on Debian that is 
not there on Fedora.


.bashrc

===truncated===

# set a fancy prompt (non-color, unless we know we "want" color)
case "$TERM" in
xterm-color|*-256color) color_prompt=yes;;
esac

# uncomment for a colored prompt, if the terminal has the capability; turned
# off by default to not distract the user: the focus in a terminal window
# should be on the output of commands, not on the prompt
#force_color_prompt=yes

if [ -n "$force_color_prompt" ]; then
if [ -x /usr/bin/tput ] && tput setaf 1 >&/dev/null; then
# We have color support; assume it's compliant with Ecma-48
# (ISO/IEC-6429). (Lack of such support is extremely rare, and such
# a case would tend to support setf rather than setaf.)
color_prompt=yes
else
color_prompt=
fi
fi

===truncated===

I have copied it over to .bashrc on Fedora and uncommented 
`force_color_prompt=yes` but it makes no difference.


--
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/62120076-9be6-1d62-4831-a3f638d3414f%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

2023-05-04 Thread Vít Šesták

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

It's easy to find.

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.

Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time

2023-05-04 Thread Vít Šesták

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.

2. Look in the binary:
strings /usr/lib64/libQt6Gui.so.6.4.3 | grep '^QT_'

Regards,
Vít Šesták 'v6ak'

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

Re: [qubes-users] Colourful prompt

2023-05-04 Thread 'unman' via qubes-users

On Thu, May 04, 2023 at 05:01:38AM -0700, Andrew David Wong wrote:
> On 5/3/23 4:02 AM, Qubes wrote:
> > I have noticed on Fedora, the cli prompt itself is not colourful although 
> > the rest of the output is. Is there a way to get the prompt itself in 
> > colour as well? The prompt on Debian is in colour, it makes it easier to 
> > find things when the prompt is in colour aswell.
> > 
> 
> Since this is not a Qubes-specific question, you might have better luck 
> searching the web for how to do this in Fedora (or Linux in general) or 
> asking in a Fedora (or general Linux) venue.
> 
I wonder if this *is* Qubes specific, as it is stated that the Debian
prompt is in color. (Implicit, I think, is the suggestion that the color
matches the window decorations.)
OP - is that what you see? That the prompt is consistent with the window
decoration set by 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/ZFOgEprkEoVo25%2Bv%40thirdeyesecurity.org.

Re: [qubes-users] Colourful prompt

2023-05-04 Thread Andrew David Wong

On 5/3/23 4:02 AM, Qubes wrote:
> I have noticed on Fedora, the cli prompt itself is not colourful although the 
> rest of the output is. Is there a way to get the prompt itself in colour as 
> well? The prompt on Debian is in colour, it makes it easier to find things 
> when the prompt is in colour aswell.
> 

Since this is not a Qubes-specific question, you might have better luck 
searching the web for how to do this in Fedora (or Linux in general) or asking 
in a Fedora (or general Linux) venue.

-- 
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/3100e550-911f-c078-72a8-e075512009e9%40qubes-os.org.

Re: [qubes-users] The NovaCustom NV41 Series laptop is Qubes-certified!

2023-05-04 Thread Andrew David Wong

On 5/3/23 8:30 AM, Leo28C wrote:
> On Wed, May 3, 2023 at 5:12 AM Andrew David Wong  wrote:
> 
>> nor can we control whether physical hardware is modified (whether
>> maliciously or otherwise) *en route* to the user.
>>
> 
> Actually you could:
> 
> 1) Laminate product with `warranty void if removed` stickers of various
> brands and types
> 2) Send PGP-signed high-res photo of sticker placement to buyer before
> shipping
> 3) Buyer receives product and compares sticker placement to the photo to
> verify integrity
> 

We (the Qubes OS Project) can't do that, because we never take possession of 
inventory. When you purchase a Qubes-certified computer from a vendor, you are 
purchasing directly from that vendor.

However, you could offer your suggestion to the vendors who sell 
Qubes-certified hardware.

-- 
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/b69230c2-621f-6650-f104-4f2e1fe242dd%40qubes-os.org.

Re: [qubes-users] ThinkPad W530

2023-05-04 Thread Simon Newton

Sounds like you have not enabled VT-d (intel virtualisation) in the bios.
That CPU does support VT-d, so it just needs to be enabled in the bios for
qubesOS to work properly.


S

On Thu, 4 May 2023 at 10:40, T. I. N. Comp-E  wrote:

> I hope this finds you well... I have a thinkpad W530. I was able to
> upgrade it to upgrade the ram to 16 Gigs I have met all the
> requirements and specs(I7 3740QM)... it still say my pc is not
> supported what else do i need to do... Ive tried many combination on
> the bios I dont know how to unlock the advanced tab, I dont understand
> what im doing wrong... please help
>
> --
> 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/CAAMOyp0zzDXGh%3DNMqAgXLAdcpO5v9KkxrJN9bmLh4h1%2BgEd1oA%40mail.gmail.com
> <https://groups.google.com/d/msgid/qubes-users/CAAMOyp0zzDXGh%3DNMqAgXLAdcpO5v9KkxrJN9bmLh4h1%2BgEd1oA%40mail.gmail.com?utm_medium=email_source=footer>
> .
>


-- 
Kind Regards,

Simon Newton

E: simon.new...@gmail.com

-- 
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/CADLktjC7OOm0fCnnzS%3D6f3U6w4R%2BZE_nQN7K1opUvEsuUXZ9Gw%40mail.gmail.com.

[qubes-users] ThinkPad W530

2023-05-04 Thread T. I. N. Comp-E

I hope this finds you well... I have a thinkpad W530. I was able to upgrade
it to upgrade the ram to 16 Gigs I have met all the requirements and
specs(I7 3740QM)... it still say my pc is not supported what else do i
need to do... Ive tried many combination on the bios I dont know how to
unlock the advanced tab, I dont understand what im doing wrong... please
help

-- 
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/CAAMOyp0zzDXGh%3DNMqAgXLAdcpO5v9KkxrJN9bmLh4h1%2BgEd1oA%40mail.gmail.com.

Re: [qubes-users] qubes HCL report HP_EliteBook 845 G8

2023-05-04 Thread haaber


Dear all,

Update of my HCL report: suspend to memory via xfce button works fine,
but often sys-net is dead at wake-up. No harm: a simple qvm-start
sys-net resolves that quickly, in particular, sys-firewall takes it
easy.  Only lid-closing is more delicate: it hangs/crashes often -- so I
decided close lid *after*  "suspend to memory" via xfce button only.

best, Bernhard

--
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/073859e0-3338-2ff5-5994-c6b796d01a27%40web.de.
---
layout:
  'hcl'
type:
  'notebook'
hvm:
  'yes'
iommu:
  'yes'
slat:
  'yes'
tpm:
  'unknown'
remap:
  'yes'
brand: |
  HP
model: |
  HP EliteBook 845 G8 Notebook PC
bios: |
  T82 Ver. 01.10.01
cpu: |
  AMD Ryzen 7 PRO 5850U with Radeon Graphics
cpu-short: |
  FIXME
chipset: |
  Advanced Micro Devices, Inc. [AMD] Renoir Root Complex [1022:1630]
chipset-short: |
  FIXME
gpu: |
  Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev d1) (prog-if 
00 [VGA controller])
gpu-short: |
  FIXME
network: |
  Realtek Semiconductor Co., Ltd. RTL8822CE 802.11ac PCIe Wireless Network 
Adapter
memory: |
  32065
scsi: |

usb: |
  3
versions:

- works:
'FIXME:yes|no|partial'
  qubes: |
R4.1
  xen: |
4.14.5
  kernel: |
5.15.94-1
  remark: |
FIXME
  credit: |
FIXAUTHOR
  link: |
FIXLINK

---

Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time

2023-05-03 Thread 'unman' via qubes-users

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] The NovaCustom NV41 Series laptop is Qubes-certified!

2023-05-03 Thread Leo28C

On Wed, May 3, 2023 at 5:12 AM Andrew David Wong  wrote:

> nor can we control whether physical hardware is modified (whether
> maliciously or otherwise) *en route* to the user.
>

Actually you could:

1) Laminate product with `warranty void if removed` stickers of various
brands and types
2) Send PGP-signed high-res photo of sticker placement to buyer before
shipping
3) Buyer receives product and compares sticker placement to the photo to
verify integrity

-- 
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/CAALhvVYsei7LV4qJyoyQDYpvvrxfLbi65iDBo0U7nh6%3Dq0PmGw%40mail.gmail.com.

Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time

2023-05-03 Thread 'unman' via qubes-users

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

2023-05-03 Thread Cristian Margine

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] Time and date of appVM


Qubes wrote:

Qubes wrote:

Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0 
date and time updates as soon as my computer gets net connectivity, 
but my appVMs can take a loong time before their date and time 
also update. Is there any explanation for this and maybe a way to fix 
it?


Ok I can sync it manually in the appVM using `sudo qvm-sync-clock`. So 
the question is how can I set it to run more frequently in the appVM?


Update: When my computer wakes from sleep the appVMs never update their 
time. The only way is to manually run `sudo-qvm-sync-clock` or reboot 
the VM. Why do I see this behavior? I am sure date and time should sync 
everywhere automatically. Without the need, which looks to be the only 
solution currently, to create a small script that is executed at VM 
startup and it goes into a loop and runs `sudo-qvm-sync-clock` every 30 
seconds.


 This is a serious problem, VMs don't sync their time on 4.2. Can 
anybody provide meaningful input?


--
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/651672d7-f28c-c96c-f243-dbc9e139a40f%40ak47.co.za.

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] qubes HCL report

2023-05-03 Thread Sven Semmler


Thank you Bernhard for your HCL report, which is 
[online](https://www.qubes-os.org/hcl/#hewlett-packard_elitebook-845-g8_ryzen-7-pro-5850u_integrated-graphics-rx-vega-8-5000_bernhard-haaber_r4-1)
 now!

/Sven

--
https://keys.openpgp.org/vks/v1/by-fingerprint/DA5975C9ABC40C833B2F620B2A632C537D744BC7

--
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/ba4b6254-d05c-e91f-87ef-9008fe1335ce%40SvenSemmler.org.

[qubes-users] Colourful prompt

I have noticed on Fedora, the cli prompt itself is not colourful 
although the rest of the output is. Is there a way to get the prompt 
itself in colour as well? The prompt on Debian is in colour, it makes it 
easier to find things when the prompt is in colour aswell.


--
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/9dec4ccb-d633-4776-5cbe-617cc716121d%40ak47.co.za.

[qubes-users] The NovaCustom NV41 Series laptop is Qubes-certified!

2023-05-03 Thread Andrew David Wong

Dear Qubes Community,

It is our pleasure to announce that the [NovaCustom NV41 
Series](https://configurelaptop.eu/nv41-series/) laptop has become the fifth 
[Qubes-certified computer](https://www.qubes-os.org/doc/certified-hardware/) 
for Qubes 4.X!

## About the NovaCustom NV41 Series

The [NV41 Series](https://configurelaptop.eu/nv41-series/) is a 14-inch laptop 
from [NovaCustom](https://configurelaptop.eu/), a European vendor known for 
their highly customizable, Linux-friendly laptops. This 12th Generation Intel 
Core (Alder Lake) laptop comes with Dasharo coreboot open-source firmware, 
USB-C charging, the latest Intel Xe graphics, and up to 64 GB of memory.

## Qubes-certified configurations

The following configuration options are certified for Qubes OS 4.X:

Processor:
- Intel Core i5-1240P processor
- Intel Core i7-1260P processor

Memory (Dual Channel):
- 2 x 16 GB Kingston DDR4 SODIMM 3200 MHz (32 GB total)
- 1 x 32 GB Kingston DDR4 SODIMM 3200 MHz (32 GB total)
- 2 x 32 GB Kingston DDR4 SODIMM 3200 MHz (64 GB total)

M.2 storage chip:
- Samsung 980 SSD (all capacities)
- Samsung 980 Pro SSD (all capacities)

Wi-Fi and Bluetooth:
- Intel AX-200/201 Wi-Fi module 2976 Mbps, 802.11ax/Wi-Fi 6 + Bluetooth 5.2
- Killer (Intel) Wireless-AX 1675x M.2 Wi-Fi module 802.11ax/Wi-Fi 6E + 
Bluetooth 5.3
- Blob-free: Qualcomm Atheros QCNFA222 Wi-Fi 802.11a/b/g/n + Bluetooth 4.0
- No Wi-Fi/Bluetooth chip

### Notes on Wi-Fi and Bluetooth options

- When viewed in a Linux environment with `lspci`, the "Killer (Intel) 
Wireless-AX 1675x M.2 Wi-Fi module 802.11ax/Wi-Fi 6E + Bluetooth 5.3" device 
displays the model number "AX210." However, according to its [Intel Ark 
entry](https://ark.intel.com/content/www/us/en/ark/products/211485/intel-killer-wifi-6e-ax1675-xw.html)
 (in the "Product Brief" file), they are actually the same Wi-Fi module.

- Similarly, when viewed in a Linux environment with `lspci`, the "Blob-free: 
Qualcomm Atheros QCNFA222 Wi-Fi 802.11a/b/g/n + Bluetooth 4.0" device displays 
the model number "AR9462," which seems to be just the Wi-Fi chip model number, 
whereas "QCNFA222" seems to be the model number of the whole device (which 
include Bluetooth). Meanwhile, the Bluetooth device presents itself as "IMC 
Networks Device 3487."

- The term "blob-free" is used in different ways. In practice, being 
"blob-free" generally does *not* mean that the device does not use any 
closed-source firmware "blobs." Rather, it means that the device comes with 
firmware *preinstalled* so that it does not have to be loaded from the 
operating system. In theory, the preinstalled firmware could be open-source, 
but as far as we know, that is not the case with this particular Atheros 
Wi-Fi/Bluetooth module. (Qualcomm has published firmware source code in the 
past, but only for other device models, as far as we are aware.) Meanwhile, the 
Free Software Foundation (FSF) 
[considers](https://www.gnu.org/philosophy/free-hardware-designs.en.html#boundary)
 unmodifiable preinstalled firmware to be part of the hardware, hence they 
regard such hardware as "blob-free" from a software perspective. While common 
usage of the term "blob-free" often follows the FSF's interpretation, it is 
worthwhile for Qubes users who are concerned about closed-source firmware to 
understand the nuance.

## Special note regarding the need for `kernel-latest`

Beginning with Qubes OS 4.1.2, the Qubes installer includes the `kernel-latest` 
package and allows users to select this kernel option from the GRUB menu when 
booting the installer. At the time of this announcement, `kernel-latest` is 
*required* for the NovaCustom NV41 Series to function properly. Therefore, all 
potential purchasers and users of this model should be aware that they will 
have to select a non-default option (`Install Qubes OS RX using kernel-latest`) 
from the GRUB menu when booting the installer. However, since Linux 6.1 has 
officially been promoted to being a long-term support (LTS) kernel, it will 
become the default kernel at some point, which means that the need for this 
non-default selection is only temporary.

## What is Qubes-certified hardware?

[Qubes-certified hardware](https://www.qubes-os.org/doc/certified-hardware/) is 
hardware that has been certified by the Qubes developers as compatible with a 
specific [major release](https://www.qubes-os.org/doc/version-scheme/) of Qubes 
OS. All Qubes-certified devices are available for purchase with Qubes OS 
preinstalled. Beginning with Qubes 4.0, in order to achieve certification, the 
hardware must satisfy a rigorous set of [requirements], and the vendor must 
commit to offering customers the very same configuration (same motherboard, 
same screen, same BIOS version, same Wi-Fi module, etc.) for at least one year.

[Qubes-certified 
computers](https://www.qubes-os.org/doc/certifie

Re: [qubes-users] Template for X?

2023-05-02 Thread Sandy Harris

Steve Coleman  wrote:
>
> On Sat, Apr 29, 2023, 4:53 AM Sandy Harris  wrote:
>>
>> Is there a template to make a qube that just runs as an X terminal?
>
> If you turn on Qubes debugging for any AppVM it will start within a terminal 
> window with a command line interface. If that AppVM has X installed you 
> should still be able to start other apps that will appear in their own window.
>
> Is this what you are looking for?

It does not sound like it. I'll have two machines, one running Qubes &
two monitors, the other headless. What I want is a qube that runs X
with all its client processes on the headless one. I know I can do
that with a full linux in that qube, but wonder how much that can be
stripped down in an X server. I do not need that qube to do anything
except handle display for the headless machine.

-- 
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/CACXcFmneeANShO4TU1jWnc%2BLyD0K6TKJFTS%3DJdE%3D2p1iX5qsFA%40mail.gmail.com.

Re: [qubes-users] Time and date of appVM

2023-05-02 Thread Qubes


Qubes wrote:

Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0 date 
and time updates as soon as my computer gets net connectivity, but my 
appVMs can take a loong time before their date and time also 
update. Is there any explanation for this and maybe a way to fix it?


Ok I can sync it manually in the appVM using `sudo qvm-sync-clock`. So 
the question is how can I set it to run more frequently in the appVM?


Update: When my computer wakes from sleep the appVMs never update their 
time. The only way is to manually run `sudo-qvm-sync-clock` or reboot 
the VM. Why do I see this behavior? I am sure date and time should sync 
everywhere automatically. Without the need, which looks to be the only 
solution currently, to create a small script that is executed at VM 
startup and it goes into a loop and runs `sudo-qvm-sync-clock` every 30 
seconds.


--
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/4e59b2d6-c25f-0943-0645-b5861fe2f376%40ak47.co.za.

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

2023-05-02 Thread Qubes

Qubes wrote:

Vít Šesták wrote:
I sometimes need something similar, but I prefer a slightly different
approach. I prefer the config files to be in the TemplateVM, so that I
can easily update them for all the VMs. There is no general solution
for all the cases, but you often can find a global file. For example:

* /etc/xdg/xfce4/terminal/terminalrc for XFCE4 Terminal settings

Thank you for the nice tip. Rather using a global config file is in fact
more like I want it. I will definitely use the xfce4-terminal settings
file global location. What is the best way to find other configuration
files' global location. Is it just a matter of searching or is there a
more sophisticated approach?

For example I would also like to use global settings locations for,

1. global dark theme, currently I have it configured in
`~/.config/gtk-3.0/settings.ini`

The global path for the dark theme is `/usr/share/gtk-3.0/settings.ini`.

2. is there one for `~./.bashrc`
3. `~/.config/dconf/user` (the config file that gets created by
executing `gsettings set org.gnome.desktop.interface color-scheme
prefer-dark. A necessary setting with newer Gtk applications, like the
latest evince, not following the dark theme setting in
`~/.config/gtk-3.0/settings.ini` anymore. Some software is changing over
to Handy StyleManager for theming.

4. Is there on for Krusader, currently it is in `~/.config/krusaderrc`

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time


Cristian Margine wrote:
That happens because bash will replace an alias only if it is is the 
first word. You can set the alias
alias sudo='sudo '. Because it has a space at the end it will also check 
the parameter('l' in your situation) if it is an alias.



 Thank you kindly that works a treat.

--
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/f5352c2c-bff5-d147-231c-8b529d5f27cb%40ak47.co.za.

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

2023-05-01 Thread Cristian Margine

That happens because bash will replace an alias only if it is is the first 
word. You can set the alias
alias sudo='sudo '. Because it has a space at the end it will also check the 
parameter('l' in your situation) if it is an alias.
\ Original Message 
On May 1, 2023, 11:03 PM, Qubes < qubes...@ak47.co.za> wrote:

>
> > Vít Šesták wrote: > I have several ways: > > a. Google > b. ChatGPT, e.g. 
> > “Can I configure XFCE Terminal for all users?” (real > example copied from 
> > my history) > c. Try to find a file with the same name (maybe without 
> > initial dot) in > /usr, /etc, etc. Something like this: sudo find / -xdev 
> > -name zshrc > I have a question that I was hoping someone can shed some 
> > light on. I put an alias, now in /etc/bashrc to make it global, to alias 
> > l='ls -Ahl' This works everywhere but it does not work with sudo, 
> > \[user@fedora ~\]$ sudo l sudo: l: command not found 
> > \[user@fedora-37-m-default ~\]$ Why is that, can I make it comply? -- 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/0d57fe08-5556-cf45-7ab1-6fdc376281ef%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/fqO_IiJxnkI_1dPgRdYog0VY5gjcAtIaqbCBRWzykKL1rEB6nWhlm9nVUOFihwAT-SpshwjSouETjvdWJ1t2_ACOyeWdZBBh8HTb6L1jeXg%3D%40cristiioan.me.


publickey - EmailAddress(s=cristiioan@cristiioan.me) - 0xDAC92D89.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time


Vít Šesták wrote:
I have several ways:

a. Google
b. ChatGPT, e.g. “Can I configure XFCE Terminal for all users?” (real 
example copied from my history)
c. Try to find a file with the same name (maybe without initial dot) in 
/usr, /etc, etc. Something like this: sudo find / -xdev -name zshrc




I have a question that I was hoping someone can shed some light on. I 
put an alias, now in /etc/bashrc to make it global, to


alias l='ls -Ahl'

This works everywhere but it does not work with sudo,

[user@fedora ~]$ sudo l
sudo: l: command not found
[user@fedora-37-m-default ~]$

Why is that, can I make it comply?

--
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/0d57fe08-5556-cf45-7ab1-6fdc376281ef%40ak47.co.za.

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

2023-05-01 Thread Vít Šesták

I have several ways:

a. Google
b. ChatGPT, e.g. “Can I configure XFCE Terminal for all users?” (real 
example copied from my history)
c. Try to find a file with the same name (maybe without initial dot) in 
/usr, /etc, etc. Something like this: sudo find / -xdev -name zshrc

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/744da41a-f7a2-4764-9342-0bc82ae77c7dn%40googlegroups.com.

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

Qubes wrote:

* /etc/xdg/xfce4/terminal/terminalrc for XFCE4 Terminal settings

For example I would also like to use global settings locations for,

1. global dark theme, currently I have it configured in
`~/.config/gtk-3.0/settings.ini`

2. is there one for `~./.bashrc`

I see in my ~/.bashrc it gives the global location

# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc

3. `~/.config/dconf/user` (the config file that gets created by
executing `gsettings set org.gnome.desktop.interface color-scheme
prefer-dark. A necessary setting with newer Gtk applications, like the
latest evince, not following the dark theme setting in
`~/.config/gtk-3.0/settings.ini` anymore. Some software is changing over
to Handy StyleManager for theming.

4. Is there on for Krusader, currently it is in `~/.config/krusaderrc`

Re: [qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

Vít Šesták wrote:
I sometimes need something similar, but I prefer a slightly different
approach. I prefer the config files to be in the TemplateVM, so that I
can easily update them for all the VMs. There is no general solution for
all the cases, but you often can find a global file. For example:

* /etc/xdg/xfce4/terminal/terminalrc for XFCE4 Terminal settings

For example I would also like to use global settings locations for,

1. global dark theme, currently I have it configured in
`~/.config/gtk-3.0/settings.ini`

4. Is there on for Krusader, currently it is in `~/.config/krusaderrc`

[qubes-users] Re: Injecting configuration files into appVM when it's created/started for the first time

2023-05-01 Thread Vít Šesták

I sometimes need something similar, but I prefer a slightly different 
approach. I prefer the config files to be in the TemplateVM, so that I can 
easily update them for all the VMs. There is no general solution for all 
the cases, but you often can find a global file. For example:
* /etc/ssh/ssh_known_hosts
* /etc/ssh/ssh_config.d/something.conf allows you to configure SSH client, 
e.g., RevokedHostKeys.
* /etc/xdg/xfce4/terminal/terminalrc for XFCE4 Terminal settings
* /usr/share/geany/geany.conf
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/cdf49d9c-8427-434a-a579-5cc1277c8af1n%40googlegroups.com.

Re: [qubes-users] Injecting configuration files into appVM when it's created/started for the first time

2023-04-30 Thread Rusty Bird

-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.

Re: [qubes-users] Time and date of appVM

2023-04-29 Thread Qubes


Qubes wrote:
I have noticed than when my computer wakes up from sleep the dom0 date 
and time updates as soon as my computer gets net connectivity, but my 
appVMs can take a loong time before their date and time also update. 
Is there any explanation for this and maybe a way to fix it?


Ok I can sync it manually in the appVM using `sudo qvm-sync-clock`. So 
the question is how can I set it to run more frequently in the appVM?


--
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/165f432e-0f49-7676-3028-6de0fa2565e7%40ak47.co.za.

[qubes-users] Time and date of appVM

2023-04-29 Thread Qubes

I have noticed than when my computer wakes up from sleep the dom0 date 
and time updates as soon as my computer gets net connectivity, but my 
appVMs can take a loong time before their date and time also update. 
Is there any explanation for this and maybe a way to fix it?


--
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/8e6f8181-5fcd-69e1-4ba9-32f2a650add1%40ak47.co.za.

[qubes-users] Injecting configuration files into appVM when it's created/started for the first time

2023-04-29 Thread 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.


--
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.

Re: [qubes-users] Template for X?

2023-04-29 Thread Steve Coleman

On Sat, Apr 29, 2023, 4:53 AM Sandy Harris  wrote:

> Is there a template to make a qube that just runs as an X terminal?
>

If you turn on Qubes debugging for any AppVM it will start within a
terminal window with a command line interface. If that AppVM has X
installed you should still be able to start other apps that will appear in
their own window.

Is this what you are looking for?

-- 
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/CAJ5FDngZpbkSRrY-at8S7082xbfFAqX_ML3XGQ%2B7mAg9dEyYWA%40mail.gmail.com.

Re: [qubes-users] Updating via a wireguard connection

2023-04-29 Thread 'unman' via qubes-users

On Fri, Apr 28, 2023 at 11:58:55AM -0700, Jeremy Hansen wrote:
> I would like to configure Qubes to do its updates via a connection to a 
> wireguard service I have set up.
> 
> I understand how to set up a wireguard enabled template and a qubes based on 
> that template following this:
> 
> https://github.com/hkbakke/qubes-wireguard
> 
> which works great, but I would like to force package updates to also use a 
> wireguard connection. I???m not quite sure what to alter to do this. Any help 
> would be much appreciated.
> 
> -jeremy
> 

The default is for updates to run in sys-net.
You need to change this by changing the policy - look in 
`/etc/qubes/policy.d/90-default.policy` 
for the `qubes.UpdatesProxy` lines, and then create a new policy in 
 `/etc/qubes/policy.d/30-user.policy` like this:
`qubes.UpdatesProxy  *  @type:TemplateVM  @default  allow target=QUBE`
where QUBE is the name of the qube you want to use.

If you use Whonix you will need to copy the relevant Whonix lines also.

Set the netvm for QUBE to be your wireguard qube.

-- 
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/ZEzwfyp8Whgzsfcl%40thirdeyesecurity.org.

Re: [qubes-users] Template for X?

2023-04-29 Thread 'unman' via qubes-users

On Sat, Apr 29, 2023 at 04:53:10PM +0800, Sandy Harris wrote:
[quote]
Is there a template to make a qube that just runs as an X terminal?
[/quote]
Have you tried a minimal template?

-- 
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/ZEzuT6GWcmBSk%2BCi%40thirdeyesecurity.org.

[qubes-users] Template for X?

2023-04-29 Thread Sandy Harris

Is there a template to make a qube that just runs as an X terminal?

-- 
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/CACXcFmnT8GbJbz7_OTdeBq6thKGY58dDmM5U8K8GOBOHDu7MnA%40mail.gmail.com.

[qubes-users] Updating via a wireguard connection

2023-04-28 Thread Jeremy Hansen

I would like to configure Qubes to do its updates via a connection to a 
wireguard service I have set up.

I understand how to set up a wireguard enabled template and a qubes based on 
that template following this:

https://github.com/hkbakke/qubes-wireguard

which works great, but I would like to force package updates to also use a 
wireguard connection. I’m not quite sure what to alter to do this. Any help 
would be much appreciated.

-jeremy

-- 
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/99eb6d69-9242-4077-b317-5a8793d189be%40Canary.

Re: [qubes-users] Attaching USB devices by name instead of devid (from the command line)

2023-04-28 Thread vicviq

On Wed, 2023-04-26 at 13:45 +0200, Gabriel Philippe wrote:
> Hi,
> 
> I use an USB scanner which is sometimes unplugged and might be
> plugged
> to another USB port. I would like it to be permanently attached to
> the
> "scanner" vm (I don't want to reattach it after reboot).
> 
> However the documented way uses the devid, ex. sys-usb:2.5. If I
> attach it permanently to a vm (qvm-usb attach -p scanner sys-
> usb:2.5),
> then unplug the scanner and plug an USB flash drive to same port, the
> flash drive gets attached automatically to my "scanner" vm (which I
> don't want).
> 
> Is there a way to attach a specific device to a vm, and not an USB
> port?
> 
> I tried with qvm-block, but couldn't find my scanner label in /dev/
> 
> Currently, my best solution is to have a launcher running this:
> qvm-usb attach scanner "$(qvm-usb|grep Canon|cut -f 1 -d ' ')"
> 

Currently I have a similar script:
qvm-usb attach --verbose sys-net ${qvm-usb l | awk
'/.*Realtek_USB_10_100_1000_LAN.*/ {print $1}')

> -- 
> Gabriel
> 

-- 
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/6d14abeaa2452c8cc20c2c95d79f6d6e5723d3d4.camel%40gmail.com.

Re: [qubes-users] dbus-x11 missing from Fedora-37

To withdraw my mistake, in order to install dbus x11, as an user:
1. sudo dnf install apt
2. add the Debian Buster package repositories to /etc/apt folder via root
3. After you are doing so, sudo apt update for the packages
4. sudo apt install [package]

Apr 27, 2023 08:34:53 Qubes :

> When i attempted to launch a root gnome-terminal on the default Fedora-37 
> template i received a "dbus-launch" error.
> 
> "
> [user@fedora-37-clone-1 ~]$ sudo gnome-terminal
> # gdk_atom_intern: assertion 'atom_name != NULL' failed
> # gdk_atom_intern: assertion 'atom_name != NULL' failed
> # Error constructing proxy for 
> org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child 
> process “dbus-launch” (No such file or directory)
> [user@fedora-37-clone-1 ~]$
> "
> 
> I know I can "sudo COMMAND" or I can become root "sudo su", but it my case I 
> need to launch a root gnome-terminal.
> 
> Installing dbus-launch solves the issue, "sudo dnf install dbus-x11". I have 
> checked the default Debian-11 template has dbus-x11 installed.
> 
> 
> -- 
> 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/3b77bcf0-bb9d-4cb4-0513-6ec5d4fd6a90%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/7be72d21-0f81-4faa-8933-b447406e84db%40gmail.com.

Re: [qubes-users] dbus-x11 missing from Fedora-37

Additionally, the fc37 minimal does not have GUI terminal because of its nature 
of execution from formal installation of minimal setup. As a result, fc37 
minimal only provides CLI based programs.

Apr 27, 2023 08:46:45 Howard Chen :

> Correct:
> 
> After you went to the terminal, for Debian: execute either sudo or root:
> 
> 1. dnf update
> 
> 2. dnf install dbus-x11
> 
> 
> !! Notes: must be executed in xterm, not gnome terminal. !!
> 
> Apr 27, 2023 08:41:32 Qubes :
> 
>> 
>>>  Original Message 
>>> From: Howard Chen 
>>> Sent: Thursday, April 27, 2023 at 17:39
>>> To: Qubes
>>> Cc: qubes-users@googlegroups.com
>>> Subject: [qubes-users] dbus-x11 missing from Fedora-37
>>> Just execute 'gnome-terminal' or 'terminal' without using sudo or root.
>>> 
>> 
>> You clearly have not read what i have said.
>> 
>> -- 
>> 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/296a94f3-5d54-8b36-0536-b9e17f05d8d6%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/8670d29b-f1b4-4ee8-b1f8-3fe9235ca97f%40gmail.com.

Re: [qubes-users] dbus-x11 missing from Fedora-37

Correct:

After you went to the terminal, for Debian: execute either sudo or root:

1. dnf update

2. dnf install dbus-x11


!! Notes: must be executed in xterm, not gnome terminal. !!

Apr 27, 2023 08:41:32 Qubes :

> 
>>  Original Message 
>> From: Howard Chen 
>> Sent: Thursday, April 27, 2023 at 17:39
>> To: Qubes
>> Cc: qubes-users@googlegroups.com
>> Subject: [qubes-users] dbus-x11 missing from Fedora-37
>> Just execute 'gnome-terminal' or 'terminal' without using sudo or root.
>> 
> 
> You clearly have not read what i have said.
> 
> -- 
> 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/296a94f3-5d54-8b36-0536-b9e17f05d8d6%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/cb87bfc2-fec5-43ef-a730-187e7fdd1c87%40gmail.com.

Re: [qubes-users] dbus-x11 missing from Fedora-37





 Original Message 
From: Howard Chen 
Sent: Thursday, April 27, 2023 at 17:39
To: Qubes
Cc: qubes-users@googlegroups.com
Subject: [qubes-users] dbus-x11 missing from Fedora-37

Just execute 'gnome-terminal' or 'terminal' without using sudo or root.



You clearly have not read what i have said.

--
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/296a94f3-5d54-8b36-0536-b9e17f05d8d6%40ak47.co.za.

Re: [qubes-users] dbus-x11 missing from Fedora-37

Just execute 'gnome-terminal' or 'terminal' without using sudo or root.

Apr 27, 2023 08:34:53 Qubes :

> When i attempted to launch a root gnome-terminal on the default Fedora-37 
> template i received a "dbus-launch" error.
> 
> "
> [user@fedora-37-clone-1 ~]$ sudo gnome-terminal
> # gdk_atom_intern: assertion 'atom_name != NULL' failed
> # gdk_atom_intern: assertion 'atom_name != NULL' failed
> # Error constructing proxy for 
> org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child 
> process “dbus-launch” (No such file or directory)
> [user@fedora-37-clone-1 ~]$
> "
> 
> I know I can "sudo COMMAND" or I can become root "sudo su", but it my case I 
> need to launch a root gnome-terminal.
> 
> Installing dbus-launch solves the issue, "sudo dnf install dbus-x11". I have 
> checked the default Debian-11 template has dbus-x11 installed.
> 
> 
> -- 
> 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/3b77bcf0-bb9d-4cb4-0513-6ec5d4fd6a90%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/53a19007-e5f8-431b-ae80-a1c08f1d57eb%40gmail.com.

[qubes-users] dbus-x11 missing from Fedora-37

When i attempted to launch a root gnome-terminal on the default 
Fedora-37 template i received a "dbus-launch" error.


"
[user@fedora-37-clone-1 ~]$ sudo gnome-terminal
# gdk_atom_intern: assertion 'atom_name != NULL' failed
# gdk_atom_intern: assertion 'atom_name != NULL' failed
# Error constructing proxy for 
org.gnome.Terminal:/org/gnome/Terminal/Factory0: Failed to execute child 
process “dbus-launch” (No such file or directory)

[user@fedora-37-clone-1 ~]$
"

I know I can "sudo COMMAND" or I can become root "sudo su", but it my 
case I need to launch a root gnome-terminal.


Installing dbus-launch solves the issue, "sudo dnf install dbus-x11". I 
have checked the default Debian-11 template has dbus-x11 installed.



--
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/3b77bcf0-bb9d-4cb4-0513-6ec5d4fd6a90%40ak47.co.za.

Re: [qubes-users] Re: Help with a small test


Leslie Smith wrote:

 > As soon as you add evince using the Add button and you
 > click on Apply you should see the KSysoca error logged on your terminal
 > window.

Yes.  I see

10:24:04.570-warning kf.service.services unknown@0 # KServiceFactory: 
unexpected object entry in KSycoca database (type= 305 )
10:24:04.571-warning kf.service.services unknown@0 # KServiceFactory: 
unexpected object entry in KSycoca database (type= 305 )
kf.service.services: KServiceFactory: unexpected object entry in KSycoca 
database (type= 305 )
kf.service.services: KServiceFactory: unexpected object entry in KSycoca 
database (type= 305 )
kf.service.services: KServiceFactory: unexpected object entry in KSycoca 
database (type= 305 )
kf.service.services: KServiceFactory: unexpected object entry in KSycoca 
database (type= 305 )


 > Can you also confirm, when executing "kbuildsycoca5 --noincremental" on
 > cli do you also get
 > "applications.menu"  not found in  ("/etc/xdg/menus")    ?



To fix this really annoying issue, create a applications.menu symbolic 
link in /etc/xdg/menus/ (in the template).


sudo ln -s /etc/xdg/menus/kf5-applications.menu 
/etc/xdg/menus/applications.menu


--
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/50b3a2c4-9a06-11f7-1e1d-8664a1d7b4d7%40ak47.co.za.

Re: [qubes-users] ""applications.menu" not found in ("/etc/xdg/menus")"