Re: [qubes-users] How to setup Win10 HVM ?

[Franz]

On Sun, Mar 22, 2020 at 7:32 PM Franz <169...@gmail.com> wrote:

>
>
> On Sun, Mar 15, 2020 at 8:15 AM 'M' via qubes-users <
> qubes-users@googlegroups.com> wrote:
>
>> How to setup a Win 10 HVM according to this page: 
>> https://github.com/elliotkillick/qvm-create-windows-qube
>> ?
>>
>> 
>>
>>
>> See below for my detailed description on how to use this method:
>>
>> 1)  Open your Firefox browser in a VM - for example in the untrusted VM.
>>
>> 2)  To save the install.sh script file:  Open this page:
>> https://raw.githubusercontent.com/elliotkillick/qvm-create-windows-qube/master/install.sh
>> and save it as install.sh
>>
>> 3)  To copy the file to dom0: Open the dom0 terminal and execute this
>> command:  qvm-run -p --filter-escape-chars --no-color-output untrusted
>> "cat '/home/user/Downloads/install.sh'" > install.sh
>>
>> 4)  To check that the file is copied to dom0: Execute this command in the
>> dom0 terminal: ls
>>
>> 5)  To get Qubes OS to execute the script in the "install.sh" file:
>> Execute this command in the dom0 terminal: chmod +x install.sh &&
>> ./install.sh
>>
>> 6)  Download the version of Windows 10 you want to use to the
>> "windows-mgmt" VM.
>>  You can execute the script in the file "download-windows.sh , but it
>> might not work - I couldn't make it work. In that case, do the following:
>>
>>  6a)  Open the “Qube Settings” for the domain “windows-mgmt”. Under
>> “Network”, choose the “default” one and click on “Apply”.
>>
>>  6b)  Open the domains Firefox browser and search the web for “how to
>> download windows 10”.
>> One of the first results is a link to a Microsoft webpage
>> from which it is possible to download the file in the local language.
>> The file gets downloaded to the download folder in the
>> domain.
>>
>>  6c)  Open the “Qube Settings” for the domain “windows-mgmt”. Under
>> “Network”, choose “(none)” and click on “Apply”.
>>
>>  6d)  Move or copy the downloaded Win10 ISO-file to this destination:
>> /Documents/qvm-create-windows-qube/windows-media/isos
>>
>>  6e)  Open the terminal in dom0 and execute the following script
>> (remember to write the name of the ISO-file you downloaded in step 6b
>> instead of “filename”): ./qvm-create-windows-qube.sh -n sys-whonix -oyw
>> -i filename.iso -a win10x64-pro.xml Win10
>> Info: "Win10" will be the name of the domain.
>> Do not close the terminal before it says the installation was
>> complete (successfully) !  Let the terminal do the job, it restarts the
>> qube and so on when it is necessary.
>>
>> 7)  When you get into Windows there might appear three message boxes. One
>> saying that the pc has to be restarted. A second one saying that drive D
>> has to be formatted. And the third one saying something about a private
>> drive. Just click on "OK". Then Windows will close immediately and restart.
>> Afterwards the terminal should write that the installation was completed
>> successfully.
>>  When Windows start up again you probably do not have a functioning
>> internet connection.
>>
>>
> When I start Windows again I get a green point on the state column of
> Qubes Manager, which is encouraging, but no GUI whatsoever appears, even if
> the Windows screen appeared and restarted many times during the
> installation process.
>

qvm-sync-appmenus   fixed 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qAZVJ9u1V6%2B_H0oHfV4grj93QfbRiDqwG3P4KKy3M%2BSiw%40mail.gmail.com.

Re: [qubes-users] How to setup Win10 HVM ?

[Franz]

On Sun, Mar 15, 2020 at 8:15 AM 'M' via qubes-users <
qubes-users@googlegroups.com> wrote:

> How to setup a Win 10 HVM according to this page: 
> https://github.com/elliotkillick/qvm-create-windows-qube
> ?
>
> 
>
>
> See below for my detailed description on how to use this method:
>
> 1)  Open your Firefox browser in a VM - for example in the untrusted VM.
>
> 2)  To save the install.sh script file:  Open this page:
> https://raw.githubusercontent.com/elliotkillick/qvm-create-windows-qube/master/install.sh
> and save it as install.sh
>
> 3)  To copy the file to dom0: Open the dom0 terminal and execute this
> command:  qvm-run -p --filter-escape-chars --no-color-output untrusted
> "cat '/home/user/Downloads/install.sh'" > install.sh
>
> 4)  To check that the file is copied to dom0: Execute this command in the
> dom0 terminal: ls
>
> 5)  To get Qubes OS to execute the script in the "install.sh" file:
> Execute this command in the dom0 terminal: chmod +x install.sh &&
> ./install.sh
>
> 6)  Download the version of Windows 10 you want to use to the
> "windows-mgmt" VM.
>  You can execute the script in the file "download-windows.sh , but it
> might not work - I couldn't make it work. In that case, do the following:
>
>  6a)  Open the “Qube Settings” for the domain “windows-mgmt”. Under
> “Network”, choose the “default” one and click on “Apply”.
>
>  6b)  Open the domains Firefox browser and search the web for “how to
> download windows 10”.
> One of the first results is a link to a Microsoft webpage from
> which it is possible to download the file in the local language.
> The file gets downloaded to the download folder in the domain.
>
>  6c)  Open the “Qube Settings” for the domain “windows-mgmt”. Under
> “Network”, choose “(none)” and click on “Apply”.
>
>  6d)  Move or copy the downloaded Win10 ISO-file to this destination:
> /Documents/qvm-create-windows-qube/windows-media/isos
>
>  6e)  Open the terminal in dom0 and execute the following script
> (remember to write the name of the ISO-file you downloaded in step 6b
> instead of “filename”): ./qvm-create-windows-qube.sh -n sys-whonix -oyw
> -i filename.iso -a win10x64-pro.xml Win10
> Info: "Win10" will be the name of the domain.
> Do not close the terminal before it says the installation was
> complete (successfully) !  Let the terminal do the job, it restarts the
> qube and so on when it is necessary.
>
> 7)  When you get into Windows there might appear three message boxes. One
> saying that the pc has to be restarted. A second one saying that drive D
> has to be formatted. And the third one saying something about a private
> drive. Just click on "OK". Then Windows will close immediately and restart.
> Afterwards the terminal should write that the installation was completed
> successfully.
>  When Windows start up again you probably do not have a functioning
> internet connection.
>
>
When I start Windows again I get a green point on the state column of Qubes
Manager, which is encouraging, but no GUI whatsoever appears, even if the
Windows screen appeared and restarted many times during the installation
process.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAPzH-qD3NmSBH-z1d93ftJPwsf3R_zsCtYetkHADN6ZgSzuYaA%40mail.gmail.com.

[qubes-users] Re: Using 2 monitors in full screen mode with one application spanning both monitors

[redpollwan]

On Monday, 23 March 2020 03:02:42 UTC+11, Robin Green wrote:
>
> I am running VMWare Horizon in a trusted VM in order to WFH. It is able to 
> detect and use both monitor geometries for what you might call a 
> "double-full screen mode" - however, even though I have enabled full-screen 
> mode for this trusted AppVM in /etc/qubes/guid.conf on dom0, Qubes 
> unfortunately does not recognise what it's doing as "full-screen" and 
> retains the title bar over the virtual window (which spans both screens) 
> and over the Windows Remote Desktop widget (which appears as a separate 
> window fully obscured by the Qubes window title bar, rather than a widget). 
>
> Yes, I am running Remote Desktop, on a remote computer, that I am 
> connecting to with VMWare Horizon, to connect to yet *another* computer! 
> So many levels of desktop virtualisation here, hehe
>
> If I right-click on the Qubes window title bar and choose Full screen, it 
> of course goes to full screen on only the first display, and no second 
> virtual monitor on the remote computer is accessible to me. If I leave it 
> like it is, I can't see what's at the bottom of any maximised windows on 
> the remote machine - and since I like to maximise all of my windows, this 
> is pretty much unusable for me.
>
> Gonna have to reboot my local machine into Windows for now so that I can 
> use both screens with VMWare Horizon and Remote Desktop, but I would like 
> to figure out a way to get this to work... that doesn't involve manually 
> resizing all the windows on the remote computer!
>

 You might have already tried but in dom0 try fn/f8 (or whatever your pc 
has for display) may give you some more options than going via 
system>display.  This worked for me when I trying to extend the display 
rather than mirror.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/d1da031b-8162-4d0d-b289-716d0f1b3909%40googlegroups.com.

Re: [qubes-users] how to start with QubesOS

[redpollwan]

