Re: AW: Re: AW: [qubes-users] Re: i3 under Qubes 4 RC3

[Florian Brandes]

On 22.02.2018 22:39, '[799]' via qubes-users wrote:

Hello Florian

 Original-Nachricht 
An 22. Feb. 2018, 09:07, Florian Brandes schrieb:

 > I use i3 under Q4rc4 without any issues
 > or problems.

Would you mind sharing your i3-config files?



Hi,

not at all. config file taken from /home/dom0user/.config/i3/config

The only line I changed from the default setup is:
# start dmenu (a program launcher)
bindsym $mod+d exec --no-startup-id i3-dmenu-desktop --dmenu="dmenu -i -nb #d2d2d2 
-nf #00 -sb #63a0ff"

where I added the "-i" option.

I also added the /usr/bin/qubes-i3status bash script.

I changed

local qubes=$(qvm-ls 2>/dev/null | grep ' \* ' | wc -l)
to
local qubes=$(qvm-ls 2>/dev/null | grep 'Running ' | wc -l)


and
local disk=`df -h / | tail -n 1 | awk '{print $4}'`
to
local disk=`sudo lvs --noheadings -o lv_size,data_percent /dev/mapper/qubes_dom0-pool00 | 
perl -pe 's/\s*([0-9.]+)([a-zA-Z]*)\s+([0-9.]+).*/sprintf("%.1f%s", ($1 * (100 
-$3) \/ 100.0), $2)/e'`

Both are attached.

Regards,

Florian






--
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/7b75712c-3288-90aa-d939-b76efab12197%40gmx.de.
For more options, visit https://groups.google.com/d/optout.
# This file has been auto-generated by i3-config-wizard(1).
# It will not be overwritten, so edit it as you like.
#
# Should you change your keyboard layout some time, delete
# this file and re-run i3-config-wizard(1).
#

# i3 config file (v4)
#
# Please see http://i3wm.org/docs/userguide.html for a complete reference!

set $mod Mod4

# Font for window titles. Will also be used by the bar unless a different font
# is used in the bar {} block below.
# This font is widely installed, provides lots of unicode glyphs, right-to-left
# text rendering and scalability on retina/hidpi displays (thanks to pango).
font pango:DejaVu Sans Mono 8
# Before i3 v4.8, we used to recommend this one as the default:
# font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
# The font above is very space-efficient, that is, it looks good, sharp and
# clear in small sizes. However, its unicode glyph coverage is limited, the old
# X core fonts rendering does not support right-to-left and this being a bitmap
# font, it doesn’t scale on retina/hidpi displays.

client.background   dom0#121212
client.focused  dom0#522702 #522702 #ff #a6907d
client.focused_inactive dom0#522702 #361a01 #ff #a6907d
client.unfocuseddom0#522702 #361a01 #99 #a6907d
client.urgent   dom0#66 #a6907d #ce #a6907d

client.background   red #121212
client.focused  red #e53b27 #e53b27 #ff #f19b90
client.focused_inactive red #e53b27 #902519 #ff #f19b90
client.unfocusedred #e53b27 #902519 #99 #f19b90
client.urgent   red #e53b27 #f19b90 #ce #f19b90

client.background   orange  #121212
client.focused  orange  #d05f03 #d05f03 #ff #daa67e
client.focused_inactive orange  #d05f03 #7b3702 #ff #daa67e
client.unfocusedorange  #d05f03 #7b3702 #99 #daa67e
client.urgent   orange  #d05f03 #daa67e #ce #daa67e

client.background   yellow  #121212
client.focused  yellow  #999b00 #999b00 #ff #cacb7c
client.focused_inactive yellow  #999b00 #666700 #ff #cacb7c
client.unfocusedyellow  #999b00 #666700 #99 #cacb7c
client.urgent   yellow  #999b00 #cacb7c #ce #cacb7c

client.background   green   #121212
client.focused  green   #04af5b #04af5b #ff #7dd5aa
client.focused_inactive green   #04af5b #02713b #ff #7dd5aa
client.unfocusedgreen   #04af5b #02713b #99 #7dd5aa
client.urgent   green   #04af5b #7dd5aa #ce #7dd5aa

client.background   gray#121212
client.focused  gray#8c959f #8c959f #ff #c3c8cd
client.focused_inactive gray#8c959f #676d75 #ff #c3c8cd
client.unfocusedgray#8c959f #676d75 #99 #c3c8cd
client.urgent   gray#8c959f #c3c8cd #ce #c3c8cd

client.background   blue#121212
client.focused  blue#3384d6 #3384d6 #ff #95bee8
client.focused_inactive blue#3384d6 #1f5082 #ff #95bee8
client.unfocusedblue#3384d6 #1f5082 #99 #95bee8
client.urgent   blue#3384d6 #95bee8 #ce #95bee8

client.background   purple  #121212
client.focused  purple  #8f5cbe #8f5cbe #ff #c6abdd
client.focused_inactive purple  #8f5cbe #5c3e78 #ff #c6abdd
client.unfocusedpurple  #8f5cbe #5c3e78 #99 #c6abdd
client.urgent   

Re: [qubes-users] Install to Dell T3610, no Intel graphics, VNC install, NVS 310

['awokd' via qubes-users]

On Thu, February 22, 2018 1:39 pm, CMaurice wrote:
> So, having exhausted other options as far as I could tell, followed the
> instructions for installing over VNC, which went ok.
>
> Legacy boot elected in BIOS for hd and for USB media at install.
>
>
> But on boot without nomodeset and no i915 entry went quickly to a reboot
>
>
> Log nomodeset.out attached.
>
>
> Booting without nomodeset and with modprobe.blacklist=nouveau in place of
> the i915 entry failed at '[OK] Started Accounts Service' (logs dmesg.txt,
> Xorg.9.log attached).
>
>
>
> I'd be grateful for ideas on how to proceed, even perhaps alternate
> graphics card suggestions.

Saw in your other email this is Qubes 4.0rc4. Looks like you've tried all
the basic steps and then some. Does this laptop have a way to use Intel
integrated graphics? If so, check
https://www.qubes-os.org/doc/intel-igfx-troubleshooting/ for the command
line option to enable that driver.
Nvidia and Linux generally don't work well together, and I don't have any
of their hardware so don't have much insight there. AMD RX580s and earlier
(maybe newer too but not a lot of data) work pretty well with Qubes, as
does Intel video (usually).

-- 
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/8fcccbca856f56f4c6aa613de3dfad29.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

['awokd' via qubes-users]

On Thu, February 22, 2018 9:51 pm, Daniil .Travnikov wrote:
> When I updated last time my BIOS Firmware, it was been from here:
> https://downloadcenter.intel.com/download/23908/Intel-Server-Board-S5520HC
> -S5500HCV-S5520HCT-and-Intel-Workstation-Board-S5520SC-Firmware-Update-Pa
> ckage-for-EFI?product=36599
>
> "S5520HC S5500HCV S5520HCT S5520SC BIOS Recovery Package for EFI"
>
>
>
> Maybe this is the problem, that my bios in some reason could working
> always with EFI mode even if I change it on 'Disable' in bios menu?

I don't think that's the problem, since in your other email you said it
was booting from GRUB, correct? Assuming that board uses Intel video, have
you seen https://www.qubes-os.org/doc/intel-igfx-troubleshooting/ ?

-- 
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/c01db925d99feba35470d56a79cd9534.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] USB VM based on fedora-26 doesn't pass block devices

['awokd' via qubes-users]

On Tue, February 20, 2018 5:02 pm, Kelly Dean wrote:
> I'm getting the same bug as reported at
> https://github.com/QubesOS/qubes-issues/issues/2018

>
> qvm-block -l says the USB device is attached to the appVM. But the appVM
> has no /dev/xvdi

I wonder if this might be related to a recent patch in testing. Are both
your dom0 and templates on the same repository (current vs. testing) and
updated? A recent patch also required a reboot once both were updated.

-- 
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/36700ab0f8449b3a840191b1f731633d.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Bitmessage Shortcut in Whonix APP VM

['awokd' via qubes-users]

On Sun, February 18, 2018 5:47 pm, klausdiet...@mail2tor.com wrote:
> Hey,
>
>
> i want to know how to set a shortcut in the whonix App VM. I installed
> Bitmessage in Whonix WS Template and used this to create a shortcut:
>
>
> https://qubes-os.org/doc/managing-appvm-shortcuts/
>
>
> But it didn´t work this way. Any Ideas?

I don't see why it shouldn't work. What version of Qubes, and what do you
mean by it didn't work?

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

Re: [qubes-users] How to delete or upgrade app VMs?

[Kyle Breneman]

> Yes, somewhat, but I found #7 on this page
>  more
> helpful.  I've almost gotten everything configured the way I want, but one
> thing still puzzles me.  I used "sudo dnf remove qubes-template-fedora-23"
> from the terminal (mistakenly did this before deleting/switching all app
> VMs that depended on it), but apparently that didn't completely remove
> fedora-23 template VM because even after several restarts the fedora-23
> template VM is still showing up in the Qubes VM Manager.  How can I get rid
> of it for good?
>
​
​See link in first line.  I forgot link the first time I sent 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/CAOtZr%3DGQ6P8trq-8EH73bY3VnxMKuPC-dt0kuCm%2B3B2TExvt%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] How to delete or upgrade app VMs?

[Kyle Breneman]

>Does this help?
>https://www.qubes-os.org/doc/templates/fedora/#after-installing


Yes, somewhat, but I found #7 on this page more helpful.  I've almost
gotten everything configured the way I want, but one thing still puzzles
me.  I used "sudo dnf remove qubes-template-fedora-23" from the terminal
(mistakenly did this before deleting/switching all app VMs that depended on
it), but apparently that didn't completely remove fedora-23 template VM
because even after several restarts the fedora-23 template VM is still
showing up in the Qubes VM Manager.  How can I get rid of it for good?

Regards,
Kyle

On Wed, Feb 21, 2018 at 1:25 AM, Andrew David Wong  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2018-02-20 22:48, Kyle Breneman wrote:
> > I'm running Qubes 3.2.  I have the default Fedora 23 template VM, and the
> > default app VMs built from it, but I also installed a Fedora 26 template
> > VM.  Now I want to delete or upgrade my Fedora 23 app VMs, but I cannot
> > figure out how to do this.  The "Delete VM" menu option in the Qubes VM
> > Manager always seems to be grayed-out.  How can I either delete these app
> > VMs based on Fedora 23, or switch them over to my Fedora 26 template?
> >
> > Regards,
> > Kyle
> >
>
> Does this help?
>
> https://www.qubes-os.org/doc/templates/fedora/#after-installing
>
> - --
> Andrew David Wong (Axon)
> Community Manager, Qubes OS
> https://www.qubes-os.org
>
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAlqNELUACgkQ203TvDlQ
> MDDjCBAAuCHhRevjEfHIRhSkpTs6QIh8c8BBy+dWceVM14Qu24187j6hZ5OedsJZ
> QVoP00tdW+xRZfnroW15f9Rzb5MPWQp/RW84rESGVBt1f7mCwzwR1aLRa7ivBPWf
> +idL5WdJIMAYrCTAaI7zksPFfYrgK9tSgmULVqrkOkpYI3K24/N8JZyRmRJc6GEU
> O6+8pprFykzoRE2pvSL0J1Vg24a4paYyuaKTT1wHBqkHg87Sm42amueTQUkXP8p7
> d1hQ0JHyfMma53Qv2taA0l1K9WR9ifB+HH5dc0w5d7KUvc5Bs0fr5ed/5vim75fX
> HyJn5P/wugaaw0+vBwU381WkCYuq/tB/HLPDirsDjK0iX9hkh6/McDZ7uD0mWmCH
> NZnHKjifEkF57P5wNLVFaz90q6YfrGnyS8jJKNEopcurZOtpd0wHKnW7eh/0iO6H
> EEeYkJ5M309AvFFWLE1UDHfCuPgTll/l3WB+SzUTGeF9wq7JP6RlsT02at7kXCHt
> mAxfycSJ6b3B35XxBdqVmUKo9jB/XwjgGOT/RJGU/w9PxXcgmI7yR8oOXPtopH7v
> HKR/dwSHlMfox+tAzAf2SFE7KIwr3JtEjcrLDP0+fDrW3QnK0zhdC5R7jXI//cwM
> bFQ7jKlS8wI1ZEOYZw2oBWm72nkFO0uIt8A+60mxdq4/zY++FPg=
> =Xrgv
> -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/CAOtZr%3DEsdYq5G3F%2B1D_MVXB1-pzUuV8XbBZboJw7ToWnkJHucA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] HVM resolution not working by changing xorg.conf

[snowboard789]

On Thursday, February 22, 2018 at 4:26:57 PM UTC+1, Unman wrote:
> On Wed, Feb 21, 2018 at 05:56:54PM -0800, snowboard...@gmail.com wrote:
> > I installed an HVM of Linux Mint 18 on a laptop. I followed everything that 
> > is in the HVM tips and changed the driver to vesa, the horiz sync to 30-60 
> > the vert refresh to 40-80 (and tried without it). I tried hardcoding 
> > resolutions and not hardcoding them. 
> > 
> > I get a sync problem as long as I log in (the login screen is huge but ok). 
> > Then it's all totally fuzzy.
> > 
> > What else can I try? Thanks
> > 
> 
> here's an alternate approach:
> 
> sudo apt-get install xvfb xfonts-100dpi xfonts-75dpi xfstt
> 
> Edit /etc/default/grub, and set:
> GRUB_GFXMODE=1600x1200,1280x1024,800x600
> GRUB_PAYLOAD_LINUX=keep
> 
> sudo update-grub
> 
> Restart the HVM.
> Obviously, use resolutions that work for you. (You may find that only
> the FIRST in that list is active and available.)

this solved it. thanks a ton! 

-- 
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/748e0de0-bd8a-4aca-b647-786e2ab719ac%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] How to add "nouveau.modeset=0" to boot settings in Qubes 4.x? (ASUS ROG GL552VW-DM141 laptop)

[@LeeteqXV (Twitter & Mastodon.technology)]

Hi all. I initially thought to save some time and cleared a reply to an 
existing thread to do a new post, but that did not work. Sorry about the 
wrong post. Reposting it here now. Thanks for the reply and pointing it 
out, Yuraeitha.


See my reply + follow-up question at the bottom, below the quoted posts:

##

My original post, incl. a reply by "Yuraeitha" below..:



"I am considering Qubes 4.x for an ASUS ROG GL552VW-DM141 laptop with 
NVIDIA graphics and built-in/onboard "fallback" Intel graphics.


In order to get for example Ubuntu Mate installed onto it, to get past 
the installer incompatibilities with NVidia, it is necessary to edit the 
boot menu and add "nouveau.modeset=0" to the startup command. Then 
Ubuntu boots fine.


Can this be done with Qubes 4.x?
How/where to affect such boot commands; can that be done from the boot 
media/USB stick directly, as we do with other Linux live USB sticks?


Thanks, "

--
https://mastodon.technology/@LeeteqXV/

###

Reply from "Yuraeitha" on Feb. 19th..:

- show quoted text -

"@LeeteqXV
It's probably best you start a new thread, this thread is about a whole 
different issue altogether.


But since this is an old thread, I'll briefly answer you.
This what you seek, directing a GPU directly into an AppVM, or any other 
work arounds, can currently be done in Qubes 3.2. nor Qubes 4.0.


However, it is planned for Qubes 4.1, which may reach release. Just 
don't get hyped yet, things can change, 4.0. is barely finished and 4.1. 
is currently only on the drawing board. Look here for quick information 
about 4.1. https://github.com/rootkovska/qubes-roadmap 
 you can see the GTX 
passthrough ability on the map.


Also, you don't really need Ubuntu for these kind of things, it can 
easily be fixed up in both Debian and Fedora. You can use Intel graphics 
just fine for 4k videos, you don't need nvidia for stuff like that on 
modern motherboard/CPU systems. You may need powerful graphic cards for 
gaming and high end graphics, but this too isn't possible, at least 
before Qubes 4.1. anyway. If you didn't need these in Qubes 4, then it 
will likely make no difference to you to use Intel graphics. Also Qubes 
dom0 frequently has nvidia graphic issues and may require a full 
properitary driver download/install, with a manual install.


