manjaro-settings-manager issueshttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues2023-05-28T14:24:00Zhttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/228Wrong kernel is installed2023-05-28T14:24:00Zroot@Optiplex-790Wrong kernel is installedWhenever i try to install linux-xanmod kernel, linux-xanmod-lts kernel is reinstalled for some reason, and whenever i try to remove the vanilla linux kernel, the linux-xanmod kernel is also removed
```
The following packages will be ins...Whenever i try to install linux-xanmod kernel, linux-xanmod-lts kernel is reinstalled for some reason, and whenever i try to remove the vanilla linux kernel, the linux-xanmod kernel is also removed
```
The following packages will be installed:
linux-xanmod
linux-xanmod-lts
linux-xanmod-headers
Starting
resolving dependencies...
warning: linux-xanmod-lts-6.1.30-1 is up to date -- reinstalling
looking for conflicting packages...
Package (3) Old Version New Version Net Change
chaotic-aur/linux-xanmod 6.3.4-1 373.90 MiB
chaotic-aur/linux-xanmod-headers 6.3.4-1 146.11 MiB
chaotic-aur/linux-xanmod-lts 6.1.30-1 6.1.30-1 0.00 MiB
Total Installed Size: 895.16 MiB
Net Upgrade Size: 520.01 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove --no-depmod nvidia/530.41.03 -k 6.1.30-x64v1-xanmod1-1-lts
==> dkms remove --no-depmod vboxhost/7.0.8_OSE -k 6.1.30-x64v1-xanmod1-1-lts
:: Processing package changes...
installing linux-xanmod...
Optional dependencies for linux-xanmod
crda: to set the correct wireless channels of your country [installed]
linux-firmware: firmware images needed for some devices [installed]
reinstalling linux-xanmod-lts...
installing linux-xanmod-headers...
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Updating module dependencies...
(3/6) Install DKMS modules
==> dkms install --no-depmod vboxhost/7.0.8_OSE -k 6.3.4-x64v1-xanmod1-1
Error! Bad return status for module build on kernel: 6.3.4-x64v1-xanmod1-1 (x86_64)
Consult /var/lib/dkms/vboxhost/7.0.8_OSE/build/make.log for more information.
==> WARNING: `dkms install --no-depmod vboxhost/7.0.8_OSE -k 6.3.4-x64v1-xanmod1-1' exited 10
==> dkms install --no-depmod vboxhost/7.0.8_OSE -k 6.1.30-x64v1-xanmod1-1-lts
Error! Bad return status for module build on kernel: 6.1.30-x64v1-xanmod1-1-lts (x86_64)
Consult /var/lib/dkms/vboxhost/7.0.8_OSE/build/make.log for more information.
==> WARNING: `dkms install --no-depmod vboxhost/7.0.8_OSE -k 6.1.30-x64v1-xanmod1-1-lts' exited 10
==> dkms install --no-depmod nvidia/530.41.03 -k 6.3.4-x64v1-xanmod1-1
Error! Bad return status for module build on kernel: 6.3.4-x64v1-xanmod1-1 (x86_64)
Consult /var/lib/dkms/nvidia/530.41.03/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/530.41.03 -k 6.3.4-x64v1-xanmod1-1' exited 10
==> dkms install --no-depmod nvidia/530.41.03 -k 6.1.30-x64v1-xanmod1-1-lts
Error! Bad return status for module build on kernel: 6.1.30-x64v1-xanmod1-1-lts (x86_64)
Consult /var/lib/dkms/nvidia/530.41.03/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/530.41.03 -k 6.1.30-x64v1-xanmod1-1-lts' exited 10
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-lts.preset: 'default'
-> -k /boot/vmlinuz-linux-xanmod-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-lts.img --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.30-x64v1-xanmod1-1-lts'
-> Running build hook: [base]
-> Running build hook: [plymouth]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: '/boot/initramfs-linux-xanmod-lts.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod-lts.preset: 'fallback'
-> -k /boot/vmlinuz-linux-xanmod-lts -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-lts-fallback.img -S autodetect --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.1.30-x64v1-xanmod1-1-lts'
-> Running build hook: [base]
-> Running build hook: [plymouth]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: '/boot/initramfs-linux-xanmod-lts-fallback.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod.preset: 'default'
-> -k /boot/vmlinuz-linux-xanmod -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod.img --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.3.4-x64v1-xanmod1-1'
-> Running build hook: [base]
-> Running build hook: [plymouth]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: '/boot/initramfs-linux-xanmod.img'
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod.preset: 'fallback'
-> -k /boot/vmlinuz-linux-xanmod -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod-fallback.img -S autodetect --microcode /boot/amd-ucode.img --microcode /boot/intel-ucode.img
==> Starting build: '6.3.4-x64v1-xanmod1-1'
-> Running build hook: [base]
-> Running build hook: [plymouth]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [consolefont]
==> WARNING: consolefont: no font found in configuration
-> Running build hook: [plymouth]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating lz4-compressed initcpio image: '/boot/initramfs-linux-xanmod-fallback.img'
==> Image generation successful
(5/6) Refreshing PackageKit...
(6/6) Update grub after installing or removing a kernel or ucode.
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/pentract/theme.txt
Found linux image: /boot/vmlinuz-linux-xanmod-lts
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-xanmod-lts.img
Found fallback initrd image(s) in /boot: intel-ucode.img amd-ucode.img initramfs-linux-xanmod-lts-fallback.img
Found linux image: /boot/vmlinuz-linux-xanmod
Found initrd image: /boot/intel-ucode.img /boot/amd-ucode.img /boot/initramfs-linux-xanmod.img
Found fallback initrd image(s) in /boot: intel-ucode.img amd-ucode.img initramfs-linux-xanmod-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.
which: no umount in ((null))
Adding boot menu entry for UEFI Firmware Settings ...
Detecting snapshots ...
Found snapshot: 2023-05-20 13:34:51 | timeshift-btrfs/snapshots/2023-05-20_13-34-51/@ | ondemand | Saturday May 20 2023. |
Found 1 snapshot(s)
Unmount /tmp/grub-btrfs.DWHDjTQHbv .. Success
Found memtest86+ image: /boot/memtest86+/memtest.bin
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
done
Done ...
```https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/222Failure of ceph-lib and python 22022-11-24T15:36:07ZAnthony BrunoriFailure of ceph-lib and python 2updates for ceph-libs and python 2 continue to fail to update and build and I currently have the recommended kernel.updates for ceph-libs and python 2 continue to fail to update and build and I currently have the recommended kernel.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/221Can't go back to previous already-installed kernel2022-11-12T14:34:11ZJosh McCulloughCan't go back to previous already-installed kernel![image](/uploads/6d81fa9444e8af690907f4c9ee32999b/image.png)
There is no option to go back to e.g. `5.15.76-1` from `5.16.20-2`.![image](/uploads/6d81fa9444e8af690907f4c9ee32999b/image.png)
There is no option to go back to e.g. `5.15.76-1` from `5.16.20-2`.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/219Second monitor - Intel onboard - dont works2022-10-16T13:59:10ZcetbSecond monitor - Intel onboard - dont worksHi ! Need help.
Very loved Manjaro, but unable to connect second monitor, which connected to onboard VGA (Intel)
( Intel Corporation Xeon E3-1200 )
Tried many ways to detect second monitor, but nothing works.
Thanks,Hi ! Need help.
Very loved Manjaro, but unable to connect second monitor, which connected to onboard VGA (Intel)
( Intel Corporation Xeon E3-1200 )
Tried many ways to detect second monitor, but nothing works.
Thanks,https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/218Add ability to open application directly from system tray with right-clicking2022-10-09T20:14:40ZAhmetAdd ability to open application directly from system tray with right-clickingAs per title. Left-click shows some options but do not have ability to open the application's main page.As per title. Left-click shows some options but do not have ability to open the application's main page.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/216Text cut in Kernel - System Settings2022-10-09T20:15:59ZsuperbonaciText cut in Kernel - System SettingsAbout system:
````
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.19.1-3-MANJARO (64-bit)
Graphics Platform: X11
Graphics Processor: SVGA3D; build: RELEASE; ...About system:
````
Operating System: Manjaro Linux
KDE Plasma Version: 5.24.6
KDE Frameworks Version: 5.96.0
Qt Version: 5.15.5
Kernel Version: 5.19.1-3-MANJARO (64-bit)
Graphics Platform: X11
Graphics Processor: SVGA3D; build: RELEASE; LLVM;
````
Screenshot (notice that when there are 3 item `Unsupported` gets cut at the bottom. Probably the UI does not take into account that 3 item can be stacked on top of each other:
![](https://i.imgur.com/Q2aZMfy.png)
this issue is related to https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/188https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/215Asus ROG Zephyrus GX701L sound problem2022-08-21T20:37:25ZIwancheAsus ROG Zephyrus GX701L sound problemHello,
First of all, let me mention that I tried everything I could find on the forums, and I did not succeed in getting the sound from the speakers.
So, the headphones and microphone work without problems, only the speakers do not pro...Hello,
First of all, let me mention that I tried everything I could find on the forums, and I did not succeed in getting the sound from the speakers.
So, the headphones and microphone work without problems, only the speakers do not produce sound.
Please, can someone add a fix in the kernel for ROG Zephyrus S17 GX701LWS_GX701LWS, Subsystem Id: 0x10431f01.
```
[codec]
0x10ec0294 0x10431f01 0
[pincfg]
0x19 0x03A11050
0x1a 0x03A11C30
```
This is what a quirk should look like for my notebook:
+SND_PCI_QUIRK(0x1043, 0x1f01, “ASUS GX701L”, ALC294_FIXUP_ASUS_SPK)
If you need any more data, just say so.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/212Incorrect Chinese translation for the word "Install packages" in language set...2022-08-21T19:17:04Z星外之神Incorrect Chinese translation for the word "Install packages" in language settingsThe translation now ("已安装的软件包") means "Installed packages", and the translation there should be "安装软件包".
The incorrect translation is [***here***](https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/blob/master/src/libmsm...The translation now ("已安装的软件包") means "Installed packages", and the translation there should be "安装软件包".
The incorrect translation is [***here***](https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/blob/master/src/libmsm/translations/msm_zh_CN.ts#L871)
![image](/uploads/21fc97a7b3b93ec81041b53f0e200e76/image.png)https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/211Latest QT5 update breaks dependency; can't reinstall MSM2022-06-19T17:32:47ZjeoisLatest QT5 update breaks dependency; can't reinstall MSMThe newest qt5 update from Manjaro-unstable (Arch) breaks the "qt5-base < 5.15.5" dependency.
I had to manually uninstall `manjaro-settings-manager-knotifier` and `manjaro-settings-manager-kcm` in order to update QT. Now, I can't rein...The newest qt5 update from Manjaro-unstable (Arch) breaks the "qt5-base < 5.15.5" dependency.
I had to manually uninstall `manjaro-settings-manager-knotifier` and `manjaro-settings-manager-kcm` in order to update QT. Now, I can't reinstall `manjaro-settings-manager` because of that same dependency requirement since pamac automatically uninstalled MSM during the update.
Sorry if I should have posted this in the forums, but I wasn't sure of the category and thought it was relevant here.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/210bluetooth mouse not recognized correctly2022-06-16T23:33:55Zbeams3sgebluetooth mouse not recognized correctlyhello i have a XIAOMI MI DUAL MODE mouse (two types of connection Bluetooth and 2.4Ghz adapter).
On kernel 4.14.280-1 it works out of the box all buttons works correct.
but when i switch to another kernel example 4.19 or 5.10 or the lat...hello i have a XIAOMI MI DUAL MODE mouse (two types of connection Bluetooth and 2.4Ghz adapter).
On kernel 4.14.280-1 it works out of the box all buttons works correct.
but when i switch to another kernel example 4.19 or 5.10 or the latest kernel the forward-backward buttons doesn't work on bluetooth mode but on 2.4Ghz mode works normally.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/209Modules broken with Manjaro 5.17.9-1 kernel version2022-05-24T07:05:44ZTechManWalkerModules broken with Manjaro 5.17.9-1 kernel versionFew hours ago I updated with "sudo pacman -Syu" from the 5.17.1 to the 5.17.9. The update was successful, or that's what I believed. Then I reboot and now I can't boot my computer because all filesystems stopped being recognized, includi...Few hours ago I updated with "sudo pacman -Syu" from the 5.17.1 to the 5.17.9. The update was successful, or that's what I believed. Then I reboot and now I can't boot my computer because all filesystems stopped being recognized, including FAT32 and EXT4! Total, I was sent to GRUB Rescue command line and no filesystem is recognized now, NOT EVEN ONE. I don't know how GRUB Rescue could be boot. That was caused due to broken kernel modules.
I had to downgrade to version 5.15.41 with help of my USB installation medium. I had to manually delete the just-updated kernel and run "sudo pacman -Sy linux515 linux-firmware" and reinstall GRUB. Only then I can boot my computer again.
At this moment I'm using the version 5.15.41, the same one that came on my installation media. I chose that one because I knew that version would work well as it was working in my Live USB.
I highly recommend not to update to the version 5.17.9 because you can face the same problem that me.
Thanks.
![283872896_977490926297016_4456118068605384217_n](/uploads/2e8e3c1ce0b821ec495d35282596c937/283872896_977490926297016_4456118068605384217_n.jpg)https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/208Text not visible in a dark theme2022-05-14T22:15:13ZPeter MajchrákText not visible in a dark themeTitle of the settings section and some text in dialogs is almost invisible when using a dark theme.
Note the text "Kernel", to the right of the penguin:
![Screenshot_from_2022-05-14_21-14-43](/uploads/697810090c97cbc1b764b1608b0ec273/Sc...Title of the settings section and some text in dialogs is almost invisible when using a dark theme.
Note the text "Kernel", to the right of the penguin:
![Screenshot_from_2022-05-14_21-14-43](/uploads/697810090c97cbc1b764b1608b0ec273/Screenshot_from_2022-05-14_21-14-43.png)
Note the dialog text:
![Screenshot_from_2022-05-14_21-32-22](/uploads/2dc8b9d0737c54a02aa11b0f0ef3cde8/Screenshot_from_2022-05-14_21-32-22.png)https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/207Compositor Rendering Backend option missing2022-03-30T15:30:40ZAzis RamadhanCompositor Rendering Backend option missing![Screenshot_20220309_131838](/uploads/ebe6c0d46fe67485fa81a6c12257602b/Screenshot_20220309_131838.png)
After updating from 21.2.2 to 21.2.4 the OpenGL 2.0 and OpenGL 3.1 Rendering Backend option is missing.![Screenshot_20220309_131838](/uploads/ebe6c0d46fe67485fa81a6c12257602b/Screenshot_20220309_131838.png)
After updating from 21.2.2 to 21.2.4 the OpenGL 2.0 and OpenGL 3.1 Rendering Backend option is missing.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/206Bluetooth device not recognised2022-06-16T23:36:17ZS KBluetooth device not recognisedLinux kernel 5.16.5-1 installed. Motherboard bluetooth device now not recognised. Motherboard: MSI MAG B460M MORTAR WIFI, Intel B460, S 1200, DDR4, SATA3, Dual M.2, CrossFire, 2.5GbE/ax WiFi, USB 3.2 Gen1, MicroATX $6UDWM. Please fix.Linux kernel 5.16.5-1 installed. Motherboard bluetooth device now not recognised. Motherboard: MSI MAG B460M MORTAR WIFI, Intel B460, S 1200, DDR4, SATA3, Dual M.2, CrossFire, 2.5GbE/ax WiFi, USB 3.2 Gen1, MicroATX $6UDWM. Please fix.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/205Kernel installation reported successfully installed when installation failed ...2022-06-16T23:36:55ZPavel SkipenesKernel installation reported successfully installed when installation failed because of missing disk spaceI just ran out of space on /boot when installing a new kernel however manjaro setting manager reported installation as successful. ![image](/uploads/98017a24f726cf46b25fea605e52223b/image.png)![image](/uploads/280a37860ae42d7054ff010d904...I just ran out of space on /boot when installing a new kernel however manjaro setting manager reported installation as successful. ![image](/uploads/98017a24f726cf46b25fea605e52223b/image.png)![image](/uploads/280a37860ae42d7054ff010d90405676/image.png)
<details><summary>pacman -Q | grep manjaro</summary>
```
arc-dark-lxqt-manjaro 1-6
bashrc-manjaro 5.1.016-2
grub-theme-manjaro 20.2-12
manjaro-alsa 20210928-1
manjaro-application-utility 1.3.3-6
manjaro-artwork 1.0.8-4
manjaro-base-skel 20171029-3
manjaro-browser-settings 20201114-1
manjaro-dynamic-wallpaper 1.3-1
manjaro-firmware 20160419-1
manjaro-gdm-branding 20210529-2
manjaro-gdm-theme 20210528-1
manjaro-gnome-extension-settings 20211226-2
manjaro-gnome-postinstall 0.1.1-3
manjaro-gnome-settings 20211221-1
manjaro-gnome-tour 3.38.0+31+gdf1ba86-1
manjaro-hello 0.6.6-11
manjaro-hotfixes 2018.08-6
manjaro-icons 20191015-1
manjaro-keyring 20210910-2
manjaro-pipewire 20220123-1
manjaro-release 21.2.3-1
manjaro-settings-manager 0.5.7-1
manjaro-settings-manager-notifier 0.5.7-1
manjaro-system 20220202-2
manjaro-wallpapers-18.0 1.4-3
manjaro-zsh-config 0.22-2
plymouth-theme-manjaro 2.1-2
python-manjaro-sdk 0.5-1
steam-manjaro 1.0.0.74-1
```
</details>
<details><summary>full log</summary>
```
The following packages will be installed:
linux516
linux516-nvidia
linux516-virtualbox-host-modules
linux516-headers
Starting
resolving dependencies...
looking for conflicting packages...
Packages (4) linux516-5.16.5-1 linux516-headers-5.16.5-1 linux516-nvidia-510.47.03-1 linux516-virtualbox-host-modules-6.1.32-5
Total Download Size: 194.52 MiB
Total Installed Size: 303.97 MiB
:: Proceed with installation? [Y/n]
:: Retrieving packages...
linux516-5.16.5-1-x86_64 downloading...
linux516-nvidia-510.47.03-1-x86_64 downloading...
linux516-headers-5.16.5-1-x86_64 downloading...
linux516-virtualbox-host-modules-6.1.32-5-x86_64 downloading...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing linux516...
Optional dependencies for linux516
crda: to set the correct wireless channels of your country [installed]
installing linux516-nvidia...
In order to use nvidia module, reboot the system.
installing linux516-virtualbox-host-modules...
===> You must load vboxdrv module before starting VirtualBox:
===> # modprobe vboxdrv
installing linux516-headers...
:: Running post-transaction hooks...
(1/6) Arming ConditionNeedsUpdate...
(2/6) Updating module dependencies...
(3/6) Install DKMS modules
==> dkms install --no-depmod nvidia/510.47.03 -k 5.16.5-1-MANJARO
Error! Bad return status for module build on kernel: 5.16.5-1-MANJARO (x86_64)
Consult /var/lib/dkms/nvidia/510.47.03/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/510.47.03 -k 5.16.5-1-MANJARO' exited 10
==> dkms install --no-depmod v4l2loopback-dc/1.8.1 -k 5.16.5-1-MANJARO
Error! Bad return status for module build on kernel: 5.16.5-1-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback-dc/1.8.1/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback-dc/1.8.1 -k 5.16.5-1-MANJARO' exited 10
==> dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.5-1-MANJARO
Deprecated feature: REMAKE_INITRD
Error! Bad return status for module build on kernel: 5.16.5-1-MANJARO (x86_64)
Consult /var/lib/dkms/v4l2loopback/0.12.5/build/make.log for more information.
==> WARNING: `dkms install --no-depmod v4l2loopback/0.12.5 -k 5.16.5-1-MANJARO' exited 10
(4/6) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'default'
-> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64.img
==> Starting build: 5.16.5-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.16-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux516.preset: 'fallback'
-> -k /boot/vmlinuz-5.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.16-x86_64-fallback.img -S autodetect
==> Starting build: 5.16.5-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
==> WARNING: Possibly missing firmware for module: xhci_pci
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.16-x86_64-fallback.img
gzip: stdout: No space left on device
bsdtar: Write error
==> ERROR: Image generation FAILED: bsdtar (step 1) reported an error
(5/6) Updating Kernel initcpios for Nvidia-DRM...
(6/6) Updating Grub-Bootmenu
Generating grub configuration file ...
cat: write error: No space left on device
Done ...
```
</details>https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/204Pull request: Prevent users from deleting kernel while it is actually being used2022-08-21T20:07:08ZelliotwutingfengPull request: Prevent users from deleting kernel while it is actually being usedAccording to the Manjaro wiki, it is a bad idea to [delete a kernel while it is actually being used](https://wiki.manjaro.org/index.php/Manjaro_Kernels#Removing_Kernels). However, the Manjaro Settings Manager GUI still allows for this.
!...According to the Manjaro wiki, it is a bad idea to [delete a kernel while it is actually being used](https://wiki.manjaro.org/index.php/Manjaro_Kernels#Removing_Kernels). However, the Manjaro Settings Manager GUI still allows for this.
![Screenshot_from_2022-01-31_23-33-41](/uploads/e542bf82d87cd9b31048be970a44a853/Screenshot_from_2022-01-31_23-33-41.png)
Greying out the 'Remove' button on the kernel version that is currently running can help prevent users from borking their setup via the GUI.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/203Frequently parking of hard disk heads and hdd turns off2022-06-16T23:39:35ZDmitryFrequently parking of hard disk heads and hdd turns offAfter the update on 5.10 LTS kernel, there was a problem on asus n750jk notebook (i7-4710hq modification) with system ssd (sata) + hdd configuration. After accessing the hard drive (for example, opening an picture) and the last 2-5 secon...After the update on 5.10 LTS kernel, there was a problem on asus n750jk notebook (i7-4710hq modification) with system ssd (sata) + hdd configuration. After accessing the hard drive (for example, opening an picture) and the last 2-5 seconds, hdd power supplying turns off. If I want to, for example, open another picture, my hard drive will start spinning again, which will cause the file manager to hang while waiting for the hard drive to turn on again
This problem is not present in kernel 4.19 and earlier versions.
Playing with Hdparm utility, does not give any results. The kernel 5.10 seems to ignore the utility values.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/202Kernel System Settings Module - Displays changes were made successfully when ...2022-06-16T23:40:18ZfoxrumorKernel System Settings Module - Displays changes were made successfully when failing.There is a user interface oversight in the kernel system settings module which displays a "Changes were made successfully" prompt despite a kernel upgrade having dependency errors and failing. This can be very confusing to an inexperienc...There is a user interface oversight in the kernel system settings module which displays a "Changes were made successfully" prompt despite a kernel upgrade having dependency errors and failing. This can be very confusing to an inexperienced user that does not know to click the "Show details" option.
If left unchanged, this could lead to confused users unaware of why their kernel has not fully upgraded despite no error message being displayed.
![image](/uploads/17e845cb227208bc705513a1a1493c5c/image.png)
![image](/uploads/2b807dfbd70589fc2f6d93a9799e4da4/image.png)https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/201msm_kernel.so - LTS flags2022-06-16T23:40:49Zquietpinguinmsm_kernel.so - LTS flagsKernel version 15.x.x is not listed as a Longterm release kernel (LTS) although this has been officially publicised on
https://www.kernel.org/category/releases.htmlKernel version 15.x.x is not listed as a Longterm release kernel (LTS) although this has been officially publicised on
https://www.kernel.org/category/releases.htmlhttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/200Problem on booting2022-06-16T23:41:04ZRealdo BejaProblem on bootingI have a problem. When booting the system and meanwhile laptop connected to a monitor via hdmi cable, after i type the password it boots with a black img on wallpaper and i can't press right click or anything on the screen(the panel work...I have a problem. When booting the system and meanwhile laptop connected to a monitor via hdmi cable, after i type the password it boots with a black img on wallpaper and i can't press right click or anything on the screen(the panel works fine), kernel 5.15.7-1