On Friday, 20 March 2020 20:36:47 UTC+11, Peter Funk wrote:
>
> Hello all, 
>
> agroz...@cegepgim.ca  wrote yesterday, 19.03.2020 at 11:11 
> CET: 
> > On Thursday, 19 March 2020 13:38:11 UTC-4, Sven Semmler wrote: 
> > > I think you'd be best served going onto youtube and searching for 
> Qubes 
> > > demos and overview presentations/talks. 
> ... 
> > Thank you for thr prompt reply Sven, 
> > 
> > Could you send links to some particular ones, please? 
>
> I would start by watching this one: 
> https://www.youtube.com/watch?v=Aghj8MyDF4I 
> It is less than six months old by now. 
> And this one is also interesting: 
> https://www.youtube.com/watch?v=sbN5Bz3v-uA 
>
> Best regards or as we say here in Germany: Liebe Grüße, Peter Funk 
> -- 
> Peter Funk ✉:Oldenburger Str.86, 2 Ganderkesee, Germany; 
> :+49-179-640-8878 
> A: Because most humans read top down. 
> Q: Why should I write my answer below the asked question? 
>

You're very welcome for the links.

Noted.

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2b355393-2f5d-4b22-8f19-c0678eeaa240%40googlegroups.com.

Re: [qubes-users] No Match for argument qubes-template-whonix-ws-15-4.0.1-201910102356.noarch ?

[Chris Laprise]

On 3/20/20 10:08 PM, Stumpy wrote:
I'm trying to reinstall the whonix ws template but while seems to find 
it it then says there is no match?



[zack@dom0 ~]$ sudo qubes-dom0-update --action=reinstall 
qubes-template-whonix-ws-15
WARNING: Replacing a template will erase all files in template's /home 
and /rw !

Template VM halted
Using sys-whonix as UpdateVM to download updates for Dom0; this may take 
some time...

No Match for argument qubes-template-whonix-ws-15-4.0.1-201910102356.noarch
Nothing to download


That means you have an older template package that was removed from the 
Qubes servers, so it can't be reinstalled as the same version.


When that happens, you can use '--action=upgrade' instead and it should 
grab the latest available version.


https://www.qubes-os.org/doc/reinstall-template/

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/90145bbb-feff-61a8-9cbe-65fc210da85a%40posteo.net.

Re: [qubes-users] How can I recover my Qube'sVM if I cannot boot anymore ?

[Chris Laprise]

On 3/22/20 7:11 AM, dhorf-hfref.4a288...@hashmail.org wrote:

On Sun, Mar 22, 2020 at 11:57:38AM +0100, haaber wrote:

Assuming you didn't make backups before the crash: You need to have a
running Qubes system to backup VMs the normal way.

Does that mean Chris, that in case of a disaster, there is no way to
backup your data "by hand" (booting a live linux, opening the luks ..)
because of a "thin pool" mess? That sounds in first hand like a strong
argument against the use of thin pools! As you know a lot about thin
pools, could you please comment on that, Chris?  thx, Bernhard


thin pools are plain linux tech, nothing qubes specific.
and you can back them up in whatever way you want, from whatever
distro/system you want.
or not back them up at all, and simply attach the disk to some
other system.

it is not trivial to use the _qubes_ backup tooling outside
of a qubes system.
but besides that, they are just blockdevices with filesystems inside.


Right. Another way to phrase my advice is that the "vm*-private" volumes 
are simply disk images and contain all the data for regular appVMs. For 
templates and standalone VMs, the "vm*-root" volumes are also a part of 
the VM's data. Backing these up can be pretty simple, since they are 
block devices accessible from /dev/qubes_dom0 and you can use 'dd' or 
'dd | gzip' or whatever. You could even use my backup tool (wyng).


The perceived "mess" is actually rather organized, and has nothing to do 
with LVM thin pools. If you had installed Qubes with non-LVM storage, 
you would still have separate disk image files for each VM. You can make 
the volume list more readable with 'lvs | grep private' to filter out 
non-private volumes.


Of course there is Qubes-specific metadata (i.e. the Settings dialog for 
your VM) in /var/lib/qubes/qubes.xml and maybe firewall.xml files in the 
subdirs there. But these should only matter if you changed VM settings 
in the Settings dialog or via 'qvm-prefs' or 'qvm-firewall' commands, 
and even then many settings like 'Memory' and 'Applications' are trivial.


Finally... It should be possible to write a recovery script for this 
situation, which presents the user with a list of VMs to recover and 
optionally allows you to recover the contents of /var/lib/qubes.


--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/ab71a53a-f7ab-d4d3-7138-349d5d03bba3%40posteo.net.

[qubes-users] Using 2 monitors in full screen mode with one application spanning both monitors

[Robin Green]

I am running VMWare Horizon in a trusted VM in order to WFH. It is able to 
detect and use both monitor geometries for what you might call a 
"double-full screen mode" - however, even though I have enabled full-screen 
mode for this trusted AppVM in /etc/qubes/guid.conf on dom0, Qubes 
unfortunately does not recognise what it's doing as "full-screen" and 
retains the title bar over the virtual window (which spans both screens) 
and over the Windows Remote Desktop widget (which appears as a separate 
window fully obscured by the Qubes window title bar, rather than a widget). 

Yes, I am running Remote Desktop, on a remote computer, that I am 
connecting to with VMWare Horizon, to connect to yet *another* computer! So 
many levels of desktop virtualisation here, hehe

If I right-click on the Qubes window title bar and choose Full screen, it 
of course goes to full screen on only the first display, and no second 
virtual monitor on the remote computer is accessible to me. If I leave it 
like it is, I can't see what's at the bottom of any maximised windows on 
the remote machine - and since I like to maximise all of my windows, this 
is pretty much unusable for me.

Gonna have to reboot my local machine into Windows for now so that I can 
use both screens with VMWare Horizon and Remote Desktop, but I would like 
to figure out a way to get this to work... that doesn't involve manually 
resizing all the windows on the remote 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/a661398e-df6a-4270-ad43-d0017f5904bf%40googlegroups.com.

Re: [qubes-users] Re: Fedora-31 template

[dhorf-hfref . 4a288f10]

On Sun, Mar 22, 2020 at 05:07:44AM -0700, max via qubes-users wrote:
> [max@dom0 ~]$ sudo qubes-dom0-update 
> --enablerepo=qubes-dom0-current-testing qubes-template-fedora-31

wrong repo.

try with --enablerepo=qubes-templates-itl-testing


-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200322121354.GC8973%40priv-mua.

[qubes-users] Re: Fedora-31 template

[max via qubes-users]

søndag den 15. marts 2020 kl. 16.04.00 UTC+1 skrev Lorenzo Lamas:
>
> A Fedora 31 template is now available in the testing repo for Qubes 4.0.
>

I tried:

[max@dom0 ~]$ sudo qubes-dom0-update 
--enablerepo=qubes-dom0-current-testing qubes-template-fedora-31
Using sys-firewall as UpdateVM to download updates for Dom0; this may take 
some time...
Last metadata expiration check: 2:24:09 ago on Sun Mar 22 08:07:23 2020.
No match for argument: qubes-template-fedora-31
Error: Unable to find a match: qubes-template-fedora-31
[max@dom0 ~]$ 

Last it seems I did something like sudo dnf install 
qubes-template-fedora-30, but I don't remember.

Any clues?

Sincerely
Max

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/bb78cf04-8734-489f-8df5-dda2b2f12394%40googlegroups.com.

Re: [qubes-users] Tor on Whonix: A couple of questions

[Anil]

> the location, as far as I can understand. And they try to guess the
> location using all the tools and data at their disposal, including
> machine learning, constrained perhaps by my privacy setting
> (hopefully). If you are signed in, it will work in one way. If you are
> not signed in (like in Tor Browser), it will work differently.

I am sure Qubes OS and Tor developers know this.That is why Tor starts
with a particular window size and at random location on the screen and
it warns against changing the window size, particular to full screen.

Regards,

Anil Kumar Singh

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAPfsu-0%3DbdLT%3DBiEg4Nui5uaRxygexLCYT4dH2RCdtwgM18RA%40mail.gmail.com.

Re: [qubes-users] How can I recover my Qube'sVM if I cannot boot anymore ?

[dhorf-hfref . 4a288f10]

On Sun, Mar 22, 2020 at 11:57:38AM +0100, haaber wrote:
> > Assuming you didn't make backups before the crash: You need to have a
> > running Qubes system to backup VMs the normal way.
> Does that mean Chris, that in case of a disaster, there is no way to
> backup your data "by hand" (booting a live linux, opening the luks ..)
> because of a "thin pool" mess? That sounds in first hand like a strong
> argument against the use of thin pools! As you know a lot about thin
> pools, could you please comment on that, Chris?  thx, Bernhard

thin pools are plain linux tech, nothing qubes specific.
and you can back them up in whatever way you want, from whatever
distro/system you want.
or not back them up at all, and simply attach the disk to some
other system.

it is not trivial to use the _qubes_ backup tooling outside
of a qubes system.
but besides that, they are just blockdevices with filesystems inside.



-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2020032231.GB8973%40priv-mua.

Re: [qubes-users] Tor on Whonix: A couple of questions

[Anil]

> I have attached the screenshots about the second question, of
> corrupted context menu.

The first screenshot is when I detach the tab from the window where
all the other tabs are, and second is when the tab is in the original
window.

Regards,

अनिल एकलव्य
(Anil Eklavya)

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/CAAPfsu_U%3DX-_c-vBPp1QEt8wsfsNr2poNeqv60f9V8fnQtXgdQ%40mail.gmail.com.

Re: [qubes-users] How can I recover my Qube'sVM if I cannot boot anymore ?

[haaber]

[Initial question: snipped ]

I cannot boot on Qubes anymore but I can access the file system. When
I mount my qubes partition, it give me a huge mess of small 2g
partition and bigger ones.


[Chris' answer -- snipped ]


Assuming you didn't make backups before the crash: You need to have a
running Qubes system to backup VMs the normal way.


Does that mean Chris, that in case of a disaster, there is no way to
backup your data "by hand" (booting a live linux, opening the luks ..)
because of a "thin pool" mess? That sounds in first hand like a strong
argument against the use of thin pools! As you know a lot about thin
pools, could you please comment on that, Chris?  thx, Bernhard

--
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/471d3179-5ddc-c7a8-bfbf-aa5b0c43c29d%40web.de.

Re: [qubes-users] Newbie question on disposable VMs?

[viktor . ransmayr]

Hello Mike,

Am Samstag, 21. März 2020 23:05:03 UTC+1 schrieb Mike Keehan:
>
> On 3/21/20 6:25 PM, viktor@gmail.com  wrote: 
> > Am Samstag, 21. März 2020 18:14:51 UTC+1 schrieb viktor@gmail.com: 
> > 
> > Am Samstag, 21. März 2020 14:39:18 UTC+1 schrieb Stumpy: 
> > 
> > On 2020-03-21 04:26, Viktor Ransmayr wrote: 
> >  > Am Fr., 20. März 2020 um 21:30 Uhr schrieb <
> viktor@gmail.com 
> >  > >: 
> >  > 
> > ... 
> >  > 
> >  > Additional info & update on question: 
> >  > 
> >  > I'm running Qubes OS 4.0.3 - and - was starting a disposable 
> >  > 'fedora-29-dvm' yesterday & by default the terminal offered 
> > is an Xterm. 
> >  > 
> >  > This morning it became clear to me, that I should use the 
> > same setup, 
> >  > that I had used previously with the persistant VMs, i.e. 
> > where by 
> >  > default a standard (Gnome?) terminal is offered ... 
> >  > 
> >  > I updated the Qube settings for 'fedora-29-dvm', increased 
> > the memory 
> >  > size & enabled network access. 
> >  > 
> >  > However the terminal only shows up temporarily - and - the 
> > disposable VM 
> >  > is halted again ... 
> > 
> > Sorry, I havent a clue on that one, thought i dont think mem is 
> > an issue 
> > as the default is 4gb which should be plenty AFAIR. 
> > 
> > I have no clue if this would fix things but since you are on 29 
> > and 30 
> > has been out you might upgrade to fed 30 which might resolve the 
> > issue 
> > you are having. 
> > 
> > I'll take your advice, upgrade to F30 - and - will report back here. 
> > 
> > I renamed "fedora-29-dvm", changed template to "fedora-30", kept 
> > networking to "sys-firewall" as well as max memory to 8 GB - plus - I 
> > exchanged "xterm" with "terminal" & tried again. 
> > 
> > However the behaviour did not change. 
> > 
> > Is this information sufficient to file a bug report - or - what else 
> > should I provide? 
> > 
> > With kind regards, 
> > 
> > VR 
> > 
> "Terminal" not showing up in a template has been answered on this list 
> before.  Something to do with the way gnome starts their program, I think. 
>

Thanks a lot for your F/B. - This is the link to the qubes-user msg 
providing the details:

* https://groups.google.com/d/msg/qubes-users/keKZRDawupQ/HYM3m4xmAwAJ

No further question ( for the moment ;-)

With kind regards,

VR

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/b60c0124-8a0f-4225-a61b-34041c0dcb88%40googlegroups.com.