To get a bit back on-topic, it saves you whole lot of hassle if you get 
adjusted to not be depending too much on Ubuntu and others that give 
everything on a silverplate. Although DVM protected content is never 
stable regardless of the Linux distribution, unless you download the 
Google Chrome browser from Google (Not Chromium), which usually always 
have working DVM videos in any Linux. Issue being, that Firefox and 
others, often loose the ability to play the video, especially Microsoft 
silverlight videos, which the work-arounds frequently break.


Essentially you can play the codecs fine, HTML5 is for example extremely 
easy to install in Fedora through enabling the RPMFusion repositories, 
which can easily be done in Qubes fedora template (best make a copy 
first). But it does not include HTML5-DVM.


Essentially, DVM is so messed up, you ma/y just want to download the 
Google Browser specifically for these videos, and just be done with the 
crapware copyright protectors throw at us. It's not like they care about 
Linux anyway, so why would changing to Ubuntu make any difference? 
Ubuntu is just as unstable in this regard of protected content due to 
lack of developer support of protected contents.


However, Fedora+Firefox+RPMFusionRepositories+ffmpeg+Firefox's own DVM = 
Netflix and all HTML5 videos on youtube, and similar modern websites, 
works smoothly without issues.


Try not to get too dependent on a system, really it makes little 
difference if you adjust yourself to it.


Also install Qubes with LegacyBIOS/Grub and press the E key during the 
Grub menu, then add after or before "quiet" on the module code-line. Or 
just temporarily disable nvidia in your UEFI, works too, more or less 
does the same as nouveau.modeset=0."'


###

The final part of Yuraeitha's answer is relevant for my case as it is 
about installing Qubes itself, not inside a VM..:


Also install Qubes with LegacyBIOS/Grub and press the E key during the 
Grub menu, then add after or before "quiet" on the module code-line. Or 
just temporarily disable nvidia in your UEFI, works too, more or less 
does the same as nouveau.modeset=0."


So; 1. That (ASUS ROG GL552VW-DM141 laptop) AMI BIOS does not have any 
function to disable NVIDIA for UEFI (or anything about disabling 
graphics at all), as far as I can see.


2. I add the modeset to the startup, then get to the actual startup GUI 
first page, but then cannot proceed. I manage to restart the installer 
in TEXT mode, which actually lets me install 

Re: [qubes-users] Problem installing Qubes on Lenovo Thinkpad T450s

[velcro]

I am trying to load 3.2 onto a T450s, I'd like to keep Legacy mode as it allows 
me to have AEM.

I was able to install using the same thumb(created using dd) on another 
computer, no problems, however I keep going back to "Test and install 3.2" when 
trying to load Qubes onto a T450s.

I saw some users having similar challenges...any suggestions? Kind of a bummer 
thought I was getting a popular "all green" choice from the HCL list.

Any help would be greatly appreciated

V

(I corrected an omission in this post: "I was able to install using the same 
thumb(created using dd) ON ANOTHER COMPUTER"

-- 
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/23fc9d9c-070e-49f6-a3bd-1c1026bb8a87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Problem installing Qubes on Lenovo Thinkpad T450s

[velcro]

I am trying to load 3.2 onto a T450s, I'd like to keep Legacy mode as it allows 
me to have AEM.

I was able to install using the same thumb(created using dd), no problems, 
however I keep going back to "Test and install 3.2" when trying to load Qubes 
onto a T450s.

I saw some users having similar challenges...any suggestions? Kind of a bummer 
thought I was getting a popular "all green" choice from the HCL list.

Any help would be greatly appreciated

V

-- 
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/89ebdc33-9f24-407e-b12a-9a53fee01f2b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Can't install Qubes, Rebooting after loading initrd.img

[Daniil .Travnikov]

When I updated last time my BIOS Firmware, it was been from here:
https://downloadcenter.intel.com/download/23908/Intel-Server-Board-S5520HC-S5500HCV-S5520HCT-and-Intel-Workstation-Board-S5520SC-Firmware-Update-Package-for-EFI?product=36599

"S5520HC S5500HCV S5520HCT S5520SC BIOS Recovery Package for EFI"


Maybe this is the problem, that my bios in some reason could working always 
with EFI mode even if I change it on 'Disable' in bios menu?

-- 
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/c0fef8c5-a3a5-475a-8b33-85f43800b400%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

AW: Re: AW: [qubes-users] Re: i3 under Qubes 4 RC3

['[799]' via qubes-users]

Hello Florian

 Original-Nachricht 
An 22. Feb. 2018, 09:07, Florian Brandes schrieb:

> I use i3 under Q4rc4 without any issues
> or problems.

Would you mind sharing your i3-config files?

[799]

-- 
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/fgkaOM_dacYgqN8iMgQsa6_mqpTqLxTIcYvSbqN89sMmyzxQSxIho-uT7OQHMH__wSBn4YMcx_Mfc8XWwQa2nQchu2nCMgpzzdE8XAcZa6s%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Firewall rules for Thunderbird and Gmail

[taii...@gmx.com]

I find it ironic you use qubes and egress IP filtering but you are still 
using google services rather than simply paying $5-10/mo for real email 
that doesn't spy on you.


--
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/4748223f-8ac1-a321-2557-9b7742527f8d%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['awokd' via qubes-users]

On Thu, February 22, 2018 6:19 pm, 'Aaron Dough' via qubes-users wrote:

> Sorry for the avalanche of messages, I just had sys-net freeze on me even
> though the Ethernet controller was detached. As it turns out, the
> Wireless controller needs no-strict-reset=true too. Now it seems much
> more stable.

No problem, it's also helpful for others who might encounter the same
problem as you some day and search this mailing list.

> However, still
> - 3:00.0 can not be attached, or sys-net won't start
> - whenever Ethernet (3:00.1) is attached, no matter the strict-reset flag,
> standby will mess with sys-net: The network-icon will show the "trying to
> connect"-animation, and it thinks it's connected to "Wired connection 1",
> although there is no cable attached. That's the bug I couldn't quite
> remember before, and it is now reproducable.

That might be something else. Check out this article and try looking for
your Ethernet driver instead of the wireless one.
https://www.qubes-os.org/doc/wireless-troubleshooting/

> I also wrote Tuxedo-computers, maybe they will be able to help.

Please let us know what you hear back! Unfortunately, they might not be
able to do anything about it if it's inside the Realtek hardware. At least
if they are aware it's causing people problems, maybe they'll look for a
better chip next time.

> Big thanks to awokd for all the helpful replies :-)

