New issues after upgrade new 6.9kernel based manjaro os

omit * 2, I maybe forget update grub

Here is mine grub config, working with dualboot and remembering the last booted os, see what you are missing (i bet on “menu/saved/savedefault”)

[teo@teo-lenovo-v15 ~]$ cat /etc/default/grub
# GRUB boot loader configuration

GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="LEAVE_THIS_AS_IT_WAS..........."
GRUB_CMDLINE_LINUX=""
GRUB_EARLY_INITRD_LINUX_STOCK=""

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Set to 'countdown' or 'menu' to change timeout behavior,
# press ESC key to display menu.
GRUB_TIMEOUT_STYLE=menu

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

# Uncomment to make GRUB remember the last selection. This requires
# setting 'GRUB_DEFAULT=saved' above.
GRUB_SAVEDEFAULT=true

# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y

# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false

# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true

He actually did.
These are so called “hidden” directories, their name starts with a dot
Path is:
~/.config
and
~/.cache

Seeing it may be easier than describing it.
Having a file manager available in TTY also makes the job much easier for someone not familiar with the command line.

install mc - it is a file manager, short for “Midnight Commander”
sudo pacman -Syu mc
type mc in TTY or in terminal and off you go

No mouse - just keyboard
Arrow keys and Tab to navigate and Enter are the most important.

1 Like

~/.config
~/.local

~/.cache - because the cache is likely to disturb after syncing to Plasma 6

.local and .config - it is possible to be selective - again it is because old configuration may contain settings and values which contradicts one another or is no longer supported.

Hi guys, all issues above were solved,
and one more question:
how should I launch latte-dock successfully in my new system?
I can only see the config page

You dont.
Latte-dock is dead (and will never be compatible with Plasma6).

1 Like

Bad news,
So do we have some replacements?

I’m not sure what you need replacement(s) for.
But I suppose the idea would be to check plasma6 widgets for equitable functionality.

I want to print all history cmmand in console,
but I find out which can only print 10 lines,
So how can I print all of them?

history | less

or

zenity --text-info --title="my history" --filename=$HOME/.bash_history --width=400 --height=600

or

history > $HOME/history.txt | zenity --text-info --title="my history" --filename=$HOME/history.txt --width=600 --height=600

Thanks a lot,
One more question, If I want to make konsole text copy and paste like below, how to config it?
1.zsh left click to select copy, right click to paste;
2.short key: ctrl + C :copy; ctrl + v: paste?

more question, when I try to upgrade the system using yay -Syyu, it print follow fail msg:
→ 1 error occurred:
* request failed: Get “https://aur.archlinux.org/rpc?arg[]=bcompare&arg[]=brave-nightly-bin&arg[]=deepin-udis86&arg[]=deepin-wine-helper&arg[]=deepin-wine-wechat&arg[]=deepin-wine5&arg[]=deepin-wine5-i386&arg[]=deepin-wine6-stable&arg[]=glib&arg[]=gopeed-bin&arg[]=gtk&arg[]=imfile&arg[]=keepassx&arg[]=laptop-mode-tools&arg[]=lib32-udis86-git&arg[]=linuxqq&arg[]=listen1&arg[]=netease-cloud-music&arg[]=stacer&arg[]=vmware-horizon-client&arg[]=yesplaymusic&type=info&v=5”: EOF

So how to solve it forever?

and this:
ERROR:can not fetch ''core.db" from mirrors.tuna.tsinghua.edu.cn : OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to mirrors.tuna.tsinghua.edu.cn:443

These are all AUR packages.
Either you have trouble connecting to the AUR or there is some other issue.

Remove all the AUR packages.

You are having trouble connecting to that mirror.
(seemingly due to SSL [https])

Please check your network configurations.

Archlinux automatically mounts Windows disks without entering a password, so how to config to meet this requirement?

Not sure what you mean as a not needed password may point to an encrypted disk or to a network drive.
Windows disks usually use the NTFS filesystem - here is a forum post that talks about it.

Because I have a dual boot system(win11 + manjaro),
So I want to auto mount and don’t need to input password for windows disk partitions(NTFS, exfat, …)
For now, I need to click the partition n, and it will popup a dialog, hint you need the root password,
So I don’t want to do such trouble, how to automatically run this?

read the post
educate yourself how /etc/fstab works - or systemd-mount units
I’m sure you will find many, many examples if you start looking.

I don’t think so.

Whether you decide to use mount units or fstab that is a choice - but don’t use both for the same device - that will grind the gear.

Using Plasma - you will have kio installed - this mounts on demand using /run/media/$USER and - in case of ntfs or fat - do so with write access - but the /run tree is volatile - it is recreated at boot - so nothing survives over restarts.

If you require the devices mounted at predicatable locations - either a mount unit or fstab - in a predefined location e.g. /data/subfolder

If you only want not to type password when clicking in the file manager - look here

Otherwise, if you want the partition to be mounted on startup, as already written, consider fstab or systemd mount.
A good starting point is

1 Like