octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #65477] Using character '^' starts a 100% cpu


From: John W. Eaton
Subject: [Octave-bug-tracker] [bug #65477] Using character '^' starts a 100% cpu process in gnome wayland
Date: Tue, 19 Mar 2024 14:16:14 -0400 (EDT)

Follow-up Comment #11, bug #65477 (group octave):

Can anyone explain exactly how I might try to reproduce this problem?  On my
system, I see


$ ps axuww | grep -i wayland
jwe       115361  0.0  0.0 162388  5888 tty2     Ssl+ 14:03   0:00
/usr/libexec/gdm-wayland-session env GNOME_SHELL_SESSION_MODE=ubuntu
/usr/bin/gnome-session --session=ubuntu
jwe       115876  0.2  0.4 1331644 79160 ?       Sl   14:03   0:00
/usr/bin/Xwayland :0 -rootless -noreset -accessx -core -auth
/run/user/1000/.mutter-Xwaylandauth.VCH1K2 -listen 4 -listen 5 -displayfd 6
-initfd 7


Does that mean I am using Wayland in the way that is meant in this report?

I normally run Octave builds across an ssh connection (ssh -X to a remote
system, run Octave there and display on the Ubuntu system that is running
Xwayland).  But if it might matter, I can try to build a copy of Octave that
will run locally on my Ubuntu system.

Also if it matters, the version of Xwayland on my system is


$ Xwayland -version
The X.Org Foundation Xwayland Version 22.1.1 (12201001)
X Protocol Version 11, Revision 0


Also, Octave itself doesn't really do anything directly with X/Xorg/Xwayland. 
So it seems likely to me that any issues with those components are likely to
be either problems with libraries used by Octave (Qt or other libraries) or
bugs in Xwayland itself, not bugs in Octave.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?65477>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]