On Friday 24 February 2023 10:03:31 pm Max Nikulin wrote:
> On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:
> > On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
> >> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> >>> So this got me curious, and I tried it out. In the terminal
On 25/02/2023 00:55, Roy J. Tellason, Sr. wrote:
On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
So this got me curious, and I tried it out. In the terminal that's
running inside of the virtualbox instance where I'm doing emails,
On Wednesday 22 February 2023 09:24:17 pm Max Nikulin wrote:
>
> On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
> > On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> >> echo "$DISPLAY"
> >
> > So this got me curious, and I tried it out. In the terminal that's
> > running inside
On 19/02/2023 01:01, Roy J. Tellason, Sr. wrote:
On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
echo "$DISPLAY"
So this got me curious, and I tried it out. In the terminal that's
running inside of the virtualbox instance where I'm doing emails, it
comes back with:
:0
Have
My thanks to David Wright and Max Nikulin.
That was a good wake-up call. Most of my VMs are safe, but it was
interesting to learn what was really going on.
ForwardX11 was enabled for the ssh session. Initially I imagined
vncviewer (to the KVM host though ssh) was the one causing the problem,
On Saturday 18 February 2023 12:17:20 am Max Nikulin wrote:
> echo "$DISPLAY"
So this got me curious, and I tried it out. In the terminal that's running
inside of the virtualbox instance where I'm doing emails, it comes back with:
:0
But in a terminal which is running on the host Debian
On 18/02/2023 08:57, Albert S. wrote:
If you think I issued the xrandr command on the wrong machine, that was
not the case: history makes it clear.
Behavior depends on the DISPLAY environment value at the moment when
xrandr was executed. Likely it was pointed not to vnc Xserver, but to
the
On Fri 17 Feb 2023 at 20:57:38 (-0500), Albert S. wrote:
> Running “xrandr --size 800x600” on a virtual machine affected both
> monitors on my workstation. That was completely unexpected and I am
> wondering how to explain that.
>
> Below you will find the detailed description.
[ … ]
> But my
Running “xrandr --size 800x600” on a virtual machine affected both
monitors on my workstation. That was completely unexpected and I am
wondering how to explain that.
Below you will find the detailed description.
I run KVM on a Debian 11 server, which has no monitor or keyboard
attached to
9 matches
Mail list logo
