Re: [qubes-users] External monitor resolution

[Franz]

On Mon, Sep 24, 2018 at 5:30 PM, Franz <169...@gmail.com> wrote:

>
>
> On Mon, Sep 24, 2018 at 2:38 PM, Franz <169...@gmail.com> wrote:
>
>>
>>
>> On Mon, Sep 24, 2018 at 1:11 PM, unman 
>> wrote:
>>
>>> On Mon, Sep 24, 2018 at 01:02:50PM -0300, Franz wrote:
>>> > On Qubes 3.2 had to add an External monitor because my Lenovo x230
>>> laptop
>>> > display started flickering and slowing down. But the resolution on the
>>> > external monitor is wrong. What appears on screen is correctly high,
>>> but
>>> > too large to fit into the screen.
>>> >
>>> > Running xrandr gives the output on the enclosed photo. From that I
>>> imagine
>>> > that the resolution of the external monitor should be changed to
>>> 1366x768.
>>> >
>>> > But how do I do that? I spent a couple hours reading many old threads,
>>> but
>>> > they imply a knowledge I do not have, só cannot figure out. Also am
>>> afraid
>>> > of doing something wrong and loosing access to my computer.
>>> >
>>> > Any idea?
>>>
>>> I don't know what was in the photo.
>>> But you should be able to access these settings under the Qubes menu,
>>> System Settings, Display entry.
>>>
>>>
>>

Your System setting works Unman, i had to set all three flags:

1. external display is in Use
2. External display is primary
3. Displays are in mirror mode

So what is shown on the laptop is a bit smaller than the screen, but the
external display is perfect.

I understand that the Lenovo x230 does not have the power to properly set
the two displays each with the correct resolution, but in mirror mode, they
are exactly the same and it works.

Many thanks 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/CAPzH-qAX00js6Vk4_43qsDWLZCoZQpizNNXzqDnsMNR4eZqoAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] External monitor resolution

[Franz]

On Mon, Sep 24, 2018 at 2:38 PM, Franz <169...@gmail.com> wrote:

>
>
> On Mon, Sep 24, 2018 at 1:11 PM, unman  wrote:
>
>> On Mon, Sep 24, 2018 at 01:02:50PM -0300, Franz wrote:
>> > On Qubes 3.2 had to add an External monitor because my Lenovo x230
>> laptop
>> > display started flickering and slowing down. But the resolution on the
>> > external monitor is wrong. What appears on screen is correctly high, but
>> > too large to fit into the screen.
>> >
>> > Running xrandr gives the output on the enclosed photo. From that I
>> imagine
>> > that the resolution of the external monitor should be changed to
>> 1366x768.
>> >
>> > But how do I do that? I spent a couple hours reading many old threads,
>> but
>> > they imply a knowledge I do not have, só cannot figure out. Also am
>> afraid
>> > of doing something wrong and loosing access to my computer.
>> >
>> > Any idea?
>>
>> I don't know what was in the photo.
>> But you should be able to access these settings under the Qubes menu,
>> System Settings, Display entry.
>>
>>
> Thanks Unman,
> I found it and it is pretty easy, but maximum resolution option for the
> external monitor is 1024x768. Does this mean that for some reason it is
> impossible to set 1366x768?
>

Here are some old comments from Marek that suggest that something can be
done, but they are somehow abstracted for me to be able to follow:

"I'm not sure if the driver loaded at disk password prompt time is able
to set higher resolution. But you can try with "video=" kernel
parameter.

For one-time test, you can edit kernel command line in grub (press "e"
on the entry, go to "module /vmlinuz..." line and add the option at the
end, then boot with ctrl-x). You can start with something like
video=1920x1080 (or whatever resolution you want). Details about option
syntax in kernel documentation[1].

When you find the right value, you need to edit /etc/default/grub
(GRUB_CMDLINE_LINUX line) in dom0 to make the change permanent. After
editing this file, you need to regenerate actual grub configuration:
grub2-mkconfig -o /boot/grub2/grub.cfg

[1] https://www.kernel.org/doc/Documentation/fb/modedb.txt;



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

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

Re: [qubes-users] HCL - Lenovo Thinkpad T480

[sagi-qubes-users]

On 2018-09-07 17:56, bbrr3...@gmail.com wrote:
> As far as I recall it was simply:
> 
> qvm-pci detach sys-usb dom0:3c_00.0
> 
> This is the production machine now so can't investigate things further 

I can succesfully reproduce this workaround, without loss of functionality. 
Awesome. Thanks for sharing.

kind regards, Sagi

