Siduction Forum
Siduction Forum => Ideas & Improvements => Topic started by: otto on 2012/12/27, 14:08:45
-
:idea:
Dear siduction buddies,
I suggest E-17 version on siduction because the final official release of Enlightment on 21 december, 2012 on E17. Are E-17 already on the repositories? I have used the bodhi that comes with a E-17 version and I found it wonderful and very light.You can view it at http://www.bodhilinux.com/
Quotation:
“Enlightenment News
E17 Release: ZERO
Dec 21, 2012 at 11:59 PM
E17 has been in development for a long time, and there have been a lot of people involved over the years. At this time, the first and final official release of E17, I think it's important to name names and thank everyone who has been involved over the years”.
Source: http://enlightenment.org/
:?:
-
would be really nice to have a graphical environment with this siduction
T+ = Bye
-
It would be good to have an official Siduction version with E17 but the Debian packagers say they are working on a new release and is simple to install from the repros. I think E17 is probably the most polished of the lightweight desktops, although it is technically described as a WM.
-
Well, suggestions are always nice, though someone has to do the work!
greetz
devil
-
Installing E17 is simple in siduction. It is just
apt-get install e17Finding some sane setup is really difficult, because you have to limit the 'bling' of the desktop manager to get not distracted or bury essential panels under windows, or switch the desktops unintentionally.
You also have to know the applications you need to get a complete desktop. E17 does not care for KDE or GNOME preloaded libraries, but nevertheless is able to get them 'ready in the background'.
-
Well, suggestions are always nice, though someone has to do the work!
greetz
devil
:D
devil,
I know it's not very tough to buid up the E17. Just type as root the code: "apt-get install e17" But the other advantage it's the distros competition. Only the bodhi linux is free. the other one the elivecd at http://www.elivecd.org/ is a paying distro.Btw, It's only a hint for the future.Perhaps it's not very much difficult to develop the E17 at the siduction.This will be another plus with siduction by offering a ready distro with the E17. This is a kind of suite which will attract many new users to the siduction.Enlightenment is not just a window manager for Linux/X11 and others, but also a whole suite of libraries to help you create beautiful user interfaces with much less work than doing it the old fashioned way and fighting with traditional toolkits, not to mention a traditional window manager. It covers uses from small mobile devices like phones all the way to powerful multi-core desktops (which are the primary development environment).
cheers.
:lol:
-
Perhaps it's not very much difficult to develop the E17 at the siduction.
That is not even half the job. Someone, preferably more than one person, is needed to maintain it on a steady base, fix when broken, support where needed. Kicking out a new DE is not the problem.
greetz
devil
-
Installing E17 is simple in siduction. It is just apt-get install e17Finding some sane setup is really difficult, because you have to limit the 'bling' of the desktop manager to get not distracted or bury essential panels under windows, or switch the desktops unintentionally.
You also have to know the applications you need to get a complete desktop. E17 does not care for KDE or GNOME preloaded libraries, but nevertheless is able to get them 'ready in the background'.
This will not install the newest e17, it will install 0.16.999.70492-2
you would have to dofor I in eina eet evas embryo ecore eio edje efreet e_dbus \
evas_generic_loaders ethumb eeze emotion elementary; do \
wget http://download.enlightenment.org/releases/$I-1.7.4.tar.gz; \
done
wget http://download.enlightenment.org/releases/enlightenment-0.17.0.tar.gzexport PATH=/usr/local/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/lib:$LD_LIBRARY_PATH
export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:$PKG_CONFIG_PATH
export CFLAGS="-O3 -fvisibility=hidden -ffast-math"
for I in eina eet evas embryo ecore eio edje efreet e_dbus \
evas_generic_loaders ethumb eeze emotion elementary; do \
tar zxf $I-1.7.4.tar.gz; \
cd $I-1.7.4; \
./configure --disable-gnutls && make && su; make install; \
cd ..; \
donetar zxf enlightenment-0.17.0.tar.gz
cd enlightenment-0.17.0
./configure && make && su; make install; exit
cd ..as rootln -s /usr/local/share/xsessions/enlightenment.desktop /usr/share/xsessions/enlightenment.desktop
A little different from svn or git, trunk (dev) is different also e_dbus is replaced
Yes, I do have it installed :)
-
So will the E17 Final land in Sid after the release of Wheezy?
-
Otto,
I agree with you.
E-17 is a good option for light and beautiful Graphical Environment.It may be a good option for Siduction
-
As devil said: Someone has to do the work. A good start would be a E17-settings-package for siduction. But this can only be build by people knowing E17 and are able to maintain it for the next month and years.
We can offer help with this, we have a space on github for siduction, we have the infrastructure to provide the package. So if anybody is willing to do the work: Go for it.
-
Right, and my understanding is, that E17 will be the hardest to preconfigure from all our DEs, due to the many config options it offers. Looking at Bodhi Linux and using their pre-config as a start would be a good idea imho. In the end E17 could be our prettiest DE.
greetz
devil
-
Is not the point of E17 that it so configurable for individual tastes after installation. The standard Debian and Bohdi versions are quite plain. For a Siduction version the Debian ( or Bohdi) defaults with a Siduction wallpaper would be a good starting point.
-
For a Siduction version the Debian ( or Bohdi) defaults with a Siduction wallpaper would be a good starting point.
I was just looking at Bodhi, and they actually offer SEVEN default profiles! So, it starts getting complicated right away, on the first screen.
I have always though E16 and E17 were beautiful -- I actually ran e-live for some months back when I was distro hopping in 2007.
I have a couple of platforms and some time available to support testing and debugging, but I'm the farthest thing from a developer, and don't know much about E17 either. :(
-
titan: just do it ...
-
titan: just do it ...
If you mean run E17 I am, and have been for a while. The version in Debian is not that much different from the new release so I will wait for it to appear in the repros. It only took an hour or so to find my way around all the configuration options and get a set up I am happy with.
-
I rather thought of a package with siduction settings ... :)
-
I am just trying newest Bodhi (ubuntu-12.04 base) in a virtualbox. It is very different, I had to learn the little trickies, for example:
- If I open a menu near the desktop border - I cannot see the content of submenus reaching out of the desktop. Kde shows the submenu the other side then. ... I needed two evenings to push the mouse direction border of the desktop to see the submenu :(
- I found profiles, enabled the composite profile (after installing virtualbox-guest-dkms). Then all my configs of two evenings got lost :( But it is a beautiful design though ...
- All my desktops are configured to have the close and minimize buttos left - like nearly all desktops nowadays (Xos, ubuntu, gnome). But I cannot find that option yet for Enlightenmet :( The gui config of Enlightenent has a very different tree to reach what you want. Maybe there is some search facility (Anything?). Think of all Kde options and multiply this number with three - that is what you have to learn if you want to reign your enlightenment desktop but not the other way round.
- Bodhi has a taskbar with icons, but they start a new instance, not aktivating an already started instance of a program like standard nowadays.
The list goes on with these little differences ...
After three days - getting used to Enlightenment1 of this Bodhi release - there comes fun slowly more and more. Really impressive performance with little footprint of ressources :)
-
... If I open a menu near the desktop border - I cannot see the content of submenus reaching out of the desktop. ...
I found the same one and opened bug #1751 (http://trac.enlightenment.org/e/ticket/1751) two month ago. They set it on "won't fix", because "intended behavior. move your mouse towards the submenu and it will adjust."
Did not try that so far because I deleted my e17-testinstall, but if you find that it is still there as an annoying and unexpected behaviour, please reopen that bug or else the nearly similar one bug #1802 (http://trac.enlightenment.org/e/ticket/1802) which they declared as fixed.
Gruß, der_bud
-
@der_bud, it is intended. In german words:
Enlightenment hat neben Kde und Ubuntu oft einen dritten Weg gefunden, wie der Benutzer agieren soll, auf den man zuerst nicht gleich kommt! Man muss viel neu lernen! Das wollte ich sagen in meinem verkrüppelten Englisch :)
-
@der_bud, it is intended. In german words:
Enlightenment hat neben Kde und Ubuntu oft einen dritten Weg gefunden, wie der Benutzer agieren soll, auf den man zuerst nicht gleich kommt! Man muss viel neu lernen! Das wollte ich sagen in meinem verkrüppelten Englisch :)
I think a reasonable translation would be like this:
"Enlightenment often provides a "third way", not available in KDE or Gnome/Ubuntu, for the user to interact with the desktop."
@der_bud -- On a USB stick Bodhi installation, which I booted on a Dell Latitude E6500, the action is just as you were informed. If your cursor is close to the screen edge (the right edge in my experiment), the submenus are off the screen, but if you move the cursor toward the submenus, the entire submenu structure moves onto the screen so you can see everything. It does work that way.
-
Yeah, finally realised that it works that way. Did not get that before, because I am not "used to" move my mouse cursor towards an "invisible" submenu, and I think that belongs on the visible screen and should not open outside the edge. Yes, in e17 several things work different... :-)
-
Just another one different: Alt+F4 changes to Desktop4 and is not closing the application. But of cause you can configure this shortkey - as everything if you know where to do that. I found it, but I don't know if I will find the place the next time. You can even configure how the config options are shown. In basic mode some suboptions are not shown. And every module has its own config-module, which you can choose to not load. Then you will certainly search that specific option to configure an eternal time.
I just shreddered my virtualbox Bodhi-Enlightenment by choosing "opengl" compositing. In Virtualbox with virtualbox-guest-extension only software compositing is possible. I don't know how to get to a cli-console to disable opengl mode, because Ctrl-Alt-F2 is fetched by my host system.
-
...Ctrl-Alt-F2 is fetched by my host system.
In Virtualbox-Systems try Host-F2 instead, so if you set your vb-"Host"-key to be right AltGr, use AltGr+Anykey for any Ctrl-Alt-Combination.
And from the Arch-Wiki-E17 (https://wiki.archlinux.org/index.php/E17#Compositing):
Composite provides the more stable module and is supported on most hardware through either OpenGL or compositing software rendering. When the configuration is messed up and the settings windows can no longer be approached, configuration for the comp module can be reset by the hardcoded keybinding Ctrl + Alt + Shift + Home.
As a last resort backup ~/.e and remove it (e.g. mv ~/.e ~/.e.back).
-
@der_bud, very thanks - I had forgotten this Host-F2 key.
I had to delete the old /home/user, because obviously E17 saves its configuration in a binary format. Manipulating a Kde ini files, which is dumb text, is not that a problem.
Inspecting my profile I observed a hundreds instances of ever the same config files. Seemingly a bug not deleting the old when I tried all of that possibilities with E17 configuration.
I expect this kind of bug in a version 1.0. I will consider E17 seriously if their developer team manages to release bug maintainance releases in a manner Kde does this in reliable time frames ...
If they do:
E17 is a very strong contender to all other desktop environments!!!
Although Bodhis Enlightenment-1 has some very useful ready to go profiles I miss some like:
- EnlightenmentProfileForNewbieComingFromUnity
- EnlightenmentProfileForNewbieComingFromKde
which could easening the first steps by configuring most as the user has been used to (eg: Alt-F4)
-
Hi,
I think that Bodhi should be a start point for a siduction E17.
If someone want to help for a siduction E17 he/she must study:
1)E17 settings
2) desktop-defaults, fll-live-initscripts, siduction-settings-$flavour and fll-installer packages.
After doing that it's needed to add:
1) E17 display manager ( it can be lightdm, slim... ) to fll-xdm script from fll-live-initscripts
2) E17 live settings to desktop-defaults-e17
3) E17 installed settings to siduction-settings-e17
It may be possible to be needed to add some scripts to fll-installer package in fll-installer/backends to convert live iso to a regular debian install and maybe to do another things.
If someone want to start a E17 sidction i will try to help.
Thank you.
-
I would also like the E17 version. The version in the repos is very old. I am not a developer but maybe i can help testing.
-
@RAIDENSUB: Find two long term maintainers for the flavour and we are in the business ..
-
As convbsd listed hopefully complete: quiet a bag to carry. A maintainer could begin with source debs from bodhi to have a high starting point.
But never ending: You can preconfigure nearly all with enlightenment. You can make a look alike unity or kde-active out of it, but performing better than the original. That could be fun for someone, many targets can be reached quiet easily and successfully.
But a never ending story ...of fun?
:)
-
I just borked (compiled from git) my e17 1.7.5 , gonna start from scratch
-
As an exercise to teach myself how to build debian packages, I set up a 32-bit siduction Razor-Qt VM and used it to build the new 1.7.5 e17 packages, and installed them with dpkg. In a couple hours of playing with it/getting used to it, everything seems to work as intended. I thought I found a bug with the screen resolution setting, but it's just very "touchy". With a little patience I got it set to 1366x768, which looks fine on my 1920x1200 monitor. This may be an issue with my VMware video setup and might not be a problem on real hardware.
From this experience with the "plain vanilla" E17, I would say it is usable out of the box, but the defaults are nowhere near as flashy as Bodhi. The first login takes you through a couple of preference screens (lappy or desktop?), scaling, and localization screens, and then it's ready to go. There are 26 themes included.
-
Piper does his E17 using pure GNU make commands - but gets borked after a while ...
I would like to use Debian dpkg repository features. But I am a bit overwelmed: Where do I begin to lern building Debian packages?
-
As any other packager: Right from the beginning ...
A good start is the debian manual for new maintainers ...
-
Where do I begin to lern building Debian packages?
For this particular case, you can start here on siduction forum!
Notes -- E17 Build From Source
1. Open these web pages:
http://www.enlightenment.org/p.php?p=contribute&l=en
http://www.debian.org/distrib/packages
http://forums.debian.net/viewtopic.php?p=228570
http://trac.enlightenment.org/e/wiki/Installation
2. On the enlightenment page, install as many of the required and suggested development packages as possible. Some translation to current debian packages can be accomplished by searching the debian packages database.
Also, translating from the enlightenment list to current debian packages:
libfreetype-* = libfreetype6-*
libxcb-xyz-* = libxcb-xyz0-*
lib*svg-dev = lib*svg2-dev
libdbus* = libdbus-1* and libdbus-c++*
zlib* = zlib1g*
3. If you don't have them, install dh-make, cmake, fakeroot, libpoppler-private-dev, texinfo, and devscripts.
4. As user, download the 15 enlightenment tarballs, to your build directory under your user's home folder.
5. At your build directory prompt (use current version numbers!):
for I in eina eet evas embryo ecore eio edje efreet e_dbus evas_generic_loaders ethumb eeze emotion elementary; do tar zxf $I-1.7.5.tar.gz; done
tar zxf enlightenment-0.17.0.tar.gz
Now you have 15 package directories containing the source code tree.
6. Enter each package directory and run dh_make. Answer "s" for single binary.
NOTE: For any tarball and extracted directory name that contains a non-lowercase alphanumeric character other than "-", "+", or ".", like e_dbus and evas_generic, it will be necessary to rename with mv to change the illegal character. It is not really necessary to change the name of the downloaded tarball if you use the "--createorig" option on dh_make (this will make new original tarball).
7. In each package build directory, use "dpkg-buildpackage -rfakeroot -us -uc" " to build the package.
Sequence (build, then install, each package before building the next one):
Eina
Eet
Evas
Evas_Generic_Loaders
Ecore
Eio
Embryo
Edje
Efreet
E_Dbus
Eeze
Emotion (dependency issue with libxine1, resolve with apt-get -f install)
Ethumb
Elementary
Enlightenment
Today I followed this procedure for 64-bit and all is working as expected. But you will spend a lot of time on the Debian package site getting all the xxx-dev packages first.
-
One who will build e17 should be advised to setup a pbuilder and a local repository. and script this.
-
If other siductions users want it, then I would be willing, but I would need a lot of guidance (i.e. I did not read the Debian manual and I can barely write a script for ~.config/autostart and I've never made a local repo ...). In other words, I am unqualified to do it. :cry:
-
hehe,my first longer term relationship with linux begun with karmic koala in 09/10. Before this i know nothing about any linux and mostly nothing about unix. :)
-
Let's see how many siducers care about it, and then we can talk if needed. :)
-
Most of the latest e17 libs are in experimental, but not e17, yet !
-
E17 is now in experimental. All the libs installed Ok but e17 and e17-data had dependency problems with libeio1, I can't find this as a separate lib there are other eio libs but not later versions in in experimental. If anyone has better luck please let us know.
-
0.17.1 was released the other day (bug fixes) plus a first snapshot of E18 (0.17.99.83478). http://enlightenment.org/p.php?p=news/show&l=en&news_id=80
greetz
devil
-
I think the problem is with eio which has still to be uploaded into experimental
http://lists.alioth.debian.org/pipermail/pkg-e-devel/2013-January/001631.html
-
I guess that enlightenment in experimental would be the same version as the one I compiled yesterday.
root@siduction-64vm:/etc/apt/sources.list.d# apt-cache policy enlightenment
enlightenment:
Installed: 0.17.1-1
Candidate: 0.17.1-1
Version table:
*** 0.17.1-1 0
100 /var/lib/dpkg/status
root@siduction-64vm:/etc/apt/sources.list.d# apt-cache policy e17
e17:
Installed: (none)
Candidate: 0.16.999.70492-2
Version table:
0.17.1-1 0
1 http://cdn.debian.net/debian/ experimental/main amd64 Packages
0.16.999.70492-2 0
500 http://http.debian.net/debian/ unstable/main amd64 Packages
eio-1.7.5 was one of the 15 source packages needed from enlightenment.org.
-
The screen resolution issue that I noticed in both 32-bit and 64-bit is apparently a known bug that was reported under Bodhi a couple weeks ago. In ~.xsession-errors I can find this one:
CRI<e>e_gadcon.c:607 DANGLING GADCON CLIENT 0x7f78780dc630! THIS IS A BUG!!!
However in both my 32-bit and 64-bit VMs, I can size the screen as needed -- up to the size of my real monitor (1920x1200) but I don't want it full screen. Once I get it sized, there's no problem, but the size will be not be held across a restart of X, or a reboot.
-
The default color scheme is shades of gray:
(http://img72.imageshack.us/img72/5505/e17screen.png) (http://imageshack.us/photo/my-images/72/e17screen.png/)
-
The default color scheme is shades of gray:
(http://img72.imageshack.us/img72/5505/e17screen.png) (http://imageshack.us/photo/my-images/72/e17screen.png/)
mmm that looks nice for a default E17 theme...bet debian will make use of that color scheme for their own default
How does the default profile work for you?
-
The user profile is under ~/.e/e and I just started exploring there. I confess I don't understand everything I see there. In general, the desktop works out of the box -- I haven't found anything I can't do.
There is a spurious error on logging in, that networking can't be started. I think is due to the NAT bridge on VMware. The network is in fact working correctly (this is siduction underneath the DE).
There are two issues that I would consider bugs, but they're not fatal. The screen resolution is way too "slippery" on a VM, and is hard to set using the graphical settings tool. Somewhere in the guts of it is a file that I could edit, and if I could ever find it I could probably solve that issue. The default is 800x600 which is too small for me. The second issue only happens on my 64-bit VM. Placement of a package on the "shelf" aka launcher works, but the icon is not displayed. In other words, you can tell it is there, because when you hover the cursor over the empty area, it shows the name of the package, and if you click, the package launches, so it is some minor video display problem. It works correctly on 32-bit.
-
I would love to see E17 with siduction. But since I don't know enough about package building I won't be good help I think.
Anyway, I can test things and give feedback if needed.
-
The user profile is under ~/.e/e and I just started exploring there. I confess I don't understand everything I see there. In general, the desktop works out of the box -- I haven't found anything I can't do.
There is a spurious error on logging in, that networking can't be started. I think is due to the NAT bridge on VMware. The network is in fact working correctly (this is siduction underneath the DE).
There are two issues that I would consider bugs, but they're not fatal. The screen resolution is way too "slippery" on a VM, and is hard to set using the graphical settings tool. Somewhere in the guts of it is a file that I could edit, and if I could ever find it I could probably solve that issue. The default is 800x600 which is too small for me. The second issue only happens on my 64-bit VM. Placement of a package on the "shelf" aka launcher works, but the icon is not displayed. In other words, you can tell it is there, because when you hover the cursor over the empty area, it shows the name of the package, and if you click, the package launches, so it is some minor video display problem. It works correctly on 32-bit.
What happens if you were to set it up on a physical 64 bit siduction install?
-
What happens if you were to set it up on a physical 64 bit siduction install?
Yep, I'm thinking about giving it a shot -- I have a Dell laptop running siduction KDE that should support it.
EDIT: I have a Dell E6500 laptop:
System: Host: delle6500 Kernel: 3.7-6.towo-siduction-amd64 x86_64 (64 bit, gcc: 4.7.2)
Desktop: Enlightenment 0.17.1 Distro: siduction 12.1-RC1 Desperado - kde - (201205152133)
Machine: System: Dell product: Latitude E6500
Mobo: Dell model: 0PP476 Bios: Dell version: A14 date: 07/31/2009
CPU: Dual core Intel Core2 Duo CPU P8600 (-MCP-) cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 ssse3 vmx) bmips: 9576.66
Clock Speeds: 1: 2401.00 MHz 2: 2401.00 MHz
Graphics: Card: NVIDIA G98M [Quadro NVS 160M] bus-ID: 01:00.0
X.Org: 1.12.4 drivers: nouveau (unloaded: fbdev,vesa) Resolution: 1920x1200@60.0hz
GLX Renderer: Gallium 0.4 on NV98 GLX Version: 2.1 Mesa 8.0.5 Direct Rendering: Yes
Network: Card-1: Broadcom BCM4312 802.11b/g LP-PHY driver: b43-pci-bridge bus-ID: 0c:00.0
IF: wlan0 state: up mac: 00:23:4e:ab:86:7a
Card-2: Intel 82567LM Gigabit Network Connection driver: e1000e ver: 2.1.4-k port: efe0 bus-ID: 00:19.0
IF: eth1 state: down mac: 00:21:70:d4:d3:04
Drives: HDD Total Size: 120.0GB (44.7% used) 1: model: OCZ_VERTEX
Info: Processes: 132 Uptime: 35 min Memory: 278.7/3948.4MB Runlevel: 5 Gcc sys: 4.7.2
Client: Shell (bash 4.2.37) inxi: 1.8.27
It has a broken ethernet chip and broken CD drive (which is why I got it cheap), but wifi works once you get the firmware installed.
So I took my set of 64-bit E17 deb files and installed them in sequence. The only dependency that was missing was libxp6. I accidently skipped installing the embryo package, and when I tried to install the edje package it errored out saying it could not find embryo. So I backed up and installed in sequence, and everything installed without errors. I restarted X and in KDM found where to change the session to enlightenment.
Upon logging in to enlightenment, I saw the "cannot initialize network" error, which is bogus. The network is fine. So that's a cosmetic bug.
During the little configuration routine, in the background it picked up iceweasel, gimp, and libreoffice and put them on the "I-bar", a launcher on the panel. I had the same problem with chromium browser that I had on the VM. But konsole went on with no problem. When you run a package in enlightenment, if you right-click on the titlebar of the window, there's an option to put the package on the I-bar by default, and it works for konsole, libreoffice, gimp, and iceweasel, but not for chromium-browser, so I think maybe it is a configuration issue with chromium.
The desktop resolution was set at 1920x1200, and looks great. I went in to the screen setting and played with it, and found it just as squirrely as on the VM, so I would consider that buggy behavior, although it works if you hold your mouth just right and say a chant to the monkey-god while stretching it.
Otherwise everything is the same as on the VM, except of course that I have the KDE packages on this system instead of Razor-QT.
There's your report DeepDayze! :)
-
Maybe that cosmetic bug should be reported so a fix/workaround can be posted for it
As well for that other oddities you found on the physical install as well as in the VM's why not put that into the enlightenment bugtracker to see what comes back :)
-
I might do that after I work with it a bit more. I don't wish to expose any more ignorance than absolutely necessary. :)
-
I might do that after I work with it a bit more. I don't wish to expose any more ignorance than absolutely necessary. :)
Don't blame you...anything else you find just let us know :D
-
This is a copy of the report I wrote for the siduction community on google +:
E17 report:
I have been working with E17 on my 64-bit Dell E6500 laptop for a few days, basically trying to get familiar with it, and also to resolve the initial problems that I saw. I have installed new themes from e17-stuff.org, configured the "I_Bar" which KDE users would call a task manager widget on the "shelf" which KDE users would call a panel. All those things work as expected and you can make a beautiful work environment.
After initially installing E17 and going through the configuration procedure for the first login, there were three issues that I thought needed to be fixed, before I would call it a fully satisfactory desktop environment. Of those three issues, I have fully resolved one of them. The other two remain unsolved, and probably will not be solved in the near term. I will describe all three and my attempts to fix them, so anyone else who would like to take a shot can have some information to start with.
1. After login, an error message says:
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 /usr/lib/enlightenment/modules/cpufreqlinux-gnu-x86_64-0.17.1/freqset
sudo chmod u+x.a+x /usr/lib/enlightenment/modules/cpufreqlinux-gnu-x86_64-0.17.1/freqset
The solution to this is:
# chmod 4711 /usr/lib/enlightentment/modules/cpufreq/linux-gnu-x86_64-0.17.1/freqset
2. After login, an error message says:
Shot error: Cannot initialize network
But the networking service is running just fine. So the error message is bogus.
I spent quite a bit of time trying some different things to fix this, based on what I could find online. I changed the network manager from wicd to connman, and I confirmed that the dbus extensions module was loaded. None of it made any difference. I found on sourceforge the source code for the shot function, and I can see the line that generates the error -- it results from checking a URL. I ultimately concluded that this is a bug in the software design, and as requested on the sourceforge page, I sent a detailed message to the enlightenment development team. So, maybe they will change the code, or maybe they think that's the way they want it to work.
3. In the "System" menu, the power off, reboot, hibernate, and sleep items are grayed -- they are not functional for the user. (Of course, "Log Out" works fine, and returns the user to KDM or Light DM). I spent a lot of time working on this, and I think the true answer is, it's over my head to fix it. It would appear to be a user permission problem, or another setuid bit problem. Google led me to multiple "solutions", on arch forums, in the enlightenment docs/wiki, and elsewhere, but none of them fixed it. If I had known how many "solutions" I was going to try and fail, I would have made a more detailed list. But here are things that don't work (but you can find online claims that they do work, including enlightenment documentation):
- modify /etc/enlightenment/sysactions.conf to give the user the options
- modify /usr/local/etc/sysactions.conf to give the user the options
- setuid on /usr/bin/enlightenment_sys
- setuid on /usr/lib/enlightenment/utils/enlightenment_sys
I would suspect this is something about Debian file structures and/or system initialization that is beyond my knowledge (most of that is). The online documentation indicates that /etc/enlightenment/sysactions.conf is where this should be controlled, but apparently that file is not being scanned, or the information is not being registered as the enlightenment devs expect. Reviewing their forum and mailing lists indicates that they would view this as a distro-specific issue and not an issue with their code.
So, I have a good-working and good-looking E17 desktop, with a bogus error message that I can close after login, and the necessity to log out and use KDM to shutdown (or Ctrl-Alt-F1 and root to issue the command). It's not a bad result. :)
-
The problems you have may be caused by self building and installing to /opt . I did a clean install of Arch on my laptop and then installed the latest e17 it all works fine but did not look much different to the version in sid. I have since removed Arch and installed siduction nox (very nice thank you devs) and installed sid's e17 version, all we are waiting for now is libeio to be accepted from new into experimental, it has been there a month now !! and all e17 can be installed from experimental with hopefully sid not too long after that. Connman needs Econnman to work in e17.I just use Ceni, works every time.
-
No, that is why I build debian packages and installed with dpkg. There's nothing in /opt except some old teamviewer package. But, since I could not use apt-get, it is possible that something is not as Debian would expect.
-
There should be no difference installing with either dpkg -i or apt-get. From what I remember, apt-get calls dpkg. But I do think it is not something Debian would expect.
-
The main difference between installing per apt-get or per dpkg is that dpkg does not resolve dependencies. That is why in cases, where those exist, an apt-get -f install is needed.
greetz
devil
-
For step #3, have you tried
ln -s /usr/local/share/xsessions/enlightenment.desktop /usr/share/xsessions/enlightenment.desktop
-
Thanks piper! I tried it, but got the error: "File exists."
-
I don't have it installed at the moment, as you know, I lost everything :), but, I will install tonight, tomorrow, and I usually put it in /opt, all my notes, configs, gone with the wind .... haha
-
Ahhh -- piper you are on the correct theory! I copied /usr/share/xsessions/enlightenment.desktop to /usr/local/share/ and now I can power off from E17. But still the suspend, hibernate and reboot options are grayed out.
-
I don't do suspend, hibernate, lol, but, I can see a reason to with laptops which I don't own.
A couple things you might want to try as root
groupadd power
adduser username
nano /etc/enlightenment/sysactions.conf
add the line:group: power allow: halt reboot suspend hibernateto the bottom of the group section below the line group: plugdev allow: *save the file sysactions.conf, and the user *should* be able to shutdown,halt, reboot, suspend as well as hibernate the computer
I have not tried this myself
-
Yes, that was one of the many "solutions" that I found online. Actually it is still configured that way.
However, here's news. I believe that when I put the enlightenment.desktop file in /usr/local/share/xsessions, I actually fixed the reboot, hibernate, and suspend functions as well. When I said they were grayed out, I was going by the little "light" or "bullet" indicator in front of them. But I just tested reboot, and in fact it rebooted. So ... I dunno why those three little bullets remain gray (or blue?) when the other ones are white.
Anyway, it works, so there's just a couple of minor cosmetic questions lingering at this point.
I would happy to zip up the .debs for anyone who wants to try it.
-
Today I went through the procedure with one of the VMs to make sure I understand what fixes the user privileges issue. Here is what works:
1. Create a "power" group, add your user(s) to that group, and add the power group to /etc/enlightenment/sysactions.conf on a new line under the "plugdev" group, and list the four actions "halt reboot suspend hibernate". (Not sure if a "*" will work there or not). Then copy that file to /usr/local/etc/.
2. Copy /usr/share/xsessions/enlightenment.desktop to /usr/local/share.
3. chmod 4711 /usr/lib/enlightenment/utils/enlightenment_sys
Restart X and the user has full privileges to shutdown, reboot, suspend, or hibernate.
-
Well after nearly four months waiting libeio finally hits experimental. I had given up with E17 and gone back to i3 but today I re-installed it and it all appears to be running fine with no obvious bugs.
-
Figures, been kinda working with snowlinux and siduction to get a working build of e17, I actually like the the snowlinux build better than bodhi and that it is debian and not ubuntu ;)
-
@piper did you encounter the "Shot Error" regarding network initialization? That remains the only bug in my otherwise beautiful E17 desktop.
-
@piper did you encounter the "Shot Error" regarding network initialization? That remains the only bug in my otherwise beautiful E17 desktop.
If you mean the conman (network) error, yes, but it works fine.
No error with snowlinux
-
Yes it comes from conman but there is no connectivity issue -- the error message is bogus. But it's a distraction at each login. I wrote the dev team a message about it, as requested on their website, but I never heard any response.
-
Just installed it - I didn't do the work but check it out
nano /etc/apt/sources.list
add new lines to the list:
deb http://ftp.pl.debian.org/debian/ sid main contrib non-free
deb-src http://ftp.pl.debian.org/debian/ sid main contrib non-free
deb http://www.deb-multimedia.org sid main non-free
Then save the file and update the repo list:
apt-get update
Install e17:
apt-get install e17
After installation put "#" in the front of each sid lines:
and update the repo list again.
The basic setup but easy to add themes and wallpapers
(http://i.imgur.com/CkcXmTJ.png)
-
What are you talking about?
siduction is unstable and unstable = sid.
There is nothing to change in the sources!
-
What are you talking about?
siduction is unstable and unstable = sid.
There is nothing to change in the sources!
Thank you , as an ignoranmus and a newbie I didn't know that , forgive My ignorance