Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread yuraeitha
A worry I've been thinking about regarding the backup feature missing, is that 
it seems like it's intended to be used through the AdminVM over a network. In 
other words, this seems more like a move towards business users, rather than 
the regular every day user that might prefer an external USB drive through a 
GUI window. 

Qubes is moving towards business users, we already know that much. But are the 
regular users getting ignored now as a result? or are both still being seen as 
primary users? 

It's clear that Qubes 4 took a lot of hard work, so perhaps there just wasn't 
enough time to work on everyday touch and feels, like proper GUI and user 
experience.

But the deep worry that Qubes might or might not be giving up on normal users, 
is definitely there for me. I have high hopes for Qubes to change the PC/Mobile 
environment of the future, forcing the hand on any other OS out there. There 
should be no issues to support both users and businesses. 

It's not that I believe this, but the elephant is still in the room. Are users 
getting ignored now? or was it just because Qubes 4 had so much work that there 
was little time left for anything else?

If the latter is indeed the case, what is the next everyday user experience 
development in planning? Gnome 3? Return of GUI tools such as backup? Graphics 
in VM's for high end graphics? Gaming even? I mean, I do believe if these 
mentioned issues were fixed, Qubes could draw in quite a lot of new users. 
Heck many gamers care about privacy and security too, there is a large 
user-base there if you manage to make gaming through virtualization work 
smoothly. 
Think about it, how highly connected gamers are through gaming news etc., if 
gaming worked in Qubes, it'd in my opinion draw a lot of positive attention, 
and a likely substantial Qubes userbase growth. Getting graphics to work in 
Qubes is being seen as a low priority, for the life of me, I cannot see why 
this is the case, with so many potential new Qubes users laying in wait.

-- 
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/9129ef8d-e958-4f80-918d-59c5b5384c9e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Franz
On Thu, Aug 3, 2017 at 12:18 PM, Unman  wrote:

> On Thu, Aug 03, 2017 at 12:43:31AM -0300, Franz wrote:
> > On Wed, Aug 2, 2017 at 9:47 PM, Eva Star 
> wrote:
> >
> > > -BEGIN PGP SIGNED MESSAGE-
> > > Hash: SHA256
> > >
> > > On 08/02/2017 03:04 AM, cooloutac wrote:
> > >
> > > > oh ok I see,  so a taskbar widget or something to replace the
> > > > manager.  I thought they lost their minds for a second. My
> > > > immediate thought was what about attaching drives, and seeing if
> > > > updates available?  Joanna addressed all my concerns but I'm gonna
> > > > have to wait and see what happens with this.   Hopefully it doesn't
> > > > turn out to be more confusing then the manager.
> > >
> > > It is a miscalculation. How about the words "we must make Qubes user
> > > friendly for all users non IT advanced" and release Qubes without
> > > manager? :(
> > >
> > > Maybe, widgets is not a good idea, but Qubes Manager is one of the
> > > important part that make Qubes useful to manage all vms with mouse.
> > > Some UX to old one QM + start menu links to right mouse action and it
> > > will be amazing.
> > >
> > >
> > Well, I never use the start menu on the left lower side of the screen
> > because it is too complicated, too many items and needs customization
> that
> > I am too lazy to do or have better things to do. I do everything with the
> > Qubes Manager that is so well organized and compact. I am afraid that the
> > new arrangement may make things more difficult to find for a new user
> since
> > items are spread over different buttons/places.
> >
> > I would suggest to mitigate this risk putting links to the other places
> on
> > the widget/window that opens when you click on one of them. You can
> > separate things, but better put links to find them again.
> >
> > Also I imagine that somewhere I'll find the list of VMs. There please
> > 1. keep the "run command in VM" choice and
> > 2. add something new: the chance to show only preferred VM
> >
> > The first is very important to avoid using the start button.
> > The second is important to simplify the view and speed up the most common
> > routines
> >
> > Cooloutac made me smile telling of his mother and family using Qubes.  I
> > had my wife using Qubes for some years, but recently she rised up against
> > Qubes telling that it is too complicated for her to be able to master it
> > without help. She wanted a Mac.  Really it is impossible to maintain
> Qubes
> > without the CLI and this makes it beyond limits for most people.  But
> > perhaps if we are able to find a stable architecture and then Qubes
> matures
> > enough, this may change. But we are not there yet.
> > Best
> > Fran
> >
>
> I completely disagree with you, and I'm with cooloutac on this.
> I have a number of Qubes users who are fine, and NEVER touch the command
> line. (Most of them would go to pieces at the prospect.)


Sorry, but I do not believe that. How can your users perform the following
basic required actions without a CLI:
 1. verify iso
2. put the iso on a usb stick
3. print (you need a custom DVM)
4. scan
5. update templates after EOL
6. update dom0 and templates when the same Manager command does not work
for some reason. How many times it happened?
7. solve various issues when something simply does not work as expected,
such as the last one with the wrong kernel when you Unman kindly helped me
to solve it with the terminal because it did not work with the Manager

Most of them
> rarely touch the Manager.
>
>
How can they update templates and dom0 without touching the Manager?

You users may be able to use Qubes only because you kindly help them with
the above and other issues. Nothing wrong with that of course, you are a
very nice person, but they are not autonomous. If they have to travel a
couple of months and something wrong happens, as with my wife that had wifi
dead, then they are unable to solve it. Worse,  NOBODY is able to help
because when they see Qubes they declare inability.  In that case I was
lucky to be able on the phone to tell her to connect with ethernet and
upgrade Fedora 24 to Fedora 25 and it fixed it. But it was just luck that
it worked and that she was able to correctly do what I told her. What was
broken? No idea.

Without you, coouloutac  or even me, always ready to help, how can a normal
person use Qubes without using the CLI. No way. Now Qubes is still a
project for geeks. Too many issues. And it is obvious that this state
cannot improve until we are obliged to continuously change architecture
such as the last one release 4 for the Xen issues. But hopefully this is
the last change we need to do and can concentrate on maturing Qubes into a
more mainstream product.
Best
Fran


I suspect your wife suffered from your (self confessed ) laziness -
> If you spend some time customizing the menu, creating shortcuts, and
> hiding the infrastructure as much as possible, then in my experience,
> 

[qubes-users] Re: [qubes-devel] Re: Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2

2017-08-04 Thread Michael Carbone
Lorenzo Lamas:
> Because Fedora 25 has a newer version of NetworkManager, can the same
> method for MAC randomization for Debian now be used for Fedora
> instead of using macchanger as described here? 
> https://www.qubes-os.org/doc/anonymizing-your-mac-address/

yes that is correct. I have just submitted a pull request to update that
doc to reflect that fact:

https://github.com/QubesOS/qubes-doc/pull/452

-- 
Michael Carbone

Qubes OS | https://www.qubes-os.org
@QubesOS 

PGP fingerprint: D3D8 BEBF ECE8 91AC 46A7 30DE 63FC 4D26 84A7 33B4


-- 
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/3df78c01-0afa-6136-b464-76edda48cf66%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] F25 VM Manager Update green arrow persisting

2017-08-04 Thread yreb-qusw
Anyone else having this issue ?   Suggested fix  or just ignore,  I 
haven't actually rebooted the machine  but have closed all VMs and 
reopened only the F25 to 'update'  but 'there is nothing to do' and yet 
it persists..


--
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/1027701f-02f7-b51b-a2c8-55833a435272%40riseup.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Announcement: Recommended Fedora 25 TemplateVM Upgrade for Qubes 3.2

2017-08-04 Thread Lorenzo Lamas
Because Fedora 25 has a newer version of NetworkManager, can the same method 
for MAC randomization for Debian now be used for Fedora instead of using 
macchanger as described here?
https://www.qubes-os.org/doc/anonymizing-your-mac-address/

-- 
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/2f0cb08b-5254-4fb5-a7e3-bd6956cd5ec9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] cannot install kernel 4.9.35 from …-current-testing

2017-08-04 Thread Holger Levsen
On Tue, Aug 01, 2017 at 01:06:24PM +0200, Marek Marczykowski-Górecki wrote:
> > I fail to install kernel 4.9.35 on Qubes 3.2, any hints how I can 
> > accomplish this? 
> > [user@dom0 ~]$ LANG=C sudo qubes-dom0-update 
> > --enablerepo=qubes-dom0-current-testing   kernel kernel-qubes-vm
> Try adding --action=update 

whoohoo, thanks for that, Marek! It also doens't work but at least hinted what
would be and was working: --action=upgrade!

Now let's see how this kernel works! :-)


-- 
cheers,
Holger

-- 
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/20170804192735.GB15943%40layer-acht.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature


[qubes-users] Re: Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread yuraeitha
I'm excited about the work you did on Qubes 4, it looks good so far. Can't wait 
to see the final stable version.

Obvious bugs during alpha/beta stages aside, I do feel sorrow for the lack of 
the Qubes VM Manager as well., and some other minor things that may have major 
user impact for some people.

- VM Backup GUI seems missing. Is this perhaps something still being worked on 
and is coming later? Seems really odd that it's missing. I am by no means 
worried about using the terminal, but it's often extra work. Which is really 
bad when it takes away valuable time, especially when on the move and in a 
hurry. It is also a disadvantage for people who are visually stronger to gather 
a mental overview of their system.

- Seems like there is a missing ability to see inactive VM's for the visual 
users (Just like the 3.2 VM Manager can show inactive VM's). This is really 
important for some people, while not important for some others. Albeit, perhaps 
I just missed the feature to turn it on in the widget?

- Not sure of this one, it might just be due to the VM starting bug, but it 
seems like we can't easily have an overview of used memory/drive space for each 
VM anymore? If true, this is a big problem for people on limited hardware 
resources, who need to be mindful of what is currently running in order not to 
spend it all up. For example (A contrast example), I never worry if I use all 
memory, it's essentially almost impossible for me to use it all up inside 
normal use cases. However on my "8GB ram/128GB SDD" laptop/tablet hybrid 
running Qubes, this is a very, very different story altogether.
Devices are only getting smaller, the inability to upgrade drives or memory in 
the near future, seems to make smart software more important than ever before. 
Having good overview of VM resources is imho a really, really good thing.
Especially because not everyone runs around with laptops that have 12-16+ GB 
memory.

- VM colors? It might be my limited knowledge here, but adding extra colors, 
even if just a few, shouldn't take long? 5-10 minutes to add? I might just be 
super naive here. But having said that, even a few extra colors would be really 
nice. Heck, even light and dark color versions, like for example light/dark 
variants of (blue,red,purple,green, etc.).


I did not have much time to look around, so perhaps I just missed some of the 
changes, but this is my first impression nontheless.

Having said that, I'm really, really excited about the increased virtualization 
security and the AdminVM features. Can't say nothing else but that it's an 
amazing job you guys did there (and a lot of hard work too, which we end users 
should appreciate more).

-- 
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/901c6245-fa32-4b8e-ad75-8893c74a0a87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/04/2017 02:20 PM, Marek Marczykowski-Górecki wrote:
> On Fri, Aug 04, 2017 at 01:12:29PM +0200, Zrubi wrote:

>> Can't see the networking stuff. The most important is (at least
>> for me) the actual NetVM used by a Qube.
> 
> So, you switch netvm for VMs frequently? Doesn't it mean you should
> have separate VMs, instead of switching one between two (or more)
> networks?

No.
I'm using separate WiFi, and Ethernet VM's, I have several VPN proxy
VM's as well, my dispVM start without net access. And need to use/test
lot of things with different network exits.


> Anyway, adding such information to domains widget shouldn't be a
> big problem. Just don't show it by default (see reasoning why
> dropping old manager, in announcement post).

I do not really agree with the reasoning tho.
But if it would be customizable? - just like the old Qubes manager ;)


> The main reason for nftables is to simplify custom scripts. If you 
> have nftables, qubes-firewall no longer flush standard tables - it 
> register its own. This means you don't need to re-apply own rules
> every time qubes-firewall change something. And you can register
> own tables before or after qubes-firewall. And in theory you can
> still use iptables for your custom rules.

Let's talk about these in a separate thread or ticket
Will collect my ideas and share it soon.

Currently even the basic networking looks unreliable, so I can't even
test my custom firewall rules...


>> But still feels like a bare naked login screen. IMHO this should
>> be just as important as the Qubes boot (splash) screen.
> 
> Which also have similar aesthetic. Do you think about just some
> better background there, or some bigger change?

A would say it's needs a bigger change.
But of course this is really subjective, and currently do not have
time to design a qubes related skin for the login manager :(

So this is just my (and my surroundings) opinion.
Handle with sustenance ;)


- -- 
Zrubi
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZhIJVAAoJEH7adOMCkunmTksP/3lDt5xZoRzMCdQWfdVGhvVk
qQOxLQq05QXi5r1+lxbg8gBHGiG3h/J1mLmeeqUjKgi1ywyxi6JUMOfwEyC77gtH
IG0Dz4yz0W/B1BsUngJFqPurvYJknmcQsughkwJGV17SiOoj71GBBPKkm7Dlow2w
BMrw8az4We5hulSSokSLKQGunZ9iPvm6e0pvRjhKtK/hlhao1w3/9UKKJEGGoIqN
kAAFiq9y4LYLTx8PHPZgNMnxw6XvxpXWRtAXeheG7VMuVO+1A8n4B0Th4hzB55Gs
bC+xCTJL7pJUbT0BtlnlqlM3CdiVVMRZo2GKGuAupjJ6UOm/6q1k2g2ZCF2aS5w2
3vPH0oFB6/E6Znfc/cxDJ+daAAN2vdcgbt9ExyAoUSr79sp9mYvKqaJftA9OAj99
XH35FlbuSPLxOrQ+1uKCImvmkHtAL6SV9Cnb8gWxiFTxMQ0FTw63W7oAkfzTFNEI
FT1sgBMv7RoxW/kpQf4LQOuyaLs4OUlgoK5V/pyw4M6IXNrQBL2leanbKeQkNlxQ
UlpFO/LvP261vlGV0znWCmnifffPtcTcfBI/b+Fxw4XsNzmJb3/Bzh9NRJ317gS1
WWleM0JdIQo4bp3qF3D4BsmdK8a+eUBNePlVaF/TB57DAAlAhh+YvOooFaI0QL0Z
QxiU4qQldkhOGdyG0nK/
=Qvvd
-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/e794e91b-8091-c31b-edfd-965fe3743744%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/03/2017 08:30 PM, Micah Lee wrote:
> The devices systray applet thing for me lists these devices:
> 
> sys-firewall:1-1 QEMU_QEMU_USB_Tablet_42

> 
> What is this qemu thing in sys-firewall?
Ihave the same issue, opened a ticket to track:
https://github.com/QubesOS/qubes-issues/issues/2969

- -- 
Zrubi
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZhHB7AAoJEH7adOMCkunmi/YP/RqQnkvTFedQmEI3GC64oebG
OvtHdsfxqOkecdPQyug7qTTImpN6IB3w7WwdoS09FcYq4FepOx08e672JQpMZeaT
nA1jMmgkS/PM4jUiX0/oDU7GP+gphANeHnV86KOhHxRBQz9yH2SjJ9iBsC3QNvWD
8ISaZt7nh+lZuig6IKLtA3AzmYnk1ZazQAkJgDqNw6QctnJ67fuhXAYoSexafEDX
A+esyTgBmWIELeloTkikksDlJpE4e3TKFEmk9n4/nouGTk7cArIeXOFgcRWo/5qI
LN2PAemSMjUyBG7ez3hG2kAXqRxAxztNBKnxwumgcqbio+G2BJd4OaPCn05p3MgQ
xY2+pZ6hwITDa0ouTbXL+xCn1f0m5hMlHvSvBLI2U927O+KIHLjoD7INuKejDdUj
puJ7UCwNgnGGmm9xx43VIdFZt6f1z2wOpIq53djHiOoMT2JzrSyk9Qu35iq/ik27
EzL1Bbnd31gX6mahtV2trpReWyk0GGhEgvi5Rugnfi1HGfkrq36hum3qjgNzM7FP
9pj9LquW9htdOTFyitIvVFMEF1Np0p8CkGsp62aMwitv/dgHAh52+lGzbiYkCtDP
fPRqCOkEd9g29S11Qt4y4IOjoK8rAdXb9ZL1OszzzA7284OB3lDxiEWJibrllA4+
fBhbT0oE8Nkl5MiyMSON
=+Lv7
-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/c678ef28-7573-d651-bd2a-3aa065c55785%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Aug 04, 2017 at 01:12:29PM +0200, Zrubi wrote:
> On 08/01/2017 01:02 PM, Marek Marczykowski-Górecki wrote:
> > On Tue, Aug 01, 2017 at 11:25:11AM +0200, Zrubi wrote:
> 
> >> - The isntall process is really long. Not debugged jet but
> >> the creating initramfs seems to be running forever. But at least
> >> was successfull at the end :)
> > 
> > Is it just about initramfs and "post installation tasks" - compared
> > to the whole installation time? There may be some bug causing
> > initramfs being generated twice (or more...) - I think I've fixed
> > something like this before, but maybe not all the places.
> Yes, this is the case.
> But have no time to install it again and again to identify the root
> cause :(

I have some other installer issues to debug, so may look into this too.

> >> - the missing Qubes Manager is a pain. - the 'replacement' in the
> >> task bar is small and buggy: the tooltip? like thing is randomly
> >> shirk to unusable. But too samll in general. I have 40 vm's right
> >> now.
> > 
> > What do you mean by "randomly shirk to unusable"? Can you provide
> > a screenshot?
> #2970
> 
> 
> > What do you mean? Domains widget is specifically there to show you 
> > VM status.
> 
> Can't see the networking stuff.
> The most important is (at least for me) the actual NetVM used by a Qube.

So, you switch netvm for VMs frequently? Doesn't it mean you should have
separate VMs, instead of switching one between two (or more) networks?

Anyway, adding such information to domains widget shouldn't be a big
problem. Just don't show it by default (see reasoning why dropping old
manager, in announcement post).

> >> - the 'new' Qubes firewall solution causing more confusions. -
> >> mixed iptables and nftables? why?
> > 
> > What do you mean by mixed? Setting for VMs are applied using
> > nftables if supported (Fedora), or iptables when not (Debian). Not
> > both.
> 
> the default "self defending rules" are Iptables based, the VM traffic
> forwarding rules are nftables based.

Ah I see.

> Custom firewall scripts now have to handle both.
> My opinion that there is no real need for nftables until it can really
> replace iptables. We are using just a really few rules here and the VM
> based chains achievable by iptables too.

The main reason for nftables is to simplify custom scripts. If you
have nftables, qubes-firewall no longer flush standard tables - it
register its own. This means you don't need to re-apply own rules every
time qubes-firewall change something. And you can register own tables
before or after qubes-firewall.
And in theory you can still use iptables for your custom rules.

> BTW:
> I plan to continue the L7 filtering thing I started to play with. Can
> you point the related documentation - if any - or at least the VM side
> code processing the Qubes firewall rules please?

It's here:
https://github.com/QubesOS/qubes-core-agent-linux/blob/master/qubesagent/firewall.py

I think you can extend one or both of those classes and use them instead
of default ones. Or submit a patch.
This code unfortunately do not have (yet?) nice interface to extend it
for other rule types.

> >> - even if Allow is the default policy I see a DROP rule at the
> >> end. Why? :o
> > 
> > To fail closed - if something goes wrong, there will be that DROP
> > rule at the end anyway.
> 
> :)
> It should be decided by the user, by selecting default policy.
> IMHO Qubes should not try to override the user decisions.

If you choose to have default action "allow", there will be appropriate
rule just before it.

> >> - the default login screen is just ugly. I know that this is not
> >> the first priority, and not even a technical issue. But new users
> >> will see that ugly thing first. So it's should be a Qubes skinned
> >> one. at least.
> > 
> > Hmm, I do see Qubes logo in the background there. Do you have
> > something different?
> 
> Nope, I see the qubes backround. :)
> 
> But still feels like a bare naked login screen.
> IMHO this should be just as important as the Qubes boot (splash) screen.

Which also have similar aesthetic.
Do you think about just some better background there, or some bigger
change?

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZhGZ5AAoJENuP0xzK19csrEUH/1oHKMAGQKfnD36j3CKN3qvb
JisyZ7AUhICjM7vVoWNw07PUMLtq4ijRdVjra1vNbZ6QHq5Hm7Er5DwOzstEIfYC
j96nWHLUczh5lqXEV/E2Yg+A8LEt8VodyhWrzNM8L/bYeyKK8pn+vS8Ofxqxr6pm
z2MO0APzOoR3I5Alru4W1+JA6c+kOGWjHzPIinL0v2xe7ROrkIczfL8+D4pj7PsQ
Sh74J6H8c8drRhixB9db2TomaB0gb0Hdzq065lUoVQtbjRwAYvsqkAfNMbrnejn2
YmUDMhJ6Xtefn+WK/1tWao1GbsK7Nv8sXOhi98NJDpXgK5Dk9NEdPsauyxOOd5o=
=COcE
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe 

[qubes-users] Re: Nvidia drivers in dom0 still works? (need to get a GTX 1070 off the ground)

2017-08-04 Thread mj . engelbrecht
On Sunday, 8 January 2017 19:42:35 UTC+2, daltong defourne  wrote:
> On Sunday, January 8, 2017 at 11:07:55 AM UTC+3, Foppe de Haan wrote:
> > On Sunday, January 8, 2017 at 1:36:37 AM UTC+1, daltong defourne wrote:
> > > On Monday, December 19, 2016 at 1:33:23 AM UTC+3, Mathew Evans wrote:
> > > > Just to update.
> > > > 
> > > > I am currently running Nvidia drivers without a issue.
> > > > 
> > > > dom0 Kernel: 4.4.31-11
> > > > Nvidia: 375.20
> > > > Kernel-module: compiled in dom0; 
> > > > 
> > > > Quick Guide:
> > > > 1. dom0:   qubes-dom0-update install gcc devel-kernel ksmod 
> > > > linux-headers
> > > > 2. appvm:  download NVIDIA-Linux-375.20-install.run (any appvm)
> > > > 3. dom0:   qvm-run --pass-io  'cat /PATH/TO/NVIDIA.run' > 
> > > > NVIDIA.run
> > > > 4. dom0:   ./NVIDIA.run --ui=none --no-x-check --keep --extract-only 
> > > > 5: dom0:   cp NVIDIA-*/kernel/;  IGNORE_XEN_PRESENCE=y CC="gcc 
> > > > -DNV_VMAP_4_PRESENT -DNV_SIGNAL_STRUCT_RLIM" make module;
> > > > 6: dom0:   cp nvidia.ko 
> > > > /lib/modules/4.4.31-11.pvops.qubes.x86_64/extra/.
> > > > 7: dom0:   depmod -a; modinfo nvidia (all working will show up fine)
> > > > 8: dom0:   EDIT GRUB or EFI; add rd.driver.blacklist=nouveau
> > > > 9: dom0;   reboot and enjoy nvidia support.
> > > > 
> > > > additional: you can install nvidia extra apps etc.. if you so wish just 
> > > > run ./nvidia.run --no-kernel-module -a
> > > > 
> > > > 
> > > > Hopefully this will help those of you wanting Nvidia driver instead of 
> > > > Nouveau.
> > > > Please note this is a ruff write up and guide not a perfect solution, 
> > > > and assumptions are made that you are always fimilar enough with *nix 
> > > > operating systems to figure out that parts i've missed out or aint put 
> > > > in detail.
> > > 
> > > Did you run into a fatal xorg crash when trying to get xorg use nvidia 
> > > driver?
> > > If yes, how did you beat it? 
> > > 
> > > I get a "Failed to allocate sofware rendering cache surface: out of 
> > > memory" error which, according to Google, is pretty damn bad 
> > > https://www.google.se/search?q=NVIDIA+xorg+Failed+to+allocate+sofware+rendering+cache+surface:+out+of+memory.
> > > 
> > > Full log of my Xorg's sad demise when using Nvidia driver
> > > 
> > > http://pastebin.com/E9Guuea4
> > > 
> > > P.S.:
> > > If I may ask, what nvidia card are you using?
> > 
> > I got (to) the same (point). Have not managed to get it to work so far. 
> > Same error, too, though I got multiple (depending on how I tried to 
> > initialize X). gtx 950.
> 
> I hope Mathew Evans has the secret (he said he is running the driver "without 
> an issue" ... (intense finger crossing)

Having the same issue. It's very clear that NVIDIA is not supporting Xen 
according to this chat 
https://devtalk.nvidia.com/default/topic/691565/linux/geforce-driver-problem-on-centos-6-4-with-xen-installed/2/?offset=26#5197554
 

-- 
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/e7961e63-9738-4b71-874a-c68d7cd7d646%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/01/2017 01:02 PM, Marek Marczykowski-Górecki wrote:
> On Tue, Aug 01, 2017 at 11:25:11AM +0200, Zrubi wrote:

>> - The isntall process is really long. Not debugged jet but
>> the creating initramfs seems to be running forever. But at least
>> was successfull at the end :)
> 
> Is it just about initramfs and "post installation tasks" - compared
> to the whole installation time? There may be some bug causing
> initramfs being generated twice (or more...) - I think I've fixed
> something like this before, but maybe not all the places.
Yes, this is the case.
But have no time to install it again and again to identify the root
cause :(


> 
>> - the missing Qubes Manager is a pain. - the 'replacement' in the
>> task bar is small and buggy: the tooltip? like thing is randomly
>> shirk to unusable. But too samll in general. I have 40 vm's right
>> now.
> 
> What do you mean by "randomly shirk to unusable"? Can you provide
> a screenshot?
#2970


> What do you mean? Domains widget is specifically there to show you 
> VM status.

Can't see the networking stuff.
The most important is (at least for me) the actual NetVM used by a Qube.


>> - the 'new' Qubes firewall solution causing more confusions. -
>> mixed iptables and nftables? why?
> 
> What do you mean by mixed? Setting for VMs are applied using
> nftables if supported (Fedora), or iptables when not (Debian). Not
> both.

the default "self defending rules" are Iptables based, the VM traffic
forwarding rules are nftables based.

Custom firewall scripts now have to handle both.
My opinion that there is no real need for nftables until it can really
replace iptables. We are using just a really few rules here and the VM
based chains achievable by iptables too.

BTW:
I plan to continue the L7 filtering thing I started to play with. Can
you point the related documentation - if any - or at least the VM side
code processing the Qubes firewall rules please?

>> - even if Allow is the default policy I see a DROP rule at the
>> end. Why? :o
> 
> To fail closed - if something goes wrong, there will be that DROP
> rule at the end anyway.

:)
It should be decided by the user, by selecting default policy.
IMHO Qubes should not try to override the user decisions.

>> - the default login screen is just ugly. I know that this is not
>> the first priority, and not even a technical issue. But new users
>> will see that ugly thing first. So it's should be a Qubes skinned
>> one. at least.
> 
> Hmm, I do see Qubes logo in the background there. Do you have
> something different?

Nope, I see the qubes backround. :)

But still feels like a bare naked login screen.
IMHO this should be just as important as the Qubes boot (splash) screen.


- -- 
Zrubi
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZhFaWAAoJEH7adOMCkunmwEwQAIbwUTS/qKwczyhclNTPRknb
lSNTH9xPuh44fx3Iql+cwU6EpcDRvTswTZ0uuMsrCE5vk1XsZlgyRbJSL5n0Nmof
Ax+x6nMoEiOo3pbKOYRmqc5SmWCdi6rUbHRYmOa0eij7+rvdStAD6opca5x8lhkO
rStnTKVMTQSSYk/BHT7V2P27tChDAiD2ahB3tvi00SrszhHGrxW/oZ/8RPwkHEWi
XEdsqEqJWDS1BkR85IYV0bzoED/uDEtfNqMzPpvAaIORDGdClQi6Ky31BR7dxJRZ
o3ngKj9F/lvOd/1HYeD2bErB/y5LJSzgX/18lMiaA+CJa3cXwjzGMEuho7Hra0dK
ts1G5bfBDomHfriQElXhspggsleHV+V0aQJnMKd4gGfY0/5/h+xgeUMi/RevVScX
nCDvjguDJoktoUQXK8dgt5hwauvPWsSTyJjk5h9I94ij9hMGkbfRzwA+2gEriZw/
g8Dl3WGzm3kX5aOzO9S3CqKY2bQoJwWTO11q9VcjfdE3Qtnu7Y44ECa3bi59B1AD
UMc2RQEs9RZ37hUXd5Yfdj68fTD1qCuTX0NRBwxGddT/tOZYXvwEUjs8HqXsM2qf
mRGspB/OnHZ2F48J1q6uE4JE+Hyap1lJeSgXaUKpMtzvLBwQTC8v/v5wF8j581ao
vwPw7/gGelMGQ4qIAS6S
=zTfv
-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/bdecc032-8cf8-047d-6cd9-f02c42ee9c56%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] DELL Latitude E6410 Installation IO, but hangs after reboot

2017-08-04 Thread pencilfight



3. Aug 2017 07:24 by srv-net-fo...@kozo.ch:


> Hello
>  i have installed Qubes 3.2 on a DELL | Latitude E6410
>  The Installation works fine, with no error, then he Need a reboot and there 
> it hangs just after the Bios Check.
>  what should i do?
>
>  have a nice day
>  vinc
>
> -- 
>
>




Hit F1 in the bios check. This happens sometimes on thinkpads as well and the 
fix is disabling all networking and vt-d for your very first boot up. Reboot, 
then re-enabling them. Also go through everything in the Bios menus and make 
sure options like legacy boot is enabled and things like secure boot are 
disabled, off there top of my head. I would start there and play around with 
those options and I bet that may fix it. 




Pen

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


Re: [qubes-users] Unable to install KDE desktop

2017-08-04 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Aug 04, 2017 at 12:22:15PM +0200, Zrubi wrote:
> On 08/04/2017 01:18 AM, Marek Marczykowski-Górecki wrote:
> > 
> >> https://github.com/QubesOS/qubes-issues/issues/2921 appears to
> >> track this issue.
> > 
> > Fixed, for both 3.2 and 4.0.
> 
> 
> Thanks, the installation works as before:
> https://www.qubes-os.org/doc/kde/
> 
> However, because of the tray-icon bugs (#2283, #2264, and manymore) it
> is pretty unusable now.
> 
> The last templates where the tray icons are working:
> F23, Debian8
> 
> Newer releases are showing transparent icons for most of the apps.
> 
> Moreover the new (Qubes related) devices tray icon coming from dom0 is
> invisible too.
> 
> 
> 
> I know that nobody cares about KDE related bugs.
> This is just a status report, to save hours for other users try to use
> KDE :)

