![](https://seccdn.libravatar.org/avatar/a836ff90f492078f494adcf0c6059fc6.jpg?s=120&d=mm&r=g)
-pj composed on 2024-05-17 23:23 (UTC-0500):
On 05-17-2024 01:45AM, Felix Miata wrote:
-pj composed on 2024-05-16 23:37 (UTC-0500): ...
Please tell me how to verify that the Tumbleweed snapshot on the machine is fully upgraded. Currently hostnamectl reports 20240515 .
Try just purging stuff you don't need and/or don't use:
zypper pa --unneeded
Then zealously remove....
Is there a need to create a snapshot before doing this (removing)?
You'll need to get someone familiar with snapshot usage to answer that. I'm still using EXTx everywhere except for one ancient laptop for which I was not the openSUSE installer. My brother gave it to me with Leap on BTRFS.
:~> sudo zypper pa --unneeded ... S | Repository | Name | Version | Arch --+-----------------------+------------------------------------+---------------------+------- i | Main Repository (OSS) | accountsservice-lang | 23.13.9-8.1 | noarch i | Main Repository (OSS) | akonadi-plugin-contacts | 24.02.2-1.1 | i586 i | Main Repository (OSS) | akonadi-plugin-mime | 24.02.2-1.1 | i586 ...>> i | Main Repository (OSS) | libLLVM17 | 17.0.6-4.1 | i586 ... i | @System | ruby3.2-rubygem-ruby-dbus | 0.23.1-2.3 | i586 i | @System | ruby3.2-rubygem-simpleidn | 0.2.1-1.8 | i586 i | Main Repository (OSS) | systemd-doc | 255.5-1.1 | noarch paul@localhost:~>
So you are saying to use zypper to remove each of the packages displayed above I think?
I'm saying zypper says removal of all would be a safe operation - nothing remaining would be "broken". None of the packages listed there are required to keep the system operational. Many are packages available in multiple versions, such as libLLVM1# and ruby3.#-rubygem-*. Most people who are not software developers have zero need for multiple versions of the same software installed at once. You may selectively remove only some, leaving behind any you believe you have use for. Installed size of libLLVM17 is 137,703,210, nothing to sneeze at with another almost like it also installed, libLLVM18.
I categorize SDDM as evil here. Its use hijacks vt1 & vt2. BAAAD. I have only about two instances remaining on openSUSE. Everything else (triple digits) uses KDM3, TDM, XDM, or in just a very select few cases, LightDM.
Do you have over 100 machines there?
40-something or other that remain known to be bootable, all multiboot except for the brother's BTRFS 2008 laptop. Median OS installation count per PC is probably in the mid-20s. Max is about 60. I'm typing from one with a mere five. My newest has 17.
I have switched the machine in question here to use XDM now. I cannot see the ability of XDM to allow to select a different X session or Window manager. So I used # update-alternatives --config default-xsession.desktop then I selected option three -> /usr/share/xsessions/plasma6.desktop I have turned off software rendering. Should I have compositing on or off? The taskbar is stable...just that big white box issue.
I don't think Plasma can be made to run anymore with compositing disabled at the X level (as was normal here until 2-3 years ago). If disabling it is desired, it must be done via systemsettings, or via kwinrc: [Compositing] Enabled=false
Consider shooting for something like what I have here for 32bits: # inxi -SMC System: Host: gx28c Kernel: 6.7.7-1-default arch: i686 bits: 32 Console: pty pts/1 Distro: openSUSE Tumbleweed 20240515 Machine: Type: Desktop System: Dell product: OptiPlex GX280 v: N/A serial: 2R0QS71 Mobo: Dell model: 0H8164 serial: ..CN6986155A0396. BIOS: Dell v: A08 date: 03/03/2006 CPU: Info: single core model: Intel Pentium 4 bits: 32 type: MT cache: L2: 1024 KiB Speed (MHz): avg: 2793 min/max: N/A cores: 1: 2793 2: 2793 # df / /home /usr/local Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda17 4839833 3977936 616105 87% / /dev/sda8 2402073 226809 2052369 10% /home /dev/sda10 1016488 789456 174823 82% /usr/local
I do not see which type of graphics but I see your CPU is 2 core p4 32 bit. Which is similar to the T2400 here in ways.
That PC is the first generation of i915 graphics, namesake of the Kernel's aging Intel GPU driver, roughly two years older than your 945, or mine, but my 945s all have either 64 bit operating systems, or a discrete (non-Intel) GPU card installed.
# zypper lr ... # | Alias | Enabled | GPG Check | URI --+----------+---------+-----------+------------------------------------------------------------------------- 1 | KDE3 | Yes | (r ) Yes | http://download.opensuse.org/repositories/KDE:/KDE3/openSUSE_Tumbleweed/ 2 | Non-OSS | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/non-oss 3 | OSS | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/tumbleweed/repo/oss 4 | PackmanE | Yes | (r ) Yes | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_Tumbleweed/Essentials 5 | Update | Yes | (r ) Yes | http://download.opensuse.org/ports/i586/update/tumbleweed/ 6 | openh264 | Yes | (r ) Yes | http://codecs.opensuse.org/openh264/openSUSE_Tumbleweed/
If I change the repos on the machine here to what you have provided above will I be more on track then?
Without knowing your own repo details, that's unanswerable. There's no need for KDE3 unless you intend to use KDM3 to replace SDDM, and/or add KDE3 as a DE selection on your laptop.
Do you suggest KDE3 (as per repo shown above) and not KDE5? KDE5 seemed to be working fairly decent I thought on this machine in question here.
KDE5 has been replaced by KDE6 in TW. KDE3 remained as an option when KDE4 was introduced, kept when KDE5 replaced KDE4, and continues alongside KDE6. It's not an official part of TW, but maintained by very welcome volunteers.
# zypper --no-refresh se -si | grep 'tem Pac' | grep -v plication il | kernel-default | package | 6.7.7-1.1 | i586 | (System Packages) il | kernel-default | package | 6.6.11-1.1 | i586 | (System Packages) il | kernel-default | package | 6.5.9-3.1 | i586 | (System Packages) il | libtag1 | package | 1.13.1-1.3 | i586 | (System Packages) i | libvpx8 | package | 1.13.1-1.2 | i586 | (System Packages) il | xfsprogs | package | 6.1.1-1.1 | i586 | (System Packages)
Your list is not large at all. Why are you not using 6.8.9-1-pae ? Is it
No one has ever persuaded me there's any point to using PAE on systems with 2G or less installed RAM. The 32bit PCs I have with 2G of RAM are at max, can't have more.
because of the matching with your report here -> https://bugzilla.opensuse.org/show_bug.cgi?id=1212696
That report is about i965 graphics, which is part of a chipset for 64 bit CPUs.
# zypper --no-refresh se -si | egrep 'kde|plasma|sddm|gdm|lightdm|kdm' | grep -v block i+ | kde3-gwenview | package | 1.4.2-157.8 | i586 | KDE3 i+ | kde3-kcm_gtk | package | 0.7svn20070827-24.10 | i586 | KDE3 i | kde3-susetranslations | package | 12.1-24.4 | noarch | KDE3 i+ | kdeaddons3-kicker | package | 3.5.10-38.192 | i586 | KDE3 i+ | kdeadmin3 | package | 3.5.10-55.90 | i586 | KDE3 i+ | kdeartwork3 | package | 3.5.10-78.6 | i586 | KDE3 i | kdebase3 | package | 3.5.10.1-380.9 | i586 | KDE3 i+ | kdebase3-apps | package | 3.5.10.1-380.9 | i586 | KDE3 i+ | kdebase3-kdm | package | 3.5.10.1-380.9 | i586 | KDE3 i | kdebase3-ksysguardd | package | 3.5.10.1-380.9 | i586 | KDE3 i | kdebase3-runtime | package | 3.5.10.1-380.9 | i586 | KDE3 i+ | kdebase3-session | package | 3.5.10.1-380.9 | i586 | KDE3 i+ | kdebase3-SuSE | package | 11.3-106.5 | i586 | KDE3 i+ | kdebase3-SuSE-branding-openSUSE | package | 11.3-106.5 | i586 | KDE3 i+ | kdebase3-workspace | package | 3.5.10.1-380.9 | i586 | KDE3 i+ | kdegraphics3 | package | 3.5.10-166.8 | i586 | KDE3 i+ | kdegraphics3-pdf | package | 3.5.10-166.8 | i586 | KDE3 i | kdelibs3 | package | 3.5.10-267.11 | i586 | KDE3 i | kdelibs3-default-style | package | 3.5.10-267.11 | i586 | KDE3 i+ | kdemultimedia3 | package | 3.5.10.1-85.8 | i586 | KDE3 i+ | kdemultimedia3-mixer | package | 3.5.10.1-85.8 | i586 | KDE3 i+ | kdenetwork3-IRC | package | 3.5.10-159.5 | i586 | KDE3 i+ | kdeutils3 | package | 3.5.10-123.9 | i586 | KDE3 i | libQt5Core5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5DBus5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5Gui5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5Network5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5OpenGL5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5Svg5 | package | 5.15.13+kde6-1.2 | i586 | Non-OSS i | libQt5Test5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5Widgets5 | package | 5.15.13+kde138-1.2 | i586 | Non-OSS i | libQt5X11Extras5 | package | 5.15.13+kde0-1.2 | i586 | Non-OSS i+ | systemsettings-kde3 | package | 0.2-11.113 | i586 | KDE3 #
No Plasma, no SDDM, no GDM, no QT6, no Wayland, no Gnome, no bling, no bloat. Lotsa stuff that's been working for decades.
I have a long list of files when I pass the command above.
I'll bet. :)
Perhaps I could start from scratch with the repos you have illuminated above?
It could be easy enough, but best to isolate source of white box with least amount of expended effort first. Does the white box only appear in Plasma? Is it still present if you open IceWM or openbox instead? Is it there if you boot only to multi-user target, then use startx? Is it there if you create a test/virgin user to open a Plasma session? -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata