[qubes-users] Re: Dracut failing on ASUS Z270A Motherboard

[Aaron Gray]

Okay installed sort of ish on an old AMD machine the net-sys process did not 
install properly.

Anyway swapped the disk over to the Intel and it booted okay apart from 
net-sys. AFAICS VM's are running okay except net-sys so no networking.

Will post better reports tomorrow as its late...

On Monday, 17 September 2018 17:52:54 UTC+1, Aaron Gray  wrote:
> Dracut failing on ASUS Z270A Motherboard based on Intel Z270 chipset 
> 
> Attached rdsosreport.txt
> ~~
> 
> + cat /lib/dracut/dracut-046-2.git20170811.fc25
> dracut-046-2.git20170811.fc25
...

-- 
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/06cee8f1-5529-4ed1-a4ad-298aa72b8545%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] dom0 uses 105%+ of cpu

[Guy Frank]

I've noticed on my new Qubes install that dom0 is perpetually at 105% cpu when 
I'm not doing anything on the computer, according to xentop (which I imagine 
means that dom0 is using about one VCPU).  Also, the hard disk light flashes 
every couple seconds or so.  Is this all normal or is something wrong?

When I run top in dom0, it shows 75%+ going to a kworker thread, but I don't 
know of any way to learn what that thread is doing.

I also started my xenial qube, ran tor-browser in it, and opened a newspaper 
website.  My dom0 xentop reading went to 200%, my xenial qube reading was at 
50% even when I wasn't doing anything with tor-browser, and tor-browser was so 
sluggish I have to wait 15 seconds or more for a page-down.  I've reproduced 
this problem twice.  Maybe what's happening here gives some hint as to what's 
happening with dom0

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/9ea048f0-92b0-4d22-a8d2-817fee411873%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes locks up half the time on startup with filenotfound error trying to run qubes manager

[Guy Frank]

On Friday, September 14, 2018 at 4:48:17 AM UTC-5, Marcus Linsner wrote:
> On Thursday, September 13, 2018 at 7:43:57 PM UTC+2, Guy Frank wrote:
> > On Tuesday, September 11, 2018 at 5:12:00 PM UTC-5, Guy Frank wrote:
> > > On Tuesday, September 11, 2018 at 4:29:02 PM UTC-5, awokd wrote:
> > > > On Tue, September 11, 2018 7:10 pm, Guy Frank wrote:
> > > > > On Tuesday, September 11, 2018 at 1:44:13 PM UTC-5, Guy Frank wrote:
> > > > >
> > > > >> Was a bit premature thinking that my qubes installation was stable.
> > > > >> About half the time I start the system, it locks up and I am only 
> > > > >> able
> > > > >> to access Dom0 (qubes manager will not open, nor will any qubes, even
> > > > >> from command line).  The system gives a serious 'filenotfound' error
> > > > >> msg.  I've looked at previous posts on problems like this, but my
> > > > >> problem doesn't seem to fit what others reported--qubes.xml is not
> > > > >> empty and disk utilization is minimal (or near 50% in one case).  The
> > > > >> error message is:
> > > > >>
> > > > >> #
> > > > >> Whoops.  A critical error has occurred.  This is most likely a bug in
> > > > >> Qubes Manager
> > > > >> FileNotFoundError:  [Errno 2]
> > > > >> No such file or directory
> > > > >> at line 9 of file /usr/bin/qubes-qube-manager #
> > > > >>
> > > > >>
> > > > >> Line 9 reads:  load_entry_point('qubesmanager==4.0.16',
> > > > >> 'console_scripts', 'qubes-qube-manager')()
> > > > >>
> > > > >>
> > > > >> Ok, so the weird thing is that this works fine half the time.  On 
> > > > >> half
> > > > >> of my boot ups, I don't encounter this problem.  So if there is no 
> > > > >> such
> > > > >> file or directory, it's not there half the time.  qubes.xml looks 
> > > > >> good
> > > > >> (to my untrained eyes), and df -h shows nothing at more than 1%
> > > > >> utilization except for /dev/nvme0n1p1 mounted on /boot/efi which is 
> > > > >> 56%
> > > > >> of 200MB.  nvme0n1p1 is, I believe, the GPT table?
> > > > >>
> > > > >> I'm worried about coming to rely on this installation if at some 
> > > > >> point
> > > > >> the error doesn't go away every other reboot and becomes permanent.  
> > > > >> Am
> > > > >> trying updates now--maybe that will help.
> > > > >>
> > > > >> Guy
> > > > >>
> > > > >
> > > > > Updating the software in dom0 doesn't make the problem disappear, 
> > > > > though
> > > > > now the main error message is:
> > > > >
> > > > > QubesDaemonCommunicationError: Failed to connect to qubesd service:
> > > > > [Errno 2] No such file or directory
> > > > > at line 9 of file /usr/bin/qubes-qube-manager
> > > > 
> > > > Nothing related earlier in the "sudo journalctl -e" log? Try "sudo
> > > > systemctl restart qubesd"?
> > > 
> > > Thanks awokd!  I'll give these a try next time I run into the problem
> > 
> > Ok, so on my next reboot, it ran into this problem again.  I made a copy of 
> > the journalctl log and tried to restart qubesd, to no effect.  
> > 
> > The attached file, jnlctlErr.txt, if you scroll down to 09:24:43, I think 
> > you can see where the Qubes OS daemon fails.  It is immediately preceded by 
> > the 1d.2 pci device worker failing, suggesting that something about this 
> > failure is causing the daemon from starting (which occurs below the blank 
> > line I added to the log). 1d.2 is a PCI Bridge, Intel Corp Device a332.  No 
> > idea what exactly this is or how to find out (not a hardware person).  
> > 
> > One thing I thought of is the fact that there's a PS/2 card in the machine 
> > to which a PS/2 keyboard & mouse are attached.  Neither has ever worked in 
> > Qubes (though they worked in Windows), so maybe that's what's triggering 
> > the problem?  Will do some testing.
> > 
> > When I attempt to start qubes daemon w/ sudo systemctl restart qubesd, 
> > journalctl log shows other errors.  The qubes daemon doesn't get started 
> > and I can't use the system.
> > 
> > What I can do is reboot.  And about every other time, Qubes comes up and is 
> > fine.  My concern is that at some point it'll stop doing this, so I'd 
> > really like to figure out how to solve this problem.
> > 
> > Guy
> 
> Looking the the relevant errors, in context (and the time between them):
> 
> ...
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device found, 
> idVendor=413c, idProduct=2002
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: New USB device strings: Mfr=1, 
> Product=2, SerialNumber=0
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: Product: Dell USB Keyboard Hub
> Sep 13 09:20:23 localhost kernel: usb 1-10.1: Manufacturer: Dell
> Sep 13 09:20:23 localhost kernel: input: Dell Dell USB Keyboard Hub as 
> /devices/pci:00/:00:14.0/usb1/1-10/1-10.1/1-10.1:1.0/0003:413C:2002.0001/input/input3
> Sep 13 09:20:23 localhost kernel: hid-generic 0003:413C:2002.0001: 
> input,hidraw0: USB HID v1.10 Keyboard [Dell Dell USB Keyboard Hub] on 
> usb-:00:14.0-10.1/input0
> Sep 13 09:20:23 localhost kernel: input: Dell Dell USB 

