Manjaro问题搜集

chenkun大约 12 分钟

1、降级软件包

安装downgrade程序 sudo pacman -S downgrade 降级 sudo DOWNGRADE_FROM_ALA=1 downgrade xxx包 注意DOWNGRADE_FROM_ALA=1一定要按照我上边这样写，不能单独export DOWNGRADE_FROM_ALA=1 设置忽略升级的包第二步会让你选择更新的时候是否要忽略更新，选择y的话，它会在/etc/pacman.conf添加一个忽略，如果不想湖绿，把下面的IgnorePkg注释即可

2、开机报错failed to start rotate log files

2.1 分析问题

logrotate是什么按照老套路分析，先百度了一下logrotate是什么，参考，说白了就是个日志切割，和java里面的差不多。就是防止单文件日志过大，按照一定的规则切割成多个日志，或者删除，比如设置超过一个月直接删除，或者超过10M直接删除等等。
查看logrotate是什么时候启动，以及启动后的状态。首先我们知道它是一个systemctl启动的service服务。那就到/lib/systemd/system下看一下ll |grep rotate

 ll|grep rota
-rw-r--r-- 1 root root  870  1月  8  2021 logrotate.service
-rw-r--r-- 1 root root  191  1月  8  2021 logrotate.timer

可以看到和这个问题open in new window一模一样的套路。 3. 到 logrotate.service查看它实际上执行的是什么命令

$ cat logrotate.service     
[Unit]
Description=Rotate log files
Documentation=man:logrotate(8) man:logrotate.conf(5)
RequiresMountsFor=/var/log
ConditionACPower=true

[Service]
Type=oneshot
ExecStart=/usr/sbin/logrotate /etc/logrotate.conf

# performance options
Nice=19
IOSchedulingClass=best-effort
IOSchedulingPriority=7

# hardening options
#  details: https://www.freedesktop.org/software/systemd/man/systemd.exec.html
#  no ProtectHome for userdir logs
#  no PrivateNetwork for mail deliviery
#  no NoNewPrivileges for third party rotate scripts
#  no RestrictSUIDSGID for creating setgid directories
LockPersonality=true
MemoryDenyWriteExecute=true
PrivateDevices=true
PrivateTmp=true
ProtectClock=true
ProtectControlGroups=true
ProtectHostname=true
ProtectKernelLogs=true
ProtectKernelModules=true
ProtectKernelTunables=true
ProtectSystem=full
RestrictNamespaces=true
RestrictRealtime=true

可以看到ExecStart=/usr/sbin/logrotate /etc/logrotate.conf 执行的是这个命令，那就好办了，手动以debug模式执行一下此命令 4. 查看执行结果

$ sudo logrotate --debug /etc/logrotate.conf                              
[sudo] chenkun 的密码：
WARNING: logrotate in debug mode does nothing except printing debug messages!  Consider using verbose mode (-v) instead if this is not what you want.

reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file cups
reading config file lirc
reading config file mysqlrouter
error: mysqlrouter:31 unknown option 'var' -- ignoring line
error: mysqlrouter:45 unexpected }
error: found error in file mysqlrouter, skipping
reading config file nginx
reading config file samba
warning: 'monthly' overrides previously specified 'weekly'
Reading state from file: /var/lib/logrotate.status
Allocating hash table for state file, size 64 entries
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state
Creating new state

Handling 6 logs

