Activity log for bug #881885

Date Who What changed Old value New value Message
2011-10-26 09:35:39 James Hunt bug added bug
2011-10-26 09:35:46 James Hunt upstart: assignee James Hunt (jamesodhunt)
2011-10-26 09:36:05 James Hunt description init-checkconf(8) fails if the user is logged in on a console only due to the recent DBUS behavioural change outlined in bug 812940. Error is: ERROR: failed to ask Upstart to check conf file The solution is for init-checkconf to: 1) Check to see if a dbus-daemon exists for the user invoking the script. 2) If not, have it run: eval `dbus-launch --auto-syntax` and ensure the daemon starts. Note that the script should also kill the dbus-daemon but *ONLY* if it was not running when the script first started. init-checkconf(8) fails if the user is logged in on a console only (no X session) due to the recent DBUS behavioural change outlined in bug 812940. Error is: ERROR: failed to ask Upstart to check conf file The solution is for init-checkconf to: 1) Check to see if a dbus-daemon exists for the user invoking the script. 2) If not, have it run: eval `dbus-launch --auto-syntax` and ensure the daemon starts. Note that the script should also kill the dbus-daemon but *ONLY* if it was not running when the script first started.
2011-10-26 09:36:16 James Hunt description init-checkconf(8) fails if the user is logged in on a console only (no X session) due to the recent DBUS behavioural change outlined in bug 812940. Error is: ERROR: failed to ask Upstart to check conf file The solution is for init-checkconf to: 1) Check to see if a dbus-daemon exists for the user invoking the script. 2) If not, have it run: eval `dbus-launch --auto-syntax` and ensure the daemon starts. Note that the script should also kill the dbus-daemon but *ONLY* if it was not running when the script first started. init-checkconf(8) fails if the user is logged in on a console only (no X session) due to the recent D-Bus behavioural change outlined in bug 812940. Error is: ERROR: failed to ask Upstart to check conf file The solution is for init-checkconf to: 1) Check to see if a dbus-daemon exists for the user invoking the script. 2) If not, have it run: eval `dbus-launch --auto-syntax` and ensure the daemon starts. Note that the script should also kill the dbus-daemon but *ONLY* if it was not running when the script first started.
2011-10-26 15:30:30 Mark Russell bug added subscriber Mark Russell
2012-02-03 00:14:19 Aaron C. de Bruyn bug added subscriber Aaron C. de Bruyn
2012-08-13 12:43:24 Peter Matulis bug added subscriber Peter Matulis
2013-01-09 15:47:52 James Hunt upstart: status New In Progress
2013-08-13 19:12:12 Dan Lipsitt bug added subscriber Dan Lipsitt
2014-07-28 09:59:19 Dimitri John Ledkov upstart: status In Progress Fix Released