Listmates,
Hello, first post. I found enlightenment (both e16 & 17) about a week
ago
when I needed a new WM to troubleshoot a problem with the kde-greeter causing
X to crash with and Intel gpu on one of my boxes. I'm glad the box broke! Both
e16 & e17 rock! (I have e16 on my suse 11.0 box because the e17 build they
have isn't quite where it needs to be on x86_64) I have e17 on the second
drive that has Archlinux on it, and e17 runs fine.
Tonights quandaries are (1) how do I add a separator to the e16 menus;
and
(2) I have a nasty little hang that has developed switching themes on e16
(user created problem no doubt)
First, I've googled, but haven't found a clean way to put a separator
in the
e16 menu (e.g. user_apps.menu). Guessing I tried 'separator', but no go. So I
have, where needed, just put a text separator there:
"--------------------------" NULL exec "mystub"
where mystub is just a shell script of 'echo "" &>/dev/null' Is there a
keyword that will actually produce a separator that is a thin line that
doesn't take up a whole line of text?
Second problem is the hang on theme change. I don't know what is going
on
here. I had used e16 for several days and changing themes worked fine. A quick
flash of the screen (you could see the framebuffer of kdm during the change)
and then the new theme appeared just like it should. Now however, something
has changed and when I go to change themes, I navigate to choose the theme I
want with: rt-click (menu) -> Themes (they all appear), and as soon as I click
on a theme to kickoff the change process -- WHAM, my screen freezes (mouse
moves, but all epplets/apps are frozen).
Another peculiar symptom is the pager. When the screen is frozen, if I
move
my mouse inside the pager (cursor changes to an X), the pager captures it and
will not let it out of the pager dialog borders. I can still move it around
within the borders, but there is no escape from the "pager jail".
ctrl+alt+F1 drops me to console, and I then have to kill Xorg manually
to get
things running again. Basically I have to kill off:
\_ /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth
/var/lib/xdm/authdir/authfiles/A:0-aR2yAp
\_ /usr/bin/Xorg -br -nolisten tcp :0 vt7 -auth
/var/lib/xdm/authdir/authfiles/A:0-aR2yAp
\_ -:0
\_ e16
\_ /usr/bin/gpg-agent --sh --daemon --write-env-file
/home/david/.gnupg/agent.info /usr/bin/s
<snip>
and then I can restart xdm. The normal xdm shutdown causes e16 to
shutdown
leaving only the two Xorg instances that have to be manually killed with 'kill
-9' I'm not sure what is going on there, but it appears that I have two
instances of Xorg running (I don't know, that may be normal) but I cannot
figure out what is causing the hang. Can anybody suggest what I can check to
find the answer? Anybody had this happen to them?
I've posted the hang to the openSuSE list as well, but if you guys know
of
something to check or a work-around, then I would appreciate any help you can
give. Thanks.
--
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
enlightenment-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-users