Issue with SDDM

To be honest I use the terminal as little as possible except for Topgrade. I like EOS because it’s so minimal without having to deal with things the out and out Arch way.

Seriously you should think about installing the BTRFs set up either encryted or not. Then you can just roll back to an older snapshot. It works really well. I’m getting used to it as i have Btrfs with timemachine and snapshots on triple boot. One is encrypted and two are not. Using refind and i like it because they all have separate grub loading when you select from refind. Something messes up you can roll back if needed.

I have the grub-btrfs for timeshift, and autosnap. I do know EOS needs to fix their install to give a choice of Ex4 or BTRFS so those of us that just want to let the installer do the partition can. As for rolling back to say the 9th the SDDM bug we’re working on doesn’t seem to be show stopper so not worth reupdating things after a rollback. Just a matter of clicking ok, then getting taken to the login screen. No biggy in my book. As for encryption yes when I do rerun I will be encrypting the OS., just wanted to test out BTRFS on EOS before doing that.

I’m not sure what you mean by that. You can do the partitions? You’ll have to explain that one? Also rolling back and doing the updates to bring it up to date is a click for me and takes seconds. I could roll it back to the initial install and it wouldn’t matter. To me it’s really insignificant compared to reinstalling.

When I installed from the live using the July ISO it was either ext4 or manual partition. I chose Manual so I could do btrfs. As for rerunning the OS I currently have it on my Evo 850 SSD which is SATA. I want it on my M.2 where it belongs. What I’ll probably do is keep thew current OS, install to the M.2, slowly build it up and be good to go. As for rolling back if you rollback to when you first installed those updates are going to take awhile. Yes far less time that reinstalling and resetting up everything but still awhile.

That’s correct. I used the Method by @2000 in the wiki to install Btrfsonluks with timeshift and snapshots. Then i used the same method without encryption. I’m don’t think EndeavourOS will have a Btrfs setup automatically from the live ISO. That’s for a user to implement. Some of this stuff is more advanced for some users and those people who know this stuff can easily do it after or during an install.

1 Like

Probably better to use Gparted and create the partitions first and then start the installer. I see that reccomendation all the time regardless of which OS. I know in the part with Windows I got in the habit of booting into Partied Magic, resetting the HDD or SSD, and then create my partitions. Windows for a long time if you used their tools during install to do that a lot of time you ended up with bleed through of items from the previous install. That’s just simply sad. 25 years of playing around with Linux and I’ve never seen that with any Linix distro.

That’s exactly what i do and then when I start the installer I use manual partitioning and select the partitions I created and set the mount and /boot/efi points. You can do it this way or through the gui. I haven’t really had any problems with it either way.

Your permissions are completely screwed.

  • /var/lib should pretty much be root

Example:

#Yours:
drwxr-xr-x 1 alienprober autologin  20 Sep  6 09:27 AccountsService
#Mine:
drwxr-xr-x  4 root    root    4.0K Jul 27 21:29 AccountsService

How to fix is the problem…

Think you issued a chown in the wrong directory?

This is my /var/lib…

ls -lah
total 188K
drwxr-xr-x 46 root    root    4.0K Sep 25 16:53 .
drwxr-xr-x 14 root    root    4.0K Sep 25 16:51 ..
drwxr-xr-x  4 root    root    4.0K Jul 27 21:29 AccountsService
drwxr-xr-x  2 root    root    4.0K Jun 22 10:39 alsa
drwxr-xr-x  2 root    root    4.0K Jun 21 17:13 apparmor
drwxr-xr-x  2 root    root    4.0K Jun  3 08:11 arpd
drwxr-xr-x  2 root    root    4.0K Aug  1 15:05 blueman
drwx------  3 root    root    4.0K Jul 28 19:14 bluetooth
drwxr-xr-x  2 root    root    4.0K Jun 15 21:14 boltd
drwxr-xr-x  2 clamav  clamav  4.0K Aug  9 10:55 clamav
drwxr-xr-x  4 colord  colord  4.0K Aug  1 21:23 colord
drwxr-xr-x  3 root    root    4.0K Sep 19 21:59 connman
drwxr-xr-x  2 root    root    4.0K Sep 11 23:23 connman-vpn
drwx--x--x 10 root    root    4.0K Sep 20 12:17 containerd
drwxr-xr-x  2 root    root    4.0K Jul 27 21:26 dbus
drwxr-xr-x  3 root    root    4.0K Sep  7 23:32 dkms
drwx--x--x 14 root    root    4.0K Sep 20 18:26 docker
drwxrwxrwt  2 root    root    4.0K Nov 13  2019 ex
drwxr-xr-x  6 root    root    4.0K Jul 28 08:42 fwupd
drwxr-xr-x  2 geoclue geoclue 4.0K Aug  2 15:42 geoclue
drwxr-xr-x  2 root    cups    4.0K Aug  1 21:10 hp
drwxr-xr-x  2 root    root    4.0K Jul 27 21:25 krb5kdc
drwxr-xr-x 11 root    root    4.0K Aug 12 21:58 libvirt
drwxrwx--T  2 lightdm lightdm 4.0K Aug 29 16:37 lightdm
drwxrwx--T  2 lightdm lightdm 4.0K Aug 29 16:37 lightdm-data
drwxr-xr-x  4 root    root    4.0K Jul 27 21:32 lirc
drwxr-x---  2 root    locate  4.0K Apr  2 18:02 locate
-rw-r--r--  1 root    root     612 Sep 25 16:34 logrotate.status
drwx------  2 root    root    4.0K Jul 27 21:25 machines
drwxr-xr-x  2 root    root    4.0K May 19 23:42 misc
drwxr-x---  2 root    locate  4.0K Sep 25 17:11 mlocate
drwxr-xr-x  4 mpd     mpd     4.0K Sep  6 14:55 mpd
drwx------  2 root    root    4.0K Sep 25 19:11 NetworkManager
drwxr-xr-x  2 root    root    4.0K Sep 19 14:49 os-prober
drwxr-xr-x  2 root    root    4.0K Jul 29 16:58 PackageKit
drwxr-xr-x  4 root    root    4.0K Sep 25 17:11 pacman
drwx------  2 root    root    4.0K Jul 27 21:25 portables
drwx------  2 root    root    4.0K Jul 27 21:25 private
drwxr-xr-x 13 sddm    sddm    4.0K Jul 27 21:38 sddm
drwxr-xr-x 10 root    root    4.0K Aug  6 22:41 systemd
drwxr-xr-x  2 root    root    4.0K Sep 25 16:51 tlp
drwxr-xr-x  3 root    root    4.0K Jul 27 21:36 tpm2-tss
drwx------  2 root    root    4.0K May 29 13:57 udisks2
drwxr-xr-x  2 root    root    4.0K Jul 27 21:30 uniconf
drwxr-xr-x  2 root    root    4.0K Sep 25 17:02 upower
drwxr-xr-x  2 root    root    4.0K Jul 19 12:15 usb_modeswitch
drwxr-xr-x  2 root    root    4.0K Sep  2 13:47 xkb
2 Likes

Mine shows the following.

drwxr-xr-x 1 root   root    20 Sep  8 21:55 AccountsService

@ricklinux - Same as mine.

@anon83136962 keep away from my bottom :rofl: roll back to a snapshot before you changed permissions for emby.

Then we can try and talk you through changing permissions.

1 Like

Cross your fingers and toes that I haven’t blown something up. Used root actions in Dolphin to gain access to the one Emby folder that’s not suppose to be locked and when that faild I just took ownership of the lib folder. I just used root actions to return ownership to root.

[alienprober@TheMothership lib]$ ls -lh
total 8.0K
drwxr-xr-x 1 root root  20 Sep  6 09:27 AccountsService
drwxr-xr-x 1 root root   0 Jun 22 02:39 alsa
drwxr-xr-x 1 root root   0 Jun 21 09:13 apparmor
drwxr-xr-x 1 root root   0 Aug  8 14:48 arpd
drwxr-xr-x 1 root root   0 Jun 15 13:14 boltd
drwxr-xr-x 1 root root   6 Sep  6 09:27 colord
drwxr-xr-x 1 root root  20 Sep  6 09:26 dbus
drwxr-xr-x 1 root root   0 Feb 22  2020 dhclient
drwxr-xr-x 1 root root  54 Sep 23 07:34 dkms
lrwxrwxrwx 1 root root  12 Sep  9 09:13 emby -> private/emby
drwxrwxrwt 1 root root   0 Nov 13  2019 ex
drwxr-xr-x 1 root root  92 Sep 25 09:26 flatpak
drwxr-xr-x 1 root root  68 Sep  8 16:05 fwupd
drwxr-xr-x 1 root root   0 Sep  6 11:11 geoclue
drwxr-xr-x 1 root root  12 Sep 10 14:30 komga
drwxr-xr-x 1 root root  16 Sep  6 09:25 krb5kdc
drwxr-xr-x 1 root root  26 Sep  6 09:30 lirc
drwxr-x--- 1 root root   0 Sep  1 05:29 locate
-rw-r--r-- 1 root root 245 Sep 25 00:00 logrotate.status
drwxr-xr-x 1 root root   0 Sep 25 11:52 machines
drwxr-xr-x 1 root root  34 Sep 15 13:08 mhwd
drwxr-xr-x 1 root root   0 Aug 21 04:19 misc
drwxr-x--- 1 root root  20 Sep 25 00:00 mlocate
drwx------ 1 root root 270 Sep 25 11:49 NetworkManager
drwxr-xr-x 1 root root   0 Sep 11 08:22 os-prober
drwxr-xr-x 1 root root  18 Sep 25 10:53 pacman
drwxr-xr-x 1 root root  34 Sep  9 08:23 plex
drwxr-xr-x 1 root root   0 Sep 25 11:52 portables
drwx------ 1 root root   8 Sep  9 09:13 private
drwxr-xr-x 1 root root 182 Sep  8 16:02 sddm
drwxr-xr-x 1 root root 222 Sep 25 11:39 snapd
drwxr-xr-x 1 root root 104 Sep  6 09:45 systemd
drwxr-xr-x 1 root root   0 Feb 10  2020 tlp
drwxr-xr-x 1 root root  12 Sep  6 09:32 tpm2-tss
drwx------ 1 root root   0 Aug 15 11:40 udisks2
drwxr-xr-x 1 root root  24 Sep  6 09:28 uniconf
drwxr-xr-x 1 root root 884 Sep 25 04:59 upower
drwxr-xr-x 1 root root   0 Jul 19 04:15 usb_modeswitch
drwxr-xr-x 1 root root  30 Sep  6 09:26 xkb

There is your problem it is a symlink (l in first column).

Change sddm to

sudo chown -R sddm:sddm /var/lib/sddm
1 Like

OK done, Thanks. Still doesn’t explain why Emby or the system had that folder locked in the first place.

Where is private/emby? Full path?

/var/lib/emby/

realpath /var/lib/emby/

Returns?

bash: cod: command not found
[alienprober@TheMothership ~]$ realpath /var/lib/emby/
realpath: /var/lib/emby/: Permission denied
[alienprober@TheMothership ~]$

Use sudo

/var/lib/private/emby

What the BLEEP? according to members of the Emby forums that should be only /var/lib/emby/