-- 
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/20180924183937.30163.46724%40kardo2.rtsn.nl.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: Open in Qube 3.0 beta released!

[Sven Semmler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 9/16/18 9:28 AM, Ivan Mitev wrote:
> Just curious - isn't it possible to open a link with 
> `qvm-open-in-dvm` in your ThunderbirdVM and tweak the
> corresponding rpc service (qubes.OpenInVM) to open a whonix-dvm ?

Yes it is, following the way you outlined for me here:
https://groups.google.com/d/msg/qubes-devel/0CpN7ol1ZdM/0cBPvwc6CgAJ

When I click any link in my Thunderbird VM I get the Open in VM dialog
that allows me to either choose a new disp VM or an already running /
existing VM. Works perfect!

/Sven
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEE18ry22WNibwI1qeq2m4We49UH7YFAlupKhcACgkQ2m4We49U
H7YF4A/9GQWityx7n1J/Nxfnb/ydhoBQScQyCqj+ZY+Us0OTZ5HNI1Y/L75Ixv3o
sh+cUhcS5AE6NveqHpK7ldU945q2P4hUZMhOxx2wTCn7kXLuHdfD1DjJJ4jfHPgv
pnGPLDti05IjBA1Fq1hgydU0YS/Kw+O2kpibqyFzge8PifB9M8FCcYZlMrhTMb1Y
TLObDO0S6yI0OB9JES5rROHNpX46CTKzkjtOOkJlP55xe21xhTt9JzDdqc3TUxAi
8y2/NXpExFyoAPTF0VHuXYKdzaNs4+/j+3ww7+IzBG2oUlBYs71RszlxckaxbZD8
eDC2UQcmvTFSl06IvLm4wFSljuV/ezkDsJYgdCZGedvaX6+tlBJfv8L+kl57kaFg
Y8u34z3eChmd1buOcg0bGoJo6MIPsXI1G6ZjtEjbTLcP/XGyHed3eHlxSAwDesCp
XXIrv2Ynifz50UKDlVMs+3F42npC/qjXBwqVSY1SYBuZd1GqEgHuRw+/EZZpQQkT
ykbzFG1+nkjTkQSoab2nax5POQeARF3u+j1jgWq7j3mjOL9pRpTm4YAh6D77sGrO
K0bPr5I552Ct2PYfEDjsjWBZUQ0FGuIWrCcq1M2VBzPUuI9L7VgjoPtRd+jtg6D8
hpjRA9e9QOBEk9CsUmQPCnrdMJdXMTrR1cDQjNnGQQfl8KCOnMA=
=yrFS
-END PGP SIGNATURE-

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To post to this group, send email to qubes-users@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/e17f2cfa-95c3-a4e0-f383-1365d93fcad8%40SvenSemmler.org.
For more options, visit https://groups.google.com/d/optout.

[qubes-users]

[Wolf moon]

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

Re: [qubes-users] External monitor resolution

[Franz]

On Mon, Sep 24, 2018 at 1:11 PM, unman  wrote:

> On Mon, Sep 24, 2018 at 01:02:50PM -0300, Franz wrote:
> > On Qubes 3.2 had to add an External monitor because my Lenovo x230 laptop
> > display started flickering and slowing down. But the resolution on the
> > external monitor is wrong. What appears on screen is correctly high, but
> > too large to fit into the screen.
> >
> > Running xrandr gives the output on the enclosed photo. From that I
> imagine
> > that the resolution of the external monitor should be changed to
> 1366x768.
> >
> > But how do I do that? I spent a couple hours reading many old threads,
> but
> > they imply a knowledge I do not have, só cannot figure out. Also am
> afraid
> > of doing something wrong and loosing access to my computer.
> >
> > Any idea?
>
> I don't know what was in the photo.
> But you should be able to access these settings under the Qubes menu,
> System Settings, Display entry.
>
>
Thanks Unman,
I found it and it is pretty easy, but maximum resolution option for the
external monitor is 1024x768. Does this mean that for some reason it is
impossible to set 1366x768?

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

-- 
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/CAPzH-qALsB%3DSnfCiEMdQ1TRgAT%3Dorh4eJCD%2BXSyezJyoTYpC9Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] XL VM connectivity to Qubes Network

[unman]

