[qubes-users] Re: [qubes-devel] Re: Request for feedback: 4.9 Kernel

On Thursday, June 1, 2017 at 10:00:09 AM UTC-4, Pablo Di Noto wrote: > > >> 4) General feedback on the 4.9 kernel. > > > > > > Oh, yeah... I have started experiencing quite annoying internet > > > connectivity issues, very, very difficulty to troubleshot. Symptoms are: > > > > > > - Web browsing

Re: [qubes-users] Any release schedule for Qubes 4.0

> On Jun 20, 2017, at 11:27 AM, Reg Tiangha wrote: > > On 2017-06-20 9:06 AM, Swâmi Petaramesh wrote: >> Hi there, >> >> I've been googling here and there, and couldn't find any release >> schedule for the upcoming qubes 4.0... > > They haven't released one yet and

[qubes-users] Containing Twitter sessions

I am perplexed by the challenge of containing Twitter use in Qubes. With Twitter, you must be logged in to effectively read or write. On the read side, it is a wildly promiscuous experience exposing the user to various untrusted sites. Indeed a key goal of using Twitter is to discover new

Re: [qubes-users] X.org failure preventing boot, Intel graphics

> On May 25, 2017, at 12:48 AM, ryant...@ryantate.com wrote: > > Maybe my Intel graphics are too new for this X? So I made a fedora 23 live usb and was able to boot into fine on the same system. No X issues, full GUI. So I am wondering if this is really about Xorg, since presumably this has

Re: [qubes-users] X.org failure preventing boot, Intel graphics

> On May 25, 2017, at 10:25 PM, Ryan Tate <ryant...@ryantate.com> wrote: > > So I made a fedora 23 live usb and was able to boot into fine on the same > system. No X issues, full GUI. > Ah, it turns out I was able to boot when using same fedora but different (older) k

Re: [qubes-users] X.org failure preventing boot, Intel graphics

On May 25, 2017, at 11:19 PM, Ryan Tate <ryant...@ryantate.com> wrote: > > Ah, it turns out I was able to boot when using same fedora but different > (older) kernel (4.2.3). To be clear, I still can't boot qubes, I'm just saying it seems to have more to do with the kernel tha

Re: [qubes-users] X.org failure preventing boot, Intel graphics

> On Jun 10, 2017, at 2:39 AM, Vít Šesták > wrote: > > Good to hear it helps. Fronm “without being able to actually boot into > Qubes?”, I wrongly assumed you are unable to switch to a different tty. This was actually a

Re: [qubes-users] X.org failure preventing boot, Intel graphics

> On May 27, 2017, at 3:35 AM, Vít Šesták > wrote: > > Are you able to connect the laptop via ethernet? If so, you might try > something like? > > 1. Boot in rescue mode. > 2. chroot > 3. systemctl mask lightdm # this will

[qubes-users] Clearly expose --mem option in HVM docs

Right now the HVM documentation does not prominently disclose that initial memory/RAM may be configured on creation of the HVM domain via --mem option (https://www.qubes-os.org/doc/hvm/ ). This is mentioned only in "Converting VirtualBox VM to HVM” which is

[qubes-users] Re: Clearly expose --mem option in HVM docs

By the way, it looks like this was suggested previously, see number 3 in the ordered list under “Steps to reproduce” here: https://github.com/QubesOS/qubes-issues/issues/3089 -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from

Re: [qubes-users] DispVM and Word/docx - no go

gt; On Thu, Oct 19, 2017 at 11:08:07AM -0400, Ryan Tate wrote: >> In Qubes 3.2 from a fedora 25 AppVM, when I try and open a docx (Word) >> file via DispVM via the right-click menu, I just get a directory >> listing inside the DispVM. Instead of opening the file with >> LibreOf

Re: [qubes-users] Re: Can't use settings in fedora 28 vm.

This happened to me, too, I Googled around and found setting an environment variable would make the Settings panel/app work: [user@fedora28vm ~] env XDG_CURRENT_DESKTOP=GNOME gnome-control-center (I re-typed the above while looking at another machine rather than copy/paste hopefully no typos!)

[qubes-users] update broke whonix, can't reinstall

I run stock Qubes 4, no special repos or templates. Qubes Manager was showing an update for whonix-ws and whonix-gw templateVMs. Update process on whonix-gw went as usual. On whonix-ws, update seemed to proceed fine initially but then suddenly the update window disappeared. Usually it prompts

[qubes-users] Re: update broke whonix, can't reinstall

On Wednesday, November 7, 2018 at 3:25:34 PM UTC-5, Ryan Tate wrote: > On Wednesday, November 7, 2018 at 3:23:46 PM UTC-5, Ryan Tate wrote: > > Installed package qubes-template-whonix-gw-4.0.0-201803270426.noarch not > > available > > Error: No packages marked for reinstal

[qubes-users] Re: update broke whonix, can't reinstall

Well, now I can't figure out how to uninstall the template. Other VMs depend on it. Am I supposed to just reassign all of them, and delete it? Obviously I tried every permutation of "action=remove" I could think of but none matched. I tried copy/pasting every version of the full (and

[qubes-users] Re: update broke whonix, can't reinstall

On Wednesday, November 7, 2018 at 3:23:46 PM UTC-5, Ryan Tate wrote: > Installed package qubes-template-whonix-gw-4.0.0-201803270426.noarch not > available > Error: No packages marked for reinstall. > > Installed package qubes-template-whonix-ws-4.0.0.-201803270504.noarch n

[qubes-users] Re: update broke whonix, can't reinstall

Ah, finally I realize that whonix is in a community repo. This was not intuitive as I recall it coming with my Qubes 4 install (do I misremember?). Adding --enablerepo=qubes-templates-community seems to make it work. So I just needed to do qubes-dom0-update

[qubes-users] Qubes menu failing. Come on guys

I don't know what is going on with 4.0.1 but suddenly my machine is haywire. The latest is everything above and below the VMs is gone from the Qubes menu. The bottom of the menu where I'd go to shut down just says "No applications found." The top where I would go to find settings, Qubes

Re: [qubes-users] Re: dom0 environment lost on restore

> On Apr 1, 2019, at 10:01 PM, Andrew David Wong wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 01/04/2019 2.54 PM, Ryan Tate wrote: >> >> If the wish is not “restore” but rather to copy some files — “some >> files and scripts that

Re: [qubes-users] Re: dom0 environment lost on restore

Thanks for the thoughtful replies (I just now saw Chris' from before). Also thank you Andrew for making a Github issue! It sounds like there is at least some common ground on providing smoother restore as an option, which I appreciate. If it's too much to add code to that effect anytime soon (I

Re: [qubes-users] Re: dom0 environment lost on restore

On Wed, Apr 3, 2019 at 1:53 PM Ryan Tate wrote: > That said, I would just note -- Files from dom0 do traverse other VMs > in all the scenarios we've discussed. I expect in backup/restore > scenario they are encrypted as they transit, for example, sys-usb. But > I don't know o

Re: [qubes-users] Can’t boot after attempting to verify backup

> On Apr 1, 2019, at 11:48 AM, Chris Laprise wrote: > > I think its more related to this issue: > > https://github.com/QubesOS/qubes-issues/issues/4791 I think you nailed it. The first time I ran the verification, I panicked when it said it was extracting data, as it seemed to have already

[qubes-users] Re: dom0 environment lost on restore

> On Apr 1, 2019, at 2:26 PM, Ryan Tate wrote: > > Although the backup included dom0, and the restore as well, I have lost > various key settings. My xfce panel shrank and moved to the top and the > button size changed, for example. My desktop icons for launching applications

[qubes-users] dom0 environment lost on restore

I recently had to wipe my Qubes machine, resinstall, and do a full restore of my VMs from a very recent backup (three days old). Although the backup included dom0, and the restore as well, I have lost various key settings. My xfce panel shrank and moved to the top and the button size changed,

[qubes-users] Re: Can’t boot after attempting to verify backup

Hmmm, looks an awful lot like this: https://github.com/QubesOS/qubes-issues/issues/4479 https://groups.google.com/forum/#!msg/qubes-users/PR3-ZbZXo_0/wem9wbGTBgAJ https://github.com/QubesOS/qubes-issues/issues/4857 :-\ Fwiw I am on stable, NOT testing (a question raised in that first thread).

[qubes-users] Re: Can’t boot after attempting to verify backup

PS not an April 1 joke sadly. -- 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] Re: Can’t boot after attempting to verify backup

Looking over journalctl in emergency mode. It looks like it decrypts fine (“Reached target Encrypted Volumes. Reached Target System Initialization. Reached Target Basic System.”) It seems like it sees many of my vms (many “inactive ‘/dev/qubes/dom0/vm-foo’ [10.0GB] inherit”) But there is

[qubes-users] Can’t boot after attempting to verify backup

On Friday I backed up my machine and attempted to verify the backup by launching qubes-backup-restore (GUI interface) and ticking the verify only box. Is it possible this box does not work? I was a bit alarmed when qubes began unpacking the backup after verifying each qube, but thought perhaps

[qubes-users] Re: dom0 environment lost on restore

> On Apr 1, 2019, at 2:33 PM, Ryan Tate wrote: > > Now I see there is a folder in my dom0 home dir called > ‘home-restore-2019-04-01-etcetc’. > > But what do I do with this? I just have to manually figure out what files are > important? :-\ I just sort of methodically

Re: [qubes-users] Can't set default_target to @dispvm:foo in policy

On Fri, Mar 8, 2019 at 7:03 PM Marek Marczykowski-Górecki wrote: > > Seems like a bug? > > Indeed. Could you report it at > https://github.com/QubesOS/qubes-issues/issues ? OK, done: https://github.com/QubesOS/qubes-issues/issues/4881 -- You received this message because you are subscribed to

[qubes-users] networked dvm for vault?

Short version: Is it a security issue to set a networked disp vm as the default disp vm for a vaulted vm? I have a vaulted vm (no network) and a printing dvm (limited local network access via firewall). It would be convenient to set the printing dvm as default disp vm for the vault so i can

Re: [qubes-users] networked dvm for vault?

On Thursday, March 7, 2019 at 7:24:11 PM UTC-5, unman wrote: > The fact that you don't see a prompt suggests that you have a policy se > to "allow" - you can check this in /etc/qubes-rpc/policy/qubes.OpenInVM > If you change that so that it reads: > vault $dispvm ask > then you should see a

[qubes-users] Can't set default_target to @dispvm:foo in policy

I was trying to have a qubes.OpenInVM policy that would pre-fill a target in the permission dialog when the destination was an inside of a certain dispvm. Specifying the destination vm (#2 entry) in the policy works fine to specify a dispvm instance. But specifying the default_target (part of

[qubes-users] Qubes backup UI stalls badly

Today I went to backup my machine using Qubes backup GUI and near the end (?) the progress bar was at 100% but the Finish button was not clickable. I waited maybe half an hour, an hour, and tried closing the window. I got an error message saying the window was not responding and asking if I

Re: [qubes-users] Re: Qubes 4 boot stuck at: "[ OK ] Reached target Basic System. "

It would be nice if someone from the Qubes team could provide at least some basic tips for Qubes users on how to avoid having our installations completely ruined by what are apparently LVM issues. This case is at least the sixth I'm aware of counting myself of a Qubes system totally unable to

[qubes-users] How to enter ipv6 in firewall settings?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 I suspect this is a "dumb" question, but can't figure out the answer after searching through the list archives: I am unable to enter colons (from ipv6 addresses) into the firewall whitelist on the "Firewall rules" tab of "Qube Settings" when I

[qubes-users] Re: Does qubes block usb on thunderbolt port?

Ryan Tate writes: > On my ThinkPad X1 Carbon gen5, I can use my thunderbolt 3 ports fine for > display and for power. However, Qubes does not seem to recognize a usb-c > flash stick or a usb-c yubikey plugged into these ports I think I got this figured out. ThinkPads apparently do

[qubes-users] Does qubes block usb on thunderbolt port?

Does qubes block USB data on Thunderbolt ports? On my ThinkPad X1 Carbon gen5, I can use my thunderbolt 3 ports fine for display and for power. However, Qubes does not seem to recognize a usb-c flash stick or a usb-c yubikey plugged into these ports (the only usb-c ports). (The flash stick has

[qubes-users] What's your flow for new templateVM?

Saw the new f31 templateVM (thanks for that) and just curious how folks generally migrate to a new templateVM. I manually maintain this big text list of packages and just use that to manually update the fresh templateVM to what I need. There's typically also some non package installs, which I

[qubes-users] Special template to isolate less trusted software?

I've started making special templateVMs where I install less trusted software, typically closed source binaries or code distributed directly from a vendor. I am curious if others do this and if people think it adds much security wise. For example, in addition to vanilla fedora-32, where I

[qubes-users] attach encrypted usb drive as block?

Are there any known issues attaching a LUKS encrypted USB drive as a block device? If I attach the drive as a USB device it works fine, it shows up in nautilus in the destination VM and I can click the drive and enter the password. If I attach as a block device, first it doesn't show up in

[qubes-users] Re: attach encrypted usb drive as block?

Ryan Tate writes: If I attach as a block device, first it doesn't show up in nautilus. Actually, I found that for some reason as a block device it shows up under "Other Locations" in the nautilus sidebar. Once I navigate there all is cake. Sorry for the noise. -- Yo

Re: [qubes-users] MS Office 365 in Qubes

On Thursday, May 13, 2021 at 10:33:31 AM UTC-4 sv...@svensemmler.org wrote: > > https://github.com/elliotkillick/qvm-create-windows-qube > > But if Office 365 Suite are the only windows apps you need I'd go for > CrossOver. > I'm very curious about your experience running CrossOver in Qubes