Re: [qubes-users] Re: application icons not displayed in panel in xenial

[Guy Frank]

On Friday, September 14, 2018 at 2:00:56 AM UTC-5, awokd wrote:
> On Thu, September 13, 2018 11:38 pm, Guy Frank wrote:
> > On Thursday, September 13, 2018 at 12:29:22 PM UTC-5, Guy Frank wrote:
> >
> >> On Wednesday, September 12, 2018 at 6:52:48 PM UTC-5, Guy Frank wrote:
> >>
> >>> I created a template for Xenial.  Things work well w/ the AppVM based
> >>> on this, but there's one hitch:  most of the icons for applications
> >>> do not display in the panel.  The odd thing is that the icons show
> >>> just fine in the Applications launcher and in Whiskers.  But on the
> >>> desktop panel, they just show as a lock.  It gets quite difficult to
> >>> find windows after a bunch have been opened without icons to clue me
> >>> in.  Not sure what's causing this problem because evidently the
> >>> .desktop files work fine for the launcher and Whiskers.
> >>>
> >>>
> >>> Guy
> >>>
> >>
> >> Hi folks:  Sorry, false alarm!  I was quite concerned about this issue
> >> because it made Qubes potentially to difficult for me to use because I
> >> need a lot of software and files open at once, so being able to see
> >> icons is important for me.  Turns out the problem resolved itself when
> >> I rebooted the system.  I've been reluctant to reboot because I had a
> >> number of things open I needed to address.
> >>
> >> Guy
> >>
> >
> > Whoops, have to take that back.  More icons are now showing in the panel,
> > but far from all.  Particularly important icons such as for various
> > Libreoffice document types are not showing.
> 
> Might be related to https://github.com/QubesOS/qubes-issues/issues/1495.

Yup, that certainly sounds like it.  I probably should put a note up about 
various places I'm finding padlocks rather than icons.  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/cc74fe77-228d-4772-9c21-23700a8fc474%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] HCL - Purism Librem 13 v2

[qubes-fan]

Looks like it is a bit of a blind way. To use the reasonably secure OS without 
possibility to use it on the reasonably secure HW, is an issue which needs to 
be addressed a bit. I originally guessed that Qubes would run on the RYF 
devices well, and I am quite surprised it doesn't (doesnt it?). Is there any 
strong issue which prevents Qubes to function with RYF devices? 

Am I missing something on the assumption that RYF devices, with disabled 
IME-AMT known security hole, with the coreboot  instead of BIOS and so on, are 
more secure-potential than the non-RYFs? 

I need a working laptop. Desktop is not an option. 


Sep 17, 2018, 11:54 PM by taii...@gmx.com:

> On 09/16/2018 02:51 AM, 'awokd' via qubes-users wrote:
>
>> On Sat, September 15, 2018 10:30 am, >> qubes-...@tutanota.com 
>> >>  wrote:
>>
>>> Hi, during my email conversation with the Todd Weaver
>>>
>
> That liar comes out of nowhere with his super slick marketing and sets
> the computing freedom movement back 10 years.
>
> At first I thought it was just being naive but now as he persists it
> seems more like malice.
>
> puri.junk does NOT respect you, it is fully blobbed and the ME is not at
> all disabled.
>
> Todd weaver is a lying fraudster.
>
>>> in the
>>> pre-IME-disabled time, he told me they will fully disable the IME and AMT
>>> within next week. After about a week they announced they did just that.
>>> Are this links a lie?
>>> https://puri.sm/posts/measuring-the-intel-me-to-create-a-more-secure-compu 
>>> 
>>> ter/
>>> <>>> 
>>> https://puri.sm/posts/measuring-the-intel-me-to-create-a-more-secure-com 
>>> 
>>> puter/>
>>> https://puri.sm/posts/purism-librem-laptops-completely-disable-intel-mana 
>>> 
>>> gement-engine/
>>> <>>> 
>>> https://puri.sm/posts/purism-librem-laptops-completely-disable-intel-man 
>>> 
>>> agement-engine/>
>>>
>>
>> "Lie" depends on your definition of "completely". Skylake onwards
>> processors can have much of ME disabled. I believe Purism with Heads and a
>> handful of other manufacturers are using the technique here:
>> http://blog.ptsecurity.com/2017/08/disabling-intel-me.html 
>> >> , but as you 
>> can
>> see there are still some modules required for initialization before the
>> HAP bit takes effect and skips the remainder. Additionally, there is an
>> FSP blob needed for init. Currently shipping AMD CPUs are no better.
>>
>
> Skylake kernel still runs, that is not disabled and there is more than
> enough ability to play dirty tricks like SMM rootkits or what not.
>
> HAP is asking politely.
>
>>> Talking about alternatives: how the Qubes 4.0 stand with RYF certified
>>> X200? Like for example this one: >>> 
>>> https://tehnoetic.com/laptops/tet-x200s 
>>> 
>>> <>>> https://tehnoetic.com/laptops/tet-x200s 
>>>  and others like T400 and 
>>> T500,
>>> which can be found there as well. Working well? Any issues known? Thank
>>> you
>>>
>>
>> At present, RYF has not certified any laptops with hardware capable of
>> running Qubes 4.0, but there are a couple older AMDs that can. A scale of
>> hardware openness/owner control from most to least would be something
>> like:
>>
>> 10: OpenPOWER, RYF certified x86 with all blobs replaced- Qubes 4.0 can't
>> run on either
>>
>
> Since you mention power and there aren't currently any laptops do you
> mean laptops or desktops? In terms of desktops there are a variety that
> qubes 4.0 can run on.
>
> The future is POWER for all...
>
>> 8: older AMD like A10-5750M- a couple blobs required but Qubes 4.0 works
>> on these and the rest listed
>> 6: pre-Skylake Intel with ME/HAP tweaks- a few more blobs and 2 ME modules
>> required
>> 4: Skylake+ Intel with ME/HAP tweaks, AMD Ryzen with PSP disabled in UEFI
>> config- more blobs and modules required
>>
>
> That doesn't disable it! you are simply asking nicely for it to shut off
> and hoping that it does so. It is not at all equivilant to say pre-core
> intel systems where one really could disable it or even better one that
> doesn't have any black boxes like the talos.
>
>> 0: Intel/AMD x86 with no tweaks- most shipping volume today
>>
>> ARM (& possibly RISC) is a special case in that the integrator can decide
>> where on the scale they want to deliver their product, but neither support
>> Qubes 4.0.
>>
>
> -- 
> 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 
> 

