#72 cdemu-daemon-session.sh exited with status 255

[Le Gluon du Net]

Hello,

I installed cdemu on Ubuntu 13.10 with PPA and for several weeks now it doesn't start anymore. At session start, I obtain this error message:

Daemon autostart failed. Error:
Erreur lors de l'appel de StartServiceByName pour net.sf.cdemu.CDEmuDaemon : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/cdemu-daemon-session.sh exited with status 255

Thank you for your help.

LGDN.

[Rok Mandeljc]

When the daemon is started via /usr/libexec/cdemu-daemon-session.sh, it is configured to produce a log file called .cdemu-daemon.log in your home folder (i.e., ~/.cdemu-daemon.log). Can you check if it exists and what its contents are? (alternatively, try running /usr/libexec/cdemu-daemon-session.sh from terminal to see what the daemon's output is)

[Le Gluon du Net]

I uninstalled all cdemu applications:

apt-get remove --purge cdemu-daemon libao-common libao4 libmirage9 vhba-dkms

then reinstalled it:

apt-get install gcdemu

and it works again if "Use system bus" unchecked.

Perrhaps a bug after upgrade Ubuntu raring to saucy...Anyway it works now.

[Rok Mandeljc]

Yes, the PPA packages will not work with system bus (see the comment at bug report #73), so you should leave "Use system bus" unchecked.

Good to hear you got it to work. Maybe there was indeed an issue with upgrade; perhaps the vhba module was not rebuilt or the permission on the control device got reset...

[Le Gluon du Net]

Hello,

me again for the same trouble: after last ubuntu kernel update 3.11.0-14, gcdemu start with error message:

Daemon autostart failed. Error:
Erreur lors de l'appel de StartServiceByName pour net.sf.cdemu.CDEmuDaemon : GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/libexec/cdemu-daemon-session.sh exited with status 255

Gcdemu is all grey --> cdemu feature is disabled.

Restart Linux (remember me time I used Windows lol), no change.
I uninstalled gcdemu and all cdemu packages, restart, reinstall gcdemu, launch gcdemu ,it works!

It is possible there is a problem with dkms when new cdemu module is made for new kernel?

[Rok Mandeljc]

Hmm, it does look like there might be some issues with dkms. Unfortunately, I cannot reproduce the issue in a VM, so the issue might be specific to your configuration.

Next time you hit the issue (either when next kernel update comes along, or if you downgrade and re-upgrade the kernel), can you please check:
a) if vhba module is properly built (i.e., check the output of 'modinfo vhba' after booting new kernel)
b) after daemon autostart fails, what is the output in daemon's log file; by default, the log file should be called .cdemu-daemon.log and located in your home folder, so you can check if for example using 'cat ~/.cdemu-daemon.log'