[Silvan]

The new received report is about a Intel Core 3 CPU based hardware. The log shows a series of crashed which would suggest investigation:

Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/bin/gpg-agent" 6821 ""
Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/bin/gpg-agent" 6922 ""
Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/bin/gpg-agent" 7134 ""
Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/bin/kwalletmanager5" 9204 "/var/lib/systemd/coredump/core.kwalletmanager5.1000.2c0861e734744eaca96288c02f4e69c1.9204.1756379708000000.zst"
Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/libexec64/drkonqi" 9252 "/var/lib/systemd/coredump/core.drkonqi.1000.2c0861e734744eaca96288c02f4e69c1.9252.1756379709000000.zst"
Nov 10 08:52:26 lptp drkonqi-coredump-processor[5184]: "/usr/libexec64/drkonqi" 9251 "/var/lib/systemd/coredump/core.drkonqi.1000.2c0861e734744eaca96288c02f4e69c1.9251.1756379709000000.zst"

A useful backtrace for these coredumps would be necessary. Unfortunately
– the packages installation log shows that the last package was updated on October 20, in order to try to install the needed debug packages they should be aligned with current repositories, so the system should be updated first
– drkonqi itself is crashing so no crash helper would be available on the desktop

I suggest to update the system, try to install some debug package like:
sudo dnf install gnupg2-debug kwalletmanager-debug qt6-qtbase-debug

reboot, reproduce the problem and generate a new report. By having the system up-do-date the more recent coredumps can be shared in order to try to obtain a useful stack trace.
The more useful would be the one related to gpg-agent as is it probably the cause of the subsequent kwalletmanager5 crash, but first it has to be confirmed that after the system upgrade it gets these same processes to crash.

• This reply was modified 1 week, 6 days ago by Silvan.
• This reply was modified 1 week, 6 days ago by Silvan.

[Silvan]

While the nvidia-470 installation may have a history of its own, I suppose the Ryzen PC is running with standard drivers and you are reporting the kwallet problem as present on both. By the way it seems you only sent reports of the nvidia-470 PC. A report from the Ryzen PC might be useful to try to make a diagnosis of the problem.

[Silvan]

I’ve tried today’s livecd, installed the system on VirtualBox, rebooted, logged in, run firefox and did not get any kde wallet password request. I also tried logging in with plasma-x11 and did not reproduce the problem either.

[Silvan]

Additionaly, code can be installed by following the same instructions for RPM based distributions on this page . A Microsoft dnf repository is set and will provide the updates, this is the way Skype could be used until it was dismissed.

sudo rpm --import https://packages.microsoft.com/keys/microsoft.asc
echo -e "[code]\nname=Visual Studio Code\nbaseurl=https://packages.microsoft.com/yumrepos/vscode\nenabled=1\nautorefresh=1\ntype=rpm-md\ngpgcheck=1\ngpgkey=https://packages.microsoft.com/keys/microsoft.asc" | sudo tee /etc/yum.repos.d/vscode.repo > /dev/null
sudo dnf install code

You may need to remove visual-studio-code-bin before to avoid conflicts.

Edge is currently only distributed in .deb format so the above mechanism is not applicable.

[Silvan]

openmamba has already a project called netsrpms which provides support for local download and RPM packaging of components which cannot be distributed. Adding support for vscode and edge is now in my TODO list.

[Silvan]

By doing a quick check the license might not allow binary distribution of vscode either, although other official sources like this page seem to be permissive when citing some distributions.
While I need to do further checks when I have time I have removed the visual-studio-package from openmamba repository as a precaution.

[Silvan]

I will do an installation test with the latest livecd ISO image. Did you set automatic login on your installations?

[Silvan]

I cannot get a useful stacktrace.
This and this are reports to a similar problem.
I assume that no system changes have been made and the package kwallet-pam is installed.
If it is a general openmamba problem it should be reproduced by me or reported by other users when updating existing installations or doing a fresh installation but the fact that this is happening only to you and on two installations suggests to investigate on any post installation operation you have made on both systems, for example the installation of any external software might have changed the /etc/pam.d files and as written above it seems that the problem is at PAM level.

[Silvan]

The report you sent (related to another problem) shows a crash of the ksecretd daemon. I don’t know if it is the same installation of this post, in any case it might be worth to see a useful stacktrace of the crash dump. As an example the following console commands might produce the stacktrace as output:

sudo dnf install kf6-kwallet-debug
coredumpctl info -q -r

[Silvan]

I’ve checked but the license does not allow to redistribute Microsoft Edge binaries in a public repository.
By the way it might be provided as an openmamba installable component from network, a specific mechanism which locally downloads the upstream archive and creates the RPM. However this requires some more effort than simply creating the package for the repository so I will evaluate doing this work when possible.

The process of updating packages is managed by a chain of openmamba specific tools called autospec, autodist and webbuild which are today provided in a ready-to-use docker environment with the openmamba-docker-buildvm project. This project provides a web interface and scripts that are periodically run to do batch operations like checking for packages to be updated, build them and release to a repository.

• This reply was modified 2 weeks, 5 days ago by Silvan.

[Silvan]

Hi,
this would normally happen because the user has set a password for KDE Wallet. You may want to try to open KWalletManager and change the password by setting an empty one.

[Silvan]

Hi,
I’ve updated the kernel to version 6.12.49 and I have included the patch you requested.
The missing files resulting from your build probably are related to a missing dependency that would result by examinating the full build log, maybe kmod.

[Silvan]

You only see a tenth of lines in the Console output box? There should be hundreds if not thousands of lines since the beginning of rpmbuild… maybe the scrollbar is not working?
About not seeing anything “relevant” in /var/webbuild/tmp, did you by chance use the “build” button below the editor or the autodist “build” button in the right?
Additionally, if you clicked on the [x] on the line in the top processes box, then the build log (if done using the “build” button below the editor) is gone.

• This reply was modified 1 month, 3 weeks ago by Silvan.
• This reply was modified 1 month, 3 weeks ago by Silvan.

[Silvan]

Addition: as most builds are parallelized you often won’t find the error at the very bottom of the build log. By scrolling up the “Console log” you might find the error information many lines before the end. The Console box tries to help by evidencing possible error lines using a red background.

[Silvan]

When you build a SRPM using the build button of the **Webbuild** you get the build process in a line in the top box. When build is finished by clicking on this line you get the full scrollable build log in the “Console output” box. The build logs for the processes in the top, which you can show in the console output box, are the files located in /var/webbuild/tmp. Or are you looking for something else?

[Author]

Posts