Re: [qubes-users] Gaming with qubes

[taii...@gmx.com]

On 09/15/2018 12:01 AM, David Schissler wrote:
> 
> What is IOMMU-GFX?  I can't find any references to the GFX part.
> 

IOMMU for Graphics, it is much more complex to assign a graphics device
than a regular device such as a NIC, HBA, etc.

-- 
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/c732498c-154d-3b4b-a12a-24f30762c553%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] HCL - Purism Librem 13 v2

[taii...@gmx.com]

On 09/16/2018 02:51 AM, 'awokd' via qubes-users wrote:
> On Sat, September 15, 2018 10:30 am, qubes-...@tutanota.com wrote:
>> Hi, during my email conversation with the Todd Weaver 

That liar comes out of nowhere with his super slick marketing and sets
the computing freedom movement back 10 years.

At first I thought it was just being naive but now as he persists it
seems more like malice.

puri.junk does NOT respect you, it is fully blobbed and the ME is not at
all disabled.

Todd weaver is a lying fraudster.

>> in the
>> pre-IME-disabled time, he told me they will fully disable the IME and AMT
>> within next week. After about a week they announced they did just that.
>> Are this links a lie?
>> https://puri.sm/posts/measuring-the-intel-me-to-create-a-more-secure-compu
>> ter/
>> > puter/>
>> https://puri.sm/posts/purism-librem-laptops-completely-disable-intel-mana
>> gement-engine/
>> > agement-engine/>
> 
> "Lie" depends on your definition of "completely". Skylake onwards
> processors can have much of ME disabled. I believe Purism with Heads and a
> handful of other manufacturers are using the technique here:
> http://blog.ptsecurity.com/2017/08/disabling-intel-me.html, but as you can
> see there are still some modules required for initialization before the
> HAP bit takes effect and skips the remainder. Additionally, there is an
> FSP blob needed for init. Currently shipping AMD CPUs are no better.

Skylake kernel still runs, that is not disabled and there is more than
enough ability to play dirty tricks like SMM rootkits or what not.

HAP is asking politely.

> 
>> Talking about alternatives: how the Qubes 4.0 stand with RYF certified
>> X200? Like for example this one: https://tehnoetic.com/laptops/tet-x200s
>>  and others like T400 and T500,
>> which can be found there as well. Working well? Any issues known? Thank
>> you
> 
> At present, RYF has not certified any laptops with hardware capable of
> running Qubes 4.0, but there are a couple older AMDs that can. A scale of
> hardware openness/owner control from most to least would be something
> like:
> 
> 10: OpenPOWER, RYF certified x86 with all blobs replaced- Qubes 4.0 can't
> run on either

Since you mention power and there aren't currently any laptops do you
mean laptops or desktops? In terms of desktops there are a variety that
qubes 4.0 can run on.

The future is POWER for all...

> 8: older AMD like A10-5750M- a couple blobs required but Qubes 4.0 works
> on these and the rest listed
> 6: pre-Skylake Intel with ME/HAP tweaks- a few more blobs and 2 ME modules
> required
> 4: Skylake+ Intel with ME/HAP tweaks, AMD Ryzen with PSP disabled in UEFI
> config- more blobs and modules required

That doesn't disable it! you are simply asking nicely for it to shut off
and hoping that it does so. It is not at all equivilant to say pre-core
intel systems where one really could disable it or even better one that
doesn't have any black boxes like the talos.

> 0: Intel/AMD x86 with no tweaks- most shipping volume today
> 
> ARM (& possibly RISC) is a special case in that the integrator can decide
> where on the scale they want to deliver their product, but neither support
> Qubes 4.0.
> 

-- 
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/c8670cee-80f5-1b08-0a82-8ffb60641867%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] whonix-ws-14 apt-get autoremove broke the template

[qubes-fan]

hi, after the last update of the whonix-ws-14 template with recommended apt-get 
autoremove, the template got broken. 
- Most of the apps disappeared
- torbrowser doesnt connect to net
- template itself cant be updated. 

user@host:~$ sudo apt-get update
Reading package lists... Done
E: Could not get lock /var/lib/apt/lists/lock - open (11: Resource temporarily 
unavailable)
E: Unable to lock directory /var/lib/apt/lists/

Upon launching TorBrowser, the wellcome page is "File not found". Upon trying 
to connect to a web page, "Secure connection failed".

any ideas?

-- 
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/LMdVNII--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Workspace names (even per-monitor)?

[Chris Laprise]

On 09/17/2018 02:23 PM, Teqleez Motley wrote:

Thanks for the reply. I have already the names technically just there as you 
say, but they do not show up in the switcher unless..:

a) I have to hover over the WS in the switcher to get a pop-up showing the 
name, but that only works if;
b) I have either minimized all windows so that no window shows in the WS switcher, or at 
least not maximized any of them, so that it leaves a tiny spot that I guess is possible 
to "hit", but which makes it too inconvenient, too easy to point to an open 
window instead of the workspace background, which then causes the popup to show the 
window name instead of the WS name.

So the point is how to show the workspace names without pointing, just visible 
all the time.

Alternatively, if each WS could be given a customizeable color, maybe that 
panel app could put a colored frame around each one, so we can easier 
distinguish between them.

And: 2+ monitors adds to the need for visible names:

With 2 or more monitors, both belonging as "monitor-0" and "monitor-1" to each WS, then the panel 
app has 2 sets of "areas" per WS... This is very practical when showing miniature windows, BUT, it ends up 
becoming an issue when we cannot see the WS name for the actual "pair". Not easy to see if it is the right or 
left one that belongs in the same group as the one you are looking at in the panel.

Complicating perspective;
- We are most likely going to get _more_ monitors, not less...

On a side note, related to navigating open windows on multiple Workspaces:
- The Tails live USB system has an ultra-practical (and "cool") "hud" that 
appears as an overlay when placing the cursor in the upper-right corner.
Is such a thing possible to get working with Qubes 4.x?


Yes,

KDE 5 pager settings lets you set how desktop workspaces are labeled. 
KDE also resolves quite a few bugs and annoyances I had with Xfce, 
although it does introduce a bug where VM systray icons aren't displayed 
(but are still present and work).


I don't know about labeling screens, but the pager settings do have a 
checkbox for displaying only the current screen.


--

Chris Laprise, tas...@posteo.net
https://github.com/tasket
https://twitter.com/ttaskett
PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886

--
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/2f29c4d6-a72e-d170-1ac2-73bf91f9754d%40posteo.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Open in Qube 3.0 beta released!

['Raffaele Florio' via qubes-users]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

>> here's my vote for whatever "gsoc idea" is , 'cause: I wish I could click on 
>> a URL in ThunderbirdVM and have it open a >> whonix-dvm by default . 
>> afaik there is no current way to do that.
> No, but there is a way to do that in chrome or firefox now

Exactly.

> In my setup thunderbird opens links with `qvm-open-in-vm` in a 
> "semi-permanent" dispVM (eg., a VM of DispVM class), this way I know the name 
> of the dispVM in advance - in my case 'dispBrowser' and I don't have to wait 
> each time for a dispVM to start. That's a bit of a security compromise, but 
> then I just have to power the VM to get it back to a clean slate.

Yeah, the same approach can be used with this extension. Indeed you can set the 
default qube to be a 'semi-permanent' disposable qube and that's all. 
Furthermore you could set to 'allow' the default policy of qubes.OpenURL, with 
the (default-)target set to that qube. In this way you get a very natural and 
more secure, way to navigate, with a little compromise.

Best Regards,
Raffaele.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXw2ov1HEFPFo+AVy07vJZYtrAOMFAluf8UkACgkQ07vJZYtr
AOMPbxAAgLSksez4gVQZjDCAk6QpB7RR64umDFtfvT8b8Ntgj78T4pS2NeCX9d3i
gKxTQexTgkSC2C8PzCxEtJXvZw236Wv0evt7zfdVDcgQVCfV2dlUn4NEO712Ze7i
8lKjtyMvV0H48ZfRrGDtcqbeSMUfQQOKvO/FdXtxO4qtgXl8Wj3mP4erWsSNLfwZ
Oi3AUuZFyrSSMytAy6RK8D1fSKMkfECRCMB3PO3aHm7rie5qTDypspw8C/Z/n/kL
vgs8Uja8MFvwbd3HrQOwhd24b96faNwc1Mtpw8IP0gBeHgHRpdFSFanziBYQYtBH
nwSot44HJ0fiuFpJjPSfRvYT/B/OjfCFgzrRNytSCtwBSUZdKfGXzoYKbskce0oX
tux3lNYq/EvLdVrSBL1zF9iv9Z6vtdPtu8xhIcbx50tgmdsbyrHW0o4va5mW7XGG
6rC0TnhuCSTT4MdXoifJB3ixs3/2ApLDFu5IYHfyeN74Z3XyqP3tQjdrLXCsrYwi
2pvHPbMTboQlgEPhKZv01K9BWUfuJ8MVeE8IDQNcqncQGOW9VhxvZEwjVIR25hoV
D4eb8w19x1vj0M7Uo4wfWJNC4k/YDvjWLzmQkxd9OhPBFp2Rfd1kEdYtpCXQu7rS
S1/COhefg6221y2rsvh5PLDvPr5xjqMI02XanBseHOsDlg+xe5Q=
=egnv
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2tnVkZKHtxSQOI9mblSh6KA4Z33r-6MtCCM5uC5ewAMwvBs7YCQoxYdka22qSojOWD-jy8FSOCxVIZB3oRN18p7n86AGPQSeXJLFKn7qelI%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Workspace names (even per-monitor)?

[Teqleez Motley]

Thanks for the reply. I have already the names technically just there as you 
say, but they do not show up in the switcher unless..: 

a) I have to hover over the WS in the switcher to get a pop-up showing the 
name, but that only works if;
b) I have either minimized all windows so that no window shows in the WS 
switcher, or at least not maximized any of them, so that it leaves a tiny spot 
that I guess is possible to "hit", but which makes it too inconvenient, too 
easy to point to an open window instead of the workspace background, which then 
causes the popup to show the window name instead of the WS name. 

So the point is how to show the workspace names without pointing, just visible 
all the time.

Alternatively, if each WS could be given a customizeable color, maybe that 
panel app could put a colored frame around each one, so we can easier 
distinguish between them.

And: 2+ monitors adds to the need for visible names:

With 2 or more monitors, both belonging as "monitor-0" and "monitor-1" to each 
WS, then the panel app has 2 sets of "areas" per WS... This is very practical 
when showing miniature windows, BUT, it ends up becoming an issue when we 
cannot see the WS name for the actual "pair". Not easy to see if it is the 
right or left one that belongs in the same group as the one you are looking at 
in the panel.

Complicating perspective;
- We are most likely going to get _more_ monitors, not less...

On a side note, related to navigating open windows on multiple Workspaces:
- The Tails live USB system has an ultra-practical (and "cool") "hud" that 
appears as an overlay when placing the cursor in the upper-right corner.
Is such a thing possible to get working with Qubes 4.x?

Regards,


On Mon, Sep 17, 2018, at 17:27, Daniel Allcock wrote:
> This is part of xfwm, and not qubes-specific. You can do it in the 
> workspaces preferences panel.  Under Names, where it says Workspace 1 
> etc., double click on one of them and you can then edit the name.
> 
> Not sure about your other questions.  Something I would like is for the 
> backgrounds of the labels in the window list on the panel to be color-
> coded.  the icons are color-coded but they are small and differences can 
> be subtle.
> 
> Best wishes,
> Daniel
> 
> > On Sep 17, 2018, at 9:18 AM, Teqleez Motley  
> > wrote:
> > 
> > Hi, is it possible to set custom names for workspaces in Qubes 4.x, for 
> > example using the xfconf settings editor?
> > 
> > I want them to show permanently in the workspace switcher panel app, like 
> > we can do with for example the dconf-editor in Gnome.
> > 
> > Regards,
> > 
> > 
> > -- 
> > You received this message because you are subscribed to the Google Groups 
> > "qubes-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an 
> > email to qubes-users+unsubscr...@googlegroups.com.
> > To post to this group, send email to qubes-users@googlegroups.com.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/qubes-users/CAOQTMaxZUXwLuhVe28craAdb%3DgHfU2dQH7K66Yhp2uHRp6s1_Q%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
> 


-- 
Regards,
Teqleez

-- 
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/1537208612.3539953.1511129088.6399E7AD%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Open in Qube 3.0 beta released!

