Processed: Re: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Processing control commands: > clone -1 -2 Bug #856985 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Bug 856985 cloned as bug 857159 > retitle -2 systemd-cron: stop cron-update.path before removal Bug #857159 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Changed Bug title to 'systemd-cron: stop cron-update.path before removal' from 'systemd: Uninstalling systemd-cron hangs/crashes systemd'. > reassign -2 systemd-cron 1.3.1+ds1-2 Bug #857159 [systemd] systemd-cron: stop cron-update.path before removal Bug reassigned from package 'systemd' to 'systemd-cron'. No longer marked as found in versions systemd/215-17+deb8u6. No longer marked as fixed in versions systemd/232-1. Bug #857159 [systemd-cron] systemd-cron: stop cron-update.path before removal Marked as found in versions systemd-cron/1.3.1+ds1-2. > found -1 215-1 Bug #856985 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Marked as found in versions systemd/215-1. > fixed -1 232-1 Bug #856985 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Ignoring request to alter fixed versions of bug #856985 to the same values previously set -- 856985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856985 857159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Control: clone -1 -2 Control: retitle -2 systemd-cron: stop cron-update.path before removal Control: reassign -2 systemd-cron 1.3.1+ds1-2 Control: found -1 215-1 Control: fixed -1 232-1 On Tue, Mar 7, 2017 at 11:32 PM, Andreas Bombe wrote: > On Tue, Mar 07, 2017 at 10:05:38AM +0100, Michael Biebl wrote: >> Andreas, can you confirm that stopping the cron-update.path unit prior >> to the removal avoids the crash? You will have to edit >> /lib/systemd/system/cron-update.path to remove >> RefuseManualStart=true >> RefuseManualStop=true > > I did: > - install systemd-cron again > - remove those lines > - systemctl daemon-reload (to pick up these changes) > - systemctl stop cron-update.path > - installed cron at the same time systemd-cron is uninstalled > > Now I have seen no crash or other problems. I have cloned this bug to track that fix separately from the systemd issue. It is a good idea to stop the path unit before the removal anyway, as it makes no sense to retrigger systemd-cron if it will be removed. The systemd crash on the other hand has been fixed in 232. Michael found the fixing commit here: https://github.com/systemd/systemd/commit/47fffb35 Unfortunately, that does not apply cleanly to 215, so some backporting will be needed. -- Saludos, Felipe Sateler ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: fixed 857159 in 1.5.2-1
Processing commands for cont...@bugs.debian.org: > fixed 857159 1.5.2-1 Bug #857159 [systemd-cron] systemd-cron: stop cron-update.path before removal Marked as fixed in versions systemd-cron/1.5.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 857159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Hi, The path activation is pulled-in like the rest by cron.target, so stopping cron.target is enough to also stop cron-update.path . Back then, this commit was enough to solve this bug in v1.5.2-1; well maybe having a more recent debhelper/dh_systemd available helped too. https://anonscm.debian.org/cgit/collab-maint/systemd-cron.git/commit/?id=afacd3645349530dd447ff88bd46c985479279e2 Alexandre 2017-03-07 11:29 GMT+01:00 Michael Biebl : >> I remember code is there but needs a sponsor: >> >> https://anonscm.debian.org/cgit/collab-maint/systemd-cron.git/commit/?h=jessie&id=06f38df6e42bf60f44ce4ceb8cf752c819ea92da >> > > Disabling path activation on remove looks like a more robust fix to me. ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Am 08.03.2017 um 15:30 schrieb Alexandre Detiste: > Hi, > > The path activation is pulled-in like the rest by cron.target, > so stopping cron.target is enough to also stop cron-update.path . No it is not. Starting cron.target starts cron-update.path, but stopping cron.target does not stop cron-update.path. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: notfixed 857159 in 1.5.2-1
Processing commands for cont...@bugs.debian.org: > notfixed 857159 1.5.2-1 Bug #857159 [systemd-cron] systemd-cron: stop cron-update.path before removal No longer marked as fixed in versions systemd-cron/1.5.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 857159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Re: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
I removed the fixed tag. systemd-cron *does* stop cron.target in prerm in recent versions, but stopping cron.target *does not* stop cron-update.path. Contrary to the other units, cron-update.path is not marked as PartOf=cron.target. And due to the use of RefuseManualStart=yes RefuseManualStop=yes the cron-update.path unit can not be controlled individually via systemctl. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: bug 857159 is not forwarded
Processing commands for cont...@bugs.debian.org: > notforwarded 857159 Bug #857159 [systemd-cron] systemd-cron: stop cron-update.path before removal Unset Bug forwarded-to-address > thanks Stopping processing here. Please contact me if you need assistance. -- 857159: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=857159 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#857159: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Hi, > systemd-cron *does* stop cron.target in prerm in recent versions, but > stopping cron.target *does not* stop cron-update.path. > > Contrary to the other units, cron-update.path is not marked as > PartOf=cron.target. So could it be enough to just add this "PartOf=cron.target" to cron-update.path too ? > And due to the use of > RefuseManualStart=yes > RefuseManualStop=yes This has been cargo culted & could also be changed, but I prefer the first option (the .target that controls everything). Alexandre Detiste ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#857159: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Am 08.03.2017 um 20:12 schrieb Alexandre Detiste: > Hi, > >> systemd-cron *does* stop cron.target in prerm in recent versions, but >> stopping cron.target *does not* stop cron-update.path. >> >> Contrary to the other units, cron-update.path is not marked as >> PartOf=cron.target. > > So could it be enough to just add this "PartOf=cron.target" > to cron-update.path too ? I think so, yes. Unless upstream had a specific reason not to do it this way. I notice that for the other units it also uses Requires, but Wants for cron-update.path >> And due to the use of >> RefuseManualStart=yes >> RefuseManualStop=yes > > This has been cargo culted & could also be changed, > but I prefer the first option (the .target that controls everything). I don't see a good reason why the individual units should not be stoppable/startable by the admin, so I'd probably drop it for all the units. Again, ask upstream. Maybe there is a good reason for this. -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#857194: Add check for obsolete systemd BindTo= option
Package: lintian
Version: 2.5.50.1
Severity: wishlist
Tags: patch
Hi,
while filing [1], I thought it might be a good idea to turn that into a
lintian check.
Please find attached patch for that.
Regards,
Michael
[1]
https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintainers@lists.alioth.debian.org;tag=obsolete-bind-to
-- System Information:
Debian Release: 9.0
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.9.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages lintian depends on:
ii binutils 2.28-2
ii bzip2 1.0.6-8.1
ii diffstat 1.61-1+b1
ii file 1:5.29-3
ii gettext 0.19.8.1-2
ii intltool-debian 0.35.0+20060710.4
ii libapt-pkg-perl 0.1.30
ii libarchive-zip-perl 1.59-1
ii libclass-accessor-perl0.34-1
ii libclone-perl 0.38-2+b1
ii libdigest-sha-perl5.96-1+b1
ii libdpkg-perl 1.18.23
ii libemail-valid-perl 1.202-1
ii libfile-basedir-perl 0.07-1
ii libipc-run-perl 0.94-1
ii liblist-moreutils-perl0.416-1+b1
ii libparse-debianchangelog-perl 1.2.0-12
ii libperl5.24 [libdigest-sha-perl] 5.24.1-1
ii libtext-levenshtein-perl 0.13-1
ii libtimedate-perl 2.3000-2
ii liburi-perl 1.71-1
ii libyaml-libyaml-perl 0.63-2
ii man-db2.7.6.1-2
ii patchutils0.3.4-2
ii perl 5.24.1-1
ii t1utils 1.39-2
ii xz-utils 5.2.2-1.2+b1
Versions of packages lintian recommends:
ii dpkg 1.18.23
ii libautodie-perl 2.29-2
ii libperlio-gzip-perl 0.19-1+b2
ii perl 5.24.1-1
ii perl-modules-5.24 [libautodie-perl] 5.24.1-1
Versions of packages lintian suggests:
pn binutils-multiarch
ii dpkg-dev 1.18.23
ii libhtml-parser-perl3.72-3
ii libtext-template-perl 1.46-1
-- no debconf information
-- debsums errors found:
debsums: changed file /usr/share/lintian/checks/systemd.desc (from lintian
package)
debsums: changed file /usr/share/lintian/checks/systemd.pm (from lintian
package)
>From d390729926ba5ae34fe2f7132ae7b10608f55ff1 Mon Sep 17 00:00:00 2001
From: Michael Biebl
Date: Wed, 8 Mar 2017 20:26:21 +0100
Subject: [PATCH] c/systemd: Check for obsolete BindTo= option
The BindTo= option has been deprecated in favour of BindsTo= which
should be used instead.
See
https://github.com/systemd/systemd/commit/7f2cddae09fd2579ae24434df577bb5e5a157d86
---
checks/systemd.desc | 8
checks/systemd.pm | 3 +++
2 files changed, 11 insertions(+)
diff --git a/checks/systemd.desc b/checks/systemd.desc
index d4aea020a..0071c1a58 100644
--- a/checks/systemd.desc
+++ b/checks/systemd.desc
@@ -34,6 +34,14 @@ Info: The systemd service file refers to an obsolete target.
example, declaring After=syslog.target is unnecessary by now because
syslog is socket-activated and will therefore be started when needed.
+Tag: systemd-service-file-refers-to-obsolete-bindto
+Severity: normal
+Certainty: certain
+Info: The systemd service file refers to the obsolete BindTo= option.
+ .
+ The BindTo= option has been deprecated in favour of
+ BindsTo= which should be used instead.
+
Tag: systemd-no-service-for-init-script
Severity: serious
Certainty: certain
diff --git a/checks/systemd.pm b/checks/systemd.pm
index a7ea9cd29..0b92e19ab 100644
--- a/checks/systemd.pm
+++ b/checks/systemd.pm
@@ -200,6 +200,9 @@ sub check_systemd_service_file {
tag 'systemd-service-file-refers-to-obsolete-target', $file, $_
for @obsolete;
+tag 'systemd-service-file-refers-to-obsolete-bindto', $file,
+ if extract_service_file_values($file, 'Unit', 'BindTo');
+
if (not $file->is_symlink or $file->link ne '/dev/null') {
tag 'systemd-service-file-missing-documentation-key', $file,
unless extract_service_file_values($file, 'Unit', 'Documentation',1);
--
2.11.0
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Processed: Re: Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Processing control commands: > tags -1 + patch Bug #856985 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Added tag(s) patch. -- 856985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Bug#856985: systemd: Uninstalling systemd-cron hangs/crashes systemd
Control: tags -1 + patch Am 08.03.2017 um 14:48 schrieb Felipe Sateler: > https://github.com/systemd/systemd/commit/47fffb35 > > Unfortunately, that does not apply cleanly to 215, so some backporting > will be needed. Cherry-picking https://github.com/systemd/systemd/commit/96fb8242 https://github.com/systemd/systemd/commit/47fffb35 + some minor changes to log_* applies cleanly on top of v215 and fixes the crash. Both patches attached -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? From d8d0306db9d91083d7002b3c7d95b2bcd1466497 Mon Sep 17 00:00:00 2001 From: Lennart Poettering Date: Thu, 21 Aug 2014 18:50:42 +0200 Subject: [PATCH 1/2] service: allow services of Type=oneshot that specify no ExecStart= commands This is useful for services that simply want to run something on shutdown, but not at bootup. They should only set ExecStop= but leave ExecStart= unset. (cherry picked from commit 96fb8242cc1ef6b0e28f6c86a4f57950095dd7f1) --- man/systemd.service.xml | 44 +++- src/core/service.c | 39 +-- 2 files changed, 56 insertions(+), 27 deletions(-) diff --git a/man/systemd.service.xml b/man/systemd.service.xml index 013125026..0045689c6 100644 --- a/man/systemd.service.xml +++ b/man/systemd.service.xml @@ -139,9 +139,10 @@ If set to simple (the default -value if neither +if neither Type= nor -BusName= are +BusName=, but +ExecStart= are specified), it is expected that the process configured with ExecStart= is the @@ -177,13 +178,17 @@ exits. Behavior of -oneshot is similar -to simple; however, -it is expected that the process has to +oneshot is similar to +simple; however, it +is expected that the process has to exit before systemd starts follow-up units. RemainAfterExit= is particularly useful for this type -of service. +of service. This is the implied +default if neither +Type= or +ExecStart= are +specified. Behavior of dbus is similar to @@ -313,22 +318,27 @@ When Type is not oneshot, only one -command may be given. When +command may and must be given. When Type=oneshot is -used, more than one command may be -specified. Multiple command lines may -be concatenated in a single directive -by separating them with semicolons -(these semicolons must be passed as -separate words). Alternatively, this -directive may be specified more than -once with the same effect. -Lone semicolons may be escaped as +used, none or more than one command +may be specified. Multiple command +lines may be concatenated in a single +directive by separating them with +semicolons (these semicolons must be +passed as separate +words). Alternatively, this directive +may be specified more than once with +the same effect. Lone semicolons may +be escaped as \;. If the empty string is assigned to this option, the list of commands to start is reset, prior assignments of this option will -have no effect. +have no effect. If no +ExecStart= is +
Bug#809069: logind sometimes blocks input to X after VT switch
Hi Ben On Sat, 26 Dec 2015 22:44:45 + Ben Hutchings wrote: > Package: systemd > Version: 228-2 > Severity: important > > After switching between a text console (VT 1) and X (VT 7) a few > times, I found that keyboard and mouse input no longer worked in X. > The system log showed this: > > [switching to VT 1] > > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: > Suspending AIGLX clients for VT switch > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 226:0 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:69 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:64 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:66 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:72 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:65 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:68 > Dec 26 22:28:41 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:71 > > [switching to VT 7] > > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 226:0 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) AIGLX: > Resuming AIGLX clients after VT switch > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) intel(0): > switch to mode 1600x900@60.0 on LVDS1 using pipe 0, position (0, 0), rotation > normal, reflection none > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:69 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:64 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:66 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD > keymap compiler (xkbcomp) reports: > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Meta_R added to symbol map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Meta_L added to symbol map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Key added to map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from > xkbcomp are not fatal to the X server > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:72 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: The XKEYBOARD > keymap compiler (xkbcomp) reports: > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Meta_R added to symbol map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Meta_L added to symbol map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > Error: > Key added to map for multiple modifiers > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: > > Using Mod4, ignoring Mod1. > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: Errors from > xkbcomp are not fatal to the X server > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:65 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (--) synaptics: > SynPS/2 Synaptics TouchPad: touchpad found > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:68 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got resume for 13:71 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 226:0 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:69 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:64 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for 13:66 > Dec 26 22:29:06 deadeye /usr/lib/gdm3/gdm-x-session[2280]: (II) > systemd-logind: got pause for
Processed: tagging 856985
Processing commands for cont...@bugs.debian.org: > tags 856985 + pending Bug #856985 [systemd] systemd: Uninstalling systemd-cron hangs/crashes systemd Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 856985: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856985 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
