Enlightenment cannot successfully start the enlightenment_system service since it can't become group root. Missing setuid bit?

[Norbert]

Steps to reproduce:
1. Install Enlightenment on 22.04 LTS
2. Login to it

Expected results:
* e17 works normally

Actual results:
* error shown on login

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: enlightenment 0.24.2-8
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Uname: Linux 5.13.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu74
Architecture: amd64
CurrentDesktop: Enlightenment
Date: Mon Dec 27 21:54:03 2021
InstallationDate: Installed on 2021-12-27 (0 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211227)
SourcePackage: e17
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2021-12-27T20:14:17.309279

[axt (axt.)]

A package e17 doesn't exist in Jammy. It's enlightenment with e25.

[axt (axt.)]

You could set the <a href="https://en.wikipedia.org/wiki/Setuid">suid</a>:

# chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_sys
# chmod 4755 /usr/lib/x86_64-linux-gnu/enlightenment/utils/enlightenment_system

[Norbert (nrbrtx)]

The deb-package should install these files with suid bits.
Otherwise it it not user-friendly.

[axt (axt.)]

It's a solution for you and for now.

You only need to search. The issue itself appears from time to time since years, always only scattered (as you can see here - I have never had this problem with Lubuntu or siduction and e17/e18/e19) and in different distributions, e.g. also once in Arch. This would make it an upstream problem.

Possibly the cause is how enlightenment was installed, root or sudo, tty or terminal (so with running DE).

So the question is if you can reproduce the problem.

[Norbert (nrbrtx)]

Source package is still actually named e17 - see https://packages.ubuntu.com/source/jammy/e17 . I have installed Enlightenment from official deb-packages from official Ubuntu repository.

[axt (axt.)]

e17 is the short name for enlightenment 0.17, so it is a version.

e17 is located in universe and is only available for Bionic, but has reached EoS years ago. The package e17 was last updated 5 1/2 years ago.

https://packages.ubuntu.com/search?keywords=e17&searchon=names&suite=all&section=all

"LTS" is promised anyway only for main and restricted.

The name for the source package "e17 (0.25.3-1)" is a contradiction in terms, simply nonsense.

The binary deb package is called enlightenment for Focal, Hirsute, Impish, and Jammy. You should specify this correctly.

https://packages.ubuntu.com/search?keywords=enlightenment&searchon=names&suite=all&section=all

[axt (axt.)]

Your bug report is a month and a half old with enlightenment 0.24.2-8. A development version is in constant movement. Installable now is enlightenment 0.25.3-1.

I also had pointed out the following:

> Possibly the cause is how enlightenment was installed,
> root or sudo, tty or terminal (so with running DE).
>
> So the question is if you can reproduce the problem.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.