• Plasma, XFCE and Chrome

    From William Unruh@2:250/1 to All on Wed Dec 23 03:34:29 2020
    Have just found another difference between Plasma and XFCE. Google Earth
    works in Plasma and does not work in XFCE, at least in the version I
    have.
    I installed Google Earth 7.3.2.5776 (64-bit)
    in Plasma on Mageia 7.1 with Plasma Desktop many months ago
    and it worked fine. Recently, because share in Zoom does not work on
    Plasma (the clients see a flickering/tearing image) I started to use
    XFCE in which Zoom and Sharing does work. Now however, Google earth
    refuses to work and in fact does not start up at all. I gives me an
    error message which implies it cannot authorize itself and asks me to
    check my network (it is fine) and quits. Google Earth does still work
    under Plasma.
    Any hints anyone might have?

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Paul@2:250/1 to All on Wed Dec 23 09:09:37 2020
    William Unruh wrote:
    Have just found another difference between Plasma and XFCE. Google Earth works in Plasma and does not work in XFCE, at least in the version I
    have.
    I installed Google Earth 7.3.2.5776 (64-bit)
    in Plasma on Mageia 7.1 with Plasma Desktop many months ago
    and it worked fine. Recently, because share in Zoom does not work on
    Plasma (the clients see a flickering/tearing image) I started to use
    XFCE in which Zoom and Sharing does work. Now however, Google earth
    refuses to work and in fact does not start up at all. I gives me an
    error message which implies it cannot authorize itself and asks me to
    check my network (it is fine) and quits. Google Earth does still work
    under Plasma.
    Any hints anyone might have?

    There are controls galore in sync-to-retrace country.

    https://www.reddit.com/r/kde/comments/99ykiw/screen_tearing_with_kde/

    The last post in the thread mentions that Chrome is always
    synchronized to retrace (to avoid tearing for things it
    has control over). Now, if a source of frames from somewhere
    which is not synchronous to your 60FPS refresh rate comes
    along, who knows what will happen.

    This is an example of one of the settings, that in the
    past would have fixed tearing at the whole-screen level.
    I don't know if Nouveau has the same sort of setting, a
    Sync to VBlank to reduce tearing.

    "nvidia-settings ... disable Sync to VBlank"

    One disturbing trend I've seen on computers, is the
    removal of dedicated C code for something, and replacement
    with an entire web browser engine module, so that the project
    can be turned into Javascript/HTML spaghetti. When you install
    a software now, be aware that some of the things you're installing
    are private browsers in disguise and may inherit whatever
    table manners the browser happens to have, as a side effect.

    Paul

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Wed Dec 23 18:01:24 2020
    On 2020-12-23, Paul <nospam@needed.invalid> wrote:
    William Unruh wrote:
    Have just found another difference between Plasma and XFCE. Google Earth
    works in Plasma and does not work in XFCE, at least in the version I
    have.
    I installed Google Earth 7.3.2.5776 (64-bit)
    in Plasma on Mageia 7.1 with Plasma Desktop many months ago
    and it worked fine. Recently, because share in Zoom does not work on
    Plasma (the clients see a flickering/tearing image) I started to use
    XFCE in which Zoom and Sharing does work. Now however, Google earth
    refuses to work and in fact does not start up at all. I gives me an
    error message which implies it cannot authorize itself and asks me to
    check my network (it is fine) and quits. Google Earth does still work
    under Plasma.
    Any hints anyone might have?

    There are controls galore in sync-to-retrace country.

    https://www.reddit.com/r/kde/comments/99ykiw/screen_tearing_with_kde/

    Unfortunately that does not help with the Google Earth problem.
    (It was not helped by my putting Chrome in the Subject, rather than what
    I meant which was Google Earth).
    The "flicker/tearing" was a very bad translation of the reality in Zoom,
    in which large blocks of the window I was sharing were replaced with the desktop background at a rate of about 1to 5 times per second. This is
    not really tearing (it is large blocks not individual lines, and is
    replacement of those blocks with the background Desktop), nor
    flickering, and is not a problem on my own machine but the computers of
    others who are trying to look at the window I am sharing. On my computer
    the Zoom sharing looks completely fine. No problems at all. On all of
    the people who are watching my share on Zoom on their machines--
    Windows, Mac, all brands of Linux with all types of video cards-- see
    this block replacement of parts of the window being shared with the
    Desktop background from my machine at a rate of a few per second.
    Ie, when Zoom reads the window from my machine, for sending out to
    others, it seems that there is a mismatch and instead of sending out the
    window it is supposed to it sends out the desktop "behind" the window.
    And this occurs in blocks-- each block about 1/4 of the size of the
    window and it tends to be along the outer edges of the window, and the
    center block is rarely replaced.


    The last post in the thread mentions that Chrome is always
    synchronized to retrace (to avoid tearing for things it
    has control over). Now, if a source of frames from somewhere
    which is not synchronous to your 60FPS refresh rate comes
    along, who knows what will happen.

    As I said, on my machine in Zoom everything is OK, it is others with
    whom I am sharing that see this mess. It is also recorded.


    Anywhaty this behaviour of Zoom is not the purpose of this thread. It is
    the behaviour of Google Earth-- it refuses to start with an error
    message in XFCE but works fine in Plasma.


    This is an example of one of the settings, that in the
    past would have fixed tearing at the whole-screen level.
    I don't know if Nouveau has the same sort of setting, a
    Sync to VBlank to reduce tearing.

    "nvidia-settings ... disable Sync to VBlank"

    I have a Intel onboard graphics


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Paul@2:250/1 to All on Fri Dec 25 18:29:45 2020
    William Unruh wrote:

    Unfortunately that does not help with the Google Earth problem.
    (It was not helped by my putting Chrome in the Subject, rather than what
    I meant which was Google Earth).
    The "flicker/tearing" was a very bad translation of the reality in Zoom,
    in which large blocks of the window I was sharing were replaced with the desktop background at a rate of about 1to 5 times per second. This is
    not really tearing (it is large blocks not individual lines, and is replacement of those blocks with the background Desktop), nor
    flickering, and is not a problem on my own machine but the computers of others who are trying to look at the window I am sharing. On my computer
    the Zoom sharing looks completely fine. No problems at all. On all of
    the people who are watching my share on Zoom on their machines--
    Windows, Mac, all brands of Linux with all types of video cards-- see
    this block replacement of parts of the window being shared with the
    Desktop background from my machine at a rate of a few per second.
    Ie, when Zoom reads the window from my machine, for sending out to
    others, it seems that there is a mismatch and instead of sending out the window it is supposed to it sends out the desktop "behind" the window.
    And this occurs in blocks-- each block about 1/4 of the size of the
    window and it tends to be along the outer edges of the window, and the
    center block is rarely replaced.

    The last post in the thread mentions that Chrome is always
    synchronized to retrace (to avoid tearing for things it
    has control over). Now, if a source of frames from somewhere
    which is not synchronous to your 60FPS refresh rate comes
    along, who knows what will happen.

    As I said, on my machine in Zoom everything is OK, it is others with
    whom I am sharing that see this mess. It is also recorded.

    I'm able to run Chromium-browser without any messages
    being thrown here. I got off to a bad start using the 4GB
    Mageia disc (which I had in my collection already), and the
    2.5GB one installed much better, with less drama. The other
    one was a dumpster file (black screen at start, usual problems
    as seen in my serial link console which I debug with).

    Once selecting the more reasonable install disc

    Mageia-7.1-Live-GNOME-x86_64.iso
    2,703,861,760 bytes
    SHA1: 35E3E4294A47029509A0A5F0A6FF68CAAB24E323

    this is what I see.

    https://i.postimg.cc/YqdZdRDp/chromium-browser.gif

    ( via https://postimage.org )

    Paul

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Sat Dec 26 19:46:01 2020
    On 2020-12-25, Paul <nospam@needed.invalid> wrote:
    William Unruh wrote:

    Unfortunately that does not help with the Google Earth problem.
    (It was not helped by my putting Chrome in the Subject, rather than what
    I meant which was Google Earth).

    And suddenly Google-Earth works fine on XFCE. The bug, whatever it was, seems to have been temporary.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)