Fondos europeos:FEDER, FEI y BEI. Para Pymes y autónomos
constituidos y que operen en España. Importe máximo: 12,5
millones por Pyme. Al tratarse de líneas con garantía del FEI
cuentan con condiciones preferentes. Somos expertos en gestionar
líneas con fondos europeos. Quiero saber más Si
Am 25.06.2018 um 17:45 schrieb Martin Steigerwald:
> Michael Biebl - 25.06.18, 17:20:
>> Am 25.06.2018 um 15:11 schrieb Michael Biebl:
>>> Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
Package: systemd
Version: 239-1
Severity: normal
> […]
Since using kernel 4.17-rc7 I thin
Am 25.06.2018 um 15:11 schrieb Michael Biebl:
> Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
>> Package: systemd
>> Version: 239-1
>> Severity: normal
>>
>> Dear Michael, dear Maintainers,
>>
>> Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
>> kernel), I see a stra
Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
> Package: systemd
> Version: 239-1
> Severity: normal
>
> Dear Michael, dear Maintainers,
>
> Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
> kernel), I see a strange new behavior on this ThinkPad T520. I did not yet
Processing control commands:
> reassign -1 debootstrap
Bug #902350 [systemd-container] systemd-container: /proc/1/environ doesn't
contain "container=systemd-nspawn" info
Bug reassigned from package 'systemd-container' to 'debootstrap'.
No longer marked as found in versions systemd/239-1.
Ignoring
control: reassign -1 debootstrap
Hi,
I've got a suggestion to use $container to detect systemd-nspawn,
it can be used before/after 239-1. debootstrap should be changed
to use it, so reassign to debootstrap.
--
Regards,
Hideki Yamane henrich @ debian.org/iijmio-mail.jp
___
Package: systemd-container
Version: 239-1
Severity: normal
Dear Maintainer,
In debootstrap, it checks whether systemd-nspawn environment with
/proc/1/environ contains "container=systemd-nspawn"
> root@sid:~# cat /proc/1/environ
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bi
Dear Michael.
Thank you for your replies.
Michael Biebl - 25.06.18, 10:26:
> Am 25.06.2018 um 10:14 schrieb Martin Steigerwald:
> > severity 902336 important
> > thanks
> >
> > Martin Steigerwald - 25.06.18, 09:18:
> >> Package: systemd
> >> Version: 239-1
> >> Severity: normal
> >
> > […]
> >
Am 25.06.2018 um 10:14 schrieb Martin Steigerwald:
> severity 902336 important
> thanks
>
> Martin Steigerwald - 25.06.18, 09:18:
>> Package: systemd
>> Version: 239-1
>> Severity: normal
> […]
>> % systemctl --state=failed
>> UNIT LOAD ACTIVE SUBDESCRIPTION
>> ● chrony.service l
Processing commands for cont...@bugs.debian.org:
> severity 902336 important
Bug #902336 [systemd] systemd: sddm login screen does not appear until after
more than a minute
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
severity 902336 important
thanks
Martin Steigerwald - 25.06.18, 09:18:
> Package: systemd
> Version: 239-1
> Severity: normal
[…]
> % systemctl --state=failed
> UNIT LOAD ACTIVE SUBDESCRIPTION
> ● chrony.service loaded failed failed chrony, an NTP client/server
> ● upower.service
Am 25.06.2018 um 09:18 schrieb Martin Steigerwald:
> Kernel: Linux 4.17.0-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT)
I would try a Debian provided kernel as a first step.
What happens if you restart chrony when the system is up an running?
Does chrony log something itself?
The journal log from
Package: systemd
Version: 239-1
Severity: normal
Dear Michael, dear Maintainers,
Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla
kernel), I see a strange new behavior on this ThinkPad T520. I did not yet
test whether it is related to the kernel or something else I upgrad
13 matches
Mail list logo
