Re: live-config 104-gnome-screensaver gconf > dconf
Hi all!
Maybe this is an old topic, but I've just hit this problem too.
In my case, I'm using wheezy's live-config (3.0~a43-1). Since the old
gconf thing do not work as expected I moved to gsettings and I'm
getting these errors during boot time.
"""
** (process:584): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
** (process:584): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
** (process:589): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
** (process:589): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
** (process:594): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
** (process:594): WARNING **: Command line `dbus-launch
--autolaunch=6428063aa6c0cd1aade8ff6b50c880f8 --binary-syntax
--close-stderr' exited with non-zero exit status 1: Autolaunch error:
X11 initialization failed.\n
"""
Yes, it's true, there are just warnings, but it doesn't work. And
IMVVHO, having this behaviour in a Live session isn't good at all.
Is this issue solved? If not, should I move the hook to be executed
during other stage? Should I use the workaround that Philip provided?
Any hint will be appreciate.
Best regards,
Javi.
Reply to: