Bug 32953

this ready to qa, i have already run this with Ventoy/vhd from 1tb usb hdd...

Working on advisory are a lot of src packages

This packages not have i586 version

audiocd-kio-23.04.3-1.mga9.x86_64.rpm
audiocd-kio-devel-23.04.3-1.mga9.x86_64.rpm
lib64audiocdplugins5-23.04.3-1.mga9.x86_64.rpm

It is expected?

The filelight bug in desktops != Plasma is still valid
https://bugs.mageia.org/show_bug.cgi?id=32683#c22

With the issues that have been discovered already this is not yet really ready for QA, but I have asked on the QA ML for testers anyway.

@QA: Until more testing is completed, DO NOT test on a production install. Use only VirtualBox for now, or real hardware installs that aren't necessary for production. Also, I recommend the use of qarepo, but because this is an active bug with issues being corrected as they come up, for now qarepo will work best if the "fuzzy version" feature is enabled.

Sorry katnatek, but I am removing the advisory keyword, as there is at least one srpm version that needs to be changed in it now, and there will most certainly be more before we're done.

Keywords: advisory => (none)
CC: (none) => andrewsfarm

(In reply to Thomas Andrews from comment #5)
> With the issues that have been discovered already this is not yet really
> ready for QA, but I have asked on the QA ML for testers anyway.
> 
> @QA: Until more testing is completed, DO NOT test on a production install.
> Use only VirtualBox for now, or real hardware installs that aren't necessary
> for production. Also, I recommend the use of qarepo, but because this is an
> active bug with issues being corrected as they come up, for now qarepo will
> work best if the "fuzzy version" feature is enabled.
> 
> Sorry katnatek, but I am removing the advisory keyword, as there is at least
> one srpm version that needs to be changed in it now, and there will most
> certainly be more before we're done.

Don't worry I check my work because I make mistakes more often of what I like, I will check again the src.rpm list for the moment I'll remove filelight and move the new src.rpm to bug#32683

(In reply to katnatek from comment #4)
> The filelight bug in desktops != Plasma is still valid
> https://bugs.mageia.org/show_bug.cgi?id=32683#c22
That has just been fixed by an update.

Summary: New Kde Application available for mageia 9 => New Kde Applications available for mageia 9

Correcting the bug assignment to KDE/Plasma, who will pass it to QA when it looks ready. Although I did not see the reason(s) for:
> With the issues that have been discovered already this is not yet really
> ready for QA, but I have asked on the QA ML for testers anyway.

katnatek deserves special thanks for wrestling with what must be an enormous Advisory.
Not to overlook Otto's important comment 1: he has already flown this.

Assignee: bugsquad => kde

Flying here too on four mga9-64 systems.
Including other parts in testing, i.e mesa, nvidia 550, java, and pretesting kernel 6.6.20-1.

No regressions noted yet, will yell if I see one.
Only using Plasma and not tested all parts of course (i.e not Kmail, akonadi, ...)

CC: (none) => fri
Summary: New Kde Applications available for mageia 9 => New KDE Applications available for Mageia 9

MGA9-64 Plasma in VirtualBox. Host system: i5-7500, nVidia Quadro K620, using nvidia-current (550).

No installation issues with the 260 packages. So far, Dolphin is OK, but DragonPlayer only shows a black screen when playing either an mp4 (h.264 codec), or the same file as it came from an old video camera. The original avi file was converted with Handbrake in 2019. 

VLC plays both without issue.

Played from the terminal, I see this:

$ dragon MVI_0350.mp4 
QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int)
QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int)
QObject::connect: No such signal Phonon::VLC::MediaObject::angleChanged(int)
QObject::connect: No such signal Phonon::VLC::MediaObject::availableAnglesChanged(int)
[00007f926c00b0f0] main filter error: Failed to create video converter
QPainter::begin: Paint device returned engine == 0, type: 2
[00007f9274072d50] vdpau_avcodec generic error: Xlib is required for VDPAU

Another Plasma guest, which hasn't received these updates, has the same issue. 3D acceleration is enabled for both guests. The host does not have the problem.

A VirtualBox issue, perhaps?

(In reply to Thomas Andrews from comment #10)

> Another Plasma guest, which hasn't received these updates, has the same
> issue. 3D acceleration is enabled for both guests. The host does not have
> the problem.
> 
> A VirtualBox issue, perhaps?

Disabling 3D acceleration in the guests allows video display.

(In reply to Lewis Smith from comment #8)
> Correcting the bug assignment to KDE/Plasma, who will pass it to QA when it
> looks ready. Although I did not see the reason(s) for:
> > With the issues that have been discovered already this is not yet really
> > ready for QA, but I have asked on the QA ML for testers anyway.
> 
> katnatek deserves special thanks for wrestling with what must be an enormous
> Advisory.
> Not to overlook Otto's important comment 1: he has already flown this.

The hard part (even with papoteur's tool) was put manually the src.rpm, I just wait the official QA stage to edit the src.rpm list, by the moment need to remove filelight and edit dolphin

skrooge is not in the list - oversight or not to be updatd?

CC: (none) => westel

skrooge is not part of the kde-gear stack.

x86_64 multi DE install, running LXDE.

$ kajongg
Traceback (most recent call last):
  File "/usr/bin/kajongg", line 20, in <module>
    from qt import QObject, QCommandLineParser, QCommandLineOption, Qt, QGuiApplication
  File "/usr/share/kajongg/qt.py", line 12, in <module>
    from qtpy import uic
ModuleNotFoundError: No module named 'qtpy'

Should be in next kajongg-23.04.3-1.1.mga9 update!

MGA9-64 Plasma, Phenom II X4 910, AMD HD 8490 graphics.

Updated already installed stuff - 250 packages! No issues. Tried some things, Dolphin, Gwenview, Dragon, Kpat, all worked as they should. 

No sign of the issue I saw in VirtualBox with dragon. That must be an issue with  VirtualBox 3D acceleration. A search of the Net reveals many posts about the subject.

I fired up MCC and installed some of the games - arcade and board. Ran them from the menu, and all seemed to work as designed - though my gaming skills aren't what they were 40 years ago with my Atari 800. (I still have that 800, and it still works...)

So far, so good.

not sure what to make of this one:
there are 2 kalzium .desktop entries.

org.kde.kalzium_cml.desktop
org.kde.kalzium.desktop

one entry in application menu.

org.kde.kalzium.desktop
$kalzium

works fine every time.

org.kde.kalzium_cml.desktop
$ kalzium -qwindowtitle %c -molecule %f
Segmentation fault (core dumped)

4 out of 5 times ( on different hardware / intel & amd CPUs ) above result.
1 out of 5 times works fine.

users would not normally use the above command.

well that explains that.

$ kalzium

clicking the "molecule" button results in a core dump, so, needs to be fixed.

xfce-32 install (64bit capable CPU)

kig segfault:

$ grep -w Exec /usr/share/applications/org.kde.kig.desktop
Exec=kig %U --qwindowtitle %c

$ kig %U --qwindowtitle %c
Segmentation fault (core dumped)
$ kig %U --qwindowtitle
Segmentation fault (core dumped)
$ kig %U
Segmentation fault (core dumped)
$ kig
Segmentation fault (core dumped)

(In reply to Ben McMonagle from comment #18)

kalzium +"molecule button" segfaults on both 32 and 64bit installs.

(In reply to Ben McMonagle from comment #18)
> not sure what to make of this one:
> there are 2 kalzium .desktop entries.
> 
> org.kde.kalzium_cml.desktop
> org.kde.kalzium.desktop
> 
> one entry in application menu.
> 
> org.kde.kalzium.desktop
> $kalzium
> 
> works fine every time.
> 
> org.kde.kalzium_cml.desktop
> $ kalzium -qwindowtitle %c -molecule %f
> Segmentation fault (core dumped)
> 
> 4 out of 5 times ( on different hardware / intel & amd CPUs ) above result.
> 1 out of 5 times works fine.
> 
> users would not normally use the above command.

Apparently this issue come from avogadrolibs and not kalzium itself:

https://bugs.kde.org/show_bug.cgi?id=457191
https://github.com/OpenChemistry/avogadrolibs/issues/1193


Should be fixed now with new avogadrolibs-1.99.0-1.mga9 update:

Packages in 9/Core/Updates_testing:
======================
avogadro2-1.99.0-1.mga9

avogadrolibs-1.99.0-1.mga9
lib64avogadrocalc1-1.99.0-1.mga9
lib64avogadrocore1-1.99.0-1.mga9
lib64avogadroio1-1.99.0-1.mga9
lib64avogadrolibs-devel-1.99.0-1.mga9
lib64avogadromolequeue1-1.99.0-1.mga9
lib64avogadroqtgui1-1.99.0-1.mga9
lib64avogadroqtopengl1-1.99.0-1.mga9
lib64avogadroqtplugins1-1.99.0-1.mga9
lib64avogadroquantumio1-1.99.0-1.mga9
lib64avogadrorendering1-1.99.0-1.mga9
libavogadrocalc1-1.99.0-1.mga9
libavogadrocore1-1.99.0-1.mga9
libavogadroio1-1.99.0-1.mga9
libavogadrolibs-devel-1.99.0-1.mga9
libavogadromolequeue1-1.99.0-1.mga9
libavogadroqtgui1-1.99.0-1.mga9
libavogadroqtopengl1-1.99.0-1.mga9
libavogadroqtplugins1-1.99.0-1.mga9
libavogadroquantumio1-1.99.0-1.mga9
libavogadrorendering1-1.99.0-1.mga9


From SRPMS:
avogadrolibs-1.99.0-1.mga9.src.rpm
avogadro2-1.99.0-1.mga9.src.rpm

(In reply to Ben McMonagle from comment #20)
> xfce-32 install (64bit capable CPU)
> 
> kig segfault:
> 
> $ grep -w Exec /usr/share/applications/org.kde.kig.desktop
> Exec=kig %U --qwindowtitle %c
> 
> $ kig %U --qwindowtitle %c
> Segmentation fault (core dumped)
> $ kig %U --qwindowtitle
> Segmentation fault (core dumped)
> $ kig %U
> Segmentation fault (core dumped)
> $ kig
> Segmentation fault (core dumped)

Does kig only fails on 32bits?

Here it work on my Cauldron 64bis.

(In reply to David GEIGER from comment #23)

> 
> Does kig only fails on 32bits?
> 
> Here it work on my Cauldron 64bis.

yes, 
OK on 64bit
NOK on 32bit

(In reply to David GEIGER from comment #22)
> (In reply to Ben McMonagle from comment #18)
> > not sure what to make of this one:
> > there are 2 kalzium .desktop entries.
> > 
> > org.kde.kalzium_cml.desktop
> > org.kde.kalzium.desktop
> > 
> > one entry in application menu.
> > 
> > org.kde.kalzium.desktop
> > $kalzium
> > 
> > works fine every time.
> > 
> > org.kde.kalzium_cml.desktop
> > $ kalzium -qwindowtitle %c -molecule %f
> > Segmentation fault (core dumped)
> > 
> > 4 out of 5 times ( on different hardware / intel & amd CPUs ) above result.
> > 1 out of 5 times works fine.
> > 
> > users would not normally use the above command.
> 
> Apparently this issue come from avogadrolibs and not kalzium itself:
> 
> https://bugs.kde.org/show_bug.cgi?id=457191
> https://github.com/OpenChemistry/avogadrolibs/issues/1193
> 
> 
> Should be fixed now with new avogadrolibs-1.99.0-1.mga9 update:
> 
> Packages in 9/Core/Updates_testing:
> ======================
> avogadro2-1.99.0-1.mga9
> 
> avogadrolibs-1.99.0-1.mga9
> lib64avogadrocalc1-1.99.0-1.mga9
> lib64avogadrocore1-1.99.0-1.mga9
> lib64avogadroio1-1.99.0-1.mga9
> lib64avogadrolibs-devel-1.99.0-1.mga9
> lib64avogadromolequeue1-1.99.0-1.mga9
> lib64avogadroqtgui1-1.99.0-1.mga9
> lib64avogadroqtopengl1-1.99.0-1.mga9
> lib64avogadroqtplugins1-1.99.0-1.mga9
> lib64avogadroquantumio1-1.99.0-1.mga9
> lib64avogadrorendering1-1.99.0-1.mga9
> libavogadrocalc1-1.99.0-1.mga9
> libavogadrocore1-1.99.0-1.mga9
> libavogadroio1-1.99.0-1.mga9
> libavogadrolibs-devel-1.99.0-1.mga9
> libavogadromolequeue1-1.99.0-1.mga9
> libavogadroqtgui1-1.99.0-1.mga9
> libavogadroqtopengl1-1.99.0-1.mga9
> libavogadroqtplugins1-1.99.0-1.mga9
> libavogadroquantumio1-1.99.0-1.mga9
> libavogadrorendering1-1.99.0-1.mga9
> 
> 
> From SRPMS:
> avogadrolibs-1.99.0-1.mga9.src.rpm
> avogadro2-1.99.0-1.mga9.src.rpm

Can I handle this in other bug?

Yes you can katnatek.

(In reply to David GEIGER from comment #16)
> Should be in next kajongg-23.04.3-1.1.mga9 update!

Thanks David,

now working after update (64bit)

(In reply to Ben McMonagle from comment #27)
> (In reply to David GEIGER from comment #16)
> > Should be in next kajongg-23.04.3-1.1.mga9 update!
> 
> Thanks David,
> 
> now working after update (64bit)

and ok on 32bit

(In reply to Ben McMonagle from comment #24)
> (In reply to David GEIGER from comment #23)
> 
> > 
> > Does kig only fails on 32bits?
> > 
> > Here it work on my Cauldron 64bis.
> 
> yes, 
> OK on 64bit
> NOK on 32bit

after update today, kig is ok on 32bit

Of the 292 applications .desktop files I have tested, the following 7 .desktop files I cannot test via automation:

kcm_breezedecoration
kipiplugins
ktelnetservice5
org.kde.kde-add-printer
org.kde.kdevelop_kdev4
org.kde.krfb.virtualmonitor
org.kde.kwin_rules_dialog

results of manually testing from cli:

kcm_breezedecoration.desktop
The command is :kcmshell5 kcm_breezedecoration
reports:
Could not find module 'kcm_breezedecoration'. See kcmshell5 --list for the full list of modules.

kipiplugins.desktop
kipiplugins is a place holder: 
The command is: ""
Comment is: # "" is necessary to get this entry to show up in khelpcenter.

ktelnetservice5.desktop
The command is: ktelnetservice5 %u
reports:Invalid protocol  ""

org.kde.kde-add-printer.desktop
The command is: kde-add-printer
manually editing the command to: 
kde-add-printer --add-printer
brings up a window - working
(different from kde system settings printer)

org.kde.kdevelop_kdev4.desktop
The command is: kdevelop -p %u
reports
Invalid project: %u - should be either a path to a .kdev4 file or a directory containing a .kdev4 file
kdevplatform.language: Unregistering type class 57
kdevplatform.language: Unregistering type class 58
kdevplatform.language: Unregistering type class 39
kdevplatform.language: Unregistering type class 9
kdevplatform.language: Unregistering type class 20
kdevplatform.language: Unregistering type class 14
kdevplatform.language: Unregistering type class 21
kdevplatform.language: Unregistering type class 7
kdevplatform.language: Unregistering type class 8
kdevplatform.language: Unregistering type class 4
kdevplatform.language: Unregistering type class 3
kdevplatform.language: Unregistering type class 6
kdevplatform.language: Unregistering type class 5
kdevplatform.language: Unregistering type class 2

krfb.virtualmonitor.desktop 
the command is: /usr/bin/krfb-virtualmonitor
reports:
Virtual Monitors are only supported on Wayland

I am not running a wayland session.

org.kde.kwin_rules_dialog.desktop
The command is: kwin_rules_dialog
reports:
bash: kwin_rules_dialog: command not found


I removed from test:

org.kde.mobile.okular_chm.desktop
org.kde.mobile.okular_comicbook.desktop
org.kde.mobile.okular_djvu.desktop
org.kde.mobile.okular_dvi.desktop
org.kde.mobile.okular_epub.desktop
org.kde.mobile.okular_fax.desktop
org.kde.mobile.okular_fb.desktop
org.kde.mobile.okular_ghostview.desktop
org.kde.mobile.okular_kimgio.desktop
org.kde.mobile.okular_md.desktop
org.kde.mobile.okular_mobi.desktop
org.kde.mobile.okular_pdf.desktop
org.kde.mobile.okular_plucker.desktop
org.kde.mobile.okular_tiff.desktop
org.kde.mobile.okular_txt.desktop
org.kde.mobile.okular_xps.desktop

Command for all above: okularkirigami %u
Require a mobile device/platform?

org.kde.akonadi_davgroupware_resource.desktop
org.kde.akonadi_google_resource.desktop
org.kde.akonadi_imap_resource.desktop
org.kde.akonadi_kolab_resource.desktop

Never seen these 4 work via cli.
They have no application menu entry, nor can I "run" them.

MGA9-64 Plasma, HP Probook 6550b, i3-m350, Intel graphics, Broadcom wifi.

Testing on a new system is getting more complicated. I used "*23.04* in qarepo, and that worked OK, but when I went to update in MCC Dolphin couldn't be selected because of a new balloo dependency.(bug 32845) After adding that to the list, there were no installation issues. I don't know what other new dependencies I might have missed because I don't have everything Plasma installed here.

But, so far, so good. All my standards are working OK. 

A new test: I put ktorrent to work downloading a Mageia 9 iso, and it started downloading OK. Running out of battery, so I stopped it before completion, but at least it starts.

Bug 29232 has been closed as OLD. It's a lingering Mageia 8 bug, neither katnatek nor I can reproduce it, and I can't do so in a MGA8 vbox guest.

(In reply to David GEIGER from comment #26)
> Yes you can katnatek.

avogadro2 &  avogadrolibs packages are now in bug#32961

(In reply to katnatek from comment #3)
> This packages not have i586 version
> 
> audiocd-kio-23.04.3-1.mga9.x86_64.rpm
> audiocd-kio-devel-23.04.3-1.mga9.x86_64.rpm
> lib64audiocdplugins5-23.04.3-1.mga9.x86_64.rpm
> 
> It is expected?

David GEIGER I still not see 32b versions of the listed packages

an oversight :( you have to added  libaudiocdplugins5-23.04.3-1.mga9

(In reply to David GEIGER from comment #36)
> an oversight :( you have to added  libaudiocdplugins5-23.04.3-1.mga9

But is not In any mirror , 

I can see https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/i586/media/core/release/libaudiocdplugins5-23.04.1-1.mga9.i586.rpm 

But in testing I just can see

https://distrib-coffee.ipsl.jussieu.fr/pub/linux/Mageia/distrib/9/i586/media/core/updates_testing/audiocd-kio-handbook-23.04.3-1.mga9.noarch.rpm

I just rebuilded audiocd-kio now they will be available in audiocd-kio-23.04.3-1.1.mga9 from audiocd-kio-23.04.3-1.1.mga9.src.rpm

(In reply to David GEIGER from comment #38)
> I just rebuilded audiocd-kio now they will be available in
> audiocd-kio-23.04.3-1.1.mga9 from audiocd-kio-23.04.3-1.1.mga9.src.rpm

That is fine now, thank you

Created attachment 14454 [details]
katnatek's Log of packages updated x86_64

I know still is not officially in QA list

RH mageia 9 x86_64

64 packages updated, I'll use Plasma session after this comment to make test

Created attachment 14455 [details]
katnatek's Log of packages updated i586

RH mageia 9 i586
122 packages updated, not surprise, this system was Plasma only for long time

Start the testing with this message

falkon not works on 32b, this is not a regression the current version have the issue

falkon 
Falkon: Creating new profile directory
Error creating database schema "Consulta vacía No es posible obtener la fila"
Falkon: Python plugin support initialized
Library plugin "KDEFrameworksIntegration.so" not found
Falkon: 1 extensions loaded
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
0383../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 03830383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
alkon 
Falkon: Creating new profile directory
Error creating database schema "Consulta vacía No es posible obtener la fila"
Falkon: Python plugin support initialized
Library plugin "KDEFrameworksIntegration.so" not found
Falkon: 1 extensions loaded
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
0383../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 03830383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383
../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall ../../3rdparty/chromium/sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0383

(In reply to katnatek from comment #43)
> falkon not works on 32b, this is not a regression the current version have
> the issue
split falkon issue in bug#32966 , that bug not must block this update because is something already exists (and perhaps just to happen to me)

list of .destop files whose executeables fail to invoke.
Real 32bit hardware (AMD xp2400+, pre-sse2)
System is a nearly pure Plasma DE, only extra packages are qarepo:



kcm_breezedecoration.desktop
kcm_krunnersettings.desktop
kfmclient.desktop
kfmclient_dir.desktop
kfmclient_html.desktop
kfmclient_war.desktop
kipiplugins.desktop
kmail_view.desktop
konqbrowser.desktop
ktelnetservice5.desktop
marble_kml.desktop
marble_worldwind.desktop
notification-daemon.desktop
org.kde.akonadiconsole.desktop
org.kde.akonadiimportwizard.desktop
org.kde.akregator.desktop
org.kde.angelfish.desktop
org.kde.bomber.desktop
org.kde.cantor.desktop
org.kde.contactprintthemeeditor.desktop
org.kde.digikam.desktop
org.kde.falkon.desktop
org.kde.ghostwriter.desktop
org.kde.granatier.desktop
org.kde.headerthemeeditor.desktop
org.kde.kalendar.desktop
org.kde.kalgebra.desktop
org.kde.kapman.desktop
org.kde.kblocks.desktop
org.kde.kbounce.desktop
org.kde.kde-add-printer.desktop
org.kde.kdevelop_bzr.desktop
org.kde.kdevelop.desktop
org.kde.kdevelop_git.desktop
org.kde.kdevelop_kdev4.desktop
org.kde.kdevelop_ps.desktop
org.kde.kdevelop_svn.desktop
org.kde.kimagemapeditor.desktop
org.kde.klickety.desktop
org.kde.klipper.desktop
org.kde.kmail2.desktop
org.kde.knetwalk.desktop
org.kde.knights.desktop
org.kde.kolf.desktop
org.kde.kollision.desktop
org.kde.kontact.desktop
org.kde.krfb.virtualmonitor.desktop
org.kde.ksame.desktop
org.kde.kshisen.desktop
org.kde.ktplogviewer.desktop
org.kde.kwin_rules_dialog.desktop
org.kde.marble.desktop
org.kde.marble-qt.desktop
org.kde.mboximporter.desktop
org.kde.minuet.desktop
org.kde.neochat.desktop
org.kde.parley.desktop
org.kde.pimdataexporter.desktop
org.kde.plasmatube.desktop
org.kde.sieveeditor.desktop
org.kde.skrooge.desktop
org.kde.systemmonitor.desktop
org.kde.umbrello.desktop
org.strawberrymusicplayer.strawberry.desktop
signon-ui.desktop

org.kde.umbrello.desktop I will have to test manually, as the automated test is designed to strip off the trailing %x. of the executable. (why : reasons) Umbrello will run on a 64bit if just the first part of the executable is invoked ( $ umbrello5 ). just did not have time this morning.

(In reply to katnatek from comment #44)
> (In reply to katnatek from comment #43)
> > falkon not works on 32b, this is not a regression the current version have
> > the issue
> split falkon issue in bug#32966 , that bug not must block this update
> because is something already exists (and perhaps just to happen to me)

is in my list : org.kde.falkon.desktop (comment #45)

apologising in advance for long report:

i586 Plasma install on real h/w.:

$ lscpu
Architecture:           i686
  CPU op-mode(s):       32-bit
  Address sizes:        34 bits physical, 32 bits virtual

  Model name:           AMD Athlon(tm) XP 2400+

    Flags:              fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mm
                        x fxsr sse syscall mmxext 3dnowext 3dnow cpuid 3dnowprefetch vmmcall

 ------------------------------------------------------
 
Results output from bulk tester. (edited for clarity) 
Tests 39 & 42 failed with: Illegal instruction
All others were: Segmentation fault 

------------------------------------------------------

Trying launcher for application: org.kde.akonadiconsole
Test # 1 of 44.

Segmentation fault      (core dumped)
The command is: akonadiconsole
------------------------------------------------

Trying launcher for application: org.kde.akonadiimportwizard
Test # 2 of 44.

Segmentation fault      (core dumped)
The command is: akonadiimportwizard
------------------------------------------------

Trying launcher for application: org.kde.akregator
Test # 3 of 44.

Segmentation fault      (core dumped)
The command is: akregator %u
------------------------------------------------

Trying launcher for application: org.kde.angelfish
Test # 4 of 44.

Segmentation fault      (core dumped)
The command is: angelfish %u
------------------------------------------------

Trying launcher for application: org.kde.bomber
Test # 5 of 44.

No valid processes were found.
The command is: bomber -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.cantor
Test # 6 of 44.

Segmentation fault      (core dumped)
The command is: cantor -qwindowicon cantor -qwindowtitle %c %U
------------------------------------------------

Trying launcher for application: org.kde.contactprintthemeeditor
Test # 7 of 44.

Segmentation fault      (core dumped)
The command is: contactprintthemeeditor
------------------------------------------------

Trying launcher for application: org.kde.digikam
Test # 8 of 44.

Segmentation fault      (core dumped)
The command is: digikam -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.falkon
Test # 9 of 44.

Segmentation fault      (core dumped)
The command is: falkon %u
------------------------------------------------

Trying launcher for application: org.kde.ghostwriter
Test # 10 of 44.

Segmentation fault      (core dumped)
The command is: ghostwriter %f
------------------------------------------------

Trying launcher for application: org.kde.granatier
Test # 11 of 44.

Segmentation fault      (core dumped)
The command is: granatier
------------------------------------------------

Trying launcher for application: org.kde.headerthemeeditor
Test # 12 of 44.

Segmentation fault      (core dumped)
The command is: headerthemeeditor
------------------------------------------------

Trying launcher for application: org.kde.kalendar
Test # 13 of 44.

Segmentation fault      (core dumped)
The command is: kalendar
------------------------------------------------

Trying launcher for application: org.kde.kalgebra
Test # 14 of 44.

Segmentation fault      (core dumped)
The command is: kalgebra %u
------------------------------------------------

Trying launcher for application: org.kde.kapman
Test # 15 of 44.

Segmentation fault      (core dumped)
The command is: kapman
------------------------------------------------

Trying launcher for application: org.kde.kblocks
Test # 16 of 44.

Segmentation fault      (core dumped)
The command is: kblocks -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.kbounce
Test # 17 of 44.

Segmentation fault      (core dumped)
The command is: kbounce -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.kdevelop_bzr
Test # 18 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop --ps --fetch %U
------------------------------------------------

Trying launcher for application: org.kde.kdevelop
Test # 19 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop
------------------------------------------------

Trying launcher for application: org.kde.kdevelop_git
Test # 20 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop --ps --fetch %U
------------------------------------------------

Trying launcher for application: org.kde.kdevelop_kdev4
Test # 21 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop -p %u
------------------------------------------------

Trying launcher for application: org.kde.kdevelop_ps
Test # 22 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop --ps
------------------------------------------------

Trying launcher for application: org.kde.kdevelop_svn
Test # 23 of 44.

Segmentation fault      (core dumped)
The command is: kdevelop --ps --fetch %U
------------------------------------------------

Trying launcher for application: org.kde.kimagemapeditor
Test # 24 of 44.

Segmentation fault      (core dumped).
The command is: kimagemapeditor -qwindowtitle %c %F
------------------------------------------------

Trying launcher for application: org.kde.klickety
Test # 25 of 44.

Segmentation fault      (core dumped)
The command is: klickety -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.kmail2
Test # 26 of 44.

Segmentation fault      (core dumped)
The command is: kmail -qwindowtitle %c %u
------------------------------------------------

Trying launcher for application: org.kde.knetwalk
Test # 27 of 44.

Segmentation fault      (core dumped)
The command is: knetwalk -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.knights
Test # 28 of 44.

Segmentation fault      (core dumped)
The command is: knights -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.kolf
Test # 29 of 44.

Segmentation fault      (core dumped)
The command is: kolf %U
------------------------------------------------

Trying launcher for application: org.kde.kollision
Test # 30 of 44.

Segmentation fault      (core dumped)
The command is: kollision
------------------------------------------------

Trying launcher for application: org.kde.kontact
Test # 31 of 44.

Segmentation fault      (core dumped)
The command is: kontact
------------------------------------------------

Trying launcher for application: org.kde.ksame
Test # 32 of 44.

Segmentation fault      (core dumped)
The command is: klickety --KSameMode -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.kshisen
Test # 33 of 44.

Segmentation fault      (core dumped)
The command is: kshisen -qwindowtitle %c
------------------------------------------------

Trying launcher for application: org.kde.ktplogviewer
Test # 34 of 44.

Segmentation fault      (core dumped)
The command is: ktp-log-viewer %u
------------------------------------------------

Trying launcher for application: org.kde.marble
Test # 35 of 44.

Segmentation fault      (core dumped)
The command is: marble %F
------------------------------------------------

Trying launcher for application: org.kde.marble-qt
Test # 36 of 44.

Segmentation fault      (core dumped)
The command is: marble-qt %F
------------------------------------------------

Trying launcher for application: org.kde.mboximporter
Test # 37 of 44.

Segmentation fault      (core dumped)
The command is: mboximporter %u
------------------------------------------------

Trying launcher for application: org.kde.minuet
Test # 38 of 44.

Segmentation fault      (core dumped)
The command is: minuet
------------------------------------------------

Trying launcher for application: org.kde.neochat
Test # 39 of 44.

Illegal instruction      (core dumped)
The command is: neochat %u
------------------------------------------------

Trying launcher for application: org.kde.parley
Test # 40 of 44.

Segmentation fault      (core dumped)
The command is: parley %u
------------------------------------------------

Trying launcher for application: org.kde.pimdataexporter
Test # 41 of 44.

Segmentation fault      (core dumped)
The command is: pimdataexporter
------------------------------------------------

Trying launcher for application: org.kde.plasmatube
Test # 42 of 44.

Illegal instruction      (core dumped)
The command is: plasmatube
------------------------------------------------

Trying launcher for application: org.kde.sieveeditor
Test # 43 of 44.

Segmentation fault      (core dumped)
The command is: sieveeditor
------------------------------------------------

Trying launcher for application: org.kde.systemmonitor
Test # 44 of 44.

Segmentation fault      (core dumped)
The command is: systemmonitor
------------------------------------------------

(In reply to Lewis Smith from comment #8)
> Correcting the bug assignment to KDE/Plasma, who will pass it to QA when it
> looks ready. Although I did not see the reason(s) for:
> > With the issues that have been discovered already this is not yet really
> > ready for QA, but I have asked on the QA ML for testers anyway.
> 
> katnatek deserves special thanks for wrestling with what must be an enormous
> Advisory.
> Not to overlook Otto's important comment 1: he has already flown this.

I held back from assigning to QA, as it is a very complicated update, with a lot of parts, and I wanted to know that the basic parts were working before enlisting everybody. That seems to be the case, as I have used this on a secondary production system for several days, so I'm re-assigning it to QA. 

Katnatek, you have no idea how much I appreciate the work you have done on this, and continue to do with it.

Testers: Qarepo is your friend! Be sure to use the updated rpm list katnatek has attached, separated by arch, as several problems that were revealed in the original list have been corrected already. Katnatek, I'm relying on you to keep that list up-to-date as more issues are corrected.

If you come across a problem, be sure to check the list of "depends on" bugs to see if it has already been reported. If it has, add your comments to that bug. If not, be sure to report it here. 

Thank you to everyone who has been working on this massive update, and to all those who join us now.

Assignee: kde => qa-bugs

(In reply to Ben McMonagle from comment #45)
> list of .destop files whose executeables fail to invoke.
> Real 32bit hardware (AMD xp2400+, pre-sse2)
> System is a nearly pure Plasma DE, only extra packages are qarepo:
> 
> 
> 
> kcm_breezedecoration.desktop
> kcm_krunnersettings.desktop
> kfmclient.desktop
> kfmclient_dir.desktop
> kfmclient_html.desktop
> kfmclient_war.desktop
> kipiplugins.desktop
> kmail_view.desktop
> konqbrowser.desktop
> ktelnetservice5.desktop
> marble_kml.desktop
> marble_worldwind.desktop
> notification-daemon.desktop
> org.kde.akonadiconsole.desktop
> org.kde.akonadiimportwizard.desktop
> org.kde.akregator.desktop
> org.kde.angelfish.desktop
> org.kde.bomber.desktop
> org.kde.cantor.desktop
> org.kde.contactprintthemeeditor.desktop
> org.kde.digikam.desktop
> org.kde.falkon.desktop
> org.kde.ghostwriter.desktop
> org.kde.granatier.desktop
> org.kde.headerthemeeditor.desktop
> org.kde.kalendar.desktop
> org.kde.kalgebra.desktop
> org.kde.kapman.desktop
> org.kde.kblocks.desktop
> org.kde.kbounce.desktop
> org.kde.kde-add-printer.desktop
> org.kde.kdevelop_bzr.desktop
> org.kde.kdevelop.desktop
> org.kde.kdevelop_git.desktop
> org.kde.kdevelop_kdev4.desktop
> org.kde.kdevelop_ps.desktop
> org.kde.kdevelop_svn.desktop
> org.kde.kimagemapeditor.desktop
> org.kde.klickety.desktop
> org.kde.klipper.desktop
> org.kde.kmail2.desktop
> org.kde.knetwalk.desktop
> org.kde.knights.desktop
> org.kde.kolf.desktop
> org.kde.kollision.desktop
> org.kde.kontact.desktop
> org.kde.krfb.virtualmonitor.desktop
> org.kde.ksame.desktop
> org.kde.kshisen.desktop
> org.kde.ktplogviewer.desktop
> org.kde.kwin_rules_dialog.desktop
> org.kde.marble.desktop
> org.kde.marble-qt.desktop
> org.kde.mboximporter.desktop
> org.kde.minuet.desktop
> org.kde.neochat.desktop
> org.kde.parley.desktop
> org.kde.pimdataexporter.desktop
> org.kde.plasmatube.desktop
> org.kde.sieveeditor.desktop
> org.kde.skrooge.desktop
> org.kde.systemmonitor.desktop
> org.kde.umbrello.desktop
> org.strawberrymusicplayer.strawberry.desktop
> signon-ui.desktop
> 

In this list, discard all what contain NoDisplay=true , are for internal use of Plasma, are for systemsetings5 or other parts of the desktop

curious.

32bit, XFCE install, real h/w.
64bit Plasma install, real h/w.

umbrello invokes from cli ($ umbrello5 ) in both cases.

Does not invoke from the application menu launcher.
likewise, right click the /usr/share/applications/org.kde.umbrello.desktop file and choose execute, does nothing, in both cases.

(In reply to Ben McMonagle from comment #50)
> curious.
> 
> 32bit, XFCE install, real h/w.
> 64bit Plasma install, real h/w.
> 
> umbrello invokes from cli ($ umbrello5 ) in both cases.
> 
> Does not invoke from the application menu launcher.
> likewise, right click the /usr/share/applications/org.kde.umbrello.desktop
> file and choose execute, does nothing, in both cases.

Confirm this, run dolphin in terminal and execute the desktop produce this message

umbrello: Opciones desconocidas: c, a, p, t, i, o, n.
Cannot initialize model with data QJsonObject(). missing: QJsonValue(string, "urls")

Opciones desconocidas = "unknown options"

The Exec line of desktop
umbrello5 %u -caption %c

But the application help not include that option

 LC_ALL=C umbrello5 --help-all
Usage: umbrello5 [options] file
Umbrello – Visual development environment for software, based on the industry standard Unified Modelling Language (UML).<br/>See also <a href="http://www.omg.org/spec/">http://www.omg.org/spec/</a>.

Options:
  -h, --help                           Displays help on commandline options.
  --help-all                           Displays help including Qt specific
                                       options.
  -v, --version                        Displays version information.
  --author                             Show author information.
  --license                            Show license information.
  --desktopfile <file name>            The base file name of the desktop entry
                                       for this application.
  --export <extension>                 export diagrams to extension and exit
  --export-formats                     list available export extensions
  --directory <url>                    the local directory to save the exported
                                       diagrams in
  --import-files                       import files
  --languages                          list supported languages
  --use-folders                        keep the tree structure used to store
                                       the views in the document in the target
                                       directory
  --import-directory <dir>             import files from directory <dir>
  --set-language <proglang>            set language
  --qmljsdebugger <value>              Activates the QML/JS debugger with a
                                       specified port. The value must be of
                                       format port:1234[,block]. "block" makes
                                       the application wait for a connection.
  --platform <platformName[:options]>  QPA plugin. See QGuiApplication
                                       documentation for available options for
                                       each plugin.
  --platformpluginpath <path>          Path to the platform plugins.
  --platformtheme <theme>              Platform theme.
  --plugin <plugin>                    Additional plugins to load, can be
                                       specified multiple times.
  --qwindowgeometry <geometry>         Window geometry for the main window,
                                       using the X11-syntax, like 100x100+50+50.
  --qwindowicon <icon>                 Default window icon.
  --qwindowtitle <title>               Title of the first window.
  --reverse                            Sets the application's layout direction
                                       to Qt::RightToLeft (debugging helper).
  --session <session>                  Restores the application from an earlier
                                       session.
  --display <display>                  Display name, overrides $DISPLAY.
  --name <name>                        Instance name according to ICCCM
                                       4.1.2.5.
  --nograb                             Disable mouse grabbing (useful in
                                       debuggers).
  --dograb                             Force mouse grabbing (even when running
                                       in a debugger).
  --visual <id>                        ID of the X11 Visual to use.
  --geometry <geometry>                Alias for --qwindowgeometry.
  --icon <icon>                        Alias for --qwindowicon.
  --title <title>                      Alias for --qwindowtitle.

Arguments:
  file                                 File to open

The current version of the desktop file not have the -caption option
https://github.com/KDE/umbrello/blob/master/umbrello/org.kde.umbrello.desktop

Created attachment 14466 [details]
Patch to remove '-caption %c' from ubrello desktop file.

$ umbrello5 -caption 'a caption'
umbrello: Unknown options: c, a, p, t, i, o, n.

-caption is not a valid option according to umbrello5 --help.

CC: (none) => davidwhodgins

Created attachment 14467 [details]
Very simple xmi diagram

After removing the '-caption %c' string from the exec line, opening umbrello
works from the menu, and by opening an xmi file with umbrello in dolphin.

I created the xmi file using umbrello, though it has just one entity in it.

(In reply to Dave Hodgins from comment #52)
> Created attachment 14466 [details]


thanks Dave

will await the update in due course.

(In reply to katnatek from comment #51)

this discovered by the applauncher script.
As it was unable to be invoked by applauncher, it meant that a closer look / manual intervention required for this application.  

This is a good reason for using automation is testing bugs like this. there are so many applications / programmes to check, it is unfair to expect QA to test each one manually.

In saying that, it cannot replace your knowledge about those programmes that you are familiar with, so manually testing those popular ones manually also pays off.

Hello everyone!

I have installed the entire update for plasma since yesterday, the applications that I use at the moment work well.

Baloo, dolphin, kdenlive, krita, elisa (I left this one to start using it), Ktorrent.

Updated on Mageia x86_64 with X11 session (Wayland still gives me some problems that are not due to this update).

Version: 9 => Cauldron
Target Milestone: --- => Mageia 10
CC: (none) => joselp
Component: RPM Packages => Security

Skanpage also works correctly for me and the problems reported in bug 32572 have been solved.

https://bugs.mageia.org/show_bug.cgi?id=32572

umbrello desktop file fixed in umbrello-23.04.3-1.1.mga9 from umbrello-23.04.3-1.1.mga9.src.rpm

(In reply to Jose Manuel López from comment #55)
> Hello everyone!
> 
> I have installed the entire update for plasma since yesterday, the
> applications that I use at the moment work well.
> 
> Baloo, dolphin, kdenlive, krita, elisa (I left this one to start using it),
> Ktorrent.
> 
> Updated on Mageia x86_64 with X11 session (Wayland still gives me some
> problems that are not due to this update).

I'm confused. Why did you change this to a Cauldron bug? From the beginning, this was meant to be the last step in the Plasma update for Mageia 9.

Setting flags back.

Version: Cauldron => 9
Component: Security => RPM Packages
Target Milestone: Mageia 10 => ---

(In reply to Morgan Leijström from comment #59)
> Setting flags back.

Well I could have done that. I just wanted to know why he changed them before I did. Seemed like there had to be a reason.

(In reply to David GEIGER from comment #57)
> umbrello desktop file fixed in umbrello-23.04.3-1.1.mga9 from
> umbrello-23.04.3-1.1.mga9.src.rpm

Tested it works from the menu and I can open the file provided by Dave H. from dolphin

Created attachment 14468 [details]
Updated list of packages and src.rpm

Attachment 14453 is obsolete: 0 => 1

(In reply to Ben McMonagle from comment #54)
> (In reply to katnatek from comment #51)
> In saying that, it cannot replace your knowledge about those programmes that
> you are familiar with, so manually testing those popular ones manually also
> pays off.

I don't have any special knowledge of many of the applications, I'm just a person with some curiosity and in the time I have using linux I find run things from terminal provides useful information when something is wrong, in this case if the application complains of "unknown option" the obvious thing for me is search the application options, once confirmed the application not handle the options my next step is found who to "blame" for that mageia or upstream

(In reply to David GEIGER from comment #57)
> umbrello desktop file fixed in umbrello-23.04.3-1.1.mga9 from
> umbrello-23.04.3-1.1.mga9.src.rpm

thanks David _G.
updated applied 
umbrello now invokes from menu application launcher and testing script.

Created attachment 14470 [details]
QA-Repo list of packages used in my testing

Installed in physical hardware.  Turned out to be around 700+ (nearly 800) packages installed.

Testing out quite well.  I think this is in pretty good shape per how I used Plasma.

CC: (none) => brtians1

I went against my own advice, and updated my production install yesterday. I used it all day, off and on, with no issues at all - though I must admit that the only KDE apps I used extensively were Dolphin and Okular, but that's common for me this time of year.

It seems to me that we are very close to sending this on, if I'm not mistaken.

Other than the issues stemming from older i586 hardware, are there any known issues that still need to be fixed? Anything we should be testing that we somehow missed?

(In reply to Thomas Andrews from comment #66)
> I went against my own advice, and updated my production install yesterday. I
> used it all day, off and on, with no issues at all - though I must admit
> that the only KDE apps I used extensively were Dolphin and Okular, but
> that's common for me this time of year.
> 
> It seems to me that we are very close to sending this on, if I'm not
> mistaken.
> 
> Other than the issues stemming from older i586 hardware, are there any known
> issues that still need to be fixed? Anything we should be testing that we
> somehow missed?

I think the worst part is already ironed, we have conformations of other related bugs be fixed by these updates, and Ben "Bug destructor" not report new issues found by his tools.

I not fin nothing in my daily use of Plasma x86_64 neither in my few uses of Plasma in i586, I don't use a lot of kapplications but the few I use works

I will update the advisory later

With no noted objections, I'm sending this on. Giving it OKs on both arches (with the understanding that some apps won't work on some i586 systems because of hardware limitations), and validating.

CC: (none) => sysadmin-bugs
Whiteboard: (none) => MGA9-64-OK MGA9-32-OK
Keywords: (none) => validated_update

ran applauncher into a kde wayland session.

base system was a slimmed down IceWM-session less most applications.
added kf5 update and checked all 33 .desktop executables. (x11 session)
added plasma update and checked the new 198 .desktop executables (x11 session)
added plasmaapps update (this one), changed to wayland session and checked the new 178 .desktop executables.
no difference from x11 session. 

specific fails (5 only) to invoke =>

kipiplugins => placeholder .desktop file: exec=""

org.kde.ConfigurePrinter => requires a printer name  ( configure-printer Generic-PCL-6-PCL-LX ) opens a config window.

org.kde.kde-add-printer => requires a specific parameter and it will open a config window

org.kde.kdevelop_kdev4 requires a kdev4 file to open - I dont have one.

org.kde.krfb.virtualmonitor require a remote monitor  -I dont have access to a remote virtual system.

Did not check application usability.

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2024-0112.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED