[einar.hjortdal]

Fixed by f965004b426a391b17f58a3ce07319e77727898e

[einar.hjortdal]

That will take me a little while because her systems are at her office and I work at another location, but I will do that and send you a new report.

[einar.hjortdal]

I have reinstalled openmamba using the openmamba-livecd-en-snapshot-20251107.x86_64.iso image and as soon as I opened firefox (for the first time after logging in) I was given the kde wallet password request.
It happens on both Wayland and x11, I use x11 on this one system in particular because of the nvidia_470 package that is not supported by wayland (the nvidia package has its own problems recently according to the reports I’ve submitted).

• This reply was modified 2 weeks ago by einar.hjortdal.

[einar.hjortdal]

It happens on all the systems I installed openmamba on though 🤔

[einar.hjortdal]

Should I attempt to reinstall?

[einar.hjortdal]

Then maybe writing a script that downlaods the binary on the user’s system is the correct thing to do for both vscode and edge

• This reply was modified 2 weeks, 3 days ago by einar.hjortdal.
• This reply was modified 2 weeks, 3 days ago by einar.hjortdal.

[einar.hjortdal]

Actually, isn’t redistribution of vscode also not allowed by their license?
I’ll check out how vscode’s package works

[einar.hjortdal]

No automatic login. Disabled root user login.

[einar.hjortdal]

I believe kwallet-pam is installed by default.
The system I am using right now has some non-default software installed, like nvidia_470, though that shouldn’t touch kwallet.
However, my girlfriend’s secondary system is much simpler: it’s an intel-based laptop with no discrete graphics and no additional software installed.
The issue appeared immediately after install too, before any updates, and persisted after updates.
Should I provide a stack trace using the same method on her laptop? I can do that later today. Let me know if there is more I can provide so I only take over her workstation once today

• This reply was modified 2 weeks, 4 days ago by einar.hjortdal.

[einar.hjortdal]

Silvan wrote:

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.

The kwallet behavior I described happens on both this system, with Microsoft Edge, and on my girlfriend’s system with Firefox.

coredumpctl info -q -r
           PID: 6457 (ksecretd)
           UID: 1000 (einar)
           GID: 1001 (einar)
        Signal: 11 (SEGV)
     Timestamp: Tue 2025-11-04 18:39:48 CET (14h ago)
  Command Line: /usr/bin/ksecretd
    Executable: /usr/bin/ksecretd
 Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/dbus.service
          Unit: user@1000.service
     User Unit: dbus.service
         Slice: user-1000.slice
     Owner UID: 1000 (einar)
       Boot ID: 47ed0ddcb97a447385b37b7837646ae4
    Machine ID: 499600159b1242a489ec6afef12cbf3c
      Hostname: ws00
       Storage: /var/lib/systemd/coredump/core.ksecretd.1000.47ed0ddcb97a447385b37b7837646ae4.6457.1762277988000000.zst (present)
  Size on Disk: 3.1M
       Message: Process 6457 (ksecretd) of user 1000 dumped core.
                
                Stack trace of thread 6457:
                #0  0x00007f38c789e95c n/a (n/a + 0x0)
                #1  0x0000000000000000 n/a (n/a + 0x0)
                ELF object binary architecture: AMD x86-64

Do you want the 3.1M file in /var/lib/systemd/coredump/core.ksecretd.1000.47ed0ddcb97a447385b37b7837646ae4.6457.1762277988000000.zst?
That’s a massive stack trace
I have uploaded it here

• This reply was modified 2 weeks, 4 days ago by einar.hjortdal.
• This reply was modified 2 weeks, 4 days ago by einar.hjortdal.
• This reply was modified 2 weeks, 4 days ago by einar.hjortdal.
• This reply was modified 2 weeks, 4 days ago by einar.hjortdal.

[einar.hjortdal]

Silvan wrote:

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.

I don’t think it’s worth it at that point. I could whip up a script instead

[einar.hjortdal]

I don’t think I’ve ever set a password for the KDE wallet, the password is the same as the user login password. Perhaps it is automatically set to that?

[einar.hjortdal]

Thank you so much

[einar.hjortdal]

No of course there are many lines, I just truncated the last few. But I did find the error, it was above, as you suggested.
I did press the build button below the editor. I don’t even see the other one.
I don’t know the reason why the logs were not matching what I got in the web application before, now they match and are what I’d expect. Thank you for telling me the path of the logs

I have encountered this error now, but I can’t find anything in the log. Do you remember also encountering this error?

RPM build errors:
File not found: /var/autodist/RPM/BUILD/kernel-6.12.37-build/BUILDROOT/lib/modules/6.12.37-2mamba-x86_64/modules.builtin.alias.bin
File not found: /var/autodist/RPM/BUILD/kernel-6.12.37-build/BUILDROOT/lib/modules/6.12.37-2mamba-x86_64/modules.builtin.bin

I tried to upload the log in zst format but I got an error saying I am not allowed to upload this kind of files 😀

I would like to backport this commit to the kernel, because I have a device that would work with this commit that does not work now.
This may be a crazy request but, do you think you could backport this for me?
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/drivers/bluetooth/btusb.c?id=7722d6fb54e428a8f657fccf422095a8d7e2d72c

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

[einar.hjortdal]

Silvan wrote:

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.

You’re right! I found out by piping the output to a file and grepping, because I couldn’t find the log file.

cat /var/autodist/log/logloglog.log | grep Error
make[3]: *** [arch/x86/boot/compressed/Makefile:140: arch/x86/boot/compressed/vmlinux.bin.zst] Error 127
make[2]: *** [arch/x86/boot/Makefile:100: arch/x86/boot/compressed/vmlinux] Error 2
make[1]: *** [arch/x86/Makefile:312: bzImage] Error 2
make: *** [Makefile:224: __sub-make] Error 2

[Author]

Posts