Bug#806256: libpam-systemd: log out from a TTY and your X input devices get lost!

On Sun 29 Nov 2015 at 01:05:44 +0100, Michael Biebl wrote: > Am 28.11.2015 um 19:23 schrieb Francesco Poli: > > > Please tell me whether you need any further information in order to > > investigate. Otherwise, please drop the moreinfo tag. > > So far I don't know yet, how I can reproduce the

[no subject]

___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Re: Bug796588#: adjtimex: Has init script in runlevel S but no matching service file

Dear Felipe and Andreas, Your detailed feedback is really helpful. I really appreciate your kindness help! Enclosed my updated adjtimex.service file. Here's the explanation why I changed a bit. >> [Unit] >> Description=adjtimex service in early boot > I think the description of the init script

Re: Bug796588#: adjtimex: Has init script in runlevel S but no matching service file

On 29 November 2015 at 11:04, Roger Shimizu wrote: > Dear Felipe and Andreas, > > Your detailed feedback is really helpful. > I really appreciate your kindness help! > > Enclosed my updated adjtimex.service file. > Here's the explanation why I changed a bit. > >>> [Unit]

Bug#788050: systemd-fsck : Check disks at each reboot

On 29-11-15 01:28, Michael Biebl wrote: Am 29.11.2015 um 00:12 schrieb Manuel Bilderbeek: How can I help? Describe your setup in as much detail as possible. LVM, RAID, fstab etc. No RAID, no LVM. I've got a HDD and an SSD. I'm now booting from the SSD. $ cat /etc/fstab # /etc/fstab: static

Bug#798242: systemd: Failed to execute operation: Connection timed out

Martin Pitt wrote: > This sounds like another case of > https://github.com/systemd/systemd/issues/1505, which finally got > fixed in version 228. Thanks, very interesting. Yes, it sounds likely. > ... > > I don't close this for now, it would be interesting to see whether > this still happens

Bug#806291: systemd: systemctl status ignores -n argument

On Sat, Nov 28, 2015 at 11:37:55AM +0100, Eduard Bloch wrote: > Hallo, > * Michael Biebl [Thu, Nov 26 2015, 04:32:43PM]: > > Am 26.11.2015 um 15:59 schrieb Michael Biebl: > > > Works here. But I actually need a service which produces more then 10 > > > lines of output when started. > > > > To

Bug#798242: systemd: Failed to execute operation: Connection timed out

Martin Pitt wrote: > James Cameron wrote: > > The problem system is still in the state it was left in when > > #798242 was raised. We've been unable to take the risk of a > > reboot; yet. Can you speculate if reboot would be bad idea? > > No, a reboot is probably the only thing which will reset

Bug#798242: systemd: Failed to execute operation: Connection timed out

Hello James, James Cameron [2015-11-30 10:40 +1100]: > Is 228 planned for jessie, or should we temporarily repoint sources to > stretch and try an update of systemd only? Jessie has and will keep 215, we will only backport individual fixes for it. I would strongly advise against a partial