<div dir="ltr">Very sorry, fn key NOT working.</div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/13 Carlo Marchiori <span dir="ltr"><<a href="mailto:carlo.marchiori@gmail.com" target="_blank">carlo.marchiori@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>The journal was not present because I had not configured journald.conf, now I have it.</div>It was not a freeze after all, but a timeout. It appears to be a <a href="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" target="_blank">bug</a> <div>
(but strangely the supposed culprit udev <span style="white-space:pre-wrap">61-msft.rules is not present on my system).</span></div><div><span style="white-space:pre-wrap"><br></span></div><div><span style="white-space:pre-wrap">Coming to the subject, the brighness problem is still present. Fn keys now working.</span></div>
<div><span style="white-space:pre-wrap">If can be of any help I attach my </span><span style="white-space:pre-wrap">.cache/gdm/session.log (systemd error gone).</span></div><div><span style="white-space:pre-wrap"><br></span></div>
<div><span style="white-space:pre-wrap">Also I tried to get rid of the consolekit error buy upgrading, without results.</span></div><div><span style="white-space:pre-wrap">Of course all this maybe due to my jepardized system (based on testing</span></div>
<div><span style="white-space:pre-wrap">but with some packages from unstable and experimental). </span></div><div><span style="white-space:pre-wrap">AFTER ALL, I WAS JUST EAGER TO HAVE THE LAST VERSION OF THE GNOME SHELL! ;-)</span></div>
<div><span style="white-space:pre-wrap">If you deem so, </span><span style="white-space:pre-wrap">we may eventually reconsider the issue when everything is in testing.</span></div><div><span style="white-space:pre-wrap"><br>
</span></div><div><span style="white-space:pre-wrap">(My /etc/apt/preferences is currently</span><br></div><div><span style="white-space:pre-wrap"><br></span></div><div><span style="white-space:pre-wrap">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).</span></div><div><span style="white-space:pre-wrap"><br></span></div><div><span style="white-space:pre-wrap">Best Regars,</span></div><div><span style="white-space:pre-wrap">Carlo.</span></div><div><span style="white-space:pre-wrap"><br>
</span></div><div><span style="white-space:pre-wrap">ps: strangely, first I had the full systemd journal at debug level,</span></div><div><span style="white-space:pre-wrap">then I changed journald.conf to default, then I changed it to debug again,</span></div>
<div><span style="white-space:pre-wrap">but systemd don't want to log with debug level now!</span></div>
<div><font color="#000000"><span style="white-space:pre-wrap"><br></span></font><div><font color="#000000"><span style="white-space:pre-wrap"><br></span></font></div><div><font color="#000000"><span style="white-space:pre-wrap"><br>
</span></font><div><div><div><br></div></div></div></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">2013/9/12 Carlo Marchiori <span dir="ltr"><<a href="mailto:carlo.marchiori@gmail.com" target="_blank">carlo.marchiori@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Freezing with /bin/systemd too.<div><br></div><div>All usual logs (debug, kern, messages, syslog, in my ignorance I can hardly tell them apart...)</div>
<div>bear no trace of the failed boot. systemd-journalctl reports an empy log, and, under /var/logs,</div>
<div>there is no trace of systemd logs.</div><div><br></div><div>To be precise, I just put this line </div><div><div>GRUB_CMDLINE_LINUX="init=/bin/systemd acpi_backlight=vendor"</div></div><div>in /etc/default/grub and issued update-grub.</div>
<div><br></div><div>I don't know how to take a screenshot during boot.</div><div><br></div><div>Thanks in advance for any help,</div><div>Carlo.</div></div><div><div><div class="gmail_extra">
<br><br><div class="gmail_quote">2013/9/12 Michael Biebl <span dir="ltr"><<a href="mailto:biebl@debian.org" target="_blank">biebl@debian.org</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Am 12.09.2013 01:34, schrieb Carlo Marchiori:<br>
<div>> There is such an error in the log<br>
><br>
> (gnome-settings-daemon:3566): media-keys-plugin-WARNING **: Failed to<br>
> connect to systemd: Error calling StartServiceByName for<br>
> org.freedesktop.login1:<br>
> GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper<br>
> exited with unknown return code 1<br>
> .<br>
> My attempt to switch to systemd have ended first in a kernel panic,<br>
> then in a freeze during boot (investigating).<br>
<br>
</div>That sounds like you were not passing the correct parameters on the<br>
kernel command line and the kernel couldn't find the systemd binary.<br>
You'll need init=/bin/systemd<br>
<br>
If you can attach a screenshot, that would help<br>
<br>
And yes, GNOME will get a hard dependency on systemd, at least the parts<br>
which require functionality from systemd.<br>
<span><font color="#888888"><br>
--<br>
Why is it that all of the instruments seeking intelligent life in the<br>
universe are pointed away from Earth?<br>
<br>
</font></span></blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>