Re: [qubes-users] Witch one is the best?

[Jarrah]

>
> My question is, would some of the newer/faster AMD CPUs and chipsets
> work with Qubes?

I can speak for the 2000 series working. I believe some people have
working 3000 series, but 4000 has been a serious issue. Not sure if
that's the CPU or the specific laptop.

https://qubes-os.discourse.group/t/qubes-support-on-amd-4000-series-lenovo-x13-t14/202/1

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/154d92d0-24d3-ef23-ddb0-cb7e6493b2b3%40undef.tools.

Re: [qubes-users] Witch one is the best?

[Stumpy]

On 2020-08-23 11:21, 'awokd' via qubes-users wrote:

Mélissa Ch.:


Silitech

Intel(R)  Core(TM)  i5-3450 CPU @ 3.10 GHz   3.10GHz

Mémoire 16.0 Go ram

Système d’exploitation 64 bits

Windows 7 Familiale Premium

Carte graphique  ADM Radeon HD 7470


This one is the better Qubes candidate because of the AMD video card and
16GB RAM. Be aware Qubes can sometimes be more challenging to install
than Windows, so might need troubleshooting.



I am planning to put a new system together at some point and saw this 
post when i was looking for AMD related posts.


I have a Radeon card that has the number of ports i need and works fine 
so i dont think i need to worry about graphics.


My question is, would some of the newer/faster AMD CPUs and chipsets 
work with Qubes?


I am more price/performance sensitive than i am "brand loyal" but it 
seems to me that one gets more speed for less money with AMD nowadays so 
was really hoping to get a faster AMD proc with an m2 drive and speedy mem?


Thoughts would be 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/02261781-93cb-763f-2812-87af016ad739%40posteo.net.

[qubes-users] Re: Installation error. Alienware M17 R3, I9 10thgen, rtx 2080, 32Gb ram

[Catacombs]

 "I knew the graphics was going to be an issue as it has always been with 
Nvidia. This time round though i'm at a loss." 

I am probably not as Linux savvy as you, just an experience which might 
give you insight.   I have been working on an Alienware 17 inch, Core I7 
Skylake processor, 16 GB RAM 512 M2, one TB spinning drive.  I have Legacy 
Boot.  I have experienced that I can Not boot after installing to the one 
TB spinning drive, but I can install to the m2, with a test Iso of 4.1 and 
boots, I still have a tab missing to do updates.   Guessing the link to 
updates is broken.I did find that it would not shut down when I was 
still connected to WiFi, I broke connection and it immediately shutdown.

I suspect there is an issue with the  Nividia Graphics card, and Qubes 
4.0.3, I read does not have support for that.  I think I had it working 
though many months ago, but the screen did not show the depth of color that 
Windows 10 had.

That being said, Alienware was not to meant to allow dual boot between 
different OS's, and as you know, the firmware has been dovetailed to 
Windows 10..  Qubes was designed to be the only OS on computer.  Still I 
have Legacy Boot.   

Right now I am using one of the test iso's of 4.1, which has a later kernel 
and a video driver for this Nividia graphics card.

There are several threads on different parts of this subject.   

Not sure what the status is of having an I9 10th generation.  

I doubt if it relates to your issue, I have a fresh install, and the button 
for update does not show up.   I don't see a common denominator to your 
issue.   and I am using a test Iso of 4.1 from about June.  Which is not 
trustworthy from a security stand point.   Keep hoping for a release of 
Qubes 4.1 with Fedora 33.   

I know our developers are very overworked.   I know the real solution to 
these things is to find a way for Qubes Project to have more money, a lot 
more money.   I live on Social Security, so I will not provide the solution 
to overworked, under compensated developers.  

There is another forum.   https://qubes-os.discourse.group\ 



On Friday, September 18, 2020 at 2:08:15 PM UTC-5 kaine wright wrote:

> I'm not completely new to Qubes OS and have it installed on inferior 
> machines before but due to hardware limitations always reverted back to 
> something lighter. This time though i have a pretty decent machine, it runs 
> windows in RAID0 and I have a 2230 form factor m.2 ssd with no raid and 
> this has ubuntu installed. My plan was to get rid of the ubuntu 
> installation and use Qubes. 
>
> I knew the graphics was going to be an issue as it has always been with 
> Nvidia. This time round though i'm at a loss.
>
> I've downloaded a fresh copy of 4.0.3 dd' using Linux and Rufus on 
> windows. Tried both without modification and neither worked. (This is using 
> both 16Gb and an 8Gb because of issues raised about anything higher than 
> 8). 
> Tried to losetup mount the iso but its not possible it complains about the 
> sector not being 512bytes and fails to mount. If i mount it any other way i 
> get the first partition which can not be modified. So only option is to 
> mount the second partition and manually edit; /mnt/EFI/BOOT/BOOTX64.cfg. 
> Remove lines noexitboot=1 and mapbs=1, try again and still failure although 
> i should mention the RGB keyboard does hold its color meaning the loading 
> has finished and something is open. Theres no response to ctrl alt f6 or 
> f2. it will respond to ctrl alt del and the power off button shutting down 
> the installation. One comment that did get me quite far but still jammed 
> the computer was to use a comments answer from QubesOS issue 5165 
> . This managed to 
> get a full but slow output that gave very few warnings until you get to a 
> dracut warning timeout script error. This will happen a few times and then 
> request you copy the error to a usb stick for viewing but at this point 
> nothing but a reboot is possible even after a half hour wait. 
>
> The usb installations are fine and even with the modified settings i can 
> install Qubes on an old machine lying around. Alienware's bios is a bit 
> tricky and it seems Legacy mode has been completely removed leaving only 
> UEFI. Secure boot is disabled but qubes install is unable to detect this. 
> So im kind of lost on what it is i should be doing. Blacklisting nouveau  
> drivers doesn't help much. 
>
> If anyone has experienced this or if i need to give further details please 
> let me know. Logs are difficult to get as they are unable to be saved due 
> to the crashing. 
>
> Warmest regards 
>
> Kaine
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on

[qubes-users] Re: Installation error. Alienware M17 R3, I9 10thgen, rtx 2080, 32Gb ram

[Catacombs]

 "I knew the graphics was going to be an issue as it has always been with 
Nvidia. This time round though i'm at a loss." 

I am probably not as Linux savvy as you, just an experience which might 
give you insight.   I have been working on an Alienware 17 inch, Core I7 
Skylake processor, 16 GB RAM 512 M2, one TB spinning drive.  I have Legacy 
Boot.  I have experienced that I can boot after installing to the one TB 
spinning drive, but I can install to the m2, with a test Iso of 4.1 and 
mostly seems to work.

I suspect there is an issue with the  Nividia Graphics card, and Qubes 
4.0.3, I read does not have support for that.  I think I had it working 
though many months ago, but the screen did not show the depth of color that 
Windows 10 had.

That being said, Alienware was not to meant to allow dual boot between 
different OS's, and as you know, the firmware has been dovetailed to 
Windows 10..  Qubes was designed to be the only OS on computer.  Still I 
have Legacy Boot.   

Right now I am using one of the test iso's of 4.1, which has a later kernel 
and a video driver for this Nividia graphics card.

There are several threads on different parts of this subject.   

Not sure what the status is of having an I9 10th generation.  

I doubt if it relates to your issue, I have a fresh install, and the button 
for update does not show up.   I don't see a common denominator to your 
issue.   and I am using a test Iso of 4.1 from about June.  Which is not 
trustworthy from a security stand point.   Keep hoping for a release of 
Qubes 4.1 with Fedora 33.   

I know our developers are very overworked.   I know the real solution to 
these things is to find a way for Qubes Project to have more money, a lot 
more money.   I live on Social Security, so I will not provide the solution 
to overworked, under compensated developers.  

There is another forum.   https://qubes-os.discourse.group/



On Friday, September 18, 2020 at 2:08:15 PM UTC-5 kaine wright wrote:

> I'm not completely new to Qubes OS and have it installed on inferior 
> machines before but due to hardware limitations always reverted back to 
> something lighter. This time though i have a pretty decent machine, it runs 
> windows in RAID0 and I have a 2230 form factor m.2 ssd with no raid and 
> this has ubuntu installed. My plan was to get rid of the ubuntu 
> installation and use Qubes. 
>
> I knew the graphics was going to be an issue as it has always been with 
> Nvidia. This time round though i'm at a loss.
>
> I've downloaded a fresh copy of 4.0.3 dd' using Linux and Rufus on 
> windows. Tried both without modification and neither worked. (This is using 
> both 16Gb and an 8Gb because of issues raised about anything higher than 
> 8). 
> Tried to losetup mount the iso but its not possible it complains about the 
> sector not being 512bytes and fails to mount. If i mount it any other way i 
> get the first partition which can not be modified. So only option is to 
> mount the second partition and manually edit; /mnt/EFI/BOOT/BOOTX64.cfg. 
> Remove lines noexitboot=1 and mapbs=1, try again and still failure although 
> i should mention the RGB keyboard does hold its color meaning the loading 
> has finished and something is open. Theres no response to ctrl alt f6 or 
> f2. it will respond to ctrl alt del and the power off button shutting down 
> the installation. One comment that did get me quite far but still jammed 
> the computer was to use a comments answer from QubesOS issue 5165 
> . This managed to 
> get a full but slow output that gave very few warnings until you get to a 
> dracut warning timeout script error. This will happen a few times and then 
> request you copy the error to a usb stick for viewing but at this point 
> nothing but a reboot is possible even after a half hour wait. 
>
> The usb installations are fine and even with the modified settings i can 
> install Qubes on an old machine lying around. Alienware's bios is a bit 
> tricky and it seems Legacy mode has been completely removed leaving only 
> UEFI. Secure boot is disabled but qubes install is unable to detect this. 
> So im kind of lost on what it is i should be doing. Blacklisting nouveau  
> drivers doesn't help much. 
>
> If anyone has experienced this or if i need to give further details please 
> let me know. Logs are difficult to get as they are unable to be saved due 
> to the crashing. 
>
> Warmest regards 
>
> Kaine
>

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/2be7cb78-3aef-458f-9aa9-b304e670f521n%40googlegroups.com.

Re: [qubes-users] startx over ssh leads to many new Qubes windows

[unman]

On Sat, Sep 19, 2020 at 12:50:35PM +, 'qubesanon' via qubes-users wrote:
> Hello! I am trying to start X on a different machine (FreeBSD if it matters) 
> over SSH in a Qube VM (nothing fancy, just a Qube based on Fedora 32).
> 
> This works, but every window I open ends up being a new window in Qubes. It's 
> worse than that because UI components also end up as new windows in Qubes. 
> For example, the Xfce panel ends up as a new window too.
> 
> What I'd like to happen is for everything to open in a single window, so 
> there's just a single Qube window and anything that happens in that 
> environment stays in that window. Is that doable?
> 
> Sorry I couldn't find anything in the documentation for this.
> 
> Here's exactly what I do:
> $ ssh -X me@host.
> 
> $ /usr/local/bin/startxfce4 --with-ck-launch
> 
> And then chaos ensues.
> 
> Appreciate any help here, thanks!
> 

It's doing exactly what you are asking to do. The client is forwarding
everything to the Xserver you are sitting at.

What you *want* to do is to see the remote desktop in a window on the
Qubes desktop.
For that you should use a remote desktop tool like vnc, and tunnel it
over ssh. (Search for vnc over ssh and you will find many online
guides.)

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200919232804.GC24307%40thirdeyesecurity.org.

Re: [qubes-users] startx over ssh leads to many new Qubes windows

[Jarrah]

> Here's exactly what I do:
> $ ssh -X me@host.
The `-X` here forwards all X11 windows on the remote host back to your
local machine. Is this your goal?
> $ /usr/local/bin/startxfce4 --with-ck-launch
This will start a bunch of X11 windows, which are then forwarded back to
you.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/977fbcb8-9e88-44f6-5166-a9bd6e42cfc6%40undef.tools.

Re: [qubes-users] Adding new kernels to iso?

[Andrew David Wong]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2020-09-19 7:53 AM, unman wrote:
> [...]
>
> (Also, the documentation should do this by default too.)

Patches welcome. :)

Most links were probably added before the the Mail Archive
mirror existed.

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

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEZQ7rCYX0j3henGH1203TvDlQMDAFAl9mXwgACgkQ203TvDlQ
MDDu0BAAo20deJQ62gk9oLgRkTsOO9aH57VfEHIATqZ+EwxpjuTRrbkDgzwnFJ0l
CwQDhgUPTHkm7MlGDQrQ+2MkF4ujXHzDy5S7HFd+R6EcBR8vHT3HqEEpmng+1jjf
7VBjdj2uVbid8ZCm0cXVuDL0Z+QTtcwKi/lOnnaNdzOEO+qqZ9+2DQ9WlzqJcuKa
UiFoy6qylqUx0r+A/G7A1kvyrkHApjQFj97nzbIF/5HYdpTnqrJRicafRzV+ZMyC
jNn9oK05cbsBvrv8uty8dDa21XR8j1g2N0v6ezKYvW1y4Gml9GyVP9gzKFMgwCGY
NfpusWSMdwb4/TD4rjYzh9sDzxwvx/X2aOeIR54SMB4RT5IY+57kARZL0hfM6J7W
9wVxq+8nFmiPFx4RjHKljbLpI2MtDefkNUWtfoQCJnTh/+vTBT7ACF6zxe3UXwxi
QT5CNpWpDCrJsDikNVHE5lKSmZs7v/tm0ZZyXiKMzphgsSf9nnYCv9Q4pYne6xp0
JhwM0YkrAr81MrV3zZVKKCWOIiVcID5vIqkxooO23fHKK2LbOKTX4TO5swBPfB3Y
1uBWR8S33d22OLO+qdV2wHuYFWoit6sHs8e1airR++h+7AsggwvTql07xthFAo0n
gsxlh85tyBepdQRbmeFn5/w/W+7vTjOBp+aUL4uNEBzLmudoJn0=
=ovo3
-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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/dae9020a-e912-20dd-fbc7-0bf341ab27a3%40qubes-os.org.

Re: [qubes-users] Adding new kernels to iso?

[Ondřej Fiala]

I haven't managed to install Qubes yet (see the first email in this thread). I 
have accessed Google groups through clearnet... Tor can be easily deanonymized 
with JavaScript turned on, so I didn't see any benefit in setting it up outside 
of Qubes for regular browsing.On Sep 19, 2020 18:47, unman 
 wrote:
