Comment 5 for bug 480704

Revision history for this message
totty (tsadowski-gmx) wrote : Re: xfburn still relies on HAL

Ok.

totty@Kapitaen:~$ LANG=C apt-cache policy hal
hal:
  Installed: 0.5.13-1ubuntu8
  Candidate: 0.5.13-1ubuntu8
  Version table:
 *** 0.5.13-1ubuntu8 0
        500 http://de.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

totty@Kapitaen:~$ LANG=C status hal
Command 'status' is available in '/sbin/status'
The command could not be located because '/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
status: command not found

totty@Kapitaen:~$ sudo LANG=C status hal
[sudo] password for totty:
hal stop/waiting

So hal is not runnig. If I start hal, then xfburn starts, too.

totty@Kapitaen:~$ sudo /etc/init.d/hal restart
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service hal restart

Since the script you are attempting to invoke has been converted to an
Upstart job, you may also use the restart(8) utility, e.g. restart hal
hal start/running, process 16008
totty@Kapitaen:~$ sudo LANG=C status hal
hal start/running, process 16008
totty@Kapitaen:~$ xfburn
** Message: Using Thunar-VFS 1.0.1
** Message: Using HAL
** Message: Using gstreamer transcoder.

Cheers
Torsten