[qubes-users] Re: HVM Mouse Emulation Options
On Sunday, 8 May 2016 09:31:31 UTC+10, fred_...@sigaint.org wrote: > > I've installed an Android-based HVM (Remix OS). When installed on bare > metal, physical usb mice behave like normal desktop mice in the OS. > > However, in the HVM, the cursor needs to be dragged around with the mouse. > I read previously on qubes-users that Qubes uses USB Tablet emulation. > Could that be the cause? Is it possible to use PS/2 emulation instead? > > I'm not sure if this is more of a Xen topic than a Qubes one. Tried > searching for "xen virtual mouse usb tablet ps/2" with no success. Thanks > in advance! > > I have no issue with this. the cursor works normally for me. Wether it be x86 or x64 it doesn't matter. I move the mouse and click and it works. Perhaps there is some other issue with your PC/Virtual? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/12e2a1d0-6b21-45e4-8487-c2f65e902c69%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Firewall VM, rule not working, what has gone wrong?
On Thursday, 2 June 2016 11:12:14 UTC+10, Unman wrote: > > Oh Drew, > Geek is confirmed. > > If you want to control traffic from the vif+ interfaces, you need the > FORWARD chain. > > The default rules allow RELATED,ESTABLISHED traffic both ways in FORWARD > chain, and drop all traffic between vifs - you know this already. > > What you want (assuming $eth is defined) is: > iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW > -j ACCEPT > iptables -I FORWARD 3 -i vif+ -o $eth -j DROP > > This is because the ESTABLISHED rule is by default #1, you insert 1 > before, and then I3 to insert the DROP rule after. > You were almost there but got the count wrong. > > unman > Hi Unman, I tried it and I've found that it requires the extras. This is what I have that now works perfectly thanks. iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -I FORWARD 1 -o vif+ -i $eth -s 1.2.3.0/24 -m state --state NEW,ESTABLISHED,RELATED -j ACCEPT iptables -I FORWARD 3 -i vif+ -j DROP iptables -I FORWARD 3 -i $eth -j DROP IPTABLES now looks like this... --- Chain INPUT (policy DROP) target prot opt source destination DROP udp -- anywhere anywhere udp dpt:bootpc ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT icmp -- anywhere anywhere ACCEPT all -- anywhere anywhere REJECT all -- anywhere anywhere reject-with icmp-host-prohibited Chain FORWARD (policy DROP) target prot opt source destination ACCEPT all -- 1.2.3.0/24 anywhere state NEW,RELATED,ESTABLISHED ACCEPT all -- anywhere 1.2.3.0/24 state NEW,RELATED,ESTABLISHED DROP all -- anywhere anywhere DROP all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere DROP all -- anywhere anywhere ACCEPT udp -- 10.137.2.2 gateway udp dpt:domain ACCEPT udp -- 10.137.2.2 10.137.2.254 udp dpt:domain ACCEPT tcp -- 10.137.2.2 gateway tcp dpt:domain ACCEPT tcp -- 10.137.2.2 10.137.2.254 tcp dpt:domain ACCEPT icmp -- 10.137.2.2 anywhere DROP tcp -- 10.137.2.2 10.137.255.254 tcp dpt:us-cli ACCEPT all -- 10.137.2.2 anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination --- After the 4th rule in FORWARD, I can just remove everything else can't I? Since it's now completely restricted from rule 1-4? Or do they still have some effect? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2b38cb9f-d48e-49cb-ade9-013cbf728abe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] update whonix failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-01 11:04, 921'38451'034918'093248'1093248'01943 wrote: > Hello, > > I have a fresh installed R31 and updated whonix like described in > > https://www.qubes-os.org/doc/whonix/update/ > > But it finished with: > > Whonix firewall script failed: > > ## Whonix firewall > script failed! ## > iptables v1.4.21: can't initialize iptables table `filter': > Permission denied (you must be root) Perhaps iptables or your > kernel needs to be upgraded. dpkg: error processing package > qubes-whonix (--unpack): subprocess installed post-installation > script returned error exit status 3 Errors were encountered while > processing: qubes-whonix E: Sub-process /usr/bin/dpkg returned an > error code (1) user@host:~$ > > How can I fix it? > > Kind Regards > To receive a faster reply, I recommend asking this in the Whonix forums. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXT7qwAAoJENtN07w5UDAw98gP/2zeXQDyaVUC90scSM4akduo 58GfNFfbUP4Wi1ZNPR8CfRUVl3sBOxIUpTHRCOdBI4l+z3it7ypdahb+UpicrdHm Py5V4NxKLnX/A06hjTj7xCz3YIeXACIfZboH4vE5cI+67gA7wECHMy4pi8kh5f6I f+wdhjU/zLaUXhshjQUhlDnpETYuoRxXDzZjqpmecgj//dnYuWdwS9dtiSE3/ays bgsie1TIkQfT7U6qoTgRz11jr/8jeSTTK5IfKYcvhtQfD2hyzXQ5U56OM5PC8TbI F69blqqtaLuEwrvVinSr5SYOSDEy1QSib21/oH745d4A6I8h2p4xGbTLUC0E6eoG P3LYARwHifeMPMmFIEMNs7rexjZNTJEHQ0fLvoxT4X4tV+OlnAvK/cKs+/YTSMwj UBfv17X5CJ5ck4DdXZ2qomfs0A3F/VfY2R1Sshc9SYtRT9qv+v6fh9QlC8T2huCb 3GffEg7ZjFDn5U2/QPHFPdqlqkyvi+P0Z45eJ6AE8vhDYV1LysE8sZL/mu1FCS+h 8f41QQ9WZo/Tq3HRjKQByON/00b5ojdaVxo8G6Of3qcxTn/3ByLlInfGllAJ5nhM 490u/jFgm6i7D3468Z2aEbFzuDnV6K1k0CnptxNwd7g3tj09I6dDwgZ/ifJ1bKwu nqLV0KxTxvWZ/yBnG8xs =ks94 -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/15531e4c-4df5-5192-3818-f8b48d078c25%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
On Thursday, 2 June 2016 14:11:32 UTC+10, Chris Laprise wrote: > > > > On 06/01/2016 10:29 PM, Drew White wrote: > > > > The UI he is describing is system-config-printer (Red Hat). He > > could try > > gnome-control-center ->Printers instead. That works for me. > > > > Chris > > > > > > Chris, that is essentially what I did. But not through the > > control center, just directly through the menu system and > > running that exact section. > > The gnome utility is not the same as the system-config-printer utility > (written by Red Hat). The former works fine for me in debian. BTW, I > setup my debian template using 'tasksel' and chose both debian desktop > and gnome. > Isn't Gnome the Debian Dektop GUI? > > > I did the same thing in Fedora (RedHat) and it worked fine. > > > > After it detected the printer, it searched for the drivers, didn't > > find them, so I put the OpenDriver file on and installed it. > > RedHat based, easy. Debian based, crashed. > > I have been manually choosing from the built-in drivers. For many > printers, you can use a driver with a model number that's close if > there's no exact match. > There is the problem in the first place. That's the bit I can't get to, as per my OP. I can't get THAT far. If I could then I wouldn't be having the issue and be here trygin to get an answer. > > > > Currently on Debian 8. I don't know if it's a bug in Debian 8 > > or not though. > > Either in debian or the driver. > It could be something in Debian OR the Qubes Drivers. Not the Printer drivers, as I can't even get to the point to select 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/022752df-3de7-4741-8006-8382ae2c0b52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
On 06/01/2016 10:29 PM, Drew White wrote: The UI he is describing is system-config-printer (Red Hat). He could try gnome-control-center ->Printers instead. That works for me. Chris Chris, that is essentially what I did. But not through the control center, just directly through the menu system and running that exact section. The gnome utility is not the same as the system-config-printer utility (written by Red Hat). The former works fine for me in debian. BTW, I setup my debian template using 'tasksel' and chose both debian desktop and gnome. I did the same thing in Fedora (RedHat) and it worked fine. After it detected the printer, it searched for the drivers, didn't find them, so I put the OpenDriver file on and installed it. RedHat based, easy. Debian based, crashed. I have been manually choosing from the built-in drivers. For many printers, you can use a driver with a model number that's close if there's no exact match. Currently on Debian 8. I don't know if it's a bug in Debian 8 or not though. Either in debian or the driver. Chris -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/574FB1EC.8030705%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Tools for Windows definitly broken.
On Thursday, 2 June 2016 08:43:56 UTC+10, raah...@gmail.com wrote: > > actually, sometimes windows hvm errors and won't load when selecting an > app from the startmenu. So usually I just start the win7 vm manually > from the qubes-manager first before loading a program from it. I have the HVM started before I even start an application. I give it 2 minutes before I even clicked an application to start. I even attempted to run a command using the "Run command in VM" option from the manager. Neither way worked. Nothing showed up. Is there anything you have disabled in Windows to get it all to work properly? But that is one thing I think they need to fix in the Tools too, because I noticed that it creates it as 1 large monitor, not as multiple displays. Which it should, to prevent issues. It may even resolve some of the issues I have been reading about in the bug reporting things. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/57e35fbd-e4cc-4305-a781-5a5455417201%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
> The UI he is describing is system-config-printer (Red Hat). He could try > gnome-control-center ->Printers instead. That works for me. > > Chris > Chris, that is essentially what I did. But not through the control center, just directly through the menu system and running that exact section. I did the same thing in Fedora (RedHat) and it worked fine. After it detected the printer, it searched for the drivers, didn't find them, so I put the OpenDriver file on and installed it. RedHat based, easy. Debian based, crashed. Currently on Debian 8. I don't know if it's a bug in Debian 8 or not though. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f79806eb-ccc7-4967-979e-4820b772e0df%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
To star print settings you add it to the application list by using the ADD MORE SHORTCUTS for that virtual. Then you click on that shortcut. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7a1c80e0-6578-4c23-a6fb-265c46425957%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Firewall VM, rule not working, what has gone wrong?
One more thing.. Where in that section can I specify the port/port range to have the communications on? Is it possible to have a range? Or do I have to specify each and every port? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/cf6cf163-b8a0-411c-8b29-551dac7063fe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Firewall VM, rule not working, what has gone wrong?
Hi Unman, Happy to hear from someone that I knew has been able to assist in the past. On Thursday, 2 June 2016 11:12:14 UTC+10, Unman wrote: > > Oh Drew, > Geek is confirmed. > Geek? GEEK?? I'm not just an ordinary geek my friend. I'm a super geek! :/ lol > If you want to control traffic from the vif+ interfaces, you need the > FORWARD chain. > I've got forwards for all my InterVM Network and my bridged virtuals and more. > The default rules allow RELATED,ESTABLISHED traffic both ways in FORWARD > chain, and drop all traffic between vifs - you know this already. > > What you want (assuming $eth is defined) is: > iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW > -j ACCEPT > iptables -I FORWARD 3 -i vif+ -o $eth -j DROP > > This is because the ESTABLISHED rule is by default #1, you insert 1 > before, and then I3 to insert the DROP rule after. > You were almost there but got the count wrong. > And yes, $eth is defined after discovery of identifiers. I recently had a huge issue with it when I transferred from Fedora to Debian.. ifconfig differences.. But I resolved it all, and it's all now working apart from this bit for traffic restrictions. Ahh, okay. I'll give it a shot and inform you of the results. So for the incoming connections, it's the same methodology, just switched source and destination around? And ... iptables -I FORWARD 3 -i vif+ -o $eth -j DROP Does it really need the interfaces specified if I have the ... ... iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW -j ACCEPT iptables -I FORWARD 1 -o vif+ -i $eth -s 1.2.3.0/24 -m state --state NEW -j ACCEPT can't it be ... ? iptables -I FORWARD 3 -j DROP -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/52d96fbe-0b79-4bf2-9250-748ccb0c745c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Firewall VM, rule not working, what has gone wrong?
On 05/31/2016 09:27 PM, Drew White wrote: Hi folks, I'm trying to get my ProxyVM to work properly the way I want it to, but the firewall is not cooperating and I feel there is either something I am doing wrong, OR something in Qubes initial configuration causing an issue, but I can't find what is wrong. Any good help would be greatly appreciated. Thanks in advance! The result I'm looking for is to block everything outgoing from vif+ to any ip range OTHER than what I specify. The hashed out are ones that I tried, but they failed. In the end I brought it back to the first one, the base simplicity, but even that still doesn't work (and I didn't think it would really, but I tried it anyway). Syntax errors... iptables -i $eth -s 1.2.3.0/24 -j ACCEPT iptables -o $eth -d 1.2.3.0/24 -j ACCEPT iptables -o $eth -j DROP iptables -i $eth -j DROP ^ This block is missing a command and chain name, such as '-A INPUT'. #iptables -I PREROUTING 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW -p tcp -m tcp -j ACCEPT #iptables -I PREROUTING 1 -i vif+ -o $eth -d 1.2.3.024 -p udp -m udp -j ACCEPT #iptables -I PREROUTING 3 -i vif+ -m state --state NEW -p tcp -m tcp -j DROP #iptables -I PREROUTING 3 -i vif+ -p udp -m udp -j DROP ^ This block is trying to use the default table, which doesn't have a PREROUTING chain. Try specifying '-t nat'. Chris -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/574F923F.1060901%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
On 06/01/2016 06:52 PM, raahe...@gmail.com wrote: On Tuesday, May 31, 2016 at 9:12:49 PM UTC-4, Drew White wrote: On Saturday, 28 May 2016 04:01:57 UTC+10, raah...@gmail.com wrote: what printer model? if its networked as been said you have to temp allow network access. Maybe you dont' realize your fedora template is being allowed network acess for some reason but the debian one is not? double check the firewall settings for each. It's a Konica Minolta. I'll go into more detail for you since you may not be understanding what I meant because I didn't go into enough detail. 1. start Print Settings 2. click Add button 3. click on Network Printer. 4. Find Network Printer. 6. Enter Host IP of Printer. 7. Click Find 8. Select Konica Minolta from found printers list. 9. Make sure hostname is correct for printer. 10. Chance it to the IP instead of hostname and click Probe. 11. Ensure the Queue is correct and Connection as well. 12. Click Forward 13. "Searching for Drivers" dialogue pops up, then vanishes, New Printer window vanishes, Print Settings vanishes. -- All other windows open stay there, it's only the print settings and sub windows that vanish. -- That was the first thing I checked. -- If I perform the same thing in an AppVM, the whole Print Settings and Add Printer all just lock up. instead of vanishing. How are you starting "print settings"? Did you try system-config-printer command from the terminal? And So it finds the printer on the network but crashes when it says searching for drivers?I'm not sure what you mean by print settings and sub windows. Wouldn't print settings be after you install it? Never even heard of that model maybe you have to manually download the driver from their website for fedora? not sure. You could also try asking on fedora forums. The UI he is describing is system-config-printer (Red Hat). He could try gnome-control-center ->Printers instead. That works for me. Chris -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/574F908B.8060704%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Firewall VM, rule not working, what has gone wrong?
On Tue, May 31, 2016 at 06:27:14PM -0700, Drew White wrote: > Hi folks, > > I'm trying to get my ProxyVM to work properly the way I want it to, but the > firewall is not cooperating and I feel there is either something I am doing > wrong, OR something in Qubes initial configuration causing an issue, but I > can't find what is wrong. > > Any good help would be greatly appreciated. > > Thanks in advance! > > The result I'm looking for is to block everything outgoing from vif+ to any > ip range OTHER than what I specify. > > The hashed out are ones that I tried, but they failed. > In the end I brought it back to the first one, the base simplicity, but > even that still doesn't work (and I didn't think it would really, but I > tried it anyway). > > iptables -i $eth -s 1.2.3.0/24 -j ACCEPT > iptables -o $eth -d 1.2.3.0/24 -j ACCEPT > iptables -o $eth -j DROP > iptables -i $eth -j DROP > > #iptables -I PREROUTING 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state > NEW -p tcp -m tcp -j ACCEPT > #iptables -I PREROUTING 1 -i vif+ -o $eth -d 1.2.3.024 -p udp -m udp -j > ACCEPT > #iptables -I PREROUTING 3 -i vif+ -m state --state NEW -p tcp -m tcp -j DROP > #iptables -I PREROUTING 3 -i vif+ -p udp -m udp -j DROP > # > #iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW > -p tcp -m tcp -j ACCEPT > #iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -p udp -m udp -j ACCEPT > #iptables -I FORWARD 3 -i vif+ -j DROP > # > #iptables -I INPUT 1 -i vif+ -d 1.2.3.0/24 -m state --state NEW -p tcp -m > tcp -j ACCEPT > #iptables -I INPUT 1 -i vif+ -d 1.2.3.0/24 -p udp -m udp -j ACCEPT > #iptables -I INPUT 3 -i vif+ -j DROP > # > #iptables -I OUTPUT 1 -o $eth -d 1.2.3.0/24 -m state --state NEW -p tcp -m > tcp -j ACCEPT > #iptables -I OUTPUT 1 -o $eth -d 1.2.3.0/24 -p udp -m udp -j ACCEPT > #iptables -I OUTPUT 3 -o $eth -j DROP > Oh Drew, Geek is confirmed. If you want to control traffic from the vif+ interfaces, you need the FORWARD chain. The default rules allow RELATED,ESTABLISHED traffic both ways in FORWARD chain, and drop all traffic between vifs - you know this already. What you want (assuming $eth is defined) is: iptables -I FORWARD 1 -i vif+ -o $eth -d 1.2.3.0/24 -m state --state NEW -j ACCEPT iptables -I FORWARD 3 -i vif+ -o $eth -j DROP This is because the ESTABLISHED rule is by default #1, you insert 1 before, and then I3 to insert the DROP rule after. You were almost there but got the count wrong. 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20160602011213.GA15000%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] qubes-builder failing to build template
On Tuesday, May 31, 2016 at 6:21:00 AM UTC-4, Marek Marczykowski-Górecki wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Fri, May 27, 2016 at 01:34:35PM -0700, patie...@terminalmoronicy.com > wrote: > > I'm trying to build an installation ISO based on Qubes R3.1, but with > the > > kernel swapped out (I'm using a qubes- patched 4.5.5 kernel). > > > > I have successfully built installation ISOs before, but not with v4.5 > > kernels. > > > > Qubes builder keeps failing in template-local-fc23. The tail of > > build-logs/template-fc23.log looks like: > > > > $ tail build-logs/template-fc23.log > > Package dnf-1.1.9-1.fc23.noarch is already installed, skipping. > > Dependencies resolved. > > Nothing to do. > > Complete! > > -> Installing package groups... > > 28 files removed > > Last metadata expiration check: 0:00:14 ago on Fri May 27 18:50:16 2016. > > Error: libreoffice-math > > Makefile:47: recipe for target 'rootimg-build' failed > > make[1]: *** [rootimg-build] Error 1 > > > > If I rerun "make template-local-fc23" repeatedly, it keeps failing on > > different packages (i.e. "libreoffice-math" became "libreoffice-impress" > > after another attempt) - I'm assuming it is making some progress each > time. > > This is upstream bug (triggered by recent dnf update - 1.1.9-1): > https://bugzilla.redhat.com/show_bug.cgi?id=1339742 > > Just pushed workaround for it: > > https://github.com/marmarek/qubes-builder-fedora/commit/1b6ea836d0556437946e94a4835f0ee3f962f498 > > > Theoretically it should be fixed by dnf 1.1.9-2 (they've reverted the > change triggering the bug), but haven't tested it yet. > > The problem didn't resolve by re-trying the build (which maybe would be expected to pick up the new dnf?), but I can confirm your workaround did the job - thanks! -tom > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJXTWWHAAoJENuP0xzK19cs7r8H/RK9mYFX4jU3MOoDmiN+RYlA > d9PrLgR34TDaDfH17GmZsZozHNczfJ/EyiD+8Fqc/A6s9nMOCN3Q/VikeBL2vOgA > ZuNnHYuCUnPQ6Md4b5JMZ8tavP7Gm2Sqir9FaEi8Q+bmnI1yLZKAisXWVqyuN/oU > w31i6oSIysF/BVPiZiGpoDQR2esXj9opnXxTk4zKQErnG1RLXPm/ltZdc1FmBczq > emTHcNsfeVW5AOaLkOfqmu//nTM+piX3ng80kDOtMyXxuOJOgIhwtQS0JbPDEzpx > em/agF3LnsDo9RICtY9jGZTs3sXsGnjDChl/1JMspKDsVUMU4mjDlRLmroCN/tc= > =Gaxe > -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1bdc850b-20a5-47cb-960f-04f03de7f20a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793 )
On Wednesday, June 1, 2016 at 6:18:44 PM UTC-4, tnt_b...@keemail.me wrote: > thats correct it will work , but as u know we should find out the correct > fixation to this problem. > > > 1. Jun 2016 10:53 by a...@qubes-os.org: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-06-01 03:47, tnt_b...@keemail.me wrote:well i have already opened > this topic in github before long time , > but now andrewdavidwong recommended me to send this topic to users > section:- > > https://github.com/QubesOS/qubes-issues/issues/1745#event-665419288 > > I've experienced this too. If I just wait about 10 seconds, then try > to start sys-net again, it always works. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJXTr67AAoJENtN07w5UDAwAMgQALQdF58VO2/RW520IgCx12jc > Jc506wDrBXlMHU3Qts3N3eQmKeNMjdJrLLP/ZONNC1az1sI0ssrIVjkT5XO8h2/P > b/lY67Qa+9WMQpf8tj0faz6tsnh/tBuUyImEKkpo/389GtAGJAtLrR25cPjDCNXQ > /KTFn6/B4VJxwHFxjJjk2yAxtM4VyO5cTOGtkcrJK07SrC7U9722KDOOhLKLv6Ul > OtaRR0gA7UG6PghvV2ilUOYEshzEFQXoaeaaL3uHcNVuIFW9eb42rYSrStDPF+tg > pox4FXiqG/UZfc9dYZWESYgGItsEwCxHiXZH0zruEaaK8Euea/yNRDHcKh5mwDzs > 82O66WmnGvjP2q1YtHlJD1p0TEJma8M0uviLY+sjyi9S6psRBpnX4dAzW5CtKcpw > CsEj+wcQYlXWJ+LmAueDICC2NF2zsi9KtGXFRFHBllMFtTYklUGNYm08MUulzdvE > G6ZCkXkdJ5kv94d8krax3iQalYxH1dhBoXUhVsqXccVCNUHbbaS9S3G/Lf2g9CBf > gCk+dtCMAOexRiK71bZlpSyIQKrYGYGza6vYu6UEUml2r1fRoa8pLI/KmeJicKhd > lKcgcjy75eHJwGvylMnoTZ8h8oLm7fvbe6zJvdjBdTtT3qTKHkFLgN3lUahSFqKp > fe0ZvgThe7OeqrSSRM/+ > =hin+ > -END PGP SIGNATURE- Happens to me too. It can happen when restarting it too quick I guess because it takes a couple secs for it to fully close the old instance. I guess the faster your computer the less it would happen. For example same thing happens to me with sys-firewall if I start it too quick after the sys-net, basically before the sys-net has internet connection, which will cause an error as well. To avoid this now, instaed of manually starting the sysnet or proxies, i just load the appvm i want to use. So this way the sys-net and sys-firewall and proxy is automatically started at the proper intervals one after the other avoiding me accidentally starting one of them too quick. But you still have to give it acouple secs after first closing the sys-net . -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d905d866-a122-4249-bf14-b488ef343437%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] R31 installation with btfrs - error?
On 06/01/2016 02:10 PM, 1723094178230941780934781092437814328 wrote: Hello, I fresh installed R31, but if I tried to use the btfrs filesystem, the first boot will not work. It looks like I was running into some XEN error. Errors: Not switching root: /sysroot does not sem to be an OS tree Failed to fin d module xen-blkback How I can use btfrs under R31? Kind Regards Earlier fedora/redhat versions (like f20 in Qubes) apparently have issues finding the filesystem on some systems (though it has been fine on my system)... http://zurlinux.com/?p=1887 https://lists.centos.org/pipermail/centos/2014-December/148481.html Chris -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/574F682B.3090409%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Debian 8 Template, can't install printers
On Tuesday, May 31, 2016 at 9:12:49 PM UTC-4, Drew White wrote: > On Saturday, 28 May 2016 04:01:57 UTC+10, raah...@gmail.com wrote: > what printer model? if its networked as been said you have to temp allow > network access. Maybe you dont' realize your fedora template is being > allowed network acess for some reason but the debian one is not? double > check the firewall settings for each. > > It's a Konica Minolta. > > I'll go into more detail for you since you may not be understanding what I > meant because I didn't go into enough detail. > > 1. start Print Settings > 2. click Add button > 3. click on Network Printer. > 4. Find Network Printer. > 6. Enter Host IP of Printer. > 7. Click Find > 8. Select Konica Minolta from found printers list. > 9. Make sure hostname is correct for printer. > 10. Chance it to the IP instead of hostname and click Probe. > 11. Ensure the Queue is correct and Connection as well. > 12. Click Forward > 13. "Searching for Drivers" dialogue pops up, then vanishes, New Printer > window vanishes, Print Settings vanishes. > -- All other windows open stay there, it's only the print settings and sub > windows that vanish. > -- That was the first thing I checked. > -- If I perform the same thing in an AppVM, the whole Print Settings and > Add Printer all just lock up. instead of vanishing. How are you starting "print settings"? Did you try system-config-printer command from the terminal? And So it finds the printer on the network but crashes when it says searching for drivers?I'm not sure what you mean by print settings and sub windows. Wouldn't print settings be after you install it? Never even heard of that model maybe you have to manually download the driver from their website for fedora? not sure. You could also try asking on fedora forums. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/7a3f3ee0-0a95-46ef-b91f-3b08e46dee48%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Tools for Windows definitly broken.
On Tuesday, May 31, 2016 at 9:15:14 PM UTC-4, Drew White wrote: > On Saturday, 28 May 2016 03:57:26 UTC+10, raah...@gmail.com wrote:seamless > gui doesn't work for me for all programs. It will end up loading the whole > desktop regardless. It might depend on the program you are installing I'm > not sure. > > At least yours works for something. > Doesn't work for me, seamless just doesn't work. > What have you done to enable SOME things to work? actually, sometimes windows hvm errors and won't load when selecting an app from the startmenu. So usually I just start the win7 vm manually from the qubes-manager first before loading a program from 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4fc8edcf-b63e-49a0-800d-23d6abef5d17%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793 )
thats correct it will work , but as u know we should find out the correct fixation to this problem. 1. Jun 2016 10:53 by a...@qubes-os.org: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-06-01 03:47, > tnt_bom_...@keemail.me> wrote: >> well i have already opened this topic in github before long time , >> but now andrewdavidwong recommended me to send this topic to users >> section:- >> >> https://github.com/QubesOS/qubes-issues/issues/1745#event-665419288 >> >> > I've experienced this too. If I just wait about 10 seconds, then try > to start sys-net again, it always works. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJXTr67AAoJENtN07w5UDAwAMgQALQdF58VO2/RW520IgCx12jc > Jc506wDrBXlMHU3Qts3N3eQmKeNMjdJrLLP/ZONNC1az1sI0ssrIVjkT5XO8h2/P > b/lY67Qa+9WMQpf8tj0faz6tsnh/tBuUyImEKkpo/389GtAGJAtLrR25cPjDCNXQ > /KTFn6/B4VJxwHFxjJjk2yAxtM4VyO5cTOGtkcrJK07SrC7U9722KDOOhLKLv6Ul > OtaRR0gA7UG6PghvV2ilUOYEshzEFQXoaeaaL3uHcNVuIFW9eb42rYSrStDPF+tg > pox4FXiqG/UZfc9dYZWESYgGItsEwCxHiXZH0zruEaaK8Euea/yNRDHcKh5mwDzs > 82O66WmnGvjP2q1YtHlJD1p0TEJma8M0uviLY+sjyi9S6psRBpnX4dAzW5CtKcpw > CsEj+wcQYlXWJ+LmAueDICC2NF2zsi9KtGXFRFHBllMFtTYklUGNYm08MUulzdvE > G6ZCkXkdJ5kv94d8krax3iQalYxH1dhBoXUhVsqXccVCNUHbbaS9S3G/Lf2g9CBf > gCk+dtCMAOexRiK71bZlpSyIQKrYGYGza6vYu6UEUml2r1fRoa8pLI/KmeJicKhd > lKcgcjy75eHJwGvylMnoTZ8h8oLm7fvbe6zJvdjBdTtT3qTKHkFLgN3lUahSFqKp > fe0ZvgThe7OeqrSSRM/+ > =hin+ > -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/KJD1zNd--3-0%40keemail.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Lenovo Yoga 2 (updated)
The HCL page links to my old report from two years ago when there were problems with drivers. Now everything works fine for me. I use sys-usb so the touchscreen and bluetooth are not used and I'm not sure about their behaviour.They do appear in lsusb output. The camera and card reader work. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86c580cc-f1ed-fcd3-95a0-5d89e89d9a6e%40icloud.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-LENOVO-20344-20160601-221315.yml Description: application/yaml
[qubes-users] R31 installation with btfrs - error?
Hello, I fresh installed R31, but if I tried to use the btfrs filesystem, the first boot will not work. It looks like I was running into some XEN error. Errors: Not switching root: /sysroot does not sem to be an OS tree Failed to fin d module xen-blkback How I can use btfrs under R31? Kind Regards -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c72100ee-6120-4363-b96d-a586b92a5110%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] update whonix failed
Hello, I have a fresh installed R31 and updated whonix like described in https://www.qubes-os.org/doc/whonix/update/ But it finished with: Whonix firewall script failed: ## Whonix firewall script failed! ## iptables v1.4.21: can't initialize iptables table `filter': Permission denied (you must be root) Perhaps iptables or your kernel needs to be upgraded. dpkg: error processing package qubes-whonix (--unpack): subprocess installed post-installation script returned error exit status 3 Errors were encountered while processing: qubes-whonix E: Sub-process /usr/bin/dpkg returned an error code (1) user@host:~$ How can I fix it? Kind Regards -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b5046b78-26d2-4048-8f16-8e9d366b7ad1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: VM Manger VM App change keyboard?
solved! Just a right click on the VM manager on the VM and than I can change the keyboard layout (but must sort first under the shortnames, so I have a fast orientation in this very long list). Kind Regards -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1aaa6c06-58be-47b0-855b-3ddcc886b366%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Schenker Workstations as Notebooks / QubesOS?
Hi JPL, so the best in this case would be something like a dual boot like Debian for GPU calculations and QubesOS to run with the CPU's? Kind Regards -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/d4dd6bdd-1f37-4da4-88c7-1ba6d0eb51c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] nm-applet disappeared
On Wed, 1 Jun 2016 08:36:51 -0700 Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-06-01 06:13, ad5108...@gmail.com wrote: > > Hi, for some reason my nm-applet has disappeared from my system. I > > tried searching around for the cause of this, and the only causes > > I could find for Qubes 3 were deletion of the System Tray widget or > > related to changes in the NetVM template. I'm currently running the > > default configuration (aside from a few random applications > > installed in the fedora-23 template) and my System Tray is > > present. I have tried restarting the nm-applet, which generates a > > passed through notification that I'm connected to the network but > > does not display the applet. I'm not sure how long ago it stopped > > displaying either, I only noticed it because I wanted to change my > > network configuration and couldn't see the applet. Is there > > anything else I should try? > > > > Have you already tried restarting the NetVM itself (or the > whole system)? > > - -- By disappeared from the sytsem, I assum you mean you can't see it's icon, rather than it being not installed. Are you running xfce? This happens in fedora xfce sometimes and can be a bit frustrating. Try resizing the icon and menu bar several times. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0D5DB04C-F808-4FB2-A693-04CAF1449B96%40mail.bitmessage.ch. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] nm-applet disappeared
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-01 06:13, ad5108...@gmail.com wrote: > Hi, for some reason my nm-applet has disappeared from my system. I > tried searching around for the cause of this, and the only causes > I could find for Qubes 3 were deletion of the System Tray widget or > related to changes in the NetVM template. I'm currently running the > default configuration (aside from a few random applications > installed in the fedora-23 template) and my System Tray is > present. I have tried restarting the nm-applet, which generates a > passed through notification that I'm connected to the network but > does not display the applet. I'm not sure how long ago it stopped > displaying either, I only noticed it because I wanted to change my > network configuration and couldn't see the applet. Is there > anything else I should try? > Have you already tried restarting the NetVM itself (or the whole system)? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXTwD/AAoJENtN07w5UDAwajsQAJW3rK1iRIyHzaC/Y+D/xcj0 PW4+SAHJllXyyGC3oB2IWOJiFnPRlyHD/8uDdrJObU9Bqi00c+hMdHBpVYLlKO7X 2IJxjXvppc+5wJdPMTgEJeAvXw4oUoIiP6o0k0chNjIUXAQZmhe6jARkWE3tvcLT vYCWMR073nTbWBRYAsGmji1BxqnD6jUBwEG79LPpLqRU/qL8VIEyyj3odBU6GEMB OSTBcR+TeHewOyfWhzw1pO/5KWFkfayjSEGtCT61S+32XdMfl7aZVrH2964JwkHo e/yZlT0u4O8HnP+VpDKCImGwbOd0I5ehms4mMjKfxKn1T/2kWaw/JM1/oMc+gUpX 7Zn2glP5mEJPyEaSyVZrpeDdJ5Un5cfHrtmSn0Kyh9hpP8IROpS/ROjoEQnz/wat j0cnMVPgjf3hFEb6rwFLgL47W6gZ01nMG2vcAyTgLxZfcway8ZXGFlJ1pC8ik8+u bw69pA+Mr8Kc2C3gM1lnBhrNLRQd9pZq1KkBbgRH+MS3OeuSKlzKqzi5CJEVjw12 Wys8fhaDckq4j55gcw+65eikGLZ55aTER1UNQ+3S910/unz+6NcTc+9+66+7Vx6y GgWgqYOWDXD1LBzSjrgQqc83NEQeIKpTXQ4ZrCOQEfO60B59u44avfnJlY8AsGsX +vLXHScZFoQNZd8dGiFc =AlUa -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2e4f43bc-709a-030a-189e-dfd049573542%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] nm-applet disappeared
Hi, for some reason my nm-applet has disappeared from my system. I tried searching around for the cause of this, and the only causes I could find for Qubes 3 were deletion of the System Tray widget or related to changes in the NetVM template. I'm currently running the default configuration (aside from a few random applications installed in the fedora-23 template) and my System Tray is present. I have tried restarting the nm-applet, which generates a passed through notification that I'm connected to the network but does not display the applet. I'm not sure how long ago it stopped displaying either, I only noticed it because I wanted to change my network configuration and couldn't see the applet. Is there anything else I should try? -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4b10447b-f481-447b-9f1d-ad43eb03ceed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793 )
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2016-06-01 03:47, tnt_bom_...@keemail.me wrote: > well i have already opened this topic in github before long time , > but now andrewdavidwong recommended me to send this topic to users > section:- > > https://github.com/QubesOS/qubes-issues/issues/1745#event-665419288 > > I've experienced this too. If I just wait about 10 seconds, then try to start sys-net again, it always works. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJXTr67AAoJENtN07w5UDAwAMgQALQdF58VO2/RW520IgCx12jc Jc506wDrBXlMHU3Qts3N3eQmKeNMjdJrLLP/ZONNC1az1sI0ssrIVjkT5XO8h2/P b/lY67Qa+9WMQpf8tj0faz6tsnh/tBuUyImEKkpo/389GtAGJAtLrR25cPjDCNXQ /KTFn6/B4VJxwHFxjJjk2yAxtM4VyO5cTOGtkcrJK07SrC7U9722KDOOhLKLv6Ul OtaRR0gA7UG6PghvV2ilUOYEshzEFQXoaeaaL3uHcNVuIFW9eb42rYSrStDPF+tg pox4FXiqG/UZfc9dYZWESYgGItsEwCxHiXZH0zruEaaK8Euea/yNRDHcKh5mwDzs 82O66WmnGvjP2q1YtHlJD1p0TEJma8M0uviLY+sjyi9S6psRBpnX4dAzW5CtKcpw CsEj+wcQYlXWJ+LmAueDICC2NF2zsi9KtGXFRFHBllMFtTYklUGNYm08MUulzdvE G6ZCkXkdJ5kv94d8krax3iQalYxH1dhBoXUhVsqXccVCNUHbbaS9S3G/Lf2g9CBf gCk+dtCMAOexRiK71bZlpSyIQKrYGYGza6vYu6UEUml2r1fRoa8pLI/KmeJicKhd lKcgcjy75eHJwGvylMnoTZ8h8oLm7fvbe6zJvdjBdTtT3qTKHkFLgN3lUahSFqKp fe0ZvgThe7OeqrSSRM/+ =hin+ -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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0d8a0a36-463c-beff-ddd9-3c5db4e8051f%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Error starting VM 'sys-net': Failed to kill old QubesDB instance (PID 1793 )
well i have already opened this topic in github before long time , but now andrewdavidwong recommended me to send this topic to users section:- https://github.com/QubesOS/qubes-issues/issues/1745#event-665419288 -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/KJAZjPX--3-0%40keemail.me. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Does Qubes play well with Computer vision, and ML?
AFAIK you will need to gave 2 GPUs if you want to pass one to VM. On PC you can buy one more GPU, but on laptop that might be a problem. Some laptops have 2 GPUs: one discrete, and one inside a CPU. Still, on some laptops (MSI GT72 for example), there are 2 GPUs, but they can not run simultaneously, only one at a time, what makes GPU passthrough impossible. Btw, I am studing ML and CV for two years, and still never faced a necessity of using GPU. (May be it's just me). If there would be a case, when I will need a GPU, I can walkaround this problem by buying Amazon's virtual server with gpu. -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/38565cfc-4593-4fd9-bdd8-6c4b96192326%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Does Qubes play well with Computer vision, and ML?
i never tried, but you can pass your pci devices to an appvm (e.g. your gpu). https://www.qubes-os.org/doc/assigning-devices/ frameworks will often allow you to use your cpu in case you have no gpu. as long as your models are small enough you can train that on cpu. (but training a big nn (neuronal network, but i guess you know that) will take a long time and cnns (and other deep nns) are big). so passing through your gpu would be the best course of action. (maybe your university provides some pcs with standard dev software and ssh-access. you could try using those.) -john -- 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 post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4f7ed783-52ba-5305-23ed-8ff33f9e8eb7%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
