Bug#722515: gnome-shell: Brightness FN keys not working any more

Carlo Marchiori carlo.marchiori at gmail.com
Thu Sep 12 00:26:08 UTC 2013

Freezing with /bin/systemd too.

All usual logs (debug, kern, messages, syslog, in my ignorance I can hardly
tell them apart...)
bear no trace of the failed boot. systemd-journalctl reports an empy log,
and, under /var/logs,
there is no trace of systemd logs.

To be precise, I just put this line
GRUB_CMDLINE_LINUX="init=/bin/systemd acpi_backlight=vendor"
in /etc/default/grub and issued update-grub.

I don't know how to take a screenshot during boot.

Thanks in advance for any help,

2013/9/12 Michael Biebl <biebl at debian.org>

> Am 12.09.2013 01:34, schrieb Carlo Marchiori:
> > There is such an error in the log
> >
> > (gnome-settings-daemon:3566): media-keys-plugin-WARNING **: Failed to
> > connect to systemd: Error calling StartServiceByName for
> > org.freedesktop.login1:
> > GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper
> > exited with unknown return code 1
> > .
> > My attempt to switch to systemd have ended first in a kernel panic,
> > then in a freeze during boot (investigating).
> That sounds like you were not passing the correct parameters on the
> kernel command line and the kernel couldn't find the systemd binary.
> You'll need init=/bin/systemd
> If you can attach a screenshot, that would help
> And yes, GNOME will get a hard dependency on systemd, at least the parts
> which require functionality from systemd.
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20130912/4f14ecea/attachment.html>

More information about the pkg-gnome-maintainers mailing list