[qubes-users] Compositing in AppVMs

[jimmy . dack . 68]

I really like transparent Terminal windows and would like to use them in 
AppVMs. They work on the dom0 Terminal, no sweat. But when I try to set the 
Background to transparent in the Terminal Preferences in any Fedora-24 AppVM I 
get: "Sorry, your Window Manager does not support compositing: Opacity setting 
is not available."

I'm using xfce-terminal in my AppVMs, same as dom0. The version numbers are 
different, but both offer the option of transparent backgrounds. It just 
doesn't seem to work in the AppVMs like it does in dom0.

I have Enable Display Compositing checked in the Window Maanger Tweaks for 
dom0. Is this supposed to affect AppVMs, too? Or do I need to set that within 
the AppVMs themselves? If the latter, I'm not sure how to get Windows Manager 
Tweaks running in AppVMs; maybe I'm blind, but I just don't find it anywhere 
and don't seem to be figuring out the right package name to run it from the CLI.

Any information, ideas, solutions about this would be most appreciated. :-)

-- 
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/469c107d-4f33-4a69-8962-22cb1fe3041f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Programs Not Showing in Available Applications List

[jimmy . dack . 68]

On Monday, February 27, 2017 at 12:13:15 PM UTC-5, Grzesiek Chodzicki wrote:
> run qvm-sync-appmenus in dom0

Thanks so much for the reply! You are of course exactly correct, that works 
perfectly. It is in the Documentation, too, under Common Tasks--I had been 
looking in the Configuration and Troubleshooting areas. Guess my intuition 
wasn't that this would be a Common Task. Still learning. :-)

-- 
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/93fdde4c-b9cb-4554-a6ec-9d70a76e8044%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] HCL - HP EliteBook 8560p

[Brendon Green]

S3 Sleep sometimes takes a few minutes to activate; crashes upon wakeup if
any USB3 storage devices are mounted.

All integrated and external PS/2 devices work and are independently
configurable.
The 2-button PS/2 pointing stick is identified as a "PS/2 Generic Mouse",
and works best if libinput is installed and reconfigured to provide
scrolling while the right-button is held; I cannot get middle-button
emulation working on the pointing stick, despite using this configuration
successfully with Debian 9.
The PS/2 Synaptics touchpad defaults to middle-button emulation and fully
supports 2-finger gestures.

Integrated 3D accelerometer could be useful for detecting and defeating
"snatch-and-run" attack.

Integrated fingerprint scanner lacks driver support for Linux.

CPU and GPU are both (theoretically) upgradable.

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


Qubes-HCL-Hewlett_Packard-HP_EliteBook_8560p-20170304-152235.yml
Description: application/yaml


Qubes-HCL-Hewlett_Packard-HP_EliteBook_8560p-20170304-155538.cpio.gz
Description: application/targz

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

[Ed Welch]

I figured out how to install an older version of qubes-windows-tools

sudo dnf remove qubes-windows-tools

sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing 
qubes-windows-tools-3.2.1-3.x86_64


From the testing repo: 
http://yum.qubes-os.org/r3.2/current-testing/dom0/fc23/rpm/


I was able to see the different versions so I chose the most recent 
prior to 3.2.2-3, which was 3.2.1-3.


And I have to say, this was a whole different ballgame, everything with 
this version went really smoothly, I'm up and running now with an 
updated win 7 instance, gui comes up fine, never even needed debug mode.


I'm not sure if Ted and I are just among the first to do a clean install 
with 3.2.1-3 or if there is something about our systems giving us these 
issues.


Anyone please let me know how I can help (filing issues in github, logs, 
etc) but for now I'm happy with how the older version is working.


Ed

On 03/03/2017 11:45 AM, Ted Brenner wrote:

For what it's worth, I'm having the exact same issues.

On Fri, Mar 3, 2017 at 9:13 AM, Ed Welch > wrote:


Hey everyone, new to qubes, love it!

Getting going with linux I found pretty straight forward, no issues.

Trying to get a Windows 7 HVM template created, not going so well.

Thought I would post some of the issues I've had for posterity and
also see if I can get some help.


If you are like me and don't generally read long winded posts,
please at least scroll to my QUESTION at the bottom :)


Most of the instructions tell you to create a VM, however, none of
them tell you to increase the default VM specs.  For win 7 64 it
seems you want to increase the RAM to 4096MB and primary partition
to 40960MB (40G) I know for a fact 20G is not enough to update
windows 7 sp1 to latest.

You'll want to do this before anything else because it's more
difficult to do after you get started


Then I ran into the xen/cirrus video driver issue which causes
windows to freeze on the startup screen, found this issue with
workaround: https://github.com/QubesOS/qubes-issues/issues/2488


This workaround does the trick, but I think it's important to note
a few additional steps, after the last setup reboot and BEFORE YOU
SHUTDOWN windows and try to install the windows guest additions.

MAKE SURE to enable login without password through the netplwiz
tool, it seemed like this was the crucial step in avoiding this
issue:
https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ



Also, users mentioned in that thread the importance of adding more
RAM, however, for me it seemed that enabling login without
password was the step that avoided putting your VM in a totally
unrecoverable BSOD loop.

Following the wiki instructions, I then installed the windows
tools from the qubes-dom0-current-testing repo (and also updated
the qrexec_timeout to 300 seconds) then switching back to the
modified instructions for working around the cirrus/xen bug I was
able to boot into windows and install the windows tools.


This is where I hit my next big stumbling point, during the
installation the PV drivers prompt you to reboot.  DO NOT REBOOT
until the installation finishes, I did eventually see on this page
'Xen PV driver components may display a message box asking for
reboot during installation – it’s safe to ignore them and defer
the reboot.'

Really this needs to be promoted to
https://www.qubes-os.org/doc/windows-appvms/
 IMO and in big bold
letters DO NOT REBOOT until the installation is completed kind of
thing.  If you reboot before it finishes this is really
unrecoverable and it's easier to just blow away the vm and start
again...


Ok, so now we get to where I'm stuck, my vm is installed,
qubes-windows-tools 3.2.2-3 is installed, however as soon as I
start the thing, it boots and the display immediately goes away,
found this issue:
https://github.com/QubesOS/qubes-issues/issues/1896
 which
matches the behavior I'm seeing, however, this was fixed some time
ago, but not totally sure when it was released??


My second, issue, which may actually be causing the first, seems
to best be described in this thread:
https://groups.google.com/d/topic/qubes-users/4OgwojFK-sI/discussion


Specifically I'm having the issue in the last comment, the only
way I can get any UI is if I boot with --debug, and when I do, I
often see that error linked: 'The GUI agent that runs in the VM
'win7' implements 

[qubes-users] Re: Time sync failed

[raahelps]

On Wednesday, March 1, 2017 at 11:03:01 AM UTC-5, Richard wrote:
> My clock is not syncing and I can't figure out what the issue is.  Any 
> assistance would be greatly appreciated.
> 
> I'm running Qubes 3.2 (R3.2)
> 
> From Dom0:
> $ qubes-pref
> clockvm   : sys-net
> default-fw-netvm  : sys-net
> default-kernel: 4.4.38-11
> default-netvm : sys-firewall
> 
> $ qvm-sync-clock --verbose
> --> Waiting for network for ClockVM.
> Time sync failed! - Exiting
> 
> $ timedatectl status
> Failed to query server: Input/output error

any special firewall settings on the sys-net vm?  What about the router or 
gateway connection?

-- 
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/c4eecf68-3742-4d02-8a88-4d3ae3f7c00d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Mssing WiFi capabilities Qubes OS R3.2

[raahelps]

On Friday, March 3, 2017 at 12:25:25 AM UTC-5, hela...@gmail.com wrote:
> Hi,
> 
> I just installed Qubes R3.2 on a Lenovo Ideapad Yoga i7 with a Realtek 
> RTL8732 NIC. I can't see the NIC under  sys-netvm and hence can't change it 
> to a managed device. dmesg shows that it finds it, but the kernel module for 
> the NIC does not seem loaded. In the menu I can only see 'Device not managed' 
> for networking as would be expected.
> 
> I have read a few posts about Realtek cards being troublesome to use under 
> Qubes.
> 
> Unfortunately I'm not by my Qubes laptop writing this so I cant' post any 
> outputs from the machine.
> 
> Anyone have any ideas how to proceed ?
> 
> Thanks

Might want to check what driver module needed for fedora. or Maybe you need to 
use a diff kernel

-- 
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/8b08a7bc-2f51-441a-91f8-d1274866b9ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: fedora-24 update error: nothing provides ostree-libs(x86-64) >= 2016.14 needed by flatpak-0.8.3-3.fc24.x86_64

[raahelps]

On Friday, March 3, 2017 at 6:38:24 PM UTC-5, raah...@gmail.com wrote:
> On Friday, March 3, 2017 at 9:40:20 AM UTC-5, mitte...@digitrace.de wrote:
> > Hello fellow Qubes users,
> > 
> > If I execute update of the fedora-24 template via the Qubes VM manager,
> > it aborts with the error
> > 
> > nothing provides ostree-libs(x86-64) >= 2016.14 needed by
> > flatpak-0.8.3-3.fc24.x86_64
> > 
> > If I use
> > sudo dnf upgrade
> > from the terminal within fedora-24 the command is executed, but later
> > executions list the problem with flatpack (broken dependencies)
> > 
> > of course I can remove flatpack, but I don't know whether I may need it?!
> > 
> > thanks
> 
> I removed it haven't noticed any problems.  But I also wonder what it is.

Hopefully removing it did not lessen my security?

-- 
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/2beae5b2-0435-4eb8-bc90-9e36f7db124b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: fedora-24 update error: nothing provides ostree-libs(x86-64) >= 2016.14 needed by flatpak-0.8.3-3.fc24.x86_64

[raahelps]

On Friday, March 3, 2017 at 9:40:20 AM UTC-5, mitte...@digitrace.de wrote:
> Hello fellow Qubes users,
> 
> If I execute update of the fedora-24 template via the Qubes VM manager,
> it aborts with the error
> 
> nothing provides ostree-libs(x86-64) >= 2016.14 needed by
> flatpak-0.8.3-3.fc24.x86_64
> 
> If I use
> sudo dnf upgrade
> from the terminal within fedora-24 the command is executed, but later
> executions list the problem with flatpack (broken dependencies)
> 
> of course I can remove flatpack, but I don't know whether I may need it?!
> 
> thanks

I removed it haven't noticed any problems.  But I also wonder what it is.

-- 
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/33686c18-1c6b-497d-a06b-c854f5ee96ff%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Fedora-24 Template Corrupted?

[raahelps]

On Friday, March 3, 2017 at 10:56:26 AM UTC-5, qub...@tutanota.com wrote:
> Fedora-24 template shows updates available. However updates terminal returns 
> error [cannot copy/past results]. I then open gnome terminal and get the 
> following:
> [user@fedora-24 ~]$ sudo dnf update
> Last metadata expiration check: 2:23:51 ago on Fri Mar  3  2017.
> Dependencies resolved.
> 
>  Package   Arch  Version   Repository  
> Size
> 
> Skipping packages with broken dependencies:
>  gnome-software    x86_64    3.22.5-1.fc24 updates    9.3 
> M
> 
> Transaction Summary
> 
> Skip  1 Package
> 
> Nothing to do.
> Sending application list and icons to dom0
> The above output from gnome terminal is completely different from the updates 
> terminal - which refers to skipping "flatpak" package.
> To resolve I reloaded Qubes OS 3.2 but got same errors.
> Any thoughts?
> 
> 
> --
> 
> 
> Securely sent with Tutanota. Claim your encrypted mailbox today!
> 
> 
> https://tutanota.com

I had the same exact issue. And yes you only get the message when running the 
update from the qubes-manager, which halts the update.
If updating manually from a terminal it will just skip that package and proceed 
with rest of the updates.

What I did was sudo dnf autoremove and then sudo dnf remove flatpak and just 
hit y to remove dependencies that were listed.  I haven't noticed any problems 
running my vms after doing so, but I also wonder what it is.

-- 
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/93482035-dab8-4bcd-a26b-dd3a75ca6378%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] salt, getting started (to disable CAPS LOCK and configure basic tools everywhere)

[Holger Levsen]

Hi,

so I've read qubes-doc.git/configuration/salt.md and wonder, /srv/salt is
installed by the qubes packages and the document says the Qubes salt API is
supposed to change between minor release - so where am I supposed to put
*my* salt config?

Also what best practices / tools exist to maintain this in git in a VM and
then copy it over to dom0?

My actual first "pressing" usecase to use Salt is to disable CAPS LOCK
everywhere… :-)

My second use case would be to deploy the same customisations to basic
tools (eg enable syntax highlighting in vim) everywhere…

Disclaimer: I indeed have basically no clue about salt, not read the upstream
docs yet, just the above document…


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


signature.asc
Description: Digital signature

Re: [qubes-users] Feedback request: Incremental file-based backup PoC

[Holger Levsen]

On Fri, Mar 03, 2017 at 12:42:56PM -0800, Vít Šesták wrote:
> Well, I don't see any problem with restore. This is roughly what dom0 does 
> (or initiates):

Vít, please design and *test* your restore. Nobody wants backup, everybody
wants restore.


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


signature.asc
Description: Digital signature

Re: [qubes-users] Feedback request: Incremental file-based backup PoC

[Vít Šesták]

Well, I don't see any problem with restore. This is roughly what dom0 does (or 
initiates):

1. create a new VM (with default or explicitly provided parameters and no netvm 
– as I have mentioned, I don't backup anything but files and VM name)
2. start a new DVM (we have chosen to trust the DVM…)
3. attach the private.img to that DVM and mount it
4. add permissions for the DVM (BackupStorageVM allows the DVM accessing only 
the specified subfolder of backup) – well, it currently gets RW access, which 
is suboptimal (R access should be enough), but I don't se a real threat here.
5. start the backup script in the DVM (The script deletes everything but 
lost+found on the attached FS and starts restore.)

Do you think I miss something important?

Ad DVMs in QubesOS 4: Even cooler than I thought. My idea was to use the same 
DVM (maybe I am influenced with the current Qubes) in order to be sure we have 
Duplicity (or another software) of the version we want. But you have a point on 
the trust.

This is even more interesting and it could be an important design shift. Maybe 
a template could know how to backup related AppVM's data. This is not a minor 
change, as it would allow using different backup backends for different VMs. 
And it is not so trivial, because we probably would want to use just one 
storage backend for all backups. Duplicity has a very simple API for backends 
(you have to implement just get/put/list/delete, it does not even have 
subfolders), but I am not sure about other backends.

Anyway, the storage backends are going to be a challenge, at least a bit. With 
Duplicity not supporting subfolders, I rely on some features of the storage 
backends (subfolder-compliant URI scheme and automatic subfolder creation). 
This works with file backend (which is fortunately somewhat universal thanks to 
various fuse-based filesystems). However, with rsync, I had to implement a hack 
that violates encapsulation. (See 
https://github.com/v6ak/qubes-incremental-backup-poc/commit/83a285307042eb9363b5ed77e9701dcfa7ab3514
 .) And I currently have no idea about other backends. Maybe the storage 
backend in BackupStorageVM can be quite generic (i.e., agnostic to backup 
backend), but maybe we can be badly suprised…

TemplateVMs: I haven't published my idea, so I'll do it now: Backup list of 
explicitly installed packages and config files. I know, this is going to be 
package-manager-specific. There is not much a reason for storing backup of 
packages I can download.

Ad StandaloneVMs: I agree it is tricky here. Currently, I backup/restore just 
private.img of AppVM. We definitely can't perform fully OS-agnostic file-based 
backup without cooperation of the OS (that is not yet installed). There are 
several ways how to handle it:

a. Backup just private.img. I would be usually OK with this, because my 
StandaloneVMs don't have a large lists of packages, they are usually rather 
default installation with few additional packages installed.
b. Handle root.img like TemplateVM and private.img like template-based VM.
c. Handle root.img by block-based backup and private.img by file-based backup.

Ad attributes: Good point. I honestly don't know what Duplicity supports. I am 
sure it has some basic support, so I concluded it is good enough for me, but 
maybe I should review its limitations again.

Ad Windows: currently, it can theoretically mount private.img provided that 
there is ntfs module etc., so it should be possible to perform backup. I am not 
sure about attributes supported. The restore process for Windows will currently 
not work out-of-box without any further tuning.

Thank you for your notes. Maybe we should follow Pareto rule. Maybe it should 
not be a goal to use file-based backup on everything. We can use file-based 
backup in most cases and use the current block-based backup in other cases. 
Especially when we integrate both backup types together – we could consider the 
current block-based backup as just another backup backend.

My priorities are roughly:
1. Have good file-based backup and restore process for Linux template-based 
AppVMs.
2. Have similar process for Debian/Fedora TemplateVMs.
3. Have block-based backup backend.
4. Have good support for StandaloneVMs, Windows and other OSes.

I believe this corresponds not only to my needs, but also to needs of many 
others. I am generally not against implementing something that has lower 
priority for me, especially if there is a pull request.  ☺

Regards,
Vít Šesták 'v6ak'

-- 
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/d6da74af-f17c-4ca4-bcac-30ae1165cdc0%40googlegroups.com.
For more options, visit 

Re: [qubes-users] removed qubes-core-dom0 by accident

[sofoobard]

hurray! rpms are in /mnt/install... but how do I deal with dependencies? is 
there a way to invoke yum or dnf during 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/e352a739-cf85-402a-b74a-025479adebb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] removed qubes-core-dom0 by accident

[sofoobard]

My apologies for the bother, Marek.

Where is PATH_TO_PACKAGE once in a recovery shell?

(finally got a good sig on 4th download of iso)

thanks so much
sf

-- 
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/7817bcf5-395e-4416-9988-f233d35697df%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] RE: Win7, qvm-copy-to-vm, QubesIncoming location?

[Martin L . Fällman]

> 
> Does the issue still occur after You change the default Windows user in
> Qubes settings? qvm-prefs -s windows default_user admin ?

Just tried it, yep. This is strange!

//MLF.

-- 
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/ed79bafb4a5b4810ae3cadbbcf535538%40Exchange01.domain.local.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: Win7, qvm-copy-to-vm, QubesIncoming location?

[Grzesiek Chodzicki]

W dniu piątek, 3 marca 2017 13:31:40 UTC+1 użytkownik Martin L. Fällman napisał:
> > -Original Message-
> > From: Foppe de Haan [mailto:0spinbo...@gmail.com]
> > Sent: den 3 mars 2017 11:31
> > To: qubes-users 
> > Cc: Martin L. Fällman 
> > Subject: Re: Win7, qvm-copy-to-vm, QubesIncoming location?
> > 
> > it'll be in a subfolder of the documents root.
> 
> This is the problem: the files are nowhere to be found. Somewhere they do get 
> written because the file copy mechanism identifies that there's already an 
> object there by the same name and it shouldn't be overwritten, but there's no 
> way for me to find it. I did a proper clean re-install of the Windows tools, 
> and set the default user for my W7 HVM to the correct name (the one I log in 
> as) in qvm-prefs, but the problem persists.
> 
> Wherever the files I send to the VM gets written, I can't find them from 
> inside the VM, and they persist between restarts. Could it be that they're 
> written to private.img but somewhere Windows doesn't consider "real" for 
> whatever reason? Tried reading the source too but I'm not a C programmer and 
> can't make heads or tails of what's going on.
> 
> Best,
> //MLF.

Does the issue still occur after You change the default Windows user in Qubes 
settings? qvm-prefs -s windows default_user admin ?

