On Tue, 1 Dec 2015 11:23:45 -0300 Felipe Sateler wrote:
[...]
> Upstream claims the problem is either X or the graphics driver:
>
> https://github.com/systemd/systemd/issues/2061
>
> (Not exactly the same reproducer, but similar).
Hello Felipe,
thanks for your comment.
However, the upstream bu
Hi,
On 29-11-15 01:28, Michael Biebl wrote:
Does the problem go away if you use "systemctl mask
systemd-fsckd.service systemd-fsckd.socket"
Yes, it does. Using this I got to see the following while booting, which
wasn't visible before:
A start job is running... for sda1 (1min23 / no limit)
Hi,
On 29-11-15 01:28, Michael Biebl wrote:
Can you boot with systemd.debug-shell on the kernel command line, and
then switch to tty9 while the fsck is running and attach strace to the
fsckd and fsck process?
I want to try this, but for some reason, grub always boots, even if I
keep SHIFT pre
Package: systemd
Version: 228-2
Severity: wishlist
Double messages upon disable:
# systemctl disable mysql
Synchronizing state of mysql.service with SysV init with
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable mysql
insserv: warning: current start runle
Control: forwarded -1 https://github.com/systemd/systemd/issues/2079
On Tue, 2015-12-01 at 15:02 +0100, Michael Biebl wrote:
> > ForwardToConsole=yes
> > TTYPath=/dev/ttySx
I just gave that a try and it seems not to be what I want... as it
forwards *everything* on the journal to the serial consol
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/2079
Bug #806793 {Done: Michael Biebl } [systemd] systemd: can one
have systemd output on both, serial console and tty0?
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/2079'.
--
80
On 1 December 2015 at 10:49, Brian Potkin wrote:
> On Mon 30 Nov 2015 at 23:04:37 +0100, Francesco Poli wrote:
>
>> I am more and more suspecting that this issue is ultimately caused by
>> systemd-logind / libpam-systemd...
>
> I have installed Jessie without any tasks. The minimum for a working X
Dear Felipe,
Considering now we have consensus on the service file except the
description part, which is quite minor, I made a release build of
adjtimex package and uploaded to mentors.
I also created a RFS: https://bugs.debian.org/806797
Since you helped me greatly on the service file, which is
Your message dated Tue, 1 Dec 2015 14:54:13 +0100
with message-id <565da685.40...@debian.org>
and subject line Re: Bug#806793: systemd: can one have systemd output on both,
serial console and tty0?
has caused the Debian Bug report #806793,
regarding systemd: can one have systemd output on both, se
On Mon 30 Nov 2015 at 23:04:37 +0100, Francesco Poli wrote:
> I am more and more suspecting that this issue is ultimately caused by
> systemd-logind / libpam-systemd...
I have installed Jessie without any tasks. The minimum for a working X
on this machine is xserver-xorg-video-nouveau. xserver-xo
Package: systemd
Version: 228-2
Severity: wishlist
Hey.
Not sure whether this is a wishlisht, bug or whether I just oversee anything ;-)
When configuring the kernel for serial console ouput, i.e. sth. like
console=ttySx,115200n8 ...
I'd actually like to have output on both, serial consol and VG
On 1 December 2015 at 10:05, Felipe Sateler wrote:
> Control: tags -1 confirmed
>
> On 1 December 2015 at 08:32, Ansgar Burchardt wrote:
>> Package: systemd-container
>> Version: 228-2
>> Severity: normal
>>
>> Hi,
>>
>> machines.target is not enabled by default. This means machines
>> configure
Control: tags -1 confirmed
On 1 December 2015 at 08:32, Ansgar Burchardt wrote:
> Package: systemd-container
> Version: 228-2
> Severity: normal
>
> Hi,
>
> machines.target is not enabled by default. This means machines
> configured to start at boot with "machinectl enable " will
> actually not
Processing control commands:
> tags -1 confirmed
Bug #806787 [systemd-container] systemd-container: machines.target not enabled
by default
Added tag(s) confirmed.
--
806787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with pro
Package: systemd-container
Version: 228-2
Severity: normal
Hi,
machines.target is not enabled by default. This means machines
configured to start at boot with "machinectl enable " will
actually not start unless one also enables machines.target manually.
Ansgar
-- System Information:
Debian Rel
15 matches
Mail list logo