Any time.


-- 
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/2c922b9eb11e7b702777fb82d8749e21.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

On February 22, 2018 5:01 PM, Aaron Dough  wrote:

>On February 22, 2018 1:57 PM, 'awokd' via qubes-users 
>qubes-users@googlegroups.com wrote:
>
>>On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:
>>>Good to know. Since Tuxedo especially advertises it's native
>>> Linux-support, I think I'll ask their support directly regarding this
>>> issue. It may be far fetched, but if this is really solvable with updated
>>> firmware, it's worth a shot :-)
>>>His case was a little different because he wanted to use them across
>> separate VMs. In theory that can be done if you set both devices to not
>> require strict reset. In your case, maybe try to assign them both to
>> sys-net without strict reset (but you might have already tried that too).
>>
> Yes, I've tried that too. Although I noticed that the Qubes Manager currently 
> doesn't seem to set no-strict-reset property properly, so I tried again via 
> command line.
> As soon as both devices (3:00.1 and 3:00.0) are attached, sys-net will not 
> start, no matter the no-strict-reset flag(s).
> If only .1 (Ethernet) is attached, it will result in unstable behavior. With 
> no-strict-reset=true sys-net will freeze after a standby (no reaction when I 
> click the networking-icon, no qvm-shutdown possible, only qvm-kill).
>

Sorry for the avalanche of messages, I just had sys-net freeze on me even 
though the Ethernet controller was detached. As it turns out, the Wireless 
controller needs no-strict-reset=true too. Now it seems much more stable.

However, still
- 3:00.0 can not be attached, or sys-net won't start
- whenever Ethernet (3:00.1) is attached, no matter the strict-reset flag, 
standby will mess with sys-net: The network-icon will show the "trying to 
connect"-animation, and it thinks it's connected to "Wired connection 1", 
although there is no cable attached. That's the bug I couldn't quite remember 
before, and it is now reproducable.

I also wrote Tuxedo-computers, maybe they will be able to help.

Big thanks to awokd for all the helpful replies :-)

Kind regards,
Aaron

-- 
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/imNpaQvCnVnjD6igDetitlT_5m-C-Dmlm8i6gYBAN6C5Hk50u7zgSv2HkvuZkG5WuTpXQ5G5E0a8Bpgacapk8bEt90zpSHRp2a3Dj5noLUc%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Building Centos template conflict error?

[fepitre]

Le jeudi 22 février 2018 02:28:23 UTC+1, Tim W a écrit :
> AWESOME!!!
> Thanks for taking the time post the update.  I will build as soon as I get 
> home and report back.

You's welcome. No problem, the time Marek do the necessary, you can cherry pick 
the commit.

> 
> Should it build ok as part of the qubes os iso as well?

You mean you want to build it and generate an ISO with CentOS? Sure you can.

-- 
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/4eb6006c-f809-4bd5-8f49-005138368969%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

 On February 22, 2018 1:57 PM, 'awokd' via qubes-users 
 wrote:

>On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:
>
>>Good to know. Since Tuxedo especially advertises it's native
>> Linux-support, I think I'll ask their support directly regarding this
>> issue. It may be far fetched, but if this is really solvable with updated
>> firmware, it's worth a shot :-)
>>
>
> His case was a little different because he wanted to use them across
> separate VMs. In theory that can be done if you set both devices to not
> require strict reset. In your case, maybe try to assign them both to
> sys-net without strict reset (but you might have already tried that too).
>

Yes, I've tried that too. Although I noticed that the Qubes Manager currently 
doesn't seem to set no-strict-reset property properly, so I tried again via 
command line.
As soon as both devices (3:00.1 and 3:00.0) are attached, sys-net will not 
start, no matter the no-strict-reset flag(s).
If only .1 (Ethernet) is attached, it will result in unstable behavior. With 
no-strict-reset=true sys-net will freeze after a standby (no reaction when I 
click the networking-icon, no qvm-shutdown possible, only qvm-kill).

-- 
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/JJqOfvco5VlYyzgmAcLUxXo3TGhv_O2p3dKsLKGSgzt6vF2UmoGNRyYTj7qNd7bYe7iEzqOWI6ESs5FwoNw1bJrVZtQox2oa5s4I20CdF9Y%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] HVM resolution not working by changing xorg.conf

[Unman]

On Wed, Feb 21, 2018 at 05:56:54PM -0800, snowboard...@gmail.com wrote:
> I installed an HVM of Linux Mint 18 on a laptop. I followed everything that 
> is in the HVM tips and changed the driver to vesa, the horiz sync to 30-60 
> the vert refresh to 40-80 (and tried without it). I tried hardcoding 
> resolutions and not hardcoding them. 
> 
> I get a sync problem as long as I log in (the login screen is huge but ok). 
> Then it's all totally fuzzy.
> 
> What else can I try? Thanks
> 

here's an alternate approach:

sudo apt-get install xvfb xfonts-100dpi xfonts-75dpi xfstt

Edit /etc/default/grub, and set:
GRUB_GFXMODE=1600x1200,1280x1024,800x600
GRUB_PAYLOAD_LINUX=keep

sudo update-grub

Restart the HVM.
Obviously, use resolutions that work for you. (You may find that only
the FIRST in that list is active and available.)

-- 
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/20180222152655.yicoikgpeatf7v7p%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['awokd' via qubes-users]

On Thu, February 22, 2018 1:49 pm, Aaron Dough wrote:

> Good to know. Since Tuxedo especially advertises it's native
> Linux-support, I think I'll ask their support directly regarding this
> issue. It may be far fetched, but if this is really solvable with updated
> firmware, it's worth a shot :-)

His case was a little different because he wanted to use them across
separate VMs. In theory that can be done if you set both devices to not
require strict reset. In your case, maybe try to assign them both to
sys-net without strict reset (but you might have already tried that too).

-- 
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/c4ce51d5bd790438455fb2f4853a53e0.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Install to Dell T3610, no Intel graphics, VNC install, NVS 310

[CMaurice]

Forgot to mention: Qubes Release 4.0-rc4

-- 
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/5a4da685-1492-46c3-8543-3729a65226f0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

 Original Message 
 On February 22, 2018 1:28 PM, 'awokd' via qubes-users 
 wrote:

>On Thu, February 22, 2018 1:18 pm, 'Aaron Dough' via qubes-users wrote:
>>On February 22, 2018 1:06 PM, 'awokd' via qubes-users
>>qubes-users@googlegroups.com wrote:
>>
>>
>>>I'm wondering if sys-net and suspending will be more stable if you
>>> attach everything on bus 3 to sys-net while leaving strict_reset to
>>> default to required.
>>>
>>
> Have you tried this already?

Yes, when I do this sys-net won't even start up ("Cannot execute 
qrexec-daemon!")

>
>>lspci only gives me 03:00.0 and .1, with 03:00.0 being "Unassigned class
>> [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader
>> (rev 01)"
>>
>
> Someone else recently had a similar problem with those Realteks too
> (https://mail-archive.com/qubes-users@googlegroups.com/msg18953.html). I
> don't know what they were thinking when they designed that setup or why
> any manufacturers would use it...

Good to know. Since Tuxedo especially advertises it's native Linux-support, I 
think I'll ask their support directly regarding this issue. It may be far 
fetched, but if this is really solvable with updated firmware, it's worth a 
shot :-)

-- 
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/SP-uwJKRmI6yCTfeY8eqVypF5P4j79FCSPS89NcQed-HgletXZkokvuE55pk_rZcJRjl4jdDyHoA5d9FqNBbwuDjlxeQ2s2zN553W90ndGY%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['awokd' via qubes-users]

On Thu, February 22, 2018 1:18 pm, 'Aaron Dough' via qubes-users wrote:
> On February 22, 2018 1:06 PM, 'awokd' via qubes-users
>  wrote:

>> I'm wondering if sys-net and suspending will be more stable if you
>> attach everything on bus 3 to sys-net while leaving strict_reset to
>> default to required.

Have you tried this already?

> lspci only gives me 03:00.0 and .1, with 03:00.0 being "Unassigned class
> [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader
> (rev 01)"

Someone else recently had a similar problem with those Realteks too
(https://mail-archive.com/qubes-users@googlegroups.com/msg18953.html). I
don't know what they were thinking when they designed that setup or why
any manufacturers would use it...




-- 
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/4ab85a63af9f8b0569f63184b0ee83de.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

On February 22, 2018 1:06 PM, 'awokd' via qubes-users 
 wrote:

>On Thu, February 22, 2018 12:52 pm, 'Aaron Dough' via qubes-users wrote:
>
>>Attaching 3:00.0 to sys-net also did not help, instead sys-net would not
>> start up any more ("Cannot execute qrexec-daemon").
>>So I'm back to disabling ethernet altogether by not attaching 3:00.1 to
>> sys-net. This is not a problem at the moment.
>>
>
> What device is 03:00.0? If you do an lspci, is there anything else on bus
> 3 besides 03:00.1?
>
> I'm wondering if sys-net and suspending will be more stable if you attach
> everything on bus 3 to sys-net while leaving strict_reset to default to
> required.
>
>
>
>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/b2d14fc757f2f50ed643212a2053c8fd.squirrel%40tt3j2x4k5ycaa5zt.onion.
> For more options, visit https://groups.google.com/d/optout.
>

lspci only gives me 03:00.0 and .1, with 03:00.0 being "Unassigned class 
[ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI Express Card Reader (rev 
01)"

-- 
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/X8KnEw9dqniXnVDKyGRd9Lr8BekeZTyFX9bgqqvmDMEjuPtk5qcoa6eKpH6G-EKr6LdGeDu8SSXaXcUgALbOZXZ6V4gNAB8Lv10nioreAQk%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - Tuxedo BU1406

['Aaron Dough' via qubes-users]

Most things seem to work fine, but Ethernet is still problematic at this moment 
with Qubes 4.0 RC4, but I'll refrain from posting this here until 4.0 becomes 
stable and I've had more time for testing. (If you are interested have a look 
at my other post "Qubes 4.0 on Tuxedo BU1406". In essence, for now I don't have 
the Ethernet-controller attached.)

-- 
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/TDUlxgFk-ERDO_UfoOwCOkyCIZd2rcECYm_kt5zTz3URvWcyVT9gTVi0mqiY1L1vwwz0q-OMAhtvzrUxfLRipHZZiArzNckX6F3M_aWEH0I%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.


Qubes-HCL-TUXEDO-N24_25BU-20180222-095713.yml
Description: application/yaml

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['awokd' via qubes-users]

On Thu, February 22, 2018 12:52 pm, 'Aaron Dough' via qubes-users wrote:

> Attaching 3:00.0 to sys-net also did not help, instead sys-net would not
> start up any more ("Cannot execute qrexec-daemon").
>
> So I'm back to disabling ethernet altogether by not attaching 3:00.1 to
> sys-net. This is not a problem at the moment.

What device is 03:00.0? If you do an lspci, is there anything else on bus
3 besides 03:00.1?

I'm wondering if sys-net and suspending will be more stable if you attach
everything on bus 3 to sys-net while leaving strict_reset to default to
required.


-- 
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/b2d14fc757f2f50ed643212a2053c8fd.squirrel%40tt3j2x4k5ycaa5zt.onion.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

On February 22, 2018 12:52 PM, Aaron Dough  wrote:

>Hello again, my long overdue update on the matter, now with RC4:
>
>1. Installing Qubes 4.0 RC4 in UEFI-Mode works fine now :)
>
>2. No manual adjustment of GRUB needed any more :)
>
>3. Standby seems to work almost perfectly now. It does need about a minute to 
>kick in, and if I unlock my screen in this time frame I'm able to resume from 
>standby without any lockscreen, but I can live with that :)
>
>4. qubesd service doesn't crash anymore :)
>
> New issue:
>
> During installation, before the first reboot and basic configuration, the 
> system stops with
> [terminated]
> [ 1513.579240] reboot: Restarting system
> and doesn't react any more. Cold shutdown and reboot resumes the 
> installation-process.
>
> Remaining issues:
>
> Sys-net still causes trouble. The error-message ("Unable to reset PCI device 
> 000:03:00.1") still occurs during installation, and later keeps sys-net from 
> starting. Setting pci_strictreset to false mitigates the problem, but doesn't 
> make sys-net stable. Particularly the behavior after standby is kind of 
> strange, for example it tells me a connection is gone several times, although 
> there never was a connection. Also it will not halt properly with 
> qvm-shutdown, a qvm-kill is needed. One time a new wired connection appeared 
> under a new wired controller, but I've not seen it since.
>
> Attaching 3:00.0 to sys-net also did not help, instead sys-net would not 
> start up any more ("Cannot execute qrexec-daemon").
>
> So I'm back to disabling ethernet altogether by not attaching 3:00.1 to 
> sys-net. This is not a problem at the moment.
>
> I'll upload the HCL-report in a new post and will try to use RC4 over the 
> next weeks.
>
> Best regards,
>
> Aaron
>
>


Oh, I almost forgot: I was supposed to attach 3:00.0 and 3:00.1 to sys-usb, and 
I did that by doing a complete reinstall using the corresponding options. The 
results were still the same. Unless of course I made some mistake in the 
process. Is it correct that by doing so I'll end up with only one sys-net qube 
which is also my usb-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/-sv5bMwemcSOisXDi61ve3mL8Zlf6WEtOY2wT4Er2GyUkrHGGaXg__4wWr3VSta8StQuHT77pfOwJW89wks7-Po5ctS6_lz2OwNQkDymtgI%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 4.0 on Tuxedo BU1406

['Aaron Dough' via qubes-users]

Hello again, my long overdue update on the matter, now with RC4:

1. Installing Qubes 4.0 RC4 in UEFI-Mode works fine now :)
2. No manual adjustment of GRUB needed any more :)
3. Standby seems to work almost perfectly now. It does need about a minute to 
kick in, and if I unlock my screen in this time frame I'm able to resume from 
standby without any lockscreen, but I can live with that :)
4. qubesd service doesn't crash anymore :)

New issue:

During installation, before the first reboot and basic configuration, the 
system stops with
[terminated]
[ 1513.579240] reboot: Restarting system
and doesn't react any more. Cold shutdown and reboot resumes the 
installation-process.

Remaining issues:

