SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Works well and is fast. Looks good too. Can't lock the screen though because no PAM, but that's okay for now, I just reboot into something else if I need to do that for any reason.
Hightlights (IMHO):
- Terminology
- Candy for my eyes
- Still responsive and efficient
- Slackware theme
- Additional apps included with SlackE17 (good selection)
Lowlights:
- No network file support in EFM, so no way to access SMB shares etc.
- Categories in application menu not translated (so you get English "Office" instead of German "Büro" and "Development" instead of "Entwicklung", although everything else is translated)
I downloaded the x86_64 packages from Sourceforge and chose the max install option. When I tried to launch E17 from startx it walked me through the configuration steps but kept saying almost done but never completed. Any ideas?
I couldn't reproduce your problem on my 2 test systems. You should try to get the logs, for instance by launching X with:
Code:
$ startx 2>&1 | tee /tmp/e17.log
And then search /tmp/e17.log for any special problem.
There is maybe a bug in the wizard, you can try to run e17 in a Xephyr window (under any other window manager). Go to: http://svn.enlightenment.org/svn/e/b...enment-0.17.0/
and grab x-ui.sh and xdebug.sh. Run one of these scripts from a terminal emulator and watch the output.
When starting after a reboot the panel doesn't appear, and the other panel appears as static. Doesn't happen after logging out and back in. The first panel is set to invisible, so perhaps it's just the stuff on it not appearing. Only seems to happen immediately after booting.
Weird. Did you remove your old ~/.e folder before launching e17 for the first time? Did you ask for a panel at the end of the wizard? Do you use any login manager (kdm, xdm...)? Do you change your screen resolution or use xinerama?
- Categories in application menu not translated (so you get English "Office" instead of German "Büro" and "Development" instead of "Entwicklung", although everything else is translated)
Yep, I saw that too, didn't have time to investigate, will take a look later.
Weird. Did you remove your old ~/.e folder before launching e17 for the first time? Did you ask for a panel at the end of the wizard? Do you use any login manager (kdm, xdm...)? Do you change your screen resolution or use xinerama?
No change in resolution, no xinerama, using slim. I did tell the wizard to have a panel, and had a new .e/.
I moved my .e/ and went through the wizard again, which stopped the problem. So I went back to the .e/ I was using and the problem still seems to have gone, which is strange because it was consistently happening at every reboot, although could be solved by going to "restart enlightenment" in the menu.
Yep, I saw that too, didn't have time to investigate, will take a look later.
Nothing to do with SlackE17, of course, like the lacking EFM network share support. Has to be resolved upstream, and Rasterman seems to have picked up this.
This was one of the first packages I installed on my new system. For those wondering how to install you can get this from Slackbuilds.org.
This site links back to sourceforge and at the present moment will give you the latest build. There is an order to install the deps:
Code:
The complete build order is: lua, eina, eet, evas, ecore, eio, embryo, edje, efreet, e_dbus, enlightenment.
Easy-peasey! Everything works including screen dimming, sound, battery monitor, cpu meter. I have not checked the internet with the e17 Network Manager 'connman' as I don't want to take the chance of messing up my working net setup. I'm skeptical that it would work as I've found connman didn't work for me in Debian, Gentoo, Snowlinux or Bodhi.
As for performance this is amazing. Uses very low cpu on idle. Startup ram is about 78mb. Debian used only 46mb but I had not installed nearly as many packages in the deb install. Gentoo install used about 56mb. The Slack install seems the most stable. All icons are showing in the menu. And installed Feanza icons. Looks great!
This was one of the first packages I installed on my new system. For those wondering how to install you can get this from Slackbuilds.org.
This site links back to sourceforge and at the present moment will give you the latest build. There is an order to install the deps:
Code:
The complete build order is: lua, eina, eet, evas, ecore, eio, embryo, edje, efreet, e_dbus, enlightenment.
That's not correct, you are missing a lot of thing, most notably elementary which is required for the final E17. If you really want to compile the packages yourself, just use the SlackE17 source tarball. It contains all the required SlackBuilds plus a wrapper script that will compile everything in one time (around 30 minutes on my box). You can pass your extra CFLAGS to the wrapper script (ECFLAGS='-march=native -mtune=native') or even build everything with debug symbols to help debugging (DEBUG=1). That's really more convenient than going to compile the 16+ packages for E17 one by one.
Quote:
Originally Posted by bedtime
Easy-peasey! Everything works including screen dimming, sound, battery monitor, cpu meter. I have not checked the internet with the e17 Network Manager 'connman' as I don't want to take the chance of messing up my working net setup. I'm skeptical that it would work as I've found connman didn't work for me in Debian, Gentoo, Snowlinux or Bodhi.
ConnMann used to work well, but there was too big API changes between 0.7x and 1.0. It's not related at all to the E17 project, it's coming from Intel to compete against NetworkManager. E17 interfaces with it because it is used in embedded devices. In same time, NetworkManager improved enough to be the good candidate. No NetworkManager E17 module on the roadmap, though. But it's working well with the default applet in systray.
I'm going to push a bug fix release of E17 very soon. This will fix some minor problem in E17 and the EFL.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.