[john1@manjaro Dokumente]$ yay
[sudo] Passwort für john1:
:: Paketdatenbanken werden synchronisiert …
core ist aktuell
extra 8,7 MiB 16,4 MiB/s 00:01 [-----------------------------------------------------------------------------] 100%
multilib ist aktuell
:: Vollständige Systemaktualisierung wird gestartet …
Es gibt nichts zu tun
[john1@manjaro ~]$ pacman-mirrors
Pacman-mirrors version 4.24.0
Local mirror status for stable branch
Mirror #1 OK 02:37 Germany https://mirror.23m.com/manjaro/
Mirror #2 OK 00:27 Germany https://manjaro.kurdy.org/
Mirror #3 OK 00:57 Germany https://mirror.netcologne.de/manjaro/
Mirror #4 OK 00:17 Germany https://mirror.alpix.eu/manjaro/
Mirror #5 OK 05:37 Germany http://ftp.tu-chemnitz.de/pub/linux/manjaro/
Mirror #6 OK 00:27 Germany https://ftp.gwdg.de/pub/linux/manjaro/
After recent update for lightdm, system is not applying configuration settings in ~/.profile including: export QT_QPA_PLATFORMTHEME="qt5ct"
for QT theme
If there is no response to this command
echo $QT_QPA_PLATFORMTHEME
Forum users have posted 3 different ways to resolve this:
Copy configuration in ~/.profile to ~/.bash_profile
OR
Configure ~/.bash_profile to read ~/.profile
tee -a ~/.bash_profile <<< "[[ -f ~/.profile ]] && . ~/.profile"
After upgrade While sddm starts (as I understood), screen flickers with some garbage. Autologin brings me to Plasma X11 session with compositing turned off. Triet to switch to Wayland - compositing is working but everything is choppy, even mouse. Amd laptop with Amd graphics + discrete nvidia. I think it might be running at Nvidia now? How to revert back to Amd?
Fixed. The problem was in mesa from non-free repository. Downgraded everything to Manjaro’s repos, now everything works (sad that without video acceleration from non-free repo)
Unsure if I miss something from the link or if it is really necessary for me “to deal with the seal” at this point…
╭─░▒▓ ~ ▓▒░ ░▒▓ 3 ✘ 15:59:42 ▓▒░─╮
╰─ sudo systemctl restart mariadb.service && mariadb-upgrade -u root -p ─╯
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xeu mariadb.service" for details.
╭─░▒▓ ~ ▓▒░ ░▒▓ 1 ✘ 15:59:45 ▓▒░─╮
╰─ systemctl status mariadb.service ─╯
× mariadb.service - MariaDB 11.3.2 database server
Loaded: loaded (/usr/lib/systemd/system/mariadb.service; disabled; preset: disabled)
Active: failed (Result: exit-code) since Sat 2024-03-09 15:59:45 CET; 3s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 2479 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (c>
Process: 2480 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`>
Process: 2508 ExecStart=/usr/bin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_P>
Main PID: 2508 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 303ms
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] InnoDB: Loading buffer pool(s>
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] InnoDB: Buffer pool(s) load c>
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Can't open and lock privileg>
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] Server socket created on IP: >
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] Server socket created on IP: >
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Fatal error: Can't open and >
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Aborting
Mar 09 15:59:45 COMPUTENAME systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FA>
Mar 09 15:59:45 COMPUTENAME systemd[1]: mariadb.service: Failed with result 'exit-code'.
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.se>
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] Server socket created on IP: '0.0.0.0'.
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [Note] Server socket created on IP: '::'.
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Fatal error: Can't open and lock privilege tables: Ta>
Mar 09 15:59:45 COMPUTENAME mariadbd[2508]: 2024-03-09 15:59:45 0 [ERROR] Aborting
Mar 09 15:59:45 COMPUTENAME systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 09 15:59:45 COMPUTENAME systemd[1]: mariadb.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Mar 09 15:59:45 COMPUTENAME systemd[1]: Failed to start MariaDB 11.3.2 database server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 2470 and the job result is failed.
~
~
~
~
╭─░▒▓ ~ ▓▒░ ░▒▓ ✔ 1m 2s 16:01:03 ▓▒░─╮
╰─ mariadb --version ─╯
mariadb from 11.3.2-MariaDB, client 15.2 for Linux (x86_64) using readline 5.1
journalctl -xeu mariadb.service ─╯
Mar 09 16:07:54COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [Note] Plugin 'wsrep-provider' is disabled.
Mar 09 16:07:54COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_>
Mar 09 16:07:54 COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plug>
Mar 09 16:07:54COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [Note] InnoDB: Buffer pool(s) load completed at 240309 16:07:>
Mar 09 16:07:54COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.se>
Mar 09 16:07:54 COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [Note] Server socket created on IP: '0.0.0.0'.
Mar 09 16:07:54 COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [Note] Server socket created on IP: '::'.
Mar 09 16:07:54 COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [ERROR] Fatal error: Can't open and lock privilege tables: Ta>
Mar 09 16:07:54COMPUTENAME mariadbd[3018]: 2024-03-09 16:07:54 0 [ERROR] Aborting
Mar 09 16:07:54COMPUTENAME systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ An ExecStart= process belonging to unit mariadb.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 09 16:07:54 COMPUTENAME systemd[1]: mariadb.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Mar 09 16:07:54COMPUTENAME systemd[1]: Failed to start MariaDB 11.3.2 database server.
░░ Subject: A start job for unit mariadb.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit mariadb.service has finished with a failure.
░░
░░ The job identifier is 2590 and the job result is failed.
How would I attempt post install if the first things won’t work?
But you are right, this fixes the apparent update!
Unsure though if I would touch that on my btrfs system as Arch Wiki says I should partly disable COW.
If the database (in /var/lib/mysql) resides on a Btrfs file system, you should consider disabling Copy-on-Write for the directory before creating any database.
I guess my use case for MySql is less then theoretical anyways.