all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ng0 <ng0@pragmatique.xyz>
To: 27311@debbugs.gnu.org
Subject: bug#27311: Enlightenment: 'cpufreq binary needs suid or has to be owned by root'
Date: Sat, 10 Jun 2017 15:03:23 +0000	[thread overview]
Message-ID: <20170610150323.qqys6t7febaalmra@abyayala> (raw)

[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]

To reproduce (on an desktop computer):

Add enlightenment to your system config, reconfigure,
reboot, log in and click through the Enlightenment
first start dialogue (which itself reveals more bugs ;))
and the first message box you get after you completed
the first start dialogue and E21 has loaded is this:

Cpufreq Permissions Error

The freqset binary in the cpufreq module
is not owned by root or does not have the
setuid bit set. Please ensure this is the
case. For example:

sudo chown root /gnu/store/aaaaaaaaaaa-enlightenment-0.21.7/lib/enlightenment/modules/cpufreq/linux-gnu-x86_64-ver-0.21/freqset
sudo chmod u+s,a+x /gnu/store/aaaaaaaaaaa-enlightenment-0.21.7/lib/enlightenment/modules/cpufreq/linux-gnu-x86_64-ver-0.21/freqset




It seems like we need to have an 'enlightenment-service' similar to
xfce4 and gnome.

There's a number of dysfunctional features at the moment, I like to
track them all in related or unique bugs.
-- 
ng0
OpenPG: A88C8ADD129828D7EAC02E52E22F9BBFEE348588

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2017-06-10 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-10 15:03 ng0 [this message]
     [not found] ` <handler.27311.B.149710706324063.ack@debbugs.gnu.org>
2017-06-11 16:35   ` bug#27311: Acknowledgement (Enlightenment: 'cpufreq binary needs suid or has to be owned by root') ng0
2017-06-11 17:25     ` ng0
2017-06-21  8:00       ` Ricardo Wurmus
2018-08-05  9:44         ` Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170610150323.qqys6t7febaalmra@abyayala \
    --to=ng0@pragmatique.xyz \
    --cc=27311@debbugs.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.