Fail to autostart in Ubuntu Jaunty

Bug #372114 reported by Andrey Sitnik
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
origami
Invalid
High
Christer Edwards

Bug Description

I install origami 0.6.9 on Ubuntu 9.04, but after reset origami didn’t start.

~$ origami status
#########################################
current status of origami on sputnik5
#########################################
Status of FAH client(s): FAILURE

~$ ls /etc/rc*/*origami
/etc/rc0.d/K20origami /etc/rc3.d/S20origami /etc/rc6.d/K20origami
/etc/rc1.d/K20origami /etc/rc4.d/S20origami
/etc/rc2.d/S20origami /etc/rc5.d/S20origami

When I start origami manually by “sudo origami start” or “sudo /etc/init.d/origami start;, it work fine.
I also has encrypted home dir if it’s matter.
I try to search “FAH” or “origami” in logs, but didn’t find anything? What logs I can get to you?

Tags: autostart
Andrey Sitnik (iskin)
description: updated
description: updated
summary: - fail to autostart in Ubuntu Jaunty
+ Fail to autostart in Ubuntu Jaunty
Revision history for this message
Nico Zanferrari (nicozanf) wrote :

I also have the same problem, on Jaunty 64 bit (without encrypted home dir).

Revision history for this message
Nico Zanferrari (nicozanf) wrote :

Logs dir is under /var/lib/origami/foldingathome.

I can see that on autostart it stops at the following lines:

[08:14:40] Preparing to commence simulation
[08:14:40] - Ensuring status. Please wait.

While if it's manually launched they become:

[06:39:35] Preparing to commence simulation
[06:39:35] - Looking at optimizations...
[06:39:35] - Files status OK

and so on. ...

Revision history for this message
Andrey Sitnik (iskin) wrote :

My logs in /var/lib/origami/foldingathome/CPU*/FAHlog.txt with fail autostart and next manual start.

Fail autostart end with:

[16:40:55] Assembly optimizations on if available.
[16:40:55] Entering M.D.

Changed in origami:
assignee: nobody → Christer Edwards (christer.edwards)
importance: Undecided → Critical
status: New → Confirmed
Revision history for this message
Nico Zanferrari (nicozanf) wrote :

Good news.

I've found by accident that it works correctly if you disable the splash option on /boot/grub/menu.lst ! But don't ask me why ...

Revision history for this message
Christer Edwards (christer.edwards) wrote : Re: [Bug 372114] Re: Fail to autostart in Ubuntu Jaunty

While not a proper fix it does put us on the right track as to what
might be causing the problem. I'll continue to look into this.

Thank you

On Thu, Jun 18, 2009 at 1:01 AM, Nico Zanferrari<email address hidden> wrote:
> Good news.
>
> I've found by accident that it works correctly if you disable the splash
> option on /boot/grub/menu.lst ! But don't ask me why ...
>
> --
> Fail to autostart in Ubuntu Jaunty
> https://bugs.launchpad.net/bugs/372114
> You received this bug notification because you are a bug assignee.
>

Revision history for this message
Eros Zanchetta (eros) wrote :

Same here on 2 different computers running Ubuntu 9.04: I have to manually start it every time.

I tried changing the start order using:

update-rc.d origami defaults 95

but it didn't help.

I tried disabling the splash option on /boot/grub/menu.lst as suggested by Nico above and now it autostarts correctly.

Interestingly enough, mediatomb (which previously refused to autostart too) now autostarts as expected. Maybe it's not an origami issue after all?

Revision history for this message
robinl (robin4home) wrote :

Any updates? This bug defeats one of the main points of having origami in the first place.

Revision history for this message
Christer Edwards (christer.edwards) wrote :

It has been confirmed that this is not a bug in origami but actually in usplash. If you disable usplash origami will start just fine at boot.

There is nothing for me to "fix", and the hope is that the 9.10 will resolve the issue.

Changed in origami:
importance: Critical → High
status: Confirmed → Invalid
Revision history for this message
Nico Zanferrari (nicozanf) wrote :

I'm happy to report that in my case the bug has disappeared with the upgrade to 9.10 (Karmic) ;-))

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.