rotating pattern: /var/log/cups/*_log  weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/cups/access_log
  Now: 2021-07-15 09:24
  Last rotated at 2021-07-11 16:22
  log does not need rotating (log has been rotated at 2021-07-11 16:22, which is less than a week ago)
considering log /var/log/cups/error_log
  Now: 2021-07-15 09:24
  Last rotated at 2021-07-11 16:22
  log does not need rotating (log has been rotated at 2021-07-11 16:22, which is less than a week ago)

rotating pattern: /var/log/lircd  weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/lircd
  log /var/log/lircd does not exist -- skipping

rotating pattern: /var/log/nginx/*log  weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/nginx/access.log
  Now: 2021-07-15 09:24
  Last rotated at 2021-06-02 08:34
  log does not need rotating (log is empty)
not running postrotate script, since no logs were rotated

rotating pattern: /var/log/samba/log.smbd /var/log/samba/log.nmbd /var/log/samba/*.log  weekly (4 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/samba/log.smbd
  log /var/log/samba/log.smbd does not exist -- skipping
considering log /var/log/samba/log.nmbd
  log /var/log/samba/log.nmbd does not exist -- skipping
considering log /var/log/samba/*.log
  log /var/log/samba/*.log does not exist -- skipping

rotating pattern: /var/log/wtmp  monthly (1 rotations)
empty log files are rotated, only log files >= 1048576 bytes are rotated, old logs are removed
considering log /var/log/wtmp
  Now: 2021-07-15 09:24
  Last rotated at 2021-03-20 18:00
  log does not need rotating ('minsize' directive is used and the log size is smaller than the minsize value)

rotating pattern: /var/log/btmp  monthly (1 rotations)
empty log files are rotated, old logs are removed
considering log /var/log/btmp
  Now: 2021-07-15 09:24
  Last rotated at 2021-07-01 19:33
  log does not need rotating (log has been rotated at 2021-07-01 19:33, which is less than a month ago)

在日志中找error
报错很明显了是mysqlroute的日志切割失败了。
logrotate其实是被很多程序都使用了，其配置文件在/etc/logrotate.d下

可以看到nginx ，mysqlrouter，Samba等都用了logrotate，并且他们都有自己的配置，根据上面我们已经知道了是mysqlrouter配置有问题，我们只需要打开nginx的配置和mysqlrouter对比就知道了。经过比我我的mysqlrouter的配置文件在var前面少了一个/ 加上就好了

linux下输入法无法输入中文中括号问题

如果使用的是fcitx5，修改/usr/share/fcitx5/punctuation/punc.mb.zh_CN下的对应符号即可，打开文件有两列，第一列代表英文状态下的符号，第二列是中文下符号。有时发现无论怎么输入都只有英文，那么就续呀点击一下输入法上的半角符号

3、美化

kde设置proxy有个很大的bug,就是无法全局，搞笑的是通过kde设置的proxy,它自己都无法使用，在国内用kde下载主题、图标等根本下载不动。

解决办法就是挂梯子，下载后手动安装，

4、设置yakuake提示没有权限修改文件

修改yakuake的文字大小

保存时会报错，大概是没有/usr/share/konsole的权限
添加一下权限就行了

给当前用户添加一下权限，chmod 666 xxx

4、Manjaro不支持Mysql

在Manjaro上使用mysql,经常会遇到libicu不兼容问题，即使解决了，下次系统滚动升级可能又会出现

4.1 使用MariaDB代替mysql

4.2 使用docker安装Mysql

5、Manjaro设置DNS

用双网卡同时上内外网，有时一个域名是内网才能解析的，比如我司的iccm.sonoscape.com，这个是一个内网域名，要走内部DNS才能访问到，
但是公司因该是有两个DNS服务器，一个用来解析外网访问xxx.sonoscape.com，另一个是用来访问内网的xxx.sonoscape.com,

6、Manjaro fcitx5中文大括号问题

sudo vim /usr/share/fcitx5/punctuation/punc.mb.zh_CN

修改对应的行符号就可以了

[ 【
] 】

7、分支管理

7.1 概述

Template:重要 One of the many features that sets Manjaro apart from other Arch-based distributions is that it uses its own dedicated software branches, rather than relying on those provided by Arch itself. In fact, to ensure continued stability and reliability, Manjaro actually uses three distinct branches:

Stable branch : The packages that come to stable have gone through roughly a couple of weeks testing by the users of the Unstable/Testing repos, before they get the packages. These packages are usually free of any problems.
Testing branch: This is the second line of defense. Being a larger number of users than those using Unstable, they refine the work done prior to them by providing feedback on the packages they recieve on updates.
Unstable branch : Unstable is synced several times a day with Arch package releases. Only a subset of Arch packages are modified to suit Manjaro. Those that use Unstable need to have the skills to get themselves out of trouble when they move their system to this branch. They are the Manjaro users who are most likely to need to use such skills. Due to the feedback from the users of the Unstable repo, many issues are caught and fixed at this level. Although the very latest software will be located here, using the unstable branch is usually safe but - in rare cases - may cause issues with your system!

Summing up , Manjaro packages start their lives in the unstable branch. Once they are a deemed stable, they are moved to the testing branch, where more tests will be realized to ensure the package is ready to be submitted to the stable branch.

Note on unstable branch

Remember: Manjaro specific packages such as kernels, kernel modules and Manjaro applications enter the repo on unstable branch and it is those packages which are considered unstable when they enter. Unmodifed packages synced from Arch repo are considered stable as they have already been vetted by Archlinux Community.

7.2切换分支

In order to access a branch, you need to change your pacman-mirrors configuration.

You should substitute the value colored in green (for illustrative purposes only) to one of the following: stable, testing or unstable.

sudo pacman-mirrors --api --set-branch {branch}

After you changed the branch, rebuild the mirrorlist and update your packages:

sudo pacman-mirrors --fasttrack 5 && sudo pacman -Syyu

7.3 How do I go back after changing to one of the testing branches?

Going back to the stable branch is easy. All you have to do is to repeat the above, and use stable as the branch value.

Be aware that after switching to a more stable branch you will receive messages from pacman, informing about newer packages installed than available in the repo. Don't be alarmed as the situation will resolve itself when the packages reaches your current branch.

If for whatever reason you do wish to also 'downgrade' packages while changing branches add an extra u to the pacman command:


### 8、wine安装exe报错

报错内容

~~~shell

Runtime Error (at - 1:0):
Cannot Import dll:C:\users\xxx\Temp\is-00IEG.tmp\isskin.dll

解决方法

1. 安装winetricks
   `sudo pacman -S winetricks`
2. 用winetricks安装必要的依赖
  `winetricks vcrun6sp6`

参考：

https://www.linuxquestions.org/questions/red-hat-31/wine-runtime-error-isskin-dll-issue-879119/

https://wiki.winehq.org/Winetricks

9、解压缩中文乱码

使用下面命令：

unzip -O cp936  'xxx.zip'

ArchLinux 需要安装 unzip-iconv

10、vmware使用问题

在manjaro安装了vmware17版本，然后安了一个deepin系统，无法使用虚拟网卡，以为是deepin的问题，然后换其他发行版，同样不行。然后开启了排查之路

尝试路线：

开始以为是桥接/nat配置问题，然后各种尝试，没卵用
然后尝试降低vm版本，降低版本后遇到vmnet/vmmon问题
更换manjaro内核，从6+版本内核降级到5.15,然后安装vm17,安装好以后加载vmnet/vmmon模块，然后启动虚拟网sudo vmware-networks --start，居然好了
为了确认6.0内核是否有问题，我又重启系统，选择6.4的内核，开机后挂载vmnet,发现又和之前一样了，一直挂载不了，基本可以确认vmware和6.0内核还不兼容

总结：

manjro必须使用6.0以下的内核
安装vm17后，必须手动加载模块 sudo modprobe vmnetsudo modprobe vmmon
启动虚拟网 sudo vmware-networks --start

提示

以上方法作废，在比较新的linux内核上vmware支持的不够友好，在Manjaro官方是不支持vmware的，如果实在要安装vmware，不要用yay也不要用archlinuxcn中的，

How to install VMware

Enable CPU virtual extensions in your system’s firmware.

To install vmware on Manjaro you will have to resort to a PKGBUILD script.

There is a lot of AUR helpers and they all mimic what you should do manually - the Arch way is usually the best way.

Important kernel precaution

The AUR PKGBUILD is created for Archlinux and therefore the kernel headers dependency must be solved manually on Manjaro. Archlinux only have two kernel versions - linux and linux-lts.

Archlinux kernels follow the release schedule on kernel.org 23 and on Manjaro you will need to use the same kernel version.

19 June 2023 (Copenhagen)

Linux 6.3.x (stable)
Linux 6.1.x (LTS)

Using other kernels will most likely fail.

Building steps

Update your system and Install the necessary build tools

sudo pacman -Syu git base-devel --needed

Then check your kernel version(s) - example - remember to use the same version as Arch

$ mhwd-kernel -li

Currently running: 6.3.8-1-MANJARO (linux63) The following kernels are installed in your system:

linux61
linux63

Then install the headers for your kernel(s) and dkms (use the kernels listed from your system) sudo pacman -Syu $KERNELXYY-headers dkms
Clone the PKGBUILKD script git clone https://aur.archlinux.org/vmware-workstation.git

expect output like this

Cloning into 'vmware-workstation'...
remote: Enumerating objects: 498, done.
remote: Counting objects: 100% (498/498), done.
remote: Compressing objects: 100% (239/239), done.
remote: Total 498 (delta 307), reused 439 (delta 258), pack-reused 0
Receiving objects: 100% (498/498), 256.62 KiB | 3.21 MiB/s, done.
Resolving deltas: 100% (307/307), done.

Familiarize yourself with the content - it is all text files and you should read them and verify what they are doing. ls ~/vmware-workstation
When you are satisfied - cd into the folder and run makepkg to install dependencies, build and install the package.

cd ~/vmware-workstation
makepkg -is

The post install message reads

==> Before using VMware, you need to reboot or load vmw_vmci and vmmon kernel modules (in a terminal on root: modprobe -a vmw_vmci vmmon)
==> You may also need to enable some of the following services:
- vmware-networks: to have network access inside VMs
- vmware-usbarbitrator: to connect USB devices inside VMs
These services can be activated during boot by enabling .service units or only when a VM is started by enabling .path units.

Choose either of the options - not both

To start and enable vmware network and usb service at boot

sudo systemctl enable --now vmware-networks.service
sudo systemctl enable --now vmware-usbarbitrator.service

To start and enable vmware network and usb on demand

sudo systemctl enable --now vmware-networks.path
sudo systemctl enable --now vmware-usbarbitrator.path

Either reboot your system or load the kernel modules by hand

sudo modprobe -a vmw_vmci vmmon Because the resulting build is using dkms - you won’t have to rebuild the kernel modules on system update - dkms will take care of this.

参考： https://forum.manjaro.org/t/root-tip-how-to-installing-vmware-on-manjaro/57596

11、vnc

在manjaro一直使用的realvnc,这是一个商业软件，使用体验一直不错，不过在某次升级后，无法破解所以放弃了它，后来转用tigervnc,记录以下tigervnc的使用

安装软件

##安装以后会自动包含客户端和服务端
sudo pacman -S tigervnc

服务端设置密码

#根据提示输入
vncpasswd

启动服务端

#启动一个服务，监听5901,以此类推vncserver :2 监听5902……
vncserver :1

客户端使用任何一个vnc客户端都可以连接，可以用realvnc,tigervnc，ultravnc等客户端都行，需要注意的是一定要开启键盘鼠标

20231013103250

12、Remmina远程windows字体发虚

使用remmina远程windows，字体发虚，尤其chrome浏览器，在视觉效果自定义中选择“平滑屏幕字体边缘”重新打开chrome发现就好了，但是断开remmina重新连接发现 “平滑屏幕字体边缘”又被去掉了勾选。

20240416112834

解决方法：在remmina设置——高级——画质，选择最好（最慢）就可以了

20240416112927

13、manjaro-kde下idea新版本UI问题

新版本IDEA的UI在manjaro-kde下显示没有使用KDE桌面设置的样式， 20240808112352

解决方案如下： 20240808112509

设置后重启idea，效果如下，终于和我设置的样式一致了： 20240808112611

12、GTK3主题设置

gtk开发的软件在kde桌面下，默认的窗口样式不好看，设置好全局主题后对GTK软件是不生效的，需要单独设置GTK3主题，在kde桌面下，右键点击桌面，选择设置，选择主题，选择GTK3主题，有的主题会专门提供GTK，设置方法如下： 20240815143416

下载对应主题的gtk包，然后选择应用，当然有的主题作者没有提供gtk包，那就随便选择一个其他主题的gtk包就行了， 20240815143437