Bug#871490: mention how to force listing of /var/lib/systemd/coredump

> "MB" == Michael Biebl writes: MB> coredumpctl afaik uses the journal to look up coredump entries. MB> Do the coredumps show up in the journal? It seems so: /var/log/syslog.6.gz:Aug 9 00:04:56 jidanni6 systemd-coredump[1801]: Process 1797 (epiphany) of user 1000 dumped core... MB> Have y

Bug#868269: Regression from jessie to stretch in handling of %u, %U, %s, and %h

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: normal > > > > I'm not suggesting a change here, but I do think this could use > > documentation in the release notes a

Bug#871490: mention how to force listing of /var/lib/systemd/coredump

On Tue, 08 Aug 2017 18:55:06 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Package: systemd-coredump > Version: 234-2 > Severity: wishlist > File: /usr/share/man/man1/coredumpctl.1.gz > > Man page says > >It's worth noting that different restrictions apply to data saved >

Bug#739051: systemd: does not align the OK printouts

Control: tags -1 + unreproducible On Thu, 22 Dec 2016 10:59:13 +0100 Salvo Tomaselli wrote: > Still there, for a short while. Then it resets and looks normal. But it > then shuts down so i don't know if they are the same lines or new ones. I was never able to reproduce the issue. Can you provide

Processed: Re: systemd: does not align the OK printouts

Processing control commands: > tags -1 + unreproducible Bug #739051 [systemd] systemd: does not align the OK printouts Added tag(s) unreproducible. -- 739051: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#850169: marked as done (systemd should Provide: time-daemon)

Your message dated Sun, 10 Sep 2017 01:57:11 +0200 with message-id <82c1194c-cf6f-e0e5-3297-2d10045e2...@debian.org> and subject line Re: Bug#850169: systemd should Provide: time-daemon has caused the Debian Bug report #850169, regarding systemd should Provide: time-daemon to be marked as done. Th

Bug#850436: marked as done (mounting var at boot: Mount point is not empty)

Your message dated Sun, 10 Sep 2017 01:51:17 +0200 with message-id <538baa77-2f87-57f7-b239-89ba37f1c...@debian.org> and subject line Re: Bug#850436: mounting var at boot: Mount point is not empty has caused the Debian Bug report #850436, regarding mounting var at boot: Mount point is not empty to

Bug#866624: marked as done (resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found.)

Your message dated Sun, 10 Sep 2017 01:48:17 +0200 with message-id <79c890b3-2748-39a1-5900-abd796deb...@debian.org> and subject line Re: Bug#866624: resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found. has caused the Debian Bug report #866624, regarding resolve call failed:

Processed: bug 867902 is forwarded to https://github.com/systemd/systemd/issues/6787

Processing commands for cont...@bugs.debian.org: > forwarded 867902 https://github.com/systemd/systemd/issues/6787 Bug #867902 [systemd] systemd: don't try to execute non-executables under /lib/systemd/system-sleep/ Changed Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/6

Processed: bug 867902 is forwarded to man systemd-suspend.service says:

Processing commands for cont...@bugs.debian.org: > forwarded 867902 man systemd-suspend.service says: Bug #867902 [systemd] systemd: don't try to execute non-executables under /lib/systemd/system-sleep/ Set Bug forwarded-to-address to 'man systemd-suspend.service says:'. > thanks Stopping process

Bug#868269: Regression from jessie to stretch in handling of %u, %U, %s, and %h

On Thu, 13 Jul 2017 15:09:29 -0700 Josh Triplett wrote: > Package: systemd > Version: 233-10 > Severity: normal > > I'm not suggesting a change here, but I do think this could use > documentation in the release notes and NEWS.Debian file. > > Commit 79413b673b45adc98dfeaec882bbdda2343cb2f9 in sy

Bug#864456: marked as done (missing powerpc clone() syscall def)

Your message dated Sun, 10 Sep 2017 01:38:46 +0200 with message-id <83a58e0b-d535-8e47-c3b9-93aa4cb1f...@debian.org> and subject line Re: powerpc is the only remaining one with warning has caused the Debian Bug report #864456, regarding missing powerpc clone() syscall def to be marked as done. Thi

Bug#869144: marked as done (systemd: Setting PATH with environment.d does not work)

Your message dated Sun, 10 Sep 2017 01:35:50 +0200 with message-id and subject line Re: Bug#869144: systemd: Setting PATH with environment.d does not work has caused the Debian Bug report #869144, regarding systemd: Setting PATH with environment.d does not work to be marked as done. This means t

Processed: bug 871252 is forwarded to https://github.com/systemd/systemd/issues/6529

Processing commands for cont...@bugs.debian.org: > forwarded 871252 https://github.com/systemd/systemd/issues/6529 Bug #871252 [systemd] systemd: Crypttab with Dependency on Keyfile Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/6529'. > thanks Stopping processing here

Processed: bug 869144 is forwarded to https://github.com/systemd/systemd/issues/6414

Processing commands for cont...@bugs.debian.org: > forwarded 869144 https://github.com/systemd/systemd/issues/6414 Bug #869144 [systemd] systemd: Setting PATH with environment.d does not work Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/6414'. > thanks Stopping proce

Bug#871641: marked as done (udev: USB serial device wrongly tagged as pci in /dev/serial/by-id/)

Your message dated Sun, 10 Sep 2017 01:32:29 +0200 with message-id <7b741b70-b632-eb01-fa3a-61593dedb...@debian.org> and subject line Re: Bug#871641: udev: USB serial device wrongly tagged as pci in /dev/serial/by-id/ has caused the Debian Bug report #871641, regarding udev: USB serial device wron

systemd_234-3~bpo9+1_source.changes ACCEPTED into stretch-backports

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sun, 10 Sep 2017 00:27:07 +0200 Source: systemd Binary: systemd systemd-sysv systemd-container systemd-journal-remote systemd-coredump systemd-tests libpam-systemd libnss-myhostname libnss-mymachines libnss-resolve li

Processing of systemd_234-3~bpo9+1_source.changes

systemd_234-3~bpo9+1_source.changes uploaded successfully to localhost along with the files: systemd_234-3~bpo9+1.dsc systemd_234-3~bpo9+1.debian.tar.xz systemd_234-3~bpo9+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Bug#856924: marked as done (systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated)

Your message dated Sat, 9 Sep 2017 10:08:51 -0300 with message-id and subject line Re: Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated has caused the Debian Bug report #856924, regarding systemd: on WorkingDirectory not existing, some weird log abo

Bug#856924: systemd: on WorkingDirectory not existing, some weird log about CHROOT is generated

On Mon, 6 Mar 2017 09:48:11 -0300 Felipe Sateler wrote: > On Mon, Mar 6, 2017 at 7:32 AM, Salvo Tomaselli wrote: > > WorkingDirectory=/does/not/exist > > > > And when I try to start it I obtain > > lala.service: Failed at step CHROOT spawning /bin/sh: No such file or > > directory > > > > whic

Bug#855209: marked as done (systemd ignores configuration for getty when switching and autostarting a new vt)

Your message dated Sat, 9 Sep 2017 11:40:42 +0200 with message-id and subject line Re: Bug#855209: systemd ignores configuration for getty when switching and autostarting a new vt has caused the Debian Bug report #855209, regarding systemd ignores configuration for getty when switching and autos