On Mon, Jun 16, 2014 at 07:57:58PM +0100, Brian wrote: > On Tue 17 Jun 2014 at 06:25:01 +1200, Chris Bannister wrote: > > > On Mon, Jun 16, 2014 at 05:43:18PM +0100, Brian wrote: > > > > > On the other hand, not running X on the console you started it from with > > > startx brings a raft of other problems. > > > > Well, I typed startx in tty4 and it started in tty3, so it isn't running > > in the console I started it from anyway, if I am understanding you. > > If you had upower installed and were running Xfce you would find the > "Suspend" button greyed out. This is because X on tty4 doesn't inherit > the login conditions of tty3. It may not matter to you (it doesn't > matter to me) but that's how systemd works. From the man himself: > > https://lists.fedoraproject.org/pipermail/devel/2014-May/198927.html > > Actually, you get the same thing on Wheezy with sysvinit but without > consolekit. The solution is possibly easier with systemd > > startx -- vt4
One other thing, I sense that the key repeat is not as fast as it was before I installed systemd-sysv. It seems strange that an init system should mess with the keyboard settings. Has anyone else noticed this or is it just me? JFTR. I've already had to do a dpkg-reconfigure console-setup to fix the console font, and even then a reboot was required. I tested with 'init=/bin/systemd' first just to check, it started out strange then came right. It was when I went the whole hog and installed systemd-sysv that it needed a kick in the pants. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140618023137.GC10733@tal