['Raffaele Florio' via qubes-users]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

> Can't quite understand how or why this would be used, though..? am sure 
> it makes sense to the smart folks :)

For the how: it's explained (I hope clearly.. :)) in the welcome page of the 
extension, it will be showed one time after the installation.
For the why: it should be used because you shouldn't open untrusted stuff in a 
qube with more trust than that resource or with other purpose..
This extension embraces the Qubes philosophy and applies it also on the browser.


> here's my vote for whatever "gsoc idea" is , 'cause: I wish I could click on 
> a URL in ThunderbirdVM and have it open a whonix-dvm by default . afaik 
> there is no current way to do that.

I'll implement this feature when Thunderbird will support the WebExtension API 
and it seems soon.


Best Regards,
Raffaele.
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEXw2ov1HEFPFo+AVy07vJZYtrAOMFAluf63QACgkQ07vJZYtr
AOMigQ//dTGBxekTWuYCB+pv33rZGtB1YXYnizJIlwI2xZ+T4R7Jw+w+qtYW2769
bKOnnubLie4znOoBtVh6mSfJlpDNsU5oEP9/l/pFBmtcIXAIU215SdmxlATVPn+s
o0p7V1vzE4eQo6ryHpS074I0Kb6acRPyvNHTLy+ytan+S3SJ8e932W+vDOZ5F1qZ
FxwM7aE9qCP7xBC6ljgKhsc3st43+oDljHbgmd6x5cW7kx9neRdOH892tRjDq/hp
pMXUoXfJtLU9GPQLClTSQRE/tVFhCLs4iWRlxSit4W9STggj/ZYJCX1GVAeCyqEc
PMAQfIlLVHuOWBaQt7emHudIzPjM9HZLuZYyL4pYf2xuTqSFgOdIDP2ETWrLlfkg
2Nq/egikQNxx3CJ1UL1grqcRm8LC68wKVp1+Gzbnls9Ivjt4Z95oBOR7Ox6TJvf9
Ee1He5l9G0Fs8t1vxoZIuhbmajw7DcgFaheyjSMGU8iS57ASdcxD6VYSYeeEwfLN
G94vYWwSKFs5Z0mb1ed688ntyJ1MZ6N0gcdtHQeEph/HtKtMEsjL9Joj4cWYf9nk
NWz6qyMyHlKwK9BCTv4AaIxPMH3kotJ79bJzwWisMyfYeCRzhuceTFMfB2XdKEHA
S+C26mFBgNEtkczNcYem3cW9bscBrEdzUAXPqob1/1HHeZFgHW0=
=RZ6u
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/Ijm6ech9o7WvY5ctfgPI0QimBotNpzapXS1EonScosFONJNx6luJAI2gIW4aPhxpaU13Drp0M4OFguEOLxntDfWpiYNcXLXJDoy61v-koQ4%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Dracut failing on ASUS Z270A Motherboard

[aaronngray]

Verified on second system also with different manufacturer USB stick

On Monday, 17 September 2018 17:52:54 UTC+1, aaron...@gmail.com  wrote:
> Dracut failing on ASUS Z270A Motherboard based on Intel Z270 chipset 
> 
> Attached rdsosreport.txt
> ~~
> 
> + cat /lib/dracut/dracut-046-2.git20170811.fc25
> dracut-046-2.git20170811.fc25
> + cat /proc/cmdline
> inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1
> + '[' -f /etc/cmdline ']'
> + for _i in '/etc/cmdline.d/*.conf'
> + '[' -f /etc/cmdline.d/99-anaconda-disable-disk-activation.conf ']'
> + echo /etc/cmdline.d/99-anaconda-disable-disk-activation.conf
> /etc/cmdline.d/99-anaconda-disable-disk-activation.conf
> + cat /etc/cmdline.d/99-anaconda-disable-disk-activation.conf
> rd.dm=0
> rd.md=0
> rd.lvm=0
> rd.luks=0
> + cat /proc/self/mountinfo
> 1 1 0:2 / / rw shared:1 - rootfs rootfs rw,size=15998836k,nr_inodes=3999709
> 18 1 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
> 19 1 0:5 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw
> 20 1 0:6 / /dev rw,nosuid shared:9 - devtmpfs devtmpfs 
> rw,size=15998852k,nr_inodes=3999713,mode=755
> 21 18 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - 
> securityfs securityfs rw
> 22 20 0:19 / /dev/shm rw,nosuid,nodev shared:10 - tmpfs tmpfs rw
> 23 20 0:20 / /dev/pts rw,nosuid,noexec,relatime shared:11 - devpts devpts 
> rw,gid=5,mode=620,ptmxmode=000
> 24 1 0:21 / /run rw,nosuid,nodev shared:12 - tmpfs tmpfs rw,mode=755
> 25 18 0:22 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs 
> ro,mode=755
> 26 25 0:23 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 
> - cgroup cgroup 
> rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
> 27 18 0:24 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore 
> pstore rw
> 28 18 0:25 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime 
> shared:7 - efivarfs efivarfs rw
> 29 25 0:26 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:13 
> - cgroup cgroup rw,memory
> 30 25 0:27 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
> shared:14 - cgroup cgroup rw,perf_event
> 31 25 0:28 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
> shared:15 - cgroup cgroup rw,cpu,cpuacct
> 32 25 0:29 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
> shared:16 - cgroup cgroup rw,net_cls,net_prio
> 33 25 0:30 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:17 - 
> cgroup cgroup rw,blkio
> 34 25 0:31 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:18 
> - cgroup cgroup rw,cpuset
> 35 25 0:32 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:19 
> - cgroup cgroup rw,devices
> 36 25 0:33 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:20 
> - cgroup cgroup rw,freezer
> 37 25 0:34 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:21 - 
> cgroup cgroup rw,pids
> 38 25 0:35 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:22 
> - cgroup cgroup rw,hugetlb
> 61 18 0:36 / /sys/kernel/config rw,relatime shared:23 - configfs configfs rw
> + cat /proc/mounts
> rootfs / rootfs rw,size=15998836k,nr_inodes=3999709 0 0
> sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
> proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
> devtmpfs /dev devtmpfs rw,nosuid,size=15998852k,nr_inodes=3999713,mode=755 0 0
> securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
> tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
> devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 
> 0 0
> tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
> tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
> cgroup /sys/fs/cgroup/systemd cgroup 
> rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
>  0 0
> pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
> efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 > 0
> cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
> cgroup /sys/fs/cgroup/perf_event cgroup 
> rw,nosuid,nodev,noexec,relatime,perf_event 0 0
> cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
> rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
> cgroup /sys/fs/cgroup/net_cls,net_prio cgroup 
> rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
> cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
> cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
> cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 
> 0 0
> cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 
> 0 0
> cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
> cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 
> 0 0
> configfs /sys/kernel/config configfs rw,relatime 0 0
> + 