On Mon, Sep 24, 2018 at 05:40:16AM -0700, 3mp...@gmail.com wrote:
> Hi,
> 
> I’m still working on my Qubes 4.0 migration and I’m trying to connect a 
> Windows 10 XL created VM to Qubes Networking by adding this kind of line in 
> the hvm file :
> 
> vif = [ 'mac=00:16:3e:5e:6d:11,model=e1000,
> ip=10.137.0.50,script=vif-route-qubes,backend=sys-vpn’ ]
> 
> The backend is a functional proxy VM created by following the « Set up a 
> ProxyVM as a VPN gateway using iptables and CLI scripts » tutorial
> 
> The guest VM is a Windows 10 1804 with Xen paravirtual drivers 8.2.1 
> installed. The e1000 is correctly detected as a Xen adapter with link up and 
> configured with IP : 10.137.0.50 / 24, no gateway, I’m just trying to access 
> some HTTP services in another qube connected to the same proxyVM. Firewall 
> rules are OK because it’s working from a third qube connected to the proxyVM.
> 
> The Windows 10 VM is acting like it has no connectivy at all. Can’t connect 
> to the HTTP server of my qube. I tried removing all firewall rules in proxyVM 
> and qube HTTP server and setting ACCEPT policy for all chains, it doesn’t 
> change anything so I think it’s not a firewall problem…
> 
> I’d be grateful if someone gives me a clue where the problem could be :(
> 
Some obvious questions.

You say the interface is correctly configured.
Do you have any routes set in the Windows box?
Do you see traffic outbound on the 10.137.0.50 iface?

If you sniff traffic inbound on the vif attached to the Windows HVM, do
you see anything there? (I mean sniff on the proxyVM)

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

Re: [qubes-users] External monitor resolution

[unman]

On Mon, Sep 24, 2018 at 01:02:50PM -0300, Franz wrote:
> On Qubes 3.2 had to add an External monitor because my Lenovo x230 laptop
> display started flickering and slowing down. But the resolution on the
> external monitor is wrong. What appears on screen is correctly high, but
> too large to fit into the screen.
> 
> Running xrandr gives the output on the enclosed photo. From that I imagine
> that the resolution of the external monitor should be changed to 1366x768.
> 
> But how do I do that? I spent a couple hours reading many old threads, but
> they imply a knowledge I do not have, só cannot figure out. Also am afraid
> of doing something wrong and loosing access to my computer.
> 
> Any idea?

I don't know what was in the photo.
But you should be able to access these settings under the Qubes menu,
System Settings, Display entry.

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

Re: [qubes-users] A few tips on installing Qubes 4.0

['William Pate' via qubes-users]

‐‐‐ Original Message ‐‐‐
On Sunday, September 23, 2018 10:53 PM, Stuart Perkins 
 wrote:

>
>
> On Mon, 24 Sep 2018 02:30:50 +
> "'William Pate' via qubes-users" qubes-users@googlegroups.com wrote:
>
> > ‐‐‐ Original Message ‐‐‐
> > On Sunday, September 23, 2018 8:56 PM, Patrick patr...@runthisproject.com 
> > wrote:
> >
> > > Hi,
> > > I had already istalled 4.0 on my laptop and decided to upgrade a 
> > > workhorse desktop running 3.0. So I just boot to a usb stick with a 
> > > validated 4.0 iso. Actually, that's the first tip, make sure you're using 
> > > the "dd" option when creating the iso (like the doc says anyway). That 
> > > made a big difference in just getting the boot right.
> > > I loaded it, had issues, tweaked some things, wasted time here and there 
> > > but what what worked well was:
> > > 1 - boot to and loading a disk partioner like https://gparted.org/
> > >
> > > -   then I just removed all existing partitions.
> > >
> > > 2 - booting to and load a disk wipe program like killdisk: 
> > > http://www.killdisk.com/
> > > I don't know, I felt like there was just something existing on the disk 
> > > that was causing a problem, and when I erased and wiped the drive and 
> > > then did another 4.0 install it worked perfectly, no issues at all.
> > > PS - I had issues trying to get dban working, for some reason.
> > > Hope that helps some folks.
> > > Patrick
> >
> > My fresh installation of Qubes 4.0 was similarly trouble-free. I put it on 
> > a Dell Latitude E7240 laptop. It took a while. I only partitioned the disk 
> > -- now to just figure out how to extend Qubes' partition over Windows'. Oh, 
> > and more RAM would be nice. (I jumped straight from no-Linux-knowledge to 
> > Qubes. It's taking a while to learn.)
> > Next up: Lenovo W520.
> > William Pate
> > willp...@pm.me
> > 512-947-3311
> > www.wopate.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/5bf26b3e-4c55-4c2e-8885-55e518151ec5%40googlegroups.com.
> > > For more options, visit https://groups.google.com/d/optout.
>
> Kinda like Ross Perot and Donald Trump's political careers...start by running 
> for President.
>
> Just get a good grasp of the architecture of Qubes...separate programs from 
> data with templates...separate tasks with appVMs...restrict network exposure 
> to ONLY the tasks which require it...it works very well as long as you keep 
> that in mind when are working with it.
>
>


Oh, I know I jumped into the deep, deep, deep end first. That's why I don't bug 
people with questions. Trial, error, research, fix, trial, error . . .

Ultimately, I want to use it for security purposes and (hopefully) productivity.


William



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


-- 
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/CCmTiEAR3rvg-mkOWNEDL73of5xy_b_KXyyOMjwy7yLkP63N8md7Hr1v9MDLEUwQhC650wDRt5_RG2Fc06_ZlLMOv83J0Qy9PS6Ri-76F2I%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Re: A method can effectively lock up a VM and any attempt of killing the VM in dom0 lock up the GUI.

[rqwang2018]

On Sunday, 23 September 2018 16:35:55 UTC-4, awokd  wrote:
> rqwan...@gmail.com:
> > On Sunday, 23 September 2018 00:54:26 UTC-4, rqwan...@gmail.com  wrote:
> >> Currently in my work I encountered VM lock-ups that can be reliably 
> >> replayed. And each time I must cold reboot my laptop in order to recover.
> >>
> >> I have allocated 2 VCPUs to the VM and the triggerer process is single 
> >> threaded. However when that happens, Qubes VM Manager shows that 50% of 
> >> the CPU is busy in the mentioned VM. Noticing that my cpu has 4 cores and 
> >> a recent update disabled hyper-threading, certainly some disaster happened 
> >> to the VM. I don't know whether Shutdown VM does its job (I believe it 
> >> should be unlikely), but to make things worse, Kill VM in the Qubes VM 
> >> Manager locked up the GUI and I cannot even use Ctrl+Alt+Fx to open the 
> >> other ttys.
> >>
> >> The lock up is limited to several instructions in userspace.
> >>
> >> Any idea of tracking the problems?
> > 
> > For reference I use Qubes 3.2, and the guest is Fedora 28.
> 
> Does qvm-kill from the command line work any better than the GUI?

qvm-kill cannot kill the locked up VM. As for GUI lock up I don't know how it 
works, it may lock after certain period of time or after I operate on Qubes VM 
Manager; anyway the whole qubes gets locked by the VM _often_.

I used another fedora 26 old VM and got the same result.

-- 
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/6e7ce697-6137-407a-94b2-7218d088479c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Help! qvm-start-gui won't restart properly, so my qube windows are invisible

['floasretch' via qubes-users]

‐‐‐ Original Message ‐‐‐
On Monday, September 24, 2018 6:03 AM, 'awokd' via qubes-users 
 wrote:

> All I'd know to do is reboot- don't know if there's a more elegant way.

Then does Qubes have any way yet to suspend or snapshot VM state, like vmware 
can do? Most of my qubes won't be a problem to reboot after I reboot the 
system, but I have one qube in particular with running state that would be a 
big hassle to re-initialize if I have to reboot the qube.

-- 
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/7N5BlhcjLTldJdHqiy6Fk2Cp6fvrlLvCts1DEs2OdAbv3LY89BawFUBo0euxwS-f6SwH4dHjBcwqE02lRS37oUmON8dhX3Rvm4cerQqktNc%3D%40protonmail.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] XL VM connectivity to Qubes Network

[3mptyy]

Hi,

I’m still working on my Qubes 4.0 migration and I’m trying to connect a Windows 
10 XL created VM to Qubes Networking by adding this kind of line in the hvm 
file :

vif = [ 'mac=00:16:3e:5e:6d:11,model=e1000,
ip=10.137.0.50,script=vif-route-qubes,backend=sys-vpn’ ]

The backend is a functional proxy VM created by following the « Set up a 
ProxyVM as a VPN gateway using iptables and CLI scripts » tutorial

The guest VM is a Windows 10 1804 with Xen paravirtual drivers 8.2.1 installed. 
The e1000 is correctly detected as a Xen adapter with link up and configured 
with IP : 10.137.0.50 / 24, no gateway, I’m just trying to access some HTTP 
services in another qube connected to the same proxyVM. Firewall rules are OK 
because it’s working from a third qube connected to the proxyVM.

The Windows 10 VM is acting like it has no connectivy at all. Can’t connect to 
the HTTP server of my qube. I tried removing all firewall rules in proxyVM and 
qube HTTP server and setting ACCEPT policy for all chains, it doesn’t change 
anything so I think it’s not a firewall problem…

I’d be grateful if someone gives me a clue where the problem could be :(

-- 
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/4bd2169e-3271-4a64-b32d-a29ef03be8dd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Help! qvm-start-gui won't restart properly, so my qube windows are invisible

['awokd' via qubes-users]

'floasretch' via qubes-users:

A qube window that I was using in full-screen mode died and somehow locked up the 
gui in dom0 (totally unresponsive to keyboard & mouse input, except that the 
mouse still moved the pointer), and I had to switch to a text console (ctl-alt-F2) 
and kill xfce to force it to log out and reset the gui.
That worked, but when I logged back in, all of my qube windows (and all the 
dom0 windows I had open, including some terminal emulators) momentarily flashed 
on screen one at a time in rapid succession, then disappeared. Alt-tab doesn't 
show them.

I can, however, start new dom0 windows, e.g. terminal emulator, qube manager, 
etc, and they work properly.
xl list shows all my running qubes are still running, and I can access them 
using xl console, then within them I can use xlsclients and see that everything 
is still running. But if I try to create a new window, e.g. by running xterm, 
nothing appears.

https://github.com/QubesOS/qubes-issues/issues/3147 for an unrelated issue has 
instructions to fix invisible windows:
kill qvm-start-gui process and start it again: qvm-start-gui --all --watch &
But when I do that, all my windows just flash momentarily again, and disappear, 
same as happened when I logged back in.

Using Qubes 4.0 final release, fully updated.

Please help! How can I get my windows back?


All I'd know to do is reboot- don't know if there's a more elegant way.

--
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/a923f80a-b0c1-598d-3dfc-a7a0ee63afb7%40danwin1210.me.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] A few tips on installing Qubes 4.0

