Re: [qubes-users] OnionShare
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-08 17:44, Unman wrote: > On Mon, Jan 09, 2017 at 01:16:01AM +, Unman wrote: >> On Mon, Jan 09, 2017 at 12:48:58AM -, haxy wrote: On Sun, Jan 08, 2017 at 11:50:37PM -, haxy wrote: >>> On Wed, Jan 04, 2017 at 03:02:48AM +, Unman wrote: On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: >> On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: >>> Does OnionShare work safely in Qubes? >>> >>> Gave it a try with an AppVm based on a qubes-debian template > but wasn't >>> able to get it working. >>> >>> Haven't been able to find any posts in the qubes users or devel forums >>> about this. Did see some discussion on the whonix forum but > that looks >>> to >>> still be in the development stage. >>> >>> Would it be possible using a non-qubes debian or fedora hvm? >>> >>> >> >> You don't say why you weren't able to get it working, or what > steps you >> took to troubleshoot the problem. >> I can confirm that it works fine on a standard Debian appVM. >> >> From your reference to whonix, I suspect that that is your > problem. I >> don't use whonix so cant check this but I believe that > onionshare relies >> on access to a tor control port opened with Tor Browser. I think that >> the whonix design would preclude this. >> >> You can try with a normal qube connected to sys-firewall. You > can't use >> the normal qubes torVM because that doesn't have the control > port open, >> but with some minor modifications you can fix this, and then try > to run >> onionshare there. >> >> I don't believe there are any "safety" issues. >> >> unman > > @ unman: Thanks and you are right. I should have included the > steps > taken to troubleshoot. > > Steps taken: > > 1. Using a cloned qubes-debian template created an AppVM. > 2. Installed onionshare via debian apt-get. > 3. Was able to open onionshare but not able to connect using sys-firewall > as the Net-VM. > 4. Deleted the AppVM, created new AppVM and reinstalled via debian > apt-get. Although onionshare appeared to install properly, onionshare was > not accessable via konsole nor visible in file manager. > 5. Installed in the cloned template with the same results. > > unman quote: I can confirm that it works fine on a standard Debian appVM. > > As I'm unsure, are you referring to an AppVM based on the included qubes > debian template? > > Maybe a problem with the debian repo? Did you install via debian repo or > do a build? > I used a qube based on the standard Debian template. Cloned with git and installed the dependencies, and the TBB. Started the TorBrowser. Ran the onionshare-gui script. Tested the connection to TorBrowser from File-Settings. Shared a file. I'll check using the Debian package. >>> >>> OK, well apart from the huge dependencies pulled in, everything > seemed >>> to work. >>> Created qube based on standard Debian template. >>> Installed the onionshare package with apt-get. >>> Started onionshare-gui from xterm. >>> I had to start TBB - why? The install pulled in tor and started it. >>> Once TBB running and checked, I could share files. >>> >>> In view of your later email I'd suggest testing with a standard TBB. >>> You can follow progress from the term where you started onionshare, > and >>> you should see the connection established to the control port and > then >>> the HS being set up. >>> Obviously you will need to test the TBB is working. >>> >>> unman >>> >>> >>> >> @ unman: Thanks for your help! Onionshare working now. >> Found that "searching" for onionshare after install would only work as >> root. >> >> Also, you were right about testing with standared TBB version. >> Using the hardened version results in: >> >> "Can't connect to Tor control port on port [9051, 9151]. OnionShare >> requires Tor Browser to be running in the background to work. If you > don't >> have it you can get it from https://www.torproject.org/.; >> >> Works with standard TBB. >> >> > > Update. > Works as stated above but the debian repos have old 0.6 version. > > Cloned the latest version, 0.9.2, with git to a
Re: [qubes-users] Re: Fedora Desktop in Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-08 14:57, Patrick Bouldin wrote: > On Sunday, January 8, 2017 at 11:15:56 AM UTC-5, Andrew David Wong wrote: > On 2017-01-07 18:27, Patrick Bouldin wrote: On Saturday, January 7, 2017 at 3:21:42 AM UTC-5, Andrew David Wong wrote: On 2017-01-06 14:37, Patrick Bouldin wrote: >>> On Wednesday, December 28, 2016 at 2:41:28 AM UTC-5, Andrew David >>> Wong wrote: On 2016-12-27 12:39, Patrick Bouldin wrote: >> On Tuesday, December 27, 2016 at 2:13:48 PM UTC-5, Patrick >> Bouldin wrote: >>> On Tuesday, December 27, 2016 at 2:11:04 PM UTC-5, Patrick >>> Bouldin wrote: On Tuesday, December 27, 2016 at 2:04:28 PM UTC-5, Patrick Bouldin wrote: > On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, > Patrick Bouldin wrote: >> Hi, I saw some threads on this but am not clear at a >> high level. >> >> I thought I would install dropbox client on one of my >> Fedora VMs so that working with files is much >> smoother than from a browser. So, is installing a >> Fedora Desktop the best plan to do that? Don't assume >> I know enough of native Qubes ability please - maybe >> I'm missing a key point! >> >> Thanks, Patrick > > Thanks David. housekeeping question - before I started > I copied my Fedora template, just in case. Am I correct > I can easily undo those changes incorrectly made by > deleting the template and renaming the backup template > to the production one (just deleted)? > >>> >>> Yes, that's correct. >>> Sorry, I meant Andrew! >>> >>> >>> No worries. >>> >>> And I see it works so disregard, Andrew - thanks again. >> >> Wow, this is a bear for me. >> >> Dropbox said:Add the following to /etc/yum.conf. >> >> >> name=Dropbox Repository >> baseurl=http://linux.dropbox.com/fedora/\$releasever/ >> gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc >> >> So I performed a sudo gedit on that file and added the above >> three lines. When I saved it I received this: >> >> ** (gedit:1791): WARNING **: Set document metadata failed: >> Setting attribute metadata::gedit-position not supported >> [user@fedora-24 ~]$ >> >> So I do see that you can't save metadata by extending the >> yum.conf file, and tried a few other things that I think it >> was suggesting. >> >>> >>> No, I think that's just a warning message about the gedit program >>> itself. Should be safe to disregard. You can verify that the >>> contents of the file were saved with `cat /etc/yum.conf`. >>> >> When I try and run $ sudo dnf install nautilus-dropbox I get >> this: Last metadata expiration check: 0:14:35 ago on Tue Dec >> 27 15:23:35 2016. No package nautilus-dropbox available. >> Error: Unable to find a match. >> >>> >>> Try this: >>> >>> $ sudo dnf --refresh install nautilus-dropbox >>> >>> If that still doesn't work, try creating a separate repo file, >>> `/etc/yum.repos.d/dropbox.repo`, with this content: >>> >>> [Dropbox] name=Dropbox Repository >>> baseurl=http://linux.dropbox.com/fedora/$releasever/ >>> gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc >>> >>> Then try this again: >>> >>> $ sudo dnf --refresh install nautilus-dropbox >>> >>> >>> Darn, still not working - I noticed this link is not working: >>> baseurl=http://linux.dropbox.com/fedora/\$releasever/ >>> gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc >>> >>> >>> So it's not finding the file, tested that just in my browser >>> address bar. >>> >>> Patrick >>> I wouldn't expect that to work in your browser address bar due to the backslash, but I have to ask: Why not try following the instructions I provided in the previous email (to which you're replying)? Hi Andrew, I did follow them precisely, I just started fumbling around on my own - basically it still says it can't find the file, errors out - just like before - so I was just adding 2+2, figured it was the one I pointed out. So I did try the suggestions, including a special dropbox.repo in the /etc directory, same result. I need this in the fedora-24 template, right? So if I: [user@fedora-24 etc]$ cat dropbox.repo > > It needs to be in /etc/yum.repos.d/ > I get... [Dropbox] name=Dropbox Repository
Re: [qubes-users] OnionShare
On Mon, Jan 09, 2017 at 01:16:01AM +, Unman wrote: > On Mon, Jan 09, 2017 at 12:48:58AM -, haxy wrote: > > > On Sun, Jan 08, 2017 at 11:50:37PM -, haxy wrote: > > >> >> On Wed, Jan 04, 2017 at 03:02:48AM +, Unman wrote: > > >> >>> On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: > > >> >>> > > On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: > > >> >>> > >> Does OnionShare work safely in Qubes? > > >> >>> > >> > > >> >>> > >> Gave it a try with an AppVm based on a qubes-debian template > > >> but > > >> >>> wasn't > > >> >>> > >> able to get it working. > > >> >>> > >> > > >> >>> > >> Haven't been able to find any posts in the qubes users or devel > > >> >>> forums > > >> >>> > >> about this. Did see some discussion on the whonix forum but > > >> that > > >> >>> looks > > >> >>> > >> to > > >> >>> > >> still be in the development stage. > > >> >>> > >> > > >> >>> > >> Would it be possible using a non-qubes debian or fedora hvm? > > >> >>> > >> > > >> >>> > >> > > >> >>> > > > > >> >>> > > You don't say why you weren't able to get it working, or what > > >> steps > > >> >>> you > > >> >>> > > took to troubleshoot the problem. > > >> >>> > > I can confirm that it works fine on a standard Debian appVM. > > >> >>> > > > > >> >>> > > From your reference to whonix, I suspect that that is your > > >> problem. > > >> >>> I > > >> >>> > > don't use whonix so cant check this but I believe that > > >> onionshare > > >> >>> relies > > >> >>> > > on access to a tor control port opened with Tor Browser. I think > > >> >>> that > > >> >>> > > the whonix design would preclude this. > > >> >>> > > > > >> >>> > > You can try with a normal qube connected to sys-firewall. You > > >> can't > > >> >>> use > > >> >>> > > the normal qubes torVM because that doesn't have the control > > >> port > > >> >>> open, > > >> >>> > > but with some minor modifications you can fix this, and then try > > >> to > > >> >>> run > > >> >>> > > onionshare there. > > >> >>> > > > > >> >>> > > I don't believe there are any "safety" issues. > > >> >>> > > > > >> >>> > > unman > > >> >>> > > > >> >>> > @ unman: Thanks and you are right. I should have included the > > >> steps > > >> >>> > taken to troubleshoot. > > >> >>> > > > >> >>> > Steps taken: > > >> >>> > > > >> >>> > 1. Using a cloned qubes-debian template created an AppVM. > > >> >>> > 2. Installed onionshare via debian apt-get. > > >> >>> > 3. Was able to open onionshare but not able to connect using > > >> >>> sys-firewall > > >> >>> > as the Net-VM. > > >> >>> > 4. Deleted the AppVM, created new AppVM and reinstalled via debian > > >> >>> > apt-get. Although onionshare appeared to install properly, > > >> >>> onionshare > > >> >>> was > > >> >>> > not accessable via konsole nor visible in file manager. > > >> >>> > 5. Installed in the cloned template with the same results. > > >> >>> > > > >> >>> > unman quote: I can confirm that it works fine on a standard Debian > > >> >>> appVM. > > >> >>> > > > >> >>> > As I'm unsure, are you referring to an AppVM based on the included > > >> >>> qubes > > >> >>> > debian template? > > >> >>> > > > >> >>> > Maybe a problem with the debian repo? Did you install via debian > > >> >>> repo > > >> >>> or > > >> >>> > do a build? > > >> >>> > > > >> >>> > > >> >>> I used a qube based on the standard Debian template. > > >> >>> Cloned with git and installed the dependencies, and the TBB. > > >> >>> Started the TorBrowser. > > >> >>> Ran the onionshare-gui script. > > >> >>> Tested the connection to TorBrowser from File-Settings. > > >> >>> Shared a file. > > >> >>> > > >> >>> I'll check using the Debian package. > > >> >>> > > >> >> > > >> >> OK, well apart from the huge dependencies pulled in, everything > > >> seemed > > >> >> to work. > > >> >> Created qube based on standard Debian template. > > >> >> Installed the onionshare package with apt-get. > > >> >> Started onionshare-gui from xterm. > > >> >> I had to start TBB - why? The install pulled in tor and started it. > > >> >> Once TBB running and checked, I could share files. > > >> >> > > >> >> In view of your later email I'd suggest testing with a standard TBB. > > >> >> You can follow progress from the term where you started onionshare, > > >> and > > >> >> you should see the connection established to the control port and > > >> then > > >> >> the HS being set up. > > >> >> Obviously you will need to test the TBB is working. > > >> >> > > >> >> unman > > >> >> > > >> >> > > >> >> > > >> > @ unman: Thanks for your help! Onionshare working now. > > >> > Found that "searching" for onionshare after install would only work as > > >> > root. > > >> > > > >> > Also, you were right about testing with standared TBB version. > > >> > Using the hardened version results in: > > >> > > > >> > "Can't connect to Tor control port on port [9051, 9151]. OnionShare > > >> > requires Tor Browser to be running in the background to work. If you > > >> don't > > >> > have it you can get it
Re: [qubes-users] OnionShare
On Sun, Jan 08, 2017 at 11:50:37PM -, haxy wrote: > >> On Wed, Jan 04, 2017 at 03:02:48AM +, Unman wrote: > >>> On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: > >>> > > On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: > >>> > >> Does OnionShare work safely in Qubes? > >>> > >> > >>> > >> Gave it a try with an AppVm based on a qubes-debian template but > >>> wasn't > >>> > >> able to get it working. > >>> > >> > >>> > >> Haven't been able to find any posts in the qubes users or devel > >>> forums > >>> > >> about this. Did see some discussion on the whonix forum but that > >>> looks > >>> > >> to > >>> > >> still be in the development stage. > >>> > >> > >>> > >> Would it be possible using a non-qubes debian or fedora hvm? > >>> > >> > >>> > >> > >>> > > > >>> > > You don't say why you weren't able to get it working, or what steps > >>> you > >>> > > took to troubleshoot the problem. > >>> > > I can confirm that it works fine on a standard Debian appVM. > >>> > > > >>> > > From your reference to whonix, I suspect that that is your problem. > >>> I > >>> > > don't use whonix so cant check this but I believe that onionshare > >>> relies > >>> > > on access to a tor control port opened with Tor Browser. I think > >>> that > >>> > > the whonix design would preclude this. > >>> > > > >>> > > You can try with a normal qube connected to sys-firewall. You can't > >>> use > >>> > > the normal qubes torVM because that doesn't have the control port > >>> open, > >>> > > but with some minor modifications you can fix this, and then try to > >>> run > >>> > > onionshare there. > >>> > > > >>> > > I don't believe there are any "safety" issues. > >>> > > > >>> > > unman > >>> > > >>> > @ unman: Thanks and you are right. I should have included the steps > >>> > taken to troubleshoot. > >>> > > >>> > Steps taken: > >>> > > >>> > 1. Using a cloned qubes-debian template created an AppVM. > >>> > 2. Installed onionshare via debian apt-get. > >>> > 3. Was able to open onionshare but not able to connect using > >>> sys-firewall > >>> > as the Net-VM. > >>> > 4. Deleted the AppVM, created new AppVM and reinstalled via debian > >>> > apt-get. Although onionshare appeared to install properly, > >>> onionshare > >>> was > >>> > not accessable via konsole nor visible in file manager. > >>> > 5. Installed in the cloned template with the same results. > >>> > > >>> > unman quote: I can confirm that it works fine on a standard Debian > >>> appVM. > >>> > > >>> > As I'm unsure, are you referring to an AppVM based on the included > >>> qubes > >>> > debian template? > >>> > > >>> > Maybe a problem with the debian repo? Did you install via debian > >>> repo > >>> or > >>> > do a build? > >>> > > >>> > >>> I used a qube based on the standard Debian template. > >>> Cloned with git and installed the dependencies, and the TBB. > >>> Started the TorBrowser. > >>> Ran the onionshare-gui script. > >>> Tested the connection to TorBrowser from File-Settings. > >>> Shared a file. > >>> > >>> I'll check using the Debian package. > >>> > >> > >> OK, well apart from the huge dependencies pulled in, everything seemed > >> to work. > >> Created qube based on standard Debian template. > >> Installed the onionshare package with apt-get. > >> Started onionshare-gui from xterm. > >> I had to start TBB - why? The install pulled in tor and started it. > >> Once TBB running and checked, I could share files. > >> > >> In view of your later email I'd suggest testing with a standard TBB. > >> You can follow progress from the term where you started onionshare, and > >> you should see the connection established to the control port and then > >> the HS being set up. > >> Obviously you will need to test the TBB is working. > >> > >> unman > >> > >> > >> > > @ unman: Thanks for your help! Onionshare working now. > > Found that "searching" for onionshare after install would only work as > > root. > > > > Also, you were right about testing with standared TBB version. > > Using the hardened version results in: > > > > "Can't connect to Tor control port on port [9051, 9151]. OnionShare > > requires Tor Browser to be running in the background to work. If you don't > > have it you can get it from https://www.torproject.org/.; > > > > Works with standard TBB. > > > > > > Update. > Works as stated above but the debian repos have old 0.6 version. > > Cloned the latest version, 0.9.2, with git to a new cloned TemplateVM and > installed per instructions at > "https://github.com/micahflee/onionshare/blob/master/BUILD.md#gnulinux;. > > Created new AppVm based on the TemplateVM with new build but Onionshare > does not function and there are no onionshare files in the AppVm. > > It does however run fine in the TemplateVM. > > I'm at a loss as to why the AppVM based upon the template built with git > clone doesn't work while the AppVM based upon the debian repo onionshare > installed template does. > > What have I missed? I would bet that you cloned in
Re: [qubes-users] Built the software in TemplateVM from source and installed => it doesn't appear in TemplateBasedVM?
> Thank you for replying, Angel. Yes I restarted a computer after installing > this software from source, so that included restarting all the VM's. But, a > wonderful thing happened: I've done a few more reboots since the time of > writing, right now checked again: everything is OK, new executable files are > seen by TemplateBasedVMs! Not sure why it didn't happen earlier, after the > first reboot... Could there be some delay in refresh/update of root > filesystem (e.g. /usr/sbin/ directory), even if I reboot QubesOS ? Just > trying to find the explanation for that mystery... Next time you could try issuing the following command and see if that helps. qvm-sync-appmenus vmname -- 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/abdde46b-5a4b-41c4-a551-b9eaac880204%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Built the software in TemplateVM from source and installed => it doesn't appear in TemplateBasedVM?
On Sunday, January 8, 2017 at 11:15:09 PM UTC, qmast...@gmail.com wrote: > понедельник, 9 января 2017 г., 0:32:26 UTC+3 пользователь Ángel написал: > > qmaster...@gmail.com wrote: > > > Please tell, how can I enable sharing the > > > compiled-and-installed-from-source software with the TemplateBasedVM's ? > > > Or it is discouraged by Qubes to compile the software by yourself? > > > > It should be working: > > * Place the files in the TemplateVM (somewhere different than /home > > or /usr/local). > > * Power down the Template > > * (Re)start the VM based on that template > > > > Are you sure that the VM is based on the template that you customized? > > Thank you for replying, Angel. Yes I restarted a computer after installing > this software from source, so that included restarting all the VM's. But, a > wonderful thing happened: I've done a few more reboots since the time of > writing, right now checked again: everything is OK, new executable files are > seen by TemplateBasedVMs! Not sure why it didn't happen earlier, after the > first reboot... Could there be some delay in refresh/update of root > filesystem (e.g. /usr/sbin/ directory), even if I reboot QubesOS ? Just > trying to find the explanation for that mystery... Next time you could try issuing the following command and see if that helps. qvm-sync-appmenus vmname -- 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/7b05a753-c2dd-4976-9d86-dee3e68adfa8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora Desktop in Qubes
On Sunday, January 8, 2017 at 10:57:15 PM UTC, Patrick Bouldin wrote: > On Sunday, January 8, 2017 at 11:15:56 AM UTC-5, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > On 2017-01-07 18:27, Patrick Bouldin wrote: > > > On Saturday, January 7, 2017 at 3:21:42 AM UTC-5, Andrew David Wong wrote: > > > On 2017-01-06 14:37, Patrick Bouldin wrote: > > On Wednesday, December 28, 2016 at 2:41:28 AM UTC-5, Andrew David > > Wong wrote: On 2016-12-27 12:39, Patrick Bouldin wrote: > > >>> On Tuesday, December 27, 2016 at 2:13:48 PM UTC-5, Patrick > > >>> Bouldin wrote: > > On Tuesday, December 27, 2016 at 2:11:04 PM UTC-5, Patrick > > Bouldin wrote: > > > On Tuesday, December 27, 2016 at 2:04:28 PM UTC-5, > > > Patrick Bouldin wrote: > > >> On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, > > >> Patrick Bouldin wrote: > > >>> Hi, I saw some threads on this but am not clear at a > > >>> high level. > > >>> > > >>> I thought I would install dropbox client on one of my > > >>> Fedora VMs so that working with files is much > > >>> smoother than from a browser. So, is installing a > > >>> Fedora Desktop the best plan to do that? Don't assume > > >>> I know enough of native Qubes ability please - maybe > > >>> I'm missing a key point! > > >>> > > >>> Thanks, Patrick > > >> > > >> Thanks David. housekeeping question - before I started > > >> I copied my Fedora template, just in case. Am I correct > > >> I can easily undo those changes incorrectly made by > > >> deleting the template and renaming the backup template > > >> to the production one (just deleted)? > > >> > > > > Yes, that's correct. > > > > > > > > Sorry, I meant Andrew! > > > > > > No worries. > > > > And I see it works so disregard, Andrew - thanks again. > > >>> > > >>> Wow, this is a bear for me. > > >>> > > >>> Dropbox said:Add the following to /etc/yum.conf. > > >>> > > >>> > > >>> name=Dropbox Repository > > >>> baseurl=http://linux.dropbox.com/fedora/\$releasever/ > > >>> gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc > > >>> > > >>> So I performed a sudo gedit on that file and added the above > > >>> three lines. When I saved it I received this: > > >>> > > >>> ** (gedit:1791): WARNING **: Set document metadata failed: > > >>> Setting attribute metadata::gedit-position not supported > > >>> [user@fedora-24 ~]$ > > >>> > > >>> So I do see that you can't save metadata by extending the > > >>> yum.conf file, and tried a few other things that I think it > > >>> was suggesting. > > >>> > > > > No, I think that's just a warning message about the gedit program > > itself. Should be safe to disregard. You can verify that the > > contents of the file were saved with `cat /etc/yum.conf`. > > > > >>> When I try and run $ sudo dnf install nautilus-dropbox I get > > >>> this: Last metadata expiration check: 0:14:35 ago on Tue Dec > > >>> 27 15:23:35 2016. No package nautilus-dropbox available. > > >>> Error: Unable to find a match. > > >>> > > > > Try this: > > > > $ sudo dnf --refresh install nautilus-dropbox > > > > If that still doesn't work, try creating a separate repo file, > > `/etc/yum.repos.d/dropbox.repo`, with this content: > > > > [Dropbox] name=Dropbox Repository > > baseurl=http://linux.dropbox.com/fedora/$releasever/ > > gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc > > > > Then try this again: > > > > $ sudo dnf --refresh install nautilus-dropbox > > > > > > Darn, still not working - I noticed this link is not working: > > baseurl=http://linux.dropbox.com/fedora/\$releasever/ > > gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc > > > > > > So it's not finding the file, tested that just in my browser > > address bar. > > > > Patrick > > > > > > > > I wouldn't expect that to work in your browser address bar due to the > > > backslash, but I have to ask: Why not try following the instructions I > > > provided in the previous email (to which you're replying)? > > > > > > Hi Andrew, I did follow them precisely, I just started fumbling around on > > > my own - basically it still says it can't find the file, errors out - > > > just like before - so I was just adding 2+2, figured it was the one I > > > pointed out. So I did try the suggestions, including a special > > > dropbox.repo in the /etc directory, same result. I need this in the > > > fedora-24 template, right? > > > > > > So if I: > > > [user@fedora-24 etc]$ cat dropbox.repo
Re: [qubes-users] OnionShare
>> On Wed, Jan 04, 2017 at 03:02:48AM +, Unman wrote: >>> On Wed, Jan 04, 2017 at 12:39:39AM -, haxy wrote: >>> > > On Mon, Jan 02, 2017 at 11:35:22PM -, haxy wrote: >>> > >> Does OnionShare work safely in Qubes? >>> > >> >>> > >> Gave it a try with an AppVm based on a qubes-debian template but >>> wasn't >>> > >> able to get it working. >>> > >> >>> > >> Haven't been able to find any posts in the qubes users or devel >>> forums >>> > >> about this. Did see some discussion on the whonix forum but that >>> looks >>> > >> to >>> > >> still be in the development stage. >>> > >> >>> > >> Would it be possible using a non-qubes debian or fedora hvm? >>> > >> >>> > >> >>> > > >>> > > You don't say why you weren't able to get it working, or what steps >>> you >>> > > took to troubleshoot the problem. >>> > > I can confirm that it works fine on a standard Debian appVM. >>> > > >>> > > From your reference to whonix, I suspect that that is your problem. >>> I >>> > > don't use whonix so cant check this but I believe that onionshare >>> relies >>> > > on access to a tor control port opened with Tor Browser. I think >>> that >>> > > the whonix design would preclude this. >>> > > >>> > > You can try with a normal qube connected to sys-firewall. You can't >>> use >>> > > the normal qubes torVM because that doesn't have the control port >>> open, >>> > > but with some minor modifications you can fix this, and then try to >>> run >>> > > onionshare there. >>> > > >>> > > I don't believe there are any "safety" issues. >>> > > >>> > > unman >>> > >>> > @ unman: Thanks and you are right. I should have included the steps >>> > taken to troubleshoot. >>> > >>> > Steps taken: >>> > >>> > 1. Using a cloned qubes-debian template created an AppVM. >>> > 2. Installed onionshare via debian apt-get. >>> > 3. Was able to open onionshare but not able to connect using >>> sys-firewall >>> > as the Net-VM. >>> > 4. Deleted the AppVM, created new AppVM and reinstalled via debian >>> > apt-get. Although onionshare appeared to install properly, >>> onionshare >>> was >>> > not accessable via konsole nor visible in file manager. >>> > 5. Installed in the cloned template with the same results. >>> > >>> > unman quote: I can confirm that it works fine on a standard Debian >>> appVM. >>> > >>> > As I'm unsure, are you referring to an AppVM based on the included >>> qubes >>> > debian template? >>> > >>> > Maybe a problem with the debian repo? Did you install via debian >>> repo >>> or >>> > do a build? >>> > >>> >>> I used a qube based on the standard Debian template. >>> Cloned with git and installed the dependencies, and the TBB. >>> Started the TorBrowser. >>> Ran the onionshare-gui script. >>> Tested the connection to TorBrowser from File-Settings. >>> Shared a file. >>> >>> I'll check using the Debian package. >>> >> >> OK, well apart from the huge dependencies pulled in, everything seemed >> to work. >> Created qube based on standard Debian template. >> Installed the onionshare package with apt-get. >> Started onionshare-gui from xterm. >> I had to start TBB - why? The install pulled in tor and started it. >> Once TBB running and checked, I could share files. >> >> In view of your later email I'd suggest testing with a standard TBB. >> You can follow progress from the term where you started onionshare, and >> you should see the connection established to the control port and then >> the HS being set up. >> Obviously you will need to test the TBB is working. >> >> unman >> >> >> > @ unman: Thanks for your help! Onionshare working now. > Found that "searching" for onionshare after install would only work as > root. > > Also, you were right about testing with standared TBB version. > Using the hardened version results in: > > "Can't connect to Tor control port on port [9051, 9151]. OnionShare > requires Tor Browser to be running in the background to work. If you don't > have it you can get it from https://www.torproject.org/.; > > Works with standard TBB. > > Update. Works as stated above but the debian repos have old 0.6 version. Cloned the latest version, 0.9.2, with git to a new cloned TemplateVM and installed per instructions at "https://github.com/micahflee/onionshare/blob/master/BUILD.md#gnulinux;. Created new AppVm based on the TemplateVM with new build but Onionshare does not function and there are no onionshare files in the AppVm. It does however run fine in the TemplateVM. I'm at a loss as to why the AppVM based upon the template built with git clone doesn't work while the AppVM based upon the debian repo onionshare installed template does. What have I missed? -- 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
[qubes-users] Re: Can NOT get Broadcom BCM43602 Wifi Card working , DELL XPS 15 9950- Qubes sys-net freezes/ crashes
On Wednesday, August 3, 2016 at 3:05:01 PM UTC+1, Michael wrote: > Have a Broadcom BCM43602 Wifi Card in my dell xps 15 9950 > > and I downloaded Qubes Release 3.2-rc2 > > Problem: I can not connect to the internet cause my wifi card is not working > with qubes: > "If BCM43602, the wireless card is disabled in BIOS, installation succeeds, > and afterwards it's possible to re-enable BCM43602 in BIOS and boot Qubes. > However, subsecuantly adding BCM43602 device to the sys-netvm freezes the > computer." > > -my boot setup has > VT and VT-d options activated > > > how can I make my network function ? I replaced the wifi card in my XPS 9550 with an Intel 8265 and updated the fedora 23 template to the kernel from the unstable repository. Wifi now works very well (as well as everything else it seems). -- 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/eb4a7a8e-a034-400b-b7ac-dc12b2f2cc0b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Kali VM is unusable
On Tuesday, January 3, 2017 at 8:54:27 PM UTC-8, involunta...@airmail.cc wrote: > I have a Kali VM (installed in a new vm via iso). 90% of the screen is > gray. The Kali top bar appears at the bottom of the screen, and most of > the desktop is not even onscreen. Has anyone else encountered this? Yes, I was able to reproduce this. No idea on a solution, 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/067b36b4-f1fe-45ee-aed4-c62bd552788a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: compose key
Daniel Moerner wrote: > On 01/08/2017 04:14 PM, haaber wrote: > > Thank you. Doing this, I have compose key in dom0, but not in any > > other domain. Do I miss something? Bernhard > > Hi, > > Please remember to reply to the list as well. For me, using Left Win, > this setting sets the compose key for all VMs and dom0. I'm confused > that you're seeing different behavior, and not sure why that would be > the case. > > Daniel Maybe it doesn't apply to already-running VMs? I performed a simple test with xmodmap and it didn't affect other VMs. As each VM uses its own Xorg, I'm unsure about how these systemwide changes to input devices are supposed to be configured. -- 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/1483917371.2514.8.camel%4016bits.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Built the software in TemplateVM from source and installed => it doesn't appear in TemplateBasedVM?
понедельник, 9 января 2017 г., 0:32:26 UTC+3 пользователь Ángel написал: > qmaster...@gmail.com wrote: > > Please tell, how can I enable sharing the > > compiled-and-installed-from-source software with the TemplateBasedVM's ? Or > > it is discouraged by Qubes to compile the software by yourself? > > It should be working: > * Place the files in the TemplateVM (somewhere different than /home > or /usr/local). > * Power down the Template > * (Re)start the VM based on that template > > Are you sure that the VM is based on the template that you customized? Thank you for replying, Angel. Yes I restarted a computer after installing this software from source, so that included restarting all the VM's. But, a wonderful thing happened: I've done a few more reboots since the time of writing, right now checked again: everything is OK, new executable files are seen by TemplateBasedVMs! Not sure why it didn't happen earlier, after the first reboot... Could there be some delay in refresh/update of root filesystem (e.g. /usr/sbin/ directory), even if I reboot QubesOS ? Just trying to find the explanation for that mystery... -- 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/11ff355a-1d10-45a2-96a2-260c3353fab5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora Desktop in Qubes
On Sunday, January 8, 2017 at 11:15:56 AM UTC-5, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-01-07 18:27, Patrick Bouldin wrote: > > On Saturday, January 7, 2017 at 3:21:42 AM UTC-5, Andrew David Wong wrote: > > On 2017-01-06 14:37, Patrick Bouldin wrote: > On Wednesday, December 28, 2016 at 2:41:28 AM UTC-5, Andrew David > Wong wrote: On 2016-12-27 12:39, Patrick Bouldin wrote: > >>> On Tuesday, December 27, 2016 at 2:13:48 PM UTC-5, Patrick > >>> Bouldin wrote: > On Tuesday, December 27, 2016 at 2:11:04 PM UTC-5, Patrick > Bouldin wrote: > > On Tuesday, December 27, 2016 at 2:04:28 PM UTC-5, > > Patrick Bouldin wrote: > >> On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, > >> Patrick Bouldin wrote: > >>> Hi, I saw some threads on this but am not clear at a > >>> high level. > >>> > >>> I thought I would install dropbox client on one of my > >>> Fedora VMs so that working with files is much > >>> smoother than from a browser. So, is installing a > >>> Fedora Desktop the best plan to do that? Don't assume > >>> I know enough of native Qubes ability please - maybe > >>> I'm missing a key point! > >>> > >>> Thanks, Patrick > >> > >> Thanks David. housekeeping question - before I started > >> I copied my Fedora template, just in case. Am I correct > >> I can easily undo those changes incorrectly made by > >> deleting the template and renaming the backup template > >> to the production one (just deleted)? > >> > > Yes, that's correct. > > > > > Sorry, I meant Andrew! > > > No worries. > > And I see it works so disregard, Andrew - thanks again. > >>> > >>> Wow, this is a bear for me. > >>> > >>> Dropbox said:Add the following to /etc/yum.conf. > >>> > >>> > >>> name=Dropbox Repository > >>> baseurl=http://linux.dropbox.com/fedora/\$releasever/ > >>> gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc > >>> > >>> So I performed a sudo gedit on that file and added the above > >>> three lines. When I saved it I received this: > >>> > >>> ** (gedit:1791): WARNING **: Set document metadata failed: > >>> Setting attribute metadata::gedit-position not supported > >>> [user@fedora-24 ~]$ > >>> > >>> So I do see that you can't save metadata by extending the > >>> yum.conf file, and tried a few other things that I think it > >>> was suggesting. > >>> > > No, I think that's just a warning message about the gedit program > itself. Should be safe to disregard. You can verify that the > contents of the file were saved with `cat /etc/yum.conf`. > > >>> When I try and run $ sudo dnf install nautilus-dropbox I get > >>> this: Last metadata expiration check: 0:14:35 ago on Tue Dec > >>> 27 15:23:35 2016. No package nautilus-dropbox available. > >>> Error: Unable to find a match. > >>> > > Try this: > > $ sudo dnf --refresh install nautilus-dropbox > > If that still doesn't work, try creating a separate repo file, > `/etc/yum.repos.d/dropbox.repo`, with this content: > > [Dropbox] name=Dropbox Repository > baseurl=http://linux.dropbox.com/fedora/$releasever/ > gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc > > Then try this again: > > $ sudo dnf --refresh install nautilus-dropbox > > > Darn, still not working - I noticed this link is not working: > baseurl=http://linux.dropbox.com/fedora/\$releasever/ > gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc > > > So it's not finding the file, tested that just in my browser > address bar. > > Patrick > > > > > I wouldn't expect that to work in your browser address bar due to the > > backslash, but I have to ask: Why not try following the instructions I > > provided in the previous email (to which you're replying)? > > > > Hi Andrew, I did follow them precisely, I just started fumbling around on > > my own - basically it still says it can't find the file, errors out - just > > like before - so I was just adding 2+2, figured it was the one I pointed > > out. So I did try the suggestions, including a special dropbox.repo in the > > /etc directory, same result. I need this in the fedora-24 template, right? > > > > So if I: > > [user@fedora-24 etc]$ cat dropbox.repo > > > > It needs to be in /etc/yum.repos.d/ > > > I get... > > > > [Dropbox] name=Dropbox Repository > > baseurl=http://linux.dropbox.com/fedora/$releasever/ > > gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc > > > > Then when I run > > [user@fedora-24 etc]$ sudo dnf --refresh install
[qubes-users] Re: Qubes 3.2 - TeamViewer not connecting
On Friday, October 28, 2016 at 5:40:25 PM UTC-7, Vincent Elliott wrote: > Hi, > > Am very new to Qubes OS and am trying to get TeamViewer v11 working. The > problem is it will not connect and is requesting proxy settings. > > Anyone had any success with this? > > Vincent See Alex's solution here: https://groups.google.com/d/msg/qubes-users/ZRcDRHIhPLE/WQcLoAHIPAAJ I avoided the TVsetup step by first installing the RPM to the template to provide the dependencies. Then the TAR version of TeamViewer can execute without any issues. Note, this is less than ideal, since the RPM version seems to install a persistent teamviewer daemon onto the system, which may be less than trustworthy. At some point I would like to write a RPM that grabs all the dependencies and installs teamviewer in a safer mode. -- 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/6dc6a958-6aa5-43b6-a7e7-0461aba5fffe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: compose key
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 01/08/2017 04:14 PM, haaber wrote: > Thank you. Doing this, I have compose key in dom0, but not in any > other domain. Do I miss something? Bernhard Hi, Please remember to reply to the list as well. For me, using Left Win, this setting sets the compose key for all VMs and dom0. I'm confused that you're seeing different behavior, and not sure why that would be the case. Daniel -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIwBAEBCAAaBQJYcsLBExxkbW9lcm5lckBnbWFpbC5jb20ACgkQyz0BTtfxsyqO KhAAnAic/kT/cYiXoyPhPuNX7gBdYizElx7fKabax4SlcB1nr5ASBO8EheBz7ThM AoSOYgQgbfgtJQsMfd44/b3NiI0PO8lWPKwLWEFvoU5osbPhg0EFvmqW+EAsZ/yz aeWzbzpwovAj39bicUWa1XLyaZ2bEOY5MykzULJ2P9BVNq4C25ScKmJ5BfxGc+r5 noNTeVO8+xm4KSde3GghJPmkNSygmzgX6lqk97dZcJR/kjAd6vLiEiTWClr6jehQ WvQw/7scDlJWefAEG8Hf29krxPb+Ckgy7C3uqI2igBxURWeXt4cU47Of0P6SgYGx +iR1te3teDGeDEJTXU+/wq1v/x4ioXjSi6YIpQ3Paxs0BYLmnq8eagwh7AbLrrdU iwo+L3p8QjRUjvPf9VyIGsnEdCCU+4y4Dql8WSeQbBF6xI2MxUJcI/ivHs8x+96t reL6MKbpsW9ihkmUbbT1ZIMEPBfsHwuM2gdyBibr8xzwUySKqA3qzOPDAouFxo50 8cQcK3U5e+0zIZ+VpeqZWEQvbZL8enCaJZY0SUjEJbCm6ccpMAiesRd0Y0I6Vg7C UMOix7QSENwKVpcFpY0g7GKFcCscU9TvViUvGOY1xdVgYa8yVDLqISyXCu1+rxOL uYDKNNZJzYkYGXMpUBNxRnhLKLwBgn8YThPkdOrfAJV0z84= =sUES -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/900ba17c-892f-e355-72af-63d25abba231%40gmail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell XPS 15 9550
In original configuration this laptop suffers from freeze on initial boot when the system attaches the broadcom wifi card to sys-net. To make progress needed to disable the wifi card in BIOS, install was then straightforward. Used an USB wifi for initial investigation/updates. Needed to assign the USB controller to the sys-net VM and allow non strict pci reset. ThenuUpgraded the fedora23 kernel to the version in unstable repository: Linux sys-net 4.8.12-12.pvops.qubes.x86_64 #1 SMP Sat Dec 3 19:12:54 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux As there is only one USB controller on this board, this is not a great long-term solution. I then replaced the broadcom wifi card with an Intel 8265 which works very well with the 4.8 v kernel. Generally everything now seems to work well: suspend works, touchpad works well, screen dimming, attaching usb storage. No touchscreen on this model so can't comment on that. -- 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/7f12f377-2809-4910-bffa-375228ed249d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-XPS_15_9550-20170108-222328.yml Description: Binary data
Re: [qubes-users] Built the software in TemplateVM from source and installed => it doesn't appear in TemplateBasedVM?
qmaster...@gmail.com wrote: > Please tell, how can I enable sharing the compiled-and-installed-from-source > software with the TemplateBasedVM's ? Or it is discouraged by Qubes to > compile the software by yourself? It should be working: * Place the files in the TemplateVM (somewhere different than /home or /usr/local). * Power down the Template * (Re)start the VM based on that template Are you sure that the VM is based on the template that you customized? -- 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/1483911139.2514.4.camel%4016bits.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Archlinux template instruction leads to failed recipe on target "core-agent-linux-vm"
Marek Marczykowski-Górecki wrote: > Fixes for both issues already merged: > https://github.com/QubesOS/qubes-app-linux-split-gpg/pull/7 > https://github.com/QubesOS/qubes-core-agent-linux/pull/32 > > Thanks Nicklaus! Is there a flag so that qubes-builder picks the master branch instead of the last release? -- 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/1483909359.1281.1.camel%4016bits.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Galvanic Switch for Mic and Speakers?
On 01/08/2017 08:25 PM, 98'1093481'029348'1092438'0914328 wrote: > Hello, > > perhaps an galvanic switch is not only useful for the Mic (and a > shutter for the cam), but also for the speakers... > > https://www.bleepingcomputer.com/news/security/ultrasound-tracking-could-be-used-to-deanonymize-tor-users/ Hardly a "new" piece of news: that's why airgapped computers typically don't have either microphones nor speakers. As an example, here's what our Rutkowska did to her iphone in 2014: https://twitter.com/rootkovska/status/547496843291410432 (the iphone is used via a bluetooth headset that can be switched off with 100% security) -- Alex -- 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/3b17f089-39d2-eb96-6078-ef6f9917e1cf%40gmx.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Galvanic Switch for Mic and Speakers?
Hello, perhaps an galvanic switch is not only useful for the Mic (and a shutter for the cam), but also for the speakers... https://www.bleepingcomputer.com/news/security/ultrasound-tracking-could-be-used-to-deanonymize-tor-users/ 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/436ae2f8-05fd-449a-a985-dc26dd589b64%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: compose key
On Sunday, January 8, 2017 at 12:49:33 PM UTC-5, haaber wrote: > Hello, > > for foreign languages (accents, etc) I used to have a compose key > configured. I have no idea how to do this within qubes. Has anyone > had/solven this problem already? Thank you! Bernhard You just use the normal XFCE tools: Menu -> System Tools -> Keyboard. Then under "Layout" you can pick the compose key. -- 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/769e6fad-9e6f-4741-b9ee-08ac6ec7f613%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Disable Intel ME
This article may help some Users who wish to disable INTEL ME https://hackaday.com/tag/intel-me -- Securely sent with Tutanota. Claim your encrypted mailbox today! https://tutanota.com -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/K_zIAq9--3-0%40tutanota.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Built the software in TemplateVM from source and installed => it doesn't appear in TemplateBasedVM?
I wanted to get the latest implementation of exFAT (fuse-exfat + exfat-utils).
These packages are not available by default, to get them you could use RPM
Fusion repository which I didn't wanted. So I just git clone'd the official
exFAT github repository (https://github.com/relan/exfat), tar'ed it, copied the
tar archive to TemplateVM fedora-23, then boot to TemplateVM & untar'ed,
installed all the dependencies listed at at GitHub page, and finally installed
exFAT a traditional Linux way: autoreconf --install , ./configure --prefix=/usr
, make , sudo make install
After compiling from source and installing this software, I got
/usr/sbin/mount.exfat ELF file which could be successfully executed by root -
sudo mount.exfat ... However, even after completely rebooting QubesOS R3.2 ,
while I could see these installed binaries in TemplateVM ("fedora-23") - I
can't see them in TemplateBasedVM (such as "personal"). Meanwhile, the software
which I installed through a package manager (such as gcc) - is available to
both parties. This is strange for me, because I've thought that TemplateVM
shares its' root filesystem with TemplateBasedVM's - and, as result, all the
software should be available to TemplateBasedVM regardless of its' way of
installation
Please tell, how can I enable sharing the compiled-and-installed-from-source
software with the TemplateBasedVM's ? Or it is discouraged by Qubes to compile
the software by yourself?
--
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/04cbef64-c3a0-453e-9f78-5477cfa55d0c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[qubes-users] compose key
Hello, for foreign languages (accents, etc) I used to have a compose key configured. I have no idea how to do this within qubes. Has anyone had/solven this problem already? Thank you! Bernhard -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/04509dfa-50dc-b285-ac6b-16d7ec342360%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)
On Sunday, January 8, 2017 at 11:07:55 AM UTC+3, Foppe de Haan wrote: > On Sunday, January 8, 2017 at 1:36:37 AM UTC+1, daltong defourne wrote: > > On Monday, December 19, 2016 at 1:33:23 AM UTC+3, Mathew Evans wrote: > > > Just to update. > > > > > > I am currently running Nvidia drivers without a issue. > > > > > > dom0 Kernel: 4.4.31-11 > > > Nvidia: 375.20 > > > Kernel-module: compiled in dom0; > > > > > > Quick Guide: > > > 1. dom0: qubes-dom0-update install gcc devel-kernel ksmod linux-headers > > > 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) > > > 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > > > > NVIDIA.run > > > 4. dom0: ./NVIDIA.run --ui=none --no-x-check --keep --extract-only > > > 5: dom0: cp NVIDIA-*/kernel/; IGNORE_XEN_PRESENCE=y CC="gcc > > > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM" make module; > > > 6: dom0: cp nvidia.ko /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/. > > > 7: dom0: depmod -a; modinfo nvidia (all working will show up fine) > > > 8: dom0: EDIT GRUB or EFI; add rd.driver.blacklist=nouveau > > > 9: dom0; reboot and enjoy nvidia support. > > > > > > additional: you can install nvidia extra apps etc.. if you so wish just > > > run ./nvidia.run --no-kernel-module -a > > > > > > > > > Hopefully this will help those of you wanting Nvidia driver instead of > > > Nouveau. > > > Please note this is a ruff write up and guide not a perfect solution, and > > > assumptions are made that you are always fimilar enough with *nix > > > operating systems to figure out that parts i've missed out or aint put in > > > detail. > > > > Did you run into a fatal xorg crash when trying to get xorg use nvidia > > driver? > > If yes, how did you beat it? > > > > I get a "Failed to allocate sofware rendering cache surface: out of memory" > > error which, according to Google, is pretty damn bad > > https://www.google.se/search?q=NVIDIA+xorg+Failed+to+allocate+sofware+rendering+cache+surface:+out+of+memory. > > > > Full log of my Xorg's sad demise when using Nvidia driver > > > > http://pastebin.com/E9Guuea4 > > > > P.S.: > > If I may ask, what nvidia card are you using? > > I got (to) the same (point). Have not managed to get it to work so far. Same > error, too, though I got multiple (depending on how I tried to initialize X). > gtx 950. I hope Mathew Evans has the secret (he said he is running the driver "without an issue" ... (intense finger crossing) -- 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/15d546de-0b95-473e-b9a4-aa95002d1a0c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC
W dniu niedziela, 8 stycznia 2017 18:03:47 UTC+1 użytkownik Andrew David Wong napisał: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > > I know that this sounds rather bizarre, but my Qubes instance > > consistently gets stuck after GRUB menu if a USB Audio device is > > connected to the computer. So far I have a 3/3 repro rate on that. > > What type of logs/information should I gather from my machine in > > order to troubleshoot that? XL dmesg does print a RMRR warning > > about USB controllers > > > > Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all > > controllers hidden from Dom0. > > > > Is your sys-usb set to autostart? If so, try disabling that to see > whether the system can boot. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V > d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u > 8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ > 2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH > pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF > I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx > p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb > ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y > QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu > NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s > u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ > wIyI9Itq6I/JD32gR2i0 > =lqgz > -END PGP SIGNATURE- Hello Andrew, The issue still occurs after disabling autostart of the sys-usb AppVM. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/3d889653-b6e9-4c0b-854d-4dae694fb76d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-08 08:30, Grzesiek Chodzicki wrote: > I know that this sounds rather bizarre, but my Qubes instance > consistently gets stuck after GRUB menu if a USB Audio device is > connected to the computer. So far I have a 3/3 repro rate on that. > What type of logs/information should I gather from my machine in > order to troubleshoot that? XL dmesg does print a RMRR warning > about USB controllers > > Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all > controllers hidden from Dom0. > Is your sys-usb set to autostart? If so, try disabling that to see whether the system can boot. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcnDpAAoJENtN07w5UDAw8NcP/iQTveiRfsgdJbeweJC84k6V d3UdLc8i7OrFuh4Cya0opcH341OKvCid4Rv3jIVAhRhE+TSVgobKQkXXEEE9UO8u 8l2ugFuUg3gYUv//WIJUmCNZXRXTTT7Tk7JFjXXhyKUjrkD1B9oAhlVPcK3UaUiQ 2lkAgMWVPDpo9mJMoc4GaQlWZX9sDwJ14M75lMa0lPtbN93nmFOOiye6FNIQ20bH pmbuu6bfyI1w53bVMA84HZIXs1msvXfLLO2CaVksntEk8TaiO/MBM8wmXYA9IQrF I3yxsAVm6pjqlkAIABTkGzM6wOrUeHQjgqTewvmQYO+ch5K00r/Jy2/zZwmNYOOx p/qHn0q82GcITe73xDTD2vp6QILkqV3VCeFBPc9JzqrFYYRONtPr3vDyD48EJ2Nb ButtRJXAxqe6QIkfWs614tfZYWzHMgOVSHokiGnoHMIG5OfU8jDD+ywwzLGyt+2Y QZsAL7dKVxxfEybAFIacumC0HyAIJWtbZDcfl6mnP3qmrGbIo8PebzwpOGCkDMFu NS4aC+dmqJQSqfl2yufNYbr+2eZGoPmhE206qfIL0KBM3Cch8M2RytEXHjyBCH4s u5SGaOALrvlM5zWADoTWyhd6PEg9EWEHkl9vo2MkFYq90o7/VIzWQBX15H5uCsYJ wIyI9Itq6I/JD32gR2i0 =lqgz -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/b87bc9fb-cdff-99a7-56a0-77058ad24850%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Enable copr in fedora
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-07 17:54, Max Suica wrote: > Hey guys > > I recently used copr to install the remmina remote desktop client. > I ended up momentarily allowing all network traffic to the > templateVM, a process I understand is less than optimal. > > Herbies wrote: >> I have enabled all the port/protocol. > and >> Is necessary to comment the proxy directive in both yum and dnf >> config file. > > Can you note a few more details here, Herbie? I've tried to find > the ports needed for copr but cold not find them, and I'm also not > sure about the config files you mentioned (could not find anything > in the machine's /etc/yum.conf, for example). > > My goal here: 1. Configure the template to use copr acording to > qubes best practices (ie, without punching a huge hole in the > firewall) 2. Document the procedure for other users who need copr > > Andrew, once I write up the instructions, is there a place I should > submit them? > > Regards, Max > Yes, you can submit them by following these instructions: https://www.qubes-os.org/doc/doc-guidelines/ Thanks! - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcm+uAAoJENtN07w5UDAwpdcP+gPTyaY8jTNLJOyFyhJw70nB 3nxcTmI/aNCPTve/A0xkfnLr9r4Id4/ZyAffGA6tATC9BxNg01kijCsaeozoNC+D FhLtBTf80pcq4iOqt5efOk5+0NrgTgszuTESNV5edv3OYbyztrj3zyofP1mL5ySM ImHqJRgsIf7dPPpr/COKTTEJ62W1uHtBhkpwYvFfcvjK75BMgEfv/xQ+XbQ6WCj1 yLfraMjgxepCbRZy8Thg24oWyMcXyX4NtZh4cK+tC5aO6rrVoBHn1s3292dlSZG5 0GoScEJJwQv1fOhKKdZfczNqUmP9ffJAgoFJMdg1ahDJabknn8QDsAtT/p0NfDQu yEwHy2PCT+0rtC7n8i6IwpNVZTPSY3NN2A/3DVNXYAK2Jl3xVenz68/uHgENxt4x Fv+RuvYi7pGUl2AzEsP5Q7Vx0EVrDhn8GhLhIXpvOGgFf0nou9CC6vDRpxEpj+pi IR/fFOh6Kp92Q+OmnZ3GbzwPEZmDm6I8uhiJ0G1n9mvbT55by8ePxEPpwOBhz8mr gjnd5kJMIZmnUnrhqTfV+OXyG+bzIp5kHFk+Q9B+TlBuLoeBqNibHqM8BTv9aY8F znRboj+F/gYokhFSBmB+Jp49F/sLgPqFCH9wvxN+rbkIuSXRObSFx6TMU5JVf6KJ Y6tlDv+j/4tGNGKdCVQV =USh0 -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/b32fb274-c702-f2fe-37c8-4df1da74b9a5%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] installing on VM retention
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-07 12:18, 5w8ntn+1zzdj5znb09fg via qubes-users wrote: > after performing sudo commands i can successfully install > application from respository > > it works well in the vm > > but if i shutdown the vm and restart it the application has > vanished > > what am i missing when i install in the vm to keep it regardless? > kind, jim. > It sounds like you want to install these programs in a TemplateVM instead of a TemplateBasedVM: https://www.qubes-os.org/doc/templates/ - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcm8kAAoJENtN07w5UDAwjm0QAJ5PeEy8TrrG4HMmLxRw3f/e amsasyh/LoF4yli+5+ZyEmyvtLBNT/mVu4VMkosfJShqe+MC21i4ailUn2LeggbP 70ULWKF6NXbks9mBIcuMCXRDHpxB22UrcB39COvuEzwn/eAAcoDIMNW1qJ9ikZBW psDeLwaPQD9UVSrlRItXRt+yhEH891OVmJu6WJ8OwVKLLnbH0MPmoRqBYnIH/6Ds idScyacg5zxOatedFotYlrK6b3j3U4iKiEty8WMh5uMYX61BDPwM6Y5vICIwqMHS YiZXR8nok6gOhe2ST2ffsA8eIEfQAqGPDrzBcCTfqRUsEUUTaVIZ8paIYuNL8x8p gbaZVne+MeRjllf84brUE2ZNhb3mG7894E/GNG2VNEm48k+/XxMFwZIEHW63p1EX Sd24hypU/Tlvx/JNZr4DysZ0oh6tO23bSz6Iy20P+cNW8pFVp8wQPOxz0L/UEvKI 3TM6iXTP2AO/uSVrh7DkD9ERODSqT34ZWlPdAE9KhiXxiE3ZHM4B2g5HJGUWwL0c ACKKrj55f6ZIIsGBKx328nKNDzBzrHwDdGa/MSRLb6XvrH/HJHa9O8qB2igMKFdZ akZC4pDncEgtbXlGe0Fk27JnMGpfwWtfl5D/WfuhgUqq/9zI0jyo7IUD8llbevr2 s62XByS/aN4q3mQrRnw+ =wL8Z -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/c77fbe59-a450-93db-eca9-f8c8c7df5187%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Bug - Qubes fails to boot if a USB Audio device is connected to the PC
I know that this sounds rather bizarre, but my Qubes instance consistently gets stuck after GRUB menu if a USB Audio device is connected to the computer. So far I have a 3/3 repro rate on that. What type of logs/information should I gather from my machine in order to troubleshoot that? XL dmesg does print a RMRR warning about USB controllers Qubes 3.2 Kernel 4.8.12-12 I use a sys-usb AppVM with all controllers hidden from Dom0. -- 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/bc169684-65b8-4782-8acd-6b5553c7dbc3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora Desktop in Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-07 18:27, Patrick Bouldin wrote: > On Saturday, January 7, 2017 at 3:21:42 AM UTC-5, Andrew David Wong wrote: > On 2017-01-06 14:37, Patrick Bouldin wrote: On Wednesday, December 28, 2016 at 2:41:28 AM UTC-5, Andrew David Wong wrote: On 2016-12-27 12:39, Patrick Bouldin wrote: >>> On Tuesday, December 27, 2016 at 2:13:48 PM UTC-5, Patrick >>> Bouldin wrote: On Tuesday, December 27, 2016 at 2:11:04 PM UTC-5, Patrick Bouldin wrote: > On Tuesday, December 27, 2016 at 2:04:28 PM UTC-5, > Patrick Bouldin wrote: >> On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, >> Patrick Bouldin wrote: >>> Hi, I saw some threads on this but am not clear at a >>> high level. >>> >>> I thought I would install dropbox client on one of my >>> Fedora VMs so that working with files is much >>> smoother than from a browser. So, is installing a >>> Fedora Desktop the best plan to do that? Don't assume >>> I know enough of native Qubes ability please - maybe >>> I'm missing a key point! >>> >>> Thanks, Patrick >> >> Thanks David. housekeeping question - before I started >> I copied my Fedora template, just in case. Am I correct >> I can easily undo those changes incorrectly made by >> deleting the template and renaming the backup template >> to the production one (just deleted)? >> Yes, that's correct. > > Sorry, I meant Andrew! No worries. And I see it works so disregard, Andrew - thanks again. >>> >>> Wow, this is a bear for me. >>> >>> Dropbox said:Add the following to /etc/yum.conf. >>> >>> >>> name=Dropbox Repository >>> baseurl=http://linux.dropbox.com/fedora/\$releasever/ >>> gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc >>> >>> So I performed a sudo gedit on that file and added the above >>> three lines. When I saved it I received this: >>> >>> ** (gedit:1791): WARNING **: Set document metadata failed: >>> Setting attribute metadata::gedit-position not supported >>> [user@fedora-24 ~]$ >>> >>> So I do see that you can't save metadata by extending the >>> yum.conf file, and tried a few other things that I think it >>> was suggesting. >>> No, I think that's just a warning message about the gedit program itself. Should be safe to disregard. You can verify that the contents of the file were saved with `cat /etc/yum.conf`. >>> When I try and run $ sudo dnf install nautilus-dropbox I get >>> this: Last metadata expiration check: 0:14:35 ago on Tue Dec >>> 27 15:23:35 2016. No package nautilus-dropbox available. >>> Error: Unable to find a match. >>> Try this: $ sudo dnf --refresh install nautilus-dropbox If that still doesn't work, try creating a separate repo file, `/etc/yum.repos.d/dropbox.repo`, with this content: [Dropbox] name=Dropbox Repository baseurl=http://linux.dropbox.com/fedora/$releasever/ gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc Then try this again: $ sudo dnf --refresh install nautilus-dropbox Darn, still not working - I noticed this link is not working: baseurl=http://linux.dropbox.com/fedora/\$releasever/ gpgkey=http://linux.dropbox.com/fedora/rpm-public-key.asc So it's not finding the file, tested that just in my browser address bar. Patrick > > I wouldn't expect that to work in your browser address bar due to the > backslash, but I have to ask: Why not try following the instructions I > provided in the previous email (to which you're replying)? > > Hi Andrew, I did follow them precisely, I just started fumbling around on my > own - basically it still says it can't find the file, errors out - just like > before - so I was just adding 2+2, figured it was the one I pointed out. So I > did try the suggestions, including a special dropbox.repo in the /etc > directory, same result. I need this in the fedora-24 template, right? > > So if I: > [user@fedora-24 etc]$ cat dropbox.repo > It needs to be in /etc/yum.repos.d/ > I get... > > [Dropbox] name=Dropbox Repository > baseurl=http://linux.dropbox.com/fedora/$releasever/ > gpgkey=https://linux.dropbox.com/fedora/rpm-public-key.asc > > Then when I run > [user@fedora-24 etc]$ sudo dnf --refresh install nautilus-dropbox > > I get... > > google-chrome 2.3 kB/s | 3.7 kB 00:01 > > Fedora 24 - x86_64 - Updates 3.4 MB/s | 20 MB 00:05 >
Re: [qubes-users] Re: Fedora Desktop in Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-07 18:42, Manuel Amador (Rudd-O) wrote: > On 12/24/2016 05:58 PM, Andrew David Wong wrote: >> >> This is not true. Dropbox doesn't even start automatically, much >> less communicate automatically. If you install Dropbox in a >> Fedora TemplateVM according to the above instructions, the >> Dropbox daemon will *not* start automatically in any AppVM based >> on that template. You have to start it manually. (After starting >> it manually, you can configure it to start whenever the VM starts >> up, if you wish.) >> > > I believe the RPM installs a desktop file in the autostart > directory so, yes, it does start automatically. > > You can mask it, though. > Not for me. After installing in a TemplateVM with the procedure I gave above, then starting an AppVM based on that template: $ dropbox status Dropbox isn't running! - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcmUSAAoJENtN07w5UDAw1kcP/30J/akH741sj9yMS0KnhMei mdBB1ifNhTT0A/+oEmaQzjEQP0BFgLKwMqSejSRFF4t03B1y+90o3qAFXBfR1e4T IILCql8XQbHHmAKXJeMMoWP5/UWvhMe1ekEIJaIXNowsNUi+6T2tlMhwhpavLh0F WRnFy4Y6PQp32VBcBh4AP5pmSqRMw+Sw2XkJhwJ9uIiDeAkHl3C8CM4PSJh2rLLG OSeokdfk6cbBDsvOJ8NG8Adx9Did1ddoRRZYPAjzB8Hs8Ult9Sn/8e9jzX09/XQX gedk/154QD8fK1DccNw5Igsy/dE3nylvHANWBlV+WUUR3kvfAXXGDU4KBVaFpBq9 ffXI49r2YCBi9pD2s0tTeNgO8ESCUI3daCvtPRtK4yV0RfUfkgqUfQmdvnDM+1ro Fd/d23XFMsmj9EbThu9vqr1mWhVhH9AdSLJt8yMcZJVoDSy+YYo1yRLFjxkDBjzy AAYGxraUZeoNZjypgM7ao5gdTvclk45jHXnFq9bUIw2DXUM8sF7BLPw4tPm2RyAH ZKA03nt+03+n7hnboKsddLWZ+dNo4FDz9TGVYM/elKNVCbmGfekmub52gDUFmAVI C+Xruq1dWNjsEtU1c+tvdJh/xrqDjNrgOWyxtWqLslaeky5KW94N8sJqw8CBvC0o ugXXTPXoBBTycKniQB46 =BpP1 -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/f0cfb100-3e72-bbed-9e34-2958a831e630%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)
On Sunday, January 8, 2017 at 1:36:37 AM UTC+1, daltong defourne wrote: > On Monday, December 19, 2016 at 1:33:23 AM UTC+3, Mathew Evans wrote: > > Just to update. > > > > I am currently running Nvidia drivers without a issue. > > > > dom0 Kernel: 4.4.31-11 > > Nvidia: 375.20 > > Kernel-module: compiled in dom0; > > > > Quick Guide: > > 1. dom0: qubes-dom0-update install gcc devel-kernel ksmod linux-headers > > 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) > > 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > NVIDIA.run > > 4. dom0: ./NVIDIA.run --ui=none --no-x-check --keep --extract-only > > 5: dom0: cp NVIDIA-*/kernel/; IGNORE_XEN_PRESENCE=y CC="gcc > > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM" make module; > > 6: dom0: cp nvidia.ko /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/. > > 7: dom0: depmod -a; modinfo nvidia (all working will show up fine) > > 8: dom0: EDIT GRUB or EFI; add rd.driver.blacklist=nouveau > > 9: dom0; reboot and enjoy nvidia support. > > > > additional: you can install nvidia extra apps etc.. if you so wish just run > > ./nvidia.run --no-kernel-module -a > > > > > > Hopefully this will help those of you wanting Nvidia driver instead of > > Nouveau. > > Please note this is a ruff write up and guide not a perfect solution, and > > assumptions are made that you are always fimilar enough with *nix operating > > systems to figure out that parts i've missed out or aint put in detail. > > Did you run into a fatal xorg crash when trying to get xorg use nvidia driver? > If yes, how did you beat it? > > I get a "Failed to allocate sofware rendering cache surface: out of memory" > error which, according to Google, is pretty damn bad > https://www.google.se/search?q=NVIDIA+xorg+Failed+to+allocate+sofware+rendering+cache+surface:+out+of+memory. > > Full log of my Xorg's sad demise when using Nvidia driver > > http://pastebin.com/E9Guuea4 > > P.S.: > If I may ask, what nvidia card are you using? I got (to) the same (point). Have not managed to get it to work so far. Same error, too, though I got multiple (depending on how I tried to initialize X). gtx 950. -- 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/607ccde9-17a6-46ba-85b8-bc6dd6ea379f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