[qubes-users] Dracut failing on ASUS Z270A Motherboard

[aaronngray]

Dracut failing on ASUS Z270A Motherboard based on Intel Z270 chipset 

Attached rdsosreport.txt
~~

+ cat /lib/dracut/dracut-046-2.git20170811.fc25
dracut-046-2.git20170811.fc25
+ cat /proc/cmdline
inst.stage2=hd:LABEL=Qubes-R4.0-x86_64 i915.alpha_support=1
+ '[' -f /etc/cmdline ']'
+ for _i in '/etc/cmdline.d/*.conf'
+ '[' -f /etc/cmdline.d/99-anaconda-disable-disk-activation.conf ']'
+ echo /etc/cmdline.d/99-anaconda-disable-disk-activation.conf
/etc/cmdline.d/99-anaconda-disable-disk-activation.conf
+ cat /etc/cmdline.d/99-anaconda-disable-disk-activation.conf
rd.dm=0
rd.md=0
rd.lvm=0
rd.luks=0
+ cat /proc/self/mountinfo
1 1 0:2 / / rw shared:1 - rootfs rootfs rw,size=15998836k,nr_inodes=3999709
18 1 0:18 / /sys rw,nosuid,nodev,noexec,relatime shared:2 - sysfs sysfs rw
19 1 0:5 / /proc rw,nosuid,nodev,noexec,relatime shared:8 - proc proc rw
20 1 0:6 / /dev rw,nosuid shared:9 - devtmpfs devtmpfs 
rw,size=15998852k,nr_inodes=3999713,mode=755
21 18 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:3 - 
securityfs securityfs rw
22 20 0:19 / /dev/shm rw,nosuid,nodev shared:10 - tmpfs tmpfs rw
23 20 0:20 / /dev/pts rw,nosuid,noexec,relatime shared:11 - devpts devpts 
rw,gid=5,mode=620,ptmxmode=000
24 1 0:21 / /run rw,nosuid,nodev shared:12 - tmpfs tmpfs rw,mode=755
25 18 0:22 / /sys/fs/cgroup ro,nosuid,nodev,noexec shared:4 - tmpfs tmpfs 
ro,mode=755
26 25 0:23 / /sys/fs/cgroup/systemd rw,nosuid,nodev,noexec,relatime shared:5 - 
cgroup cgroup 
rw,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
27 18 0:24 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:6 - pstore 
pstore rw
28 18 0:25 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:7 
- efivarfs efivarfs rw
29 25 0:26 / /sys/fs/cgroup/memory rw,nosuid,nodev,noexec,relatime shared:13 - 
cgroup cgroup rw,memory
30 25 0:27 / /sys/fs/cgroup/perf_event rw,nosuid,nodev,noexec,relatime 
shared:14 - cgroup cgroup rw,perf_event
31 25 0:28 / /sys/fs/cgroup/cpu,cpuacct rw,nosuid,nodev,noexec,relatime 
shared:15 - cgroup cgroup rw,cpu,cpuacct
32 25 0:29 / /sys/fs/cgroup/net_cls,net_prio rw,nosuid,nodev,noexec,relatime 
shared:16 - cgroup cgroup rw,net_cls,net_prio
33 25 0:30 / /sys/fs/cgroup/blkio rw,nosuid,nodev,noexec,relatime shared:17 - 
cgroup cgroup rw,blkio
34 25 0:31 / /sys/fs/cgroup/cpuset rw,nosuid,nodev,noexec,relatime shared:18 - 
cgroup cgroup rw,cpuset
35 25 0:32 / /sys/fs/cgroup/devices rw,nosuid,nodev,noexec,relatime shared:19 - 
cgroup cgroup rw,devices
36 25 0:33 / /sys/fs/cgroup/freezer rw,nosuid,nodev,noexec,relatime shared:20 - 
cgroup cgroup rw,freezer
37 25 0:34 / /sys/fs/cgroup/pids rw,nosuid,nodev,noexec,relatime shared:21 - 
cgroup cgroup rw,pids
38 25 0:35 / /sys/fs/cgroup/hugetlb rw,nosuid,nodev,noexec,relatime shared:22 - 
cgroup cgroup rw,hugetlb
61 18 0:36 / /sys/kernel/config rw,relatime shared:23 - configfs configfs rw
+ cat /proc/mounts
rootfs / rootfs rw,size=15998836k,nr_inodes=3999709 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
devtmpfs /dev devtmpfs rw,nosuid,size=15998852k,nr_inodes=3999713,mode=755 0 0
securityfs /sys/kernel/security securityfs rw,nosuid,nodev,noexec,relatime 0 0
tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
tmpfs /sys/fs/cgroup tmpfs ro,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/systemd cgroup 
rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd
 0 0
pstore /sys/fs/pstore pstore rw,nosuid,nodev,noexec,relatime 0 0
efivarfs /sys/firmware/efi/efivars efivarfs rw,nosuid,nodev,noexec,relatime 0 0
cgroup /sys/fs/cgroup/memory cgroup rw,nosuid,nodev,noexec,relatime,memory 0 0
cgroup /sys/fs/cgroup/perf_event cgroup 
rw,nosuid,nodev,noexec,relatime,perf_event 0 0
cgroup /sys/fs/cgroup/cpu,cpuacct cgroup 
rw,nosuid,nodev,noexec,relatime,cpu,cpuacct 0 0
cgroup /sys/fs/cgroup/net_cls,net_prio cgroup 
rw,nosuid,nodev,noexec,relatime,net_cls,net_prio 0 0
cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
cgroup /sys/fs/cgroup/pids cgroup rw,nosuid,nodev,noexec,relatime,pids 0 0
cgroup /sys/fs/cgroup/hugetlb cgroup rw,nosuid,nodev,noexec,relatime,hugetlb 0 0
configfs /sys/kernel/config configfs rw,relatime 0 0
+ blkid
/dev/sdb1: LABEL="QUBES-R4_0-" UUID="F05F-3411" TYPE="vfat" 
PARTUUID="133e46b5-01"
+ blkid -o udev
ID_FS_LABEL=QUBES-R4_0-
ID_FS_LABEL_ENC=QUBES-R4_0-
ID_FS_UUID=F05F-3411
ID_FS_UUID_ENC=F05F-3411
ID_FS_TYPE=vfat
ID_FS_PARTUUID=133e46b5-01
+ ls -l /dev/disk/by-id /dev/disk/by-label /dev/disk/by-partuuid 
/dev/disk/by-path 

