Hello.  I upgraded my Leap-15.5 installation in Oracle Corporation VM (Virtual
“Machine”) VirtualBox 7.0.18 r162988 (Qt5.15.2) with gratefully well-working
VirtualBox Guest Additions from the last version 5.14.21-150500.55.65.1.x86_64
of the software package kernel-default I had installed in my Leap-15.5
installation to Leap 15.6 with initially the Linux kernel-default, version
6.4.0-150600.21.2.x86_64 in Leap 15.6.  Then on June 21, 2024 the Leap-15.6
Linux kernel kernel-default was updated to version 6.4.0-150600.21.3.x86_64 of
it; and the previous version 6.4.0-150600.21.2.x86_64 of the software package
kernel-default was removed from my Leap-15.6 installation.  In recent years I
have mainly been using the Lightweight X Windows System, Version 11 (X11)
Desktop Environment (LXDE) in installations of 64-bit, openSUSE, Leap, Linux
operating systems installed as so-called “guest” operating systems in
VirtualBox.  And in Leap 15.5 and Leap 15.6 I have in VirtualBox’s “Settings,
Display” been using primarily the Graphics Controller VMSVGA of VirtualBox,
which I think stands for Virtual “Machine” Super Video Graphics Array.  In each
one of those two Linux kernels, versions 6.4.0-150600.21… of kernel-default, in
my Leap-15.6 installation after I had chosen “LXDE desktop session” at the
login screen, entered my regular-user password on that screen, and then pressed
down on my computer’s “Enter” key, initially I could not see my notebook
computer’s touchpad, pointer “arrow” symbol when it should have been seen over
most of the window provided by VirtualBox for Leap 15.6.  (For users of desktop
computers instead of notebook or “laptop” computers I should explain that my
Dell Corporation notebook computer, which looks like what you might call a
“laptop” computer, includes a touchpad instead of a so-called computer “mouse”.
 The movement of one of my fingers over that touchpad is equivalent to the
movement of a so-called “mouse” over a pad.  That is in either case such
movement should be accompanied by the movement a symbol looking like a pointer
“arrow” or “I beam” over the computer screen.  And, just as a computer “mouse”
has at least left and right buttons on it, so my touchpad also has left and
right buttons on the side of it close to me, the user of that touchpad and its
buttons while I face my computer’s Liquid Crystal Display [LCD], screen, or
monitor.)  But interestingly if I moved my invisible touchpad “arrow” symbol
off the LXDE window, it could be seen, say for example, if the touchpad “arrow”
would then be over a part of my VirtualBox-“host”, 64-bit, Windows 10 Home
Edition, operating system’s screen.  I hope to somehow, perhaps by the
assistance of one or more of you readers and/or computer-code developers, to
instead make that pointer “arrow” symbol initially visible over all of the LXDE
window after entering an LXDE desktop session of Leap 15.6.

But to provide clues to a computer-code developers toward eliminating this
touchpad-pointer-”arrow” invisibility over most of the LXDE window, I mention
that there have been some situations in which I could initially see the
pointer-“arrow” symbol over a desktop screen in my Leap-15.6 installation:

1) after entering a Plasma (X11) desktop session instead of an LXDE desktop
session when either one of the Linux kernels kernel-default, version
6.4.0-150600.21.3.x86_64 or 6.4.0-150600.21.2.x86_64 was running; or

2) after entering an LXDE desktop session in my Leap-15.6 installation when the
running Linux kernel was the last version of the Linux kernel I used in my
Leap-15.5 installation before upgrading Leap 15.5 to Leap 15.6, namely
kernel-default, version 5.14.21-150500.55.65.1.x86_64.


So whether the touchpad pointer “arrow” was invisible or not in my Leap-15.6
installation has been both desktop session dependent and kernel-default version
dependent.

Nevertheless, when after realizing that the touchpad-“arrow” symbol was
invisible over the LXDE window in my Leap-15.6 installation, I found a
so-called “workaround” solution to make the touchpad pointer “arrow” become
visible over the LXDE window after entering an LXDE desktop session.  And this,
what-I-have-termed “trick” of mine, might be yet another clue as to where in
the relevant computer source code that the trouble might lie.  My “trick” has
been to move a finger over my computer’s touchpad from right to left and watch
the touchpad-“arrow” symbol correspondingly move from right to left below my
LXDE window.  Then, when that “arrow” symbol was just below the
bottom-left-hand corner of my LXDE window, I probably moved my finger slightly
upward and clicked once with my left, touchpad button.  Though the touchpad
“arrow” was invisible then, had it been seen, I suppose it then would have been
over the “Start button” of my LXDE window.  That clicking made the “Start menu”
appear with options listed on it.  Among those options I could select
“Internet” and then “Konquerer” to open my installation of the Konqueror file
manager.  Shortly after Konqueror’s main window appeared, the touchpad-“arrow”
symbol gratefully became visible over probably anywhere I would want to choose
over the entire LXDE window!  I could even close Konqueror; and that touchpad
“arrow” was still visible over the LXDE window.  (I don’t think that opening
Konqueror in this way was special toward making the touchpad “arrow” become
visible over the entire LXDE window.  For example, later I could use the
beginning of the “trick” to again click on the “Start button,” but afterward,
instead of clicking on “Internet” and then on “Konqueror,” click on “System”,
and then on perhaps “YaST” [Yet another Software Tool] “Software” to make the
touchpad “arrow” become visible over probably the entire LXDE window.)

Toward making the touchpad-“arrow” symbol everywhere and always visible over
the window provided by VirtualBox for an LXDE desktop session in Leap 15.6, I
can imagine a computer-code developer immediately thinking of a place in the
relevant source computer code where the touchpad- or “mouse”-pointer “arrow” is
made visible and the dependent factors which will make it visible or invisible.
 And with the different outcomes of the pointer “arrow” being visible or
invisible in the beginnings of the, respectively, Plasma (X11) or LXDE desktop
sessions I guess that something was properly initialized in a Plasma (X11)
session, but not properly initialized in an LXDE desktop session.

There has been a strange “behavior” in, for my user name “newbie”, the normally
hidden file /home/newbie/.local/share/recently-used.xbel’s owner changing from
“root” to “newbie” or that the file recently-used.xbel with one ownership may
have been deleted and remade with a different ownership.  I have seen
“Permission denied” in /var/log/warn concerning that file, I suppose when its
owner is “root” and it might then have had restricted permissions concerning
what a regular user could do with that file.  However, the purpose of that file
recently-used.xbel is to make a list of applications used, which seems to me to
not be directly related to making the pointer-“arrow” symbol visible or
invisible over the LXDE window.  I read on the Internet that the file
recently-used.xbel is a part of the GNU’s Not Unix (GNU) Image Manipulation
Program (GIMP) Tool Kit (GTK).  But suppose that there is some other file or
directory owned by “root,” with therefore likely restrictions on what a regular
user can do with it, that after I open an application is then owned by “newbie”
or else is deleted and remade with the owner “newbie,” with therefore
imaginably few, if any restrictions on what a regular user can do with it, and
that that file or directory is instead important toward making the pointer
“arrow” symbol become visible over the LXDE window.  Then by a change in
ownership and permissions of that file or directory is one way I can imagine
how the pointer “arrow” might switch from being invisible to being visible over
the entire LXDE window.  But this imagination of mine might not match reality
in the relevant computer code.

Now here is my best guess, which I present in the form of an outline, of a
possible general, not very-specific explanation of the data I presented here.

1.  I suppose that openSUSE code developers receive the source code for a new
kernel version from an organization outside of openSUSE and then modify that
code to make it suitable for an openSUSE environment.

2.  I suppose that there was a change in the source code for the software
package kernel-default from the Leap-15.5 kernel-default version
5.14.21-150500.55.65.1.x86_64 to the new series of Leap-15.6 kernel-default
versions 6.4.0-150600.21….. regarding the initialization of something
concerning the display of the touchpad- or “mouse”-pointer “arrow” over a
Leap-15.6 desktop that required that a corresponding change be made in the
source code for each type of desktop session, for example, Plasma (X11), LXDE,
et cetera, in Leap 15.6.

3.  I suppose that that necessary change was made in the Plasma (X11),
desktop-session, computer source code, but for some reason was not also made in
the LXDE, desktop-session, computer source code.  For example, suppose that the
developers of the Plasma (X11) and LXDE source codes are different human beings
and that at a non-final stage of development the Plasma (X11) code developer
passed along to the LXDE code developer his source code.  From the word
“Lightweight” appearing in the Lightweight X Windows System, Version 11 (X11)
Desktop Environment (LXDE) desktop session I suppose that an LXDE desktop
session is, in a perhaps oversimplified description, a reduced version of a
Plasma (X11) desktop session.  Assuming so, it would make sense for the LXDE
code developer to use as a basis for his code development the Plasma (X11) code
developer’s computer code and afterward to modify it according to the needs of
an LXDE desktop session.  Then suppose that at a later stage of development the
Plasma (X11) code developer realized that he needed to make the change I have
been discussing here in his source code and made it, but neglected to pass
along the news to the LXDE code developer that he needed to make a similar
change in the LXDE code.

I think that I probably have some debugging computer software installed in my
Leap-15.6 installation, based on the names of some online repositories set up
in my Leap-15.6 installation.  But I have not used such debugging computer
software in recent years of time.  In about the year 1998 I wrote some computer
code in the Visual C++, computer programming language.  I guess that much of
the computer code used in an openSUSE Linux operating system might be written
in the C, computer-programming language.  Instead my experience in computer
programming has mainly been in the Fortran, computer-programming language. 
Regarding debugging openSUSE computer source code it would seem good if I would
be familiar with some C, computer-programming language and be able to debug
such code using some debugging computer software that I might already have in
my Leap-15.6 installation.  In this regard I think it might be good if I could
sit down for an hour or so of time with an expert in both the C,
computer-programming language and the use of debugging computer software
available to openSUSE, Leap-15.6, Linux users to have him show me and explain
to me with his computer how he can debug some C-language computer code in an
openSUSE, Leap-15.6 installation.  Or instead I wonder if there would be a
YouTube video provided on the Internet within https://www.youtube.com/… of
someone showing how to use similar debugging computer software to debug
openSUSE computer code, or less desirably, the computer code for some other
distribution of a Linux operating system.