Processed: Re: Bug#884595: powermanga: Controls didn't work

Processing control commands: > tags -1 + moreinfo Bug #884595 [udev] udev creates a fake joystick device for MS mouse Ignoring request to alter tags of bug #884595 to the same tags previously set -- 884595: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884595 Debian Bug Tracking System

Bug#869354: systemd: Overwrites local config without warning

On Sat, 22 Jul 2017 16:39:26 +0100 Nick wrote: > The upgrade today appears to have overwritten the target of the symlink > /etc/systemd/system/getty.target.wants/getty@tty1.service > from my local target under /etc (which does autologin) > to the package-provided file

Processed: Re: systemd: Segfault while adding a new job

Processing control commands: > tags -1 + moreinfo Bug #787473 [systemd] systemd: Segfault while adding a new job Added tag(s) moreinfo. -- 787473: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787473 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#787473: systemd: Segfault while adding a new job

Control: tags -1 + moreinfo Hi Tino, I'm looking through old bug reports. A lot has changed since v215, so it would be great if you can test this with v232 from current stable or event better v235 from testing and report back, if the issue is still reproducible. Regards, Michael -- Why is it

Processed: tagging 881310, tagging 881823, tagging 883380, tagging 883407, tagging 882270, tagging 882245 ...

Processing commands for cont...@bugs.debian.org: > tags 881310 + pending Bug #881310 [systemd-container] systemd-container: systemd-nspawn containers get non-functioning /etc/resolv.conf Added tag(s) pending. > tags 881823 + pending Bug #881823 [src:systemd] systemd-networkd: Fails to start with

Processed: bug 881823 is forwarded to https://github.com/systemd/systemd/pull/7030

Processing commands for cont...@bugs.debian.org: > forwarded 881823 https://github.com/systemd/systemd/pull/7030 Bug #881823 [src:systemd] systemd-networkd: Fails to start with 'Could not enumerate rules: Operation not supported' Set Bug forwarded-to-address to

Processed: Re: Bug#884506: systemd: "systemd-analyze plot" fails for root

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/7667 Bug #884506 [systemd] systemd: "systemd-analyze plot" fails for root Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7667'. -- 884506:

Bug#884506: systemd: "systemd-analyze plot" fails for root

Control: forwarded -1 https://github.com/systemd/systemd/issues/7667 Am 15.12.2017 um 23:24 schrieb Rainer Kupke: > Package: systemd > Version: 235-3 > Severity: normal > > Dear Maintainer, > > A long time ago I set up a cronjob to mail the output of "systemd-analyze > plot" > (as root) after

Processed: bug #884319

Processing commands for cont...@bugs.debian.org: > reassign 884319 openvswitch-switch Bug #884319 [systemd] Networking shutdown before NFS unmount on shutdown or reboot Bug reassigned from package 'systemd' to 'openvswitch-switch'. No longer marked as found in versions systemd/235-2. Ignoring

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

On 2017-12-15 20:28:28 (+0100), Michael Biebl wrote: > Am 15.12.2017 um 20:26 schrieb Peter 'p2' De Schrijver: > > On 2017-12-15 20:23:11 (+0100), Michael Biebl wrote: > > >> Could it be a problem that > >> > >> [ OK ] Stopped LSB: Open vSwitch

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 15.12.2017 um 20:26 schrieb Peter 'p2' De Schrijver: > On 2017-12-15 20:23:11 (+0100), Michael Biebl wrote: >> Could it be a problem that >> >> [ OK ] Stopped LSB: Open vSwitch switch. >> >> is stopped before the NFS mounts are unmounted? Not familiar how ovs >>

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

On 2017-12-15 20:23:11 (+0100), Michael Biebl wrote: > Am 15.12.2017 um 20:19 schrieb Peter 'p2' De Schrijver: > > On 2017-12-14 00:58:33 (+0100), Michael Biebl wrote: > >> Am 14.12.2017 um 00:09 schrieb Michael Biebl: > >>> Am 13.12.2017 um 22:04 schrieb

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 15.12.2017 um 20:19 schrieb Peter 'p2' De Schrijver: > On 2017-12-14 00:58:33 (+0100), Michael Biebl wrote: >> Am 14.12.2017 um 00:09 schrieb Michael Biebl: >>> Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: On 2017-12-13 21:53:10 (+0100), Michael Biebl

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

On 2017-12-14 00:58:33 (+0100), Michael Biebl wrote: > Am 14.12.2017 um 00:09 schrieb Michael Biebl: > > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > >> On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > >>> Control: tags -1 + moreinfo > > >>

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

On 2017-12-14 00:09:23 (+0100), Michael Biebl wrote: > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > > On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > >> Control: tags -1 + moreinfo > >> > >> > >> Am 13.12.2017 um 21:32 schrieb Peter De

Bug#884454: marked as done (systemd: systemd udev rule is not executed when removing - only when adding)

Your message dated Fri, 15 Dec 2017 13:12:05 +0100 with message-id and subject line Re: Bug#884454: systemd: systemd udev rule is not executed when removing - only when adding has caused the Debian Bug report #884454, regarding systemd: systemd

Bug#884454: systemd: systemd udev rule is not executed when removing - only when adding

Package: systemd Version: 235-3 Severity: important Dear Maintainer, on my system, systemd_wants udev rules get only executed when I add devices, not when I remove them. I have two udev rules ENV{PRODUCT}=="3/46d/101a/111", TAG+="systemd", ENV{SYSTEMD_WANTS}="aaa"

Processed: tagging 884374

Processing commands for cont...@bugs.debian.org: > tags 884374 + moreinfo Bug #884374 [systemd] systemd: dpkg fails for systemd package when upgrading from jessie to stretch Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 884374:

Bug#884374: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

