Rome 24.07 install questions

Hi:

More problems with this install than I’ve ever had:

24.07 Rome znver for AMD Ryzen
KDE Plasma 6 Wayland

Fresh install on erased 1.82TB M.2 ext4 formatted drive
Updated per recommended Konsole procedure in OM Rome release notes

Asus ProArt X570 Creator Wifi motherboard
ACPI BIOS rev. 0801
16x AMD Ryzen 7 5700G w/Radeon graphics
Speed: 3900 MHz
Total memory: 131072 GB DDE4-2666
M.2_1: WDS200T1X0E-00AFY0 1.82 TB EXT4 drive
US English
US English generic 104 key w/L Enter key keyboard

Konsole update message:

warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.fork(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.wait(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead
warning: posix.exec(): .fork(), .exec(), .wait() and .redirect2null() are deprecated, use rpm.execute() instead

Configuration file ‘/etc/shadow’
-r–r----- 1 root shadow 556 Jul 8 07:53 /etc/shadow.rpmnew
-r–r----- 1 root root 1264 Aug 12 02:46 /etc/shadow

==> Package distributor has shipped an updated version.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version (and delete .rpmsave)
D : show the differences between the versions
M : merge configuration files
Z : background this process to examine the situation
S : skip this file
The default action is to keep your current version.
*** aliases (Y/I/N/O/D/M/Z/S) [default=N] ?
Your choice: Y

(I chose “Y” resulting in normal completion without error message.)

Results:
Ksyslog asks for root password, but fails to open and disappears.
Shut down & restart do nothing
Dolphin won’t open, along with Kate, LibreOffice, Spectacle, and others.

I then tried a full reinstall & update, choosing the “N” option, and got the same result.

After several attempts at forcing a shutdown & restart using the power/reset button, I got an emergency boot message, telling me to open journalctl and to copy the file to a USB thumb drive for analysis, but I didn’t have a convenrient way to do that without being able to boot the system.

I’m thinking that I need some kind of flowchart checklist approach to diagnose this from ground zero level. I remember some old DOS options that would allow you to visually step through each instruction in the AUTOEXEC.BAT file, and receive immediate onscreen notification of the progress with options and results… a least a log output file that I can access to trace the progression for faults. I even redirected the Konsole output to a text file, but althoiugh the file appeared, it was seriously truncated so the entire script was unavailable…

Any suggestions?

This is almost everywhere when speaking of ROME updates:

Yeah, I totally re-installed everything from scratch,erased the drive, and chose the “N” option, and got the same results.

Does that ISO work OK when you boot it ‘Live’? If so one would think something happened during the dnf dsync transaction.

ISO from SourceForge? If from ABF what would be the Build ID #? Edit: Is this x86_64 or znver1 ISO. I would want to know the exact ISO used before I start testing.


I asked the OM devs about this. These warnings can be ignored.

This should have at least corrected the lost password problem.

I have:

CPU:
  Info: 6-core model: AMD Ryzen 5 7530U with Radeon Graphics

Wayland should work fine on my laptop, it has in the past. So a reasonably good machine to try to reproduce the problem/s once I know which ISO to use.

I try:

Install as usual.

sudo dnf --refresh --allowerasing -x kernel-desktop distro-sync 2>&1 |tee rome-dsync.log

Pay attention to console messages, answer N to keep ‘/etc/shadow’ configuration

Reboot

If you notice any malfunctioning please post your newly created rome-dsync.log file
PS>
Also please post informations asked by @ben79

If all looks fine:
sudo dnf --refresh --allowerasing distro-sync 2>&1 |tee rome-dsync2.log

that will now upgrade the kernel if required

This should not happen, but if by chance you get the emergency console message, reboot to CLI mode (Advanced option -or so- in GRUB) and try

sudo dracut -f
sudo update-grub2

Reboot normally.

1 Like

Hi Ben:

I’ll try loading the live version again, test the menu apps for functionality,and report back to you.

Mike

1 Like

Hi Rugyada:

I’m going to load the live version & test the menu apps for Ben, I’ll try your suggestion after that.
Thanks.

Mike

1 Like

Rome 24.07 znver1 test results:

Live version:

  1. LibreOffice = OK

  2. Spectacle = OK

  3. Kate = OK

  4. Dolphin = OK

  5. Chrome = OK

  6. KSystemLog = icon bounces, disappears, program never opens

  7. Restart = OK

Installled before update:
Everything above works.

After update:
None of the above work.

Given the above test results, what is the recommended course of action?

Do what @rugyada suggested here. It is likely something in the dnf dsync transaction so we need those logs.

Also let me know exactly what ISO you used and I can try to reproduce the problem.

Edit: And also if KSystemLog is not working please run ksystemlog from Konsole and post all the output here. If more than 20 lines put in a .txt file and post that. It is working in x86_64 X11 P6 VBox VM.

I think it should require a root password to open. But when opened from Konsole it does not, when opened from Application Menu it does here.

Present state of system is installed but not updated, and everything works fine.
Once I update it, all the problems occur, regardless of if I answer “Y” or “N” to the shadow prompt.

ISO:
OpenMandriva Lx rolling znver1 plasma6 BUILD ID: 3207

KSystemLog (and all other programs) is presently working because I have re-installed the OS from scratch on an erased drive, but have not updated the installation yet.

I already started testing on ROME Wayland znver1 Build ID 3252. Just dsynced. Before rebooting I can not open Dophin, Kate, Lo Impress or Konsole.

Upgraded:
  cpupower-6.10.1-1.znver1                             curl-8.9.0-1.znver1                                    distro-release-OpenMandriva-24.08-1.znver1               
  distro-release-common-24.08-1.noarch                 distro-release-desktop-2:24.08-1.noarch                distro-release-indexhtml-24.08-1.noarch                  
  distro-release-repos-24.08-1.znver1                  distro-release-repos-keys-24.08-1.noarch               distro-release-repos-pkgprefs-24.08-1.noarch             
  distro-release-rpm-setup-24.08-1.noarch              distro-release-theme-24.08-1.noarch                    fastfetch-2.20.0-1.znver1                                
  glibc-6:2.40-1.znver1                                lib64comps0-0.1.21-1.znver1                            lib64curl-8.9.0-1.znver1                                 
  lib64evdev2-1.13.2-1.znver1                          lib64fmt-11.0.2-1.znver1                               lib64input-1.26.1-1.znver1                               
  lib64lz4-1.10.0-1.znver1                             lib64maxminddb0-1.10.0-1.znver1                        lib64ndp-1.9-1.znver1                                    
  lib64nm0-1.48.6-1.znver1                             lib64nss_myhostname-256.4-1.znver1                     lib64nss_resolve-256.4-1.znver1                          
  lib64nss_systemd-256.4-1.znver1                      lib64ostree1-2024.7-1.znver1                           lib64packagekitqt6_5-1.1.2-1.znver1                      
  lib64pci3-3.13.0-1.znver1                            lib64systemd-256.4-1.znver1                            lib64udev-256.4-1.znver1                                 
  lib64udev-devel-256.4-1.znver1                       lib64usbmuxd2.0-2.1.0-0.20230802.1.znver1              lib64v4l1-1.28.0-1.znver1                                
  lib64v4l2-1.28.0-1.znver1                            lib64v4lconvert-1.28.0-1.znver1                        libinput-1.26.1-1.znver1                                 
  locales-6:2.40-1.znver1                              locales-en-6:2.40-1.znver1                             lsb-release-3.2-24.noarch                                
  neovim-0.10.1-1.znver1                               neovim-data-0.10.1-1.noarch                            networkmanager-1.48.6-1.znver1                           
  networkmanager-ppp-1.48.6-1.znver1                   networkmanager-wifi-1.48.6-1.znver1                    om-welcome-2.7.10-1.noarch                               
  ostree-2024.7-1.znver1                               pciutils-3.13.0-1.znver1                               plasma6-ksshaskpass-6.1.3-2.znver1                       
  python-libcomps-0.1.21-1.znver1                      python-pkg-resources-71.0.4-1.noarch                   python-qt5-core-5.15.11-1.znver1                         
  python-qt5-gui-5.15.11-1.znver1                      python-qt5-network-5.15.11-1.znver1                    python-qt5-widgets-5.15.11-1.znver1                      
  python-qt5-xml-5.15.11-1.znver1                      python-setuptools-71.0.4-1.noarch                      python-sip-qt5-12.15.0-1.znver1                          
  systemd-256.4-1.znver1                               systemd-analyze-256.4-1.znver1                         systemd-bash-completion-256.4-1.znver1                   
  systemd-boot-256.4-1.znver1                          systemd-console-256.4-1.znver1                         systemd-coredump-256.4-1.znver1                          
  systemd-cryptsetup-256.4-1.znver1                    systemd-homed-256.4-1.znver1                           systemd-hwdb-256.4-1.znver1                              
  systemd-locale-256.4-1.znver1                        systemd-oom-256.4-1.znver1                             systemd-polkit-256.4-1.znver1                            
  systemd-rpm-macros-256.4-1.znver1                    udev-256.4-1.znver1                                    wpa_supplicant-2.11-1.znver1                             
  xfsprogs-6.9.0-1.znver1                             
Installed:
  kernel-desktop-6.10.1-1.znver1                                                       om-bug-report-0.1-1.noarch                                                      
Reinstalled:
  kf6-kio-6.4.1-1.znver1            kf6-kwidgetsaddons-6.4.1-1.znver1            lib64KF6KIO-6.4.1-1.znver1            lib64KF6WidgetsAddons-6.4.1-1.znver1           

Complete!

Something in that list is probably the culprit. We can probably eliminate the newly installed kernel since I have not rebooted. My first suspects are glibc or systemd.

This ISO is too old: built on July 04 2024. Not the ROME 24.07 officially released.
Just started a new build of the same product.

Except glibc or systemd should not affect system without rebooting so now I think must be something else.

And after reboot?

Ran the following in Konsole per your instruction:

Rebooted, no problems observed, ran the kernel upgrade you posted, finished up by entering the “N” option to the shadow question, completed with no apparent problems.

But hold on…
Now all the menu program choices won’t load again, and the system won’t reboot.

I presume you’ll want the log, but Dolphin is non-operational, so I’ll have to use the CLI to get it.
Mike

Please let me know the best version to download.

1 Like

Edit: I made a mistake and had put @ another user instead of @deltakprime. Woops. :upside_down_face:

@deltakprime or any ROME Wayland P6 user: I did the following 4 steps:

  1. sudo dnf rm krita
  2. sudo dnf swap python-qt5* python-qt6*
  3. sudo dnf reinstall kf6-kio kf6-kwidgetsaddons lib64KF6KIO lib64KF6WidgetsAddons
  4. sudo dnf in krita

And I now have a working, fully dsynced, ROME Wayland Plasma6 znver1 system on my laptop that workswith both installed kernels. At least I have not found anything not working yet.

$ rpm -qa kernel-desktop
kernel-desktop-6.10.0-1.znver1
kernel-desktop-6.10.1-1.znver1

KSystemLog does start from Konsole as ksystemlog. It does not start from Application Launcher.

Wayland is the best, way better than all the rest. :rofl: :smiling_imp:

Application not starting from menu is something I observed the 1 or 2 times I tried wayland (before everything crashed) but I considered due to system installed in vbox virtual machine.
Also observed at that time that the cursor was not really where it looked to, or should, be :upside_down_face:

Yes, looks like other things do not open from Application Launcher. Like the one right under KSystemLog, KWatchGnuPG. Even if I edit the Menu Editor like this:

This is broken and needs a bug report. Or someone needs to report this to OM devs at OpenMandriva Chat or better file a bug report.