[qubes-users] Window menu grouped by VMs?

[Teqleez Motley]

Hi all,

I am using the Window Menu panel app to show/go to already open windows.
There they are grouped per Workspace.

- I wonder if there is a possibility to have those open windows grouped by
which VM they belong to as well/instead, so that we jump to the actual
workspace when clicking on an open window in that menu?

(I´d like to have 2 such buttons; the one we already have grouping by WS,
and another grouping them by VM.)

Regards,

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAOQTMayinSqgeZj-x44JYWmVKAp7P5HwzkQ6jJSF6G-Gc1j%2BaQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Workspace names (even per-monitor)?

[Teqleez Motley]

Hi, is it possible to set custom names for workspaces in Qubes 4.x, for
example using the xfconf settings editor?

I want them to show permanently in the workspace switcher panel app, like
we can do with for example the dconf-editor in Gnome.

Regards,

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAOQTMaxZUXwLuhVe28craAdb%3DgHfU2dQH7K66Yhp2uHRp6s1_Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: qubes-u2f not installing on templates

[Ivan Mitev]

On 9/17/18 3:32 PM, digitalintag...@gmail.com wrote:
> On Monday, September 17, 2018 at 6:24:45 AM UTC-6, digital...@gmail.com wrote:
>> https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/
>>
>> Wojtek shared this on 9/11/18.
>>
>> Following the instructions, I'm not able to install qubes-u2f on either my 
>> debian or fedora templates. Anyone else have similar issues?

The packages are still in the current-testing repositories, and you
likely didn't enable them.


> to clarify, the package manager doesn't find the named package on either 
> distro.
I don't use the graphical package manager so no idea how to enable
current-testing there, but if you use a terminal it's pretty
straightforward:

For dom0:

sudo qubes-dom0-update \
--enablerepo=qubes-dom0-current-testing qubes-u2f-dom0

And for a fedora (template)VM:

sudo dnf --enablerepo=qubes-vm-r4.0-current-testing install \
qubes-u2f


There should be something similar for debian's apt-get

-- 
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/27098e9b-9636-92c1-4eff-654fd5c21dfa%40maa.bz.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: qubes-u2f not installing on templates

[digitalintaglio]

On Monday, September 17, 2018 at 6:24:45 AM UTC-6, digital...@gmail.com wrote:
> https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/
> 
> Wojtek shared this on 9/11/18.
> 
> Following the instructions, I'm not able to install qubes-u2f on either my 
> debian or fedora templates. Anyone else have similar issues?

to clarify, the package manager doesn't find the named package on either distro.

I ran the qubes global updater in dom0 and it still didn't work.

BTW, I'm relatively new to qubes. I loaded it on a relatively new laptop and 
have been slowly acclimating over the last 3 months or so.

-- 
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/0fd7022f-0f29-4b5f-91ec-f9cbe0df4aec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: qubes-u2f not installing on templates

[digitalintaglio]

On Monday, September 17, 2018 at 6:24:45 AM UTC-6, digital...@gmail.com wrote:
> https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/
> 
> Wojtek shared this on 9/11/18.
> 
> Following the instructions, I'm not able to install qubes-u2f on either my 
> debian or fedora templates. Anyone else have similar issues?

to clarify, the package manager doesn't find the named package on either distro.

-- 
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/a136bc8e-c657-4c8d-88ab-739e120f0bae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] qubes-u2f not installing on templates

[digitalintaglio]

https://www.qubes-os.org/news/2018/09/11/qubes-u2f-proxy/

Wojtek shared this on 9/11/18.

Following the instructions, I'm not able to install qubes-u2f on either my 
debian or fedora templates. Anyone else have similar issues?

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ff1651d6-6430-4ced-a335-ba17615405e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installed software gets remove after reboot

[Hugo Costa]

On Monday, 17 September 2018 11:13:04 UTC+1, awokd  wrote:
> Stuart Perkins:
> > 
> > 
> > On Sun, 16 Sep 2018 23:47:08 -0700 (PDT)
> > Hugo Costa  wrote:
> > 
> >> Hey,
> >>
> >> I couldn't find the answer to this problem that has been annoying me for a 
> >> while. Basically, Qubes 4.0, fedora 28 and PVH qubes. 
> >> Problem is simple. I install something in qube X, I reboot my machine and 
> >> it's not there anymore. I've tried several ways but this always happens. 
> >> The only way for me to have a piece of software constantly in my qubes is 
> >> by installing it in the template. 
> >>
> >> Is there a way to make sure the software stays installed in the qube 
> >> without having to install it on the template?
> >>
> >> Regards,
> >>
> >> Hugo
> >>
> > 
> > That would defeat the purpose of the template.  If you only want this 
> > software in ONE qube, consider creating a special template.  The whole 
> > template concept is to prevent changes to the software from persisting 
> > unless done in the template (intentionally).  Separation of software and 
> > data.
> 
> What Stuart said- see
> https://www.qubes-os.org/getting-started/#appvms-qubes-and-templatevms.
> You can also create a Standalone qube if you don't need/want the benefit
> of templates on that single qube.

Makes perfect sense, thank you for both answers. I'll get a standalone for this 
software.

-- 
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/d79c36b7-c86c-4ad9-9d97-3c165741c061%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Symlinks for "some" AppMVs to other partition in Qubes 4.x?

[Rusty Bird]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Teqleez Motley:
> I want to store only some AppVMs (and some custom TemplateVMs) on a
> different ext4 partition.

See , with the
exception that if you want to store your VMs in files on ext4, you'd
use the 'file' storage driver instead of 'lvm_thin':

$ qvm-pool --add  file -o dir_path=/mnt/your-partition/subdir

But note that 'file' is not in the best state. It has the fewest
features (online TRIM/discard unsupported; doesn't show which VMs
should be restarted to pick up template upgrades; can store only one
revision and can't revert to it) and yet the most complex code. So
consider just adding a regular 'lvm_thin' pool, like on the webpage.

Another, more bleeding-edge alternative - if you can set up your
partition as btrfs rather than ext4 - would be the 'file-reflink'
driver. In my biased opinion (having written it) it's solid. Though
you may want to wait for the qubes-core-dom0-4.0.30 package, which
will presumably include lots of recent improvements and a safety
check* before 'qvm-volume revert'.

Rusty


* 'qvm-volume revert' on a 'file-reflink' volume of a running or not
  cleanly stopped VM used to essentially throw away the revision.
-BEGIN PGP SIGNATURE-

iQJ8BAEBCgBmBQJbn4hWXxSAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4NEI1OUJDRkM2MkIxMjlGRTFCMDZEMDQ0
NjlENzhGNDdBQUYyQURGAAoJEEadePR6ryrfKU0QAJGutU6eXem66oOwgWIh1Zef
IRcS7+AEXKgQBVMibVqepFWn0jMxy1AQd9RS4zrtrGb1phDmgmJMqhTBHqdYqkHU
6pgN+jMfif/4zPzLCaIpUNQLpIUKQQe7RK85JF6OUsyy8QVERslCnfY2hKOdHm/r
9iCjG33C/bGb1K+sefU0s5AqXZrc7nsBg5rpIpfpZMnsZAsMPONv92maqPa4xmHt
8VkYRYQ6ujhgOHyggp+vbFhpH6778qoROdcrCCWuE7GLYAJfv4I6jTuYoul8CTCC
3yvkKz9lL3Jd3mUyl3ChwZftn8dtwSm/wC5iR0+ceN2xj1AyGIawW8u7uxeEo1ll
3WsObi9tg1AOJNPtEbXgEbbzSgbnLP6vw42BPn6rQVZOj9j+hm3M86Z+Q66rQI1Y
0zgYtFNijUHBlWe4M5c222vyOjtkCRivVug2B6yhOLsb+MrAau4nlIssZYbO2UHm
jRmTkSntdGjNAdaymxFN63i9rM4IYmbIdJG0U0LP+gWu7qfcLeuzKQX4rzVQcCq1
39QqK6heKe/OgZyW68N0TXkoXsCLGExgOxi/WIgdmTxiOKTeTyupniZe6aw8Qx2L
r2piIf4q6wyTKarbXGgOWpuU6R2K82iWVj3RADzwlo/1nQxWwkjfDdfHA6TbHHws
8xVBNGRxTpCE/PXv7DNU
=n5Mm
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20180917105622.GA1649%40mutt.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] HCL - Purism Librem 13 v2

[qubes-fan]

It is offtopic, but I gues he is referring to the need to run JS to have 
Protonmail running with web-browser and register, or a need to run Bridge to 
use the Thenderbird. The JS can be anytime replaced with a malicious one and it 
is game over. 

All clear but it really depends on the OPSEC one has. 

My point here was actually about running Qubes, which I consider as one of the 
best security solutions available out there in tandem with Tails, on the as 
much as possible secure HW. I know I knowdont stone me, but if I use a 
reasonably secure OS, I would like to use it on reasonably secure hardware 
(laptop), if thats anyhow possible. 


Sep 16, 2018, 9:57 AM by riverbo...@gmail.com:

>>
>> This made me laugh out loud. All your ranting and raving about security and 
>> dishonesty, and you sent the message using PROTON MAIL. Good lord. Talk 
>> about dishonesty and pseudo-security.
>>
>
> Off Topic - but... would you care to elaborate what fault you alleged in 
> Protonmail and your source?
>
> -- 
> 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/dabcb4d5-4400-47a8-b624-3b2cd9c5e6b5%40googlegroups.com
>  
> >
>  .
> For more options, visit > https://groups.google.com/d/optout 
> > .
>

-- 
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/LMb0l84--3-1%40tutanota.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installed software gets remove after reboot

['awokd' via qubes-users]

Stuart Perkins:
> 
> 
> On Sun, 16 Sep 2018 23:47:08 -0700 (PDT)
> Hugo Costa  wrote:
> 
>> Hey,
>>
>> I couldn't find the answer to this problem that has been annoying me for a 
>> while. Basically, Qubes 4.0, fedora 28 and PVH qubes. 
>> Problem is simple. I install something in qube X, I reboot my machine and 
>> it's not there anymore. I've tried several ways but this always happens. The 
>> only way for me to have a piece of software constantly in my qubes is by 
>> installing it in the template. 
>>
>> Is there a way to make sure the software stays installed in the qube without 
>> having to install it on the template?
>>
>> Regards,
>>
>> Hugo
>>
> 
> That would defeat the purpose of the template.  If you only want this 
> software in ONE qube, consider creating a special template.  The whole 
> template concept is to prevent changes to the software from persisting unless 
> done in the template (intentionally).  Separation of software and data.

What Stuart said- see
https://www.qubes-os.org/getting-started/#appvms-qubes-and-templatevms.
You can also create a Standalone qube if you don't need/want the benefit
of templates on that single qube.

-- 
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/6fee0ea9-0ed1-f908-90b7-9dc5bdc4739f%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Time problem

['awokd' via qubes-users]

ptitv...@gmail.com:
> Thank you.
> After using Qubes for other things, I've seen that the time in dom0 was 
> corrected automatically.
> So by going back to Fedora 26 in sys-net solved my problem.
> Maybe I should open an issue ticket.
> 
> Nevertheless I will check it with your link, seems exactly what I needed 
> yesterday! :-D

https://github.com/QubesOS/qubes-issues/issues/3983 - Fedora 28 should
be fixed in a few days once the patch gets pushed from Testing to
general release.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/713d592e-1d20-0c56-3b58-78699c9e299c%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Installed software gets remove after reboot

[Stuart Perkins]

On Sun, 16 Sep 2018 23:47:08 -0700 (PDT)
Hugo Costa  wrote:

>Hey,
>
>I couldn't find the answer to this problem that has been annoying me for a 
>while. Basically, Qubes 4.0, fedora 28 and PVH qubes. 
>Problem is simple. I install something in qube X, I reboot my machine and it's 
>not there anymore. I've tried several ways but this always happens. The only 
>way for me to have a piece of software constantly in my qubes is by installing 
>it in the template. 
>
>Is there a way to make sure the software stays installed in the qube without 
>having to install it on the template?
>
>Regards,
>
>Hugo
>

That would defeat the purpose of the template.  If you only want this software 
in ONE qube, consider creating a special template.  The whole template concept 
is to prevent changes to the software from persisting unless done in the 
template (intentionally).  Separation of software and data.

-- 
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/20180917043219.71cdc2dd%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Installed software gets remove after reboot

[Hugo Costa]

Hey,

I couldn't find the answer to this problem that has been annoying me for a 
while. Basically, Qubes 4.0, fedora 28 and PVH qubes. 
Problem is simple. I install something in qube X, I reboot my machine and it's 
not there anymore. I've tried several ways but this always happens. The only 
way for me to have a piece of software constantly in my qubes is by installing 
it in the template. 

Is there a way to make sure the software stays installed in the qube without 
having to install it on the template?

Regards,

Hugo

-- 
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/14e8f1e6-0b91-4ac1-9fba-6b22213bc917%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.