Sys-net still causes trouble. The error-message ("Unable to reset PCI device 
000:03:00.1") still occurs during installation, and later keeps sys-net from 
starting. Setting pci_strictreset to false mitigates the problem, but doesn't 
make sys-net stable. Particularly the behavior after standby is kind of 
strange, for example it tells me a connection is gone several times, although 
there never was a connection. Also it will not halt properly with qvm-shutdown, 
a qvm-kill is needed. One time a new wired connection appeared under a new 
wired controller, but I've not seen it since.

Attaching 3:00.0 to sys-net also did not help, instead sys-net would not start 
up any more ("Cannot execute qrexec-daemon").

So I'm back to disabling ethernet altogether by not attaching 3:00.1 to 
sys-net. This is not a problem at the moment.

I'll upload the HCL-report in a new post and will try to use RC4 over the next 
weeks.

Best regards,

Aaron

-- 
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/BK7OVOw-K-_UOn4c7pmVSG1qRaX6kRa7owOe8o8XYMxEbg9J6BN07jGBbv1zAqDh3Fkv8okztzeZROOFYtuVJ2jwMug3Y8-WFVPOFKg0uXk%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Qubes 3.2: Network doesn't connect automatically with hidden wifi

['Max Andersen' via qubes-users]

On 02/22/2018 08:09 AM, Yuraeitha wrote:
> On Thursday, February 22, 2018 at 3:20:32 AM UTC+1, Max Andersen wrote:
>> Sendt fra min iPhone
>>
>>> Den 21. feb. 2018 kl. 21.23 skrev Yuraeitha :
>>>
 On Wednesday, February 21, 2018 at 8:13:44 PM UTC+1, Max Andersen wrote:
 Hi,

 I've noticed that after disabling SSID broadcast on my wifi, I need to
 disable and reenable my network, every time I login.

 I've tried to describe it in detail here: https://militant.dk/?p=174

 Maybe anyone has ideas to resolve this?

 Sincerely

 Max
>>> Think of it this way. Hackers love challenges. By the act of trying to hide 
>>> that way, you're giving a hacker a challenge. He or she, may even get a 
>>> kick out of showing you how insecure your network really is by messing with 
>>> you, simply because you do something that has no effect, such as hiding the 
>>> SSID. 
>>>
>>> You're either giving them a challenge to work on, or it might even be 
>>> schadenfreude https://en.wikipedia.org/wiki/Schadenfreude
>>>
>>> Tbh, you're better off just enabling SSID again.
>> So, the solution is actually security by nudging?
>>
>> Don’t do it, or we will make qubes network manager crash to nudge you back :)
>>
>> I’d bet my network is not that interesting for a wardriving kali hacker, but 
>> it still seem like a bug that I would love to get fixed.
>>
>> Sincerely
>> Max
> hehe, well you can probably find a hack to get what you need, for example 
> making a script that automatically repairs your connection at boot. I'm not 
> seeing the particular details atm, but it seems like it might just work. I'm 
> no expert though.
>
> The bug itself is likely not related to Qubes btw. It's very likely that it 
> belongs upstream in Fedora, and even in Fedora the Network Manager may come 
> from up further upstream. Even if you track down the Network Manager 
> developers, the piece of code they're using may come even further upstream, 
> and even there, it may yet again come from another upstream. This is usually 
> called upstream/downstream movements. Linux is like lego, many pieces comes 
> elsewhere, and no one have the resources to do everything. If they tried, 
> they'd drawn in work to do. And if they change upstream code, then it becomes 
> really, really messy when new updates arrive from upstream, and you need to 
> incorporate the code changes you made to all your packages every time a new 
> update arrives. To make matters worse, it's not their code, so it can be hard 
> to find your way around and find the right places in the code, wasting a lot 
> of time. And then there is the aspect that security can be tough to enforce 
> if you spread out too far. You have to trust other developers to some extent, 
> otherwise you'd spend all your time looking for security flaws and never get 
> anything else done.
>
> The closer to you get to the source upstream, the higher your odds are that a 
> developer will track it down and report the issue. Qubes is pretty far away 
> from the source, and operates on a more broad level of coding 
> (macro-perspective, piecing a lot of different codes and mechanism together). 
> You can kind of look at Qubes as an infrastructure, and not an organ like 
> operation systems are. Qubes in and on itself is not an operation system, 
> it's a network or "mesh" of operation systems. So this issue has to be 
> tracked down.
>
> It's also an issue if developers have to spend time reporting all the bugs to 
> each others, they'd spend a huge amount of time on that. A single bug may not 
> seem like wasting a lot of time, but it piles up. Say one spends 20 dollars, 
> it's pennies, not a lot of money (well at least in some countries). Now 
> imagine if you had to pay for 1.000 pieces, then it becomes 20.000 dollars, 
> and it suddenly became very expensive. 
>
> That's why developers have to prioritize their time and focus, because if 
> they do not, they'd drawn in everything else. Qubes top priority is security. 
> I doubt they will be looking into this bug.
>
> But the community can help, by reporting the bug closer to the source, or at 
> the actual source. This way the bug can get fixed, and it may go faster too 
> (not always though) if the actual developers behind it are reported about it 
> directly. If the community does this, it'll save all developers a huge amount 
> of time. So this kind of bug, may be a matter of tracking down the actual 
> Network Manager developers. 
>
> But if you'd like a fix though, a sort of "hack", then as mentioned earlier, 
> a script may work out. But before trying to look into it, I'll ask if this is 
> something you need? or do you prefer to wait for a real bug fix? (It can take 
> a long time for what may be deemed minor bugs, and also requires someone 
> reporting it at the appropriate issue-tracker).
>
> I may not be able to make such a script though, I'm only an average Linux 
> user. But I'll 

Re: AW: [qubes-users] Re: i3 under Qubes 4 RC3

[Florian Brandes]

On 22.02.2018 03:38, '[799]' via qubes-users wrote:

Hello,


 Original-Nachricht 
An 26. Jan. 2018, 10:18, aaq via qubes-users schrieb:

 > My dmenu is broken, for starters. Dmenu only
 > shows dom0 applications, so I cannot start
 > anything that way.
 > When I run qvm-run to start something, I can
 > see that my VM is started (with qvm-ls) and I
 > can hear my CPU responding (as in it starts
 > fanning), but nothing visually happens.
 > Nothing is ever started.

Same problem for me, but I haven't found a solution. Using Qubes 4rc4 but i3 is 
not working like it has under Qubes 3.2.

Anyone else using i3 under Q4rc4?


Hi,

yes I use i3 under Q4rc4 without any issues or problems.
(Only thing I added/changed is case insensitivity for dmenu with -i option and 
changed the qube count command and the free disk space command in i3status)
Besides that, it worked out of the box for me (following the provided 
instructions concerning i3 on qubes).
I use Qubes4rc4 on two maschines, both work without a flaw concerning i3.

Regards,
Florian

--
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/b7d6fad2-87f8-5686-deec-cfd2bfe8ecb3%40gmx.de.
For more options, visit https://groups.google.com/d/optout.