Your message dated Mon, 22 Jun 2015 17:43:25 -0300
with message-id
<caafdzj97skkvmvok6fiaaemfa9fnqtgjety_pc1azyebsgc...@mail.gmail.com>
and subject line Re: Bug#776863: Bug#776859: systemd-cron: uninstalling package
dumps core and seemingly disturbs systemd
has caused the Debian Bug report #776863,
regarding systemctl daemond-reload is racy
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
776863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=776863
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd-cron
Version: 1.3.1+ds1-2
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
When uninstalling systemd-cron (replacing it with cron to allow
installation of backintime-gnome) from within an X11 session, I
suddently found myself at the console (as if I'd pressed CTRL+ALT+F1 -
not sure what that is called in techincal terms). Luckily my X11
session hadn't died, I could switch back again, and then saw these
oddities at my virtual terminal still ongoing with the package
replacement:
Failed to execute operation: Forbindelsen brudt i den anden ende
Broadcast message from systemd-journ...@bastian.jones.dk (Mon 2015-02-02
17:17:34 CET):
systemd[1]: Caught <ABRT>, dumped core as pid 15971.
Broadcast message from systemd-journ...@bastian.jones.dk (Mon 2015-02-02
17:17:34 CET):
systemd[1]: Freezing execution.
Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
Failed to execute operation: Activation of org.freedesktop.systemd1 timed out
After about a minute of seeming hanging the APT processing, it continued
but package removal failed and thus installation of cron failed too.
I guess failure to remove a non-essential package is at least important.
- Jonas
- -- System Information:
Debian Release: 8.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.14-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQF8BAEBCgBmBQJUz6cYXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ3NjQ4ODQwMTIyRTJDNTBFQzUxRDQwRTI0
RUMxQjcyMjM3NEY5QkQ2AAoJEE7BtyI3T5vWRTsIAK53hqOQOSc3Y6JOwF3ftvEi
SElT3xZKB+V0QsBib4Otvuf627ic4XLSOJ0R2fd4AGeANHBslIuMql2ZVxH2JOu+
ILwZoIYAqnjYZqPAKY/10PWWWm6nuB6dhi0e+vz6RMMEVn7ZrColu86YrycdKHXn
hmfzuSVq9O8vDXJc6hXZ15K+d69UeBuP9lQDbeH1MlsO5X4wc0mHEoCs5ZxSZL7N
WJ4FbMMoatYbOFzTliYkZR77DwZoo6IZJc53Rdm1bLbIPp+cbSVhQ3uSFhFi4fXp
z1aR73AhiS8LT1Om9hlb2vnZtdSrzpC36Gmla7bsWw1J8fH6tU8htsMppux4NQw=
=hKu/
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
On Fri, 20 Mar 2015 10:07:28 +0100 Michael Biebl <bi...@debian.org> wrote:
> Am 20.03.2015 um 09:59 schrieb Jonas Smedegaard:
> > Quoting Michael Biebl (2015-03-20 09:07:37)
> >> Am 20.03.2015 um 09:01 schrieb Jonas Smedegaard:
> >>
> >>> Quoting Michael Biebl (2015-03-20 06:38:10)
> >>
> >>>> Atm, we don't have nearly enough information to pursue this further.
> >>>
> >>> Sorry, it did not occur to me to preserve the core file: If it was in
> >>> fact dumped at all, I guess it got cleaned out automatically at next
> >>> boot - in any case it there's no core file by now :-(
> >>>
> >>> I have no suggestions how to continue from here - if you don't either
> >>> then I guess there's no other option than filing it as a mystery.
> >>
> >> Ok. I guess I'll leave this bug open for another month or so, just in
> >> case someone else encounters a similar problem and want's to
> >> follow-up. If not, I'm going to close it.
> >
> > Sounds sensible.
> >
> > ...but what you then did was close it now, not wait?
> >
> > (I guess you first changed to -done, then came up with the better plan
> > while writing, but forgot to revert to simply posting to the bugreport)
>
> Right, I forgot to drop the -done.
> But I've already re-opened again in the mean time.
I guess it's ok to close this now, so I'm doing it.
Saludos
--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
