[qubes-users] Syncing clock with ntp
I have always had a problem with my system clock losing time. My understanding is that the ClockVM, which is usually sys-net, runs ntp and and communicates the time to dom0, which communicates the time to all of the other VMs. I don't know exactly what makes sys-net the ClockVM, but I noticed that it was not running the service clocksync (I noticed this service in sys-net of a different machine), so I added clocksync as a service to sys-net of the problem machine. I assumed ntp would be running on sys-net, but it was not. And when I checked the other system (which already had clocksync as a service), I see that it too does not have ntp running. I don't know how sys-net will get network time without ntp running. Any suggestions on how to get my clock synced with network time? Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/1432b667-3372-4d71-831c-f2b7cf376656%40googlegroups.com.
Re: [qubes-users] Thunderbird Addon for launch attachments in dispVMs
Thank you Sven and Andrew. John On Thursday, October 3, 2019 at 7:44:10 PM UTC-4, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2019-10-03 4:39 PM, Sven Semmler wrote: > > On 10/3/19 3:05 PM, John Maher wrote: > >> All of a sudden Thunderbird (68.1.0) no longer has the Qubes > >> addon that allows the launching of attachments in dispVMs. Did > >> something change that I can change back? > > > > It's Thunderbird that changed, but the issue is already fixed. > > Update the thunderbird-qubes package from the current-testing repo > > and you're back in business! > > > > /Sven > > > > For further details, please see: > > https://github.com/QubesOS/qubes-issues/issues/5318 > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl2Wh7sACgkQ203TvDlQ > MDAbyQ/+MZGermCrWEBopfGZ78V4ld4e1fnhAmV43Gqkr1em4bu6puqgBmUZL3K+ > aO8RHbx4qcxNi4qdk+avbRy03DVf2u6lc7tRUsD77WMWYle55PtvGs09/+eX/igb > ZqPYa3Res0BKhLrvCaQVIAqrs3ql5LjjmFCNCRtNDqK93bo5zYI5cZjT2WhMl9tm > zBZNhzV9q/MrHTPpLcxZc1pHPU4kTVqa8TrBDxM6yrt2UnmNzxxRYGbenIFU2X0k > A0lcY3TgAXW9n0AOLWeTv5WYln7I8TrVN3CR7+lbXUt9pBAtS9w1LHYmGrKDK3/y > IkY9gxw+1JGBOzj7qtCF6tUl5yQN7HYPLhlbEkz4I2pEl62e98LeJf43wVMyyqNx > WCDVKUyqwrPgiJMpvw69Jo1czu/7DTeekewamZPAyN4e34ocnXMW8BqVPij9fjJn > S6DOc220rVH1QtAYIFGIrC0AxkJFxrTWrS1NMmefuOxW+Kjra80OCM1/McNo1sQq > SK2ktFSq0ZeYRIqawvKi+L0oUHIEKtRIRnzm/w+FhhewFxZLuCZuHLyjimWQnV1U > n6OCtlHKJnzVlM1u1fwSyefFZRWqVDaLE98U9pPoNd9KhsYTy2mP6PCNOs2Q3lES > S+kDvtK6PL6pMpZDaK/pz++QiZch1IRX9fTMXj3T6I5JsiGweLs= > =Z9xR > -END PGP SIGNATURE- > > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/356afb82-5eda-44e1-be0e-fe2b654854a7%40googlegroups.com.
[qubes-users] Thunderbird Addon for launch attachments in dispVMs
All of a sudden Thunderbird (68.1.0) no longer has the Qubes addon that allows the launching of attachments in dispVMs. Did something change that I can change back? Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a4bb496c-1997-49b9-80d2-1825fc511f61%40googlegroups.com.
Re: [qubes-users] Using an OnlyKey
On Friday, November 9, 2018 at 10:01:29 AM UTC-5, pkra...@gmail.com wrote: > > So the way mine works is actually consistent with using it on non-Qubes > > systems. I insert the onlykey, and it blinks a little, and then no lights > > display. I can then enter my PIN and the green light will go on. At that > > point the onlykey will output info from any of the buttons, but TOTP won't > > work. Then I open the onlykey app and then TOTP will work as well. > > >I used info from this page > >https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the > >OnlyKey to operate as a USB keyboard. > > What kernel version do you have? Did LED start working after you modified > /etc/qubes-rpc/policy/qubes.InputKeyboard or it was working even before? > > Mine OnlyKey still works with other OSes but doesn't work in Qubes for some > reason. I'm sorry but I don't remember exactly when the OnlyKey started working (immediately or after those modifications you mentioned). -- 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/a3043e5b-e06d-4fd8-832a-83f896697a50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using an OnlyKey
On Monday, November 5, 2018 at 11:16:59 AM UTC-5, pkra...@gmail.com wrote: > On Monday, October 15, 2018 at 9:37:48 AM UTC-4, John Maher wrote: > > On Friday, October 12, 2018 at 1:17:37 AM UTC-4, awokd wrote: > > > g80vmgm...@riseup.net wrote on 10/12/18 5:07 AM: > > > > John Maher: > > > >> I have an OnlyKey and have been unable to figure out how to make use > > > >> of it in Qubes OS 4.0. > > > >> > > > >> Relevant info: > > > >> > > > >> * OnlyKey requires either its app being opened on the computer or > > > >> one's ability to go to https://apps.crp.to (simply via a browser) in > > > >> order to set its time. > > > >> * I used info from this page > > > >> https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the > > > >> OnlyKey to operate as a USB keyboard. Doing this resulted in the > > > >> OnlyKey being attached to sys-usb and outputting text (password info) > > > >> in dom0 and any other qube. > > > >> * Although the OnlyKey can output like a USB keyboard in any qube, it > > > >> cannot get its time set without being specifically attached to an > > > >> appVM that either has the OnlyKey app or can access > > > >> https://apps.crp.to, so TOTP will not function. > > > >> * Using the yellow drop down icon to attach the OnlyKey to a qube that > > > >> has the app results in (1) the time on the OnlyKey being set, and (2) > > > >> the OnlyKey no longer working as a USB keyboard anywhere. > > > >> * Detaching from the qube does not restore the OnlyKey's ability to > > > >> function as a USB keyboard. > > > >> > > > >> Short of installing the OnlyKey app in sys-usb, is there anything else > > > >> I can try? (And I don't even know if that would work.) > > > >> > > > >> Even if I decided it was ok to install the app in sys-usb, sys-usb is > > > >> based on Fedora, and OnlyKey only has a deb package. Installing on > > > >> Fedora has proven to be very problematic. > > > >> > > > >> Thanks for any help you can provide. > > > >> > > > >> John > > > >> > > > > > > > > Hi John, > > > > > > > > I don't have an OnlyKey and unfortunately probably can't really help you > > > > to debug the issues with it not being able to act again as an HID device > > > > after attaching it directly to a VM. > > > > > > > > However, you can absolutely use a Debian-based VM as your sys-usb qube; > > > > just install the Debian 9 template and set your sys-usb qube to use it > > > > as its template. Also make sure the qubes-usb-proxy package is > > > > installed. > > > > > > > > As for the HID issues, I do have one suggestion: have you tried not only > > > > detaching the device from the AppVM, but also physically removing the > > > > USB device and re-inserting it? > > > > > > No OnlyKey either, but I think it is possible to have two USB > > > "keyboards" in Qubes if you edit the file described here: > > > https://www.qubes-os.org/doc/usb/#r32-manual. > > > > Thanks for your responses. I figured out a solution. > > > > I figured out a way to use OnlyKey with Qubes OS. I suspect I've violated > > some basic security principles relative to how Qubes is intended to be > > used, but I accept the compromise, which I think (hope) is minimal. > > > > Because an OnlyKey needs a time source in order for its TOTP feature to > > function, either the OnlyKey app (standalone or Chrome extension) or > > navigating to https://apps.crp.to, after the OnlyKey is inserted into a USB > > port, need to be available. In Qubes, I discovered that inserting the > > OnlyKey (and unlocking it with the PIN) and attaching it to the appVM where > > I want to use it resulted in the OnlyKey not functioning as a keyboard, > > which is needed to do its job. In dom0, adding this line to the top of > > /etc/qubes-rpc/policy/qubes.InputKeyboard (see > > https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard) allowed the > > OnlyKey to operate as a keyboard in all VMs (without attaching the OnlyKey > > to a VM): > > > > sys-usb dom0 allow,user=root > > > > However, to use TOTP it still needed a
Re: [qubes-users] Using an OnlyKey
On Wednesday, October 24, 2018 at 9:19:52 PM UTC-4, Stumpy wrote: > On 10/15/18 9:37 AM, John Maher wrote: > > On Friday, October 12, 2018 at 1:17:37 AM UTC-4, awokd wrote: > >> g80vmgm...@riseup.net wrote on 10/12/18 5:07 AM: > >>> John Maher: > >>>> I have an OnlyKey and have been unable to figure out how to make use of > >>>> it in Qubes OS 4.0. > >>>> > >>>> Relevant info: > >>>> > >>>> * OnlyKey requires either its app being opened on the computer or one's > >>>> ability to go to https://apps.crp.to (simply via a browser) in order to > >>>> set its time. > >>>> * I used info from this page > >>>> https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the > >>>> OnlyKey to operate as a USB keyboard. Doing this resulted in the OnlyKey > >>>> being attached to sys-usb and outputting text (password info) in dom0 > >>>> and any other qube. > >>>> * Although the OnlyKey can output like a USB keyboard in any qube, it > >>>> cannot get its time set without being specifically attached to an appVM > >>>> that either has the OnlyKey app or can access https://apps.crp.to, so > >>>> TOTP will not function. > >>>> * Using the yellow drop down icon to attach the OnlyKey to a qube that > >>>> has the app results in (1) the time on the OnlyKey being set, and (2) > >>>> the OnlyKey no longer working as a USB keyboard anywhere. > >>>> * Detaching from the qube does not restore the OnlyKey's ability to > >>>> function as a USB keyboard. > >>>> > >>>> Short of installing the OnlyKey app in sys-usb, is there anything else I > >>>> can try? (And I don't even know if that would work.) > >>>> > >>>> Even if I decided it was ok to install the app in sys-usb, sys-usb is > >>>> based on Fedora, and OnlyKey only has a deb package. Installing on > >>>> Fedora has proven to be very problematic. > >>>> > >>>> Thanks for any help you can provide. > >>>> > >>>> John > >>>> > >>> > >>> Hi John, > >>> > >>> I don't have an OnlyKey and unfortunately probably can't really help you > >>> to debug the issues with it not being able to act again as an HID device > >>> after attaching it directly to a VM. > >>> > >>> However, you can absolutely use a Debian-based VM as your sys-usb qube; > >>> just install the Debian 9 template and set your sys-usb qube to use it > >>> as its template. Also make sure the qubes-usb-proxy package is installed. > >>> > >>> As for the HID issues, I do have one suggestion: have you tried not only > >>> detaching the device from the AppVM, but also physically removing the > >>> USB device and re-inserting it? > >> > >> No OnlyKey either, but I think it is possible to have two USB > >> "keyboards" in Qubes if you edit the file described here: > >> https://www.qubes-os.org/doc/usb/#r32-manual. > > > > Thanks for your responses. I figured out a solution. > > > > I figured out a way to use OnlyKey with Qubes OS. I suspect I've violated > > some basic security principles relative to how Qubes is intended to be > > used, but I accept the compromise, which I think (hope) is minimal. > > > > Because an OnlyKey needs a time source in order for its TOTP feature to > > function, either the OnlyKey app (standalone or Chrome extension) or > > navigating to https://apps.crp.to, after the OnlyKey is inserted into a USB > > port, need to be available. In Qubes, I discovered that inserting the > > OnlyKey (and unlocking it with the PIN) and attaching it to the appVM where > > I want to use it resulted in the OnlyKey not functioning as a keyboard, > > which is needed to do its job. In dom0, adding this line to the top of > > /etc/qubes-rpc/policy/qubes.InputKeyboard (see > > https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard) allowed the > > OnlyKey to operate as a keyboard in all VMs (without attaching the OnlyKey > > to a VM): > > > >sys-usb dom0 allow,user=root > > > > However, to use TOTP it still needed access to the app or to > > https://apps.crp.to. But, again, when I attached the OnlyKey to an appVM, > > the OnlyKey stopped functioning as a keyboar
[qubes-users] Re: Errors Installing a .deb File in Qubes 4.0
On Wednesday, October 24, 2018 at 8:23:16 PM UTC-4, Alex Winter wrote: > I have figured it out. I wasn't extracting the directory properly and was > giving me the incorrect file. > > I have installed the application now but when I open it up, it doesn't > recognise the onlykey device in the application. It also doesn't show up in > my devices on the top right of the screen in dom0 when I plug it in so I cant > attach it to any AppVM. However, the device still outputs the correct > passwords when pressing the corrosponding button on the onlykey which I find > odd. > > I have qubes 4.0 setup on a laptop. It is installed on a USB drive aswell > which probably is causing most of my issues. Alex, as I mentioned here https://groups.google.com/d/msg/onlykey/z3pRlCO8Hc4/WB5dJEojCgAJ, I think you will have much better luck if you create a USB qube first. -- 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/32aa929f-a891-4ac3-8242-06728b27314c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Using an OnlyKey
On Friday, October 12, 2018 at 1:17:37 AM UTC-4, awokd wrote: > g80vmgm...@riseup.net wrote on 10/12/18 5:07 AM: > > John Maher: > >> I have an OnlyKey and have been unable to figure out how to make use of it > >> in Qubes OS 4.0. > >> > >> Relevant info: > >> > >> * OnlyKey requires either its app being opened on the computer or one's > >> ability to go to https://apps.crp.to (simply via a browser) in order to > >> set its time. > >> * I used info from this page > >> https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the > >> OnlyKey to operate as a USB keyboard. Doing this resulted in the OnlyKey > >> being attached to sys-usb and outputting text (password info) in dom0 and > >> any other qube. > >> * Although the OnlyKey can output like a USB keyboard in any qube, it > >> cannot get its time set without being specifically attached to an appVM > >> that either has the OnlyKey app or can access https://apps.crp.to, so TOTP > >> will not function. > >> * Using the yellow drop down icon to attach the OnlyKey to a qube that has > >> the app results in (1) the time on the OnlyKey being set, and (2) the > >> OnlyKey no longer working as a USB keyboard anywhere. > >> * Detaching from the qube does not restore the OnlyKey's ability to > >> function as a USB keyboard. > >> > >> Short of installing the OnlyKey app in sys-usb, is there anything else I > >> can try? (And I don't even know if that would work.) > >> > >> Even if I decided it was ok to install the app in sys-usb, sys-usb is > >> based on Fedora, and OnlyKey only has a deb package. Installing on Fedora > >> has proven to be very problematic. > >> > >> Thanks for any help you can provide. > >> > >> John > >> > > > > Hi John, > > > > I don't have an OnlyKey and unfortunately probably can't really help you > > to debug the issues with it not being able to act again as an HID device > > after attaching it directly to a VM. > > > > However, you can absolutely use a Debian-based VM as your sys-usb qube; > > just install the Debian 9 template and set your sys-usb qube to use it > > as its template. Also make sure the qubes-usb-proxy package is installed. > > > > As for the HID issues, I do have one suggestion: have you tried not only > > detaching the device from the AppVM, but also physically removing the > > USB device and re-inserting it? > > No OnlyKey either, but I think it is possible to have two USB > "keyboards" in Qubes if you edit the file described here: > https://www.qubes-os.org/doc/usb/#r32-manual. Thanks for your responses. I figured out a solution. I figured out a way to use OnlyKey with Qubes OS. I suspect I've violated some basic security principles relative to how Qubes is intended to be used, but I accept the compromise, which I think (hope) is minimal. Because an OnlyKey needs a time source in order for its TOTP feature to function, either the OnlyKey app (standalone or Chrome extension) or navigating to https://apps.crp.to, after the OnlyKey is inserted into a USB port, need to be available. In Qubes, I discovered that inserting the OnlyKey (and unlocking it with the PIN) and attaching it to the appVM where I want to use it resulted in the OnlyKey not functioning as a keyboard, which is needed to do its job. In dom0, adding this line to the top of /etc/qubes-rpc/policy/qubes.InputKeyboard (see https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard) allowed the OnlyKey to operate as a keyboard in all VMs (without attaching the OnlyKey to a VM): sys-usb dom0 allow,user=root However, to use TOTP it still needed access to the app or to https://apps.crp.to. But, again, when I attached the OnlyKey to an appVM, the OnlyKey stopped functioning as a keyboard, even when I detached it from the appVM. So, I did the following: 1. Temporarily provided Internet access to sys-usb. 2. Opened Chrome and installed the OnlyKey extension. 3. Disabled the sys-usb VM's Internet access. Now, after inserting the OnlyKey and entering its PIN, I can open the OnlyKey Chrome app (which does not need Internet access to function), resulting in the OnlyKey getting its time set. Because of the previous edit of "qubes.InputKeyboard", the OnlyKey functions as a keyboard and all is well. I'm happy to hear comments or cautions regarding this. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2e34c68f-8488-4188-a2f2-a6e5e68ad118%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Using an OnlyKey
I have an OnlyKey and have been unable to figure out how to make use of it in Qubes OS 4.0. Relevant info: * OnlyKey requires either its app being opened on the computer or one's ability to go to https://apps.crp.to (simply via a browser) in order to set its time. * I used info from this page https://www.qubes-os.org/doc/usb/#how-to-use-a-usb-keyboard to get the OnlyKey to operate as a USB keyboard. Doing this resulted in the OnlyKey being attached to sys-usb and outputting text (password info) in dom0 and any other qube. * Although the OnlyKey can output like a USB keyboard in any qube, it cannot get its time set without being specifically attached to an appVM that either has the OnlyKey app or can access https://apps.crp.to, so TOTP will not function. * Using the yellow drop down icon to attach the OnlyKey to a qube that has the app results in (1) the time on the OnlyKey being set, and (2) the OnlyKey no longer working as a USB keyboard anywhere. * Detaching from the qube does not restore the OnlyKey's ability to function as a USB keyboard. Short of installing the OnlyKey app in sys-usb, is there anything else I can try? (And I don't even know if that would work.) Even if I decided it was ok to install the app in sys-usb, sys-usb is based on Fedora, and OnlyKey only has a deb package. Installing on Fedora has proven to be very problematic. Thanks for any help you can provide. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c9c1c45e-6421-4cdd-85ac-374753f2b5af%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: What do you guys think about the "OnlyKey"
On Friday, November 3, 2017 at 2:38:06 PM UTC-4, Fabian wrote: > A lot of people know the Yubikey, but the Yubikey has one big "problem": It > has only 2 slots for Passwords. > I thought about storing my password for my disk encryption on such a key, so > I can a) use a stronger passphrase and b) don't have to type it in every > time, especially when I am at University, ... > > So I found the "OnlyKey" which is basically a Yubikey, just far less known > and it has 12+12 Slots. > https://crp.to/p/ > > I ordered one plus a small purse which I can attach to my belt, so I always > have the key with me. > What dou you think about it - is it a good idea or am I missing something > really important? > > > Negatives are: > -Product comes from the US (Yubikey aswell) > -Setting it up is done over a Google Chrome Addon (I had a bad feeling about > it, so I just made a new VM, installed chrome, disabled the network > connection, set up the key and then deleted the VM). > > The price is okay so far (46$), in my case it nearly doubled up because of > taxes (Germany) and because I've chosen Priority Shipping from Amazon US, > instead of the standard shipping (which takes approximately 2-3 Weeks). Hi Fabian, I hoping you'll get this message. I have an OnlyKey now and cannot get it to work properly (won't type when button is touched). Have you had any luck getting it to work with Qubes OS 4.0? John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0ca6a6e3-0af1-4c56-ac75-7d4c684cc29d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: debian-9 template
On Tuesday, September 11, 2018 at 5:06:49 PM UTC-4, awokd wrote: > On Tue, September 11, 2018 2:49 pm, John Maher wrote: > > On Tuesday, September 11, 2018 at 9:02:53 AM UTC-4, awokd wrote: > > > >> On Tue, September 11, 2018 12:27 pm, John Maher wrote: > >> > >>> On Tuesday, September 11, 2018 at 8:15:50 AM UTC-4, John Maher wrote: > >>> > >>> > >>>> On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > >>>> > >> > >>>>> > >>>>> I don't get it either, especially with a fresh install. Did you > >>>>> test before running any updates? If you enable debug mode, any > >>>>> hints in the console or related VM log files? > >>>> > >>>> awokd, I did test before running updates. The template definitely > >>>> starts out appearing (or having?) no applications. > >>>> > >>>> I don't know how to enable debug mode, and I don't see anything in > >>>> the official documentation. I'm also not familiar with the console, > >>>> unless you're referring to a dom0 terminal. Any guidance would be > >>>> wonderful. Thanks. > >>>> > >>>> > >>>> > >>>> John > >>>> > >>>> > >>> > >>> I decided to see if I could install the debian-8 template with > >>> different results from the debian-9 template. Sure enough, by default > >>> terminal if displayed as an available app under debian-8, and within > >>> debian-8 Qubes Settings there are plenty of expected apps in the > >>> Applications tab. I'll > >>> now try to upgrade debian-8 to debian-9 (using a different name) and > >>> see what I get. > >> > >> Same behaviour on a fresh install of 4.0, right? Try this in dom0: > >> > > > > Yes, this all started with a fresh install of 4.0 on new hardware. > > > > > >> > >> 1) qvm-run debian-9 gnome-terminal > >> > > > > output: > > > > > > Running 'gnome-terminal' on debian-9 > > > > > > Very odd behavior. I have never gotten a terminal windows when running > > the above command, but the time I ran the command in response to your > > suggestion I actually ended up with a terminal window! Subsequent > > attempts have resulted in no terminal window. > > Have you ever been able to update that debian-9 template? Maybe it's ok on > first boot but not the rest. > > > > > > > Waiting for /dev/xvdd device... > > mount: /dev/xvdd is write-protected, mounting read-only > > [5.836088] EXT4-fs (xvdd): mounting ext3 file system using the ext4 > > subsystem [5.840428] EXT4-fs (xvdd): mounted filesystem with ordered > > data mode. Opts: (null) switch_root: failed to mount moving /dev to > > /sysroot/dev: Invalid argument > > switch_root: forcing unmount of /dev > > switch_root: failed to mount moving /proc to /sysroot/proc: Invalid > > argument switch_root: forcing unmount of /proc > > switch_root: failed to mount moving /sys to /sysroot/sys: Invalid argument > > switch_root: forcing unmount of /sys > > switch_root: failed to mount moving /run to /sysroot/run: Invalid argument > > switch_root: forcing unmount of /run > > Mine shows this too- xvdd is the kernel. > > > Starting udev Kernel Device Manager... > > [6.243442] systemd-journald[205]: Received request to flush runtime > > journal from PID 1 [6.245978] qubesdb-daemon[264]: segfault at > > 76d6ff72eff8 ip 76d6ff51bf64 sp 76d6ff72f000 error 6 in > > ld-2.24.so[76d6ff512000+23000] [.[0;1;31mFAILED.[0m] Failed to start Qubes > > DB agent. > > See 'systemctl status qubes-db.service' for details. > > [.[0;32m OK .[0m] Started Flush Journal to Persistent Storage. > > Starting Load/Save Random Seed... > > Starting Init Qubes Services settings... > > [.[0;32m OK .[0m] Started udev Coldplug all Devices. > > [.[0;1;31mFAILED.[0m] Failed to start Load/Save Random Seed. > > See 'systemctl status systemd-random-seed.service' for details. > > > > > > . > > > > > > Starting Permit User Sessions... > > Starting /etc/rc.local Compatibility... > > Starting Qubes misc post-boot actions... > > [.[0;32m OK .[0m] Started Permit User Sessions. > > [.[0;32m OK .[0m] Started /etc/rc.local Compatibility. > > [9.738613] qrexec-agent[537]: segf
Re: [qubes-users] Re: debian-9 template
On Tuesday, September 11, 2018 at 10:49:43 AM UTC-4, John Maher wrote: > On Tuesday, September 11, 2018 at 9:02:53 AM UTC-4, awokd wrote: > > On Tue, September 11, 2018 12:27 pm, John Maher wrote: > > > On Tuesday, September 11, 2018 at 8:15:50 AM UTC-4, John Maher wrote: > > > > > >> On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > > > > >>> > > >>> I don't get it either, especially with a fresh install. Did you test > > >>> before running any updates? If you enable debug mode, any hints in the > > >>> console or related VM log files? > > >> > > >> awokd, I did test before running updates. The template definitely > > >> starts out appearing (or having?) no applications. > > >> > > >> I don't know how to enable debug mode, and I don't see anything in the > > >> official documentation. I'm also not familiar with the console, unless > > >> you're referring to a dom0 terminal. Any guidance would be wonderful. > > >> Thanks. > > >> > > >> > > >> John > > >> > > > > > > I decided to see if I could install the debian-8 template with different > > > results from the debian-9 template. Sure enough, by default terminal if > > > displayed as an available app under debian-8, and within debian-8 Qubes > > > Settings there are plenty of expected apps in the Applications tab. I'll > > > now try to upgrade debian-8 to debian-9 (using a different name) and see > > > what I get. > > > > Same behaviour on a fresh install of 4.0, right? Try this in dom0: > > Yes, this all started with a fresh install of 4.0 on new hardware. > > > > > 1) qvm-run debian-9 gnome-terminal > > output: > > Running 'gnome-terminal' on debian-9 > > Very odd behavior. I have never gotten a terminal windows when running the > above command, but the time I ran the command in response to your suggestion > I actually ended up with a terminal window! Subsequent attempts have resulted > in no terminal window. > > > 2) sudo xl dmesg [look for any related errors at the bottom] > > No errors. Just many lines of > > (XEN) PCI add device :xx:xx.x > > (with 'x' being various alpha numeric values). > > > 3) sudo journalctl -e [check errors again] > > No errors. Just a lot regarding my running sudo and references to pam. > > > 4) review /var/log/xen/console/guest-debian-9.log > > Here are some occurrences of 'fail', 'error', and 'seg': > > [0.002577] NMI watchdog: Perf event create on CPU 0 failed with -2 > > . > > [0.069536] dmi: Firmware registration failed. > > . > > Waiting for /dev/xvdd device... > mount: /dev/xvdd is write-protected, mounting read-only > [5.836088] EXT4-fs (xvdd): mounting ext3 file system using the ext4 > subsystem > [5.840428] EXT4-fs (xvdd): mounted filesystem with ordered data mode. > Opts: (null) > switch_root: failed to mount moving /dev to /sysroot/dev: Invalid argument > switch_root: forcing unmount of /dev > switch_root: failed to mount moving /proc to /sysroot/proc: Invalid argument > switch_root: forcing unmount of /proc > switch_root: failed to mount moving /sys to /sysroot/sys: Invalid argument > switch_root: forcing unmount of /sys > switch_root: failed to mount moving /run to /sysroot/run: Invalid argument > switch_root: forcing unmount of /run > > . > > Starting udev Kernel Device Manager... > [6.243442] systemd-journald[205]: Received request to flush runtime > journal from PID 1 > [6.245978] qubesdb-daemon[264]: segfault at 76d6ff72eff8 ip > 76d6ff51bf64 sp 76d6ff72f000 error 6 in ld-2.24.so[76d6ff512000+23000] > [.[0;1;31mFAILED.[0m] Failed to start Qubes DB agent. > See 'systemctl status qubes-db.service' for details. > [.[0;32m OK .[0m] Started Flush Journal to Persistent Storage. > Starting Load/Save Random Seed... > Starting Init Qubes Services settings... > [.[0;32m OK .[0m] Started udev Coldplug all Devices. > [.[0;1;31mFAILED.[0m] Failed to start Load/Save Random Seed. > See 'systemctl status systemd-random-seed.service' for details. > > . > > Starting Permit User Sessions... > Starting /etc/rc.local Compatibility... > Starting Qubes misc post-boot actions... > [.[0;32m OK .[0m] Started Permit User Sessions. > [.[0;32m OK .[0m] Started /etc/rc.local Compatibility. > [9.738613] qrexec-agent[537]: s
Re: [qubes-users] Re: debian-9 template
On Tuesday, September 11, 2018 at 9:02:53 AM UTC-4, awokd wrote: > On Tue, September 11, 2018 12:27 pm, John Maher wrote: > > On Tuesday, September 11, 2018 at 8:15:50 AM UTC-4, John Maher wrote: > > > >> On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > > >>> > >>> I don't get it either, especially with a fresh install. Did you test > >>> before running any updates? If you enable debug mode, any hints in the > >>> console or related VM log files? > >> > >> awokd, I did test before running updates. The template definitely > >> starts out appearing (or having?) no applications. > >> > >> I don't know how to enable debug mode, and I don't see anything in the > >> official documentation. I'm also not familiar with the console, unless > >> you're referring to a dom0 terminal. Any guidance would be wonderful. > >> Thanks. > >> > >> > >> John > >> > > > > I decided to see if I could install the debian-8 template with different > > results from the debian-9 template. Sure enough, by default terminal if > > displayed as an available app under debian-8, and within debian-8 Qubes > > Settings there are plenty of expected apps in the Applications tab. I'll > > now try to upgrade debian-8 to debian-9 (using a different name) and see > > what I get. > > Same behaviour on a fresh install of 4.0, right? Try this in dom0: Yes, this all started with a fresh install of 4.0 on new hardware. > > 1) qvm-run debian-9 gnome-terminal output: Running 'gnome-terminal' on debian-9 Very odd behavior. I have never gotten a terminal windows when running the above command, but the time I ran the command in response to your suggestion I actually ended up with a terminal window! Subsequent attempts have resulted in no terminal window. > 2) sudo xl dmesg [look for any related errors at the bottom] No errors. Just many lines of (XEN) PCI add device :xx:xx.x (with 'x' being various alpha numeric values). > 3) sudo journalctl -e [check errors again] No errors. Just a lot regarding my running sudo and references to pam. > 4) review /var/log/xen/console/guest-debian-9.log Here are some occurrences of 'fail', 'error', and 'seg': [0.002577] NMI watchdog: Perf event create on CPU 0 failed with -2 . [0.069536] dmi: Firmware registration failed. . Waiting for /dev/xvdd device... mount: /dev/xvdd is write-protected, mounting read-only [5.836088] EXT4-fs (xvdd): mounting ext3 file system using the ext4 subsystem [5.840428] EXT4-fs (xvdd): mounted filesystem with ordered data mode. Opts: (null) switch_root: failed to mount moving /dev to /sysroot/dev: Invalid argument switch_root: forcing unmount of /dev switch_root: failed to mount moving /proc to /sysroot/proc: Invalid argument switch_root: forcing unmount of /proc switch_root: failed to mount moving /sys to /sysroot/sys: Invalid argument switch_root: forcing unmount of /sys switch_root: failed to mount moving /run to /sysroot/run: Invalid argument switch_root: forcing unmount of /run . Starting udev Kernel Device Manager... [6.243442] systemd-journald[205]: Received request to flush runtime journal from PID 1 [6.245978] qubesdb-daemon[264]: segfault at 76d6ff72eff8 ip 76d6ff51bf64 sp 76d6ff72f000 error 6 in ld-2.24.so[76d6ff512000+23000] [.[0;1;31mFAILED.[0m] Failed to start Qubes DB agent. See 'systemctl status qubes-db.service' for details. [.[0;32m OK .[0m] Started Flush Journal to Persistent Storage. Starting Load/Save Random Seed... Starting Init Qubes Services settings... [.[0;32m OK .[0m] Started udev Coldplug all Devices. [.[0;1;31mFAILED.[0m] Failed to start Load/Save Random Seed. See 'systemctl status systemd-random-seed.service' for details. . Starting Permit User Sessions... Starting /etc/rc.local Compatibility... Starting Qubes misc post-boot actions... [.[0;32m OK .[0m] Started Permit User Sessions. [.[0;32m OK .[0m] Started /etc/rc.local Compatibility. [9.738613] qrexec-agent[537]: segfault at 7a9f3456bff8 ip 7a9f34368355 sp 7a9f3456c000 error 6 in ld-2.24.so[7a9f34352000+23000] [.[0;32m OK .[0m] Started Serial Getty on hvc0. [.[0;32m OK .[0m] Started Getty on tty1. [.[0;32m OK .[0m] Reached target Login Prompts. [.[0;32m OK .[0m] Started Qubes misc post-boot actions. [.[0;32m OK .[0m] Reached target Multi-User System. Starting Update UTMP about System Runlevel Changes... [.[0;32m OK .[0m] Started Update UTMP about System Runlevel Changes. [9.928387] qrexec-agent[572]: segfault at 7a9f3456bff8 ip 7a9f34368355 sp 7a9f3456c000 error 6 in ld-2.24
Re: [qubes-users] Re: debian-9 template
On Tuesday, September 11, 2018 at 8:15:50 AM UTC-4, John Maher wrote: > On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > > On Mon, September 10, 2018 6:28 pm, John Maher wrote: > > > On Friday, September 7, 2018 at 10:15:49 AM UTC-4, John Maher wrote: > > > > > >> On Friday, September 7, 2018 at 10:12:52 AM UTC-4, John Maher wrote: > > >> > > >>> On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote: > > >>> > > >>>> On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote: > > >>>> > > >>>>> On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote: > > >>>>> > > >>>>>> On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote: > > >>>>>> > > >>>>>>> On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, > > >>>>>>> higgin...@gmail.com wrote: > > >>>>>>>> tried --- > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> sudo qubes-dom0-update > > >>>>>>>> --enablerepo=qubes-templates-community --action=reinstall > > >>>>>>>> qubes-template-debian-9 > > >>>>>>>> > > >>>>>>>> Again it appears to reinstall - message appears saying > > >>>>>>>> successfully installed. > > >>>>>>>> > > >>>>>>>> Then try to start DEBIAN-9 VM and get > > >>>>>>>> "ERROR:VM directory does not exist: > > >>>>>>>> /var/lib/qubes/vm-templates/debian-9". > > >>>>>>>> > > >>>>>>>> > > >>>>>>>> Help! > > >>>>>>>> > > >>>>>>> > > >>>>>>> I just did a fresh install of Qubes OS 4.0 on new hardware > > >>>>>>> and I'm having the exact same problem. None of the > > >>>>>>> suggestions here have resulted in any change, although I did > > >>>>>>> not try: > > >>>>>>> > > >>>>>>> sudo qubes-dom0-update --enablerepo=qubes-templates-community > > >>>>>>> --action=reinstall qubes-template-debian-9 > > >>>>>>> > > >>>>>>> > > >>>>>>> and I'm not that interested in going that route. > > >>>>>>> > > >>>>>>> I've been using Qubes OS 3.2 for over a year now without this > > >>>>>>> type of problem. Any more suggestions or fixes? > > >>>>>>> > > >>>>>>> Thanks. > > >>>>>>> > > >>>>>>> > > >>>>>>> John > > >>>>>>> > > >>>>>>> > > >>>>>> > > >>>>>> Have you tried the obvious, and created the missing directory? > > >>>>>> Ownership should be root:qubes - compare to the other template > > >>>>>> directories. > > >>>>>> > > >>>>>> The only content is a symlink icon.png, pointing to > > >>>>>> /usr/share/icons/hicolor/128x128/devices/appvm-black/png > > >>>>>> You could create this yourself also. > > >>>>>> > > >>>>> > > >>>>> Unman, thanks for replying. I didn't run that command (sudo > > >>>>> qubes-dom0-update --enablerepo=qubes-templates-community > > >>>>> --action=reinstall qubes-template-debian-9), so I don't know if I > > >>>>> would get the same error message, but I do have the directory > > >>>>> /var/lib/qubes/vm-templates/debian-9. > > >>>>> > > >>>>> > > >>>>> I've performed an automatic re-install of the debian-9 template > > >>>>> twice and a manual re-install once. Still, no applications > > >>>>> display under Applications tab. I can't even run a terminal via > > >>>>> dom0 using: qvm-run debian-9 gnome-terminal > > >>>>> > > >>>>> I have to believe there is a simple comm
Re: [qubes-users] Re: debian-9 template
On Tuesday, September 11, 2018 at 6:15:43 AM UTC-4, awokd wrote: > On Mon, September 10, 2018 6:28 pm, John Maher wrote: > > On Friday, September 7, 2018 at 10:15:49 AM UTC-4, John Maher wrote: > > > >> On Friday, September 7, 2018 at 10:12:52 AM UTC-4, John Maher wrote: > >> > >>> On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote: > >>> > >>>> On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote: > >>>> > >>>>> On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote: > >>>>> > >>>>>> On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote: > >>>>>> > >>>>>>> On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, > >>>>>>> higgin...@gmail.com wrote: > >>>>>>>> tried --- > >>>>>>>> > >>>>>>>> > >>>>>>>> sudo qubes-dom0-update > >>>>>>>> --enablerepo=qubes-templates-community --action=reinstall > >>>>>>>> qubes-template-debian-9 > >>>>>>>> > >>>>>>>> Again it appears to reinstall - message appears saying > >>>>>>>> successfully installed. > >>>>>>>> > >>>>>>>> Then try to start DEBIAN-9 VM and get > >>>>>>>> "ERROR:VM directory does not exist: > >>>>>>>> /var/lib/qubes/vm-templates/debian-9". > >>>>>>>> > >>>>>>>> > >>>>>>>> Help! > >>>>>>>> > >>>>>>> > >>>>>>> I just did a fresh install of Qubes OS 4.0 on new hardware > >>>>>>> and I'm having the exact same problem. None of the > >>>>>>> suggestions here have resulted in any change, although I did > >>>>>>> not try: > >>>>>>> > >>>>>>> sudo qubes-dom0-update --enablerepo=qubes-templates-community > >>>>>>> --action=reinstall qubes-template-debian-9 > >>>>>>> > >>>>>>> > >>>>>>> and I'm not that interested in going that route. > >>>>>>> > >>>>>>> I've been using Qubes OS 3.2 for over a year now without this > >>>>>>> type of problem. Any more suggestions or fixes? > >>>>>>> > >>>>>>> Thanks. > >>>>>>> > >>>>>>> > >>>>>>> John > >>>>>>> > >>>>>>> > >>>>>> > >>>>>> Have you tried the obvious, and created the missing directory? > >>>>>> Ownership should be root:qubes - compare to the other template > >>>>>> directories. > >>>>>> > >>>>>> The only content is a symlink icon.png, pointing to > >>>>>> /usr/share/icons/hicolor/128x128/devices/appvm-black/png > >>>>>> You could create this yourself also. > >>>>>> > >>>>> > >>>>> Unman, thanks for replying. I didn't run that command (sudo > >>>>> qubes-dom0-update --enablerepo=qubes-templates-community > >>>>> --action=reinstall qubes-template-debian-9), so I don't know if I > >>>>> would get the same error message, but I do have the directory > >>>>> /var/lib/qubes/vm-templates/debian-9. > >>>>> > >>>>> > >>>>> I've performed an automatic re-install of the debian-9 template > >>>>> twice and a manual re-install once. Still, no applications > >>>>> display under Applications tab. I can't even run a terminal via > >>>>> dom0 using: qvm-run debian-9 gnome-terminal > >>>>> > >>>>> I have to believe there is a simple command to make this debian-9 > >>>>> template functional, but I don't know where to go from here. > >>>>> > >>>>> Thanks. > >>>>> > >>>>> > >>>>> John > >>>>> > >>>>> > >>>> > >>>> Sorry John, I misunderstood. > >>>> The message you quoted referred to a VM dir
Re: [qubes-users] Re: debian-9 template
On Friday, September 7, 2018 at 10:15:49 AM UTC-4, John Maher wrote: > On Friday, September 7, 2018 at 10:12:52 AM UTC-4, John Maher wrote: > > On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote: > > > On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote: > > > > On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote: > > > > > On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote: > > > > > > On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com > > > > > > wrote: > > > > > > > tried --- > > > > > > > > > > > > > > > > > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > > > > > > > --action=reinstall qubes-template-debian-9 > > > > > > > > > > > > > > Again it appears to reinstall - message appears saying > > > > > > > successfully installed. > > > > > > > > > > > > > > Then try to start DEBIAN-9 VM and get > > > > > > > "ERROR:VM directory does not exist: > > > > > > > /var/lib/qubes/vm-templates/debian-9". > > > > > > > > > > > > > > Help! > > > > > > > > > > > > I just did a fresh install of Qubes OS 4.0 on new hardware and I'm > > > > > > having the exact same problem. None of the suggestions here have > > > > > > resulted in any change, although I did not try: > > > > > > > > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > > > > > > --action=reinstall qubes-template-debian-9 > > > > > > > > > > > > and I'm not that interested in going that route. > > > > > > > > > > > > I've been using Qubes OS 3.2 for over a year now without this type > > > > > > of problem. Any more suggestions or fixes? > > > > > > > > > > > > Thanks. > > > > > > > > > > > > John > > > > > > > > > > > > > > > > Have you tried the obvious, and created the missing directory? > > > > > Ownership should be root:qubes - compare to the other template > > > > > directories. > > > > > > > > > > The only content is a symlink icon.png, pointing to > > > > > /usr/share/icons/hicolor/128x128/devices/appvm-black/png > > > > > You could create this yourself also. > > > > > > > > Unman, thanks for replying. I didn't run that command (sudo > > > > qubes-dom0-update --enablerepo=qubes-templates-community > > > > --action=reinstall qubes-template-debian-9), so I don't know if I would > > > > get the same error message, but I do have the directory > > > > /var/lib/qubes/vm-templates/debian-9. > > > > > > > > I've performed an automatic re-install of the debian-9 template twice > > > > and a manual re-install once. Still, no applications display under > > > > Applications tab. I can't even run a terminal via dom0 using: qvm-run > > > > debian-9 gnome-terminal > > > > > > > > I have to believe there is a simple command to make this debian-9 > > > > template functional, but I don't know where to go from here. > > > > > > > > Thanks. > > > > > > > > John > > > > > > > > > > Sorry John, I misunderstood. > > > The message you quoted referred to a VM directory that did not exist, > > > and I assumed *that* was your problem. > > > > > > It appears that your problem is that the template does not show any > > > applications. Have you tried running 'qvm-start debian-9' followed by > > > 'qvm-sync-appmenus debian-9' ? What is the result? > > > > > > Incidentally, it would be helpful if you gave a little more information > > > about the errors you are encountering. When you try to run > > > gnome-terminal, what exactly happens? Do you see any error messages? > > > Does the template start? > > > > > > Have you tried running other applications using qvm-run? xterm? firefox? > > > > > > > > > unman > > > > Hi unman, > > > > Thanks for this. Sorry, I do need to provide
Re: [qubes-users] Re: debian-9 template
On Friday, September 7, 2018 at 10:12:52 AM UTC-4, John Maher wrote:
> On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote:
> > On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote:
> > > On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote:
> > > > On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote:
> > > > > On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com
> > > > > wrote:
> > > > > > tried ---
> > > > > >
> > > > > >
> > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > > > --action=reinstall qubes-template-debian-9
> > > > > >
> > > > > > Again it appears to reinstall - message appears saying successfully
> > > > > > installed.
> > > > > >
> > > > > > Then try to start DEBIAN-9 VM and get
> > > > > > "ERROR:VM directory does not exist:
> > > > > > /var/lib/qubes/vm-templates/debian-9".
> > > > > >
> > > > > > Help!
> > > > >
> > > > > I just did a fresh install of Qubes OS 4.0 on new hardware and I'm
> > > > > having the exact same problem. None of the suggestions here have
> > > > > resulted in any change, although I did not try:
> > > > >
> > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > > --action=reinstall qubes-template-debian-9
> > > > >
> > > > > and I'm not that interested in going that route.
> > > > >
> > > > > I've been using Qubes OS 3.2 for over a year now without this type of
> > > > > problem. Any more suggestions or fixes?
> > > > >
> > > > > Thanks.
> > > > >
> > > > > John
> > > > >
> > > >
> > > > Have you tried the obvious, and created the missing directory?
> > > > Ownership should be root:qubes - compare to the other template
> > > > directories.
> > > >
> > > > The only content is a symlink icon.png, pointing to
> > > > /usr/share/icons/hicolor/128x128/devices/appvm-black/png
> > > > You could create this yourself also.
> > >
> > > Unman, thanks for replying. I didn't run that command (sudo
> > > qubes-dom0-update --enablerepo=qubes-templates-community
> > > --action=reinstall qubes-template-debian-9), so I don't know if I would
> > > get the same error message, but I do have the directory
> > > /var/lib/qubes/vm-templates/debian-9.
> > >
> > > I've performed an automatic re-install of the debian-9 template twice and
> > > a manual re-install once. Still, no applications display under
> > > Applications tab. I can't even run a terminal via dom0 using: qvm-run
> > > debian-9 gnome-terminal
> > >
> > > I have to believe there is a simple command to make this debian-9
> > > template functional, but I don't know where to go from here.
> > >
> > > Thanks.
> > >
> > > John
> > >
> >
> > Sorry John, I misunderstood.
> > The message you quoted referred to a VM directory that did not exist,
> > and I assumed *that* was your problem.
> >
> > It appears that your problem is that the template does not show any
> > applications. Have you tried running 'qvm-start debian-9' followed by
> > 'qvm-sync-appmenus debian-9' ? What is the result?
> >
> > Incidentally, it would be helpful if you gave a little more information
> > about the errors you are encountering. When you try to run
> > gnome-terminal, what exactly happens? Do you see any error messages?
> > Does the template start?
> >
> > Have you tried running other applications using qvm-run? xterm? firefox?
> >
> >
> > unman
>
> Hi unman,
>
> Thanks for this. Sorry, I do need to provide more info.
>
> I ran the following and got the following:
>
> [maher@dom0 ~]$ qvm-start debian-9
> [maher@dom0 ~]$ qvm-sync-appmenus debian-9
> Traceback (most recent call last):
> File "/usr/bin/qvm-sync-appmenus", line 9, in
> load_entry_point('qubesdesktop==4.0.12', 'console_scripts',
> 'qvm-sync-appmenus')()
> File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line 390,
> in main
>
Re: [qubes-users] Re: debian-9 template
On Friday, September 7, 2018 at 9:45:33 AM UTC-4, unman wrote:
> On Thu, Sep 06, 2018 at 09:31:09AM -0700, John Maher wrote:
> > On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote:
> > > On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote:
> > > > On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com
> > > > wrote:
> > > > > tried ---
> > > > >
> > > > >
> > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > > --action=reinstall qubes-template-debian-9
> > > > >
> > > > > Again it appears to reinstall - message appears saying successfully
> > > > > installed.
> > > > >
> > > > > Then try to start DEBIAN-9 VM and get
> > > > > "ERROR:VM directory does not exist:
> > > > > /var/lib/qubes/vm-templates/debian-9".
> > > > >
> > > > > Help!
> > > >
> > > > I just did a fresh install of Qubes OS 4.0 on new hardware and I'm
> > > > having the exact same problem. None of the suggestions here have
> > > > resulted in any change, although I did not try:
> > > >
> > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community
> > > > --action=reinstall qubes-template-debian-9
> > > >
> > > > and I'm not that interested in going that route.
> > > >
> > > > I've been using Qubes OS 3.2 for over a year now without this type of
> > > > problem. Any more suggestions or fixes?
> > > >
> > > > Thanks.
> > > >
> > > > John
> > > >
> > >
> > > Have you tried the obvious, and created the missing directory?
> > > Ownership should be root:qubes - compare to the other template
> > > directories.
> > >
> > > The only content is a symlink icon.png, pointing to
> > > /usr/share/icons/hicolor/128x128/devices/appvm-black/png
> > > You could create this yourself also.
> >
> > Unman, thanks for replying. I didn't run that command (sudo
> > qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall
> > qubes-template-debian-9), so I don't know if I would get the same error
> > message, but I do have the directory /var/lib/qubes/vm-templates/debian-9.
> >
> > I've performed an automatic re-install of the debian-9 template twice and a
> > manual re-install once. Still, no applications display under Applications
> > tab. I can't even run a terminal via dom0 using: qvm-run debian-9
> > gnome-terminal
> >
> > I have to believe there is a simple command to make this debian-9 template
> > functional, but I don't know where to go from here.
> >
> > Thanks.
> >
> > John
> >
>
> Sorry John, I misunderstood.
> The message you quoted referred to a VM directory that did not exist,
> and I assumed *that* was your problem.
>
> It appears that your problem is that the template does not show any
> applications. Have you tried running 'qvm-start debian-9' followed by
> 'qvm-sync-appmenus debian-9' ? What is the result?
>
> Incidentally, it would be helpful if you gave a little more information
> about the errors you are encountering. When you try to run
> gnome-terminal, what exactly happens? Do you see any error messages?
> Does the template start?
>
> Have you tried running other applications using qvm-run? xterm? firefox?
>
>
> unman
Hi unman,
Thanks for this. Sorry, I do need to provide more info.
I ran the following and got the following:
[maher@dom0 ~]$ qvm-start debian-9
[maher@dom0 ~]$ qvm-sync-appmenus debian-9
Traceback (most recent call last):
File "/usr/bin/qvm-sync-appmenus", line 9, in
load_entry_point('qubesdesktop==4.0.12', 'console_scripts',
'qvm-sync-appmenus')()
File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line 390,
in main
new_appmenus = retrieve_appmenus_templates(vm, use_stdin=use_stdin)
File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line 364,
in retrieve_appmenus_templates
new_appmenus = get_appmenus(vm if not use_stdin else None)
File "/usr/lib/python3.5/site-packages/qubesappmenus/receive.py", line 158,
in get_appmenus
"Error getting application list")
qubesadmin.exc.QubesException: Error getting application list
Regarding errors, I really haven't received any, and I've mostly worked in the
GUI. For
Re: [qubes-users] Re: debian-9 template
On Thursday, September 6, 2018 at 9:42:02 AM UTC-4, unman wrote: > On Thu, Sep 06, 2018 at 05:24:24AM -0700, John Maher wrote: > > On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com wrote: > > > tried --- > > > > > > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > > > --action=reinstall qubes-template-debian-9 > > > > > > Again it appears to reinstall - message appears saying successfully > > > installed. > > > > > > Then try to start DEBIAN-9 VM and get > > > "ERROR:VM directory does not exist: > > > /var/lib/qubes/vm-templates/debian-9". > > > > > > Help! > > > > I just did a fresh install of Qubes OS 4.0 on new hardware and I'm having > > the exact same problem. None of the suggestions here have resulted in any > > change, although I did not try: > > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > > --action=reinstall qubes-template-debian-9 > > > > and I'm not that interested in going that route. > > > > I've been using Qubes OS 3.2 for over a year now without this type of > > problem. Any more suggestions or fixes? > > > > Thanks. > > > > John > > > > Have you tried the obvious, and created the missing directory? > Ownership should be root:qubes - compare to the other template > directories. > > The only content is a symlink icon.png, pointing to > /usr/share/icons/hicolor/128x128/devices/appvm-black/png > You could create this yourself also. Unman, thanks for replying. I didn't run that command (sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-debian-9), so I don't know if I would get the same error message, but I do have the directory /var/lib/qubes/vm-templates/debian-9. I've performed an automatic re-install of the debian-9 template twice and a manual re-install once. Still, no applications display under Applications tab. I can't even run a terminal via dom0 using: qvm-run debian-9 gnome-terminal I have to believe there is a simple command to make this debian-9 template functional, but I don't know where to go from here. Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/37911ecd-dfe4-4b8c-90c1-f71796bd761f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: debian-9 template
On Sunday, April 29, 2018 at 8:20:40 AM UTC-4, higgin...@gmail.com wrote: > tried --- > > > sudo qubes-dom0-update --enablerepo=qubes-templates-community > --action=reinstall qubes-template-debian-9 > > Again it appears to reinstall - message appears saying successfully installed. > > Then try to start DEBIAN-9 VM and get > "ERROR:VM directory does not exist: /var/lib/qubes/vm-templates/debian-9". > > Help! I just did a fresh install of Qubes OS 4.0 on new hardware and I'm having the exact same problem. None of the suggestions here have resulted in any change, although I did not try: sudo qubes-dom0-update --enablerepo=qubes-templates-community --action=reinstall qubes-template-debian-9 and I'm not that interested in going that route. I've been using Qubes OS 3.2 for over a year now without this type of problem. Any more suggestions or fixes? Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/ab2f3942-357a-42b8-ab56-13f340d2b564%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Yubikey and qubes-usb-proxy
On Friday, September 22, 2017 at 3:49:24 PM UTC-4, Francesco wrote: > On Fri, Sep 22, 2017 at 2:21 PM, John Maher wrote: > > > On Friday, September 22, 2017 at 1:06:03 PM UTC-4, John Maher wrote: > > > On Friday, September 22, 2017 at 10:08:30 AM UTC-4, Francesco wrote: > > > > On Fri, Sep 22, 2017 at 9:08 AM, John Maher wrote: > > > > > > > > > > > > On Thursday, September 21, 2017 at 2:23:18 PM UTC-4, Marek > > > Marczykowski-Górecki wrote: > > > > > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > > > > > > Hash: SHA256 > > > > > > > > > > > > > > > > > > On Wed, Sep 20, 2017 at 05:46:56AM -0700, John Maher wrote: > > > > > > > > > > I've been trying to get my Yubikey to attach to my gpg qube by doing > > > > > the following: > > > > > > > > > > > > > > > > > > > > [dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1` > > > > > > > > > > > > > > > > > > > > but I'm presented with: > > > > > > > > > > > > > > > > > > > > ERROR: qubes-usb-proxy not installed in the VM > > > > > > > > > > > > > > > > > > > > But that package is installed in the VM (in the template). > > > > > > > > > > > > > > > > > > > > I got this to work fine on my laptop but not on my desktop. > > > > > > > > > > > > > > > > > > > > Any suggestions would be great. > > > > > > > > > > > > > > > > > > You need that package in both source and destination VM (template). So, > > > > > > > > > both template of gpg and sys-usb in this case. > > > > > > > > > > > > > > > > > > - -- > > > > > > > > > Best Regards, > > > > > > > > > Marek Marczykowski-Górecki > > > > > > > > > Invisible Things Lab > > > > > > > > > A: Because it messes up the order in which people normally read text. > > > > > > > > > Q: Why is top-posting such a bad thing? > > > > > > > > > -BEGIN PGP SIGNATURE- > > > > > > > > > Version: GnuPG v2 > > > > > > > > > > > > > > > > > > iQEcBAEBCAAGBQJZxAOQAAoJENuP0xzK19csf7EH/A4VSx4RqlQob2eFfxz+PSER > > > > > > > > > EwkbF90Tu7wu9haeRAhvwyWdh7BVwkA+Qb4wtsPnggZyYxCyeNtn+1qVYTZL5Ov5 > > > > > > > > > ZwLMCSwsIj7s+pK3Rh28GQfnyMgLE2Y5iUor9gLItO54+kYoPWBW0tygXFxeOqIj > > > > > > > > > NWYVHNlo+RiJDPGD3xqa6H7zRiTX+3IlYOtB6C8Gr2tYITcM1s8u5wYTs2/MpKbE > > > > > > > > > JsEph8OSiLY8YsM+u2/TvWt30Ajpdvx7sRlblOvvZg1Rn/7KZqIqnFydyt0uMeUY > > > > > > > > > 39DykFZ0WaJF28lpVcdy92kViZE8gTM00KNGulHaMc4pW/N65p5L97o1ldoQulw= > > > > > > > > > =KvN4 > > > > > > > > > -END PGP SIGNATURE- > > > > > > > > > > > > > > > > Thank you, Marek. I now believe I'm confused about sys-usb. I have no > > > sys-usb VM in either my desktop or my laptop (both 3.2) displayed in the > > > Qubes VM Manager, but I remember selecting sys-usb during the > > > installations. In terms of behavior, both my systems require that I > > > attach a USB drive to a particular qube after inserting the drive. > > > Doesn't that mean I have a USB qube (sys-usb)? > > > > > > > > > > > > > > > > So, I don't know how I would install qubes-usb-proxy when I can't see > > > sys-usb. > > > > > > > > > > > > > > > > > > > > > > > > qvm-ls will list all installed VMs so you can check if sys-usb exists > > > > > > > > best > > > > > > > > Fran > > > > > > > > > > > > John > > > > > > > > > > > > > > > > -- > > > > > > > > You received this message because you are subscribed to the Google Groups > > >
Re: [qubes-users] Yubikey and qubes-usb-proxy
On Friday, September 22, 2017 at 1:06:03 PM UTC-4, John Maher wrote: > On Friday, September 22, 2017 at 10:08:30 AM UTC-4, Francesco wrote: > > On Fri, Sep 22, 2017 at 9:08 AM, John Maher wrote: > > > > > > On Thursday, September 21, 2017 at 2:23:18 PM UTC-4, Marek > > Marczykowski-Górecki wrote: > > > > > -BEGIN PGP SIGNED MESSAGE- > > > > > Hash: SHA256 > > > > > > > > > > On Wed, Sep 20, 2017 at 05:46:56AM -0700, John Maher wrote: > > > > > > I've been trying to get my Yubikey to attach to my gpg qube by doing > > > > the following: > > > > > > > > > > > > [dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1` > > > > > > > > > > > > but I'm presented with: > > > > > > > > > > > > ERROR: qubes-usb-proxy not installed in the VM > > > > > > > > > > > > But that package is installed in the VM (in the template). > > > > > > > > > > > > I got this to work fine on my laptop but not on my desktop. > > > > > > > > > > > > Any suggestions would be great. > > > > > > > > > > You need that package in both source and destination VM (template). So, > > > > > both template of gpg and sys-usb in this case. > > > > > > > > > > - -- > > > > > Best Regards, > > > > > Marek Marczykowski-Górecki > > > > > Invisible Things Lab > > > > > A: Because it messes up the order in which people normally read text. > > > > > Q: Why is top-posting such a bad thing? > > > > > -BEGIN PGP SIGNATURE- > > > > > Version: GnuPG v2 > > > > > > > > > > iQEcBAEBCAAGBQJZxAOQAAoJENuP0xzK19csf7EH/A4VSx4RqlQob2eFfxz+PSER > > > > > EwkbF90Tu7wu9haeRAhvwyWdh7BVwkA+Qb4wtsPnggZyYxCyeNtn+1qVYTZL5Ov5 > > > > > ZwLMCSwsIj7s+pK3Rh28GQfnyMgLE2Y5iUor9gLItO54+kYoPWBW0tygXFxeOqIj > > > > > NWYVHNlo+RiJDPGD3xqa6H7zRiTX+3IlYOtB6C8Gr2tYITcM1s8u5wYTs2/MpKbE > > > > > JsEph8OSiLY8YsM+u2/TvWt30Ajpdvx7sRlblOvvZg1Rn/7KZqIqnFydyt0uMeUY > > > > > 39DykFZ0WaJF28lpVcdy92kViZE8gTM00KNGulHaMc4pW/N65p5L97o1ldoQulw= > > > > > =KvN4 > > > > > -END PGP SIGNATURE- > > > > > > > > Thank you, Marek. I now believe I'm confused about sys-usb. I have no > > sys-usb VM in either my desktop or my laptop (both 3.2) displayed in the > > Qubes VM Manager, but I remember selecting sys-usb during the > > installations. In terms of behavior, both my systems require that I attach > > a USB drive to a particular qube after inserting the drive. Doesn't that > > mean I have a USB qube (sys-usb)? > > > > > > > > So, I don't know how I would install qubes-usb-proxy when I can't see > > sys-usb. > > > > > > > > > > > > qvm-ls will list all installed VMs so you can check if sys-usb exists > > > > best > > > > Fran > > > > > > John > > > > > > > > -- > > > > You received this message because you are subscribed to the Google Groups > > "qubes-users" group. > > > > To unsubscribe from this group and stop receiving emails from it, send an > > email to qubes-users...@googlegroups.com. > > > > To post to this group, send email to qubes...@googlegroups.com. > > > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/qubes-users/dc559bd3-0947-4350-8a86-5863f5fb93ed%40googlegroups.com. > > > > > > > > For more options, visit https://groups.google.com/d/optout. > > Francesco, thanks. That helps. My confusion continues to be high, but I guess > mostly because I thought my computer had a USB qube because of it's behavior. > Like I said, I can attach my Yubikey to one Qubes computer but not another. > It's likely that I installed them slightly different from each other. > > I vaguely remember checking a "sys-usb" box during installation of both, but > the laptop (installed most recently) I think I also check a box that > referenced an experimental feature. > > Perhaps I just need to install a USB qube on my desktop, but clearly I don't > have one on my laptop, and attaching the Yubikey works there. > > John One thing that might be useful is the difference between my desktop and my laptop when I run qvm-usb (with the Yubikey plugged in). Desktop: -- $ qvm-usb dom0:7-5 1050:0407 Yubico_Yubikey_4_OTP+U2F+CCID Laptop: -- $ qvm-usb sys-net:2-3 1050:0407 Yubico_Yubikey_4_OTP+U2F+CCID Might the dom0 vs sys-net indicate an important configuration difference? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/5ca39fc6-5b6d-483c-99b5-ce8730e9659e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Yubikey and qubes-usb-proxy
On Friday, September 22, 2017 at 10:08:30 AM UTC-4, Francesco wrote: > On Fri, Sep 22, 2017 at 9:08 AM, John Maher wrote: > > > On Thursday, September 21, 2017 at 2:23:18 PM UTC-4, Marek > Marczykowski-Górecki wrote: > > > -BEGIN PGP SIGNED MESSAGE- > > > Hash: SHA256 > > > > > > On Wed, Sep 20, 2017 at 05:46:56AM -0700, John Maher wrote: > > > > I've been trying to get my Yubikey to attach to my gpg qube by doing the > > > following: > > > > > > > > [dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1` > > > > > > > > but I'm presented with: > > > > > > > > ERROR: qubes-usb-proxy not installed in the VM > > > > > > > > But that package is installed in the VM (in the template). > > > > > > > > I got this to work fine on my laptop but not on my desktop. > > > > > > > > Any suggestions would be great. > > > > > > You need that package in both source and destination VM (template). So, > > > both template of gpg and sys-usb in this case. > > > > > > - -- > > > Best Regards, > > > Marek Marczykowski-Górecki > > > Invisible Things Lab > > > A: Because it messes up the order in which people normally read text. > > > Q: Why is top-posting such a bad thing? > > > -BEGIN PGP SIGNATURE- > > > Version: GnuPG v2 > > > > > > iQEcBAEBCAAGBQJZxAOQAAoJENuP0xzK19csf7EH/A4VSx4RqlQob2eFfxz+PSER > > > EwkbF90Tu7wu9haeRAhvwyWdh7BVwkA+Qb4wtsPnggZyYxCyeNtn+1qVYTZL5Ov5 > > > ZwLMCSwsIj7s+pK3Rh28GQfnyMgLE2Y5iUor9gLItO54+kYoPWBW0tygXFxeOqIj > > > NWYVHNlo+RiJDPGD3xqa6H7zRiTX+3IlYOtB6C8Gr2tYITcM1s8u5wYTs2/MpKbE > > > JsEph8OSiLY8YsM+u2/TvWt30Ajpdvx7sRlblOvvZg1Rn/7KZqIqnFydyt0uMeUY > > > 39DykFZ0WaJF28lpVcdy92kViZE8gTM00KNGulHaMc4pW/N65p5L97o1ldoQulw= > > > =KvN4 > > > -END PGP SIGNATURE- > > > > Thank you, Marek. I now believe I'm confused about sys-usb. I have no sys-usb > VM in either my desktop or my laptop (both 3.2) displayed in the Qubes VM > Manager, but I remember selecting sys-usb during the installations. In terms > of behavior, both my systems require that I attach a USB drive to a > particular qube after inserting the drive. Doesn't that mean I have a USB > qube (sys-usb)? > > > > So, I don't know how I would install qubes-usb-proxy when I can't see sys-usb. > > > > > > qvm-ls will list all installed VMs so you can check if sys-usb exists > > best > > Fran > > > John > > > > -- > > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to qubes-users...@googlegroups.com. > > To post to this group, send email to qubes...@googlegroups.com. > > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/dc559bd3-0947-4350-8a86-5863f5fb93ed%40googlegroups.com. > > > > For more options, visit https://groups.google.com/d/optout. Francesco, thanks. That helps. My confusion continues to be high, but I guess mostly because I thought my computer had a USB qube because of it's behavior. Like I said, I can attach my Yubikey to one Qubes computer but not another. It's likely that I installed them slightly different from each other. I vaguely remember checking a "sys-usb" box during installation of both, but the laptop (installed most recently) I think I also check a box that referenced an experimental feature. Perhaps I just need to install a USB qube on my desktop, but clearly I don't have one on my laptop, and attaching the Yubikey works there. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/986e1cd4-87cd-4ba8-bcaf-efe871874efb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Yubikey and qubes-usb-proxy
On Thursday, September 21, 2017 at 2:23:18 PM UTC-4, Marek Marczykowski-Górecki wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Wed, Sep 20, 2017 at 05:46:56AM -0700, John Maher wrote: > > I've been trying to get my Yubikey to attach to my gpg qube by doing the > > following: > > > >[dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1` > > > > but I'm presented with: > > > >ERROR: qubes-usb-proxy not installed in the VM > > > > But that package is installed in the VM (in the template). > > > > I got this to work fine on my laptop but not on my desktop. > > > > Any suggestions would be great. > > You need that package in both source and destination VM (template). So, > both template of gpg and sys-usb in this case. > > - -- > Best Regards, > Marek Marczykowski-Górecki > Invisible Things Lab > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > -BEGIN PGP SIGNATURE- > Version: GnuPG v2 > > iQEcBAEBCAAGBQJZxAOQAAoJENuP0xzK19csf7EH/A4VSx4RqlQob2eFfxz+PSER > EwkbF90Tu7wu9haeRAhvwyWdh7BVwkA+Qb4wtsPnggZyYxCyeNtn+1qVYTZL5Ov5 > ZwLMCSwsIj7s+pK3Rh28GQfnyMgLE2Y5iUor9gLItO54+kYoPWBW0tygXFxeOqIj > NWYVHNlo+RiJDPGD3xqa6H7zRiTX+3IlYOtB6C8Gr2tYITcM1s8u5wYTs2/MpKbE > JsEph8OSiLY8YsM+u2/TvWt30Ajpdvx7sRlblOvvZg1Rn/7KZqIqnFydyt0uMeUY > 39DykFZ0WaJF28lpVcdy92kViZE8gTM00KNGulHaMc4pW/N65p5L97o1ldoQulw= > =KvN4 > -END PGP SIGNATURE- Thank you, Marek. I now believe I'm confused about sys-usb. I have no sys-usb VM in either my desktop or my laptop (both 3.2) displayed in the Qubes VM Manager, but I remember selecting sys-usb during the installations. In terms of behavior, both my systems require that I attach a USB drive to a particular qube after inserting the drive. Doesn't that mean I have a USB qube (sys-usb)? So, I don't know how I would install qubes-usb-proxy when I can't see sys-usb. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/dc559bd3-0947-4350-8a86-5863f5fb93ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Yubikey and qubes-usb-proxy
I've been trying to get my Yubikey to attach to my gpg qube by doing the following: [dom0 ~]$ qvm-usb -a gpg `qvm-usb | grep Yubikey | cut -f1` but I'm presented with: ERROR: qubes-usb-proxy not installed in the VM But that package is installed in the VM (in the template). I got this to work fine on my laptop but not on my desktop. Any suggestions would be great. Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/4a6876df-9581-4e9a-a533-9d9b91004780%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Prompted twice for approving GPG key use
I'm using Split GPG, and I upgraded my template from Fedora-23 to Fedora-24. Everything continues to work, but I am now prompted twice (an identical prompt) to approve the use of my GPG key for 300 seconds. Any thoughts as to why that is and how I can change it back to a single prompt? Of course, it's not a big deal (just click twice), but it concerns me that the first click accepting the use of the key for 300 seconds is not "taking effect". After clicking the second time it does work for 300 seconds. Thanks for any help. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/81674646-cecc-4eaa-b391-3111cf2f9230%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Opening links in your preferred AppVM
On Monday, August 21, 2017 at 11:14:15 AM UTC-4, John Maher wrote: > On Tuesday, May 2, 2017 at 1:14:47 PM UTC-4, Gaiko wrote: > > Thanks for the reply! > > > > > > my ~/.local/share/applications/mimeapps.list is a bit different than yours, > > really I was most interested in it handling http/https > > > > > > [Default Applications] > > text/html=open_work_vm.desktop > > x-scheme-handler/http=open_work_vm.desktop > > x-scheme-handler/https=open_work_vm.desktop > > x-scheme-handler/about=open_work_vm.desktop > > x-scheme-handler/unknown=open_work_vm.desktop > > > > > > I tried just copying/pasting yours into mine (just for kicks) but that > > didn't work either :( > > > > > > > > > > > > > > On Tue, May 2, 2017 at 4:36 AM, wrote: > > Gaiko [2017-05-02 03:36 +0200]: > > > > > > What happens if you run `qvm-open-in-vm work https://qubes-os.org` in > > > > > > tbirdVM > > > > > > > > > > it seems to work just fine that way > > > > > > > > > > > and when you run xdg-open https://qubes-os.org in the work VM > > > > > > (without the quotes)? > > > > > > > > > > ok, xdg-open I hadn't tried. But regardless this seems to work fine as > > > well. > > > > > > > > Good! That means qvm-open-in-vm (sending the link to the work VM and > > > > telling it to open it) and opening it internally in the work VM > > > > works as intended. > > > > > > > > What does ~/.local/share/applications/mimeapps.list in tbird look like? > > > > It should look like this (from the mentioned how-to): > > > > > > > > [Default Applications] > > > > x-scheme-handler/unknown=open_work_vm.desktop > > > > x-scheme-handler/about=open_work_vm.desktop > > > > x-scheme-handler/http=open_work_vm.desktop > > > > x-scheme-handler/https=open_work_vm.desktop > > > > text/html=open_work_vm.desktop > > > > text/xml=open_work_vm.desktop > > > > image/gif=open_work_vm.desktop > > > > image/jpeg=open_work_vm.desktop > > > > image/png=open_work_vm.desktop > > > > application/xhtml+xml=open_work_vm.desktop > > > > application/xml=open_work_vm.desktop > > > > application/vnd.mozilla.xul+xml=open_work_vm.desktop > > > > application/rss+xml=open_work_vm.desktop > > > > application/rdf+xml=open_work_vm.desktop > > > > > > > > Remove the lines for any MIME types you don't want to open with your > > > > work VM. > > > > > > > > -- > > > > ubestemt > > Gaiko, did you get this to work? I have the exact same experience. And > placing the files in /usr/share/applications did not help. > > When running "desktop-file-validate browser_vm.desktop" from ~/. I get "file > does not exist". From ~/.local/share/applications I get 'browser_vm.desktop: > warning: key "Encoding" in group "Desktop Entry" is deprecated', similar to > you. > > Thanks. > John Well, I got this to work mostly as desired. Turns out that even after running "xdg-settings set default-web-browser browser_vm.desktop" (and confirmed with "xdg-settings get default-web-browser"), I had to remove all .desktop files in the working VM (not the browser VM) related to Chrome and Firefox. That included files located in ~/.local/share/applications and in /usr/share/applications. Unfortunately, I really want to use Firefox in the browser VM, but only Chrome will launch. Still working on addressing that. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/9bc3c2b2-32f4-45c7-b1d9-8f9a6e809f76%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] Re: Opening links in your preferred AppVM
On Tuesday, May 2, 2017 at 1:14:47 PM UTC-4, Gaiko wrote: > Thanks for the reply! > > > my ~/.local/share/applications/mimeapps.list is a bit different than yours, > really I was most interested in it handling http/https > > > [Default Applications] > text/html=open_work_vm.desktop > x-scheme-handler/http=open_work_vm.desktop > x-scheme-handler/https=open_work_vm.desktop > x-scheme-handler/about=open_work_vm.desktop > x-scheme-handler/unknown=open_work_vm.desktop > > > I tried just copying/pasting yours into mine (just for kicks) but that didn't > work either :( > > > > > > > On Tue, May 2, 2017 at 4:36 AM, wrote: > Gaiko [2017-05-02 03:36 +0200]: > > > > What happens if you run `qvm-open-in-vm work https://qubes-os.org` in > > > > tbirdVM > > > > > > it seems to work just fine that way > > > > > > > and when you run xdg-open https://qubes-os.org in the work VM > > > > (without the quotes)? > > > > > > ok, xdg-open I hadn't tried. But regardless this seems to work fine as well. > > > > Good! That means qvm-open-in-vm (sending the link to the work VM and > > telling it to open it) and opening it internally in the work VM > > works as intended. > > > > What does ~/.local/share/applications/mimeapps.list in tbird look like? > > It should look like this (from the mentioned how-to): > > > > [Default Applications] > > x-scheme-handler/unknown=open_work_vm.desktop > > x-scheme-handler/about=open_work_vm.desktop > > x-scheme-handler/http=open_work_vm.desktop > > x-scheme-handler/https=open_work_vm.desktop > > text/html=open_work_vm.desktop > > text/xml=open_work_vm.desktop > > image/gif=open_work_vm.desktop > > image/jpeg=open_work_vm.desktop > > image/png=open_work_vm.desktop > > application/xhtml+xml=open_work_vm.desktop > > application/xml=open_work_vm.desktop > > application/vnd.mozilla.xul+xml=open_work_vm.desktop > > application/rss+xml=open_work_vm.desktop > > application/rdf+xml=open_work_vm.desktop > > > > Remove the lines for any MIME types you don't want to open with your > > work VM. > > > > -- > > ubestemt Gaiko, did you get this to work? I have the exact same experience. And placing the files in /usr/share/applications did not help. When running "desktop-file-validate browser_vm.desktop" from ~/. I get "file does not exist". From ~/.local/share/applications I get 'browser_vm.desktop: warning: key "Encoding" in group "Desktop Entry" is deprecated', similar to you. Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/80c01987-e9a2-457c-9e14-69e26ff35f19%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] XScreenSaver for dom0 pops up
On Thursday, November 3, 2016 at 12:50:13 AM UTC-4, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-11-02 08:56, John Maher wrote: > > On Thursday, October 27, 2016 at 12:42:18 AM UTC-4, Andrew David Wong wrote: > > On 2016-10-26 15:53, Gaijin wrote: > >>>> On 2016-10-26 13:38, John Maher wrote: > >>>>> On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: > >>>>>> On 2016-10-26 12:43, John Maher wrote: > >>>>>>> I'm getting the strangest thing on my screen. I'll be working and the > >>>>>>> XScreenSaver dialog pops up (indicating the screen is locked) and the > >>>>>>> screen goes black. However, the screen is not locked. I have to move a > >>>>>>> window around to redraw my screen. This has always happened since I > >>>>>>> started using Qubes about 3 weeks ago. There appears to be no pattern > >>>>>>> that prompts this response. Bizarre! Any thoughts? > >>>>>>> > >>>>>>> Thanks. > >>>>>>> > >>>>>>> John > >>>>>> > >>>>>> Yeah. I had the same thing happen when I upgraded to R3.2 as well. I > >>>>>> asked the same thing but nobody replied. > >>>>>> https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ > >>>>>> > >>>>>> It still happens from time to time. Seems to happen less if I have a > >>>>>> lot > >>>>>> of free memory. Closing down some memory hungry AppVMs seems to lessen > >>>>>> it, but I haven't been able to specifically replicate it. > >>>>> > >>>>> Interesting, because I think I have more than enough memory (32 GB). > >>>>> Thanks. > >>>> > >>>> I've got 16GB myself. It's not that the memory is full, but it seems to > >>>> happen more when I have a lot of VMs open in one desktop. That may just > >>>> be a coincidence though. > >>>> > >>>> I'm glad to see it wasn't just me though. I never had this happen with > >>>> earlier versions of Qubes on the same hardware. Not sure if it might be > >>>> the XFCE or a video driver issue. (I've never installed the nVidia > >>>> drivers.) > >>>> > > > > Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. > > > > Just to confirm: Are you both using Xfce4? > > > > Tracking the issue here: > > > > https://github.com/QubesOS/qubes-issues/issues/2399 > > > > > > Sorry for the delay in responding. I used the default install for 3.2. > > > > I also just noticed that it appears that memory is not being purged when > > apps are closed. Today when I "woke up" the screen from one of these odd > > screen saver like issues, it very briefly displayed a browser window with a > > site I was on yesterday. I looked carefully and confirmed that I did not > > actually have that window open on my system. It's as if something from > > yesterday's memory was sent to the screen and then closed. Rather > > disconcerting. > > > > John > > > > I don't think that should necessarily be disconcerting. The Qubes security > model does not include or rely upon purging memory at any particular time > interval. It assumes that you, the authentic single user, should be the only > one with access to dom0's screen content. So, the fact that you're allowed to > see your screen content from yesterday doesn't constitute any violation of > the security model. You're still the same trusted user as you were yesterday. > (If I've misunderstood your concern, please let me know.) > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYGsH3AAoJENtN07w5UDAwKtIP/2vblyc4Rf9uwU3M+WGv2K7V > T7VoTDfGjB8XWyX6LZW/TrtameFmAj/Rb0bINOrIWpkrP9RdNUm+0/BR10NkcLul > FqaxMOcl2u2Tk775VjYtC+Z7y1ycJDQjaMvtqrdDQkeGhMumzcDOHD9RufTFSIRm > 8ke7GxfMQBH7R0DJ5E26B7HZJg73k1RKFT5BbpmKrfHxBBEaJTUALeNFZnp2ekl+ > HrRV4u8+T/Tbwzha5e/iTvJEVTMcMxzD4uziaN+TfiK2Iwp40w0W8IdmRjPzdkLI > +PDhAfjpQCEcZIPT/V+u6GsMhUDJo5ABPs/as17YY4b8VMwm9F7/J2Oo6nfwl/Rh > gOnwVLFQKUtq3iaNbORDzAjBSEny6wYKlfvpL3IWGAHhH0mbP5j1ivSJoF+navuD > qPMvMyAuhFh7hSsTPJ0
Re: [qubes-users] XScreenSaver for dom0 pops up
On Thursday, October 27, 2016 at 12:42:18 AM UTC-4, Andrew David Wong wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 2016-10-26 15:53, Gaijin wrote: > > On 2016-10-26 13:38, John Maher wrote: > >> On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: > >>> On 2016-10-26 12:43, John Maher wrote: > >>> > I'm getting the strangest thing on my screen. I'll be working and the > >>> > XScreenSaver dialog pops up (indicating the screen is locked) and the > >>> > screen goes black. However, the screen is not locked. I have to move a > >>> > window around to redraw my screen. This has always happened since I > >>> > started using Qubes about 3 weeks ago. There appears to be no pattern > >>> > that prompts this response. Bizarre! Any thoughts? > >>> > > >>> > Thanks. > >>> > > >>> > John > >>> > >>> Yeah. I had the same thing happen when I upgraded to R3.2 as well. I > >>> asked the same thing but nobody replied. > >>> https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ > >>> > >>> It still happens from time to time. Seems to happen less if I have a lot > >>> of free memory. Closing down some memory hungry AppVMs seems to lessen > >>> it, but I haven't been able to specifically replicate it. > >> > >> Interesting, because I think I have more than enough memory (32 GB). > >> Thanks. > > > > I've got 16GB myself. It's not that the memory is full, but it seems to > > happen more when I have a lot of VMs open in one desktop. That may just be > > a coincidence though. > > > > I'm glad to see it wasn't just me though. I never had this happen with > > earlier versions of Qubes on the same hardware. Not sure if it might be the > > XFCE or a video driver issue. (I've never installed the nVidia drivers.) > > > > Thank you both for reporting this. Gaijin, I'm sorry I missed your thread. > > Just to confirm: Are you both using Xfce4? > > Tracking the issue here: > > https://github.com/QubesOS/qubes-issues/issues/2399 > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > -BEGIN PGP SIGNATURE- > > iQIcBAEBCgAGBQJYEYWaAAoJENtN07w5UDAwvq8P/1hFm/owsEasSXroxzK9JnTn > DSBZ9udjO+TWQypb4Hh4RO48MtJnQhKfdgJJWWJwf9dTp62LUBkVWskKDtvOfyo+ > aoVFGRBexb7yzRT90kBsjHiVPeysA4bTBftQZEZzTQBz/UzRzMkcBWj7/vbYrTkL > zeG42ZCuM75jzOv2dhrG2TeP+OlTfdnFIyFQFmdaRJyHTOBtf7Mjauuj4gFEiKNr > ztMO4jE/kn+/E79cGu33VfrxITmiH7Z5tqZQuAS0Mud9YnBuCDumIugPuSleV3IL > xARHjYjui+yPOzB66yZiDlQhTMRaEhEEQVR6UWMU+SC/nec+dTpWq/b7EgktXdud > NpJr+jIDfaoNdVBtDFIXRBo6vbR05dtWQFfLIeewGIhIC9VwLJSwEW2TvCTWFOcO > kXWV4xsg1xAJNbNBm9V42yZ6M1P+ClXlAcJYPVqrk+xisLtlWAweqT4yKw3zq5HW > rlgkLYoNAjU3ZvTHYa/2JtyQZKbUUw+ck8nRRuLUp0jqM/2TlZfQ7tmfsfb5z1HS > mzNe6UHhg5ZtoV0HKbyMIWa5ePVZaMJCkhNOMAuAQ9QBpJgqE7dWZx28S5eqnAno > WTFQI9nT6JCQz7YvmIkrxQDCUmG5JQqZlqIXArRS0WNjAzNMraKBsWeHTOqha4he > HiI1LB04rOraNysdPTpj > =MANy > -END PGP SIGNATURE- Sorry for the delay in responding. I used the default install for 3.2. I also just noticed that it appears that memory is not being purged when apps are closed. Today when I "woke up" the screen from one of these odd screen saver like issues, it very briefly displayed a browser window with a site I was on yesterday. I looked carefully and confirmed that I did not actually have that window open on my system. It's as if something from yesterday's memory was sent to the screen and then closed. Rather disconcerting. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/196229af-8c96-463f-9918-bae76a454d57%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] XScreenSaver for dom0 pops up
On Wednesday, October 26, 2016 at 9:05:48 AM UTC-4, Gaijin wrote: > On 2016-10-26 12:43, John Maher wrote: > > I'm getting the strangest thing on my screen. I'll be working and the > > XScreenSaver dialog pops up (indicating the screen is locked) and the > > screen goes black. However, the screen is not locked. I have to move a > > window around to redraw my screen. This has always happened since I > > started using Qubes about 3 weeks ago. There appears to be no pattern > > that prompts this response. Bizarre! Any thoughts? > > > > Thanks. > > > > John > > Yeah. I had the same thing happen when I upgraded to R3.2 as well. I > asked the same thing but nobody replied. > https://groups.google.com/forum/#!topic/qubes-users/xjHi2TcYBAQ > > It still happens from time to time. Seems to happen less if I have a lot > of free memory. Closing down some memory hungry AppVMs seems to lessen > it, but I haven't been able to specifically replicate it. Interesting, because I think I have more than enough memory (32 GB). 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/42f3c2a5-7cb8-412b-a600-7412647d02d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] Re: SMB mount point location
On Wednesday, October 12, 2016 at 8:55:05 AM UTC-4, John Maher wrote: > Hello, > > I'm trying to access file on the command line through an SMB mount point that > is created in the GUI. I'm using a debian-8 AppVM and connecting to an SMB > share in a Files window, but I cannot find a mount point for the share. I > would expect it to be in /run/users/1000/.gvfs, but there's nothing there. > > Can anyone point out where I would find that mount point? > > Thank you very much. > > John Manuel, So helpful! Thank you very much for your explanation. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/fff84234-d37e-464c-b469-f606bce7837c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] XScreenSaver for dom0 pops up
I'm getting the strangest thing on my screen. I'll be working and the XScreenSaver dialog pops up (indicating the screen is locked) and the screen goes black. However, the screen is not locked. I have to move a window around to redraw my screen. This has always happened since I started using Qubes about 3 weeks ago. There appears to be no pattern that prompts this response. Bizarre! Any thoughts? Thanks. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/a1dc5b59-572c-4838-b555-34ca26d5fa0a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] SMB mount point location
On Saturday, October 15, 2016 at 10:30:06 PM UTC-4, Manuel Amador (Rudd-O) wrote: > On 10/13/2016 02:25 PM, John Maher wrote: > > On Wednesday, October 12, 2016 at 12:06:15 PM UTC-4, Manuel Amador (Rudd-O) > > wrote: > >> On 10/12/2016 12:55 PM, John Maher wrote: > >>> Hello, > >>> > >>> I'm trying to access file on the command line through an SMB mount point > >>> that is created in the GUI. I'm using a debian-8 AppVM and connecting to > >>> an SMB share in a Files window, but I cannot find a mount point for the > >>> share. I would expect it to be in /run/users/1000/.gvfs, but there's > >>> nothing there. > >>> > >>> Can anyone point out where I would find that mount point? > >> By default, GVFS won't actually mount it — it just appears in the Files > >> window. I believe the first time you attempt to activate (open) a file > >> on the share, GVFS does the mount. It used to be different, I know, I > >> just hit this issue myself a few days ago. > >> > >> This is more a GNOME upstream thing. > >> > >> Do your files show on the file manager? > >> > >> > >> -- > >> Rudd-O > >> http://rudd-o.com/ > > The real issue is that I'm trying to access a KeePassX database that > > resides on a smb share, and the Database > Open dialog box does not present > > mounted smb shares or bookmarks to the shares. Any thoughts on this? > > You need an actual mount for that to work, and the dialog box will not > trigger the mount operation. You have two choices: > > 1) Open your KeepAssX database in a StandaloneVM which you have > configured to mount the SMB drive. > 2) In the template, create and enable an /etc/systemd/system mount unit > for the SMB drive, that is only active if a file in > /var/run/qubes-service/ exists (check the various > qubes-*.service files in /usr/lib/systemd/system for examples on how the > ConditionPathExists thing works), then set up the qubes-service > on the VM in question. That way, when you boot the VM in > question, and only that VM in question, the mount appears immediately. > > I would also use automount units if I were you, just to make sure that > your VM where you run KeepAssX boots fast and does not wait to mount the > remote device. > > Here is a crude example of such a thing: > > [user@tpl ~]$ mkdir /mnt/keepassxmount > [user@tpl ~]$ cat > /etc/systemd/system/mnt-keepassxmount.mount > [Unit] > Description=Mount /mnt/keepassxmount > ConditionPathExists=/var/run/qubes-service/mnt-keepassxmount > Before=remote-fs.target > After=remote-fs-pre.target mnt-keepassxmount.path > > [Mount] > What=//smbserverip/keepassxmount > Where=/mnt/keepassxmount > Type=cifs > Options=_netdev,cache=strict,forceuid,forcegid,noperm,noserverino,nomapposix,nomapchars,uid=user,gid=user,forceuid,forcegid > > [Install] > WantedBy=remote-fs.target > [user@tpl ~]$ systemctl enable mnt-keepassxmount.mount > > At this point you add the Qubes service mnt-keepassxmount in your VM's > configuration. > > Option 3: use some file sync service to keep that KeepAssX file > synchronized to local disk on that VM. > > > -- > Rudd-O > http://rudd-o.com/ Manuel, this is awesome! Thank you for the extensive explanation. Regarding option 3, are you referring to a Qubes service or some other type of utility? Being new to Qubes, your mentioning of services above is my introduction to Qubes services. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/2c228b10-2abd-4d2e-876d-77802b22614c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] SMB mount point location
On Wednesday, October 12, 2016 at 12:06:15 PM UTC-4, Manuel Amador (Rudd-O) wrote: > On 10/12/2016 12:55 PM, John Maher wrote: > > Hello, > > > > I'm trying to access file on the command line through an SMB mount point > > that is created in the GUI. I'm using a debian-8 AppVM and connecting to an > > SMB share in a Files window, but I cannot find a mount point for the share. > > I would expect it to be in /run/users/1000/.gvfs, but there's nothing > > there. > > > > Can anyone point out where I would find that mount point? > > By default, GVFS won't actually mount it — it just appears in the Files > window. I believe the first time you attempt to activate (open) a file > on the share, GVFS does the mount. It used to be different, I know, I > just hit this issue myself a few days ago. > > This is more a GNOME upstream thing. > > Do your files show on the file manager? > > > -- > Rudd-O > http://rudd-o.com/ The real issue is that I'm trying to access a KeePassX database that resides on a smb share, and the Database > Open dialog box does not present mounted smb shares or bookmarks to the shares. Any thoughts on this? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To 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/fd555cdf-486a-4579-a500-a79a0f6e182c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [qubes-users] SMB mount point location
On Wednesday, October 12, 2016 at 12:06:15 PM UTC-4, Manuel Amador (Rudd-O) wrote: > Do your files show on the file manager? Manuel, thank you for responding. Yes, they do. So, there is no way to access the files through the connection created by the file 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/3a3ff2dd-47ca-45d0-9ae3-26ad5aabf33c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[qubes-users] SMB mount point location
Hello, I'm trying to access file on the command line through an SMB mount point that is created in the GUI. I'm using a debian-8 AppVM and connecting to an SMB share in a Files window, but I cannot find a mount point for the share. I would expect it to be in /run/users/1000/.gvfs, but there's nothing there. Can anyone point out where I would find that mount point? Thank you very much. John -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/356cd8f9-d89a-4f7a-82a6-d4ce7c4f4774%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