>
> On Sat, Sep 19, 2020 at 04:00:38PM +0200, Ond??ej Fiala wrote: 
> > I tried opening the link in question on three different occasions and it 
> > required me to log in on all of them, which is why I asked for the summary. 
> > 
> > I agree that linking to a resource that does not (even occasionally) 
> > require login should be preferred. People looking to Qubes for security 
> > often do so to have a secure environment for privacy-enhancing tools such 
> > as Tor, so it's reasonable to expect that a lot of them don't have Google 
> > account.On Sep 19, 2020 14:53, unman  wrote: 
> > > 
> > > On Fri, Sep 18, 2020 at 09:39:30PM +0200, Ond??ej Fiala wrote: 
> > > > Please read more carefully next time -- "Since I don't have Google 
> > > > account 
> > > > which seems to be required to view the initial discussion (*as linked 
> > > > in the 
> > > > first post of the thread*)". The first post says "continuing from 
> > > > discussion 
> > > > at [link to Google groups]" without explaining anything... 
> > > > 
> > > 
> > > It really isn't true that you need a google account to read google 
> > > groups. 
> > > I connect over Tor, and rarely use groups- much prefer to use the mail 
> > > archive ( and you could easily have done this instead of posting snitty 
> > > comments). On the rare occasions that I *have to* use google groups, 
> > > other than enabling jscript, I connect just fine. 
> > > I realise that other users have reported a log in requirement - all I'm 
> > > saying is that it isn't universally applied. 
> > > 
> > > For the record, google groups for qubes-users is available at: 
> > > https://www.mail-archive.com/qubes-users@googlegroups.com/ 
> > > and this provides a searchable archive 
> > > 
> > > It would be desirable if every one linked to the mail archive - is there 
> > > **any** chance that this could become the default? 
> > > (Also, the documentation should do this by default too.) 
>
> Did you do this from the same qube at the same IP address? It's just not 
> my experience using variety of qubes under Tor. If I get a login, I just 
> fire up another qube and try again. 
>
> mail-archive.com undoubtedly helps, and I think it should be the default 
> reference in the docs. I believe that these lists are now echoed to the 
> Forum - perhaps "will be echoed" - I'm not sure of that: I mean I'm not 
> sure of the benefit. 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200919173508.8E76320055F20%40gmmr-3.centrum.cz.

Re: [qubes-users] Adding new kernels to iso?

[unman]

On Sat, Sep 19, 2020 at 04:00:38PM +0200, Ond??ej Fiala wrote:
> I tried opening the link in question on three different occasions and it 
> required me to log in on all of them, which is why I asked for the summary.
> 
> I agree that linking to a resource that does not (even occasionally) require 
> login should be preferred. People looking to Qubes for security often do so 
> to have a secure environment for privacy-enhancing tools such as Tor, so it's 
> reasonable to expect that a lot of them don't have Google account.On Sep 19, 
> 2020 14:53, unman  wrote:
> >
> > On Fri, Sep 18, 2020 at 09:39:30PM +0200, Ond??ej Fiala wrote: 
> > > Please read more carefully next time -- "Since I don't have Google 
> > > account 
> > > which seems to be required to view the initial discussion (*as linked in 
> > > the 
> > > first post of the thread*)". The first post says "continuing from 
> > > discussion 
> > > at [link to Google groups]" without explaining anything... 
> > > 
> >
> > It really isn't true that you need a google account to read google 
> > groups. 
> > I connect over Tor, and rarely use groups- much prefer to use the mail 
> > archive ( and you could easily have done this instead of posting snitty 
> > comments). On the rare occasions that I *have to* use google groups, 
> > other than enabling jscript, I connect just fine. 
> > I realise that other users have reported a log in requirement - all I'm 
> > saying is that it isn't universally applied. 
> >
> > For the record, google groups for qubes-users is available at: 
> > https://www.mail-archive.com/qubes-users@googlegroups.com/ 
> > and this provides a searchable archive 
> >
> > It would be desirable if every one linked to the mail archive - is there 
> > **any** chance that this could become the default? 
> > (Also, the documentation should do this by default too.) 

Did you do this from the same qube at the same IP address? It's just not
my experience using variety of qubes under Tor. If I get a login, I just
fire up another qube and try again.

mail-archive.com undoubtedly helps, and I think it should be the default
reference in the docs. I believe that these lists are now echoed to the
Forum - perhaps "will be echoed" - I'm not sure of that: I mean I'm not
sure of the benefit.

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200919164723.GB30010%40thirdeyesecurity.org.

Fwd: Re: [qubes-users] Adding new kernels to iso?

[Ondřej Fiala]

Forgot to give the list carbon copy, my bad.-- Forwarded message 
--
From: Ondřej Fiala 
Date: Sep 19, 2020 16:00
Subject: Re: [qubes-users] Adding new kernels to iso?
To: unman 
Cc: 

> I tried opening the link in question on three different occasions and it 
> required me to log in on all of them, which is why I asked for the summary.
>
> I agree that linking to a resource that does not (even occasionally) require 
> login should be preferred. People looking to Qubes for security often do so 
> to have a secure environment for privacy-enhancing tools such as Tor, so it's 
> reasonable to expect that a lot of them don't have Google account.On Sep 19, 
> 2020 14:53, unman  wrote:
> >
> > On Fri, Sep 18, 2020 at 09:39:30PM +0200, Ond??ej Fiala wrote: 
> > > Please read more carefully next time -- "Since I don't have Google 
> > > account 
> > > which seems to be required to view the initial discussion (*as linked in 
> > > the 
> > > first post of the thread*)". The first post says "continuing from 
> > > discussion 
> > > at [link to Google groups]" without explaining anything... 
> > > 
> >
> > It really isn't true that you need a google account to read google 
> > groups. 
> > I connect over Tor, and rarely use groups- much prefer to use the mail 
> > archive ( and you could easily have done this instead of posting snitty 
> > comments). On the rare occasions that I *have to* use google groups, 
> > other than enabling jscript, I connect just fine. 
> > I realise that other users have reported a log in requirement - all I'm 
> > saying is that it isn't universally applied. 
> >
> > For the record, google groups for qubes-users is available at: 
> > https://www.mail-archive.com/qubes-users@googlegroups.com/ 
> > and this provides a searchable archive 
> >
> > It would be desirable if every one linked to the mail archive - is there 
> > **any** chance that this could become the default? 
> > (Also, the documentation should do this by default too.) 

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200919140246.D0B3620055B61%40gmmr-4.centrum.cz.

Re: [qubes-users] Adding new kernels to iso?

[unman]

On Fri, Sep 18, 2020 at 09:39:30PM +0200, Ond??ej Fiala wrote:
> Please read more carefully next time -- "Since I don't have Google account
> which seems to be required to view the initial discussion (*as linked in the
> first post of the thread*)". The first post says "continuing from discussion
> at [link to Google groups]" without explaining anything...
> 

It really isn't true that you need a google account to read google
groups.
I connect over Tor, and rarely use groups- much prefer to use the mail
archive ( and you could easily have done this instead of posting snitty
comments). On the rare occasions that I *have to* use google groups,
other than enabling jscript, I connect just fine.
I realise that other users have reported a log in requirement - all I'm
saying is that it isn't universally applied.

For the record, google groups for qubes-users is available at:
 https://www.mail-archive.com/qubes-users@googlegroups.com/
and this provides a searchable archive

It would be desirable if every one linked to the mail archive - is there
**any** chance that this could become the default?
(Also, the documentation should do this by default too.)

-- 
You received this message because you are subscribed to the Google Groups 
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to qubes-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/20200919125345.GE28762%40thirdeyesecurity.org.

[qubes-users] startx over ssh leads to many new Qubes windows

['qubesanon' via qubes-users]

Hello! I am trying to start X on a different machine (FreeBSD if it matters) 
over SSH in a Qube VM (nothing fancy, just a Qube based on Fedora 32).

This works, but every window I open ends up being a new window in Qubes. It's 
worse than that because UI components also end up as new windows in Qubes. For 
example, the Xfce panel ends up as a new window too.

What I'd like to happen is for everything to open in a single window, so 
there's just a single Qube window and anything that happens in that environment 
stays in that window. Is that doable?

Sorry I couldn't find anything in the documentation for this.

Here's exactly what I do:
$ ssh -X me@host.

$ /usr/local/bin/startxfce4 --with-ck-launch

And then chaos ensues.

Appreciate any help here, 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 view this discussion on the web visit 
https://groups.google.com/d/msgid/qubes-users/TUBw_vpTz_j1aSf8-3gdf5AQ-S9ZIv5k32gdGrxEp9x1VzC1XBpGaALXtdlVyatIweISnld9ZJiIVkmWe3iJIl2UEuGbQ1OANOEbh3Mqqss%3D%40protonmail.com.