Skip to main content
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: Startx broke after installing plasma (Read 2670 times) previous topic - next topic
0 Members and 9 Guests are viewing this topic.

Re: Startx broke after installing plasma

Reply #15
I'm not sure I understand. What is the exact error?
Probably not a good idea. I wasn't able to see your Xorg.0.log even with the password "artixlinux", so what video card do you have?

1. I kind of forget what error it is, but iirc it's "..../lib/ is empty. Ignoring..." And after a bunch of that line in the end it says "Error installing, aborting" so I assume that pacman fails to install Xorg since a lot of files in /lib/ is missing/empty.
2. The Xorg.0.log is empty, I notice when the start screen dialog comes up there's one line that says "waiting for events: event logging is off" so idk if that's the problem. My video card is Radeon RX 5600xt. I've installed mesa driver for it.

Re: Startx broke after installing plasma

Reply #16
1. I kind of forget what error it is, but iirc it's "..../lib/ is empty. Ignoring..."
"/lib/ is empty. Ignoring..." means the directory (folder) lib is empty, aka it has no files, which is different than having files with zero length in it.  Running find /usr/ -empty -type fd -delete takes into account both, as well as not distinguishing between possible problematic files and files and directories which are necessary but empty, creating a potential much bigger problem. Can you provide /var/log/pacman.log?

Re: Startx broke after installing plasma

Reply #17
"/lib/ is empty. Ignoring..." means the directory (folder) lib is empty, aka it has no files, which is different than having files with zero length in it.  Running find /usr/ -empty -type fd -delete takes into account both, as well as not distinguishing between possible problematic files and files and directories which are necessary but empty, creating a potential much bigger problem. Can you provide /var/log/pacman.log?
Here's the log:

Re: Startx broke after installing plasma

Reply #18
There are two places in the log which might be indicative, namely:
Code: [Select]
[2021-02-24T23:28:31+0700] [ALPM] running 'fontconfig.hook'...
[2021-02-24T23:28:31+0700] [ALPM-SCRIPTLET] Fontconfig error: Cannot load default config file: No such file: (null)
Code: [Select]
[2021-02-25T23:45:46+0700] [ALPM] installed lib32-fontconfig (2:2.13.91+48+gfcb0420-2)
[2021-02-25T23:45:46+0700] [ALPM-SCRIPTLET] Rebuilding 32-bit fontconfig cache...Fontconfig error: Cannot load default config file: No such file: (null)
This means the fontconfig installation hook is failing for some reason.

Also,  not sure if related (probably not looking at the datetimes), but yay-git is a development version of yay, I would use yay instead:
Code: [Select]
[2021-03-17T15:14:10+0700] [PACMAN] Running 'pacman -R yay'
[2021-03-17T15:14:11+0700] [ALPM] transaction started
[2021-03-17T15:14:11+0700] [ALPM] removed yay (10.1.2-2)
[2021-03-17T15:14:11+0700] [ALPM] transaction completed
[...]
[2021-03-17T15:17:59+0700] [PACMAN] Running '/usr/bin/pacman -U /opt/yay-git/yay-git-10.1.2.r32.gece81fa-1-x86_64.pkg.tar.zst'
[2021-03-17T15:18:01+0700] [ALPM] transaction started
[2021-03-17T15:18:01+0700] [ALPM] installed yay-git (10.1.2.r32.gece81fa-1)
[2021-03-17T15:18:01+0700] [ALPM] transaction completed

Re: Startx broke after installing plasma

Reply #19
There are two places in the log which might be indicative, namely:
Code: [Select]
[2021-02-24T23:28:31+0700] [ALPM] running 'fontconfig.hook'...
[2021-02-24T23:28:31+0700] [ALPM-SCRIPTLET] Fontconfig error: Cannot load default config file: No such file: (null)
Code: [Select]
[2021-02-25T23:45:46+0700] [ALPM] installed lib32-fontconfig (2:2.13.91+48+gfcb0420-2)
[2021-02-25T23:45:46+0700] [ALPM-SCRIPTLET] Rebuilding 32-bit fontconfig cache...Fontconfig error: Cannot load default config file: No such file: (null)
This means the fontconfig installation hook is failing for some reason.

Also,  not sure if related, but yay-git is a development version of yay, I would use yay instead:
Code: [Select]
[2021-03-17T15:17:59+0700] [PACMAN] Running '/usr/bin/pacman -U /opt/yay-git/yay-git-10.1.2.r32.gece81fa-1-x86_64.pkg.tar.zst'
[2021-03-17T15:18:01+0700] [ALPM] transaction started
[2021-03-17T15:18:01+0700] [ALPM] installed yay-git (10.1.2.r32.gece81fa-1)
[2021-03-17T15:18:01+0700] [ALPM] transaction completed
[2021-03-17T15:19:14+0700] [PACMAN] Running 'pacman -U --noconfirm --config /etc/pacman.conf -- /home/kevin/.cache/yay/librewolf/librewolf-86.0-1-x86_64.pkg.tar.zst'
I see, so is there anyway to fix the font config error? Also thanks for reminding that, I'll be sure to use the yay instead of yay-git

Re: Startx broke after installing plasma

Reply #20
I think this might be due to a missing default fontconfig configuration file /etc/fonts/fonts.conf, which is included in fontconfig package. My current version of fontconfig is world/fontconfig 2:2.13.93-4.

The command fc-conflist should give a list of configuration files for fontconfig. Those files which are used are marked with a +, and the others with a -. You can pass the output through less to preview it:
Code: [Select]
$ fc-conflist | less
or redirect it to a file so we can check it out:
Code: [Select]
$ fc-conflist > fc-config.txt

Re: Startx broke after installing plasma

Reply #21
This is the fc-config requested:

Re: Startx broke after installing plasma

Reply #22
Your fc-conflist output looks normal. The mentioned fontconfig hook is located in /usr/share/libalpm/hooks/fontconfig.hook, and contains:
Code: [Select]
[Trigger]
Type = Path
Operation = Install
Operation = Upgrade
Operation = Remove
Target = etc/fonts/conf.d/*
Target = usr/share/fonts/*
Target = usr/share/fontconfig/conf.avail/*
Target = usr/share/fontconfig/conf.default/*

[Action]
Description = Updating fontconfig cache...
When = PostTransaction
Exec = /usr/bin/fc-cache -s
so check if the command fc-cache -s is reporting any errors. On my system, it doesn't output anything (good).

Re: Startx broke after installing plasma

Reply #23
try  reinstall your fontconfig with "sudo pacman - Syy fontconfig" and /or pacman - Syyu.  be sure, that your mirror is not up-to-date  (actually version is fontconfig 2:2.13.93-4).

Re: Startx broke after installing plasma

Reply #24
Your fc-conflist output looks normal. The mentioned fontconfig hook is located in /usr/share/libalpm/hooks/fontconfig.hook, and contains:
Code: [Select]
[Trigger]
Type = Path
Operation = Install
Operation = Upgrade
Operation = Remove
Target = etc/fonts/conf.d/*
Target = usr/share/fonts/*
Target = usr/share/fontconfig/conf.avail/*
Target = usr/share/fontconfig/conf.default/*

[Action]
Description = Updating fontconfig cache...
When = PostTransaction
Exec = /usr/bin/fc-cache -s
so check if the command fc-cache -s is reporting any errors. On my system, it doesn't output anything (good).
I've tried this and there's no error. It's the same like on your system.

try  reinstall your fontconfig with "sudo pacman - Syy fontconfig" and /or pacman - Syyu.  be sure, that your mirror is not up-to-date  (actually version is fontconfig 2:2.13.93-4).
I also do this, and still, startx can't work.


 

Re: Startx broke after installing plasma

Reply #26
Sorry, I think you just might need to reinstall everything. That find ... -delete command likely did more harm than good, in addition to something else before that.

Yea, I think that's the only solution. I've finished backing up everything except for a Windows vm with 30GB .vdi. Too bad I put my actual license on it. Can .vdi file be split into several 6GB files and be merged later?

Re: Startx broke after installing plasma

Reply #27
Anyway, I'll mark this as solved. Thanks a lot to @strajder and @alium for helping me.