lease ask.
Michael
Am 06.03.24 um 19:22 schrieb Michael Biebl:
On Wed, 6 Mar 2024 12:53:47 -0500 Jeffrey Walton
wrote:
Package: systemd
Version: 255.4-1
Tags: sid
It looks like Systemd's timedatectl does not recognize ntpsec. Using
it results in 'NTP service: n/a&#
Am 07.03.24 um 15:12 schrieb Timo Weingärtner:
Package: systemd-resolved
Version: 252.22-1~deb12u1
Severity: important
X-Debbugs-Cc: timo.weingaert...@quantumsimulations.de
After installing systemd-resolved name resolution does not work anymore:
8<8<
# apt-get --no-install-recommends
Am 07.03.24 um 16:22 schrieb Michael Biebl:
The chain of events afaics is this:
1/ postinst creates systemd-resolve
2/ systemd-resolved.service is started in postinst
3/ dbus trigger is activated after postinst and the dbus config is reloaded
Because the dbus daemon reload happens after the
Control: tags -1 + upstream
Am 07.03.24 um 20:25 schrieb Kai Palomaki:
Package: systemd
Version: 247.3-7+deb11u4
Severity: normal
X-Debbugs-Cc: armando.va...@gmail.com
Dear Maintainer,
* What led up to the situation?
A systemd service unit "test" has SyslogFacility=local0 set. Service
Am 05.04.24 um 11:38 schrieb Fabian Greffrath:
Package: systemd
Version: 255.4-1
Severity: normal
Hi,
sorry if this is a trivial question, but I am somehow new to this
systemd/systemctl stuff - or at least until now everything worked as
expected. ;)
Whenever I try to load a user service, syste
Am 07.04.24 um 18:19 schrieb Raphaël Halimi:
Note 1: one could think that it's debootstrap's fault for not resolving
dependencies on virtual packages; indeed, it has already been reported
several times (#878961, merged with #827602 and #931760; as well as
Launchpad #86536) unfortunately never
Hi,
after 13 years, I decided to step down as systemd maintainer and I've
removed myself as Uploader from all systemd related packages at
https://salsa.debian.org/systemd-team/, turned off gitlab notifications
and unsubscribed from pkg-systemd-maintainers@l.a.d.n
I think it's time to move on
We have two separate issues here:
a/ /tmp-on-tmpfs
b/ time based clean-up of /tmp and /var/tmp
I think it makes sense to discuss/handle those separately.
Regarding a/:
tmp.mount as shipped by systemd uses the following mount options:
"mode=1777,strictatime,nosuid,nodev,size=50%"
In the past th
Am 05.05.24 um 22:04 schrieb Luca Boccassi:
This will be mentioned in NEWS (and I guess in the release notes when
the time comes), together with the instructions to override for anybody
wanting to keep the old behaviour, which is as trivial as:
..
touch /etc/tmpfiles.d/tmp.conf
This doesn'
Am 06.05.24 um 12:18 schrieb Luca Boccassi:
Defaults are defaults, they are trivially and fully overridable where
needed if needed. Especially container and VM managers these days can
super trivially override them via SMBIOS Type11 strings or
Credentials, ephemerally and without changing the gues
Package: systemd
Version: 256~rc3-4
Severity: normal
Please do not not ship conflicting configuration for /run/lock
/usr/lib/tmpfiles.d/debian.conf:d /run/lock1777 root root - -
/usr/lib/tmpfiles.d/legacy.conf:d /run/lock 0755 root root -
triggering unnecessary warnings.
please do find a proper solution.
wontfix is it not.
OpenPGP_signature.asc
Description: OpenPGP digital signature
Control: reopen -1
On Tue, 28 May 2024 17:15:02 +0100 Luca Boccassi wrote:
Control: tags -1 wontfix
Control: close -1
On Tue, 28 May 2024 17:44:54 +0200 Michael Biebl
wrote:
> Package: systemd
> Version: 256~rc3-4
> Severity: normal
>
>
> Please do not not ship conflic
Am 03.07.24 um 21:00 schrieb Lionel Élie Mamane:
On Wed, Jul 03, 2024 at 07:25:15PM +0200, Michael Biebl wrote:
connect(5, {sa_family=AF_UNIX,
sun_path="/run/systemd/userdb/io.systemd.DynamicUser"}, 45) = -1 ECONNREFUSED
(Connection refused)
systemd should be listening on t
Package: systemd
Version: 256.2-1
Severity: normal
Given the latest changes in procps, /etc/sysctl.d/99-sysctl.conf has
now become a dangling symlink on fresh installations:
procps (2:4.0.4-5) unstable; urgency=medium
...
* Remove /etc/sysctl.conf as using /etc/sysctl.d/*.conf is better
...
that polkitd failed because systemd-sysusers
failed to create the polkitd user which makes this a systemd issue. Thus
reassigning.
Michael
Am 20.07.24 um 14:58 schrieb Andreas Tille:
Control: tags -1 - moreinfo
Hi again,
Am Wed, Jul 17, 2024 at 06:15:06PM +0200 schrieb Michael Biebl:
Can you
Control: severity -1 serious
I can reproduce the "Failed to check if group polkitd already exists:
Connection refused" error in a bullseye VM that is dist-upgraded to
bookworm.
systemd v247 before the upgrade listens on
/run/systemd/userdb/io.systemd.DynamicUser
once systemd has been upgra
Am 20.07.24 um 17:24 schrieb Michael Biebl:
Control: severity -1 serious
I can reproduce the "Failed to check if group polkitd already exists:
Connection refused" error in a bullseye VM that is dist-upgraded to
bookworm.
systemd v247 before the upgrade listens on
/run/syst
Am 20.07.24 um 17:36 schrieb Michael Biebl:
Btw, I vaguely remember successfully testing dist-upgrades of a GNOME
installation from bullseye to bookworm. So I suspect this was broken by
one of the latest stable updates
Just tested this by upgrading
247.3-7+deb11u4 → 252.6-1 (snapshots.d.o
Am 20.07.24 um 17:40 schrieb Michael Biebl:
Am 20.07.24 um 17:36 schrieb Michael Biebl:
Btw, I vaguely remember successfully testing dist-upgrades of a GNOME
installation from bullseye to bookworm. So I suspect this was broken
by one of the latest stable updates
Just tested this by upgrading
Am 20.07.24 um 17:44 schrieb Michael Biebl:
Am 20.07.24 um 17:40 schrieb Michael Biebl:
Am 20.07.24 um 17:36 schrieb Michael Biebl:
Btw, I vaguely remember successfully testing dist-upgrades of a GNOME
installation from bullseye to bookworm. So I suspect this was broken
by one of the latest
Weitergeleitete Nachricht
Betreff: Archived bug #1002993 seems to be related to unprivileged
containers
Datum: Tue, 3 Sep 2024 21:24:25 +0200
Von: Dr. Lars Hanke
An: bi...@debian.org
Dear Michael,
well, I know the bug has been archived, but I just saw exactly the same
be
Control: tags -1 + moreinfo
Am 11.11.18 um 08:06 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 239-11
>
> # aptitude full-upgrade
>
> Processing triggers for systemd (239-11) ...
> dpkg: warning: package not in status nor available database at line 1:
> libx265-160:amd64
> dpkg: warni
Am 11.11.18 um 11:41 schrieb Michael Biebl:
> Could you please file an issue at
> https://github.com/systemd/systemd/issues
Ideally, before doing so, it would be good to verify that this behaviour
is still reproducible with the current upstream version, i.e. v239,
which is available in sid/
Am 09.11.18 um 11:49 schrieb Lars Luthman:
> When the computer is suspended, the randomized delay keeps on running instead
> of pausing, and when it's woken up, the timer is 7 minutes nearer to expiring
> rather than 0 minutes as expected. If the delay expires while the computer is
> suspended, sy
Hi Dave,
On Sun, 28 Oct 2018 16:16:52 -0400 John David Anglin
wrote:
> On 2018-09-25 10:15 AM, John David Anglin wrote:
> > I will test the proposed change once this bug is fixed:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=909440
> I had a successful build of systemd 239-11 with the at
Control: reassign -1 insserv
[please always CC the maintainers of the packge when you reassign a bug
report]
Am 14.11.18 um 22:30 schrieb Debian Bug Tracking System:
> Processing commands for cont...@bugs.debian.org:
>
>> reassign 556893 init-system-helpers
> Bug #556893 [sysv-rc] say which 'de
[CCing debian-init-diversity which is planning to adopt insserv ttbomk]
On Tue, 01 Jun 2010 11:15:17 +0800 jida...@jidanni.org wrote:
> Package: sysv-rc
> Version: 2.88dsf-7
> Severity: wishlist
> File: /usr/share/man/man8/update-rc.d.8.gz
>
> We read
>-f Force removal of symlinks eve
Control: reassign -1 insserv
On Tue, 01 Jun 2010 13:52:48 +0800 jida...@jidanni.org wrote:
> Package: sysv-rc
> Version: 2.88dsf-7
> Severity: wishlist
>
> Let's take a look at this warning
>
> # update-rc.d cron defaults
> update-rc.d: using dependency based boot sequencing
> update-rc.d: warni
On Thu, 1 Nov 2018 07:47:48 +0100 Michael Biebl wrote:
> Am 01.11.18 um 03:22 schrieb Keh-Ming Luoh:
>
> > I think there is a bug in debian/extra/make-sysusers-basic
>
>
> I can confirm that running systemd-sysusers in a fresh sid chroot yields:
> > # systemd-
Hi René
On Fri, 7 Sep 2018 02:08:11 +0200 Michael Biebl wrote:
> On Mon, 25 Jun 2018 00:35:50 +0200 =?ISO-8859-1?Q?Ren=E9?= Krell
> wrote:
> > Hello Michael,
> >
> > yes, I'm interested, but I still had no success when following the
> > rough advises. I
Hi
On Tue, 23 Jan 2018 19:39:29 -0500 "LeJacq, Jean Pierre"
wrote:
> Package: systemd
> Version: 236-3~bpo9+1
> Severity: normal
>
> Dear Maintainer,
>
> I have configured a btrfs based storage system with the followin
> characteristics:
>
> * SSD drive using Opal Full Disk Encryption. No issu
On Sat, 9 Sep 2017 17:18:35 -0700 Josh Triplett
wrote:
> On Sun, Sep 10, 2017 at 01:43:09AM +0200, Michael Biebl wrote:
> > On Thu, 13 Jul 2017 15:09:29 -0700 Josh Triplett
> > wrote:
> > > Package: systemd
> > > Version: 233-10
> > > Severity: norma
On Sat, 17 Mar 2018 03:23:59 +0100 Michael Biebl wrote:
> On Tue, 30 Jan 2018 04:30:58 -0500 (EST) bw wrote:
>
> > I'll go back and read your earlier posts, and see what I need to do. I
> > guess you are recommending that I upgrade systemd and use upstream bug
> >
On Sat, 20 Oct 2018 16:47:01 +0200 Michael Biebl wrote:
> What happens if you manually (as root) execute
> /lib/systemd/systemd-rfkill
>
> Does this have any influence on your wifi connection?
>
...
On Sat, 20 Oct 2018 16:33:23 +0200 Michael Biebl
wrote:> Am 20.10.18 u
Hi Martin
Am 16.11.18 um 18:32 schrieb Martin Pitt:
> I also added some postinst cleanup with some reasonable defensiveness.
> (Double-checking it now)
>
> @Michael, does that seem ok to you?
The patch seems to work fine as is.
That said, lintian is not happy about the direct parsing and manglin
On Mon, 31 Oct 2016 07:46:13 +0200 Martin Pitt wrote:
> Alexander Kurtz [2016-10-30 22:05 +0100]:
> > Thanks a lot for your quick reply! You might want to consider also
> > adding "armhf" to that list, since both gnu-efi [0] and u-boot-rpi [1]
> > are also available there (in contrast to "armel" w
On Fri, 3 Jul 2015 08:25:37 -0400 Tom H wrote:
> Fedora (and other distributions as well as systemd upstream) uses
> "/usr/lib/systemd/systemd-vconsole-setup" and "/etc/vconsole.conf"
> whereas Debian uses its home-grown solution with systemd and sysvinit.
>
> So "localectl list-keymaps" cannot w
Am 17.11.18 um 20:32 schrieb Michael Biebl:
> One obvious difference between the keymap files shipped by kbd and
> console-data is, that kbd uses a map.gz file extension whereas
> console-data uses kmap.gz.
Something like the attached patch might be sufficient for "localectl
list-
> On Sat, Nov 17, 2018 at 08:32:40PM +0100, Michael Biebl wrote:
>> On Fri, 3 Jul 2015 08:25:37 -0400 Tom H wrote:
>>> Fedora (and other distributions as well as systemd upstream) uses
>>> "/usr/lib/systemd/systemd-vconsole-setup" and "/etc/vconsole
Am 17.11.18 um 14:11 schrieb Michael Biebl:
> Any reason you didn't use "getent group" and "delgroup" ?
I applied your patch and simplified postinst a bit using delgroup;
delgroup --system seems to DTRT already.
https://salsa.debian.org
Control: reassign -1 systemd-shim
Control: tags -1 - moreinfo unreproducible
On Mon, 3 Aug 2015 23:23:11 +0200 Michael Biebl wrote:
> Control: severity -1 normal
> Control: tags -1 moreinfo unreproducible
>
> Am 03.08.2015 um 18:30 schrieb Marcin Wolcendorf:
> > Package: s
Hi Bernhard!
On Thu, 30 Nov 2017 13:11:12 +0100 Bernhard Schmidt
wrote:
> Package: systemd
> Version: 235-3
> Severity: normal
>
> Hi,
>
> after upgrading from Stretch to Buster the physical interface in my bridge
> is stuck in "configuring", causing systemd-networkd-wait-online to stall
> and
On Mon, 06 Jul 2015 23:31:07 +0200 =?ISO-8859-1?Q?Silv=E9rio?= Santos
wrote:
> Hallo Michael,
>
> network is configured with network-manager using DHCP towards an ISC-DHCP-
> server with MAC-address-reservation.
Are you using a wireless connection?
I remember there was a bug in wpa_supplicant wh
Am 18.11.18 um 12:54 schrieb Martin Pitt:
> Hello Michael,
>
> Michael Biebl [2018-11-17 15:47 +0100]:
>>> I know that arm64 EFI boot works (Canonical uses it in their internal
>>> OpenStack deployment), but as far as I know there is no existing
>>> armhf EFI i
Hi John,
Am 18.11.18 um 19:18 schrieb John David Anglin:
> I understand the problem. The merge comment shown above is from gcc-9.
> Systemd compiles fine
> on hppa using gcc-9.
>
> The merging of PIC and PIE options is not supported using gcc-8. This is
> the corresponding comment in gcc-8:
[.
Am 18.11.18 um 20:46 schrieb John David Anglin:
> On 2018-11-18 1:54 p.m., Michael Biebl wrote:
>> Thanks for your detailed analysis.
>> If there is something to fix on the systemd side, it would be great if
>> you can create a pull request upstream as suggested in
>>
Am 21.11.18 um 18:03 schrieb Simon McVittie:
> Real solution:
>
>> ===File /etc/dbus-1/system.d/org.freedesktop.systemd-shim.conf===
> ...
>>
> ...
>>
>>
>
> org.freedesktop.systemd-shim.conf should not have this Deny line. It's
> redundant with the implicit default-de
Hi
On Thu, 22 Nov 2018 16:01:33 + Ian Jackson
wrote:
> To the systemd maintainers: will you have time to look at this, and
> make the appropriate change, soon ? If not then one of us could
> probably prepare a patch, if that would be helpful.
A patch for 40-systemd would be highly apprecia
Control: reassign -1 linux-image-4.9.0-7-686-pae
Control: retitle -1 ehci-pci.ko prevents shutdown
Hi
Am 23.11.18 um 04:12 schrieb Andrew Pavlomanolakos:
> Hi Michael,
>
> I built a 4.9.137 kernel and added some trace code and found that the
> issue occurs during device_shutdown() in the linux k
Package: ftp.debian.org
Severity: normal
Hi,
we want to have libnss-systemd installed by default if systemd is the
active PID 1, while still retaining the option to uninstall the package.
For that, the systemd-sysv package gained a Recommends: libnss-systemd [1]
Unfortunatly, Recommends are not
On Wed, 28 Nov 2018 21:58:07 +0100 Patrice Duroux
wrote:
> Package: systemd-coredump
> Version: 239-13
> Severity: normal
>
> Hi,
>
> Trying to debug a trouble with the tracker package (in fact with
> tracker-extract) so I have installed systemd-coredump. Then I got in few
> seconds 2,2G for 1
Am 30.11.2018 um 13:47 schrieb Adrian Bunk:
> Control: tags 907409 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for casync (versioned as 2+20180321-2.1) and
> uploaded it to DELAYED/14. Please feel free to tell me if I should
> cancel it.
Feel free to upload without delay.
Thanks
Am 30.11.2018 um 13:40 schrieb Pierre Ynard:
> Package: udev
> Version: 239-13
> Severity: wishlist
>
> Dear Maintainer,
>
> I looked for old bug reports about this and was surprised not to
> find anything filed against udev. My issue is with this snippet in
> /etc/init.d/udev:
>
> if ! ps --no-
Hi,
there is some discussion going on upstream atm at
https://github.com/systemd/systemd/issues/8221
and
https://github.com/systemd/systemd/issues/7587
Your ticket has been closed as not a bug in systemd.
https://github.com/systemd/systemd/issues/8221#issuecomment-443159165
Thought I'd let you k
Control: reassign openssh-server 1:7.9p1-1
Am 01.12.18 um 15:07 schrieb Nathan Anthonypillai:
> Greetings,
>
> First off, thank you for your work on this issue.
>
> After spending a bit more that 6 hours strugging with this issue on a KVM VM
> running headless debian-testing, I simply want to ad
Hi Mert!
Am 29.11.18 um 14:44 schrieb Mert Dirik:
> I've created a merge request for 40-systemd at
> https://salsa.debian.org/systemd-team/systemd/merge_requests/19 .
> Reviews and comments are welcomed.
>
> If this is fully applied, systemd redirection will work correctly for
> all init-d-script
Am 01.12.18 um 23:00 schrieb Michael Biebl:
> I'm still convinced, that fixing this properly in init-d-script would be
> the much better solution. If init-d-script was implemented in C, it
> could be used as a shebang/interpreter on non-Linux and it would be
> possible to have $
Am 01.12.18 um 23:04 schrieb Michael Biebl:
> Am 01.12.18 um 23:00 schrieb Michael Biebl:
>> I'm still convinced, that fixing this properly in init-d-script would be
>> the much better solution. If init-d-script was implemented in C, it
>> could be used as a shebang/inter
Am 01.12.18 um 23:31 schrieb Thorsten Glaser:
> On Sat, 1 Dec 2018, Michael Biebl wrote:
>
>> I'd also be interested to know why
>>
>> #!/usr/bin/env /lib/init/init-d-script
>> is preferred over
>> #!/bin/sh /lib/init/init-d-script
>> given that init
Am 01.12.18 um 23:40 schrieb Thorsten Glaser:
> On Sat, 1 Dec 2018, Michael Biebl wrote:
>
>> If there is a binary implementation, then you would be using
>> #!/lib/init/init-d-script
>
> Yes, but it would *also* still work with env(1).
But it would only be an unnece
Am 01.12.18 um 23:31 schrieb Thorsten Glaser:
> This will also make it easier to switch to a binary
> implementation later.
Ok, I take this as a positive signal. So far this has been rejected
outright.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
uni
Am 03.12.18 um 14:53 schrieb ed.go...@free.fr:
> Reproduction steps
> ==
>
> # as root, i don't have a big /, so i'll be using /home. Do as you see fit
> $ mkdir -p /home/chroots
> $ cd /home/chroots
> $ debootstrap stable stable
> [... does its work successful
Am 03.12.18 um 16:45 schrieb ed.go...@free.fr:
>> I assume the main difference is that you are not using a Debian
>> provided
>> kernel and I do?
>
> Yes i'm running my own compiled 4.19.5 kernel, old habit of mine to use
> make-kpkg builds.
>
> I'll install the standard debian kernel and give a
On 03.12.18 17:45, Harald Dunkel wrote:
> Package: udev
> Version: 239-14
>
> After the upgrade from -13 to -14 mouse and keyboard stopped working.
> Moving back to version -13 made the problem go away.
>
> Xorg.log files for old and new udev are attached. Check line 244.
Are you using sysivnit?
On 10.12.18 11:29, ed.go...@free.fr wrote:
> For no reason that i can explain precisely, since I updated/rebooted, I
> can use the systemd-container 239-15 to spawn the containers...
Are you saying, it is now working with your custom kernel as well?
--
Why is it that all of the instruments s
On 10.12.18 11:09, Matthias Urlichs wrote:
> Hi,
>
> this bug blocks two others (which actually add systemd units)
I don't see how a patch to "service" blocks those other two bug reports?
Especially #819156 looks like a completely different issue.
--
Why is it that all of the instruments seekin
On 10.12.18 12:13, Matthias Urlichs wrote:
> On the other hand -- what do you mean, "patch to service"? The patch
> in this bug changes 40-systemd to consider .target files in addition to
> .service.
I was looking at #826011. I guess I got confused as you posted it to
both bug reports.
--
Why is
Hi
Am 01.06.16 um 14:07 schrieb Terry Burton:
> This message [1] identifies that compound target units are the
> appropriate mechanism for controlling multiple service units.
>
> The LSB override hook currently only consider .service units, ignoring
> compound .target units.
>
> Support for this
Am 10.12.18 um 14:12 schrieb Michael Biebl:
> Say you have test.service and test.target.
> I'm not sure if there is a reliable way to detect whether the user
> wanted test.service or test.target when running "/etc/init.d/test ..."
Just tested systemctl. If you have a test
Am 11.12.18 um 08:13 schrieb lanquil:
> Thanks for your answer,
> I was thinking to execute it directly because the manual says:
>
> `SYNOPSISsystemd-journal-remote [OPTIONS...] [-o/--output=DIR|FILE]
> [SOURCES...]`
>
> and I need to convert an exported journal file (`journalctl -o exp
Am 13.12.18 um 21:04 schrieb Howard Johnson:
> Lennart Poettering, the author if *systemd-ui* (which loads the command
> *systemadm* GUI) writes: "*It's unmaintained since many years. Don't
> use it. It's broken."
> *
>
> So I suppose it needs to be removed from Debian.
It already has been remo
Am 15.12.18 um 11:24 schrieb Ben Harris:
> Package: systemd
> Version: 239-13
> Severity: minor
> Tags: ipv6
>
> Dear Maintainer,
>
> I have configured timesyncd to use sntp.cam.ac.uk as an NTP server (see
> configuration below). That name resolves to 2001:630:212:8::123:20.
It resolves to 1
Hi Ben
Am 15.12.18 um 13:22 schrieb Ben Harris:
> Indeed, the same problem occurs if I explicitly specify the IPv6 address:
>
> wraith:~# grep ^NTP= /etc/systemd/timesyncd.conf
> NTP=2001:630:212:8::123:20
>
> wraith:~# timedatectl timesync-status | head -1
> Server: ::2001:630:212:8:0:0
Am 15.12.18 um 15:12 schrieb Ben Harris:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/11169
>
> On Sat, 15 Dec 2018, Michael Biebl wrote:
>
>> Since this doesn't look like a Debian specific problem, would you mind
>> filing this issue upst
Control: severity -1 important
Control: tags -1 moreinfo
Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:
> | systemd[1]: Caught , dumped core as pid 2097.
Please try to get a backtrace following
https://wiki.debian.org/HowToGetABacktrace
Thanks,
Michael
--
Why is it that all of the inst
Control: severity -1 wishlist
Control: retitle -1 allow crediting the seed file for some entropy
Control: forwarded -1 https://github.com/systemd/systemd/pull/10621
On Sat, 15 Dec 2018 09:17:46 +0100 Stefan Fritsch wrote:
> reassign 914297 systemd
> affects 914297 apache2
> thanks
>
> On Saturd
Am 04.12.18 um 00:26 schrieb Dmitry Bogatov:
>
> [2018-11-28 18:48] Dmitry Bogatov
>> I am worried: freeze is coming, and nothing is happening. I am not going
>> to miss another release.
>
> Hereby I inform you, that I uploaded NMU into DELAYED/15. Feel free to
> cancel it, providing rationale w
Am 17.12.18 um 12:52 schrieb Raphael Manfredi:
> Can I have clues to collect information and try to resolve this problem?
Please boot with systemd as PID 1 and try to get a debug shell on tty9
by adding systemd.debug-shell=1 to the kernel command line.
On tty9 you can then inspect the system.
Th
Am 17.12.18 um 13:13 schrieb Cristian Ionescu-Idbohrn:
> On Mon, 17 Dec 2018, Michael Biebl wrote:
>>
>> Control: severity -1 important
>> Control: tags -1 moreinfo
>>
>> Am 17.12.18 um 11:25 schrieb Cristian Ionescu-Idbohrn:
>>
>>> | systemd[1]: Ca
clone 914297 -1
reassign -1 release-notes
retitle -1 document getrandom changes causing entropy starvation
thanks
Am 17.12.18 um 13:28 schrieb Alexander E. Patrakov:
> Michael Biebl :
>> On Sat, 15 Dec 2018 09:17:46 +0100 Stefan Fritsch wrote:
>>> It turns out there was a s
Am 17.12.18 um 13:27 schrieb Raphael Manfredi:
> Quoting Michael Biebl:
> : Please boot with systemd as PID 1 and try to get a debug shell on tty9
> : by adding systemd.debug-shell=1 to the kernel command line.
> :
> : On tty9 you can then inspect the system.
> : The outpu
Am 17.12.18 um 13:52 schrieb Stefan Fritsch:
> On Mon, 17 Dec 2018, Michael Biebl wrote:
>>> It turns out there was a similar bug against openssh which was closed as
>>> wontfix [1]. I don't see how apache can do anything about this, either.
>>
>> There is.
Am 17.12.18 um 13:59 schrieb Stefan Fritsch:
> But we have good entropy on disk.
How do you know that and what if there is no seed file from a previous boot?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description
Am 17.12.18 um 14:06 schrieb Raphael Manfredi:
> Quoting Michael Biebl:
> : Could you uncomment those autofs mounts and try again?
>
> I commented the line in /etc/auto.master.d/usr_local.autofs, to read:
>
> #/auto/usr_local /etc/auto.master.d/usr_local--timeout=1800 -
Am 17.12.18 um 14:51 schrieb Cristian Ionescu-Idbohrn:
> On Mon, 17 Dec 2018, Michael Biebl wrote:
>>
>> Do you by chance still have a core file of the crash?
>
> If there were one, where would I find it?
>
> Are there instructions somewhere? I do see both
> /usr
Am 17.12.18 um 14:58 schrieb Raphael Manfredi:
> I'd really like to help you debug this problem, as I'm sure I am not the
> first, and will not be the last, to have a similar problem!
Can you find out, if you have a service which tries to access /usr/local
during boot?
--
Why is it that all of
Am 17.12.18 um 18:11 schrieb Raphael Manfredi:
> I quickly grepped through /etc/init.d/* files (I know systemd does
> not use these anymore excepted when there is no unit and it calls
> some of these scripts). There are many files that set a PATH explicitly
> and which starts whith /usr/local/s?bi
Am 18.12.2018 um 12:09 schrieb Raphael Manfredi:
> Quoting Michael Biebl:
> : What happens if you boot into emergency mode (add emergency to the
> : kernel command line)?
> : This will start a very minimal system without any networking or started
> : services. Can you suc
control: tags 916880 + fixed-upstream patch
control: fixed 916880 234-1
(updated the meta-data)
Hi,
thanks for the detailed bug report.
Am 19.12.18 um 19:57 schrieb PODURY, SHARMILA:
> commit 5b3cc0c86aeddd4615e7e28e79aa89e5b77a6507
> Author: Yusuke Nojima
> Date: Sun Apr 30 02:37:53 2017 +0
control: tags -1 + moreinfo
Am 23.12.18 um 00:35 schrieb Ben Caradoc-Davies:
> Package: systemd
> Version: 240-1
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> after upgrade to systemd 240-1, local-fs.target fails with result
> 'dependency',
> causing boo
Control: tags -1 + moreinfo
Am 23.12.18 um 00:29 schrieb Vladimir Tiukhtin:
> Docker limits this system call be default. However RedHat image is
> running correctly which means that they have back ported a patch for
> systemd from upstream which resolves this problem on systemd side. Can
> you ple
Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies:
> Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to
> boot an 4.18.0-3-amd64 initramfs to get a working system.)
So 4.18 works and 4.19 fails?
> Attached photo shows console after failure. Plymouth LUKS passphrase
> entry has su
Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies:
> On 23/12/2018 13:11, Michael Biebl wrote:
>> Am 23.12.18 um 00:58 schrieb Ben Caradoc-Davies:
>>> Failure was seen with linux-image-4.19.0-1-amd64 4.19.9-1. (Needed to
>>> boot an 4.18.0-3-amd64 initramfs to get a workin
Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies:
> Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed
> Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator failed.
> Dec 23 13:07:52 ripley systemd[376]:
> /lib/systemd/system-generators/lvm2-activation-generator f
Control: retitle -1 lvm2 logical volumes are not properly initialized
Am 23.12.18 um 01:38 schrieb Ben Caradoc-Davies:
>> Can you provide a verbose debug log as requested in my previous reply?
>
> "journalctl -alb" output attached to my previous email. Please let me
> know if you require
Ok, fir
On Sun, 23 Dec 2018 00:15:55 + Vladimir Tiukhtin
wrote:
> Hi
>
> I believe it can be found here https://github.com/systemd/systemd/pull/5499
Ok, thanks for the reference.
I've updated the bug meta-data accordingly.
Have you verified that the patch fixes your problem with docker?
If so, I'd
Am 23.12.18 um 01:40 schrieb Michael Biebl:
> Am 23.12.18 um 01:28 schrieb Ben Caradoc-Davies:
>> Dec 23 13:07:52 ripley lvm2-activation-generator: lvmconfig failed
>> Dec 23 13:07:52 ripley lvm2-activation-generator: Activation generator
>> failed.
>> Dec 23
Control: tags -1 + moreinfo
Am 23.12.18 um 17:11 schrieb Eric Valette:
> Package: systemd
> Version: 240-1
> Severity: critical
> Justification: breaks unrelated software
>
> After upgrading to 240 version, all my system started to take ages to boot.
> It seems related to disk mapping first and
Am 23.12.18 um 17:16 schrieb Baptiste BEAUPLAT:
> Package: systemd
> Version: 240-1
> Severity: important
>
> Dear Maintainer,
>
> After updating my system, I'm was not able to start my kde desktop (plasma):
>
> The problem is kdeinit5, called itself by startkde, running into an infinite
> loop
101 - 200 of 2021 matches
Mail list logo
