Re: [qubes-users] Could Qubes Installation Configuration Be More User Friendly?

2019-03-02 Thread Aaron
Unfortunately I don't have that option in BIOS. There is no way I can
disable Nvidia chip.

An average user won't deal with that much complication during installation
and this is probably a huge barrier to convert many users from other OS to
Qubes.

I hope to see Qubes finding an easy solution for this issue.


On Sat, Mar 2, 2019 at 11:33 PM Chris Laprise  wrote:

> On 3/3/19 12:37 AM, acr...@gmail.com wrote:
> > Hi,
> >
> > This is one of the best OS I have every seen but I haven't gotten a
> chance to use it yet due to installation issues.
> >
> > I found that Qubes installation is very difficult.
> >
> > I do have a notebook comes with Intel + Nvidia GPU and it makes Qubes
> installation very difficult.
> >
> > I'm just wondering if there is a plan to make it more user friendly to
> handle installation issue?
>
> Its more accurate to say that Nvidia hardware is difficult to work with
> because they hate (or are afraid of) open source. For this reason, some
> operating systems such as Qubes warn against using Nvidia:
>
> https://www.qubes-os.org/doc/system-requirements/
>
> Many computers can disable the Nvidia chip and use the Intel integrated
> GPU instead. This can be controlled from the BIOS/firmware settings.
>
> --
>
> Chris Laprise, tas...@posteo.net
> https://github.com/tasket
> https://twitter.com/ttaskett
> PGP: BEE2 20C5 356E 764A 73EB  4AB3 1DC4 D106 F07F 1886
>

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


Re: [qubes-users] Could Qubes Installation Configuration Be More User Friendly?

2019-03-02 Thread Chris Laprise

On 3/3/19 12:37 AM, acr...@gmail.com wrote:

Hi,

This is one of the best OS I have every seen but I haven't gotten a chance to 
use it yet due to installation issues.

I found that Qubes installation is very difficult.

I do have a notebook comes with Intel + Nvidia GPU and it makes Qubes 
installation very difficult.

I'm just wondering if there is a plan to make it more user friendly to handle 
installation issue?


Its more accurate to say that Nvidia hardware is difficult to work with 
because they hate (or are afraid of) open source. For this reason, some 
operating systems such as Qubes warn against using Nvidia:


https://www.qubes-os.org/doc/system-requirements/

Many computers can disable the Nvidia chip and use the Intel integrated 
GPU instead. This can be controlled from the BIOS/firmware settings.


--

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

--
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/66e769cc-9c44-32d7-9bf6-1ff26cd12a22%40posteo.net.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Could Qubes Installation Configuration Be More User Friendly?

2019-03-02 Thread acraft
Hi,

This is one of the best OS I have every seen but I haven't gotten a chance to 
use it yet due to installation issues.

I found that Qubes installation is very difficult. 

I do have a notebook comes with Intel + Nvidia GPU and it makes Qubes 
installation very difficult.

I'm just wondering if there is a plan to make it more user friendly to handle 
installation issue? 

Thanks,
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/8cf0d0e7-3238-44d3-a84f-3d4cdb1624bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] where/how does dom0 gets its icons? ANSWERED

2019-03-02 Thread Daniel Allcock
Thank you to unman for giving me the thread to follow.
The way the icons are chosen could be improved easily.
I'd be happy to contribute a patch if I knew the procedure
for doing so.  (It would not touch dom0.)

To close out the thread, here is the answer to my question.
The process of updating the Q menus is controlled by dom0's
/usr/lib/python3.5/site-packages/qubesappmenus/receive.py.
When updating the Q menus, dom0 first asks the vm for its
desktop files.  The vm provides these using 
/etc/qubes-rpc/qubes.GetAppmenus, which is a shell script
that jumbles all the desktop files on the system
together and sends to stdout.  dom0 sanitizes and parses this,
and assembles the results into a bunch of desktop files in
dom0's ~/.local/share/qubes-appmenus/VM.  As it is doing this
it notes which icons specified in the desktop files have 
relative paths (typically, all of them).  For each icon name,
dom0 asks the vm to run /etc/qubes-rpc/qubes.GetImageRGBA 
and deliver the resulting icon file to dom0.  For icons
described by a relative path, the first thing
this shell script does is resolve the icon name to a file name using 
/usr/lib/qubes/xdg-icon, which is also a shell script, and is
where the actual resolution takes place.

This resolution is simplistic.  It uses a fixed list of
icon theme names (on my system: Humanity, Adwaita, gnome, oxygen),
followed by any additional icon themes in /usr/share/icons.  
The first theme that has a suitably named icon is the theme
whose icon file gets used.  I don't have Humanity installed, so
I was getting Adwaita icons every time, and overwriting them
was the only way I could change my icons.

A simple fix is to insert my desired icon theme at the beginning
of the fixed list of themes.  This is not the right
way to solve the problem in general.  To solve it properly would
require deciding what the right behavior is: should the theme
used in dom0 (meaning: one of the same name) get used?  Or should the
theme preferred by that template's user account get used? Not
sure what the most natural answer is.  But I'm satisfied for now.

Thank you!
Daniel

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


Re: Re[2]: [qubes-users] Responding to the Whonix trolls...

2019-03-02 Thread 799
cooloutac  schrieb am Sa., 2. März 2019, 22:16:

> [...]
> Stop being a nazi.
>

Please don't write such quotes in a public forum, as someone who might
argue that he wants to silence the discussion (which don't have to be ok)
is something completely different from someone who was involved in
something like the holocaust.
Making such a comparison is totally unacceptable.

"As an online discussion grows longer, the probability of a comparison
involving Nazis or Hitler approaches 1"
(...) that is, if an online discussion (regardless of topic or scope) goes
on long enough, sooner or later someone will compare someone or something
to Adolf Hitler or his deeds, the point at which effectively the discussion
or thread often ends.

https://en.m.wikipedia.org/wiki/Godwin%27s_law

And no, I will not refresh the discussion at this point as it is not Qubes
related (anymore).

- O

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


Re: Re[2]: [qubes-users] Responding to the Whonix trolls...

2019-03-02 Thread cooloutac
On Saturday, March 2, 2019 at 6:03:55 AM UTC-5, Achim Patzner wrote:
> On 02.03.2019 03:21:14, "unman"  wrote:
> >I don't want a list that is banning people or excluding them. It's
> >regrettable that Whonix does so. In my experience, that rarely works
> >given the ready availability of new email addresses.
> 
> That's why I like mailing lists which require a sponsor to add you and 
> which will hold said sponsor responsible for the behaviour of his 
> invitees. If you bring in too many duds. you're getting thrown out, too.
> 
> >If you don't like a user, just add them to your kill file.
> 
> As long as there are no really useful tools that eliminate everything 
> that contains quotes of the user you don't really need in your life this 
> is not as helpful as eliminating that user completely. Unless said kill 
> file is the input queue of a skilled assassin...
> 
> 
> >Build the community that *you* want, by promoting the issues/discussions
> >that are of value. Let the others wither away.
> 
> Some trolls don't wither on their own. Those have to be cut back.
> 
> 
> Achim

Stop being a nazi.

I already gave you the link for qubes-devel.  

-- 
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/4b12b761-7509-44a1-b015-6c96dc3a0490%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Structure of qubes

2019-03-02 Thread acharya . sagar . sagar5
I dug many things. The docs on qubes official site are old. I tried both the 
ways to install my NVIDIA GTX 1060 and the problem is even after installing, 
it's unclear whether I would be able to use it outside dom0.

I found a better method. I have a Ryzen 3 2200G APU which I intend to use for 
basic qubes graphics in dom0 and want to install NVIDIA GTX card in the work 
domain fedoraDev as a secondary card. In this way dom0 would remain more secure 
and I could use tensorflow-gpu in work VM(atleast that's my conjecture). 
However, when I change the settings in Booting menu to Integrated Graphics 
Device and change the connection of HDMI to motherboard from Graphics Card, 
Qubes doesn't bootup. It stops at 

Starting Show Plymouth Boot Screen...

It doesn't move forward. 

I have 2 questions, is this configuration of APU for dom0 and GPU for 1 cloned 
template possible? And how to boot with IGD after installing with GPU?

Thanks

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


[qubes-users] Re: Best ideal laptop for Qubes?

2019-03-02 Thread travorfirefuelcan
четверг, 21 февраля 2019 г., 3:49:27 UTC+3 пользователь dexint...@gmail.com 
написал:
> I've been spending hours and hours looking at laptop configs from dell to 
> lenovo and I still have yet to make a decision. I'm hoping you guys can help 
> me. 
> 
> Uses:
> 
> - Programming
> - Web Dev
> - Tor
> - Screen real estate
> - Regular web surfing and videos
> - Some video and photo editing but I have a PC for that 
> 
> I'd like to keep cost as low as possible but my budget is very flexible if I 
> need to stretch it. I want something that will last me 3-5 years.

p52 thinkpad xeon + 128gb ram :)

-- 
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/389b2e35-cf15-43f8-b6f8-68fcbdec196c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] where/how does dom0 gets its icons?

2019-03-02 Thread unman
On Sat, Mar 02, 2019 at 09:32:38AM -0600, Daniel Allcock wrote:
> Thank you David. It seems, though, to be more complicated than that.
> 
> > On 3/1/19 8:54 PM, Daniel Allcock wrote:
> > > Hello,
> > > I would like to understand what to do to customize the icons
> > > that appear in the Q menu for template and app vms.
> > > The only way I have found that works is to overwrite icon
> > > files in /usr/share/icons/Adwaita/* in the template vm.
> > > chose that icon theme in xfce settings.  Everything just works.  
> > 
> > I don't know about Adwaita or anything, but Qubes OS adheres to the 
> > Freedesktop Standard [1] (I guess version 1.0 though).
> > 
> > So the entire menu incl. icons is managed by *.desktop and *.menu
> > files in dom0. Nothing is imported from within any VM.
> 
> the vm's do communicate their desktop files to dom0, and icons for
> them.  This is what populates the directories in dom0 that produce
> the Q menu.  Whenever you install software in a template vm using
> dnf, it says "notifying dom0 about newly installed applications..."
> Whenever you choose "refresh applications" in Qubes Manager, dom0
> fires up the underlying template and reimports the desktop and icon
> files.
> 
> The basic mechanism in the Freedesktop standard is that that each
> desktop file specifies an icon, eg "Icon=utilities-terminal".
> When it comes time to display an icon, the system looks in the user's
> selected icon theme for a file of that name (perhaps with a
> suffix like .svg or .png).  That icon theme may specify a fallback
> icon theme, where the system will look if it doesn't find an icon
> of that name.  The fallback can have fallbacks, etc, with "hicolor"
> being the icon theme of last resort. (This theme might not appear
> in menus, for example it doesn't appear in xfce's icon theme setting
> screen.  But it is present in /usr/share/icons.)
> 
> The point is that what icons are displayed has two inputs: the icon
> names in the desktop files, and the user's choice of icon theme, which
> maps those icon names to actual image files.  What I would like
> to understand is how qubes handles this.  It resolves the icon
> names to image files in some way, imports the icons to dom0,
> and colorizes them.  How does the resolution work?
> 
> I had two guesses, both
> seemingly reasonable but neither correct. (For each appvm, it might
> use the icon theme setting of the user account in that appvm.  Or,
> dom0 might use the theme in the appvm that has the same name
> as the theme chosen in dom0.)
> 
> At this point my hypothesis is that the
> communication-of-icons-to-dom0 process 
> (1) completely ignores appvms in favor of their underlying templates. 
> (2) completely ignores icon theme settings, just using Adwaita icons
> (from the template vm; it does not use, or perhaps uses at a lower
> priority, the Adwaita icons already present in dom0). 
> 
> Would appreciate any info, even just confirmation of this.
> 
> Thank you,
> Daniel
> 

Hi Daniel,

It's some time since I looked at this, but I had a quick look at the
code. Take any of this with a (large) pinch of salt, but it may help you
to get to the right place.

I think the magic happens in
/usr/lib/python3.5/site-packages/qubesappmenus/receive.py .
This is where the icon directory is created, and icons are picked up
from the templates.(Yes, as you  say, they come from the template).
appmenus in the template are parsed, and the contents written in to
appmenu templates in dom0.

The icon file is read from the desktop file referenced in the template,
and copied to dom0. This is done by a call to imgconverter.
You'll find there a function get_xdg_icon_from_vm which attempts to
copy and sanitise an icon image from the template.

For applications installed in qubes, have a look at:
https://www.qubes-os.org/doc/managing-appvm-shortcuts/

So I think  your hypothesis 1 is correct, and 2 is partly right.

hth

unman

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


Re: [qubes-users] where/how does dom0 gets its icons?

2019-03-02 Thread Daniel Allcock
Thank you David. It seems, though, to be more complicated than that.

> On 3/1/19 8:54 PM, Daniel Allcock wrote:
> > Hello,
> > I would like to understand what to do to customize the icons
> > that appear in the Q menu for template and app vms.
> > The only way I have found that works is to overwrite icon
> > files in /usr/share/icons/Adwaita/* in the template vm.
> > chose that icon theme in xfce settings.  Everything just works.  
> 
> I don't know about Adwaita or anything, but Qubes OS adheres to the 
> Freedesktop Standard [1] (I guess version 1.0 though).
> 
> So the entire menu incl. icons is managed by *.desktop and *.menu
> files in dom0. Nothing is imported from within any VM.

the vm's do communicate their desktop files to dom0, and icons for
them.  This is what populates the directories in dom0 that produce
the Q menu.  Whenever you install software in a template vm using
dnf, it says "notifying dom0 about newly installed applications..."
Whenever you choose "refresh applications" in Qubes Manager, dom0
fires up the underlying template and reimports the desktop and icon
files.

The basic mechanism in the Freedesktop standard is that that each
desktop file specifies an icon, eg "Icon=utilities-terminal".
When it comes time to display an icon, the system looks in the user's
selected icon theme for a file of that name (perhaps with a
suffix like .svg or .png).  That icon theme may specify a fallback
icon theme, where the system will look if it doesn't find an icon
of that name.  The fallback can have fallbacks, etc, with "hicolor"
being the icon theme of last resort. (This theme might not appear
in menus, for example it doesn't appear in xfce's icon theme setting
screen.  But it is present in /usr/share/icons.)

The point is that what icons are displayed has two inputs: the icon
names in the desktop files, and the user's choice of icon theme, which
maps those icon names to actual image files.  What I would like
to understand is how qubes handles this.  It resolves the icon
names to image files in some way, imports the icons to dom0,
and colorizes them.  How does the resolution work?

I had two guesses, both
seemingly reasonable but neither correct. (For each appvm, it might
use the icon theme setting of the user account in that appvm.  Or,
dom0 might use the theme in the appvm that has the same name
as the theme chosen in dom0.)

At this point my hypothesis is that the
communication-of-icons-to-dom0 process 
(1) completely ignores appvms in favor of their underlying templates. 
(2) completely ignores icon theme settings, just using Adwaita icons
(from the template vm; it does not use, or perhaps uses at a lower
priority, the Adwaita icons already present in dom0). 

Would appreciate any info, even just confirmation of this.

Thank you,
Daniel

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


Re: [qubes-users] where/how does dom0 gets its icons?

2019-03-02 Thread David Hobach

On 3/1/19 8:54 PM, Daniel Allcock wrote:

Hello,
I would like to understand what to do to customize the icons
that appear in the Q menu for template and app vms.
The only way I have found that works is to overwrite icon
files in /usr/share/icons/Adwaita/* in the template vm.

In dom0 it is easy: I put an icon folder Qubes in ~/.icons,
with a custom svg icon for a terminal, named appropriately, and Adwaita
as backup icon theme, ran gtk-update-icon-theme, and then chose that
icon theme in xfce settings.  Everything just works.


I don't know about Adwaita or anything, but Qubes OS adheres to the 
Freedesktop Standard [1] (I guess version 1.0 though).


So the entire menu incl. icons is managed by *.desktop and *.menu files 
in dom0. Nothing is imported from within any VM.


If I recall correctly, the menu structure is managed at 
~/.config/menus/applications-merged/ and the name & icons of the entries 
at ~/.local/share/applications.


The sync you mentioned probably copies files from 
~/.local/share/qubes-appmenus/ to ~/.local/share/applications as you 
reconfigure your menu with e.g. the Qubes manager. I'm not 100% sure 
about that, but you can easily test it.


Hope that helps,
David

[1] https://standards.freedesktop.org/desktop-entry-spec/latest/

--
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/d5d38c19-2157-60d4-7906-9e8137304401%40hackingthe.net.
For more options, visit https://groups.google.com/d/optout.


smime.p7s
Description: S/MIME Cryptographic Signature


Re[2]: [qubes-users] Responding to the Whonix trolls...

2019-03-02 Thread Achim Patzner

On 02.03.2019 03:21:14, "unman"  wrote:

I don't want a list that is banning people or excluding them. It's
regrettable that Whonix does so. In my experience, that rarely works
given the ready availability of new email addresses.


That's why I like mailing lists which require a sponsor to add you and 
which will hold said sponsor responsible for the behaviour of his 
invitees. If you bring in too many duds. you're getting thrown out, too.



If you don't like a user, just add them to your kill file.


As long as there are no really useful tools that eliminate everything 
that contains quotes of the user you don't really need in your life this 
is not as helpful as eliminating that user completely. Unless said kill 
file is the input queue of a skilled assassin...




Build the community that *you* want, by promoting the issues/discussions
that are of value. Let the others wither away.


Some trolls don't wither on their own. Those have to be cut back.


Achim

--
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/emc30e2d80-fe44-4f38-8356-e4aceebaedca%40sir-face.
For more options, visit https://groups.google.com/d/optout.