Control: tags -1 + moreinfo
On Sun, 18 Oct 2015 14:52:12 +0300 Aryeh Leib Taurog
wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear Maintainer,
>
> I just recently upgraded from wheezy to jessie. The /home partition
> is LUKS encrypted.
>
> Shutdown always takes
Control: tags -1 + moreinfo
On Sun, 3 Mar 2019 22:57:29 + (UTC) Pierre Ynard
wrote:
> reassign 813176 systemd
> thanks
>
> This line is, or was, part of the systemd-fsckd source code:
>
>
On Tue, 24 Jul 2018 22:02:11 +0200 Michael Biebl wrote:
> Am 24.07.2018 um 21:33 schrieb Francesco Poli:
> > On Tue, 24 Jul 2018 01:46:51 +0200 Michael Biebl wrote:
> >
> >> Am 23.07.2018 um 19:53 schrieb Francesco Poli:
> > [...]
> >>> I am aga
Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>> Can you provide the output of
>> systemctl status certbot.timer
>> journalctl -u certbot.timer
>
> The output of `systemctl show certbot.timer` is at
> h
Am 10.03.19 um 17:05 schrieb Harlan Lieberman-Berg:
> Hello pkg-systemd!
>
> There's a strange bug being reported in the stable-updated version of
> certbot about the systemd timer that I'm having trouble reproducing or
> understanding how it could happen.
>
> According to the users reporting
Control: severity -1 serious
Let's bump this to serious. I think you should consider making another
stable upload for this.
As users have pointed out, systems which aren't rebooted regularly are
otherwise up for a nasty experience.
You might consider asking the security team to distribute the
Am 10.03.19 um 16:55 schrieb Michael Biebl:
> I'd like to make a stable upload for systemd, fixing 5 separate issues.
> Two of them have a CVE.
...
> The fix for CVE-2018-15686/#912005 is the most invasive one. I based it
> partially on what was uploaded to old-stable by the deb
Package: release.debian.org
Severity: normal
Tags: stretch
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I'd like to make a stable upload for systemd, fixing 5 separate issues.
Two of them have a CVE.
The changelog is
systemd (232-25+deb9u10) stretch; urgency=medium
*
Hi Mario,
On Fri, 6 Jul 2018 12:41:37 + wrote:
> > -Original Message-
> > From: Michael Biebl [mailto:bi...@debian.org]
> > Sent: Friday, July 6, 2018 5:46 AM
> > To: Joel Cross; 902...@bugs.debian.org; Limonciello, Mario
> > Subject: Re: Bug#902416
Am 10.03.19 um 17:59 schrieb Michael Biebl:
> Am 10.03.19 um 17:54 schrieb Michael Biebl:
>> Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
>>> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>>>> Can you provide the output of
>>>> systemc
Am 10.03.19 um 18:23 schrieb Harlan Lieberman-Berg:
> On Sun, Mar 10, 2019 at 1:19 PM Michael Biebl wrote:
>> Let's bump this to serious. I think you should consider making another
>> stable upload for this.
>> As users have pointed out, systems which aren't rebooted regularl
Am 10.03.19 um 17:54 schrieb Michael Biebl:
> Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
>> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>>> Can you provide the output of
>>> systemctl status certbot.timer
>>> journalctl -u certbot.timer
Hi Ben
Am 10.03.19 um 23:17 schrieb Ben Hutchings:
> I think it would make sense for systemd to only set the hibernation
> device if it's not already set (i.e. if /sys/power/resume contains
> "0:0\n").
I get $ cat /sys/power/resume
8:4
which part is responsible for setting that?
--
Why is it
Hi everyone,
given Martin's latest commits in Git, I wonder what we should do about
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-rules-Permission-changes-for-dev-dri-renderD.patch
Should we drop this patch in Debian and follow upstream, i.e. make
Am 10.03.19 um 17:54 schrieb Michael Biebl:
> Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
>> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>>> Can you provide the output of
>>> systemctl status certbot.timer
>>> journalctl -u certbot.timer
Am 13.03.19 um 19:26 schrieb Marc Haber:
> forwarded #920446 https://github.com/systemd/systemd/issues/11992
> thanks
>
> On Sun, Mar 10, 2019 at 12:04:32AM +0100, Michael Biebl wrote:
>> If this is still a problem with v241, would you mind filing a bug report
>> upstre
Am 07.03.19 um 10:35 schrieb Bob Tracy:
> On Thu, Mar 07, 2019 at 10:17:05AM +0100, Michael Biebl wrote:
>> Could you attach
>> systemctl list-units --type device
>
> Had to specify additional "--all" flag, as all units of type "device"
> are "i
Am 07.03.2019 um 08:33 schrieb Nico Haase:
> Package: systemd
> Version: 241-1~bpo9+1
> Severity: normal
>
> Dear Maintainer,
>
> this morning, apticron reminded me (once more) to upgrade some packages from
> stretch-backports. These included dovecot-core and systemd (and others).
> After
Am 07.03.19 um 08:32 schrieb Bob Tracy:
> On Thu, Feb 28, 2019 at 07:36:37PM +0100, Michael Biebl wrote:
>> Control: tags -1 + moreinfo
>>
>> Please attach the full output "journalctl -alb" output of such a failed
>> boot.
>>
>> I'd also be inter
Am 20.01.2019 um 00:11 schrieb Bob Tracy:
> Architecture: alpha
>
> Kernel: Linux 4.16.0
Could you test with a Debian provided kernel?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital
Am 07.03.19 um 09:47 schrieb Bob Tracy:
> On Thu, Mar 07, 2019 at 09:00:24AM +0100, Michael Biebl wrote:
>> Am 20.01.2019 um 00:11 schrieb Bob Tracy:
>>
>>> Architecture: alpha
>>>
>>> Kernel: Linux 4.16.0
>>
>> Could you test with a Debi
Am 07.03.19 um 10:09 schrieb Michael Biebl:
> Am 07.03.19 um 08:32 schrieb Bob Tracy:
>> On Thu, Feb 28, 2019 at 07:36:37PM +0100, Michael Biebl wrote:
>>> Control: tags -1 + moreinfo
>>>
>>> Please attach the full output "journalctl -alb" outp
Am 09.03.19 um 14:10 schrieb Julien Leproust:
> Hi,
>
> I found the issue.
>
> When looking for /etc files not belonging to any package, I discovered
> that /etc/pam.d/common-* files are managed by pam-auth-update.
>
> Most pam profiles were enabled, except "Register user sessions in the
>
On Thu, 07 Mar 2019 08:33:57 +0100 Nico Haase wrote:
> Package: systemd
> Version: 241-1~bpo9+1
> Severity: normal
>
> Dear Maintainer,
>
> this morning, apticron reminded me (once more) to upgrade some packages from
> stretch-backports. These included dovecot-core and systemd (and others).
>
On Thu, 28 Feb 2019 19:46:04 +0100 Michael Biebl wrote:
> On Fri, 08 Feb 2019 22:24:24 + Qaz W wrote:
> > Package: udev
> > Version: 232-25+deb9u8
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > *** Reporter, please consider
Am 09.03.19 um 15:00 schrieb Michael Biebl:
> Am 09.03.19 um 14:10 schrieb Julien Leproust:
>> Hi,
>>
>> I found the issue.
>>
>> When looking for /etc files not belonging to any package, I discovered
>> that /etc/pam.d/common-* files are managed by pam-au
[bringing Steve, our pam maintainer, into the loop]
Hi Steve,
the following looks like an issue in pam-auth-update and similar to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923362
Any idea what might be going wrong there?
Am 09.03.19 um 19:55 schrieb Julien Leproust:
> Hi,
>
> Well
Control: tags -1 moreinfo unreproducible
On Mon, 4 Mar 2019 08:55:33 -0300 Felipe Sateler
wrote:
> I checked a couple and they both fail on test-stat-util. Any chance
> you could get a backtrace of the failing test?
>
> My guess is that sbuild setups something in /dev in a way that
>
Control: notfound -1 232-25+deb9u9
Control: notfound -1 241-1
Hi Will
Am 09.03.19 um 00:14 schrieb Will Roberts:
> Package: systemd
> Version: 215-17+deb8u10
> Severity: important
> Tags: patch
>
> Dear Maintainer,
>
> The fix for CVE-2018-16864 contains a memory leak that was fixed for
>
Am 09.03.19 um 20:17 schrieb Michael Biebl:
> Thanks for the follow-up information.
> That was really helpful.
>
> Am 09.03.19 um 19:55 schrieb Julien Leproust:
>> And then, pam_systemd.so was incorrectly removed? I'm sure you're going
>> to assume I disabled the second op
Control: forwarded -1 https://github.com/systemd/systemd/issues/11810
On Sun, 03 Feb 2019 13:59:02 -0600 william l-k
wrote:
> The system behaves normally and can shutdown and reboot until the suspend
> state
> is triggered. Once this occurs the system still behaves normally. However,
> when
>
Thanks for the follow-up information.
That was really helpful.
Am 09.03.19 um 19:55 schrieb Julien Leproust:
> And then, pam_systemd.so was incorrectly removed? I'm sure you're going
> to assume I disabled the second option, but I really doubt this.
I said, a manual modification is more likely
Am 18.03.19 um 20:46 schrieb Jean-Pierre:
> Hi,
>
> Any news about a fix ?
>
> Or maybe an URL where I could submit a patch ?
>
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924255
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from
Control: retitle -1 restart logind on package updates
Control: block -1 by 798097
On Thu, 28 Feb 2019 15:09:14 -0600 "Karl O. Pinc" wrote:
> If systemd restarts all of its processes which are affected
> by package upgrade then the only reason to require a restart would
> be if some changes in
Am 18.03.19 um 22:00 schrieb Nico Haase:
> Dear Mika, dear Michael,
>
> thank you for your answers and apologies for answering them so late.
>
> Am 07.03.2019 um 09:15 schrieb Michael Prokop:
>> * Nico Haase [Thu Mar 07, 2019 at 08:33:57AM +0100]:
>>> Package: systemd
>>> Version: 241-1~bpo9+1
On 20.03.19 17:36, Laurent Bonnaud wrote:
> Package: systemd
> Version: 241-2
> Severity: important
>
>
> Dear Maintainer,
>
> on this system, an initial ssh connection needs 11 seconds to complete (as
> root or any other user). Further connections are fast.
Is this problem reproducible if
Am 20.03.19 um 19:19 schrieb Michael Biebl:
> Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
>> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
>> Timestamp generators-finish: Wed 2019-03-20 15:06:38 CET
>
> That is odd.
> Do you have any (user) generators whic
Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
> Timestamp generators-finish: Wed 2019-03-20 15:06:38 CET
That is odd.
Do you have any (user) generators which might take a long time?
--
Why is it that all of the instruments seeking
Control: tags -1 + moreinfo
Am 20.03.19 um 19:24 schrieb Michael Biebl:
> Am 20.03.19 um 19:19 schrieb Michael Biebl:
>> Am 20.03.19 um 19:01 schrieb Laurent Bonnaud:
>>> Timestamp generators-start: Wed 2019-03-20 15:06:27 CET
>>> Timestamp generators-finish:
Am 08.03.19 um 08:09 schrieb Bob Tracy:
> On Thu, Mar 07, 2019 at 10:52:13AM +0100, Michael Biebl wrote:
>> Sounds a bit like
>> https://github.com/systemd/systemd/issues/3446#issuecomment-224046140
>>
>> Please check that your kernel has all options enabled that are
Am 12.03.19 um 20:06 schrieb Marco d'Itri:
> On Mar 11, Michael Biebl wrote:
>
>> Should we drop this patch in Debian and follow upstream, i.e. make
>> render nodes owned by group "render"?
> I favour just following upstream.
> While conceivably somebody
Am 14.03.19 um 09:13 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 241-1
> Severity: minor
> File: /usr/share/bash-completion/completions/journalctl
>
> It's not happy about me wanting to do
> # journalctl > file
Please file this issuee directly upstream at
Control: tags -1 + moreinfo
Am 13.03.19 um 18:14 schrieb Igor Ohrimenko:
> Package: systemd
> Version: 232-25+deb9u9
> Severity: important
>
> Dear Maintainer, I read man system.conf and found multiplicative suffixes. I
> tried to use it, like 1G, but DefaultLimit does not change. I have to use
I've filed https://github.com/systemd/systemd/pull/11995
If that PR is accepted, my plan was to
- cherry-pick that patch
- drop
debian/patches/debian/Revert-udev-rules-Permission-changes-for-dev-dri-renderD.patch
- Add -Dgroup-render-mode=0660 to debian/rules
- Revert
Hi Rebecca
On Thu, 16 Oct 2014 22:22:29 +0100 "Rebecca N. Palmer"
wrote:
> Control: tags -1 patch
>
> Looks like the "swap=plain" assumption is at
> src/cryptsetup/cryptsetup.c:162; here's a patch (untested as yet, will
> try it in the morning if I don't hear anything).
>
> --- cryptsetup.c
Control: tags -1 + moreinfo
Hi Damien
On Tue, 26 Aug 2014 16:58:28 +0200 Damien Clauzel wrote:
> Yes. But there is also the problem of assembling the btrfs raid1 arrays
> after opening the encrypted volumes.
>
> Damien Clauzel
>
>
> 2014-08-26 16:41 GMT+02:00 Mich
Am 09.03.19 um 22:03 schrieb Julien Leproust:
> Indeed, it looks a lot like #923362, though I can't reproduce now by
> manually running dpkg-reconfigure libpam-runtime.
>
> Tell me if I can help debug this, I still have the full apt logs and
> etckeeper on two machines.
>
Sorry, can't really
Hi Marc
On Fri, 25 Jan 2019 17:10:55 +0100 Marc Haber
wrote:
> Package: systemd
> Version: 240-4
> Severity: normal
> File: systemd-networkd
>
> Hi,
>
> On my desktop computer, I run some VMs and am using systemd-networkd.
> The machine has its 'own' network untagged on the ethernet and the VM
On Thu, 14 Apr 2016 15:44:02 +0200 Michael Biebl wrote:
> Package: init-system-helpers
> Version: 1.29
> Severity: normal
> File: /usr/sbin/update-rc.d
>
> If a package ships a native service file, like NetworkManager.service,
> and a static symlink, like network-manager.s
Am 09.03.19 um 20:40 schrieb Santiago Vila:
> On Sat, Mar 09, 2019 at 08:32:10PM +0100, Michael Biebl wrote:
>> Control: tags -1 moreinfo unreproducible
>>
>>
>> On Mon, 4 Mar 2019 08:55:33 -0300 Felipe Sateler
>> wrote:
>>> I checked a couple and the
Am 09.03.19 um 22:27 schrieb Santiago Vila:
> On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote:
>> Am 09.03.19 um 21:50 schrieb Michael Biebl:
>>> Am 09.03.19 um 21:00 schrieb Santiago Vila:
>>>> to which I also add these two lines:
>>> ..>
Hi Colin,
sorry for the late reply
Am 08.03.18 um 13:49 schrieb Colin Watson:
> Package: init-system-helpers
> Version: 1.51
> Severity: normal
>
> dh_systemd_start generates a deb-systemd-invoke command listing all the
> binary package's units. For snapd in Ubuntu, for example, this looks
>
On Sun, 11 Nov 2018 11:43:19 +0100 Michael Biebl wrote:
> 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
&g
Could you again follow the instructions at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916689#10
switch to the debug shell on tty9
- check the network via
ip -c a
- can you ping a remote machine
- attach the output of journalctl -alb
signature.asc
Description: OpenPGP digital signature
Am 09.03.19 um 21:00 schrieb Santiago Vila:
> to which I also add these two lines:
..> /dev/urandom/dev/random nonerw,bind 0 0
This might very well be the culprit, given that test-stat-util does the
following check:
Am 09.03.19 um 23:00 schrieb Santiago Vila:
> The reason I would still consider this as a bug (with whatever severity
> you like) is that symlinking /dev/random to /dev/urandom is a common
> workaround for lack of entropy, which in turn has traditionally been a
> common problem for anybody who
Control: tags -1 + moreinfo
On Fri, 16 Nov 2018 00:52:56 +0100 Michael Biebl wrote:
> Hi
>
> On Tue, 23 Jan 2018 19:39:29 -0500 "LeJacq, Jean Pierre"
> wrote:
> > Package: systemd
> > Version: 236-3~bpo9+1
This version is rather old, could you please try
Hi Marc
On Fri, 07 Jul 2017 17:52:04 +0200 Marc Haber
wrote:
> Package: systemd
> Version: 232-25
> Severity: normal
> Tags: ipv6
>
> Hi,
>
> I do have a system with systemd-networkd. IPv6AcceptRA is set to 1,
> which is not strictly needed, but I can easily dream up a use case
> where this is
Am 09.03.19 um 21:00 schrieb Santiago Vila:
> For the second part, I'm not familiar with the package, so I'm not
> sure I will be able to get a backtrace of the failing test easily,
> that's why I offer ssh access to a test machine.
It's rather simple, really.
Run apt-get source -b systemd
Am 09.03.19 um 21:50 schrieb Michael Biebl:
> Am 09.03.19 um 21:00 schrieb Santiago Vila:
>> to which I also add these two lines:
> ..> /dev/urandom/dev/random nonerw,bind 0 0
>
> This might very well be the culprit, given that test-stat-util does
Hi Phil
On Sat, 14 Oct 2017 21:56:40 +0100 Philip Hands wrote:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
>
> Hi,
>
> After upgrading to Stretch, the system came up with its NIC named as
> enp1s9, and thus had no working network (since eth0 was configured
> in
Am 09.03.19 um 22:43 schrieb Michael Biebl:
> Am 09.03.19 um 22:27 schrieb Santiago Vila:
>> On Sat, Mar 09, 2019 at 09:59:16PM +0100, Michael Biebl wrote:
>>> Am 09.03.19 um 21:50 schrieb Michael Biebl:
>>>> Am 09.03.19 um 21:00 schrieb Santiago Vila:
>>>
Am 09.03.19 um 23:20 schrieb Santiago Vila:
> On Sat, Mar 09, 2019 at 11:08:15PM +0100, Michael Biebl wrote:
>> Am 09.03.19 um 23:00 schrieb Santiago Vila:
>>> The reason I would still consider this as a bug (with whatever severity
>>> you like) is that symlinking
On Wed, 23 Jan 2019 11:42:57 +1100 Russell Coker
wrote:
> Package: systemd
> Version: 240-4
> Severity: normal
>
> When I have a bogus /etc/crypttab entry (for example when converting an
> encrypted laptop to a virtual machine that's not encrypted) the boot process
> hangs for 90 seconds for no
Control: forwarded -1 https://github.com/systemd/systemd/issues/2739
On Thu, 1 Jun 2017 17:50:27 +0200 Michael Biebl wrote:
> On Mon, 29 May 2017 09:20:52 +0200
> =?UTF-8?B?0JDQvdC00YDQtdC5INCU0L7RhtC10L3QutC+?=
> wrote:
> > Package: systemd
> > Version: 232
>
Hi George
On Fri, 16 Mar 2018 12:31:16 + "George B." wrote:
> Package: systemd
> Version: 238-2
> Followup-For: Bug #807041
>
> tags 807041 - moreinfo
> thanks
>
> Hello,
>
> Tried this again after allowing the recent update to replace my config
> with package default.
>
> Yes, the
Control: tags -1 fixed-upstream patch
Am 10.03.19 um 11:57 schrieb Christian Kastner:
> On 10.03.19 11:07, Michael Biebl wrote:
>> I suppose this is caused by
>>
>> https://github.com/systemd/systemd/commit/a75211421fc9366068e6d9446e8e567246c72feb
>>
>> Could y
Control: reassign -1 im-config
Control: tags -1 - moreinfo
Control: affects -1 + systemd
Am 21.03.19 um 13:51 schrieb Laurent Bonnaud:
> On 20/03/2019 19.39, Michael Biebl wrote:
>
>> Another info that might help give a clue is setting
>> LogLevel=debug in /etc/systemd/user
Am 21.03.19 um 03:58 schrieb Celelibi:
> It looks like it's actually already fixed upstream.
> https://github.com/systemd/systemd/issues/11368
> Fixed by the commit:
> https://github.com/systemd/systemd/commit/39a15c8a8dad26deda140867f03e44a535b7bd8d
This sounds like something that should be
Am 09.04.19 um 21:39 schrieb Roland Fries:
> Hello,
>
> my udev post installation script fails for quite some time now.
>
> I was lazy and hoped that a new udev version would fix that issue, but
> it didn't.
>
> Here is the output:
>
> root@cross-mail:~# LANG=C dpkg -D2 --configure -a
>
On Mon, 8 Apr 2019 01:10:28 +0200 Michael Biebl wrote:
> Control: tags -1 moreinfo
>
> Am 07.04.19 um 18:51 schrieb Andy Ruddock:
> > Package: systemd
> > Severity: critical
> >
> > I'm running Windows 10 (Home edition - up to date) on the desktop, with
>
Am 15.04.19 um 22:18 schrieb Michael Biebl:
> Using debhelper compat level 12, you are able to completely decouple
> dh_installinit and dh_installsystemd which would give you the ability to
> implement what you want afaics.
From debhelper's changelog:
debhelper (12.1) unstable; urgen
Am 18.04.19 um 01:43 schrieb Jul':
> Sorry for the lack of details.
>
> 1) how udev assigns this name?
>
> Since I have no custom udev rule, AFAIK, udev assigns it with the standards
> rules (in "/lib/udev/rules.d/60-persistent-alsa.rules" since it is a sound
> device).
>
This rules file
Control: forwarded -1 https://github.com/systemd/systemd/issues/11571
On 13.04.19 13:35, Vitry David Gilbert wrote:
> Package: systemd-journal-remote
> Version: 241-1~bpo9+1
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate
Control: reassign -1 rkhunter
Am 12.04.19 um 14:53 schrieb Andrew J. Buehler:
> It is possible to whitelist this filename in rkhunter's configuration
> settings,
> but doing so does - however mildly - increase the likelihood that if this
> malware does get a foothold on the system, rkhunter will
Am 11.04.2019 um 22:47 schrieb Michael Biebl:
> Am 11.04.19 um 21:46 schrieb Guido Günther:
>> it took me a while to figure out why rendering got broken in my wayland
>> compositor. It would be great if the change from video to render group
>> could be m
Control: notfound -1 243-1
Control: found -1 241-3
Hi Guido
Am 11.04.19 um 21:46 schrieb Guido Günther:
> Package: udev
> Version: 243-1
I suppose you meant 241-3 here...
> Severity: normal
>
> Hi,
> it took me a while to figure out why rendering got broken in my wayland
> compositor. It
Control: tags -1 moreinfo unreproducible
Doesn't look like libpam-systemd is properly installed
> dbus-update-activation-environment: systemd --user not found, ignoring
> --systemd argument
> cinnamon-session[23689]: WARNING: t+0,00945s: Could not get session id for
> session. Check that
Am 11.03.19 um 19:17 schrieb Markus Koschany:
>
> Am 11.03.19 um 15:51 schrieb Dan Poltawski:
>> Thanks for your responses. One of my colleagues has been looking into this
>> trying to get the bottom of it and we do seem to have identified a memory
>> leak which isn't present on stretch. I note
Control: tags -1 + moreinfo
Am 27.05.19 um 23:03 schrieb Simon Beirnaert:
> Package: systemd
> Version: 232-25+deb9u11
> Severity: normal
>
> Dear Maintainer,
>
>
> Systemd does not seem to consistently put sshd processes under the
> relevant user's slice. I have a user with 10925 sshd
Control: forcemerge 921267 -1
Am 28.05.19 um 00:59 schrieb Kathryn Tolsen:
> Package: systemd
> Version: 241-3
> Severity: Serious
>
> All systemd services are failing to start, best guess is, this is
> related to:
>
> https://github.com/systemd/systemd/issues/11810
This is already fixed in
On Mon, 13 May 2019 16:07:27 +0100 Simon McVittie wrote:
> Control: reassign -1 systemd
>
> On Sun, 18 Nov 2018 at 15:52:39 +0100, Helge Kreutzmann wrote:
> > At the very end of the boot, just after the first user logs in
> > (usually using sddm / X) I get the following messages in my logs:
> >
On Fri, 24 May 2019 09:30:50 +0200 =?utf-8?q?Rapha=C3=ABl_Hertzog?=
wrote:
> Package: systemd
> Version: 241-3
> Severity: serious
> File: systemd-networkd
> User: de...@kali.org
> Usertags: origin-kali
>
> I upgraded an (OVH) dedicated server to Debian buster with systemd 241-3 and
> while it
Hi Dan
Am 29.05.19 um 18:02 schrieb Dan Streetman:
> Package: systemd
> Version: 241-5
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan ubuntu-patch
>
> Dear Maintainer,
>
> 'storage' test fails on some archs/releases trying to modprobe
Am 29.05.19 um 18:49 schrieb Dan Streetman:
> On Wed, May 29, 2019 at 12:35 PM Michael Biebl wrote:
>>
>> Am 29.05.19 um 18:19 schrieb Dan Streetman:
>>> Package: systemd
>>> Version: 241-5
>>> Severity: normal
>>> Tags: patch
>>> Use
On Fri, 24 May 2019 16:48:09 +0200 Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Am 24.05.19 um 16:19 schrieb gilles.nau...@laposte.net:
> > Package: systemd-sysv
> > Version: 241-3
> > Debain Version: buster
> > Severity: important
> >
> >
Am 05.06.19 um 14:03 schrieb Raphael Hertzog:
> Hi,
>
> On Wed, 05 Jun 2019, Michael Biebl wrote:
>> What's the status of this bug?
>
> No progress.
>
>> Can you reproduce it with v242 from experimental?
>
> Yes.
>
>> I guess upstream is wai
Am 04.06.19 um 14:25 schrieb Simon Beirnaert:
> Sorry for the late reply here. Got caught up in other stuff. I did
> some digging around. Set the loglevel with systemd-analyze to debug
> and also added the debug flag to pam_systemd.so.
>
> What I noticed is that on boot, when 5000+ machines try
Am 28.05.19 um 23:35 schrieb Kathryn Tolsen:
> Thank you, and *pokes the D-I team* this means YOU! We need this update
> to 241-4 or 241-5!
241-4 resp. 241-5 waits for an unblock from the release team and the
installer team.
See the request at
Control: tags -1 + moreinfo
Am 07.06.19 um 15:51 schrieb J. Pfennig:
> The man page of telinit/init says (for 'telinit N'):
>
>Change the SysV runlevel. This is translated into an activation request
> for runlevel2.target,
>runlevel3.target, ... and is equivalent to systemctl isolate
>
Control: severity -1 normal
Am 07.06.19 um 00:55 schrieb Adam Borowski:
> Source: systemd
> Version: 241-5
> Severity: critical
> Justification: breaks the whole system
>
>
> When trying to switch to any other init system (and d-i offers no way to
> start with anything but systemd), prerm
Thanks for the patch, Dan.
I see this has already been committed upstream, which is great.
Am 29.05.19 um 17:50 schrieb Dan Streetman:
> +Subject: [PATCH] ask-password: prevent buffer overrow when reading from
^
I assume this is a typo and you
Am 29.05.19 um 18:02 schrieb Dan Streetman:
> Package: systemd
> Version: 241-5
> Severity: normal
> Tags: patch
> User: ubuntu-de...@lists.ubuntu.com
> Usertags: origin-ubuntu eoan ubuntu-patch
>
> Dear Maintainer,
>
> 'storage' test fails on some archs/releases trying to modprobe and/or rmmod
Am 06.06.19 um 17:13 schrieb W. Martin Borgert:
> Source: systemd
> Version: 241-5
>
> Please change the build dependency
>
> python3-evdev ,
>
> to
>
> python3-evdev:native ,
>
> Only with that change I could cross-compile the package. TIA!
Could you give a bit more details on why
Am 06.06.19 um 22:16 schrieb W. Martin Borgert:
> On 2019-06-06 19:59, Michael Biebl wrote:
>> Could you give a bit more details on why this is necessary and e.g. why
>> python3-pyparsing does not need :native?
>
> I'm not even sure myself, but I try my best :-)
>
>
Control: reassign -1 ifupdown
Am 25.06.19 um 22:47 schrieb Joshua Hudson:
> I have attached a copy of /etc/network/interfaces. We're now waiting
> for another recurrence.
>
/etc/network/interfaces is not a systemd config file, so it seems your
network interface is managed by ifupdown.
So I'm
Am 25.06.19 um 22:51 schrieb Michael Biebl:
> Dan, could you submit your patch as merge request?
Btw, we use gbp-dch style commit messages.
E.g. Debian bugs are closed by adding a
Closes: #929730
line to the git commit message.
http://honk.sigxcpu.org/projects/git-buildpackage/manual-h
Control: severity -1 important
Hi Raphael
On Wed, 19 Jun 2019 22:33:21 +0200 Michael Biebl wrote:
> Hi Raphael,
>
> On Tue, 11 Jun 2019 15:51:14 +0200 Raphael Hertzog
> wrote:
> > Hi,
> >
> > On Wed, 05 Jun 2019, Michael Biebl wrote:
> > > systemd-netwo
[please always CC the bug report]
Am 17.06.2019 um 18:54 schrieb Joshua Hudson:
> systemd-networkd is active. NetworkManager is not.
Well, the systemd-analyze dump you attached to this bug report shows
systemd-networkd.service as inactive. And you also said this:
>> Am 17.06.2019 um 18:35
Control: tags -1 + moreinfo
Am 17.06.2019 um 18:35 schrieb Joshua Hudson:
> Package: systemd
> Version: 241-5
> Severity: important
>
> This is in fact a corporate server; real email is jhud...@cedaron.com
> but if I try to use that source for reportbug, nothing goes through. :(
>
> Dear
401 - 500 of 1843 matches
Mail list logo
