Memory low on first run
Bug #422841 reported by
Bert Freudenberg
on 2009-09-01
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Sugar on a Stick |
Low
|
Sugar on a Stick Developers | ||
Bug Description
I used soas3-20090830.vmdk in VirtualBox with 256 MB RAM. After all the installation stuff finished and I was in Sugar, I launched Etoys. It popped up two error notifiers. Its log file said
Failed to fork() to call /bin/dbus-launch: Cannot allocate memory
After shutting down and rebooting the VM, it worked fine.
| Sebastian Dziallas (sdziallas) wrote : | #1 |
| Sebastian Dziallas (sdziallas) wrote : | #2 |
Or because of the activities that got originally installed at firstboot... actually, this is fixed now, but we've some issues with appliance creation, which need to be fixed.
| Changed in soas: | |
| status: | New → In Progress |
| importance: | Undecided → Low |
| assignee: | nobody → Sebastian Dziallas (sdziallas) |
Sebastian Dziallas (sdziallas)
on 2009-10-12
| Changed in soas: | |
| assignee: | Sebastian Dziallas (sdziallas) → Sugar on a Stick Developers (soas-dev) |
To post a comment you must log in.
Oh, this is interesting. I haven't seen this before. Maybe 256 MB is too few for the first boot?