[Patrick]

On Sunday, September 23, 2018 at 10:53:12 PM UTC-5, Stuart Perkins wrote:
> On Mon, 24 Sep 2018 02:30:50 +
> "'William Pate' via qubes-users"  wrote:
> 
> >‐‐‐ Original Message ‐‐‐
> >On Sunday, September 23, 2018 8:56 PM, Patrick  
> >wrote:
> >
> >> Hi,
> >>
> >> I had already istalled 4.0 on my laptop and decided to upgrade a workhorse 
> >> desktop running 3.0. So I just boot to a usb stick with a validated 4.0 
> >> iso. Actually, that's the first tip, make sure you're using the "dd" 
> >> option when creating the iso (like the doc says anyway). That made a big 
> >> difference in just getting the boot right.
> >>
> >> I loaded it, had issues, tweaked some things, wasted time here and there 
> >> but what what worked well was:
> >>
> >> 1 - boot to and loading a disk partioner like https://gparted.org/
> >> - then I just removed all existing partitions.
> >>
> >> 2 - booting to and load a disk wipe program like killdisk: 
> >> http://www.killdisk.com/
> >> I don't know, I felt like there was just something existing on the disk 
> >> that was causing a problem, and when I erased and wiped the drive and then 
> >> did another 4.0 install it worked perfectly, no issues at all.
> >>
> >> PS - I had issues trying to get dban working, for some reason.
> >>
> >> Hope that helps some folks.
> >>
> >> Patrick
> >>
> >>  
> >
> >
> >
> >My fresh installation of Qubes 4.0 was similarly trouble-free. I put it on a 
> >Dell Latitude E7240 laptop. It took a while. I only partitioned the disk -- 
> >now to just figure out how to extend Qubes' partition over Windows'. Oh, and 
> >more RAM would be nice. (I jumped straight from no-Linux-knowledge to Qubes. 
> >It's taking a while to learn.)
> >
> >Next up: Lenovo W520.
> >
> >
> >
> >
> >William Pate
> >willp...@pm.me
> >512-947-3311
> >www.wopate.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/5bf26b3e-4c55-4c2e-8885-55e518151ec5%40googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.  
> >
> >
> 
> Kinda like Ross Perot and Donald Trump's political careers...start by running 
> for President.
> 
> Just get a good grasp of the architecture of Qubes...separate programs from 
> data with templates...separate tasks with appVMs...restrict network exposure 
> to ONLY the tasks which require it...it works very well as long as you keep 
> that in mind when are working with it.

Hi Stuart, 
I like your input there, can you say a little more about it? I totally get 
separating tasks with appVMs, restricting network to each task, but say more on 
separating programs from data with templates - what are you doing in your case? 
Also, do you do some networking between the vms, etc?

In my case I'll have maybe some dev tools on a template, then maybe a couple of 
different google profiles on different vms, and of course I'll use the throw 
away browsers on any research I'm doing.

Patrick

-- 
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/b4c3e024-0df7-48ee-9c0e-a0e45a9c0526%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.