[qubes-users] Re: After installing Libre apps can't get them on a shortcut
On Saturday, January 7, 2017 at 5:21:52 PM UTC-5, raah...@gmail.com wrote: > On Friday, January 6, 2017 at 7:57:49 PM UTC-5, Patrick Bouldin wrote: > > On Friday, January 6, 2017 at 7:40:51 PM UTC-5, Patrick Bouldin wrote: > > > Hello, > > > > > > I've added apps to the template before, and then on the app vm I could > > > then create a shortcut. I installed all the Libre apps on the template. I > > > then go to the app vm and they are there, but they don't show up on the > > > "add shortcut" menu. > > > > > > Any clue? > > > > > > Thanks, > > > Patrick > > > > PS - I see the following to add shortcuts to app that didn't make them > > available: https://www.qubes-os.org/doc/signal/ > > > > But I still confused with step 1. Am I even on the right track? What > > shortcut has been created in step 1 of the Signal example? How did he "get" > > the shortcut? > > Patrick > > yes if you mean that the programs are not showing as available to add to the > vm shortcust list, then yes qvm-sync-appmenus templatename should work. Thank you very much, successful! Patrick -- 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/2c02563c-044b-4deb-b0f7-f3b1228fc704%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Removing unwanted menu items under xfce?
On Sat, Jan 07, 2017 at 02:36:37PM -0800, Otto Kratik wrote: > I recently did a fresh install of Qubes R3.2, and then proceeded to restore > several VM's from my previous installation, among them a Windows 7 HVM. I > also installed qubes-windows-tools, which I also previously had installed. > > As a result of that restore/install, xfce has placed about 50 win7-related > app shortcuts in both the win7 sub-menu of the start menu (expected and > desired) and also simultaneously into the "System Tools" sub-menu of the > start menu (not wanted), intermingled among the normal items one usually > expects to find there (terminal, file manager etc). > > KDE is not affected, and logging into that environment shows the proper > expected behavior: win7 shortcuts in the win7 sub-menu only, and system tools > shortcuts where they belong. > > What is the easiest way to edit the entries appearing under the System Tools > sub-menu of xfce, so as to remove the approximately 50 win7-related shortcuts > that I don't want appearing there? > > Thanks.. > I'm sorry you had to go through that. The Xfce menu is at /etc/xdg/menus/xfce-applications.menu If you examine that file you will see a section for a submenu - System That should contain exclusions - X-Qubes-VM is one. If you were to comment out that line you would find the System Tools submenu filled with entries for the VMs on your system. (Try it.) >From the fact that you only have the win7 files there, my guess would be that those entries don't have this category. The entries here are taken from the desktop files in ~/.local/share/applications Have a look at the win7 files and see what category is set: you can edit the file to add X-Qubes-VM to the Categories list and check that the entry no longer appears in the System menu. These files are based on those in /var/lib/qubes/ - look in the apps directory under the HVM. You may see some common Category that you could add to the menu exclusions - otherwise it's a matter of adding the missing category to the desktop files which you could do with awk or sed. I believe there are gui tools to manage the menu, but I dont have any experience with them Hope this helps 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/20170108033328.GA27694%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora Desktop in Qubes
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. -- Rudd-O http://rudd-o.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/24b5a466-8ad9-b91a-6f9f-44ac7c51185e%40rudd-o.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Fedora Desktop in Qubes
On 12/21/2016 11:13 AM, 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
>
Run this Ansible recipe on the AppVM where you will be installing your
Dropbox client:
---
---
# It is assumed that the template will have wget. I could probably use
get_url if it didn't demand a checksum...
- hosts: localhost
tasks:
- name: deploy Dropbox
command: creates='{{ ansible_env.PWD }}/.dropbox-dist' chdir={{
ansible_env.PWD }} wget -O -
"https://www.dropbox.com/download?plat=lnx.x86_64; | tar xzf -
- name: deploy real Dropbox autostart file
copy:
content: |
[Desktop Entry]
Name=Dropbox
Comment=Run the Dropbox service
Exec={{ ansible_env.PWD }}/.dropbox-dist/dropboxd
Terminal=false
OnlyShowIn=QUBES
Type=Application
NoDisplay=true
dest: '{{ ansible_env.PWD }}/.config/autostart/dropbox.desktop'
owner: user
group: user
mode: 0644
---
Restart the AppVM. The Dropbox icon should appear on the taskbar now.
--
Rudd-O
http://rudd-o.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/74438f01-da56-0bfa-d747-7c188142dd0d%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Fedora Desktop in Qubes
On Saturday, January 7, 2017 at 3:21:42 AM UTC-5, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > 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)? > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYcKUHAAoJENtN07w5UDAw2YIQAM/02kvQYHz23LcoAEZlhtjm > DIcnTGow1qt8e5M6xBGUg+dZ0E6X1XQp6zyjZUabNnbTx1qLU1dFkMNFdb++CD9O > juRx2pzaEDTYwkQeF/ww1L3H26aW+YsOPsQ141+lJUkUX0QjvriLO49R4MaoBInS > ZTBM9jchLH3hMtruLzV4kDi2ctd4357RnjPOflv/7Upsp41uQ/zfsG3fkCXiqvWo > 2LoHbuoCuc/AhwByY4i8nVxA2oX4YiSfMhwD+hXNzdpgoYBYRLFLamfnccz8Ea65 > KM24TCFxGijkwlQl819WwP24WDYO7UiktPWji+4mUR0XCK6XdPHNeUXJCOtQXzH5 > H+tpRxICDuRG4VL5LTgHfpm2Ut7Pv57LE2mn4EUKratUG8RicATGO5V9jgTb9ORV > pRFiK0fRPacG+3fxvLTXU9ZfBIekFuDJVX4SZe8MFfsUTIvE5SVyimPUtQ92xPDz > x2mKGb4uqavTTXjlqDs9IAb6OGNNWJcUkOXUknmzVYRTtkWqUaWg0T1it7tVUQNi > JrXZPebWiu6ksiICUiKHIUw7PrrXmA3T8S5KyUSVBwOX8Dv4zrlppBz8/5pRb4Up > 5l3Mmihxm6WIgVMKBQK6Bjh49gDOz0UXbR6z+7szEBbnriSCPwb9ERSrSyNf2BgD > /FF8jo893PdeHbXyHwAa > =2EmG > -END PGP SIGNATURE- 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
Re: [qubes-users] Enable copr in fedora
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 -- 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/9b5a0486-2815-4a63-aca4-35e926f052cd%40googlegroups.com. 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 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? -- 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/62795cfd-8c07-48d1-9d0a-57a494647bbe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
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. -- 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/aac7fb542677d1411eec0c3c185f8d46.webmail%40localhost. 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 Saturday, January 7, 2017 at 8:53:12 PM UTC+3, testo...@gmail.com wrote: > looks like your lightdm died, Daltong. > Had exactly same thing. > > That's about as far as I got myself a month ago > > Maybe some Xorg driver is needed or some other magic. > > P.S. > Also, for me, despite all my efforts nouveau still was present and probed for > some device or other during boot, and I'm very certain I've edited grub > allright. I then created a blacklist.conf to "off nouveau for good" but that > did not solve my weird lightdm issues. Okay, this is indeed lightdm dying (also, xorg doesn't start, so I guess the reason for lightdm's death is that xorg is not starting) I tried to install nvidia's xorg stuff by running: ./nvidia.run --no-kernel-module -a the results ended up very dubious (xorg died again and rebooting with Intel graphics did not "resurrect" it) Managed to restore "intel compatible" xorg.conf with some trial and error (note to self: Backups!) and am writing this from qubes running with IGfx. Foppe de Haan, Mathew Evans, could you please share your xorg.confs for Nvidia driver ? -- 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/e3209468-ee63-496b-ada7-9a95217d2cfc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Error while updating the default Archlinux Community template
anti-sec...@re-gister.com wrote: > Hello @all! > > I installed the default arch community template using, > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > qubes-template-archlinux > > But when I click on the update button I get an error: > > ::Synchronizing package databases... > > error: failed retrieving file 'core.db' from mirrors.kernel.org : > Resolving timed out after 10524 milliseconds > > error: failed to update core (download library error) > > error: failed retrieving file ... > > Although the Template VM is connected to the sys-firewall... > > Appreciate any help! You will need to allow full network access if you use pacman. Alternatively, use a different package manager, see https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a-fedora-templatevm -- 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/1483832499.1886.4.camel%4016bits.net. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] fedora - mplayer (command line)
haaber wrote: > Hello, > > I wanted to provide my fedora template with mplayer (command line > version). But according to dnf / yum that does not exist (?). This seems > a subject on its own in stand-alone fedora (f22 at least), and have > qubes-fedora won't make it more easy, I fear. I could live with vlc as > well, but it does not exist either. > > Does somebody have this problem before me? Thank you! Bernhard That's indeed an upstream decision of not including those packages in fedora. The usual solution is to enable the rpmfusion repository, where it can be found. Instructions are provided at: https://www.qubes-os.org/doc/software-update-vm/#rpmfusion-for-a-fedora-templatevm 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/1483829769.1886.2.camel%4016bits.net. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Query: Adding shortcuts to VMs for software installed specifically on them.
On Saturday, January 7, 2017 at 8:53:15 PM UTC, ray wrote: > Hi Folks, > > Have just installed Qubes and am loving it so far. One item I have a > query on, is how do I go about adding shortcuts to VMs for software I've > installed on them? E.g. I've installed VNC on my admin VM using dnf and > received a message stating it was sending the application list to dom0, > but when I try to add a shortcut from the dom0 admin VM 'Add More > Shortcuts' menu, VNC doesn't appear in the Application tab list. > > > Is this related to the installation path, or is there something else I'm > missing? Thanks in advance for any assistance you can offer. > > > Regards, > > R. Are installing the software in your templatevm and not the appvm. These two links may help. https://www.qubes-os.org/doc/software-update-vm/ https://www.qubes-os.org/doc/managing-appvm-shortcuts/ -- 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/03e54fa3-f005-4751-8e43-8e0cafdc2e65%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Removing unwanted menu items under xfce?
I recently did a fresh install of Qubes R3.2, and then proceeded to restore several VM's from my previous installation, among them a Windows 7 HVM. I also installed qubes-windows-tools, which I also previously had installed. As a result of that restore/install, xfce has placed about 50 win7-related app shortcuts in both the win7 sub-menu of the start menu (expected and desired) and also simultaneously into the "System Tools" sub-menu of the start menu (not wanted), intermingled among the normal items one usually expects to find there (terminal, file manager etc). KDE is not affected, and logging into that environment shows the proper expected behavior: win7 shortcuts in the win7 sub-menu only, and system tools shortcuts where they belong. What is the easiest way to edit the entries appearing under the System Tools sub-menu of xfce, so as to remove the approximately 50 win7-related shortcuts that I don't want appearing there? Thanks.. -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/45621212-9323-4ec7-b168-248a88c0e2eb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Dom0 (System tools) shortcuts suddenly disappeared
On Friday, January 6, 2017 at 5:05:38 AM UTC-5, Ángel wrote: > > Do you still have those files listing the .desktop entries that should > be shown in the menu? Seeing no other recourse, I opted to re-install my entire operating system in order to correct the menu issue, prior to having a chance to check this specific item. Thank you for the suggestion though, nonetheless. -- 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/9804cb5d-4eb5-4402-bc97-d20f70e7f41f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: After installing Libre apps can't get them on a shortcut
On Friday, January 6, 2017 at 7:57:49 PM UTC-5, Patrick Bouldin wrote: > On Friday, January 6, 2017 at 7:40:51 PM UTC-5, Patrick Bouldin wrote: > > Hello, > > > > I've added apps to the template before, and then on the app vm I could then > > create a shortcut. I installed all the Libre apps on the template. I then > > go to the app vm and they are there, but they don't show up on the "add > > shortcut" menu. > > > > Any clue? > > > > Thanks, > > Patrick > > PS - I see the following to add shortcuts to app that didn't make them > available: https://www.qubes-os.org/doc/signal/ > > But I still confused with step 1. Am I even on the right track? What shortcut > has been created in step 1 of the Signal example? How did he "get" the > shortcut? > Patrick yes if you mean that the programs are not showing as available to add to the vm shortcust list, then yes qvm-sync-appmenus templatename should 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/8c2d59ce-301a-4b67-88d7-afc03e8d5729%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] notify about updates of cloned template
On Saturday, January 7, 2017 at 9:34:48 AM UTC-5, Eva Star wrote: > On 12/29/2016 07:17 AM, Andrew David Wong wrote: > > > > > Update checks are typically run in VMs based on the template, so if > > you haven't had any VMs running based on that template that can reach > > update repos, that's probably why. > > > After you message I run AppVm made from this clone template, and > nothing. Updates still does not check automatically.. > > > > -- > Regards does it have network access and using the sys-firewall? -- 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/ae017169-3f6d-4f1f-a730-89d6bc8d8b5b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Query: Adding shortcuts to VMs for software installed specifically on them.
Hi Folks, Have just installed Qubes and am loving it so far. One item I have a query on, is how do I go about adding shortcuts to VMs for software I've installed on them? E.g. I've installed VNC on my admin VM using dnf and received a message stating it was sending the application list to dom0, but when I try to add a shortcut from the dom0 admin VM 'Add More Shortcuts' menu, VNC doesn't appear in the Application tab list. Is this related to the installation path, or is there something else I'm missing? Thanks in advance for any assistance you can offer. Regards, R. -- 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/052b770b-1b18-9aad-fba8-931cdd190363%40rb-cc.ie. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] installing on VM retention
I am far away from being expert, but as I read the doc (and tested myself), the procedure is 1) start template VM 2) install software in template VM 3) shutdown template VM 4) restart your user VM and the software will persist. Bernhard On 01/07/2017 09:18 PM, 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. > > > > > > > Sent using Guerrillamail.com > Block or report abuse: > https://www.guerrillamail.com//abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D > > -- 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/490c59ac-1a31-92e7-bfdf-5d8ba36e3145%40web.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Dell Inc. XPS 13 9360
EFI boot tested only - no legacy. Updating kernel from 4.4.14-11 to 4.4.31-11 makes system incredibly slow, window manager takes ~100% CPU. 4.4.14-11 for dom0 is perfectly usable even after installing new kernel - by changing /boot/efi/EFI/qubes/xen.cfg to use old one. HiDPI display remains problematic - there's no good way to scale everything properly. USB type C port does not work. SD card reader works. Touchscreen does not seem to work. Webcam and mic 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/CAG9ivCxPN6_v2E7Uj-ctxEAzuAcenCpUXFfon3%3De-gBWBYpdRw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout. Qubes-HCL-Dell_Inc_-XPS_13_9360-20170107-143437.cpio.gz Description: GNU Zip compressed data Qubes-HCL-Dell_Inc_-XPS_13_9360-20170107-143437.yml Description: application/yaml
[qubes-users] installing on VM retention
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. Sent using Guerrillamail.com Block or report abuse: https://www.guerrillamail.com//abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D -- 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/67ed5b0bbaaee5c9c0de7f5780b94b6b6287%40guerrillamail.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: HCL for R3.2 - Lenovo G505S (AMD laptop with Coreboot 4.5 + SeaBIOS 1.10)
I have created a new pull request to qubes-hcl repository - https://github.com/QubesOS/qubes-hcl/pull/3 . all FixMe's already replaced with relevant information. also attaching this file below, just in case... -- 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/b6b86d21-c5ff-448d-a8c7-9e7dac22cf3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout. Lenovo-G505S-qmastery16.yml Description: Binary data
[qubes-users] Re: How to attach a Yubikey as a normal, extra usb keyboard only to specific AppVMs?
I was able to get my yubikey to work in this personal vm but for the life of me I wasn't able to use it to authenticate with my gmail on this login. I followed the instruction where you add the info to the qubes.InputKeyboard file then it worked. You'll know you've configured that file correctly if you get the popup. I'm still not able to get my smart card reader to work even though I think i've followed all the instructions. I'm gonna use all these same tricks and see if I can get it to work in the Win7 HVM...FML B4U2D0 -- 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/68ff7e9e-7bf1-454c-8c33-7a026e529e34%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL for R3.2 - Lenovo G505S (AMD laptop with Coreboot 4.5 + SeaBIOS 1.10)
Following the steps of Vladimir... ( https://groups.google.com/d/msg/qubes-users/5dwZt4xANpA/0a8VkMQlaQYJ ) I got the same G505S laptop, built Coreboot / SeaBIOS from the latest sources and also included some great payloads: memtest, filo (minimalistic bootloader), tint (Tint Is Not Tetris), nvramcui (tool to change some CMOS values), coreinfo (information about system hardware), as well as ramdisk with KolibriOS - tiny operating system that fits on a floppy! (http://kolibrios.org/en/index) Build instructions, configs and ROMs could be obtained here, for those people who are interested - http://board.kolibrios.org/viewtopic.php?f=25=3446 (sorry that it is on Russian, please use Google Translate) SeaBIOS is a pure classical BIOS (no UEFI!), so it relies on MBR to boot from Hard Drive. I have experienced the following problem: 1) Qubes R3.1 boots fine instantly after the installation; also, if to upgrade R3.1 to R3.2 - will boot fine as well 2) meanwhile, after a Clean Install of Qubes R3.2, it fails to boot - stuck at "Booting from hard drive:" SeaBIOS message with blinking "_" character, cant reach GRUB Boot Menu because MBR (or GRUB) is corrupted out-of-the-box. Luckily it can be fixed: boot from your Qubes R3.2 installation media, go to "Troubleshooting -> Rescue a Qubes system", after booting to anaconda installer please choose "1) Continue" (and enter your Qubes partition password if you chose to encrypt it during install), then enter "chroot /mnt/sysimage" - and, finally, "grub2-install /dev/sdX" (where X is a letter for your hard drive with Qubes, in my case it was sda: "grub2-install /dev/sda") After I fixed MBR/GRUB with the steps above, Qubes R3.2 boots perfectly! Although without GRUB graphical themes - the whole booting process (including the moment when you are asked to enter a Qubes partition password) will be a pure text... but it works! :) Dont worry: starting with a graphical login screen, (where you need to choose a user and enter password), you will see the "nice graphics" again. Everything else is normal and works OK ! :) Have not encountered any other problems yet... qubes-hcl-report told that my hardware/software configuration got all the important features working: HVM, IOMMU, and even SLAT (thanks to A10-5750M APU which supports NPT) https://www.qubes-os.org/news/2016/09/02/4-0-minimum-requirements-3-2-extended-support/ - Minimum requirements of Qubes 4.0 have been met by this AMD-based system P.S. Going to make a pull request to qubes-hcl repository - HCL report (.yml file) -- 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/413a479a-760a-47f8-a2bf-c7858230a8c2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Error while updating the default Archlinux Community template
On Saturday, January 7, 2017 at 5:42:56 PM UTC+1, anti-...@re-gister.com wrote: > Hello @all! > > I installed the default arch community template using, > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > qubes-template-archlinux > > But when I click on the update button I get an error: > > ::Synchronizing package databases... > > error: failed retrieving file 'core.db' from mirrors.kernel.org : Resolving > timed out after 10524 milliseconds > > error: failed to update core (download library error) > > error: failed retrieving file ... > > Although the Template VM is connected to the sys-firewall... > > Appreciate any help! You have to go to VM Settings in Qubes VM Manager -> Firewall rules -> Allow full access for 5 or more (depends on your connection) minutes. Now you can update via update vm system in Qubes VM Manager. -- 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/df96eb83-145f-402c-9038-5c03fe0f4da0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] HCL - Razer Blade 14" (01/2017)
I have the stealth one and had similar issues, unfortunately Qubes is still unstable with the new kernel and crashes on me. Unsuspend/wakeup is not working for me, the os just freezes with black screen. External monitor is also not detected unless I boot qubes with it attached. You can test the camera with cheese, mine is not working :( I am also still unable to assign devices to other VMs without something crashing or not working. Please let me know if you manage to fix any of those issues on your laptop. Thanks -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/67c85641-56cf-4dfd-a587-61e3756629af%40googlegroups.com. 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)
looks like your lightdm died, Daltong. Had exactly same thing. That's about as far as I got myself a month ago Maybe some Xorg driver is needed or some other magic. P.S. Also, for me, despite all my efforts nouveau still was present and probed for some device or other during boot, and I'm very certain I've edited grub allright. I then created a blacklist.conf to "off nouveau for good" but that did not solve my weird lightdm issues. -- 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/56eca00d-8fdf-4807-8ca0-4dfccf57e1c1%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Error while updating the default Archlinux Community template
Hello @all!I installed the default arch community template using,sudo qubes-dom0-update --enablerepo=qubes-templates-community qubes-template-archlinuxBut when I click on the update button I get an error:::Synchronizing package databases...error: failed retrieving file 'core.db' from mirrors.kernel.org : Resolving timed out after 10524 millisecondserror: failed to update core (download library error)error: failed retrieving file ...Although the Template VM is connected to the sys-firewall...Appreciate any help! -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/20170107164254.DC7103221B9%40astra4649.startdedicated.de. For more options, visit https://groups.google.com/d/optout.
[qubes-users] fedora - mplayer (command line)
Hello, I wanted to provide my fedora template with mplayer (command line version). But according to dnf / yum that does not exist (?). This seems a subject on its own in stand-alone fedora (f22 at least), and have qubes-fedora won't make it more easy, I fear. I could live with vlc as well, but it does not exist either. Does somebody have this problem before me? 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/ca5782d0-c6bb-ffe9-ef6a-65ea9278b9bc%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 Monday, December 19, 2016 at 3:12:55 PM UTC+3, Foppe de Haan wrote: > On Sunday, December 18, 2016 at 11:33:23 PM UTC+1, 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. > > Thanks. Corrected a few typos / improved readability: > > 1. dom0: qubes-dom0-update gcc kernel-devel kmod kernel-headers; > (qubes-dom0-update --enablerepo=qubes-dom0-unstable if using newer kernel) > 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) > 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > NVIDIA.run; > chmod +x NVIDIA.run; > 4. dom0: ./NVIDIA.run --ui=none --no-x-check --keep --extract-only > 5: dom0: cd NVIDIA-*/kernel/; make module IGNORE_XEN_PRESENCE=y CC="gcc > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM"; > 6: dom0: sudo cp nvidia.ko /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/. > 7: dom0: sudo depmod -a; modinfo nvidia (all working will show up fine) > 8: dom0: EDIT GRUB or EFI; add rd.driver.blacklist=nouveau (to kernel > options) > 9: dom0; reboot and enjoy nvidia support. (First boot will likely take a > while.) Poor thing just stopped after I entered my LUKS password (I pressed escape to see if there are any errors there - nope), switched to a black screen and that's ... all. Nothing more happens. Should I like, wait more? It's been at least 10 minutes... -- 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/a9457c0a-6b74-4c75-a7d5-a4f9472a6b28%40googlegroups.com. 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 Saturday, January 7, 2017 at 5:46:37 PM UTC+3, daltong defourne wrote: > On Monday, December 19, 2016 at 3:12:55 PM UTC+3, Foppe de Haan wrote: > > On Sunday, December 18, 2016 at 11:33:23 PM UTC+1, 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. > > > > Thanks. Corrected a few typos / improved readability: > > > > 1. dom0: qubes-dom0-update gcc kernel-devel kmod kernel-headers; > > (qubes-dom0-update --enablerepo=qubes-dom0-unstable if using newer kernel) > > 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) > > 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > > > NVIDIA.run; chmod +x NVIDIA.run; > > 4. dom0: ./NVIDIA.run --ui=none --no-x-check --keep --extract-only > > 5: dom0: cd NVIDIA-*/kernel/; make module IGNORE_XEN_PRESENCE=y CC="gcc > > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM"; > > 6: dom0: sudo cp nvidia.ko > > /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/. > > 7: dom0: sudo depmod -a; modinfo nvidia (all working will show up fine) > > 8: dom0: EDIT GRUB or EFI; add rd.driver.blacklist=nouveau (to kernel > > options) > > 9: dom0; reboot and enjoy nvidia support. (First boot will likely take a > > while.) > > Attempt to extract the driver results in "extraction failed TERMINATED" > > No further info. > > Where do I go from here ? Found out the reason - had too little free space out there in dom0 land (dumb nvidia installer could have at least said something about not having enough space in /tmp/). Built the module in a special folder I made in /var/... Installing now... wish me luck -- 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/6ee7931c-6375-47b2-90b0-e3c21ff15d76%40googlegroups.com. 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 Monday, December 19, 2016 at 3:12:55 PM UTC+3, Foppe de Haan wrote: > On Sunday, December 18, 2016 at 11:33:23 PM UTC+1, 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. > > Thanks. Corrected a few typos / improved readability: > > 1. dom0: qubes-dom0-update gcc kernel-devel kmod kernel-headers; > (qubes-dom0-update --enablerepo=qubes-dom0-unstable if using newer kernel) > 2. appvm: download NVIDIA-Linux-375.20-install.run (any appvm) > 3. dom0: qvm-run --pass-io 'cat /PATH/TO/NVIDIA.run' > NVIDIA.run; > chmod +x NVIDIA.run; > 4. dom0: ./NVIDIA.run --ui=none --no-x-check --keep --extract-only > 5: dom0: cd NVIDIA-*/kernel/; make module IGNORE_XEN_PRESENCE=y CC="gcc > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM"; > 6: dom0: sudo cp nvidia.ko /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/. > 7: dom0: sudo depmod -a; modinfo nvidia (all working will show up fine) > 8: dom0: EDIT GRUB or EFI; add rd.driver.blacklist=nouveau (to kernel > options) > 9: dom0; reboot and enjoy nvidia support. (First boot will likely take a > while.) Attempt to extract the driver results in "extraction failed TERMINATED" No further info. Where do I go from here ? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/55b1efc6-77b5-4493-b47d-30c4e3e0d95e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] notify about updates of cloned template
On 12/29/2016 07:17 AM, Andrew David Wong wrote: Update checks are typically run in VMs based on the template, so if you haven't had any VMs running based on that template that can reach update repos, that's probably why. After you message I run AppVm made from this clone template, and nothing. Updates still does not check automatically.. -- 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/58316d9d-50c1-da46-d524-64716a1fe33d%40openmailbox.org. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Problem setting permissive mode for a PCI device
Oh, BTW, I copied the wrong log (silly me :( ) Here's the correct log for "set permissive" service --- qubes-pre-netvm.service - Netv fixup attempt Loaded: loaded (/etc/systemd/system/qubes-pre-netvm.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2017-01-07 16:48:55 EAT; 1min 25s ago Process: 3598 ExecStart=/bin/sh -c echo :04:00.0 >> /sys/bus/pci/drivers/pciback/permissive (code=exited, status=1/FAILURE) Main PID: 3598 (code=exited, status=1/FAILURE) Jan 07 16:48:55 dom0 systemd[1]: Starting Netv fixup attempt... Jan 07 16:48:55 dom0 sh[3598]: /bin/sh: line 0: echo: write error: No such device Jan 07 16:48:55 dom0 systemd[1]: qubes-pre-netvm.service: Main process exited, code=exited, status=1/FAILURE Jan 07 16:48:55 dom0 systemd[1]: Failed to start Netv fixup attempt. Jan 07 16:48:55 dom0 systemd[1]: qubes-pre-netvm.service: Unit entered failed state. Jan 07 16:48:55 dom0 systemd[1]: qubes-pre-netvm.service: Failed with result 'exit-code'. --- -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/a43ba66c-a9c0-42a8-899c-c581200ef38c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Problem setting permissive mode for a PCI device
On Saturday, January 7, 2017 at 4:35:15 PM UTC+3, Grzesiek Chodzicki wrote: > W dniu sobota, 7 stycznia 2017 14:11:36 UTC+1 użytkownik daltong defourne > napisał: > > Hello everyone! > > Trying to follow the steps outlined here: > > > > https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues > > > > Created a service, BUT it fails to start > > > > systemctl status gives > > > > qubes-netvm.service - Qubes NetVM startup > >Loaded: loaded (/usr/lib/systemd/system/qubes-netvm.service; enabled; > > vendor preset: enabled) > >Active: active (exited) since Sat 2017-01-07 15:31:11 EAT; 35min ago > > Process: 4150 ExecStart=/bin/sh -c NETVM=`qubes-prefs --get > > default-netvm`; [ -n "$NETVM" ] && qvm-start -q --no-guid $NETVM > > (code=exited, status=0/SUCCESS) > > Main PID: 4150 (code=exited, status=0/SUCCESS) > >CGroup: /system.slice/qubes-netvm.service > > > > Jan 07 15:31:01 dom0 systemd[1]: Starting Qubes NetVM startup... > > Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session > > opened for user user1 by (uid=0) > > Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session > > closed for user user1 > > Jan 07 15:31:05 dom0 runuser[5102]: pam_unix(runuser:session): session > > opened for user user1 by (uid=0) > > Jan 07 15:31:11 dom0 runuser[5102]: pam_unix(runuser:session): session > > closed for user user1 > > Jan 07 15:31:11 dom0 systemd[1]: Started Qubes NetVM startup. > > > > HOWEVER, after startup I can do in dom0 terminal: > > > > sudo /bin/sh -c 'echo :04:00.0 > > > /sys/bus/pci/drivers/pciback/permissive' > > > > and the permissive mode is set allright (and yes, the device I want to > > "permissivize" really is :04:00.0 on my machine. Huge coincidence, I > > too was amused) > > > > I have to then reboot the VM (which is mighty annoying because it's a > > netvm) and everything seems to work out allrightey (fingers crossed very > > intensely) > > > > Any pointers why it can't see the target device "right away" ? > > Try setting the pci_strictreset to false in the preferences of the target vm. Did that, still can't set permissive 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/beed676e-502c-48d1-aacd-a8e8c4fc1d52%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Boot fails after update
W dniu sobota, 7 stycznia 2017 13:13:25 UTC+1 użytkownik Chris Willard napisał: > Hello All, > > I'm trying out Qubes as it looks very good. > > I installed it, ran the updates and then when I rebooted it drops to > the emergency shell. > > There are lots of the following type error - > [6.27831] Dev sdj: unable to read RDB block 1 > > and the last messages are - > Warning: /dev/mapper/qubes_dom0-root does not exist > Warning: /dev/qubes_dom0/root does not exist > Warning: /dev/qubes_dom0/swap does not exist > Warning: crypto LUKS UUID (long hex string) not found. > > I'm testing Qubes on a Dell Poweredge R710 using RAID. > > It seemed fine until I ran the updates. > > I have had a look on the Qubes site but think I need some help to get > me started! > > > -- > Best regards, > Chris > > P.S. Drowning in email? I use SaneBox to instantly clean up my Inbox: > http://sanebox.com/t/k3bk9 Boot the Qubes installation media and select "Rescue Qubes system" -- 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/6d500aa6-04e8-4806-ae44-951335acd318%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: Problem setting permissive mode for a PCI device
W dniu sobota, 7 stycznia 2017 14:11:36 UTC+1 użytkownik daltong defourne napisał: > Hello everyone! > Trying to follow the steps outlined here: > > https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues > > Created a service, BUT it fails to start > > systemctl status gives > > qubes-netvm.service - Qubes NetVM startup >Loaded: loaded (/usr/lib/systemd/system/qubes-netvm.service; enabled; > vendor preset: enabled) >Active: active (exited) since Sat 2017-01-07 15:31:11 EAT; 35min ago > Process: 4150 ExecStart=/bin/sh -c NETVM=`qubes-prefs --get default-netvm`; > [ -n "$NETVM" ] && qvm-start -q --no-guid $NETVM (code=exited, > status=0/SUCCESS) > Main PID: 4150 (code=exited, status=0/SUCCESS) >CGroup: /system.slice/qubes-netvm.service > > Jan 07 15:31:01 dom0 systemd[1]: Starting Qubes NetVM startup... > Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session opened > for user user1 by (uid=0) > Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session closed > for user user1 > Jan 07 15:31:05 dom0 runuser[5102]: pam_unix(runuser:session): session opened > for user user1 by (uid=0) > Jan 07 15:31:11 dom0 runuser[5102]: pam_unix(runuser:session): session closed > for user user1 > Jan 07 15:31:11 dom0 systemd[1]: Started Qubes NetVM startup. > > HOWEVER, after startup I can do in dom0 terminal: > > sudo /bin/sh -c 'echo :04:00.0 > /sys/bus/pci/drivers/pciback/permissive' > > and the permissive mode is set allright (and yes, the device I want to > "permissivize" really is :04:00.0 on my machine. Huge coincidence, I too > was amused) > > I have to then reboot the VM (which is mighty annoying because it's a netvm) > and everything seems to work out allrightey (fingers crossed very intensely) > > Any pointers why it can't see the target device "right away" ? Try setting the pci_strictreset to false in the preferences of the target vm. -- 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/505e8da7-b012-431d-ab91-b00489022311%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Problem setting permissive mode for a PCI device
Hello everyone! Trying to follow the steps outlined here: https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues Created a service, BUT it fails to start systemctl status gives qubes-netvm.service - Qubes NetVM startup Loaded: loaded (/usr/lib/systemd/system/qubes-netvm.service; enabled; vendor preset: enabled) Active: active (exited) since Sat 2017-01-07 15:31:11 EAT; 35min ago Process: 4150 ExecStart=/bin/sh -c NETVM=`qubes-prefs --get default-netvm`; [ -n "$NETVM" ] && qvm-start -q --no-guid $NETVM (code=exited, status=0/SUCCESS) Main PID: 4150 (code=exited, status=0/SUCCESS) CGroup: /system.slice/qubes-netvm.service Jan 07 15:31:01 dom0 systemd[1]: Starting Qubes NetVM startup... Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session opened for user user1 by (uid=0) Jan 07 15:31:05 dom0 runuser[5099]: pam_unix(runuser:session): session closed for user user1 Jan 07 15:31:05 dom0 runuser[5102]: pam_unix(runuser:session): session opened for user user1 by (uid=0) Jan 07 15:31:11 dom0 runuser[5102]: pam_unix(runuser:session): session closed for user user1 Jan 07 15:31:11 dom0 systemd[1]: Started Qubes NetVM startup. HOWEVER, after startup I can do in dom0 terminal: sudo /bin/sh -c 'echo :04:00.0 > /sys/bus/pci/drivers/pciback/permissive' and the permissive mode is set allright (and yes, the device I want to "permissivize" really is :04:00.0 on my machine. Huge coincidence, I too was amused) I have to then reboot the VM (which is mighty annoying because it's a netvm) and everything seems to work out allrightey (fingers crossed very intensely) Any pointers why it can't see the target device "right away" ? -- 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/bebcd78c-aa74-4dcb-ac58-8ea70f137b5a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Boot fails after update
Hello All, I'm trying out Qubes as it looks very good. I installed it, ran the updates and then when I rebooted it drops to the emergency shell. There are lots of the following type error - [6.27831] Dev sdj: unable to read RDB block 1 and the last messages are - Warning: /dev/mapper/qubes_dom0-root does not exist Warning: /dev/qubes_dom0/root does not exist Warning: /dev/qubes_dom0/swap does not exist Warning: crypto LUKS UUID (long hex string) not found. I'm testing Qubes on a Dell Poweredge R710 using RAID. It seemed fine until I ran the updates. I have had a look on the Qubes site but think I need some help to get me started! -- Best regards, Chris P.S. Drowning in email? I use SaneBox to instantly clean up my Inbox: http://sanebox.com/t/k3bk9 -- 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/MTAwMDAwOC5hbmF0b21pYw.1483791202%40quikprotect. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] My Intel system doesn't have Vt-x and Vt-d, please help me understand the implications.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On 2017-01-06 17:37, Marek Marczykowski-Górecki wrote: > On Fri, Jan 06, 2017 at 08:04:08PM +, 5vo30m+lpi66xm176ugr7ruk via > qubes-users wrote: >> Hi everyone! > >> First off happy new year! :) > >> To get into the subject, I'm trying to get as many Qubes users around me as >> possible to convert my family and friends from Windowsism to Qubism. However >> in some cases I see that the Intel®™ (backdoor℠ inside®) hardware that they >> have does not support VT-x and VT-d. > >> So I would like to better understand the implications of this. From the User >> FAQ: > >> https://www.qubes-os.org/doc/user-faq/#can-i-install-qubes-on-a-system-without-vt-x > >> I understand that this means that: > >> o Not being able to use fully virtualized VMs (e.g., Windows-based qubes) > >> o No security benefit in having a separate NetVM > >> But the points I wont to understand are: > >> ~ Does this mean that one wont be able to install Windows in a VM in such >> system (that's it?)? > Yes. > >> What does fully virtualized VM really mean? > > https://www.qubes-os.org/doc/glossary/#hvm > > In short: a VM running OS not necessary modified to be running in a VM. > >> ~ How is this relevant practically speaking? In other words, could an >> attacker deploy malware to NetVM (from an AppVM that is connected to the >> NetVM)? If not, in which situations can attacker get to the NetVM and >> therefore to dom0? > > The way you've descried, or using some remote attack directly on NetVM - > because NetVM is what is facing external network directly. > Another, additional way of answering this question: "On a system without VT-d, everything should work in the same way, except there will be no real security benefit to having a separate NetVM, as an attacker could always use a simple DMA attack to go from the NetVM to Dom0." Then read this: https://www.qubes-os.org/doc/user-faq/#what-is-a-dma-attack Basically, read the next two FAQ entries after the one you linked. :) - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcKbyAAoJENtN07w5UDAw380P/3vH/GlHBGsYV5qmU1fDdRu8 JHz9ZG5tWVIba219sYMNCHa4F+Wc907prEyooG0XRBwtIKoZ/qXP5bMKX6WBuXSw 8wQfEewrWvSU7vCGW67DEc4OYcwKNwiV8mX6ebFSt/dtKHshLmyCylnaJ0Sg59Kn PwIdkG1E7Gzt7pt0Ti2WUzjKeWMY0GWZm9kuYG5DL1iRguanGrmVyn+RRAZMn5af WRrP7GBFAK7ykOWP4zTpZ8onlL7En9s+MNp7Mn6hyDyIYKvwQ2LcE63p2H8dozku 5cDGkxWJIB/dqhd9URnVhq/cVKdXvHXGztGBR62tSpq2neuYhi8FyTpdKqxuspvV 1zMsBGp8DP8Q03Mf8AeJ7DLfrHfZYi1HmwhYa3uOZnntAHd3x93QRXOyiWiLr88e aBiYHCQMdy+o8FMrikvPfQi8Wd7JGSqmzOzw8TMhnuQ8QlZCa6GdYfQa23oBi4El t12M2RBykur2grLfRf/wUcMiTRxZ1WTVXrY4YPDoH+79QzEV5xhJrrlWKFYEYySG SsnOpToBa/iHwWtrVKqDfubca1umDnSRjYJuKjWourzO5LEpG9hkjFdUg0olTMet C05tE/Hlg8+PeLg2y06PCavQZK7nRkN7L3U0SEYck8RVovslKmbUeKFWtMM+rqQi ZPisdXAjwa+YtnEsdwbz =EXu4 -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/13f1c956-855f-cdaf-6f6e-a4331e0189b9%40qubes-os.org. 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 00:21, 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, (Not to mention the "$releasever" variable!) > but I have to ask: Why not try following the instructions I > provided in the previous email (to which you're replying)? > - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcKVLAAoJENtN07w5UDAw+x0QAMqIu7UH7UMitYNZXA1J1YYW Xxc47TZ3o0YJg8yMpFTXgYdX2Hh2M1+EMpGRMIdRZNFavAhx85EI8fYbTY6YIMeI ONDDH+JgrA5UaD07QffSkia882jscdMVQCNlxVHIMMl5QPyGc8Gt5+00CJ1n0/uI Z0t9dwdLSIWxfihbdrQIcWT53C9YU8eH9sj5tIMWpEoCdeLufoJ9MzBQTvzLyPHe JL+we/ifYyhmHMPMBaOn00LiFGkxIK86o06DBFHZdlm+3oO0C/9YoQwXXTjC2YvD pUjSulT43xqgAydlPOQbiUJcnUNCkSHOQdm9h/LdxOROQrDEB8GXvzLQXZZksaPw anEq9pkyTyEYI5WbxtO77oKclk3ipcRtKNnKRBBkMXlBApSBvWAb/0iiKDNKeUWj vBSPJ8aOCJP0fh2Omaw3c4ByaitMDxTyFW4qcK22c/ISVzTQvR+hPhpGQLpovfAK 1GHPHTmt7akgz+VuI1BX1dv9fkpJweq3DK6pVffd4psGlsg4kOcmbPBORU5Tdd/Z JKPZqhftvhzGOC+2GHzWRuP963V07idsHpqms/OpvZ9MGhuVTtRrETCYeVhQ7GWe kHRZz6rbf7352jrp9mcBILFCPd9i2Df9lctKCVLLrmsC8MISV+HH7bKsOuthX/rp ht913zVMJoIIM4hXf0e7 =ADY/ -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
Re: [qubes-users] Re: Fedora Desktop in Qubes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 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)? - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org -BEGIN PGP SIGNATURE- iQIcBAEBCgAGBQJYcKUHAAoJENtN07w5UDAw2YIQAM/02kvQYHz23LcoAEZlhtjm DIcnTGow1qt8e5M6xBGUg+dZ0E6X1XQp6zyjZUabNnbTx1qLU1dFkMNFdb++CD9O juRx2pzaEDTYwkQeF/ww1L3H26aW+YsOPsQ141+lJUkUX0QjvriLO49R4MaoBInS ZTBM9jchLH3hMtruLzV4kDi2ctd4357RnjPOflv/7Upsp41uQ/zfsG3fkCXiqvWo 2LoHbuoCuc/AhwByY4i8nVxA2oX4YiSfMhwD+hXNzdpgoYBYRLFLamfnccz8Ea65 KM24TCFxGijkwlQl819WwP24WDYO7UiktPWji+4mUR0XCK6XdPHNeUXJCOtQXzH5 H+tpRxICDuRG4VL5LTgHfpm2Ut7Pv57LE2mn4EUKratUG8RicATGO5V9jgTb9ORV pRFiK0fRPacG+3fxvLTXU9ZfBIekFuDJVX4SZe8MFfsUTIvE5SVyimPUtQ92xPDz x2mKGb4uqavTTXjlqDs9IAb6OGNNWJcUkOXUknmzVYRTtkWqUaWg0T1it7tVUQNi JrXZPebWiu6ksiICUiKHIUw7PrrXmA3T8S5KyUSVBwOX8Dv4zrlppBz8/5pRb4Up 5l3Mmihxm6WIgVMKBQK6Bjh49gDOz0UXbR6z+7szEBbnriSCPwb9ERSrSyNf2BgD /FF8jo893PdeHbXyHwAa =2EmG -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/9504e4bb-f263-e4d3-2c10-8e5d5a2b9408%40qubes-os.org. For more options, visit https://groups.google.com/d/optout.
