Jump to content
  • 0
Sign in to follow this  
Astroboy

A new issue with Moksha is coming, courtesy of E

Question

I updated my laptop to kernel 4.11. Didn't take too long to notice an issue: 'sudo su' and 'su' stopped working, as well as any app that requires admin privileges, such as gparted and synaptic. No admin access anymore. Using the previous installed kernel (4.10 in my case) solves the issue.

 

Guess who's the culprit of this weird issue? something in E. Heads up, there is a storm coming around for us with kernel 4.11:

 

https://forums.gentoo.org/viewtopic-t-1063022-postdays-0-postorder-asc-start-0.html

 

And, as usual, the E devs don't care to take a look:

 

So, it's only the Enlightenment window manager being affected. On the Enlightenment dev list the developers don't know either and to quote the main developers response to someone else report of the issue from yesterday;
 

Quote: but it's a kernel change that creates the issue. what - i don't know. ask your friendly neighbourhood kernel developer. the setuid root binaries are specifically erroring out unable to assume root privs where they could before.

...

 

Problem persist with 4.11.1 and e developers keep blaming kernel, but only e17 is affected from all DE...

Share this post


Link to post
Share on other sites

17 answers to this question

Recommended Posts

  • 0

Beside of the fact that E17 is not very well supported by Kernel 4.11 I have to ask if there is a desperate need of using Kernel 4.11?

 

I am just curious. Is 4.4  too outdated?

Share this post


Link to post
Share on other sites
  • 0

I doubt E devs will spend their time fixing E 17. It's release from 2012. "Unfortunately" Moksha is E17 fork. The only support they will give to last E release with number 21. I am in touch with some of e devs. Their info to me

Share this post


Link to post
Share on other sites
  • 0

I doubt E devs will spend their time fixing E 17. It's release from 2012. "Unfortunately" Moksha is E17 fork. The only support they will give to last E release with number 21. I am in touch with some of e devs. Their info to me

 

This issue affects e21 also, from the e-devel mailing list:

 

Hi,

 

I got the source of kernel 4.11, then comipled, and check the

behaviour of enlightenment (efl 1.18.1, enlightment 0.21.7).

 

At the start up of enlightenment, I got an error message;

 

 There was an error trying to set the cpu power state setting via the

 module's setfreq utility.

 

On the kernel 4.10.x, I never see such a message.

 

And, I tried to use su and sudo command in the terminal, I got a

strange message;

 

fulwood@linux-uw5l:~> sudo

sudo: effective uid is not 0, is sudo installed setuid root

 

fulwood@linux-uw5l:~> su

Password:

su: incorrect password

 

This means, there is a problem concerning uid treatment in the

enlightenment, doesn't it.

also there is a phab report: su not working under kernel 4.11 as well as a discussion on e-users mailing list.

 

It is my impression this is an issue reported/encountered by ppl compiling their own kernels. Now compiling kernels is not for the timid and kernels have lots and lots of options. If you do it wrong stuff doesn't work for you. And things change so what you used to do may no longer work. So give it time someone will get to the bottom of this issue even if perhaps it is a kernel developer.

  • Like 2

Share this post


Link to post
Share on other sites
  • 0

Beside of the fact that E17 is not very well supported by Kernel 4.11 I have to ask if there is a desperate need of using Kernel 4.11?

 

I am just curious. Is 4.4  too outdated?

 

Well, recent kernels have improved support for a lot of drivers, and many of them are not available in the 4.4 release.. Recent kernels have improved support for Intel Skylake and above and, namely 4.11 introduces a new swap concept that is better for SSD disks so, yes, for some of our laptops the 4.11 would be a very welcomed release.

 

4.4 is not "too outdated", but it would really awful to stay forever on 4.4 to 4.10, because those were the last kernel versions that worked fine with E...

  • Like 1

Share this post


Link to post
Share on other sites
  • 0

 

 

It is my impression this is an issue reported/encountered by ppl compiling their own kernels.

 

 

Nope. This issue also arises using the offcial Ubuntu kernel mainline build. I also got the the same weird error "sudo: effective uid is not 0, is sudo installed setuid root"

 

 

 

Share this post


Link to post
Share on other sites
  • 0

Hi, guys

 

I am in no way an expert but why not to stick with the stable E and stable kernel and get rid of the known bugs?

 

The forecast of the shit storm coming does not nurture my optimism.

 

Thank you,

 

Val

Share this post


Link to post
Share on other sites
  • 0

  So give it time someone will get to the bottom of this issue even if perhaps it is a kernel developer.

Which is likely to happen, as usual.

Share this post


Link to post
Share on other sites
  • 0

Nope. This issue also arises using the offcial Ubuntu kernel mainline build. I also got the the same weird error "sudo: effective uid is not 0, is sudo installed setuid root"

 

Nope. This issue also arises using the offcial Ubuntu kernel mainline build. I also got the the same weird error "sudo: effective uid is not 0, is sudo installed setuid root"

 

Interesting. I looked thru the kernels changelog and its configuration settings and saw nothing obvious that would account for this. Still I have faith someone with more familiarity with these kinds of issues will resolve this in time. Bodhi has enough issues of its own without worrying about possible future issues at this point.

Share this post


Link to post
Share on other sites
  • 0

Using the latest kernel is a choice but if you want something bleeding edge I think why not use Debian unstable or something like Arch. The kernel that comes with Bodhi 4.1.0  is just fine and stable. Moksha works fine on the systems here, my own  laptop (Dell), my wifes laptop (Dell) and a Sharkoon game system with Steam I've build for my son with a Asus motherboard, 16GB Corsair mem and 2GB Ati graphics card (4800 series), 240G SSD hd and 1T hd.

  • Like 2

Share this post


Link to post
Share on other sites
  • 0

It is worth noting that Cănărău Constantin has found that specific kernel commit that broke enlightenment. Also worth noting a kernel bug report has been filed on this issue. I am unsure how the kernel devs are going to respond to this issue, whether they will restore the functionality needed by e-devs, specifically restore  LSM_UNSAFE_PTRACE_CAP or rather they will tell  the e-devs what they have been doing is unsafe/wrong and to find another way to deal with what they need. But either way these developments are a good first step towards resolving this issue ;)

  • Like 4

Share this post


Link to post
Share on other sites
  • 0

It is worth noting that Cănărău Constantin has found that specific kernel commit that broke enlightenment. Also worth noting a kernel bug report has been filed on this issue. I am unsure how the kernel devs are going to respond to this issue, whether they will restore the functionality needed by e-devs, specifically restore  LSM_UNSAFE_PTRACE_CAP or rather they will tell  the e-devs what they have been doing is unsafe/wrong and to find another way to deal with what they need. But either way these developments are a good first step towards resolving this issue ;)

 

This issue should be fixed: ptrace: Properly initialize ptracer_cred on fork.

Share this post


Link to post
Share on other sites
  • 0

I run Arch with moksha and I just ran across the lets break sudo issue. I found there is a patch that someone shared because the new kernel broke their enlightenment install, but, I don't know how to install the patch, so, I will have to wait for the patch while using a different DE (currently lxde).

Share this post


Link to post
Share on other sites
  • 0

Finally with 4.11.6-1-ARCH I can use moksha again.

Do you mean you updated the kernel to 4.11.6-1 in Arch?

Share this post


Link to post
Share on other sites
  • 0

Well that is great news :) Glad to know the kernel devs came  thru and it all works again :)

  • Like 1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×