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/227Installed kernels are not detected during the first access2023-08-28T10:33:21ZMedinInstalled kernels are not detected during the first access```
Operating System: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.25-1-MANJARO (64-bit)
Graphics Platform: X11
```
I have 3 kernels installed
![Screenshot_20230502_14...```
Operating System: Manjaro Linux
KDE Plasma Version: 5.27.4
KDE Frameworks Version: 5.104.0
Qt Version: 5.15.8
Kernel Version: 6.1.25-1-MANJARO (64-bit)
Graphics Platform: X11
```
I have 3 kernels installed
![Screenshot_20230502_142620-1](/uploads/400a23809bb85672c0d668b0c1936212/Screenshot_20230502_142620-1.png)
When I access Manjaro "Kernel" page in "Plasma Settings" app for the first time, it reports that only the currently running kernel is installed
![Screenshot_20230502_131155](/uploads/8367d6cc21600428b8b8b88785199399/Screenshot_20230502_131155.png)
Inspecting the log shows the following error:
![Screenshot_20230504_110356](/uploads/e2bb15c5d401027f613c4d6f098986b6/Screenshot_20230504_110356.png)
If I access the same Kernel page for a second time, it shows all installed kernels with correct "Install/Remove" buttons.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/226Kernel show wrong version is running2023-04-27T14:39:14ZRoi EfratiKernel show wrong version is runningSystem Settings > Kernel: show as i am running version "Linux 6.3.0rc5-1" (Experimental).
While I'm actually running 6.3.0 final release (built myself with LLVM).
`
cat /proc/version
Linux version 6.3.0-MANJARO (roie@roi-80q7) (clang v...System Settings > Kernel: show as i am running version "Linux 6.3.0rc5-1" (Experimental).
While I'm actually running 6.3.0 final release (built myself with LLVM).
`
cat /proc/version
Linux version 6.3.0-MANJARO (roie@roi-80q7) (clang version 15.0.7, LLD 15.0.7) #1 SMP PREEMPT_DYNAMIC Mon Apr 24 10:59:13 IDT 2023
`https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/225Application language2023-03-22T16:29:30ZmnorkApplication languageI live in the Czech Republic so have a czech IP and have British/American English, Czech and Hungarian languages installed but my system should be primarily British English. I have had problems with a few applications opening in Czech. ...I live in the Czech Republic so have a czech IP and have British/American English, Czech and Hungarian languages installed but my system should be primarily British English. I have had problems with a few applications opening in Czech. I first noticed in terminator - I run a command and the CLI replies in Czech. This stopped recently, I did add EXPORT LANG=C to .bashrc while troubleshooting. I have checked my locales and it looks all en_gb, I can't figure out why some things are in Czech.
VLC is one, I installed through pacman and it launches in Czech, I recently tried launching it from terminator and it opened in english but if I launch from the application menu or by double clicking a video in Dolphin, it opens in Czech.
I tried another media player later and that runs in czech too.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/224MSM Notifier only allows opening "Kernels" and/or "Language packs" menu items...2023-01-21T09:54:23ZLars Juel NielsenMSM Notifier only allows opening "Kernels" and/or "Language packs" menu items once per system boot and the "Options" menu item also stops opening after either of the first have been opened on a bootIt's been like this for months by the way, but I'm not sure when it started happening.
It happens even if you don't use anything in the windows opened from the menu, just opening the window triggers it.
I'm running Manjaro XFCE on two...It's been like this for months by the way, but I'm not sure when it started happening.
It happens even if you don't use anything in the windows opened from the menu, just opening the window triggers it.
I'm running Manjaro XFCE on two systems which both have the issue.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/223Translation not on pair with transifex2023-01-08T12:19:15ZLamdarerTranslation not on pair with transifexIt seems that the german translation is not on pair with transifex.
E.g. from the Kernel section:
The string "New Kernel package(s) is/are ready to install.
Would you like to continue?" already has the translation "Neue(s) Kernel-Paket(...It seems that the german translation is not on pair with transifex.
E.g. from the Kernel section:
The string "New Kernel package(s) is/are ready to install.
Would you like to continue?" already has the translation "Neue(s) Kernel-Paket(e) ist/sind bereit zum Installieren.
Möchten Sie fortfahren?"
As well as "Show Details" and "The following packages will be installed:⏎" etc
But this was translated over 6years ago so I am not certain why it isn't there.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/220A prior version of the GPU driver is offered to be installed, instead of the ...2022-11-16T15:14:19ZNZampA prior version of the GPU driver is offered to be installed, instead of the current oneOn a nvidia-optimus laptop the driver manager (mhwd) detects a previous version of the GPU driver (nvidia-390xx) instead of the newest one (430.40 according to nvidia's website). I have not observed the same issue on other distros.
Hard...On a nvidia-optimus laptop the driver manager (mhwd) detects a previous version of the GPU driver (nvidia-390xx) instead of the newest one (430.40 according to nvidia's website). I have not observed the same issue on other distros.
Hardware configuration (GPUs): Intel Haswell iGPU + Nvidia GeForce 920Mhttps://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/217Kernels are reported as successfully removed when they're not.2022-09-18T17:28:33Zfeature-engineerKernels are reported as successfully removed when they're not.Steps to reproduce:
1. Have linux-latest package installed alongside linux510 and linux515.
2. Try to remove linux 5.10 from the manjaro settings manager
What happens:
1. Manjaro settings manager reports successful removal.
2. Manjaro...Steps to reproduce:
1. Have linux-latest package installed alongside linux510 and linux515.
2. Try to remove linux 5.10 from the manjaro settings manager
What happens:
1. Manjaro settings manager reports successful removal.
2. Manjaro settings manager still shows 5.10 as installed (correctly)
What is expected to happen:
Listing alternatives at descending orders of preference:
1. Realize that linux-latest is a deprecated meta-package which can be safely removed, and automatically remove it and the kernel.
2. Report failure to remove kernel, citing linux-latest as the source of the error (preferably also saying it is deprecated and instructing to remove it)
The issue was first discussed in the [Manjaro forums](https://forum.manjaro.org/t/unable-to-uninstall-5-10-kernel-required-by-linux-latest-even-though-5-15-is-installed/121786)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/214manjaro-settings-manager-kcm: returns success on failure on kernel install2022-08-12T08:42:02Zbkeppnermanjaro-settings-manager-kcm: returns success on failure on kernel installThis belongs to manjaro-settings-manager-kcm, but i couldnt find it.
When pacman is busy installing something, and i try to install a kernel simultaneously, it immediately returns: "Changes were made successfully.", but it obviously did...This belongs to manjaro-settings-manager-kcm, but i couldnt find it.
When pacman is busy installing something, and i try to install a kernel simultaneously, it immediately returns: "Changes were made successfully.", but it obviously did not install any kernel packages...
This of course is just a little thing, but i thought it might be worth mentioninghttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/213Conflicting files2022-08-04T13:49:39ZFusuMusuConflicting filesmhwd leaves behind these files when removing or reinstalling thus a file conflict happens when installing
<details><summary>Click to expand</summary>
```
Starting
> Removing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64....mhwd leaves behind these files when removing or reinstalling thus a file conflict happens when installing
<details><summary>Click to expand</summary>
```
Starting
> Removing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/local/pci/video-hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
checking dependencies...
:: ffmpeg optionally requires nvidia-utils: Nvidia NVDEC/NVENC support
:: ffmpeg4.4 optionally requires nvidia-utils: Nvidia NVDEC/NVENC support
:: lib32-vulkan-icd-loader optionally requires lib32-vulkan-driver: packaged vulkan driver
:: vulkan-icd-loader optionally requires vulkan-driver: packaged vulkan driver
Packages (5) lib32-nvidia-utils-515.57-1 libxnvctrl-515.57-1 linux515-nvidia-515.57-9 nvidia-prime-1.0-4 nvidia-utils-515.57-1
Total Removed Size: 606.37 MiB
:: Do you want to remove these packages? [Y/n]
:: Processing package changes...
removing linux515-nvidia...
removing lib32-nvidia-utils...
xorg configuration symlink valid...
removing nvidia-prime...
removing nvidia-utils...
xorg configuration symlink valid...
removing libxnvctrl...
:: Running post-transaction hooks...
(1/6) Reloading system manager configuration...
(2/6) Reloading device manager configuration...
(3/6) Arming ConditionNeedsUpdate...
(4/6) Updating module dependencies...
(5/6) Refreshing PackageKit...
(6/6) Updating the desktop file MIME type cache...
'/etc/X11/xorg.conf.d/90-mhwd.conf' symlink is invalid! Removing it...
> Successfully removed video-hybrid-intel-nvidia-prime
> Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
multilib downloading...
resolving dependencies...
looking for conflicting packages...
Packages (5) lib32-nvidia-utils-515.57-1 libxnvctrl-515.57-1 linux515-nvidia-515.57-9 nvidia-prime-1.0-4 nvidia-utils-515.57-1
Total Installed Size: 606.37 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
error: failed to commit transaction (conflicting files)
libxnvctrl: /usr/lib/libXNVCtrl.so.0 exists in filesystem
nvidia-utils: /usr/lib/libEGL_nvidia.so.0 exists in filesystem
nvidia-utils: /usr/lib/libGLESv1_CM_nvidia.so.1 exists in filesystem
nvidia-utils: /usr/lib/libGLESv2_nvidia.so.2 exists in filesystem
nvidia-utils: /usr/lib/libGLX_nvidia.so.0 exists in filesystem
nvidia-utils: /usr/lib/libcuda.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvcuvid.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-allocator.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-cfg.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-egl-gbm.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-encode.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-fbc.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ml.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ngx.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-opticalflow.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ptxjitcompiler.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvoptix.so.1 exists in filesystem
Errors occurred, no packages were upgraded.
Error: pacman failed!
Error: script failed!
Done ...
```
</details>
happened more than once with different files:
<details><summary>Click to expand</summary>
```
Starting
> Using config 'video-hybrid-intel-nvidia-prime' for device: 0000:00:02.0 (0300:8086:591b) Display controller Intel Corporation HD Graphics 630
> Dependencies to install: video-modesetting
> Installing dependency video-modesetting...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/video-modesetting/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
:: Synchronizing package databases...
core downloading...
extra downloading...
community downloading...
multilib downloading...
> Successfully installed dependency video-modesetting
> Installing video-hybrid-intel-nvidia-prime...
Sourcing /etc/mhwd-x86_64.conf
Has lib32 support: true
Sourcing /var/lib/mhwd/db/pci/graphic_drivers/hybrid-intel-nvidia-prime/MHWDCONFIG
Processing classid: 0300
Sourcing /var/lib/mhwd/scripts/include/0300
resolving dependencies...
looking for conflicting packages...
Packages (5) lib32-nvidia-utils-515.57-1 libxnvctrl-515.57-1 linux515-nvidia-515.57-9 nvidia-prime-1.0-4 nvidia-utils-515.57-1
Total Installed Size: 606.37 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
error: failed to commit transaction (conflicting files)
libxnvctrl: /usr/lib/libXNVCtrl.so.0 exists in filesystem
nvidia-utils: /usr/lib/libEGL_nvidia.so.0 exists in filesystem
nvidia-utils: /usr/lib/libGLESv1_CM_nvidia.so.1 exists in filesystem
nvidia-utils: /usr/lib/libGLESv2_nvidia.so.2 exists in filesystem
nvidia-utils: /usr/lib/libGLX_nvidia.so.0 exists in filesystem
nvidia-utils: /usr/lib/libcuda.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvcuvid.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-allocator.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-cfg.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-egl-gbm.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-eglcore.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-encode.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-fbc.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-glcore.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-glsi.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-glvkspirv.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-gtk3.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ml.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ngx.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-opticalflow.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-ptxjitcompiler.so.1 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-rtcore.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvidia-tls.so.515.57 exists in filesystem
nvidia-utils: /usr/lib/libnvoptix.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libEGL_nvidia.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libEGL_nvidia.so.0 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libEGL_nvidia.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv1_CM_nvidia.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv1_CM_nvidia.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv1_CM_nvidia.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv2_nvidia.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv2_nvidia.so.2 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLESv2_nvidia.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLX_nvidia.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLX_nvidia.so.0 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libGLX_nvidia.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libcuda.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libcuda.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libcuda.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvcuvid.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvcuvid.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvcuvid.so.515.57
exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-allocator.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-allocator.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-allocator.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-eglcore.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-eglcore.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-encode.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-encode.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-encode.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-fbc.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-fbc.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-fbc.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glcore.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glcore.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glsi.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glsi.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glvkspirv.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-glvkspirv.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ml.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ml.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ml.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-opticalflow.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-opticalflow.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-opticalflow.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ptxjitcompiler.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ptxjitcompiler.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-ptxjitcompiler.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-tls.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/libnvidia-tls.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/lib32/vdpau/libvdpau_nvidia.so exists in filesystem
lib32-nvidia-utils: /usr/lib32/vdpau/libvdpau_nvidia.so.1 exists in filesystem
lib32-nvidia-utils: /usr/lib32/vdpau/libvdpau_nvidia.so.515.57 exists in filesystem
lib32-nvidia-utils: /usr/share/licenses/lib32-nvidia-utils exists in filesystem
linux515-nvidia: /usr/share/licenses/linux515-nvidia/LICENSE exists in filesystem
Errors occurred, no packages were upgraded.
Error: pacman failed!
Error: script failed!
Done ...
```
</details>
list of files for better visibility:
<details><summary>Click to expand</summary>
```
/usr/lib/libXNVCtrl.so.0
/usr/lib/libEGL_nvidia.so.0
/usr/lib/libGLESv1_CM_nvidia.so.1
/usr/lib/libGLESv2_nvidia.so.2
/usr/lib/libGLX_nvidia.so.0
/usr/lib/libcuda.so.1
/usr/lib/libnvcuvid.so.1
/usr/lib/libnvidia-allocator.so.1
/usr/lib/libnvidia-cfg.so.1
/usr/lib/libnvidia-egl-gbm.so.1
/usr/lib/libnvidia-eglcore.so.515.57
/usr/lib/libnvidia-encode.so.1
/usr/lib/libnvidia-fbc.so.1
/usr/lib/libnvidia-glcore.so.515.57
/usr/lib/libnvidia-glsi.so.515.57
/usr/lib/libnvidia-glvkspirv.so.515.57
/usr/lib/libnvidia-gtk3.so.515.57
/usr/lib/libnvidia-ml.so.1
/usr/lib/libnvidia-ngx.so.1
/usr/lib/libnvidia-opticalflow.so.1
/usr/lib/libnvidia-ptxjitcompiler.so.1
/usr/lib/libnvidia-rtcore.so.515.57
/usr/lib/libnvidia-tls.so.515.57
/usr/lib/libnvoptix.so.1
/usr/lib32/libEGL_nvidia.so
/usr/lib32/libEGL_nvidia.so.0
/usr/lib32/libEGL_nvidia.so.515.57
/usr/lib32/libGLESv1_CM_nvidia.so
/usr/lib32/libGLESv1_CM_nvidia.so.1
/usr/lib32/libGLESv1_CM_nvidia.so.515.57
/usr/lib32/libGLESv2_nvidia.so
/usr/lib32/libGLESv2_nvidia.so.2
/usr/lib32/libGLESv2_nvidia.so.515.57
/usr/lib32/libGLX_nvidia.so
/usr/lib32/libGLX_nvidia.so.0
/usr/lib32/libGLX_nvidia.so.515.57
/usr/lib32/libcuda.so
/usr/lib32/libcuda.so.1
/usr/lib32/libcuda.so.515.57
/usr/lib32/libnvcuvid.so
/usr/lib32/libnvcuvid.so.1
/usr/lib32/libnvcuvid.so.515.57
/usr/lib32/libnvidia-allocator.so
/usr/lib32/libnvidia-allocator.so.1
/usr/lib32/libnvidia-allocator.so.515.57
/usr/lib32/libnvidia-eglcore.so
/usr/lib32/libnvidia-eglcore.so.515.57
/usr/lib32/libnvidia-encode.so
/usr/lib32/libnvidia-encode.so.1
/usr/lib32/libnvidia-encode.so.515.57
/usr/lib32/libnvidia-fbc.so
/usr/lib32/libnvidia-fbc.so.1
/usr/lib32/libnvidia-fbc.so.515.57
/usr/lib32/libnvidia-glcore.so
/usr/lib32/libnvidia-glcore.so.515.57
/usr/lib32/libnvidia-glsi.so
/usr/lib32/libnvidia-glsi.so.515.57
/usr/lib32/libnvidia-glvkspirv.so
/usr/lib32/libnvidia-glvkspirv.so.515.57
/usr/lib32/libnvidia-ml.so
/usr/lib32/libnvidia-ml.so.1
/usr/lib32/libnvidia-ml.so.515.57
/usr/lib32/libnvidia-opticalflow.so
/usr/lib32/libnvidia-opticalflow.so.1
/usr/lib32/libnvidia-opticalflow.so.515.57
/usr/lib32/libnvidia-ptxjitcompiler.so
/usr/lib32/libnvidia-ptxjitcompiler.so.1
/usr/lib32/libnvidia-ptxjitcompiler.so.515.57
/usr/lib32/libnvidia-tls.so
/usr/lib32/libnvidia-tls.so.515.57
/usr/lib32/vdpau/libvdpau_nvidia.so
/usr/lib32/vdpau/libvdpau_nvidia.so.1
/usr/lib32/vdpau/libvdpau_nvidia.so.515.57
/usr/share/licenses/nvidia-utils
/usr/share/licenses/linux515-nvidia/LICENSE
</details>
```
this could be an issue of pamac or pacman aswell, if so then the issue can be closedhttps://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)