Peter Robinson wrote:
On Fri, Apr 16, 2010 at 4:12 PM, Thomas C Gilliard
<satel...@bendbroadband.com> wrote:
Peter Robinson wrote:
Hi Thomas,
On Fri, Apr 16, 2010 at 3:59 PM, Thomas C Gilliard
<satel...@bendbroadband.com> wrote:
This was from log application on working soas 414
I do not know which of these are needed to fix problem.
This is what I did:
Could you reply in line (as in at the bottom of the mail) as it makes
the conversation much easier to follow.
That aside you still don't tell me what was broken in the first place
that this fixes. If it was the fix for Sugar not starting the only
thing that needs to be fixed is the new sugar-artwork build. Can you
confirm that is what you were trying to fix?
Peter
Peter;
I do not know what extra files are needed.
The sugar-artwork fix did not get me to the sugar name screen it stopped at
a blue screen.
I will repeat this test with a new USB if you like..
Only after the init 3 boot login/liveuser/su -
yum install gdm* hal* install and reboot did it work
Thanks for the clarification. I will be looking at the latest live cd
over the weekend. This week has been a little manic but looking at the
list of packages that were installed above there is nothing there that
should have had any impact on the booting at all. Most of them are
either development packages or finger print or smart card related
stuff.
Peer
I got the idea from discussion with alsroot on IRC with USR-414 (Ubuntu
)having similar starting problems:
<alsroot> satellit__: I downloaded USR414 and there are bunch of issues
> <alsroot> not python-xklavier, even in packages
> <alsroot> hal is not installed
> <alsroot> sugar packages are pretty outdated - 0.87.1
> <alsroot> satellit__: to make clear test, sugar should be at least 0.88.0
> <satellit__> thanks for your help
Thought I would try "scattergun approach" thus
gdm* and hal*
and it worked...???
Tom Gilliard
_______________________________________________
SoaS mailing list
SoaS@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas
