Origami doesn't start automatically on startup in Jaunty

[Ian Ellis]

Most of it's in the summary. Interestingly, Origami will start if I type in the command:
        ~$ sudo /etc/init.d/origami start
I don't know enough about run levels to go digging further at the moment, so that's basically all the information I have. Oh, and this is on 64 bit. I'm not sure if that's important.

Package info:
  Installed: 0.6.9-0ubuntu1
  Candidate: 0.6.9-0ubuntu1
  Version Table:
 *** 0.6.9-0ubuntu1 0
        500 http://us.archive.ubuntu.com jaunty/universe Packages
        100 /var/lib/dpkg/status

[Christer Edwards (christer.edwards)]

installing on a 9.04 jaunty virtual machine. will report my results.

[Christer Edwards (christer.edwards)]

You can try two things to see if you have better success.

sudo update-rc.d origami defaults

sudo /var/lib/origami/foldingathome/installService

It sounds like, for whatever reason, the symbolic links weren't setup properly between the /etc/init.d/origami and the runlevels. Either of the above commands should populate those.

Please let me know if this problem persists.

[Ian Ellis (ianmailstuff)]

Well, I didn't do anything and it's working now. Whatever was causing it to not start must have been fixed in the last load of patches I installed. So, I suppose this bug is no longer valid. I'll let you know if it pops up again for some reason.

[Ian Ellis (ianmailstuff)]

Well, it turns out that the bug didn't go away, but I have more details. The culprit is the splashscreen! That seems a little odd to me, so I'll tell you what led me to that conclusion.

What happened was the time it worked I saw the messages at boot because the system was doing something extra (updating some kernel modules). So, I rebooted the computer a few times and hit ctrl+alt+F1 as soon as the spalshscreen popped up. Each time, I saw all the boot messages, and Origami's "Starting up FAH client(s)" was consistently among them. After I was in Gnome each time, I checked, and FAH was running. After that, I rebooted the computer without hitting ctrl+alt+F1, and FAH was consistently NOT running once I got into Gnome.

Perhaps this isn't a bug in Origami after all.

[Christer Edwards (christer.edwards)]

@Ian - if this is still a problem can you drop into IRC (#ubuntu-folding) and we'll see about figuring this out.

[Arceliar (littlebuzz71)]

I can confirm the problem here. Upgraded from intrepid to jaunty (on amd64) and folding stopped autostarting.

I had origami remove the FaH install, i removed the symlinks from init, and purged origami. Reinstalled it, same problem.

I don't want to do a full reinstall just to get this working (if that would even fix it) so I'm just going to disable usplash as a temporary workaround (switching to the console for boot up does indeed appear to work).

[Ian Ellis (ianmailstuff)]

I just re-installed Jaunty with the final release, and it's still not running on startup, on both my desktop and laptop. It did occur to me that this problem could just be on amd64. I hope to have time to work on this via IRC tomorrow.

[Koen (koen-beek)]

I can confirm this problem also on a fresh install of Jaunty amd64

[Koen (koen-beek)]

I tried to debug the problem but I have given up for the moment.
The startup script gets called correctly and goes through the code in /etc/init.d/origami to start the faH processes (2 in my case) and the test that it uses to check whether they were started says that they were, but when I check the processes when I'm logged in in a terminal after boot they're not there (anymore ?) ...

I'm using the following workaround for the moment

I've added an Application in System->Preferences->Startup Applications with command "sudo origami start"

to avoid the problem of the system needing a password for the origami script when doing sudo I've added it to the exception clauses using visudo
  sudo visudo
and add
<your_username> ALL= NOPASSWD: /path/to/program
at the end of the file (with <your_username> replace with your login id)

[Christer Edwards (christer.edwards)]

For those running on amd64, please verify that you have ia32-libs package installed. Please comment with any status changes with that installed.

[CharlieAshford (chezzo)]

i also have this problem, but i'm on a 32 bit intel system

[Ian Ellis (ianmailstuff)]

Well, I finally decided to get back to working on this bug, but by that time Karmic was in alpha six or so. I tested it in Karmic, and it worked fine, but I decided to wait until the final release to post this comment. It seems like this bug is a side-effect of how the splash screen affected the startup of processes in Jaunty. My guess is that Jaunty cuts off the startup script because it writes more text to the screen than most and also does the whole thing of waiting for FAH to start. Anyway, since Jaunty isn't a LTS release and Origami works fine with all the other Ubuntu releases since Hardy, I personally don't see the point in trying to fix this anymore.

[Christer Edwards (christer.edwards)]

closing ticket based on latest feedback regarding jaunty vs karmic boot services.