Firefox so bad on a remote with 'ssh -YC'

[lejeczek]

Hi guys.

Those of you guys who happen to have remote f34 systems - do 
your remote Firefox via 'ssh -YC' like mine is 'unusable'?
Mine hangs almost immediately, has only brief moments when 
becomes responsive and the reason why I paint specifically 
Firefox as the villain is such, that Chrome and Chrome based 
web browsers, eg. Brave, Chromium, Vivaldi, all work okey.

thanks, L.

[Roger Heflin]

In general with remote apps, how slow they are depends on how "chatty"
they are.     The time to respond to those packets is based on the
ping time to the remote device and sometimes on the total upload
bandwidth on the remote end.

It would be nice if gnome were not "helpful" about telling me my app
is not responding all of the time.  It does get really annoying on
remote usage where bad response is going to be normal.

It is interesting that chrome works better,  I would have to be that
it chats less and/or does its display work completely differently.
Simple design differences in how the graphics are done will make big
differences in how any 2 apps like this work.    On the remotes that
are not good, using it via a VNC X session and the vncviewer will
probably be faster since VNC was intentionally designed to deal with
high latency and it will answer firefox's chats with the local server.

I will have to try that next time I need to use it remote.

On Wed, Sep 15, 2021 at 11:30 AM lejeczek via users
 wrote:
> Hi guys.
>
> Those of you guys who happen to have remote f34 systems - do
> your remote Firefox via 'ssh -YC' like mine is 'unusable'?
> Mine hangs almost immediately, has only brief moments when
> becomes responsive and the reason why I paint specifically
> Firefox as the villain is such, that Chrome and Chrome based
> web browsers, eg. Brave, Chromium, Vivaldi, all work okey.
>
> thanks, L.
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Jonathan Billings]

On Wed, Sep 15, 2021 at 05:30:07PM +0100, lejeczek via users wrote:
> Those of you guys who happen to have remote f34 systems - do your remote
> Firefox via 'ssh -YC' like mine is 'unusable'?
> Mine hangs almost immediately, has only brief moments when becomes
> responsive and the reason why I paint specifically Firefox as the villain is
> such, that Chrome and Chrome based web browsers, eg. Brave, Chromium,
> Vivaldi, all work okey.

I never use a remote firefox process, I just use OpenSSH's built in
proxy support(see below), and have the FoxyProxy Standard extension,
so certain URLs get sent over the SSH proxy.  It makes life a lot
easier, you're only sending browser traffic over the SSH link, not the
entire UI experience.

You can have openssh set up a SOCKS5 proxy via:
    $ ssh -D 5555 server.example.org

Then you just use localhost:5555 as a SOCKS5 proxy.

[Roger Heflin]

Thanks.  I did not know there was that easy of a way to proxy it.
That works much better.

On Wed, Sep 15, 2021 at 2:08 PM Jonathan Billings  wrote:
> On Wed, Sep 15, 2021 at 05:30:07PM +0100, lejeczek via users wrote:
> > Those of you guys who happen to have remote f34 systems - do your remote
> > Firefox via 'ssh -YC' like mine is 'unusable'?
> > Mine hangs almost immediately, has only brief moments when becomes
> > responsive and the reason why I paint specifically Firefox as the villain is
> > such, that Chrome and Chrome based web browsers, eg. Brave, Chromium,
> > Vivaldi, all work okey.
>
> I never use a remote firefox process, I just use OpenSSH's built in
> proxy support(see below), and have the FoxyProxy Standard extension,
> so certain URLs get sent over the SSH proxy.  It makes life a lot
> easier, you're only sending browser traffic over the SSH link, not the
> entire UI experience.
>
> You can have openssh set up a SOCKS5 proxy via:
>     $ ssh -D 5555 server.example.org
>
> Then you just use localhost:5555 as a SOCKS5 proxy.
>
> --
> Jonathan Billings 
> _______________________________________________
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure