Tiny Core Linux
Tiny Core Extensions => TCE News => TCE 2.x => Topic started by: Jason W on March 06, 2010, 05:11:00 PM
-
Thanks to Althalus for:
Title: enlightenment.tcz
Description: The Enlightenment DR17 Desktop Environment
Version: 16.999.063
Author: See http://enlightenment.org/p.php?p=contact&l=en
Original-site: enlightenment.org
Copying-policy: GPL
Size: 10.1MB
Extension_by: Althalus
Comments: No attempt at configuration for TC has been made.
It's up to the user to make it work the way you want.
Change-log: -
Current: First release 2010-03-06
-
It doesn't work for me. I try 2 times, and appbrowser says checksum error. (tinycore 2.9)
-
It doesn't work for me. I try 2 times, and appbrowser says checksum error. (tinycore 2.9)
the same for me
-
Fixed. It is an issue of there either being a new line in the md5.txt file or there not being two spaces between hash and filename, and it is happening with many extensions from several submitters. I thought I caught them all, but this one slipped through. What I think is happening is Gmail is messing up files when they are sent as raw files. The easiest way to save me a lot of time and to help prevent bad md5's from slipping through is to make a tarball of the extension files and bcrypt them. No matter how vigilant I am in running checks something here and there seems to make it's way through. Using bcrypt will eliminate the md5 issue.
-
There is missing dependency - expat2.tcz When I install it it works, but it freeze in "language choose window". I don't know why. Enlightenment is too complex enviroment for me.
-
dbus depends on expat, and since dbus was in the enlightenment dep file I went ahead and added expat as a dependency.
-
When I install it it works, but it freeze in "language choose window".
I was wrong. It didn't freeze. It's because "language choose window" doesn't show even one language to choose. And I didn't noticed "Next:" button, because it was hidden by wbar. Sorry for fake alarm.
-
The startup-file (i.e. '/usr/local/tce.installed/enlightenment') uses "#!/bin/bash" as shebang. I guess that should better be "#!/bin/sh"
-
Yeah, shebang for startup scripts should always be #!/bin/sh even if it is an extension that expects bash to be installed as a dependency.
-
The startup-file (i.e. '/usr/local/tce.installed/enlightenment') uses "#!/bin/bash" as shebang. I guess that should better be "#!/bin/sh"
My apologies, old habits =/
When I get home tonight, I'll fix and email through a new copy (Unless Jason is willing to fix it for me before I resubmit?)
@Neonix Regarding different languages: As english is my primary language, I've not even considered testing changing the language to something different - I'll look into that when i get home.
-
Yeah, my task list is short tonight and I can fix the shebang as it will only take a minute.
-
There seem to be some other problems with the 'enlightenment.tcz' extension: After working around the shebang problem (e.g. sudo sh /usr/local/tce.installed/enlightenment) the following 'startx' just ends up with a changed background, the string 'Language' written over the top center of the screen, and an empty large white box (with 'Select one' written in it's header, but nothing else). BTW, wbar seem to have been started (it's showing at the bottom) but is not "active".
There is nothing to select, mouse clicks don't achieve anything, no keystrokes seem to be accepted. So my only way out is to kill the X server (with Ctrl-Alt-Backspace). Amongst some other (probably benign) status messages the following error messages are filling the screen:
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_000.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_010.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_020.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_030.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_070.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_080.la: invalid ELF header
/tmp/tcloop/enlightenment/usr/local/lib/enlightenment/modules/wizard/linux-gnu-i686-ver-svn-05/page_200.la: invalid ELF header
My test system: TC 2.9 running under QEMU 0.11.1.
-
I will hold off the shebang fix since there seems to be other issues that also need to be tackled.
-
@maro: Make sure wbar isn't going to launch when you start X (Either remove the line from your .xsession or use the boot code). Wbar stops you being able to complete the wizard.
With a fresh install of TC in VBox, I am unable to replicate the ELF header error. Only installed TCZ's are enlightenment and it's deps. A quick google search suggests corrupted files or a different kernel than what the system was compiled on.
* Do you use the stock standard TC kernel?
* I've seen TC do strange things running under Qemu before. Do you have a non-Qemu environment you could test in?
@Jason: If you end up doing the shebang fix tonight, could you also amend the info file to include something along the lines of "Alsa is an optional dependency for the sound mixer. If you don't use alsa, just unload the mixer module when prompted" ?
-
I will go ahead and fix the shebang, but best to send an updated info file.
-
Shebang fixed.
-
Well, I managed to get past the "large white box" issue, but the error messages are occurring the same way whether I use QEMU (0.11.1) or VBox (3.1.4).
The problem with the "large white box" can be worked around by disabling wbar (in .xsession). Only then will a button labeled 'Next' become visible. This button allows the user to move to the next setup step after the (meaningless) language selection (which I assume is what that "large white box" represents).
At the bear minimum a warning needs to be included in the .info file to guide the user trough these pitfalls. A better long-term idea might be to add a flag to '/etc/sysconfig' that would control whether wbar should be executed during 'startx' or not. This would obviously require a change to Core. After this change appropriate settings could be added to the startup scripts of the window managers that require such.
Since I'm booting the VM only with the original TC 2.9 image it is as "plain" a system as possible. If one would run 'startx' with output redirection the error messages will show up in that log.
I believe there is still some work to be done to iron out the kinks.
-
Yes, I do see the ELF headers now. My apologies, I was only looking at error output before.
At this point as far as I am concerned, the only issues to be worked through are the inability to change languages, and the ELF header errors (Which may be related, as the header errors are files within the setup wizard).
Any other errors that show up in the output are a direct result of the e17 libraries, code, and modules themselves.
You are right though in that the info file should include a message to the effect of "You will need to use the noicons boot flag to use enlightenment", along with the optional alsa I mentioned earlier. I will look into the problems with the wizard, and provide an updated info file later tonight.
EDIT: Thanks Jason
-
Hi,
I just posted a reply from one of E's core developers, regarding a cooperation between both projects:
http://forum.tinycorelinux.net/index.php?topic=5209.0 (http://forum.tinycorelinux.net/index.php?topic=5209.0)
Basically, please feel to contact barbieri regarding any problems you may encounter. ;)
Thank you very much for all your hard work.
-
Actually, all through the process of building I've been working with various devs on IRC. Very friendly and helpful crowd. xD
Am building the latest svn, will see ifthat resolves issues w/ lang + efl headers
-
packages built, will submit them tonight after some more thorough testing later.
WRT the invalid ELF headers: Got the same errors using prebuilt packages and built from SVN on ubuntu, so I believe they are a problem within the Wizard module itself.