GREAT point Jeff V
about LXDE console. Observe console warnings emitted by most
complex GUI applications that you’ve started in console to see very
quickly its limitations. especially for screen sizing error exceptions
that are not obvious from looking at the application window in some
subtle cases. ( Virtual machines like VirtualBox with extra emulation
that doesnt play nice when seamless GUI Ops at a Local Desktop
Box wrt Host Screen / VM screen translations break stuff even if the
VM windows appear to be all present and proportionally correct )
I did use kconsole too, as I install multiple Desktops as different users
for separation, and to ensure that I’m only loading and running the
most resource hungry components that are needed for any given task
I use oddball arch AMD laptops that (say) have only minor Spectre
issues to contend with when looking at performance tradeoffs with
security mitigations ( these can be turned off in the GNU/linux kernels
with considerable granularity.)
I found that I could actually swap Host F37OS Disks back and forth between
oddball AMD Netbooks and High resource i5/i7 Intel Boxes easily! and look
at the wonderful text summaries reported in temporary logging directories
at a Forensic LiveCD Boot. Finding in some cases the MeltDown+Spectre
full mitigations on those boxes were a much bigger Drag on performance
that the lightweight mitigation single core processors!
It also keeps heavyweight GUI stuff functional when you cant be bothered
with addressing different Graphics Accelerator card issues, and just want
emulation for all to ensure a common performance baseline is used.
I’m LOVING this recent return to Redhat6-9 ancestry Fedora! Wish i’d made
the move sooner.
The above report explains WHY I put (say) a default set KDE plasma Desktop
on a “universal” Testing Host OS that i move back and forth across different
arch variants of x86_64 object code sets.
Hoped that this will be be useful to other readers in the community
My problem is figuring out with any of the CLI based things like dnf
( upgraded yum) OR rpm ( man pages ) How to properly name packages
that are NOT installed.
With deb package systems I can grep the /var/lib/apt/lists that are
effectively a complete list of ALL packages available.
Is there an equivalent thing I can do in this Fedora rpm based Distro?
i.e after every dnf upgrade I assume that the entire package repository
inventory is available : somewhere
where is it?
A workaround for broken dnf-dragora might be to edit the python3
source code to dump a sane simple text based equivalent to a straight
string file, or csv format specific to Fedora that I can study with grep et al
in a command line (remote) terminal if not directly at the keyboard of the
Fedora Build in progress.
Then I dont care that I cant do anything useful locally with the dragora
truncated mess, I’m free to do quick’ndirty stuff with python scripting.
Biggest DELIGHT was finding a fully functional Python 3.11.3 as a recent
update WAY TO GO GUYS!!
I’ve been unable to build IDLE on any of my legacy Devuan/Debian/Ubuntu
LTS workhorse Desktops.
WHAT a JOY that find was!
So I will contribute back at some point my seamonkey based profile that
is a real productivity tool when code cracking Python stuff. The Tab Group
operations and seamless integrated email client and basic html editor
is terrific in keeping critical reference content that may disappear from
search engine listings +3-6 months later. When in deep dive research mode.
HTH Guys. Thanks
PS what dnf package name do I use to get the KDE subset GUI software package
manager and all of its dependancies? It is NOT included in the @KDE Group!!
Anyone that can help me to get cryptmount / dm_crypt working so that I may
copy my sagemath/python Huge encrypted 9+ Years research containers into
the presence of this mighty Python 3.11.3 Beautiful environment will have my
deepest gratitude! ( dnf install )
Nothing I tried worked.