Am 14.12.2017 um 18:51 schrieb zythox: > hi, got this : > > dpkg: systemd : problème de dépendance, mais suppression comme demandé : >  systemd-sysv dépend de systemd. >  libpam-systemd:amd64 dépend de systemd (= 215-17+deb8u7). > > (Lecture de la base de données... 65% > (Lecture de la base de

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #883407 (http://bugs.debian.org/883407) # Bug title: libnss-systemd:

Bug#884374: systemd: dpkg fails for systemd package when upgrading from jessie to stretch

Am 14.12.2017 um 17:13 schrieb phil: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > Dear Maintainer, > > > I've just done an upgrade from jessie to strech and i'm stuck with the same pb > that is mentionned in this bug (https://bugs.debian.org/cgi- >

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 14.12.2017 um 00:09 schrieb Michael Biebl: > Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: >> On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: >>> Control: tags -1 + moreinfo >> NFS mount is just done manually: >> >> mount freenas:/mnt/storage /nfs/ >> mount

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Am 13.12.2017 um 22:04 schrieb Peter 'p2' De Schrijver: > On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: >> Control: tags -1 + moreinfo >> >> >> Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: >>> Package: systemd >>> Version: 235-2 >>> Severity: important >> Please

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

On 2017-12-13 21:53:10 (+0100), Michael Biebl wrote: > Control: tags -1 + moreinfo > > > Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: > > Package: systemd > > Version: 235-2 > > Severity: important > Please include more information about your network setup. > What tools

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

2017-12-13 22:58 GMT+02:00 Michael Biebl : > Control: found 883877 235-3 > > Am 08.12.2017 um 21:47 schrieb Martin-Éric Racine: >> http://q-funk.iki.fi/core.systemd.2857 >> > > Not really a backtrace, but a core file, but ok. > Looks like this is i386, so the backtrace should

Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Control: found 883877 235-3 Am 08.12.2017 um 21:47 schrieb Martin-Éric Racine: > http://q-funk.iki.fi/core.systemd.2857 > Not really a backtrace, but a core file, but ok. Looks like this is i386, so the backtrace should look like the attached .txt file. Would be great if you can file this

Processed: Re: Bug#883877: rsyslog: fails to configure, dpkg --configure exits with error

Processing control commands: > found 883877 235-3 Bug #883877 {Done: Michael Biebl } [systemd] rsyslog: fails to configure, dpkg --configure exits with error Marked as found in versions systemd/235-3 and reopened. -- 883877:

Processed: Re: Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Processing control commands: > tags -1 + moreinfo Bug #884319 [systemd] Networking shutdown before NFS unmount on shutdown or reboot Added tag(s) moreinfo. -- 884319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884319 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#884319: Networking shutdown before NFS unmount on shutdown or reboot

Control: tags -1 + moreinfo Am 13.12.2017 um 21:32 schrieb Peter De Schrijver: > Package: systemd > Version: 235-2 > Severity: important Please include more information about your network setup. What tools do you use (NM, ifupdown, networkd), what configuration (ethernet, wifi, dhcp, static),

Bug#878965: Detaching egress BPF program from cgroup failed: Invalid argument

Am 13.12.2017 um 12:01 schrieb Christian Göttsche: > I am also still getting these error messages on my machines. > > Any further information needed? No -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc

Bug#878965: Detaching egress BPF program from cgroup failed: Invalid argument

I am also still getting these error messages on my machines. Any further information needed? -- Package-specific info: -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-1-amd64 (SMP w/4

Bug#884258: machinectl shell should use bash as a default

Am 13.12.2017 um 00:30 schrieb Marco d'Itri: > Package: systemd-container > Version: 235-3 > Severity: normal > > Until https://github.com/systemd/systemd/issues/1395 will be fixed, > machinectl should be patched to use /bin/bash as the default shell > instead of /bin/sh. > While some people

Bug#883692: marked as done (systemd: pam_systemd(su:session): Failed to create session)

Your message dated Sun, 10 Dec 2017 18:53:39 -0800 with message-id <871sk2ug98@hope.eyrie.org> and subject line Re: Bug#883347: systemd fails to load pam_unix.so when spawning user.service has caused the Debian Bug report #883347, regarding systemd: pam_systemd(su:session): Failed to create

Processed: restore blocks that were removed by merge

Processing commands for cont...@bugs.debian.org: > block 882629 by 882628 Bug #882629 [systemd] systemd: debian/copyright refers to the CC0 license by URL 882629 was not blocked by any bugs. 882629 was not blocking any bugs. Added blocking bug(s) of 882629: 859649 and 882628 > block 882630 by

Bug#881675: Bug#883890: nfs-common: Fully Qualified DNS Name mounts in fstab fail to be mounted

Systemd has stated this is not their problem: See bug report 883829 and  88167. My value here is testing. I'm happy to test any proposal and provide the results. It is my problem, because Debian Stretch has introduced this behavior.  wheezy and jessie did not exhibit this behavior. My view is:

Processed: Re: Bug#883407: libc6: getpwnam_r() leaks memory

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/7596 Bug #883407 [systemd] libnss-systemd: _nss_systemd_getpwnam_r leaks memory Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7596'. -- 883407:

Re: Bug#883407: libc6: getpwnam_r() leaks memory

Control: forwarded -1 https://github.com/systemd/systemd/issues/7596 On Fri, Dec 8, 2017 at 4:15 PM, Aurelien Jarno wrote: > control: reassign -1 systemd > control: retitle -1 libnss-systemd: _nss_systemd_getpwnam_r leaks memory > > Hi, > > On 2017-12-08 16:05, Tim Rühsen

Processed: forcibly merging 859649 882628

Processing commands for cont...@bugs.debian.org: > forcemerge 859649 882628 Bug #859649 [debian-policy] debian-policy: Please add CC0-1.0 to common-licenses Bug #882628 [debian-policy] base-files: Please ship CC0 in /usr/share/common-licences 882629 was blocked by: 882628 882629 was not blocking

Bug#883829: closed by Michael Biebl <bi...@debian.org> (Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing)

Michael File systems correctly mounted after "reached target network online" File systema rw in both cases. Case 1 1. I deleted resolv.conf2. Root fs rw in fstab3. File systems mounted by IP address 4. resolve.conf built by end of boot when login possible proc

Bug#883829: Fw: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

 Michael u-boot is a bootloader. The u-boot script load  the kernel from a server,, constructs the kernel commandline, and the u-boot script is complete when the kernel starts, well before these failures. In the kernel command line there is a dns server address, 192.168.1.12 passed to the

Processed: Re: Bug#883407: libc6: getpwnam_r() leaks memory

Processing control commands: > reassign -1 systemd Bug #883407 [libc6] libc6: getpwnam_r() leaks memory Bug reassigned from package 'libc6' to 'systemd'. No longer marked as found in versions glibc/2.25-3. Ignoring request to alter fixed versions of bug #883407 to the same values previously set

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Am 08.12.2017 um 01:44 schrieb Duncan Hare: > Michael > > Full DNS is provided by an MS Windows server 2012R2. > > Because it is net boot, the network in enabled before the kernel is > loaded by u-boot, > and the kernel starts and mounts the file system over NFS. > > Networking parameters,

Bug#811548: marked as done (/usr/bin/crontab in cron-systemd has syntax error)

Your message dated Fri, 8 Dec 2017 14:09:09 +0100 with message-id and subject line closing old bug has caused the Debian Bug report #811548, regarding /usr/bin/crontab in cron-systemd has syntax error to be marked as done. This

systemd-cron_1.5.12-1_armhf.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 08 Dec 2017 11:28:24 +0100 Source: systemd-cron Binary: systemd-cron Architecture: source armhf Version: 1.5.12-1 Distribution: unstable Urgency: medium Maintainer: Debian Systemd Maintainers

Processing of systemd-cron_1.5.12-1_armhf.changes

systemd-cron_1.5.12-1_armhf.changes uploaded successfully to localhost along with the files: systemd-cron_1.5.12-1.dsc systemd-cron_1.5.12.orig.tar.gz systemd-cron_1.5.12-1.debian.tar.xz systemd-cron-dbgsym_1.5.12-1_armhf.deb systemd-cron_1.5.12-1_armhf.buildinfo

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Michael Full DNS is provided by an MS Windows server 2012R2. Because it is net boot, the network in enabled before the kernel is loaded by u-boot,and the kernel starts and mounts the file system over NFS. Networking parameters, including DNS servers are pass through the kernel parameters. Kernel

Processed: Re: Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Processing control commands: > tags -1 moreinfo Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in mounts failing Added tag(s) moreinfo. > severity -1 normal Bug #883829 [systemd] systemd: Fully qualified host names in fstab results in mounts failing Severity set to

Bug#883829: systemd: Fully qualified host names in fstab results in mounts failing

Control: tags -1 moreinfo Control: severity -1 normal Am 08.12.2017 um 00:06 schrieb Duncan Hare: > browne.danum.local:/nfsroot/b827eb/c23849/home /home nfs defaults,rw > 0 0 > tmpfs/tmptmpfs >

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #883380 (http://bugs.debian.org/883380) # Bug title: systemd 235 segfaults when using

Bug#883738: systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths

From: Michael Biebl To: Duncan Hare ; 883...@bugs.debian.org Sent: Wednesday, December 6, 2017 4:49 PM Subject: Re: Bug#883738: systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths Control:

Bug#883738: systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths

Control: tags -1 + moreinfo Am 07.12.2017 um 01:41 schrieb Duncan Hare: > Package: systemd > Version: 232-25+deb9u1 > Severity: important > > > This bug report is empty (again). Please describe your issues in much more detail. Otherwise I'll close this bug report (again) -- Why is it that

Processed: Re: Bug#883738: systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths

Processing control commands: > tags -1 + moreinfo Bug #883738 [systemd] systemd: RO Linux, systemd's link fail, links should not be created cross directory tree, use full paths Added tag(s) moreinfo. -- 883738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=883738 Debian Bug Tracking System

Bug#883347: Bug#883692: systemd: pam_systemd(su:session): Failed to create session

As asked, following up to 883...@bugs.debian.org >> After an upgrade two days ago, I get errors in system logs shortly after >> midnight. I was not able to understand what program exactly has >> problems, so I am not able to repsoduce this from the command line. > >From which version did you

Bug#883690: systemd Caught , "Freezing execution", __libc_fatal("*** %n in writable segment detected ***\n") after execute asprintf(, "U\002%c%s%n"... in src/core/manager.c:2404

Hi Jan Am 06.12.2017 um 15:42 schrieb Jan Fuchs: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > systemd[1]: Caught , dumped core as pid 786. > systemd[1]: Freezing execution. Are you able to reproduce the issue and can you describe the circumstances that are needed to

Processed: Re: Bug#883692: systemd: pam_systemd(su:session): Failed to create session

Processing control commands: > forcemerge 883347 -1 Bug #883347 [systemd] systemd fails to load pam_unix.so when spawning user.service Bug #883692 [systemd] systemd: pam_systemd(su:session): Failed to create session Merged 883347 883692 -- 883347:

Bug#883692: systemd: pam_systemd(su:session): Failed to create session

Control: forcemerge 883347 -1 Am 06.12.2017 um 16:37 schrieb Francesco Potortì: > After an upgrade two days ago, I get errors in system logs shortly after > midnight. I was not able to understand what program exactly has > problems, so I am not able to repsoduce this from the command line.

Bug#883692: systemd: pam_systemd(su:session): Failed to create session

Package: systemd Version: 235-3 Severity: normal Dear Maintainer, -- Package-specific info: -- BEGIN ATTACHMENTS -- /tmp/tmp.7PUo56QuH2/systemd-delta.txt /tmp/tmp.7PUo56QuH2/systemd-analyze-dump.txt /tmp/tmp.7PUo56QuH2/dsh-enabled.txt /etc/fstab -- END ATTACHMENTS -- After an upgrade two days

Bug#883680: marked as done (systemd: Compiling systemd-232.25 debian rules override_dh_auto_test fails)

Your message dated Wed, 6 Dec 2017 15:18:43 +0100 with message-id and subject line Re: Bug#883680: systemd: Compiling systemd-232.25 debian rules override_dh_auto_test fails has caused the Debian Bug report #883680, regarding systemd: Compiling

Bug#883569: libpam-systemd: Prefer systemd-sysv over systemd-shim

Package: libpam-systemd Version: 235-3 Severity: important libpam-systemd depending on systemd-shim first causes severe trouble with resolving dependencies, as APT picks systemd-shim but then later sees a package which needs systemd-sysv and fails. I understand the order was necessary for

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #878965 (http://bugs.debian.org/878965) # Bug title: systemd spam syslog with

Re: stretch-pu: package systemd/232-25+deb9u2

On Sun, 03 Dec 2017 15:17:53 +0100 Michael Biebl wrote: > 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 a couple of issues. I was

Bug#883395: stretch-pu: package systemd/232-25+deb9u2

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 a couple of issues. An annotated changelog follows. Full debdiff is attached. systemd (232-25+deb9u2) stretch;

Processed: severity of 880158 is normal

Processing commands for cont...@bugs.debian.org: > severity 880158 normal Bug #880158 [systemd-container] systemd-container: machinectl incorrectly reports "No machines." when using --no-legend Severity set to 'normal' from 'minor' > thanks Stopping processing here. Please contact me if you

Bug#876103: systemd-nspawn: --read-only is broken

Am 18.09.2017 um 15:43 schrieb Lauri Tirkkonen: > Package: systemd-container > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > on stretch, 'systemd-nspawn --read-only' fails to start the container > entirely. Trivial test case: > > # machinectl pull-tar >

Processed: bug 883380 is forwarded to https://github.com/systemd/systemd/issues/7055

Processing commands for cont...@bugs.debian.org: > forwarded 883380 https://github.com/systemd/systemd/issues/7055 Bug #883380 [systemd] systemd 235 segfaults when using BindPaths or BindReadOnlyPaths Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7055'. > thanks

Bug#883380: systemd 235 segfaults when using BindPaths or BindReadOnlyPaths

Package: systemd Version: 235-3 Severity: important Tags: patch upstream fixed-upstream After upgrading to systemd 235-3 I ran into the exact issue described at https://github.com/systemd/systemd/issues/7055 That is, systemd segfaults when trying to start a unit that makes use of BindPaths or

Bug#883347: systemd fails to load pam_unix.so when spawning user.service

Am 02.12.2017 um 22:39 schrieb Michael Biebl: > Hi Russ! > > Am 02.12.2017 um 19:41 schrieb Russ Allbery: >> Package: systemd >> Version: 235-3 >> Severity: normal >> >> Since upgrading a system to 235-3, all ssh connections are producing the >> following syslog errors: >> >> Dec 2 06:28:23

Re: Very Urgent

Good day to you Am Well pleased to inform you about an urgent business transaction I have for you. kindly contact my private gmail for more details: (chenalice0...@gmail.com) ___ Pkg-systemd-maintainers mailing list

In gutem Glauben, bin ich Emily. In good faith,

Grüße. Ich bin Frau Emily Brown eine Witwe zu spät Engr.Robert Brown, ich bin 57 Jahre alt und leiden unter Bauchspeicheldrüsenkrebs. Mein Zustand ist wirklich schlecht und es ist ganz offensichtlich, dass ich nicht mehr als drei Monate nach meinem Arzt leben werde. Ich bin bereit, eine Spende

Bug#883089: marked as done (udev: on alpha architecture, /dev/disk/by-XXX nodes not created)

Your message dated Sat, 2 Dec 2017 12:05:42 +0100 with message-id and subject line Re: Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created has caused the Debian Bug report #883089, regarding udev: on alpha architecture,

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

On Fri, Dec 01, 2017 at 06:13:01PM -0600, Bob Tracy wrote: > Not ignoring you... PWS 433au takes overnight to build a kernel these > days. > > Rebuilt 4.14 with the few changes noted in my previous message. Will > try it tomorrow when I've got a couple of free hours to collect data and > deal

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

On Wed, Nov 29, 2017 at 11:10:41PM -0600, Bob Tracy wrote: > On Wed, Nov 29, 2017 at 05:12:58PM +0100, Michael Biebl wrote: > > Please test the kernel that is provided by Debian and report back if it > > works with that one. Not ignoring you... PWS 433au takes overnight to build a kernel these

Bug#883202: marked as done (systemd: only sets baud rate for first console= kernel parameter)

Your message dated Fri, 1 Dec 2017 18:17:29 +0100 with message-id <0787b156-a2aa-9346-7e77-f2e48b70f...@debian.org> and subject line Re: Bug#883202: Re: Bug#883202: systemd: only sets baud rate for first console= kernel parameter has caused the Debian Bug report #883202, regarding systemd: only

Bug#883255: RFP: systemd-coredump-python -- Log Python exceptions in the journal via systemd-coredump

Package: wnpp Severity: wishlist * Package name: systemd-coredump-python Version : 2 Upstream Author : Zbigniew Jędrzejewski-Szmek * URL : https://github.com/systemd/systemd-coredump-python * License : GPL 2.1+ Programming Lang: Python Description : Log

Bug#883219: marked as done (udev: There is not connection with BLACKVIEW P2 lite)

Your message dated Fri, 1 Dec 2017 00:35:58 +0100 with message-id <9b2324a8-3584-6d58-bba9-e3df74676...@debian.org> and subject line Re: Bug#883219: udev: There is not connection with BLACKVIEW P2 lite has caused the Debian Bug report #883219, regarding udev: There is not connection with

Bug#883202: systemd: only sets baud rate for first console= kernel parameter

Am 30.11.2017 um 17:23 schrieb Joshua Marshall: > Package: systemd > Version: 232-25+deb9u1 > Severity: normal > > Dear Maintainer, > > root@debian:/home/testing# uname -a > > Linux debian 4.9.0-4-amd64 #1 SMP Debian 4.9.51-1 (2017-09-28)

Bug#883219: udev: There is not connection with BLACKVIEW P2 lite

Package: udev Version: 232-25+deb9u1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #882270 (http://bugs.debian.org/882270) # Bug title: systemd-logind crashes when

Bug#883185: systemd-networkd: physical port in bridge stuck in "configuring", failing systemd-networkd-wait-online.service

Am 30.11.2017 um 13:11 schrieb Bernhard Schmidt: > Package: systemd > Version: 235-3 > Severity: normal > > Hi, > > after upgrading from Stretch to Buster the physical interface in my bridge > is stuck in "configuring", causing systemd-networkd-wait-online to stall > and eventually timeout. > >

Bug#883185: systemd-networkd: physical port in bridge stuck in "configuring", failing systemd-networkd-wait-online.service

Package: systemd Version: 235-3 Severity: normal Hi, after upgrading from Stretch to Buster the physical interface in my bridge is stuck in "configuring", causing systemd-networkd-wait-online to stall and eventually timeout. This looks like https://github.com/systemd/systemd/issues/5043,

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

On Wed, Nov 29, 2017 at 05:12:58PM +0100, Michael Biebl wrote: > Please check all other kernel config options as well that are listed in > /usr/share/doc/systemd/README.gz A few of the listed config options do not exist, at least in 4.14: CONFIG_DMIID CONFIG_DEVPTS_MULTIPLE_INSTANCES There were

Bug#882027: Problem solved

Hi, the solution is allready reportet nad nothing to do with systemd: https://wiki.debian.org/KernelModesetting -> section nVidia GfxCards. Regards Torsten ___ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

Am 29.11.2017 um 15:56 schrieb Bob Tracy: > Package: udev > Version: 235-3 > Severity: important > > Dear Maintainer, > > With kernel version 4.13, udev worked correctly at least two releases ago. > The > current release (and maybe the prior one) fails to detect/enumerate SCSI disk >

Bug#883089: udev: on alpha architecture, /dev/disk/by-XXX nodes not created

Package: udev Version: 235-3 Severity: important Dear Maintainer, With kernel version 4.13, udev worked correctly at least two releases ago. The current release (and maybe the prior one) fails to detect/enumerate SCSI disk partitions (both real filesystems and swap partitions) except for "/"

Bug#883026: systemd-fsck invalid parameters fo f2fs file system

Control: reassign -1 f2fs-tools Control: retitle -1 fsck.f2fs should support -y On Tue, 28 Nov 2017 22:23:18 + Piotr P. wrote: > Package: systemd > Version: 232-25+deb9u1 > > I found with debsums invalid packages(not systemd) so I created file > /forcefsck to

Processed: Re: systemd-fsck invalid parameters fo f2fs file system

Processing control commands: > reassign -1 f2fs-tools Bug #883026 [systemd] systemd-fsck invalid parameters fo f2fs file system Bug reassigned from package 'systemd' to 'f2fs-tools'. No longer marked as found in versions systemd/232-25+deb9u1. Ignoring request to alter fixed versions of bug

Bug#883026: systemd-fsck invalid parameters fo f2fs file system

Package: systemd Version: 232-25+deb9u1 I found with debsums invalid packages(not systemd) so I created file /forcefsck to perform check. It didn't work. I found in syslog information that fsck was invoked with wrong parameters on boot. Nov 28 23:05:45 ppiotr systemd-fsck[122]: fsck.f2fs:

Processed: [bts-link] source package systemd

Processing commands for cont...@bugs.debian.org: > # > # bts-link upstream status pull for source package systemd > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user bts-link-upstr...@lists.alioth.debian.org Setting user to

[bts-link] source package systemd

# # bts-link upstream status pull for source package systemd # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org # remote status report for #882245 (http://bugs.debian.org/882245) # Bug title: systemd-sysv: shutdown does not

live-config: Wrong time when RTC is set to local time

Package: live-config Version: 5.20170112 Severity: normal Hi! This may be a follow up of #824197, I believe that the patches that were introduced then don't fix the problem, at least not now. I'm testing this on a live network image which was built using stretch and has as boot parameters:

Processed: Re: systemd-logind crashes when closing lid after "systemctl mask sleep.target"

Processing control commands: > forwarded -1 https://github.com/systemd/systemd/issues/7466 Bug #882270 [systemd] systemd-logind crashes when closing lid after "systemctl mask sleep.target" Set Bug forwarded-to-address to 'https://github.com/systemd/systemd/issues/7466'. -- 882270:

Bug#882270: systemd-logind crashes when closing lid after "systemctl mask sleep.target"

Control: forwarded -1 https://github.com/systemd/systemd/issues/7466 On Mon, 20 Nov 2017 22:05:49 +0100 Lars Stoltenow wrote: > disable suspend using "systemctl mask sleep.target suspend.target". ... > Nov 20 21:39:26 litterbox systemd-logind[10892]: Assertion

Processed: Bugs also affect sid

Processing commands for cont...@bugs.debian.org: > tag 882629 + sid Bug #882629 [systemd] systemd: debian/copyright refers to the CC0 license by URL Added tag(s) sid. > tag 882630 + sid Bug #882630 [systemd-bootchart] systemd-bootchart: debian/copyright refers to CC0 by URL Added tag(s) sid. >

Processed: retitle 882630 to systemd-bootchart: debian/copyright refers to CC0 by URL

Processing commands for cont...@bugs.debian.org: > retitle 882630 systemd-bootchart: debian/copyright refers to CC0 by URL Bug #882630 [systemd-bootchart] systemd-bootchart: debian/control refers to CC0 by URL Changed Bug title to 'systemd-bootchart: debian/copyright refers to CC0 by URL' from

Bug#882629: systemd: debian/copyright refers to the CC0 license by URL

Package: systemd Version: 235-3 Severity: normal Control: tag -1 + stretch buster Control: block -1 by 882628 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, This package refers to the text of the Creative Commons Zero license by its URL on creativecommons.org; as far as I

Bug#882630: systemd-bootchart: debian/control refers to CC0 by URL

Package: systemd-bootchart Severity: normal Control: tag -1 + stretch buster Control: block -1 by 882628 -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Dear maintainer, This package refers to the text of the Creative Commons Zero license by its URL on creativecommons.org; as far as I

Processed: systemd: debian/copyright refers to the CC0 license by URL

Processing control commands: > tag -1 + stretch buster Bug #882629 [systemd] systemd: debian/copyright refers to the CC0 license by URL Added tag(s) buster and stretch. > block -1 by 882628 Bug #882629 [systemd] systemd: debian/copyright refers to the CC0 license by URL 882629 was not blocked by

<    3   4   5   6   7   8   9   10   11   12   >