-- 
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/854b5a30-8771-4b9d-936b-11a8c40fb3bb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] removed qubes-core-dom0 by accident

[sofoobard]

Thank you, Marek.

Am I better off using the 3.1 or 3.2 iso? 

(I've tried direct download of both 3.1 iso and 3.2 iso, and the 3.2 torrent, 
but I get a BAD signature error for all three. Also the 3.2 iso was signed 
2016-09-20? Can that be correct?)

thank you
sf

-- 
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/046fda99-9e25-416e-83df-1bafc1f8c11d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

[Ted Brenner]

For what it's worth, I'm having the exact same issues.

On Fri, Mar 3, 2017 at 9:13 AM, Ed Welch  wrote:

> Hey everyone, new to qubes, love it!
>
> Getting going with linux I found pretty straight forward, no issues.
>
> Trying to get a Windows 7 HVM template created, not going so well.
>
> Thought I would post some of the issues I've had for posterity and also
> see if I can get some help.
>
>
> If you are like me and don't generally read long winded posts, please at
> least scroll to my QUESTION at the bottom :)
>
>
> Most of the instructions tell you to create a VM, however, none of them
> tell you to increase the default VM specs.  For win 7 64 it seems you want
> to increase the RAM to 4096MB and primary partition to 40960MB (40G) I know
> for a fact 20G is not enough to update windows 7 sp1 to latest.
>
> You'll want to do this before anything else because it's more difficult to
> do after you get started
>
>
> Then I ran into the xen/cirrus video driver issue which causes windows to
> freeze on the startup screen, found this issue with workaround:
> https://github.com/QubesOS/qubes-issues/issues/2488
>
> This workaround does the trick, but I think it's important to note a few
> additional steps, after the last setup reboot and BEFORE YOU SHUTDOWN
> windows and try to install the windows guest additions.
>
> MAKE SURE to enable login without password through the netplwiz tool, it
> seemed like this was the crucial step in avoiding this issue:
> https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ
>
> Also, users mentioned in that thread the importance of adding more RAM,
> however, for me it seemed that enabling login without password was the step
> that avoided putting your VM in a totally unrecoverable BSOD loop.
>
> Following the wiki instructions, I then installed the windows tools from
> the qubes-dom0-current-testing repo (and also updated the qrexec_timeout to
> 300 seconds) then switching back to the modified instructions for working
> around the cirrus/xen bug I was able to boot into windows and install the
> windows tools.
>
>
> This is where I hit my next big stumbling point, during the installation
> the PV drivers prompt you to reboot.  DO NOT REBOOT until the installation
> finishes, I did eventually see on this page 'Xen PV driver components may
> display a message box asking for reboot during installation – it’s safe to
> ignore them and defer the reboot.'
>
> Really this needs to be promoted to https://www.qubes-os.org/doc/w
> indows-appvms/ IMO and in big bold letters DO NOT REBOOT until the
> installation is completed kind of thing.  If you reboot before it finishes
> this is really unrecoverable and it's easier to just blow away the vm and
> start again...
>
>
> Ok, so now we get to where I'm stuck, my vm is installed,
> qubes-windows-tools 3.2.2-3 is installed, however as soon as I start the
> thing, it boots and the display immediately goes away, found this issue:
> https://github.com/QubesOS/qubes-issues/issues/1896  which matches the
> behavior I'm seeing, however, this was fixed some time ago, but not totally
> sure when it was released??
>
>
> My second, issue, which may actually be causing the first, seems to best
> be described in this thread: https://groups.google.com/d/to
> pic/qubes-users/4OgwojFK-sI/discussion
>
> Specifically I'm having the issue in the last comment, the only way I can
> get any UI is if I boot with --debug, and when I do, I often see that error
> linked: 'The GUI agent that runs in the VM 'win7' implements outdated
> protocol (0:0), and must be updated.
>
>
> After reading through that thread, several people were mentioning that
> 3.2.2-3 has seemed to make things less stable.
>
>
> What I would like to do, is install the previous version of
> qubes-windows-tools, but try as I might to manipulate the qubes-dom0-update
> script into doing so I have not been able to do this, I'm not even sure the
> older versions are kept in the repos??
>
> QUESTION:  Is there a way to install a specific version (whatever was
> previous to 3.2.2-3) of qubes windows tools?
>
>
> Thanks!
>
> Ed
>
> --
> 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/ms
> gid/qubes-users/821726de-f5c1-d6a9-b15e-078e1f9cc56d%40edjusted.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Sent from my Desktop

-- 
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 

Re: [qubes-users] do I really need these packages in dom0 :?

[haaber]

> Marek wrote:
> Yes. You can start with 'dnf remove initial-setup-gui' - it will propose
> additional packages not needed anymore. But carefully review that
> list before confirming.

While this is true, it is of no help for a lot of people, myself
included. The following packets are proposed for deletion. 

ModemManager-glib
NetworkManager-wifi
anaconda-gui
anaconda-widgets
enchant
fros
geoclue2
glade-libs
harfbuzz-icu
hunspell
hunspell-en-US
initial-setup-gui
libgnomekbd
libicu
libnm-gtk
libreport-gtk
libtimezonemap
mobile-broadband-provider-info
nm-connection-editor
python3-meh-gui
webkitgtk3
wpa_supplicant
yelp
yelp-libs
yelp-xsl

While I can easily see that hunspell is not needed in dom0, for packages
named "lib*"  this much more delicate ... so, according to you Marek, is
there something important I should not delete?

Thanks, 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 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/e85a6f01-afca-b39b-bff5-37a5c0ae8aad%40web.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] flexlm license manager in AppVM

[Stephan Marwedel]

Hi Steve,

thank you for the information.

Your approach probably won't work in my case, as the license served by 
flexlm software is tied to MAC address and hostname. If I install it in 
the TemplateVM the license will be created with MAC address and hostname 
of that TemplateVM. If I later start the software from the AppVM like 
you suggested, it will provide a different MAC address and hostname 
which will invalidate the license. So there seems to be no alternative 
other than to create a standalone VM and install the commercial package 
in that VM.


Regards,
Stephan

On 02/28/2017 04:15 PM, Steve Coleman wrote:

On 02/25/2017 04:07 PM, Stephan Marwedel wrote:

Hi,
I use a commercial simulation environment running on Debian. I installed
the software in the Debian TemplateVM and it is running fine. However,
when starting an AppVM based on that template I cannot use the
simulation software because of the flexlm license manager failing. This
is most likely caused by the AppVM getting both a hostname and MAC
address being different from those of the corresponding TemplateVM.

What options do I have, if any, to work with such a commercial software
in an AppVM, as I don't want to work in the TemplateVM?



