On 10/03/2019 11:53, Michael Biebl wrote:
Hi George
Have you filed such an upstream bug report?
https://github.com/systemd/systemd/issues/2346
It was closed though. :(
Thanks,
George
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintain
I just uploaded (to experimental) a package policy-rcd-declarative,
which ships a policy-rc.d script that can be configured through static
files, in an attempt to address some of the issues pointed out in this
bug report.
It's not yet ready for prime time (hence the upload to experimental
rather t
On Mon, 2019-03-11 at 00:20 +0100, Michael Biebl wrote:
> 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/
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 t
On Sun, 2019-03-10 at 19:25 +0100, Michael Biebl wrote:
> Hi Mario,
>
>
> On Fri, 6 Jul 2018 12:41:37 + wrote:
[...]
> > Yes I could see two swap partitions causing the wrong one to be picked.
> > It's trying to select the bigger of the two.
> >
> > If they don't match the one you're puttin
Your message dated Sun, 10 Mar 2019 22:57:30 +0100
with message-id <332ae5e5-3728-f5f9-d49f-e0b45fbb3...@debian.org>
and subject line Re: udev shows too unspecific error messages
has caused the Debian Bug report #670843,
regarding udev shows too unspecific error messages
to be marked as done.
This
Your message dated Sun, 10 Mar 2019 22:55:22 +0100
with message-id <5540b0ea-4cf9-c2b1-037a-aa3eab959...@debian.org>
and subject line Re: udev: incorrect documentation in
/lib/udev/hwdb.d/60-keyboard.hwdb
has caused the Debian Bug report #788499,
regarding udev: "udevadm trigger /dev/input/event*"
Your message dated Sun, 10 Mar 2019 22:55:22 +0100
with message-id <5540b0ea-4cf9-c2b1-037a-aa3eab959...@debian.org>
and subject line Re: udev: incorrect documentation in
/lib/udev/hwdb.d/60-keyboard.hwdb
has caused the Debian Bug report #788499,
regarding udev: incorrect documentation in /lib/ude
Processing control commands:
> tag -1 pending
Bug #924199 [udev] Removing an LVM snapshot logs `dmsetup info` error
Added tag(s) pending.
--
924199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
__
Processing control commands:
> tag -1 pending
Bug #921280 [systemd] systemd-cgtop no longer shows memory usage
Added tag(s) pending.
--
921280: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921280
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
I tried the fix_db.pl script, there was no output. Here is the only
relevant difference:
--- debconf.old/config.datâ–¸-2019-03-10 18:43:37.265483165 +0100
+++ debconf/config.datâ–¸-2019-03-10 18:43:41.261085496 +0100
@@ -1151,7 +1151,7 @@
Name: libpam-modules/disable-screensaver
Template: lib
On Sun, Mar 10, 2019 at 12:12:57AM +0100, Michael Biebl wrote:
> Is this still an issue with 241-1 from unstable?
Sorry, this is a productive system, I cannot just do upgrades to
unstable in that network setup to check wether a bug reported and worked
around nearly two years ago was fixed upstream
Processing commands for cont...@bugs.debian.org:
> tags 921280 - moreinfo
Bug #921280 [systemd] systemd-cgtop no longer shows memory usage
Removed tag(s) moreinfo.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
921280: https://bugs.debian.org/cgi-bin/bugreport.cg
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: systemd: systemctl hibernate: una
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 again pondering whether I should mask systemd-timesyncd
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 regularly are
>> otherwise up
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 regularly are
> otherwise up for a nasty experience.
> You might consider asking the se
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 upda
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
systemctl status certbot.timer
journalctl -u certb
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
>>
>> The output of `systemctl show certbo
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
> https://bugs.debian.org/cgi-bin/bu
Hi,
(Replying from a d-i point of view.)
Michael Biebl (2019-03-10):
> 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
>
> * journald: fix assertion failure on journal
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
https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=922031;filename=systemctl-show-certbot.ti
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 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 debian-lts team.
> Wi
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 the issue, between the update from
0.10~ to 0.28.0.1~deb9u1, the syst
On Saturday, March 9, 2019 6:10:16 PM EDT Michael Biebl wrote:
> 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
>
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
* journal
Processing control commands:
> tag -1 pending
Bug #918400 [systemd] systemd: Shell style globs do not work as expected with
the tmpfiles.d 'e' type
Added tag(s) pending.
--
918400: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918400
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Processing control commands:
> tag -1 pending
Bug #917122 [systemd] systemd can not start without name_to_handle_at option
Added tag(s) pending.
--
917122: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Processing control commands:
> tag -1 pending
Bug #916880 [systemd] Journald crashes in log_assert_failed()
Added tag(s) pending.
--
916880: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916880
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
__
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 proble
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 you check if
>> https://github.com/sys
Processing control commands:
> tags -1 fixed-upstream patch
Bug #924199 [udev] Removing an LVM snapshot logs `dmsetup info` error
Added tag(s) fixed-upstream and patch.
--
924199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924199
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Your message dated Sun, 10 Mar 2019 12:08:40 +0100
with message-id <662bf90b-556d-3ba7-baeb-bde63e092...@debian.org>
and subject line Re: systemctl disable --now fails for aliased D-Bus services
has caused the Debian Bug report #804438,
regarding systemctl disable --now fails for aliased D-Bus serv
On 10.03.19 11:07, Michael Biebl wrote:
> I suppose this is caused by
>
> https://github.com/systemd/systemd/commit/a75211421fc9366068e6d9446e8e567246c72feb
>
> Could you check if
> https://github.com/systemd/systemd/commit/3c37dadf627677eef62fcfc0c0f07cc67c748a9e
> helps?
Yes, that solved the i
Your message dated Sun, 10 Mar 2019 11:54:16 +0100
with message-id <6e2483f2-0dc8-1862-bb30-ab8559c14...@debian.org>
and subject line Re: systemd: Unable to disable mount of /run/user/$something
has caused the Debian Bug report #806885,
regarding systemd: Unable to disable mount of /run/user/$somet
Am 10.03.19 um 10:41 schrieb Christian Kastner:
> Package: udev
> Version: 241-1
> Severity: minor
>
> Removing an LVM snapshot logs an error. Steps to reproduce:
>
> # lvcreate --snapshot --size 500M --name testsnap $SOMEVOLUME
> # lvremove --force testsnap
>
> # journalctl -n 1
>
Package: udev
Version: 241-1
Severity: minor
Removing an LVM snapshot logs an error. Steps to reproduce:
# lvcreate --snapshot --size 500M --name testsnap $SOMEVOLUME
# lvremove --force testsnap
# journalctl -n 1
systemd-udevd[21406]: Process '/sbin/dmsetup info -j 254 -m 14 -c
39 matches
Mail list logo
