The journal was not present because I had not configured journald.conf, now I have it. It was not a freeze after all, but a timeout. It appears to be a bug<http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/487953-timed-out-waiting-device-dev-disk-x2did-ata-after-update-factory.html>
(but strangely the supposed culprit udev 61-msft.rules is not present on my system). Coming to the subject, the brighness problem is still present. Fn keys now working. If can be of any help I attach my .cache/gdm/session.log (systemd error gone). Also I tried to get rid of the consolekit error buy upgrading, without results. Of course all this maybe due to my jepardized system (based on testing but with some packages from unstable and experimental). AFTER ALL, I WAS JUST EAGER TO HAVE THE LAST VERSION OF THE GNOME SHELL! ;-) If you deem so, we may eventually reconsider the issue when everything is in testing. (My /etc/apt/preferences is currently Package: gdm3 gnome-shell* Pin: release a=experimental Pin-Priority: 1100 Package: consolekit libck-connector0 udev libpam-ck-connector *systemd* Pin: release a=unstable Pin-Priority: 1000 Package: * Pin: release a=testing Pin-Priority: 900 Package: * Pin: release a=unstable Pin-Priority: 800 Package: * Pin: release a=experimental Pin-Priority: 100). Best Regars, Carlo. ps: strangely, first I had the full systemd journal at debug level, then I changed journald.conf to default, then I changed it to debug again, but systemd don't want to log with debug level now! 2013/9/12 Carlo Marchiori <carlo.marchi...@gmail.com> > 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, > Carlo. > > > 2013/9/12 Michael Biebl <bi...@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? >> >> >
session.log
Description: Binary data
