[qubes-users] HCL Report 2023 Lenovo T480s
Remarks: sys-usb does not boot unless all external USBs are unplugged. (Poosible bug on 4.2-RC3) -- 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/3d92b6a2-6b87-41c1-882f-9fc4958b61fan%40googlegroups.com. Qubes-HCL-LENOVO-20L70028US-20230910-180450.yml Description: application/yaml
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
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.
Re: [qubes-users] Re: Creating separate sys-usb and sys-net after installation
https://forum.qubes-os.org/t/disposable-vms-names-can-the-launcher-know-the-name/12312/5 https://forum.qubes-os.org/t/poor-mans-pre-loaded-dispvm-for-faster-start/13799 On Sunday, September 25, 2022 at 5:40:44 PM UTC-7 Howard Chen wrote: > Can you send me the photos with "[what photo is that] (photo address)"? > On Friday, September 23, 2022 at 4:08:06 AM UTC-7 Lasse Kliemann wrote: > >> I tried to follow what I think is the official documentation, so I >> started with: >> >> sudo qubesctl state.sls qvm.usb-keyboard >> >> I ran into the same error as described here: >> >> https://forum.qubes-os.org/t/error-creating-sys-usb/7281 >> >> Then I followed the solution given there, essentially: >> >> sudo qubesctl state.highstate >> sudo qubesctl top.disable qvm.sys-net-as-usbvm pillar=True >> >> The latter ended with a long Python error, essentially saying: >> "ValueError: list.remove(x): x not in list". But after this, another try >> of the first command (sudo qubesctl state.sls qvm.usb-keyboard) >> succeeded. >> >> I had my USB controller persistently attached to sys-net, which I needed >> to detach before sys-net and the new sys-usb would run in parallel. >> >> On top of /etc/qubes-rpc/policy/qubes.InputKeyboard, the following line >> had been added automatically: >> >> sys-usb dom0 allow,user=root >> >> I deleted everything else in the file, except the final "$anyvm $anyvm >> deny". >> >> sys-usb is already disposable after all of this. >> >> So I think it is done now. >> >> "Howard Chen (HowardPlayzOfAdmin Gaming)" writes: >> >> > I think the best way to make disp sys-usb for the command with the >> > following: >> > >> >> sudo qubesctl state.sls qvm.sys-usb >> >> qvm-prefs sys-usb disposable_template enable >> >> qvm-prefs sys-usb tags add usb-dvm >> > >> > then in /etc/qubes-rpc/policy/qubes.InputKeyboard of dom0: >> > >> >> @tag:usb-dvm dom0 allow,user=root,default_target=dom0 >> > >> > on top of: >> > >> >> $anyvm $anyvm deny >> > >> > >> > Does it works? >> > On Monday, September 19, 2022 at 10:06:09 AM UTC-7 Lasse Kliemann wrote: >> > >> >> Greetings, upon installation a few weeks ago, I chose to create a >> single >> >> VM for USB and networking, which is called sys-net. This was in order >> to >> >> support USB network devices. The latter is no longer necessary, since >> >> the last kernel update introduced support for my internal WLAN adapter >> >> (Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz in a Thinkpad >> P14s). >> >> >> >> Now I would like to have sys-usb *and* sys-net, and also make sys-usb >> >> disposable. Will the following work? >> >> >> >> a) sudo qubesctl state.sls qvm.usb-keyboard (I use USB keyboard.) >> >> b) follow >> >> >> https://www.qubes-os.org/doc/disposable-customization/#create-the-sys-usb-disposable >> >> >> >> Thanks! >> > -- 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/af8caa21-5ed6-41dc-b3b6-baaab9ae5bd0n%40googlegroups.com.
Re: [qubes-users] Re: Creating separate sys-usb and sys-net after installation
Can you send me the photos with "[what photo is that] (photo address)"? On Friday, September 23, 2022 at 4:08:06 AM UTC-7 Lasse Kliemann wrote: > I tried to follow what I think is the official documentation, so I > started with: > > sudo qubesctl state.sls qvm.usb-keyboard > > I ran into the same error as described here: > > https://forum.qubes-os.org/t/error-creating-sys-usb/7281 > > Then I followed the solution given there, essentially: > > sudo qubesctl state.highstate > sudo qubesctl top.disable qvm.sys-net-as-usbvm pillar=True > > The latter ended with a long Python error, essentially saying: > "ValueError: list.remove(x): x not in list". But after this, another try > of the first command (sudo qubesctl state.sls qvm.usb-keyboard) > succeeded. > > I had my USB controller persistently attached to sys-net, which I needed > to detach before sys-net and the new sys-usb would run in parallel. > > On top of /etc/qubes-rpc/policy/qubes.InputKeyboard, the following line > had been added automatically: > > sys-usb dom0 allow,user=root > > I deleted everything else in the file, except the final "$anyvm $anyvm > deny". > > sys-usb is already disposable after all of this. > > So I think it is done now. > > "Howard Chen (HowardPlayzOfAdmin Gaming)" writes: > > > I think the best way to make disp sys-usb for the command with the > > following: > > > >> sudo qubesctl state.sls qvm.sys-usb > >> qvm-prefs sys-usb disposable_template enable > >> qvm-prefs sys-usb tags add usb-dvm > > > > then in /etc/qubes-rpc/policy/qubes.InputKeyboard of dom0: > > > >> @tag:usb-dvm dom0 allow,user=root,default_target=dom0 > > > > on top of: > > > >> $anyvm $anyvm deny > > > > > > Does it works? > > On Monday, September 19, 2022 at 10:06:09 AM UTC-7 Lasse Kliemann wrote: > > > >> Greetings, upon installation a few weeks ago, I chose to create a single > >> VM for USB and networking, which is called sys-net. This was in order to > >> support USB network devices. The latter is no longer necessary, since > >> the last kernel update introduced support for my internal WLAN adapter > >> (Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz in a Thinkpad P14s). > >> > >> Now I would like to have sys-usb *and* sys-net, and also make sys-usb > >> disposable. Will the following work? > >> > >> a) sudo qubesctl state.sls qvm.usb-keyboard (I use USB keyboard.) > >> b) follow > >> > https://www.qubes-os.org/doc/disposable-customization/#create-the-sys-usb-disposable > >> > >> Thanks! > -- 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/a7a7a273-0120-4994-895c-307ada9c7a8en%40googlegroups.com.
[qubes-users] Re: Creating separate sys-usb and sys-net after installation
I think the best way to make disp sys-usb for the command with the following: > sudo qubesctl state.sls qvm.sys-usb > qvm-prefs sys-usb disposable_template enable > qvm-prefs sys-usb tags add usb-dvm then in /etc/qubes-rpc/policy/qubes.InputKeyboard of dom0: > @tag:usb-dvm dom0 allow,user=root,default_target=dom0 on top of: > $anyvm $anyvm deny Does it works? On Monday, September 19, 2022 at 10:06:09 AM UTC-7 Lasse Kliemann wrote: > Greetings, upon installation a few weeks ago, I chose to create a single > VM for USB and networking, which is called sys-net. This was in order to > support USB network devices. The latter is no longer necessary, since > the last kernel update introduced support for my internal WLAN adapter > (Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz in a Thinkpad P14s). > > Now I would like to have sys-usb *and* sys-net, and also make sys-usb > disposable. Will the following work? > > a) sudo qubesctl state.sls qvm.usb-keyboard (I use USB keyboard.) > b) follow > https://www.qubes-os.org/doc/disposable-customization/#create-the-sys-usb-disposable > > Thanks! > > -- > Kind Regards / MfG > Dr. Lasse Kliemann > Westring 269, 24116 Kiel, Germany > E-Mail: la...@lassekliemann.de > Telegram / Wire: @lassekliemann > Signal / Phone: +49 162 66 88 468 > > Work Address: > Department of Mathematics > Kiel University > *Heinrich-Hecht-Platz 6*, 24118 Kiel, Germany > E-Mail: l.kli...@math.uni-kiel.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/e7d3b9b0-eb47-488c-9b77-3284789b75c3n%40googlegroups.com.
[qubes-users] Re: Problems with Timesynchronization
Did you check any system errors during the update? On Saturday, July 30, 2022 at 9:34:26 PM UTC-7 viktor@gmail.com wrote: > Hello Community, > > No advice / feedback at all ? > > Viktor Ransmayr schrieb am Samstag, 23. Juli 2022 um 22:05:39 UTC+2: > >> Hello community, >> >> I do have issues with the timesychronization of VMs in my Qubes OS 4.1.1 >> system. >> >> I was reading the information provided in [1] - and - verified that >> 'sys-net' is my clock VM. >> >> However I was not able to resolve my issues ... >> >> Here are the logs: >> >> >> >> [vr@dom0 ~]$ qubes-prefs clockvm >> sys-net >> [vr@dom0 ~]$ >> >> >> >> >> >> [user@sys-net ~]$ >> [user@sys-net ~]$ timedatectl >>Local time: Sat 2022-07-23 19:54:36 CEST >>Universal time: Sat 2022-07-23 17:54:36 UTC >> RTC time: Sat 2022-07-23 17:54:36 >> Time zone: Europe/Berlin (CEST, +0200) >> System clock synchronized: no >> NTP service: inactive >> RTC in local TZ: no >> [user@sys-net ~]$ >> >> >> >> >> >> [user@sys-net ~]$ >> [user@sys-net ~]$ systemctl restart systemd-timesyncd >> [user@sys-net ~]$ >> [user@sys-net ~]$ >> [user@sys-net ~]$ systemctl status systemd-timesyncd >> ○ systemd-timesyncd.service - Network Time Synchronization >> Loaded: loaded >> (/usr/lib/systemd/system/systemd-timesyncd.service; enabled> >> Drop-In: /usr/lib/systemd/system/systemd-timesyncd.service.d >> └─30_qubes.conf >> Active: inactive (dead) >> Condition: start condition failed at Sat 2022-07-23 20:06:48 CEST; >> 14s ago >> └─ ConditionPathExists=/var/run/qubes-service/clocksync >> was not met >>Docs: man:systemd-timesyncd.service(8) >> lines 1-8/8 (END) >> >> [user@sys-net ~]$ >> >> >> >> >> >> [user@sys-net ~]$ >> [user@sys-net ~]$ cd /var/run/qubes-service >> [user@sys-net qubes-service]$ ls >> network-manager qubes-network qubes-updates-proxy >> qubes-firewall qubes-update-check >> [user@sys-net qubes-service]$ >> >> >> >> Do you have any advice on how to continue from here - or - what else to >> check? >> > > Can you please comment on how it is possible, that > "ConditionPathExists=/var/run/qubes-service/clocksync was not met" - and - > ideally, how to resolve that issue. > > With kind regards, > > Viktor > > -- 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/99367f6d-9f30-4602-b650-55a72d5d8aacn%40googlegroups.com.
[qubes-users] Re: Problem upgrading to 4.1.1. - computer freezes
You are in the current version of Qubes. You don't need to upgrade to another fedora version as it is in 32. This might be Intel ME thing to crash your PC. A full complete reinstallation is NOT required for your PC as you need to try many times in order to work. The logs that output is well-normal at this point on because of older components needs time to recognize and train overtime. However, it will cause your PC to slow down. Are you sure that the Intel ME in your PC turned on? On Saturday, July 30, 2022 at 11:47:58 AM UTC-7 Votan wrote: > Dear all, > > I was running on Qubes OS 4.1 with kernel 5.10.112 > > After updating with the Qubes Update Tool, my computer did not reboot > anymore - it froze at the point when the password for the system needs to > be entered. I still have the previous version, so I can still boot into the > system with version 4.1. > > As a second step I tried to update via command line in dom0 as suggested > here (qubes-os.org/doc/upgrade/4.1): > > > sudo qubes-dom0-update -y qubes-dist-upgrade > > Yet I get as error message: No match found for argument: qubes-dist-upgrade > > > Any idea how to debug this? When I boot into the old version, I will not > learn from the logs. I am stuck. > > > Do I need a complete re-install? > > Hardware: > > Dell XPS 15 > > Intel Core i7-11800H > > 64GB RAM > > > Yours > > Votan > -- 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/6ef6c758-51e5-420b-bd09-d7841d1341abn%40googlegroups.com.
[qubes-users] Re: Wiki
https://alternativeto.net/software/dokuwiki/?license=opensource On Friday, July 29, 2022 at 8:23:00 AM UTC-7 Qubes wrote: > Slightly off topic, but can anybody recommend good wiki software that > plays well with Qubes VMs? > > I am asking because i am having lots of issues setting up Dokuwiki, > perhaps there is a better one that can be recommended. > -- 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/633858ba-4dc2-4487-83b3-5456c1ef686en%40googlegroups.com.
Re: [qubes-users] qvm-firewall command error
Thanks On Friday, July 29, 2022 at 5:26:58 AM UTC-7 unman wrote: > On Wed, Jul 27, 2022 at 03:59:03PM -0700, Howard Chen wrote: > > Currently, I am configuring my NetworkIT qube firewall with the > > qvm-firewall command in dom0 terminal. However, when I entered this, it > > showed this following error: > > > > [Howard@dom0 ~]$ qvm-firewall NetworkIT add dsthost 10.137.0.5 > > > > You havent given a valid rule: parameters are wrong and no action given. > Look at the manpage and qvm-firewall --help. > > qvm-firewall NetworkIT add accept 10.137.0.5 > OR > qvm-firewall NetworkIT add accept match dsthost=10.137.0.5/32 > -- 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/bffdeb92-807a-44fc-a10d-4a407a9f7695n%40googlegroups.com.
[qubes-users] qvm-firewall command error
Currently, I am configuring my NetworkIT qube firewall with the qvm-firewall command in dom0 terminal. However, when I entered this, it showed this following error: [Howard@dom0 ~]$ qvm-firewall NetworkIT add dsthost 10.137.0.5 Traceback (most recent call last): File "/usr/bin/qvm-firewall", line 5, in sys.exit(main()) File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_firewall.py", line 198, in main args = parser.parse_args(args, app=app) File "/usr/lib/python3.8/site-packages/qubesadmin/tools/__init__.py", line 385, in parse_args namespace = super().parse_args(*args, **kwargs) File "/usr/lib64/python3.8/argparse.py", line 1768, in parse_args args, argv = self.parse_known_args(args, namespace) File "/usr/lib64/python3.8/argparse.py", line 1800, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib64/python3.8/argparse.py", line 2009, in _parse_known_args stop_index = consume_positionals(start_index) File "/usr/lib64/python3.8/argparse.py", line 1965, in consume_positionals take_action(action, args) File "/usr/lib64/python3.8/argparse.py", line 1874, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib64/python3.8/argparse.py", line 1159, in __call__ subnamespace, arg_strings = parser.parse_known_args(arg_strings, None) File "/usr/lib64/python3.8/argparse.py", line 1800, in parse_known_args namespace, args = self._parse_known_args(args, namespace) File "/usr/lib64/python3.8/argparse.py", line 2009, in _parse_known_args stop_index = consume_positionals(start_index) File "/usr/lib64/python3.8/argparse.py", line 1965, in consume_positionals take_action(action, args) File "/usr/lib64/python3.8/argparse.py", line 1874, in take_action action(self, namespace, argument_values, option_string) File "/usr/lib/python3.8/site-packages/qubesadmin/tools/qvm_firewall.py", line 78, in __call__ rule = qubesadmin.firewall.Rule(None, **kwargs) File "/usr/lib/python3.8/site-packages/qubesadmin/firewall.py", line 280, in __init__ setattr(self, rule_opt, value) File "/usr/lib/python3.8/site-packages/qubesadmin/firewall.py", line 297, in action value = Action(value) File "/usr/lib/python3.8/site-packages/qubesadmin/firewall.py", line 62, in __init__ raise ValueError(value) ValueError: dsthost Can someone figure out what's going on with the code? -- 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/b1d98803-b12f-465b-b933-1fd2b1bcb0f2n%40googlegroups.com.
Re: [qubes-users] Re: dvm considerably slower on R4.1
It might be the speed in which to generate a new random number for this disposableVM and taking the file for a long time due to the size of that one file. On Thursday, July 21, 2022 at 2:13:37 PM UTC-7 Qubes wrote: > Howard Chen wrote: > > The problem lies within your computer processing speed and the numbers of > > qubes you has opened and active in one minute; This will significantly > > increases the opening time. As a result, it doubles the time of opening > and > > activating the qubes to be online. > > I didn't spell that out down to the letter but to make matters worse > when i tested the creation time of the dvm on 4.0 the system was in fact > far more busy compared to my test on 4.1. on 4.1 only the bare minimum > was booted, sys-net, sys-firewall, sys-usb, sys-whonix, and that is it. > On any regular day there are about 18 VMs running at any given time. So > definitely the measured time was not influenced by how busy, or lack of, > my system was. > > > On Thursday, July 21, 2022 at 2:02:12 PM UTC-7 Qubes wrote: > > > >> Howard Chen wrote: > >>> I have the similar as yours, but the time of one of my qubes cannot be > >> open > >>> because of light VM error that I got, which is error 135. The time > >> doubling > >>> effect is just to place for the computer took way too long on some > >>> occasional reasons to go for it. Anyways, it's just the distro issue > from > >>> Debian. > >> > >> How can it be a distro problem from Debian? Or Fedora? The same version > >> of either on either 4.0 or 4.1 should be the same. Or not? > >> > >>> On Thursday, July 21, 2022 at 1:53:56 PM UTC-7 Qubes wrote: > >>> > >>>> Has the 4.1 as well as 4.1.1, because I did test on both, release > added > >>>> additional overhead to the creation of a dvm? > >>>> > >>>> I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes > >>>> almost, in the region of 0.5 - 0.75 seconds almost, **double** the > time > >>>> for a new dvm to be ready for usage, 18 seconds vs 36 (both rounded > for > >>>> convenience). > >>>> > >>>> That is quite a hefty difference. Is there any explanation for this > >>>> behavior? > >>>> > >>> > >> > >> > > > > -- 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/aa7bd87c-8c49-4ef1-94c2-3e41dc05cfd4n%40googlegroups.com.
Re: [qubes-users] Re: dvm considerably slower on R4.1
The problem lies within your computer processing speed and the numbers of qubes you has opened and active in one minute; This will significantly increases the opening time. As a result, it doubles the time of opening and activating the qubes to be online. On Thursday, July 21, 2022 at 2:02:12 PM UTC-7 Qubes wrote: > Howard Chen wrote: > > I have the similar as yours, but the time of one of my qubes cannot be > open > > because of light VM error that I got, which is error 135. The time > doubling > > effect is just to place for the computer took way too long on some > > occasional reasons to go for it. Anyways, it's just the distro issue from > > Debian. > > How can it be a distro problem from Debian? Or Fedora? The same version > of either on either 4.0 or 4.1 should be the same. Or not? > > > On Thursday, July 21, 2022 at 1:53:56 PM UTC-7 Qubes wrote: > > > >> Has the 4.1 as well as 4.1.1, because I did test on both, release added > >> additional overhead to the creation of a dvm? > >> > >> I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes > >> almost, in the region of 0.5 - 0.75 seconds almost, **double** the time > >> for a new dvm to be ready for usage, 18 seconds vs 36 (both rounded for > >> convenience). > >> > >> That is quite a hefty difference. Is there any explanation for this > >> behavior? > >> > > > > -- 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/a668211b-5026-40c0-8aa8-538f2854bc52n%40googlegroups.com.
Re: [qubes-users] User used to write to network share
In dom0 terminal: > qvm-prefs [domain qubes name] qrexec_timeout 3600 On Thursday, July 21, 2022 at 1:56:35 PM UTC-7 Qubes wrote: > Howard Chen wrote: > > I have no ideas that are you talk about, but the R4.1 can be compatible > > with R4.0's accessibility for your servers. However, it might be another > > distro version problem(s) that R4.0 using Fedora 29 while R4.1 using > Fedora > > The version of Fedora you are referring to here is the version of Fedora > used for dom0, not the Templates. Debian-11 template is the same version > on both 4.0 and 4.1. > > > 32. @Unman will figure it out for you because I don't have the right > tools > > to do this type of troubleshoot similar as yours. > > On Thursday, July 21, 2022 at 12:52:42 PM UTC-7 Qubes wrote: > > > >> Qubes wrote: > >>> How does one overcome the problem of the user used to write to a > network > >>> share? > >>> > >>> In broader explanation. Say for example i connect to a network share > >>> > >>> sudo mount -o username=testuser //my-server/dir /home/user/testmount > >>> > >>> the share mounts and i can browse the file system but i cannot write to > >>> it because the write is made with the user "user" that logs onto the > >>> booted VM automatically with an unknown possibly empty password. This > >>> causes the write fail because the user "testuser" must make the write. > >>> > >>> Now on R4.0 i could make the mount with the noperm option > >>> > >>> sudo mount -o username=testuser,noperm //my-server/dir > >> /home/user/testmount > >>> > >>> Doing it like this worked 100%. When i wrote a file to the share it > >>> applied the ACLs on the share to the file being written to the share. > >>> Something in 4.1 is causing this to fail. > >>> > >>> Can anybody give me any pointers? > >>> > >>> Is it perhaps possible in 4.1 to specify the user that is used to > >>> automatically log into a VM? > >>> > >> > >> To add to this, perhaps a hint in the right direction. If i create a > >> file from cli on the network share, mounted with the "noperm" option, > >> and i edit and save it with vi it works as expected. > >> > >> sudo mount -o username=testuser,noperm //my-server/dir > /home/user/testmount > >> cd /home/user/testmount/ > >> touch testperm2.txt > >> vi testperm2.txt > >> i can edit and save the file and when i check the network share ACLs are > >> correct. > >> > >> Which means the problem is with Gnome Text Editor that i use for all of > >> my note taking. > >> > >> Is there someone that can help me understand this problem? I know gedit > >> creates a temporary file that it does the edits it and then writes that > >> to disk. I suspect the problem lies here but i have no idea how to > >> address it. Specifically it wasn't a problem on R4.0. > >> > >> Is it possible that something in R4.1 has changed the behavior here? > >> > > > > -- 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/18bb84bf-f8ec-4e2c-a045-f08f915f9ca3n%40googlegroups.com.
[qubes-users] Re: dvm considerably slower on R4.1
I have the similar as yours, but the time of one of my qubes cannot be open because of light VM error that I got, which is error 135. The time doubling effect is just to place for the computer took way too long on some occasional reasons to go for it. Anyways, it's just the distro issue from Debian. On Thursday, July 21, 2022 at 1:53:56 PM UTC-7 Qubes wrote: > Has the 4.1 as well as 4.1.1, because I did test on both, release added > additional overhead to the creation of a dvm? > > I have identical dvm's for Firefox on 4.0 and 4.1 and on 4.1 it takes > almost, in the region of 0.5 - 0.75 seconds almost, **double** the time > for a new dvm to be ready for usage, 18 seconds vs 36 (both rounded for > convenience). > > That is quite a hefty difference. Is there any explanation for this > behavior? > -- 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/17ad7b47-1ecb-4d57-80d5-9da6e39137cdn%40googlegroups.com.
Re: [qubes-users] User used to write to network share
I have no ideas that are you talk about, but the R4.1 can be compatible with R4.0's accessibility for your servers. However, it might be another distro version problem(s) that R4.0 using Fedora 29 while R4.1 using Fedora 32. @Unman will figure it out for you because I don't have the right tools to do this type of troubleshoot similar as yours. On Thursday, July 21, 2022 at 12:52:42 PM UTC-7 Qubes wrote: > Qubes wrote: > > How does one overcome the problem of the user used to write to a network > > share? > > > > In broader explanation. Say for example i connect to a network share > > > > sudo mount -o username=testuser //my-server/dir /home/user/testmount > > > > the share mounts and i can browse the file system but i cannot write to > > it because the write is made with the user "user" that logs onto the > > booted VM automatically with an unknown possibly empty password. This > > causes the write fail because the user "testuser" must make the write. > > > > Now on R4.0 i could make the mount with the noperm option > > > > sudo mount -o username=testuser,noperm //my-server/dir > /home/user/testmount > > > > Doing it like this worked 100%. When i wrote a file to the share it > > applied the ACLs on the share to the file being written to the share. > > Something in 4.1 is causing this to fail. > > > > Can anybody give me any pointers? > > > > Is it perhaps possible in 4.1 to specify the user that is used to > > automatically log into a VM? > > > > To add to this, perhaps a hint in the right direction. If i create a > file from cli on the network share, mounted with the "noperm" option, > and i edit and save it with vi it works as expected. > > sudo mount -o username=testuser,noperm //my-server/dir /home/user/testmount > cd /home/user/testmount/ > touch testperm2.txt > vi testperm2.txt > i can edit and save the file and when i check the network share ACLs are > correct. > > Which means the problem is with Gnome Text Editor that i use for all of > my note taking. > > Is there someone that can help me understand this problem? I know gedit > creates a temporary file that it does the edits it and then writes that > to disk. I suspect the problem lies here but i have no idea how to > address it. Specifically it wasn't a problem on R4.0. > > Is it possible that something in R4.1 has changed the behavior here? > -- 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/9f5a6ede-aa39-44ea-869e-78d5be002825n%40googlegroups.com.
Re: [qubes-users] qubes core agent networking iso building help
Thanks, Unman. This will take me about 18 to 19 months to finish and publish if I have the right tools that I need and the codes probabilities for that to happen. On Tuesday, July 19, 2022 at 4:08:06 AM UTC-7 unman wrote: > On Mon, Jul 11, 2022 at 11:47:19AM -0700, Howard Chen wrote: > > I need help to build the qubes core agent tools for the new OS that > called > > LinuxFX. Here is the story. > > > > I stumped across the YT for other Linux OS that functions similar to > > Windows. This OS that was introduced to me by a YouTuber goes by "Linux > For > > Everyone" with a video called "This Linux OS Looks EXACTLY Like Windows > > 10!" This video talks about this OS that I am working with and will > > implemented into Qubes if I can do it. The question is: How to create an > > ISO file in qubes? > > > I'm not clear what you are asking. > Do you want to build the core agent tools? Read the docs on > qubes-builder. LinuxFX is based on Ubuntu so you can probably use the > Ubuntu tools as is. > Do you want to build a template? Treat it as a flavor of Ubuntu, so you > build (e.g) focal+linuxfx. > > If you want to create a Qubes based on LinuxFX instead of Fedora, then > that's far more difficult. You'll need to build all the components for > Ubuntu. > An alternative would be to use Fedora as dom0, and try to implement > LinuxFX as sys-gui. > Whatever your aim you should read the docs on building. > > -- 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/5c9e8ad1-f351-41e0-8286-463456fe366fn%40googlegroups.com.
Re: [qubes-users] Re: Qubes OS 4.1.1 has been released!
It might be the release notes has turned into patch 2 for the qubes and correcting them in the process. On Monday, July 18, 2022 at 8:27:25 PM UTC-7 a...@qubes-os.org wrote: > On 7/18/22 7:59 PM, Howard Chen wrote: > > Danm! That's a long a** message to read, and most importantly, the qubes > > release note was written with 4.1.2 instead of 4.1.1. > > Hi Howard, > > I'm not sure what you mean. 4.1.2 doesn't exist yet, and it isn't > mentioned anywhere in this announcement. Where are you seeing 4.1.2? > > Also, this announcement isn't actually that long, but it's divided up > into small sections anyway, so feel free to skim and skip the ones that > aren't relevant to you. > > Best, > Andrew > > P.S. -- Please avoid top-posting. > > > On Monday, July 18, 2022 at 6:59:52 PM UTC-7 a...@qubes-os.org wrote: > > > >> Dear Qubes Community, > >> > >> We're pleased to announce the stable release of Qubes 4.1.1! This > >> release aims to consolidate all the security patches, bug fixes, and > >> upstream template OS upgrades that have occurred since the initial Qubes > >> 4.1.0 release in February. Our goal is to provide a secure and > >> convenient way for users to install (or reinstall) the latest stable > >> Qubes release with an up-to-date ISO. > >> > >> Qubes 4.1.1 is available on the > >> [downloads](https://www.qubes-os.org/downloads/) page. > >> > >> > >> ## Reminder: Qubes 4.0 approaching end-of-life > >> > >> As we recently > >> [announced]( > >> > https://www.qubes-os.org/news/2022/07/04/qubes-os-4-0-eol-on-2022-08-04/), > >> > >> Qubes 4.0 reaches EOL (end-of-life) on 2022-08-04. If you're using Qubes > >> 4.0 and have been waiting for an opportunity to upgrade to Qubes 4.1 via > >> the [clean > >> reinstallation]( > >> https://www.qubes-os.org/doc/upgrade/4.1/#clean-installation) > >> method, we strongly recommend using this Qubes 4.1.1 release to do so, > >> as this is the last Qubes 4.1 patch release before Qubes 4.0 reaches > EOL. > >> > >> > >> ## Existing Qubes 4.1.0 and release candidate users > >> > >> If you are already using Qubes 4.1.0 or [Qubes > >> 4.1.1-rc1](https://www.qubes-os.org/news/2022/06/27/qubes-4-1-1-rc1/), > >> then you should simply [update > >> normally](https://www.qubes-os.org/doc/how-to-update/) (which includes > >> [upgrading any EOL > >> templates]( > >> https://www.qubes-os.org/doc/how-to-update/#upgrading-to-avoid-eol) > >> you might have) in order to make your system essentially equivalent to > >> this stable Qubes 4.1.1 release. No special action is required on your > >> part. > >> > >> > >> ## What's new in Qubes 4.1.1? > >> > >> Qubes 4.1.1 includes numerous updates over the initial 4.1.0 release, in > >> particular: > >> > >> - All 4.1.0 dom0 updates to date > >> - Fedora 36 template (upgraded from Fedora 34) > >> - Linux kernel 5.15 (upgraded from 5.10) > >> > >> > >> ## What is a patch release? > >> > >> The Qubes OS Project uses the [semantic versioning](https://semver.org/ > ) > >> standard. Version numbers are written as `..`. > >> Hence, we refer to releases that increment the third number as "patch > >> releases." A patch release does not designate a separate, new major or > >> minor release of Qubes OS. Rather, it designates its respective major or > >> minor release (in this case, 4.1.0) inclusive of all updates up to a > >> certain point. Installing Qubes 4.1.0 and fully updating it results in > >> essentially the same system as installing Qubes 4.1.1. You can learn > >> more about how Qubes release versioning works in the [version > >> scheme](https://www.qubes-os.org/doc/version-scheme/) documentation. > >> > >> > >> This announcement is also available on the Qubes website: > >> https://www.qubes-os.org/news/2022/07/18/qubes-4-1-1.md > >> > > > > -- 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/9776ed1b-1cab-4312-8c88-a86c9c86cccen%40googlegroups.com.
[qubes-users] Re: Qubes OS 4.1.1 has been released!
Danm! That's a long a** message to read, and most importantly, the qubes release note was written with 4.1.2 instead of 4.1.1. On Monday, July 18, 2022 at 6:59:52 PM UTC-7 a...@qubes-os.org wrote: > Dear Qubes Community, > > We're pleased to announce the stable release of Qubes 4.1.1! This > release aims to consolidate all the security patches, bug fixes, and > upstream template OS upgrades that have occurred since the initial Qubes > 4.1.0 release in February. Our goal is to provide a secure and > convenient way for users to install (or reinstall) the latest stable > Qubes release with an up-to-date ISO. > > Qubes 4.1.1 is available on the > [downloads](https://www.qubes-os.org/downloads/) page. > > > ## Reminder: Qubes 4.0 approaching end-of-life > > As we recently > [announced]( > https://www.qubes-os.org/news/2022/07/04/qubes-os-4-0-eol-on-2022-08-04/), > > Qubes 4.0 reaches EOL (end-of-life) on 2022-08-04. If you're using Qubes > 4.0 and have been waiting for an opportunity to upgrade to Qubes 4.1 via > the [clean > reinstallation]( > https://www.qubes-os.org/doc/upgrade/4.1/#clean-installation) > method, we strongly recommend using this Qubes 4.1.1 release to do so, > as this is the last Qubes 4.1 patch release before Qubes 4.0 reaches EOL. > > > ## Existing Qubes 4.1.0 and release candidate users > > If you are already using Qubes 4.1.0 or [Qubes > 4.1.1-rc1](https://www.qubes-os.org/news/2022/06/27/qubes-4-1-1-rc1/), > then you should simply [update > normally](https://www.qubes-os.org/doc/how-to-update/) (which includes > [upgrading any EOL > templates]( > https://www.qubes-os.org/doc/how-to-update/#upgrading-to-avoid-eol) > you might have) in order to make your system essentially equivalent to > this stable Qubes 4.1.1 release. No special action is required on your > part. > > > ## What's new in Qubes 4.1.1? > > Qubes 4.1.1 includes numerous updates over the initial 4.1.0 release, in > particular: > > - All 4.1.0 dom0 updates to date > - Fedora 36 template (upgraded from Fedora 34) > - Linux kernel 5.15 (upgraded from 5.10) > > > ## What is a patch release? > > The Qubes OS Project uses the [semantic versioning](https://semver.org/) > standard. Version numbers are written as `..`. > Hence, we refer to releases that increment the third number as "patch > releases." A patch release does not designate a separate, new major or > minor release of Qubes OS. Rather, it designates its respective major or > minor release (in this case, 4.1.0) inclusive of all updates up to a > certain point. Installing Qubes 4.1.0 and fully updating it results in > essentially the same system as installing Qubes 4.1.1. You can learn > more about how Qubes release versioning works in the [version > scheme](https://www.qubes-os.org/doc/version-scheme/) documentation. > > > This announcement is also available on the Qubes website: > https://www.qubes-os.org/news/2022/07/18/qubes-4-1-1.md > -- 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/c506aaa0-778b-4293-a7d3-0e81343307e2n%40googlegroups.com.
Re: [qubes-users] Onion site and repos are down
Where's the SSL key for the onion site? On Thursday, July 14, 2022 at 4:44:57 PM UTC-7 unman wrote: > I am advised that the onion server is back online > unman > -- 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/9557b642-3648-49a2-a592-256df78d0fbcn%40googlegroups.com.
[qubes-users] Re: Onion site and repos are down
This site can’t be reached The webpage at *http://qubesosfasa4zl44o4tws22di6kepyzfeqv3tg4e3ztknltfxqrymdad.onion/* might be temporarily down or it may have moved permanently to a new web address. ERR_SOCKS_CONNECTION_FAILED On Tuesday, July 12, 2022 at 5:13:45 PM UTC-7 unman wrote: > I am advised that there is a hardware fault, and the onion site is down. > We're working on 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/e20808b7-4e54-4ff7-b94e-e0b5d3f9ce85n%40googlegroups.com.
[qubes-users] qubes core agent networking iso building help
I need help to build the qubes core agent tools for the new OS that called LinuxFX. Here is the story. I stumped across the YT for other Linux OS that functions similar to Windows. This OS that was introduced to me by a YouTuber goes by "Linux For Everyone" with a video called "This Linux OS Looks EXACTLY Like Windows 10!" This video talks about this OS that I am working with and will implemented into Qubes if I can do it. The question is: How to create an ISO file 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/825222a3-eef9-46fe-a7f9-aefd3abdb125n%40googlegroups.com.
[qubes-users] Re: Regarding Impact of US Export controls on Qubes.
The US does not export to Iran, but still exported to Cuba. Qubes just an OS that based on Fedora. You don't have t be concern because of Whonix built-in. On Sunday, July 10, 2022 at 10:10:48 AM UTC-7 Noob Qubes user wrote: > Hi , i am wondering if i am a user from cuba or iran , am i supposed to > use qubes in first place. i saw in fedora download page that people from > sanction hit areas should not use fedora . since qubes is based on fedora , > i am wondering on impact of US Export controls. > -- 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/aa29a98f-393e-48fe-817b-5e2dee25c439n%40googlegroups.com.
[qubes-users] Notification Sound Configuration
I have a file that I needed to put in the notification sound directory, but I don't know which directory to put as a notification sound in dom0. I might need some help to put my new notification file to the notification sound directory. Is there a directory for custom notification sounds? -HPOA909 -- 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/78bc161f-51e7-ae19-73c1-2cd630075876%40gmail.com.