manjaro-settings-manager issueshttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues2023-07-26T14:01:09Zhttps://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/142dkms module build fail on "gcc: error trying to exec 'cc1': execvp: No such f...2023-07-26T14:01:09ZPhilip Müllerdkms module build fail on "gcc: error trying to exec 'cc1': execvp: No such file or directory"*Created by: fullmetal1*
When I try to install a kernel through MHM, the module rtl8822bu-dkms-git does not build. If I install the kernel directly through pacman, however, it works just fine.
From the MSM output
```
(2/5) Install DKMS...*Created by: fullmetal1*
When I try to install a kernel through MHM, the module rtl8822bu-dkms-git does not build. If I install the kernel directly through pacman, however, it works just fine.
From the MSM output
```
(2/5) Install DKMS modules
==> dkms install rtl8822bu/5.2.4_20170919 -k 4.16.2-1-MANJARO
Error! Bad return status for module build on kernel: 4.16.2-1-MANJARO (x86_64)
Consult /var/lib/dkms/rtl8822bu/5.2.4_20170919/build/make.log for more information.
```
and the contents of make.log
```
DKMS make.log for rtl8822bu-5.2.4_20170919 for kernel 4.16.2-1-MANJARO (x86_64)
Tue Apr 17 21:18:00 EDT 2018
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/4.16.2-1-MANJARO/build M=/var/lib/dkms/rtl8822bu/5.2.4_20170919/build modules
make[1]: Entering directory '/usr/lib/modules/4.16.2-1-MANJARO/build'
gcc: error trying to exec 'cc1': execvp: No such file or directory
gcc: error trying to exec 'cc1': execvp: No such file or directory
Makefile:974: *** "Cannot generate ORC metadata for CONFIG_UNWINDER_ORC=y, please install libelf-dev, libelf-devel or elfutils-libelf-devel". Stop.
make[1]: Leaving directory '/usr/lib/modules/4.16.2-1-MANJARO/build'
make: *** [Makefile:1801: modules] Error 2
```
and if I do a sudo pacman -S linux416
```
-> % sudo pacman -S linux416
[sudo] password for [REDACTED]:
warning: linux416-4.16.2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) linux416-4.16.2-1
Total Installed Size: 117.11 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%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
(1/1) checking available disk space [######################] 100%
:: Running pre-transaction hooks...
(1/1) Remove DKMS modules
==> dkms remove rtl8822bu/5.2.4_20170919 -k 4.16.2-1-MANJARO
Error! There is no instance of rtl8822bu 5.2.4_20170919
for kernel 4.16.2-1-MANJARO (x86_64) located in the DKMS tree.
:: Processing package changes...
(1/1) reinstalling linux416 [######################] 100%
:: Running post-transaction hooks...
(1/5) Updating linux416 module dependencies...
(2/5) Install DKMS modules
==> dkms install rtl8822bu/5.2.4_20170919 -k 4.16.2-1-MANJARO
(3/5) Updating linux416 initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux416.preset: 'default'
-> -k /boot/vmlinuz-4.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.16-x86_64.img
==> Starting build: 4.16.2-1-MANJARO
-> Running build hook: [base]
-> 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: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.16-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux416.preset: 'fallback'
-> -k /boot/vmlinuz-4.16-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-4.16-x86_64-fallback.img -S autodetect
==> Starting build: 4.16.2-1-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-4.16-x86_64-fallback.img
==> Image generation successful
```https://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/190MSM Notifier shows message every day about new kernel when -- only notify LTS...2022-12-28T09:36:12ZGoku-SanMSM Notifier shows message every day about new kernel when -- only notify LTS kernel -- is set.Hello,
I was redirected here from the forum [relevant post](https://forum.manjaro.org/t/msm-notifier-how-to-only-notify-for-new-lts-kernel/81464/6).
The issue started after the last update 04-Sept-2021 and is just like the title states...Hello,
I was redirected here from the forum [relevant post](https://forum.manjaro.org/t/msm-notifier-how-to-only-notify-for-new-lts-kernel/81464/6).
The issue started after the last update 04-Sept-2021 and is just like the title states, so I tried few different options.
This is what I found out.
```
1. MSM Notifier disabled at start. → no messages all day.
2. MSM Notifier enabled at start
Options
Check new kernels
→ only notify recommended kernels. → no messages.
→ only notify LTS kernel && only notify recommended kernels. → no messages.
→ only notify LTS kernel. → message about new kernel although I am running 5.10 LTS.
```
So for now I am disabling MSM Notifier.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/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/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/144Broadcom wifi fails to install2022-09-12T13:44:36ZPhilip MüllerBroadcom wifi fails to install*Created by: es20490446e*
**💣 HOW TO REPRODUCE:**
Using the Manjaro Settings Manager, connected using ethernet, try to install the wifi controller:
```
03:00.0 Network controller [0280]: Broadcom Limited BCM43228 802.11a/b/g/n [14e4:435...*Created by: es20490446e*
**💣 HOW TO REPRODUCE:**
Using the Manjaro Settings Manager, connected using ethernet, try to install the wifi controller:
```
03:00.0 Network controller [0280]: Broadcom Limited BCM43228 802.11a/b/g/n [14e4:4359]
Subsystem: Broadcom Limited BCM43228 802.11a/b/g/n [14e4:05e2]
Physical Slot: 0-2
Flags: bus master, fast devsel, latency 0, IRQ 19
Memory at d3000000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: bcma-pci-bridge
Kernel modules: bcma
```
**🔥 RESULT:**
The installation fails with:
```
Installing linux414-broadcom-wl-6.30.223.271-33
modprobe: FATAL: Module bcm43xx not found.
modprobe: FATAL: Module brcm80211 not found.
modprobe: ERROR: could not insert 'wl': Exec format error
```https://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/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/167Chinese Translation Problem2022-08-21T19:17:27ZBilly YuanChinese Translation Problem![Screenshot_20190608_120823](/uploads/638dd5a189ae9e10cfd34a24643acca1/Screenshot_20190608_120823.png)
I don't think this sentence is correct.
It should be "安装或删除manjaro内核".![Screenshot_20190608_120823](/uploads/638dd5a189ae9e10cfd34a24643acca1/Screenshot_20190608_120823.png)
I don't think this sentence is correct.
It should be "安装或删除manjaro内核".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/168Incorrect Russian translation for the word "rate" in keyboard settings dialog2022-08-21T19:16:25ZTimurIncorrect Russian translation for the word "rate" in keyboard settings dialogThe keyboard dialog has incorrect translation in the label for the repeat rate [here](https://gitlab.manjaro.org/applications/manjaro-settings-manager/blame/master/src/libmsm/translations/msm_ru.ts#L843), [here](https://gitlab.manjaro.or...The keyboard dialog has incorrect translation in the label for the repeat rate [here](https://gitlab.manjaro.org/applications/manjaro-settings-manager/blame/master/src/libmsm/translations/msm_ru.ts#L843), [here](https://gitlab.manjaro.org/applications/manjaro-settings-manager/blame/master/src/libmsm/translations/msm_ru.ts#L848) and [here](https://gitlab.manjaro.org/applications/manjaro-settings-manager/blame/master/src/libmsm/translations/msm_ru.ts#L853). The word "тариф" means "tariff". Correct translation for the word "rate" here would be "частота".https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/191Bug on Chinese Translations2022-08-21T15:32:59Z19000116041900011604@pku.edu.cnBug on Chinese TranslationsOn Line 871 of [/src/libmsm/translations/msm_zh_CN.ts](https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/blob/master/src/libmsm/translations/msm_zh_CN.ts):
`<translation>已安装的软件包</translation>`
It should be:
`<translat...On Line 871 of [/src/libmsm/translations/msm_zh_CN.ts](https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/blob/master/src/libmsm/translations/msm_zh_CN.ts):
`<translation>已安装的软件包</translation>`
It should be:
`<translation>安装语言包</translation>`
The discussion can be seen at https://forum.manjaro.org/t/topic/83454
Please fix it as soon as possible, thanks!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/166Providing the headers by default2022-06-17T10:23:30ZAlberto Salvia NovellaProviding the headers by defaultI think it will be a good idea that when you install a kernel, the headers package is also installed by default. It saves trouble.
For example the package "deepin-anything-dkms" provides the file "/usr/lib/modules-load.d/anything.conf",...I think it will be a good idea that when you install a kernel, the headers package is also installed by default. It saves trouble.
For example the package "deepin-anything-dkms" provides the file "/usr/lib/modules-load.d/anything.conf", which invoques "vfs_module", which requires the headers to work.
But since Manjaro has a headers package for each kernel, any other package in Arch that assumes a single headers package will find trouble.
That's usually the case with virtualization solutions. If they are not the most frequent ones they frequently fail to launch properly.https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/12[Pacman-mirrors] Add a pacman mirrors manager2022-06-17T00:19:12ZPhilip Müller[Pacman-mirrors] Add a pacman mirrors manager*Created by: Kirek*
Create a page that replicates the functionality of the command line tool pacman-mirrors*Created by: Kirek*
Create a page that replicates the functionality of the command line tool pacman-mirrors0.7https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/14Integrate MSM into xfce-settings2022-06-17T00:19:04ZPhilip MüllerIntegrate MSM into xfce-settings*Created by: manjaro*
We might create kcm modules rather than on extra framework. However we should consider to do the same for xfce-settings-manager if possible, else we should at least have a fallback option so MSM is not purely for K...*Created by: manjaro*
We might create kcm modules rather than on extra framework. However we should consider to do the same for xfce-settings-manager if possible, else we should at least have a fallback option so MSM is not purely for KF5/KDE4.0.6https://gitlab.manjaro.org/applications/manjaro-settings-manager/-/issues/28Doxygen support2022-06-17T00:18:56ZPhilip MüllerDoxygen support*Created by: georoot*
We can start providing doxygen comments in the code for providing a better documentation support.*Created by: georoot*
We can start providing doxygen comments in the code for providing a better documentation support.