Tiny Core Extensions > TCE Talk
[enlightenment] wbar doesn't get populated during boot if desktop=enlightenment for example
jls:
I only tred enlightenment, using the boot code
--- Code: ---desktop=enghlitenment_start
--- End code ---
or something like that, but I feel the problem occours with any other wm
roberts:
jwm OK, icewm OK, hackedbox OK.
the desktop= is really not very useful anymore, unless you have multiple window managers listed onboot, and then wish to specify which one to actually use via the bootcode.
desktop=icewm
BTW, enlightenment errors out for me with
ERROR: UNABLE TO ASSUME ROOT PRIVILIDEGES.
So unable to test it.
althalus:
--- Quote from: roberts on March 25, 2010, 12:58:26 PM ---BTW, enlightenment errors out for me with
ERROR: UNABLE TO ASSUME ROOT PRIVILIDEGES.
So unable to test it.
--- End quote ---
Hmm. I'd noticed those messages too, but since I'd also seen them on a Ubuntu session, and they've never seemed to interfere with e17 being able to run, nor seemed to interfere with it's operation, I'd dismissed them as not being relevant.
If it's actually preventing e17 from starting, then I'll look into finding out the problem there. Is there anything specific in your setup that would force e to stop after those errors?
roberts:
With enlightenment, I get what appears to be a language select screen, except it is totally blank. Nothing to select. The cursor is very blurred. I tried to click on the wbar terminal and nothing worked. I don't know this window manger, so it is likely me. When exiting the window manager, I see the error messages. Reading the .info file did not help.
althalus:
Is the cursor blurry, or does the drop shadow just make it look blurry? E17 has the attitude of "We can be a lightweight desktop environment fast enough for embedded devices, AND be fancier than gnome!", but it does make the default cursor a little hard on the eyes.
On first run, it's usually best to boot with "noicons". There's actually a "Next" button hidden under wbar, and whatever e17 does on that first boot interferes with wbar's behaviour. After you get through the config screen, add /home/tc/.e to your backup and then you can turn wbar back on - I have previously promised to update the info file to include this information, but simply haven't had the time to do it properly yet.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version