Re: [qubes-users] Runing Qubes on: HP ProBook 430 G2 or HP EliteBook 820

Linus Stridbeck wrote: > I came across very inexpensive HP computers: > > HP ProBook 430 G2 > > HP EliteBook 820 > > They both have i3 procesor and I wonder if someone tried ryning Qubes on one > of them? > > > I'm typing this on an 820 G3 with an i5 6200u cpu.

Re: [qubes-users] noscript xss warning on qubes os site

Confirm I get this too with noscript in firefox. Will try and get some details together if I can and file an issue... -- 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

Re: [qubes-users] Re: QSB #37: Information leaks due to processor speculative execution bugs (XSA-254, Meltdown & Sepctre)

>> Only running VMs are vulnerable >> >> Since Qubes OS is a memory-hungry system, it seems that an attacker >> would only be able to steal secrets from VMs running concurrently with >> the attacking VM. This is because any pages from shutdown VMs will >> typically very quickly get allocated to

[qubes-users] 3.2.1 / An updated 3.2 iso?

Hi all We were chatting today in IRC about current user expectations and experiences with the 4 release candidates. While many are happily testing there are indeed some visitors who drop by with the requirement of a daily driver stable system, but have some newer hardware than the kernel on

Re: [qubes-users] kswapd0 using 100% CPU with not even a MB swap in use

>> On 10/08/2017 08:18 AM, Marek Marczykowski-Górecki wrote: > > Indeed on 4.9.45-21 kernel it happens much rarer than on 4.4.x, but still > happens sometimes... It's only anecdotal, but I seem to have been seeing it more frequently recently (i.e. on that kernel). Will try the one-liner again,

Re: [qubes-users] Fedora25 fails updates unless I reboot the machine 9.13.17

I'm experiencing a similar problem which I've reported a bug for at https://github.com/QubesOS/qubes-issues/issues/3135 If you're still encountering the issue with the update proxy failing too, could you check the output of "journalctl -u qubes-updates-proxy.service" when it fails please?

Re: [qubes-users] Re: Qubes 3.2 Building an up to date dom0 3.18 Kernel

> Original Message > Subject: [qubes-users] Re: Qubes 3.2 Building an up to date dom0 3.18 Kernel > Local Time: August 21, 2017 2:38 PM > UTC Time: August 21, 2017 1:38 PM > From: r...@reginaldtiangha.com > To: qubes-users@googlegroups.com > > If you don"t trust me, you can

[qubes-users] Qubes 3.2 Building an up to date dom0 3.18 Kernel

As previously detailed ad nauseum, none of the Qubes dom0 4.4 or 4.9 version Kernels will boot on my laptop (HP Elitebook 2540p). This means I'm stuck on the ancient 3.18.17-8. I'm comfortable(ish - have built a Xenial template) using Qubes builder and I notice Reg Tiangha has a repo with

Re: [qubes-users] Seeking moderators for unofficial Qubes IRC channels on Freenode and OFTC

> Qubes should not associate themselves with freenode or irc. That"s just my > opinion. Nobody with self respect or integrity has taken freenode serious for > over 10 years. It should stay unofficial. Not to knock what you're saying, but I think it's important for us to draw a distinction as a

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

> Specifically, it'd be nice to know if: > 2) Hardware that didn't work with 4.4 or 4.8 still doesn't work. Having just tried 4.9.35-19, this has the same problem as every other 4.x kernel on my HP Elitebook 2540p (Intel HD graphics), that is as soon as the Qubes boot screen comes up, the

Re: [qubes-users] Re: What do you think about Grsecurity future ?

> Original Message > Subject: [qubes-users] Re: What do you think about Grsecurity future ? > Local Time: July 5, 2017 6:05 PM > UTC Time: July 5, 2017 5:05 PM > From: turboa...@gmail.com > To: qubes-users > turboa...@gmail.com > End of official PaX

[qubes-users] Setting up regular bitcoin donation / buying support case?

Hi all Over on https://www.qubes-os.org/donate/ I see I can setup a donation one of two ways, Bitcoin and via Open Collective, however 14% for the latter seems a hell of a donation overhead. As such, I'd like to use Bitcoin but have no idea how. While I realise there are probably many idiots

Re: [qubes-users] HCL Elitebook 2540p / Complete inability to use any Qubes 3.2 4.x series kernel