What I have done is install the COTS software base in the template VM. I
generally choose /opt for COTS products to keep them separate.

Then I install a service to start the license manager in the one client
VM and create a desktop file pointing to that installed application
location. Install the desktop file in the template
/usr/share/applications but assign it in the start menu of just that one
VM. Look at qvm-service for how to assign the license manager service to
just that one VM instance.

Any VM may see the software on disk, but as long as you don't actually
run from the software template or other VMs then you should be good with
the license server seeing only the one install instance.

Things can get a bit trickier if the service/software demands to be able
to write to the system area of the template provided ro file system.
Then you may need some fixups performed prior to starting the license
service.

Other options might be to install in /usr/local in the client VM itself,

t> or even in your home directory if that is possible. The service is

likely required as before unless you write a script to launch the
license manager, wait for it, and then launch the application when the
license manager is ready.

My worst case situation would be a standalone VM, but I haven't found
anything quite that stubborn just yet.

Steve



--
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/fefe2e6e-9f24-f943-8ec0-4137586229ea%40tu-ilmenau.de.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] ubuntu template

[Damien Waber]

Thank you so much!

Le Fri, Mar 3, 2017 à 4:07 PM, Unman  a écrit :

> On Fri, Feb 10, 2017 at 11:15:18PM +, Unman wrote:
> > On Fri, Feb 10, 2017 at 10:04:54AM -0800, damien.wa...@gmail.com wrote:
> > > Le jeudi 9 février 2017 12:41:42 UTC+1, Unman a écrit :
> > > > On Thu, Feb 09, 2017 at 02:37:36AM -0800, wrote:
> > > > > Hi,
> > > > >
> > > > > I am new into qubes (few months) and find it great. But I need a
> distro with newer packages (debian jessie was fine until I ran in issues
> with encfs compatibility).
> > > > >
> > > > > So I wanted to build an ubuntu template but I did not found clear
> instructions.
> > > > >
> > > > > using https://github.com/QubesOS/qubes-builder and the setup
> script, I do not get ubuntu to choose in the menu.
> > > > >
> > > > > On this forum, there is few posts about it but using privaze repo.
> > > > >
> > > > > I really need help on this :-)
> > > > >
> > > > > Best regards,
> > > > >
> > > > > Damien
> > > > >
> > > >
> > > > Hi Damien,
> > > >
> > > > The Ubuntu builds are referenced in setup as Trusty and Xenial.
> > > >
> > > > I've just put in a series of Pull Requests that should allow
> > > > straightforward builds of both.
> > > > Wait a little while for them to be merged.
> > > >
> > > > It should then be a matter of:
> > > > git clone  https://github.com/QubesOS/qubes-builder
> > > > cd qubes-builder
> > > > ./setup
> > > > make qubes-vm
> > > > make template
> > > >
> > > > Copy generated Template to dom0 and install - there's a handy script
> > > > provided to do this for you.
> > > >
> > > > I'll let you know when the PRs are merged. Focus at the moment is on
> > > > the GSOC applications.
> > > >
> > > > unman
> > >
> > > Hi, thank you !
> > >
> > > Is there a way I may support you? maybe I can test it?
> > >
> > >
> > > Best regards,
> > >
> > > Damien
> > >
> >
> > As soon as the PRs are merged I'll post to the list, and you can try it
> > then. (Or you could merge them yourself of course, and try the build.)
> > Testing and feedback would be much appreciated.
> >
> > I've been using Xenial for a while and it seems fine.
>
> PRs are merged, to master if nor 3.2
>
> This means that both Xenial and Trusty should build straight.
>
> Set up a build environment as per docs.
>
> git clone  https://github.com/QubesOS/qubes-builder
> cd qubes-builder
> ./setup (select builder-debian and trsut/xenial variants, deselect
> fed23)
> edit builder.conf, changing RELEASE:=3.2 to RELEASE:=master
> make switch-branch (to get latest and greatest versions of components)
> make qubes-vm
> make template
>
> cheers
>
> 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/CAA5b1EsobC%3DZaY2ATw_-%3DZ1SpQdPKGAQJLoVXPGo6N0eoJj10g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] do I really need these packages in dom0 :?

[Marek Marczykowski-Górecki]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, Mar 03, 2017 at 03:15:59PM +0300, Oleg Artemiev wrote:
> On Fri, Mar 3, 2017 at 12:34 AM, Oleg Artemiev  wrote:
> > On Thu, Mar 2, 2017 at 11:01 PM, Marek Marczykowski-Górecki
> >  wrote:
> >> -BEGIN PGP SIGNED MESSAGE-
> >> Hash: SHA256
> >>
> >> On Mon, Feb 27, 2017 at 06:23:22AM +0300, Oleg Artemiev wrote:
> >>> After installing qubes 3.2 looked into dom0 updates.
> >>>
> >>> Found some that I possibly ok to remove:
> >>>
> >>> [olli@dom0 ~]$ rpm -q --whatrequires tigervnc-server-minimal
> >>> anaconda-gui-23.19.10-4.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-gui
> >>> initial-setup-gui-0.3.37-1.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-gui
> >>> no package requires initial-setup-gui
> >>> [olli@dom0 ~]$
> >>
> >> It is used during fist system startup. Later can be removed.
> >>
> >>> Also, do I really need this in Dom0:
> >>>
> >>> [root@dom0 olli]# rpm -q --whatrequires openssh
> >>> openssh-askpass-7.2p2-3.fc23.x86_64
> >>> [root@dom0 olli]# rpm -q --whatrequires openssh-askpass
> >>> no package requires openssh-askpass
> >>> [root@dom0 olli]#
> >>>
> >>> ?
> >>>
> >>> Also I've Network Manager in Dom0 - why - it is designed never have
> >>> networking. It is left by anaconda - setup program. Why not to delete
> >>> it?
> >>
> >> See above.
> >>
> >>> lli@dom0 ~]$ rpm -qa |grep -i net
> >>> NetworkManager-wifi-1.0.12-2.fc23.x86_64
> >>> NetworkManager-libnm-1.0.12-2.fc23.x86_64
> >>> NetworkManager-1.0.12-2.fc23.x86_64
> >>> NetworkManager-glib-1.0.12-2.fc23.x86_64
> >>> glib-networking-2.46.1-1.fc23.x86_64
> >>> libnetfilter_conntrack-1.0.4-5.fc23.x86_64
> >>> nettle-3.2-1.fc23.x86_64
> >>> netcf-libs-0.2.8-3.fc23.x86_64
> >>> NetworkManager-team-1.0.12-2.fc23.x86_64
> >>> libnfnetlink-1.0.1-7.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-wifi
> >>> anaconda-gui-23.19.10-4.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-libnm
> >>> no package requires NetworkManager-libnm
> >>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-glib
> >>> anaconda-core-23.19.10-4.fc23.x86_64
> >>> nm-connection-editor-1.0.10-1.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires nm-connection-editor
> >>> anaconda-gui-23.19.10-4.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-core
> >>> anaconda-tui-23.19.10-4.fc23.x86_64
> >>> anaconda-gui-23.19.10-4.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-tui
> >>> anaconda-core-23.19.10-4.fc23.x86_64
> >>> initial-setup-0.3.37-1.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup
> >>> initial-setup-gui-0.3.37-1.fc23.x86_64
> >>> initial-setup-gui-0.3.37-1.fc23.x86_64
> >>> initial-setup-launcher-1.0-1.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-gui
> >>> no package requires initial-setup-gui
> >>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-launcher
> >>> no package requires initial-setup-launcher
> >>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-team
> >>> anaconda-core-23.19.10-4.fc23.x86_64
> >>> [olli@dom0 ~]$ rpm -q --whatrequires nettle
> >>> no package requires nettle
> >>> [olli@dom0 ~]$ rpm -q --whatrequires libnfnetlink
> >>> no package requires libnfnetlink
> >>> [olli@dom0 ~]$
> >>>
> >>> from above only netcf-libs is required indirectly by xen related
> >>> package. So is it safe to drop all other from above w/ rpm -e  ?
> >>
> >> Yes. You can start with 'dnf remove initial-setup-gui' - it will propose
> >> additional packages not needed anymore. But carefully review that list
> >> before confirming.
> 
> > Shouldn't those be removed by default as a postinstall step?
> 
> May I add this (and above sentence as subject) as a feature request in github?
> 
> We should not have non-required packages in Dom0 by default, right?

Yes, good idea.

- -- 
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

iQEcBAEBCAAGBQJYuZfOAAoJENuP0xzK19cs+toH/i2xDVPufQry6fe1DZYqGmep
GXGRxg0nx5U1VQL7+NoKwnoum3bh3n0jvNr57WNMdAoE1obD9oZO1jF6wGqkF6Rw
z7mOWSOmFUAe8LN5WqWSauywEFavLxf09PrjXUdJt6wjDJ5gQM+JChXUKwNsTsoL
vlfx1cpeG4/dcB/Klm6KeIQ7h3hyCeQGtrvw0ZhevHQpbzQWT3ldto8ChKj0DlPo
ts536c/zpFkVc/uL84o/tSr/VtcncLewH/U4TBuYZxuGenKYpLoPihm3pcsZa+Jm
Czd8wktZsmp8fGaAzQMNeHnCx+0r9oom6x4WlP3HQl+hpkUVHVKujzFz3kYtqcY=
=3HAH
-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 

[qubes-users] Fedora-24 Template Corrupted?

[qubesos]

Fedora-24 template shows updates available. However updates terminal returns 
error [cannot copy/past results]. I then open gnome terminal and get the 
following:
[user@fedora-24 ~]$ sudo dnf update
Last metadata expiration check: 2:23:51 ago on Fri Mar  3  2017.
Dependencies resolved.

 Package   Arch  Version   Repository  Size

Skipping packages with broken dependencies:
 gnome-software    x86_64    3.22.5-1.fc24 updates    9.3 M

Transaction Summary

Skip  1 Package

Nothing to do.
Sending application list and icons to dom0
The above output from gnome terminal is completely different from the updates 
terminal - which refers to skipping "flatpak" package.
To resolve I reloaded Qubes OS 3.2 but got same errors.
Any thoughts?

--
Securely sent with Tutanota. Claim your encrypted mailbox today!
https://tutanota.com

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

[qubes-users] Win 7, Qubes 3.2, qubes-windows-tools 3.2.2-3 struggles

[Ed Welch]

Hey everyone, new to qubes, love it!

Getting going with linux I found pretty straight forward, no issues.

Trying to get a Windows 7 HVM template created, not going so well.

Thought I would post some of the issues I've had for posterity and also 
see if I can get some help.



If you are like me and don't generally read long winded posts, please at 
least scroll to my QUESTION at the bottom :)



Most of the instructions tell you to create a VM, however, none of them 
tell you to increase the default VM specs.  For win 7 64 it seems you 
want to increase the RAM to 4096MB and primary partition to 40960MB 
(40G) I know for a fact 20G is not enough to update windows 7 sp1 to latest.


You'll want to do this before anything else because it's more difficult 
to do after you get started



Then I ran into the xen/cirrus video driver issue which causes windows 
to freeze on the startup screen, found this issue with workaround: 
https://github.com/QubesOS/qubes-issues/issues/2488


This workaround does the trick, but I think it's important to note a few 
additional steps, after the last setup reboot and BEFORE YOU SHUTDOWN 
windows and try to install the windows guest additions.


MAKE SURE to enable login without password through the netplwiz tool, it 
seemed like this was the crucial step in avoiding this issue: 
https://groups.google.com/forum/#!msg/qubes-users/Vbga8Z-DjHE/GVHIWIob5uIJ


Also, users mentioned in that thread the importance of adding more RAM, 
however, for me it seemed that enabling login without password was the 
step that avoided putting your VM in a totally unrecoverable BSOD loop.


Following the wiki instructions, I then installed the windows tools from 
the qubes-dom0-current-testing repo (and also updated the qrexec_timeout 
to 300 seconds) then switching back to the modified instructions for 
working around the cirrus/xen bug I was able to boot into windows and 
install the windows tools.



This is where I hit my next big stumbling point, during the installation 
the PV drivers prompt you to reboot.  DO NOT REBOOT until the 
installation finishes, I did eventually see on this page 'Xen PV driver 
components may display a message box asking for reboot during 
installation – it’s safe to ignore them and defer the reboot.'


Really this needs to be promoted to 
https://www.qubes-os.org/doc/windows-appvms/ IMO and in big bold letters 
DO NOT REBOOT until the installation is completed kind of thing.  If you 
reboot before it finishes this is really unrecoverable and it's easier 
to just blow away the vm and start again...



Ok, so now we get to where I'm stuck, my vm is installed, 
qubes-windows-tools 3.2.2-3 is installed, however as soon as I start the 
thing, it boots and the display immediately goes away, found this issue: 
https://github.com/QubesOS/qubes-issues/issues/1896  which matches the 
behavior I'm seeing, however, this was fixed some time ago, but not 
totally sure when it was released??



My second, issue, which may actually be causing the first, seems to best 
be described in this thread: 
https://groups.google.com/d/topic/qubes-users/4OgwojFK-sI/discussion


Specifically I'm having the issue in the last comment, the only way I 
can get any UI is if I boot with --debug, and when I do, I often see 
that error linked: 'The GUI agent that runs in the VM 'win7' implements 
outdated protocol (0:0), and must be updated.



After reading through that thread, several people were mentioning that 
3.2.2-3 has seemed to make things less stable.



What I would like to do, is install the previous version of 
qubes-windows-tools, but try as I might to manipulate the 
qubes-dom0-update script into doing so I have not been able to do this, 
I'm not even sure the older versions are kept in the repos??


QUESTION:  Is there a way to install a specific version (whatever was 
previous to 3.2.2-3) of qubes windows tools?



Thanks!

Ed

--
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/821726de-f5c1-d6a9-b15e-078e1f9cc56d%40edjusted.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] ubuntu template

[Unman]

On Fri, Feb 10, 2017 at 11:15:18PM +, Unman wrote:
> On Fri, Feb 10, 2017 at 10:04:54AM -0800, damien.wa...@gmail.com wrote:
> > Le jeudi 9 février 2017 12:41:42 UTC+1, Unman a écrit :
> > > On Thu, Feb 09, 2017 at 02:37:36AM -0800, wrote:
> > > > Hi,
> > > > 
> > > > I am new into qubes (few months) and find it great. But I need a distro 
> > > > with newer packages (debian jessie was fine until I ran in issues with 
> > > > encfs compatibility).
> > > > 
> > > > So I wanted to build an ubuntu template but I did not found clear 
> > > > instructions.
> > > > 
> > > > using https://github.com/QubesOS/qubes-builder and the setup script, I 
> > > > do not get ubuntu to choose in the menu.
> > > > 
> > > > On this forum, there is few posts about it but using privaze repo.
> > > > 
> > > > I really need help on this :-)
> > > > 
> > > > Best regards,
> > > > 
> > > > Damien
> > > > 
> > > 
> > > Hi Damien,
> > > 
> > > The Ubuntu builds are referenced in setup as Trusty and Xenial.
> > > 
> > > I've just put in a series of Pull Requests that should allow
> > > straightforward builds of both.
> > > Wait a little while for them to be merged. 
> > > 
> > > It should then be a matter of:
> > > git clone  https://github.com/QubesOS/qubes-builder
> > > cd qubes-builder
> > > ./setup
> > > make qubes-vm
> > > make template
> > > 
> > > Copy generated Template to dom0 and install - there's a handy script
> > > provided to do this for you.
> > > 
> > > I'll let you know when the PRs are merged. Focus at the moment is on
> > > the GSOC applications.
> > > 
> > > unman
> > 
> > Hi, thank you !
> > 
> > Is there a way I may support you? maybe I can test it?
> > 
> > 
> > Best regards,
> > 
> > Damien
> > 
> 
> As soon as the PRs are merged I'll post to the list, and you can try it
> then. (Or you could merge them yourself of course, and try the build.)
> Testing and feedback would be much appreciated.
> 
> I've been using Xenial for a while and it seems fine.

PRs are merged, to master if nor 3.2

This means that both Xenial and Trusty should build straight.

Set up a build environment as per docs.

git clone  https://github.com/QubesOS/qubes-builder
cd qubes-builder
./setup (select builder-debian and trsut/xenial variants, deselect
fed23)
edit builder.conf, changing RELEASE:=3.2 to RELEASE:=master
make switch-branch (to get latest and greatest versions of components)
make qubes-vm
make template

cheers

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

Re: [qubes-users] Re: Idiot's guide to Ubuntu 16.04 TemplateVM on Qubes 3.2

[Unman]

On Sat, Feb 25, 2017 at 07:32:53PM +, Unman wrote:
> On Sat, Feb 25, 2017 at 03:27:28AM -0800, trul...@gmail.com wrote:
> > 
> > Trying to compile without "sudo" and "xenial" without desktop. Installation 
> > has succefull. Big Thanks.
> 
> You should be able to build with desktop enabled. As it says in the
> docs it's straightforward. What was the issue?
> 
> I have a yakkety build but haven't bothered to put it up. I'll put in a
> Zesty when it's released in April.
> 
> For anyone wanting a Trusty build, there are PRs in the pipeline for
> this, which make it as easy as the Xenial. I'll see if I can push them 
> through.
> 
> unman

For anyone interested in Trusty the PRs are finally merged, in master if
not in 3.2.

You should be able to build Trusty by following instructions in the docs
to set up a build environment,cloning qubes-builder, and running
setup.sh to select just Trusty or trusty+desktop

edit the builder.conf file, and change the line RELEASE:=3.2 to
RELEASE:=master
I also add VERBOSE=1

make switch-branch (to make sure that everything is picking up latest
and greatest from master)
make qubes-vm
make template

The build should be painless, but if you have any problems or need help
post here.

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

[qubes-users] fedora-24 update error: nothing provides ostree-libs(x86-64) >= 2016.14 needed by flatpak-0.8.3-3.fc24.x86_64

[mittendorf]

Hello fellow Qubes users,

If I execute update of the fedora-24 template via the Qubes VM manager,
it aborts with the error

nothing provides ostree-libs(x86-64) >= 2016.14 needed by
flatpak-0.8.3-3.fc24.x86_64

If I use
sudo dnf upgrade
from the terminal within fedora-24 the command is executed, but later
executions list the problem with flatpack (broken dependencies)

of course I can remove flatpack, but I don't know whether I may need it?!

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/bbde8e53-0765-68a0-b0f9-6ec3fab749c9%40digitrace.de.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] RE: Win7, qvm-copy-to-vm, QubesIncoming location?

[Martin L . Fällman]

> -Original Message-
> From: Foppe de Haan [mailto:0spinbo...@gmail.com]
> Sent: den 3 mars 2017 11:31
> To: qubes-users 
> Cc: Martin L. Fällman 
> Subject: Re: Win7, qvm-copy-to-vm, QubesIncoming location?
> 
> it'll be in a subfolder of the documents root.

This is the problem: the files are nowhere to be found. Somewhere they do get 
written because the file copy mechanism identifies that there's already an 
object there by the same name and it shouldn't be overwritten, but there's no 
way for me to find it. I did a proper clean re-install of the Windows tools, 
and set the default user for my W7 HVM to the correct name (the one I log in 
as) in qvm-prefs, but the problem persists.

Wherever the files I send to the VM gets written, I can't find them from inside 
the VM, and they persist between restarts. Could it be that they're written to 
private.img but somewhere Windows doesn't consider "real" for whatever reason? 
Tried reading the source too but I'm not a C programmer and can't make heads or 
tails of what's going on.

Best,
//MLF. 

-- 
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/999df6e2a98d4178809e1bd883c30c19%40Exchange01.domain.local.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] do I really need these packages in dom0 :?

[Oleg Artemiev]

On Fri, Mar 3, 2017 at 12:34 AM, Oleg Artemiev  wrote:
> On Thu, Mar 2, 2017 at 11:01 PM, Marek Marczykowski-Górecki
>  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>> On Mon, Feb 27, 2017 at 06:23:22AM +0300, Oleg Artemiev wrote:
>>> After installing qubes 3.2 looked into dom0 updates.
>>>
>>> Found some that I possibly ok to remove:
>>>
>>> [olli@dom0 ~]$ rpm -q --whatrequires tigervnc-server-minimal
>>> anaconda-gui-23.19.10-4.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-gui
>>> initial-setup-gui-0.3.37-1.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-gui
>>> no package requires initial-setup-gui
>>> [olli@dom0 ~]$
>>
>> It is used during fist system startup. Later can be removed.
>>
>>> Also, do I really need this in Dom0:
>>>
>>> [root@dom0 olli]# rpm -q --whatrequires openssh
>>> openssh-askpass-7.2p2-3.fc23.x86_64
>>> [root@dom0 olli]# rpm -q --whatrequires openssh-askpass
>>> no package requires openssh-askpass
>>> [root@dom0 olli]#
>>>
>>> ?
>>>
>>> Also I've Network Manager in Dom0 - why - it is designed never have
>>> networking. It is left by anaconda - setup program. Why not to delete
>>> it?
>>
>> See above.
>>
>>> lli@dom0 ~]$ rpm -qa |grep -i net
>>> NetworkManager-wifi-1.0.12-2.fc23.x86_64
>>> NetworkManager-libnm-1.0.12-2.fc23.x86_64
>>> NetworkManager-1.0.12-2.fc23.x86_64
>>> NetworkManager-glib-1.0.12-2.fc23.x86_64
>>> glib-networking-2.46.1-1.fc23.x86_64
>>> libnetfilter_conntrack-1.0.4-5.fc23.x86_64
>>> nettle-3.2-1.fc23.x86_64
>>> netcf-libs-0.2.8-3.fc23.x86_64
>>> NetworkManager-team-1.0.12-2.fc23.x86_64
>>> libnfnetlink-1.0.1-7.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-wifi
>>> anaconda-gui-23.19.10-4.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-libnm
>>> no package requires NetworkManager-libnm
>>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-glib
>>> anaconda-core-23.19.10-4.fc23.x86_64
>>> nm-connection-editor-1.0.10-1.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires nm-connection-editor
>>> anaconda-gui-23.19.10-4.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-core
>>> anaconda-tui-23.19.10-4.fc23.x86_64
>>> anaconda-gui-23.19.10-4.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires anaconda-tui
>>> anaconda-core-23.19.10-4.fc23.x86_64
>>> initial-setup-0.3.37-1.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup
>>> initial-setup-gui-0.3.37-1.fc23.x86_64
>>> initial-setup-gui-0.3.37-1.fc23.x86_64
>>> initial-setup-launcher-1.0-1.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-gui
>>> no package requires initial-setup-gui
>>> [olli@dom0 ~]$ rpm -q --whatrequires initial-setup-launcher
>>> no package requires initial-setup-launcher
>>> [olli@dom0 ~]$ rpm -q --whatrequires NetworkManager-team
>>> anaconda-core-23.19.10-4.fc23.x86_64
>>> [olli@dom0 ~]$ rpm -q --whatrequires nettle
>>> no package requires nettle
>>> [olli@dom0 ~]$ rpm -q --whatrequires libnfnetlink
>>> no package requires libnfnetlink
>>> [olli@dom0 ~]$
>>>
>>> from above only netcf-libs is required indirectly by xen related
>>> package. So is it safe to drop all other from above w/ rpm -e  ?
>>
>> Yes. You can start with 'dnf remove initial-setup-gui' - it will propose
>> additional packages not needed anymore. But carefully review that list
>> before confirming.

> Shouldn't those be removed by default as a postinstall step?

May I add this (and above sentence as subject) as a feature request in github?

We should not have non-required packages in Dom0 by default, right?

-- 
Bye.Olli.
gpg --search-keys grey_olli , use key w/ fingerprint below:
Key fingerprint = 9901 6808 768C 8B89 544C  9BE0 49F9 5A46 2B98 147E
Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/

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

[qubes-users] Re: Win7, qvm-copy-to-vm, QubesIncoming location?

[Foppe de Haan]

it'll be in a subfolder of the documents root.

-- 
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/5a6fcaa2-ed52-4cca-867e-c1d6c9e8c7c4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Win7, qvm-copy-to-vm, QubesIncoming location?

[Martin L . Fällman]

New Qubes user here. Running a Win7 VM for many work tasks. Once I set it up I 
could copy-to-vm just fine, with a QubesIncoming folder showing up and 
everything. Then I domain-joined the W7 install and got a new user account, the 
user account I set up during install was renamed admin and I dont use it unless 
I have to now.

 

All of a sudden, copy-to-vm doesnt work as expected. The file is clearly sent 
just as normal. But I cant find it anywhere on the W7 hard drive. Whats weirder 
is, if I try to send it a 2nd time I get the error message

qfile-agent: Fatal error: File copy: not overwriting existing file. Clean 
QubesIncoming dir, and retry copy; Last file: test.txt (error type: File exists)

 

So, my guess is that its written somewhere to the W7 disk, but qfile-agent is 
confused as to where exactly it should end up, and its probably written to a 
dir that Windows for some reason doesnt even see. Is there anywhere in the 
settings for the VM where I can change the incoming directory to match my 
current user profile?

 

(Ive tried to re-install the Windows tools as well; didnt make any difference.)

 

Thanks!

 

MARTIN L. FÄLLMAN
PROTECTION OFFICER

CIVIL RIGHTS DEFENDERS
Address: Sergels torg 12, floor 12, SE-111 57 Stockholm, Sweden
Tel: +46 8 120 744 03, Mobile: +46 70 484 96 75
martin.fall...@civilrightsdefenders.org 
 

PGP: 0ECD 731D D578 6145 AB22 D213 5104 FC60 779A FD28
SIGNAL available on cell number 

We defend peoples civil and political rights and empower human rights defenders 
worldwide.
Learn how to support us on www.crd.org

 

-- 
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/83abb6f27bf64499aca6272a9351b011%40Exchange01.domain.local.
For more options, visit https://groups.google.com/d/optout.


PGP.sig
Description: PGP signature