Can we create a single ticket for tracking KDE-related bugs?
So, if anyone will want to improve KDE support, there will be a single
place to look. Later we may create separate issues and reference them
from it.

It's here:
https://github.com/QubesOS/qubes-issues/issues/2968

Feel free to add comments (not only about new widgets), I'll move them
to main description as additional points there.

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJZhE5uAAoJENuP0xzK19csbpgIAJHbAkB/7Nxj2+tZK0E7qmwg
6wxfTQACbTNmsdVnph6AdewMDwakx0yavJMk8ofiDeOscSYICeVfi2+YDIhV4qHK
CJz9QxEKl+0zCB7ngmV651vs6dxBlMPv6zliI2at5HRpF47fYNb9a9a0Xw39slJN
uIKjRgHDPQp24Zni36KRGAPKFWTqmhqdTE5cC9P0w5UDR+Rz9q7OpZR1yvSaOEb3
rgo3jJWPkgC3Ro9esaKAwW+1iiBThLYyz8N3fDfBOYQoOm5I1TI4WZboH61WF2UH
YOU0iVOGbCkj2C2TsRm+Z6L+/NrSbRgYHX2JG9/5NyIrZkDw4scK6bXiVtfLOp0=
=4scJ
-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/20170804103733.GG1095%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Unable to install KDE desktop

2017-08-04 Thread Zrubi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 08/04/2017 01:18 AM, Marek Marczykowski-Górecki wrote:
> 
>> https://github.com/QubesOS/qubes-issues/issues/2921 appears to
>> track this issue.
> 
> Fixed, for both 3.2 and 4.0.


Thanks, the installation works as before:
https://www.qubes-os.org/doc/kde/

However, because of the tray-icon bugs (#2283, #2264, and manymore) it
is pretty unusable now.

The last templates where the tray icons are working:
F23, Debian8

Newer releases are showing transparent icons for most of the apps.

Moreover the new (Qubes related) devices tray icon coming from dom0 is
invisible too.



I know that nobody cares about KDE related bugs.
This is just a status report, to save hours for other users try to use
KDE :)

- -- 
Zrubi
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQIcBAEBCAAGBQJZhErQAAoJEH7adOMCkunmFGcQAJ+ZkW9Powsq7jaP8A70D0Qo
KazAIEeYS4ePEhNIc/dp9u2unuYRH6dxP4Cho7OO58NiZm4NNLLL0NdmzUIkdOAL
o5pa6jVjyj4MOhftTdkz+k0TV5iU15ukxT71+colono5YucK4dI6poDRYm72UNMR
QxhNxGQLZxHm7+Ed4SpGrSsDfqgFgaMOc1iiuEsQGsDYu8ixDptaD9j+i0HY32Kv
3F1aDCg/Pl/eJ8LEnQrSGbU1wrvgz/i4QTkH+/agaXPhSRrjL4qmugcX8uCJ2+/5
VuxDQqC6ozbKmqqw+zgUHTK82QQ0fMqLtrXv3gOEiQN1xQIJticsdOn8Jw+Sw6L+
0nfmWi57lf3I5MsQkSvPA30xPLS/jDlXe9Kcn9jUbsJgZHO+dc+Y3xtXuBYOq7/u
B0aBQfsBi3ECTgxXehpqgZ+sdAzk3/3SrVxVQ72WzZr4gkO6mVIH46X18HueuXn4
AKz+1rHcvqOLY/VdyMc2bb2Mb2GHurWxHdfGP1RDKteldCMl2T63DL8o6ghoQMmF
SUA1f/vs6ppqlsguGuaC8lm/8nUWQs3QeOXpXGOWc6XRJvw7lQGWrt1wYrcoStlx
cAne8T5B11NocUv+HzvsoAJT2Kyl6Gyyjv8zTciVQcGXXHwCtwT2w9Jx6kqzfg3z
yMmSFHToURfTn39gaaqe
=r8Jl
-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/954298e7-278a-ec59-c7cc-18ccb3f2bb10%40zrubi.hu.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes OS 4.0 first release candidate (rc1) has been released!

2017-08-04 Thread Foppe de Haan
I would (also) appreciate having a GUI for the qubes-backup functionality, so 
we can easily pick/choose which VMs to restore.

-- 
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/73322d06-b2d3-47fb-ae28-e8316b425ac4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.