Fresh install, Vanilla Arch?

I installed a fresh EndeavourOS today. I DID admit I unchecked A LOT in the net installer…
But nothing I unchecked should have had the effect of the OS not identifying as Endeavour?

Basically running screenfetch it tells me I am running pure arch, with the Arch logo?


I went back to Cinnamon again. Fresh install of Windows 10 and dual boot EndeavourOS Cinnamon.


I think you will toss & turn in your sleep and reinstall KDE in the morning :rofl:

1 Like

I got issues … :rofl: I do keep on reinstalling it but i just can’t get there. :man_shrugging:


cat /var/log/Calamares.log | curl -F 'f:1=<-'

What exactly am I looking for?

sent 662 bytes  received 45 bytes  1,414.00 bytes/sec
total size is 464  speedup is 0.66
sending incremental file list

sent 514 bytes  received 42 bytes  1,112.00 bytes/sec
total size is 331  speedup is 0.60
sending incremental file list

sent 816 bytes  received 42 bytes  1,716.00 bytes/sec
total size is 634  speedup is 0.74
sending incremental file list

install is looking fine…

╭─joekamprad@empowered64 ~  
╰─$ cat /etc/pacman.d/hooks/lsb-release.hook
Operation = Install
Operation = Upgrade
Type = Package
Target = lsb-release

Description = Add EndeavourOS specifc config.
When = PostTransaction
Exec = /bin/sh -c "sed -i -e s'?^DISTRIB_ID=.*$?DISTRIB_ID=EndeavourOS?' -e s'?^DISTRIB_DESCRIPTION=.*$?DISTRIB_DESCRIPTION=\"EndeavourOS Linux\"?' /etc/lsb-release"

I played around a bit: I can’t determine if the hook doesn’t trigger, or if it’s triggers but fails to do something.

Just realized that when I installed my very first install of EndeavourOS, the last beta before release, this happened. And I was just running the installer as is, obviously; no Net installer to screw up.

I assumed that’s just as it was supposed to be, it being a beta and Eos being closer to Arch anyway than say Antergos or Manjaro.
…But was it? Was it supposed to identify as “Endeavour” and not “Arch” even then? in that case this has happened to me twice, with several months apart on two different computers and two different installers.

1 Like

first versions (beta) do not configure lsb-release but now it should do so!

The hook is there but does nothing.

you did lsb_release -a ?

“Unknown command”.

Do a pacman.d hook and be happy :wink:

Operation = Install
Operation = Upgrade
Operation = Remove
Type = File
Target = etc/lsb-release

Description = lsb-release change description for grub
When = PostTransaction
Exec = /usr/bin/sed -i 's/^DISTRIB_DESCRIPTION.*/DISTRIB_DESCRIPTION="Beardedgeek72 - Arch-Edition"/' /etc/lsb-release
~ >>> lsb_release -a                                                                                  
LSB Version:    n/a
Distributor ID: SGS-Linux
Description:    KDE rocks
Release:        Rolling
Codename:       Privat
1 Like

do you have lsb-release package installed ?

1 Like

Duh. Easiest check ever. I was sure I had not removed it, but I guess I got a bit trigger happy.

…It IS installed, but not in the path. I try to reinstall it and I get “conflicting packages”.

the hook is for if arch update and it change back to arch name as example the hook fixes that to endeavouros

Here’s the full error:

bgeek@dorktower ~ ➤  which lsb-release
which: no lsb-release in (/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/bin/site_perl:/usr/bin/vendor_perl:/usr/bin/core_perl)
bgeek@dorktower ~ ➤  sudo pacman -S lsb-release
resolving dependencies...
looking for conflicting packages...

Packages (1) lsb-release-1.4-15

Total Installed Size:  0,02 MiB

:: Proceed with installation? [Y/n] 
(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%
error: failed to commit transaction (conflicting files)
lsb-release: /etc/lsb-release exists in filesystem
Errors occurred, no packages were upgraded.
Error installing repo packages

bgeek@dorktower ~ ➤  pacman -Qo /etc/lsb-release
error: No package owns /etc/lsb-release

This means it can be removed then reinstalled, right?

its because the hook already made a lsb-release in /etc/ so the owner is not as on the package… but is i think not the important is just neofetch as example where it read from is omportand…the bin file is lsb_release (-a)