From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: e-wm broken after yesterdays upgrade
Date: Sun, 16 Nov 2008 16:22:07 +0100 [thread overview]
Message-ID: <gfpdr0$6vm$1@ger.gmane.org> (raw)
In-Reply-To: <20081116145911.GB14299@dodger.lab.datenfreihafen.org>
On 16-11-08 15:59, Stefan Schmidt wrote:
> Hello.
>
> Sorry for the delay. Having a cold I decided to have a releaxed weekend. Will
> take a deeper look next days if the stuff below does not help.
>
> On Sat, 2008-11-15 at 22:32, Koen Kooi wrote:
>> I just built and installed the updated e-wm and it refuses to start:
>
> Installed means from the updated angstrom feed I guess?
Yes, I did 'bitbake e-wm', synced the new packages to the feeds and did
'opkg update ; opkg upgrade' on the device (an omap3evm board).
On the omap3evm board I'd like to test illume to see if it is fit to
replace mb-wm in angstrom pda images, on the beagleboard I'd like to run
a 'regular' e-wm. The omap3evm was running the 'regular' e-wm at the
time of the upgrade.
> As a sidenote. This was not rushed in without testing or review. I spent some
> good hours on reviewing it together with mickey, in his role as E maintainer in
> OE. We also decided to keep some more patches out until there is more time for
> review.
>
> And I of course tested it before pushing. Building and actually using it. No
> breakage here. But as I only tested with a complete new image and not with
> updating from a feed I may have messed up here. Should not happen though :(
It seems that almost no OE developer is tracking upgrade paths for such
intrusive changes, which is a pity. You'd be suprised how much bugs
there are when you try to build an image from the feeds[1] instead of
from a pristine deploy/. Anyway, mistakes happen :)
> If eina is installed in a matching version I would need the following to track
> this down as I don't have the problem here:
libeina0 - 2:0.0.1+svnr37324-r0.1 -
> - Full x.log
http://dominion.thruhere.net/koen/OE/e17/e-log.txt
It has scary messages about missing vars, but it *does* find the evas
engines. However:
root@omap3evm:~# cat /usr/bin/enlightenment_start.oe
#!/bin/sh
E_PROFILE=""
if [ -r /etc/enlightenment/default_profile ]; then
. /etc/enlightenment/default_profile
fi
renice -10 -p $$
exec enlightenment_start $E_PROFILE
root@omap3evm:~# ls /etc/enlightenment/
sysactions.conf
root@omap3evm:~#
Do I need an extra package to get the default_profile?
> - Full strace
http://dominion.thruhere.net/koen/OE/e17/e-strace.txt
> - Full list of installed packages
http://dominion.thruhere.net/koen/OE/e17/e-installed-packages.txt
Thanks for looking into this, let me know if you need more info.
regards,
Koen
[1] modulo bugs due to not running image_post_process commands
next prev parent reply other threads:[~2008-11-16 15:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-15 21:32 e-wm broken after yesterdays upgrade Koen Kooi
2008-11-16 14:59 ` Stefan Schmidt
2008-11-16 15:13 ` Carsten Haitzler
2008-11-16 15:24 ` Koen Kooi
2008-11-16 21:39 ` Carsten Haitzler
2008-11-17 8:52 ` Koen Kooi
2008-11-16 15:22 ` Koen Kooi [this message]
2008-11-16 22:46 ` Carsten Haitzler
2008-11-17 9:02 ` Koen Kooi
2008-11-17 9:17 ` Carsten Haitzler
2008-11-17 11:40 ` Stefan Schmidt
2008-11-17 12:42 ` Koen Kooi
2008-11-17 13:11 ` Stefan Schmidt
2008-11-17 13:22 ` Koen Kooi
2008-11-17 13:38 ` Stefan Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gfpdr0$6vm$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.