The only kernel that still functions is the leftover 3.8.17-8 from 3.1. Which is working fine for now, are there any downsides to continuing to use this? Going by today's security bulletin[1], which releases a new kernel - it seems that there may well be downsides. I wonder how best to

Re: [qubes-users] Re: Xen high CPU usage, but nothing is running in the VM

This happens to me sometimes on the current Xen/Linux versions. When I look at top in the offending VM its "kswapd" that has gone berserk. -- Chris Laprise, tas...@openmailbox.org https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- I can confirm I've also

[qubes-users] HCL Elitebook 2540p / Complete inability to use any Qubes 3.2 4.x series kernel

Hi all Having upgraded to 3.2 it's basically as I assumed, no 4.x series kernel will boot on my laptop, the graphics on the Qubes boot screen are completely corrupted and some of the kernels reboot a second or so after the Qubes boot screen appears. The only kernel that still functions is the

[qubes-users] 3.1 - 3.2 upgrade no qubes-upgrade-vm package available?

Hi all Following the upgrade instructions from 3.1 to 3.2, in the upgrade Fedora templates section the text talks about installing the qubes-upgrade-vm package, however this is not available in my Fedora 24 templates, is the section Fedora 23 specific? Thanks -- You received this message

[qubes-users] Re: Kernel issues preparing for 3.1 - 3.2 Upgrade

I've always had difficulties booting the default kernel of 3.1 (4.1.24.10), graphic corruption making it impossible to complete a boot. As such I've just always used 3.18.17-8 which behaves fine on my hardware. Am now preparing to make the upgrade to 3.2, but want to ensure if at all possible

[qubes-users] Kernel issues preparing for 3.1 - 3.2 Upgrade

I've always had difficulties booting the default kernel of 3.1 (4.1.24.10), graphic corruption making it impossible to complete a boot. As such I've just always used 3.18.17-8 which behaves fine on my hardware. Am now preparing to make the upgrade to 3.2, but want to ensure if at all possible

Re: [qubes-users] Q3.1 fedora-24-minimal template - dom0 update problem

Oh. Or install yum in fedora24 template. Nvm then. -- 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

[qubes-users] Q3.1 fedora-24-minimal template - dom0 update problem

Hi all Having installed the necessary packages (at least per website doc) and assigned fedora-24-minimal to sys-firewall dom0 complains on update that yum / yumdownloader command cannot be found on the sys-firewall (which I guess is correct on fedora-24?). I guess Yum= should be dnf in

Re: [qubes-users] GUI Daemon error with new fedora-24-minimal template

It looks like template uploaded to 3.1 repository was built for Qubes 3.2, so this is why it's incompatible. I've just removed this faulty template, building new one - will be ready in few hours. - -- Best Regards, Marek Marczykowski-Górecki Invisible Things Lab A: Because it messes up the order

[qubes-users] GUI Daemon error with new fedora-24-minimal template

Hi all Qubes 3.1 Have downloaded the new qubes-template- fedora-24-minimal however on starting it the following message is received "Dom0 GUI daemon do not support protocol version 1:1 requested by VM. To update Dom0..." etc Does the template require a version of gui currently only in

Re: [qubes-users] 3.0 to 3.1 in place upgrade broke USB VMs

Sounds like it could have been introduced in R3.1 Xen 4.6 for you specifically due to your hardware. If that's the case, it wouldn't be a good idea to note this on the page, since it might not apply to others. - -- Andrew David Wong (Axon) Community Manager, Qubes OS https://www.qubes-os.org

Re: [qubes-users] 3.0 to 3.1 in place upgrade broke USB VMs

Apologies, this appears to be the shared RMRR problem discussed in https://github.com/QubesOS/qubes-issues/issues/1544 This is indeed in the FAQ, but I was thrown by the doc at https://www.qubes-os.org/doc/user-faq/#i-created-a-usbvm-and-assigned-usb-controllers-to-it-now-the-usbvm-wont-boot

[qubes-users] 3.0 to 3.1 in place upgrade broke USB VMs

The in place upgrade from 3.0 to 3.1 broke my two USB VMs (one controller with ports, one controller with devices) which were both set to auto start and working on 3.0. The error is similar to that where devices are assigned to another running VM - this is not the case however.