On Wed, May 05, 2010 at 12:57:41PM +0200, n...@el-hennig.de wrote:
> > > For me it does not automatically, but as workaraound you can start
> > "shr_elm_softkey" from the terminal and then it works fine.
>
> I found an even better way to workaraounf this problem automatically:
>
> I created a wrapper /usr/bin/shr_elm_softkey.sh that is called from
> /etc/X11/Xsession.d/89shr_elm_softkey and that waits some time until it
> starts shr_elm_softkey
>
> The wrapper loks like this:
> ---8<-
> #!/bin/sh
> export DISPLAY=localhost:0
> sleep 60
>
> exec /usr/bin/shr_elm_softkey
> ---8<-
>
> The Xsession-Skript is the following:
> ---8<-
> #!/bin/sh -e
> DISPLAY=:0.0 /usr/bin/shr_elm_softkey.sh &
> ---8<-
There is strace for not working
http://build.shr-project.org/tests/jama/shr_elm.log.no
and working start
http://build.shr-project.org/tests/jama/shr_elm.log.yes
As TAsn confirmed shr_elm_softkey needs illume module to be loaded
before it's started.
Your workaround works, but be aware that in that 60s you have to finish
first run wizard (after reflash or .e removal). TAsn is checking
possibilities for shr_elm_softkey autostarted by e17 itself.
The best approach (imo), would be to make an app.desktop file, put it in
/usr/share/applications (or standard place for your platform). Then in
/etc/skel make a ./e/e/applications/startup/.order file with app.desktop
listed in it. Then when new users get created, the
~/.e/e/applications/startup/.order file gets copied into users home dir
and the QP app will get started every time they start E.
Shorter version of same workaround (not pushed because 20s is as bad as
60s for first start).
sed -i 's#^DISPLAY=:0.0 /usr/bin/shr_elm_softkey#sh -c "sleep 20 \&\&
/usr/bin/shr_elm_softkey"#g' /etc/X11/Xsession.d/89shr_elm_softkey
DISPLAY is also already set by /etc/profile..
--
uin:136542059jid:martin.ja...@gmail.com
Jansa Martin sip:jama...@voip.wengo.fr
JaMa
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
