I have installed Manjaro (Gnome) on my company notebook which is rolled out in a domain. After the update, the sssd service could no longer be started. As a result, I could no longer log in with my user. I suspect that it has something to do with the samba update.
I have now switched to “unstable”, the login works again, but I can no longer access samba shares.
One thing I have noticed is that some info is missing from acpi -V output; notably it used to show the manufacturer (Sanyo). Using 6.6LTS kernel. I’ll try this with other installed kernels when I get a suitable opportunity.
$ acpi -V
Battery 0: Not charging, 95%
Battery 0: design capacity 3840 mAh, last full capacity 3839 mAh = 99%
Adapter 0: on-line
Thermal 0: ok, 49.0 degrees C
Thermal 0: trip point 0 switches to mode critical at temperature 200.0 degrees C
Cooling 0: Processor 0 of 10
Cooling 1: Processor 0 of 10
Cooling 2: x86_pkg_temp no state information available
Cooling 3: Processor 0 of 10
Cooling 4: intel_powerclamp 0 of 100
Cooling 5: Processor 0 of 10
I don’t know if it was from this or a previous update or remember what other details were shown.
(Note there is no issue with the battery, it looks to be in great health and I do have the charge threshold set to 95% currently).
A post was split to a new topic: Transmission-gtk crashes after within a minute of starting it
A post was split to a new topic: Pamac won’t start anymore
3 posts were split to a new topic: Ata: libata-scsi: Sense data errors breaking hdparm with WD drives
had the same issue, resolved downgrading
Hello, I am currently using nvidia + kernel 6.9 so I tried installing kernel 6.6 before the update but I am not able to. Using the UI gives me the following message:
The following packages will be installed:
linux66
linux66-nvidia
Starting
resolving dependencies...
looking for conflicting packages...
:: installing nvidia-utils (550.107.02-1) breaks dependency 'nvidia-utils=550.90.07' required by lib32-nvidia-utils
:: installing nvidia-utils (550.107.02-1) breaks dependency 'nvidia-utils=550.90.07' required by linux69-nvidia
Done ...
It says “done” but the kernel does not get installed.
Using the command sudo mhwd-kernel -i linux66 asks me to do the full upgrade before:
$ sudo mhwd-kernel -i linux66 ✔
[sudo] password for USER:
:: Synchronizing package databases...
core is up to date
extra is up to date
multilib is up to date
The following packages are out of date, please update your system first: acpi acpid ...
What would be the best practice to not break my system?
- Update using pacman, install kernel with the command then reboot
- Update using pacman, reboot, then install kernel with the command
- Use the mhwd-kernel command to install the kernel and the rest of the update then reboot
I am currently on kernel 6.9.5-1-MANJARO (64-bit) (missed the last update).
Thanks for your help.
1 Like
If you are using linux69 there is no immediate concern as the kernel has not been removed yet.
So simply running - preferably in a TTY
sudo pacman -Syu
After that your nvidia should be in sync and you can move to the next kernel 6.6LTS or 6.10 what you prefer.
Thanks for the info, I got scared by the phrase If you use Linux 6.9 and Nvidia or inside a virtual machine, it is of great importance, that you install Linux 6.6 or Linux 6.10 to avoid driver problems. in the wiki post.
EDIT: I was able to update, reboot, install 6.10 and reboot. Everything is working without issue thanks.
I’m getting the same on my /dev/sda in Unstable.
Doesn’t seem to have an effect on the system so far…
Some sort of regression, perhaps
Edit: Seems that application have some catching up to do with a fix that was made in kernel
https://lore.kernel.org/all/ZrPw5m9LwMH5NQYy@x1-carbon.lan/
2 Likes
Things went well on my laptop, but my desktop update process had an issue at the mkinitcpio process…
(14/30) Restarting cronie for libc upgrade...
(15/30) Updating linux initcpios...
corrupted double-linked list
error: command terminated by signal 6: Aborted
(16/30) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
manually tried running mkinitcpio -P
sudo mkinitcpio -P
==> ERROR: No presets found in /etc/mkinitcpio.d
Yikes! Confirmed this was true
$ ls /etc/mkinitcpio.d
linux510.preset.pacsave linux515.preset.pacsave linux65.preset.pacsave
Learned online I needed to reinstall the kernels to put the preset files back in place.
sudo pacman -S linux66
warning: linux66-6.6.44-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) linux66-6.6.44-1
Total Installed Size: 134.76 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring [------------------------------------] 100%
(1/1) checking package integrity [------------------------------------] 100%
error: linux66: signature from "Manjaro Build Server <build@manjaro.org>" is invalid
:: File /var/cache/pacman/pkg/linux66-6.6.44-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n] y
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.
Yikes! corrupted package / invalid Signature? manually deleted the package files for the kernels I have installed to force the package re-download
sudo rm /var/cache/pacman/pkg/linux66-6.6.41*
sudo rm /var/cache/pacman/pkg/linux61-6.1.103*
sudo rm /var/cache/pacman/pkg/linux515-5.15.164*
sudo rm /var/cache/pacman/pkg/linux510-5.10.223*
Reinstalling the kernels succeeded, which also triggered the mkinitcpio -P and update-grub
sudo pacman -S linux66 linux61 linux515 linux510
warning: linux66-6.6.44-1 is up to date -- reinstalling
warning: linux61-6.1.103-1 is up to date -- reinstalling
warning: linux515-5.15.164-1 is up to date -- reinstalling
warning: linux510-5.10.223-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (4) linux510-5.10.223-1 linux515-5.15.164-1 linux61-6.1.103-1 linux66-6.6.44-1
Total Download Size: 442.88 MiB
Total Installed Size: 463.95 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] y
:: Retrieving packages...
linux61-6.1.103-1-x86_64 138.2 MiB 41.3 MiB/s 00:03 [------------------------------------] 100%
linux66-6.6.44-1-x86_64 129.1 MiB 31.3 MiB/s 00:04 [------------------------------------] 100%
linux515-5.15.164-1-x86_64 100.0 MiB 21.6 MiB/s 00:05 [------------------------------------] 100%
linux510-5.10.223-1-x86_64 75.6 MiB 16.2 MiB/s 00:05 [------------------------------------] 100%
Total (4/4) 442.9 MiB 94.1 MiB/s 00:05 [------------------------------------] 100%
(4/4) checking keys in keyring [------------------------------------] 100%
(4/4) checking package integrity [------------------------------------] 100%
(4/4) loading package files [------------------------------------] 100%
(4/4) checking for file conflicts [------------------------------------] 100%
(4/4) checking available disk space [------------------------------------] 100%
:: Processing package changes...
(1/4) reinstalling linux66 [------------------------------------] 100%
(2/4) reinstalling linux61 [------------------------------------] 100%
(3/4) reinstalling linux515 [------------------------------------] 100%
(4/4) reinstalling linux510 [------------------------------------] 100%
:: Running post-transaction hooks...
(1/4) Arming ConditionNeedsUpdate...
(2/4) Updating module dependencies...
(3/4) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64.img
==> Starting build: '5.10.223-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.10-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.10-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-x86_64-fallback.img -S autodetect
==> Starting build: '5.10.223-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.btrfs
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.xfs
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.10-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'default'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64.img
==> Starting build: '5.15.164-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux515.preset: 'fallback'
==> Using configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-5.15-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.15-x86_64-fallback.img -S autodetect
==> Starting build: '5.15.164-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.btrfs
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.xfs
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-5.15-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64.img
==> Starting build: '6.1.103-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux61.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.1-x86_64 -g /boot/initramfs-6.1-x86_64-fallback.img -S autodetect
==> Starting build: '6.1.103-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.btrfs
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.xfs
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.1-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64.img
==> Starting build: '6.6.44-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [autodetect]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux66.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
-> -k /boot/vmlinuz-6.6-x86_64 -g /boot/initramfs-6.6-x86_64-fallback.img -S autodetect
==> Starting build: '6.6.44-1-MANJARO'
-> Running build hook: [systemd]
-> Running build hook: [microcode]
-> Running build hook: [modconf]
-> Running build hook: [kms]
==> WARNING: Possibly missing firmware for module: 'ast'
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
-> Running build hook: [keyboard]
-> Running build hook: [sd-vconsole]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.btrfs
==> WARNING: Possibly missing '/bin/sh' for script: /usr/bin/fsck.xfs
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-6.6-x86_64-fallback.img'
-> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(4/4) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.6-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.6-x86_64.img
Found initrd fallback image: /boot/initramfs-6.6-x86_64-fallback.img
Found linux image: /boot/vmlinuz-6.1-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.1-x86_64.img
Found initrd fallback image: /boot/initramfs-6.1-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.15-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.15-x86_64.img
Found initrd fallback image: /boot/initramfs-5.15-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
/usr/bin/grub-probe: warning: unknown device type nvme2n1.
done
Rebooting now; hoping there are no more surprises.
UPDATE:
Rebooted successfully to desktop, no high priority items in the journal, so I feel my update recovery went well.
journalctl -p 3 -b 0
-- No entries --
Interesting find in journalctl --boot -1 --since "2024-08-09 09:10:00"
Aug 09 09:10:48 AM4-5600X-Linux systemd-coredump[653700]: Process 653699 (pacman) of user 0 terminated abnormally with signal 6/ABRT, processing...
Aug 09 09:10:48 AM4-5600X-Linux systemd[1]: Started Process Core Dump (PID 653700/UID 0).
Aug 09 09:10:48 AM4-5600X-Linux systemd-coredump[653701]: Resource limits disable core dumping for process 653699 (pacman).
Aug 09 09:10:48 AM4-5600X-Linux systemd-coredump[653701]: [🡕] Process 653699 (pacman) of user 0 terminated abnormally without generating a coredump.
Aug 09 09:10:49 AM4-5600X-Linux systemd[1]: systemd-coredump@13-653700-0.service: Deactivated successfully.
Which seems to match the original “signal 6” error I saw during update…
(15/30) Updating linux initcpios...
corrupted double-linked list
error: command terminated by signal 6: Aborted
Plasma wayland has almost invisible tiny icon in status and notification tray for HiDPI screen where as my another system with 1080p monitor setup is unaffected.
On my Minisforum UM690 - 6.11 RC1 – boots to Black screen with movable pointer. Works well on my Lenovo(AMD) & Dell(Intel) Tablets. All running KDE/Wayland
I ran into this as well - found a temp. fix on the Arch forums which stated to downgrade samba and smbclient to the previous versions as the newer releases have ABI compatibility problems.
Downgrading samba and smbclient to 4.20.2 fixed this for me.
1 Like
I installed the update on 8th and didn’t notice any issues at first. However today I discovered that all my libvirt VMs are experiencing weird network issues, like the connection is degraded or throttled.
For example: When I’m trying to upload a folder to the local NAS from guest Windows using SMB I’m getting unexpected error 0x8007003B.
I think I eliminated the possibility of this being issue with my NAS or router as the issue is persistent no matter if I use NAT or bridged connection.
Issue doesn’t occur If I boot Windows on bare metal or passthrough the Ethernet Controller as a device.
It’s a known problem with the current libvirt version, and has already amply been reported here. Please search the forum.
1 Like
No need to research too deep, it is right in the beginning of this topic.
2 Likes
With due respect. Change with “firewall_backend = “iptables”” didn’t work for me, was one of the first things I checked.
I did however found ONE topic which suggests to use “virtio-net” Host: Manjaro, Guest: Artix Linux, Issue: No virtio NAT connection on VM (KVM, qemu, libvirt, virt-manager, connman) - #8 by Teo which appears to be working for me. So I guess I had to dig slightly below the surface, as I don’t see it mentioned in this topic.
No need to be so dismissive just because I have like 4 posts on forums, I can read pinned threads 
(PS: There’s a slight difference between completely lacking the connection and having the connection degraded)
Noisetorch 0.12.2-4 has been released to all Manjaro branches to replace pulseaudio dependency with pulse-native-provider
Backup with kup has repeatedly errors.
in the log:
bup “-d” “/home/Grab_2_BIG/Backups/AutoSicherungenKDE” “fsck” “-g” “-j” “4”
Fehler: index-pack died of signal 11
Long time running without errors, No changes, disk space is not the problem
Edit 2
Deja Dup has one time error, one time working. No Idea
»/home/zero/.local/share/deja-dup/metadata« konnte nicht wiederhergestellt werden: Datei wurde in der Sicherung nicht gefunden