Windows7 issue with Dom0 GUI Daemon

[3n7r...@gmail.com]

Qubes 3.1
Windows7 Pro x64
Windows Tools 3.0.4-1

Without Debug mode, VM does not produce any windows and ends in an unresponsive Yellow state.

With Debug mode, VM appears to hang after Windows logo boot screen. In F8 Low-Resolution Mode, VM boots to desktop and is fully functional.

Increasing resolution while in Low-Resolution Mode sends VM into unresponsive Yellow state.

Any workarounds? Existing threads seem to have been patched.

[3n7r...@gmail.com]

* Multi-monitor setup

* This error presented itself on one boot but has gone away.
[Dom0] Sorry - KDialog: The Dom0 GUI daemon do not support protocol version 107:0, requested by the VM 'win7'.

[3n7r...@gmail.com]

Disabled all additional monitors.
Everything works great - including Seamless GUI.

[3n7r...@gmail.com]

Duplicate of Unresolved Issue: https://groups.google.com/forum/#!searchin/qubes-users/windows$20multi$20monitor/qubes-users/lG6ynmOkIgY/1Nu4sT9XCwAJ

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

The issue for this was recently closed:

https://github.com/QubesOS/qubes-issues/issues/1704

Rafał, is the fix for this available in a testing repo (or already live)?

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXsm1RAAoJENtN07w5UDAwuA0P/3ecW8mibedwHeBhGsMmiqCX
tLgQgua+9Nc1an0G1PhNjTnyegEIS9nbDaFoWiUhwwxP+HdgBlsciFH2xxm2gW9I
4HSjpAcO+7qJoxWkuGVpf4Ew8/ioJEDnyFfizzc6F0TabPZlLzx+Y2Wh+0VC6+zF
mAclvWjotfuSFLvFt1PqCf53xYVK2uawDQd4WEGK2LrATNmT7sj+gKg4thUm0Uin
1e04TgO7uHYebC93VpS5UtbUHhnu851ZwzYk8jB+mJ2KkLL27y4DM2+lUjCF/hcC
h25Lw/53fxdcCMNf5gX7SIUrbZFRPaRGBm1L6Hzh2uybB6kHNAv2M87wINHjnf9M
ufJgoWMWrWG3tTmwUnFFe7XWCLHb3ZOZ4XcPvWFoHBoZY9NSonWH2Qcvf0h/NPh5
v49DoyuGeA8sMwxh/2ZagLvFOhwgElj+cpLFwZju600JHyfmkT5lo6gm67CFDBTj
LX9nxSrJ6xU9Q4pZqJyPVeFPMtBEh//8Ds2Joy+0AJiTyhU00GwMX3w6Hop7Mm9F
tGcPzfgUTcPiuViBIfVKbDDtmRhBBgH5bruCyv0vbp5cHdsLOS1RPd+tIBSuKY31
PfXMXx1AVjVRlqKwy6CPsQ1Jm7ba2BNzcMPFuGrKEeIp9QAmNuV4/SoL8YhY/Bti
AchSf0W+1n3CY/yHMU5N
=d4mK
-----END PGP SIGNATURE-----

[Drew White]

On Tuesday, 16 August 2016 11:33:18 UTC+10, Andrew David Wong wrote:
> The issue for this was recently closed:
>
> https://github.com/QubesOS/qubes-issues/issues/1704
>
> Rafał, is the fix for this available in a testing repo (or already live)?
>

How does a person re-open the issue?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

If you're logged into GitHub, there should be a "reopen" button (not sure if
visibility is permissions-based). You should probably test the patch that is
supposed to fix the issue before reopening it, though. The patch should be
available for testing soon.

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXszwAAAoJENtN07w5UDAwG68P/id8COtBc12eAS5k/SY+jM6f
L/c07vYQlOe2vFnZ9sTerZyNOexJkzxEZO+GH/mF0I7hQEaHkMnW9uPFyFb87sjO
cePuSbhid4atjWRER/jlkTc0RS5nExwUPcLkKtNu+iPs0rS7cvRjl1w85V78b4to
py3j+bgAwd9Tm/1xxLHRhSeQXiCaX9gX3ENa5BcV/FkvwWRaw8yqFeLIFh7+LpdB
vu1CV2j8SV5qMQ8IJvPYPhXWAzMSw89d5oOcEAn8WDc4L4qBnHdtRZk4EiqtG8H6
fBWCWq6Lm/Hu8cSPYLGF4jXgnmyf21CloMaIyQy0pbHUrWK9azxk4semjxE9z1kR
aAF8W3xMM9FBRrvLUD2zbfx+PSzc5quRFoyUGh7F57ZlzQpOMBsPVZ2eYYUo+pNE
PXryQTbUPSLmrF+NZ1VerepUVHPTm/5baDfSUV8+U3THLn42oA6Ntf4DwZqhA+SI
LCgV9PBvkv/dAGfO1OFGvFux0ijAu6xBN4EP2aNXIxh0oQCptdYTzvm1k69DwS7X
TDlc4w5tlo0WYRL3QzYgtO6QaU3Y9AacmDysOvqju1aNlbwUcCtZOdR7yGQTCW0d
vBgUb3AIAEEHMG+N8SxsmNzheuCkBu/t3u2dDnaeRFSljX3UwWUIk6p4uLBBE7HC
gjKUGst06SH8o+1oHxBB
=KluW
-----END PGP SIGNATURE-----

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Tue, Aug 16, 2016 at 09:14:57AM -0700, Andrew David Wong wrote:
> On 2016-08-16 00:26, Drew White wrote:
> > On Tuesday, 16 August 2016 11:33:18 UTC+10, Andrew David Wong wrote:
> >> The issue for this was recently closed:
> >>
> >> https://github.com/QubesOS/qubes-issues/issues/1704
> >>
> >> Rafał, is the fix for this available in a testing repo (or already
> >> live)?
> >>
> >
> >
> > How does a person re-open the issue?
> >
>
> If you're logged into GitHub, there should be a "reopen" button (not sure if
> visibility is permissions-based). You should probably test the patch that is
> supposed to fix the issue before reopening it, though. The patch should be
> available for testing soon.

The updated package is uploaded to testing repository for Qubes 3.2.

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

iQEcBAEBCAAGBQJXs4HZAAoJENuP0xzK19csZjAH/RRPmmiGCzQ8MmshPw9TomMD
nig+jJpsZxeImETR3dhXn+8Lhf1gnVahxUcyAeAElJRVfmJ4iOn1Bpf8XfHR6+9g
etVhEdBCY99D7GrPzkK+BSaxTFL6Kh6lQ9fYEg9wHG14R4xqlYcQQuOISrJb74gd
b1Q5Fzxp/zGDFJHeKq8FZ0loPq6dgtKHv0uqxDP+8unJBKws8MYNGZRboSJBJis8
Rag7XMR2jSSflqrLu1vKluSMVKp0bzGL5muiQEI0KqigdJQdiewh/C1BDuCOaNlf
0wPdCvGHDRAYIbDMrTw/x72JRfrbLN7CLflpvZnzW46AcZno4G0p5wQAwzEnPQI=
=KsaF
-----END PGP SIGNATURE-----

[Drew White]

On Wednesday, 17 August 2016 07:13:06 UTC+10, Marek Marczykowski-Górecki wrote:
>
> The updated package is uploaded to testing repository for Qubes 3.2.
>

So how do I get the package for the multi-monitor then?

[Andrew David Wong]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

(Repeating my reply to your other thread.)

If you're on R3.2, and if you're willing to test this package (and you're
certainly under no obligation to do so), then you can do so now by following
the instructions here (under "Testing repositories"):

https://www.qubes-os.org/doc/software-update-dom0/#tocAnchor-1-1-3

I believe the correct repo is current-testing. If so, your command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing <package>

If this is, indeed, the right place, then you can see a list of available
packages here (or from the command line):

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

The only packages containing the word "windows" are different versions of
qubes-windows-tools, so I gather this is what you want. If that's correct,
then the command would be:

$ sudo qubes-dom0-update --enablerepo=qubes-dom0-current-testing \
qubes-windows-tools

- --
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCgAGBQJXs7N1AAoJENtN07w5UDAw+b4P/jHps5pp2vZOIov+qJrOm8QZ
DFxHj+fsCyc1GstG1sPYt/Rc9xEWx5AyYJEOBslvVIokDYk0PJaWXBnKVMLql35T
N2a3YZJWFjQP/ZOVytNKdOZ1RgBWxOJ8K0Y8+XSWrvwT39PdindytGlTPTqFJVxS
b7BHzA8yAfGYuN6IGNTxPmtbame2KAhQCCsrEoe9Nlp4UE7z7LdKdadlVFrHjMKU
dy738/hzTaYuCDjDh5EfvYJvrLj9MVmCka2rqemxaunFX0mr0iOqAZZKCg8idg7w
ifCsZYl7ujxXCzB6ZDQNrJruZdeFYCBchorf3X/P3sGBi5JP/ArG0MjyvsrgcubO
odN9DgfsIdYgqayqryECqB4F3pYjt/kGNDHATfqxbZVrqBlEaUmJOgal0OgBcqge
ipz9IgfmtWG6pSR5yk+vTxz+rRgnh6tdcE4Me5xXChDTukbiDP7EUz1ziIm18PqP
MPjUOV7RBvuFsoIk3ObJ3SnN9BKA2GANkc/Bdc+3brC1Rg3+d0d6wv4DySgSmvtM
ZyCgE3HulLiSNYTrgkMmjCJgtlw/MmbQdnYrlYH/oByhLMGKlWu18NOc76769zf5
adBhDXUnQN+gxxM5gM3iH+J5fUY6VT5yjYjhNJuvINt7UgRicSPVcRMktrIUDVA5
Id8KdvGS8v8CYSQjlEjX
=02su
-----END PGP SIGNATURE-----