Bug#897654: libpam-systemd: "Failed to create session: No such process"

Control: forcemerge 892585 -1 Am 04.05.2018 um 17:02 schrieb Michael Biebl: > Am 03.05.2018 um 23:56 schrieb Michael Gold: >> On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote: >>> Am 03.05.2018 um 23:12 schrieb Michael Gold: >>>> Is this proble

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 04.05.2018 um 18:24 schrieb Michael Gold: > On Fri, May 04, 2018 at 18:02:09 +0200, Michael Biebl wrote: >> I guess you have two options here: >> Either drop gid=4 from your mount flags or you add >> SupplementaryGroups=adm to systemd-logind.service > > I haven't

Bug#897266: systemd: journalctl assertion failure

Control: tags -1 + moreinfo On Tue, 01 May 2018 05:29:49 +0200 Marc Lehmann wrote: > Package: systemd > Version: 232-25+deb9u2 > Severity: normal > > Dear Maintainer, > > I tried to see cron messages using: > >journalctl -fu cron > > but journalctl aborted with

Bug#897070: udev: systemd-udevd exits with SIGABRT in __open_nocancel

Control: tags -1 + moreinfo On Fri, 27 Apr 2018 18:06:15 -0500 Nathaniel Morck Beaver wrote: > Package: udev > Version: 232-25+deb9u3 > Severity: normal > > Backtraces attached. I do not know how to reliably reproduce. > > I cannot install debugging symbols because

Bug#726003: udev: disks for multi-disk btrfs displayed few times in open dialog of applications

Control: tags -1 + moreinfo On Fri, 11 Oct 2013 05:27:10 +0400 George Shuklin wrote: > Package: udev > Version: 204-5 > Severity: minor > > Yves-Alexis Perez directed be to udev with this bug. > > Bug description: > > When multidisk btrfs volume is available in system,

Bug#898260: systemd: HP notebook ZBook 17 G4 - WLAN hardware button not working

Control: reassign -1 udev 238-4 Am 09.05.2018 um 12:24 schrieb René Krell: > When pressing it, the following lines are added to the /var/log/message > s file: > May 8 22:22:50 rkrell kernel: [40955.295433] atkbd serio0: Unknown key > pressed (translated set 2, code 0xf8 on isa0060/serio0). > May

Re: rebuilding systemd in armhf chroot

Am 27.04.2018 um 09:49 schrieb Falk Niebuhr: > Hi, > > for a Debian Jessie based ARM device I try to rebuild the systemd package > from the backports. > Unfortunately this does not work, the build never ends and hangs. > Why don't you upgrade to stretch which has a newer systemd or use the

Re: rebuilding systemd in armhf chroot

Am 27.04.2018 um 09:49 schrieb Falk Niebuhr: > Do I have to take care of something special to rebuild systemd? I would suggest using a pbuilder or sbuild chroot to rebuild the package. This is pretty close to what's used on the buildds. > Do I have to disable the tests? Well, you can disable

Re: Fixing Linux getrandom() in stable

Hi Russ Am 10.05.2018 um 19:22 schrieb Russ Allbery: > Michael Biebl <bi...@debian.org> writes: >> Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > >>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and >>> also proposed that systemd cou

Bug#898474: timedatectl can't determine if NTP is enabled

Am 12.05.2018 um 13:44 schrieb Michael Biebl: > Please attach the output of > systemctl status systemd-timesyncd The output of systemctl status dbus.socket dbus.service as well, please -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from

Bug#898388: systemd-sysv: shutdown command always fails

Am 14.05.2018 um 01:23 schrieb Meeuwissen Olaf: > Definitely not from my POV. I'm off now installing dbus myself because > systemd-sysv didn't think it important enough to do that for me :-( > Well, the systemd package does do it for you, but you actively prevented dbus from being installed,

Bug#898388: systemd-sysv: shutdown command always fails

Am 11.05.2018 um 08:10 schrieb Meeuwissen Olaf: > Hi, > > Thanks for the quick follow-up. > > Michael Biebl writes: > >> Control: tags -1 + moreinfo >> >>> I have set up unattended-upgrades to reboot my machine at 04:00 when >>> necessary. Inte

Re: debhelper: Because it is listing tmpfiles in systemd's only, conf overriding is not working

Am 04.05.2018 um 13:47 schrieb Michael Biebl: > Dropping #TMPFILES# means, systemd-tmpfiles will act on all tmpfiles. > This would be a bit like if upgrading rsyslog would restart all system > services (including rsyslog). That doesn't feel right. > So I don't think droppi

Bug#897266: systemd: journalctl assertion failure

Am 20.05.2018 um 08:59 schrieb Marc Lehmann: > Sorry for the late reply, I got a bit swamped with work. > > On Sat, May 05, 2018 at 12:13:35PM +0200, Michael Biebl <bi...@debian.org> > wrote: >> What does journalctl --verify say about this particular file? > > AF

Bug#898892: Please enable regex/pattern matching support in journalctl

Control: reassign 890265 src:systemd Control: forcemerge -1 890265 Am 17.05.2018 um 09:36 schrieb Laurent Bigonville: > Source: systemd > Version: 238-4 > Severity: normal > > Hi, > > Would be nice is the regex/pattern matching support was enabled in > journalctl. > > It requires libpcre2

Bug#900048: Please precreate /usr/lib/dnssec-trust-anchors.d/ and /etc/dnssec-trust-anchors.d/ in the package

Am 25.05.2018 um 09:25 schrieb Laurent Bigonville: > Package: systemd > Version: 238-4 > Severity: minor > > Hi, > > resolved is apparently using the /usr/lib/dnssec-trust-anchors.d/ and > /etc/dnssec-trust-anchors.d/ directories, but the package is not > shipping them. > > Shouldn't the

Bug#869282: udev: Update breaks Keyboard Configuration

Control: tags -1 + moreinfo On Sat, 22 Jul 2017 13:52:37 +0200 jEsuSdA wrote: > Package: udev > Version: 234-2 > Severity: important > > Dear Maintainer, > > I've just update udev and my keyboard does not works properly. All the > multimedia and extra keys does not work and

Bug#877985: user@1000.service: Start operation timed out. Terminating.

Control: tags -1 + moreinfo Hi, is this issue still reproducible? If so, have you tried what I wrote earlier to disable your user services one by one to see if one of them causes this delay? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away

Bug#901313: ignoring: Numerical argument out of domain

Control: tags -1 + moreinfo Am 11.06.2018 um 11:41 schrieb 積丹尼 Dan Jacobson: > Package: systemd > Version: 238-5 > > Now lots of these messages: > Jun 11 17:24:42 jidanni6 systemd[230]: Failed to add rule for system call > umount() / -10070, ignoring: Numerical argument out of domain > Jun 11

Re: systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

Hi Am 22.04.2018 um 15:09 schrieb Antonio Terceiro: > # findmnt | grep machine-id > ├─/root/patched2/etc/machine-id > /dev/mapper/lemur--vg-root[/root/patched2/run/machine-id] ext4 > ro,relatime,errors=remount-ro,data=ordered > > This explains the crash in

Re: systemd-setup-machine-id leaving mount behind? (was "Bug#871835: Call for help: review patches for debootstrap")

Hi Antonio sorry for the late reply... Am 13.06.2018 um 01:20 schrieb Michael Biebl: > Am 22.04.2018 um 15:09 schrieb Antonio Terceiro: > >> # findmnt | grep machine-id >> ├─/root/patched2/etc/machine-id >> /dev/mapper/lemur--vg-root[/root/patch

Bug#897070: udev: systemd-udevd exits with SIGABRT in __open_nocancel

On Sat, 5 May 2018 03:21:04 +0200 Michael Biebl wrote: > Control: tags -1 + moreinfo > > On Fri, 27 Apr 2018 18:06:15 -0500 Nathaniel Morck Beaver > wrote: > > Package: udev > > Version: 232-25+deb9u3 > > Severity: normal > > > > Backtraces attache

Bug#894605: systemd: System fails to suspend.

On Mon, 9 Apr 2018 23:17:28 +0200 (CEST) "hub...@golembiowski.pl" wrote: > echo "mem" > /sys/power/state suspends system correctly with possibility to > wake > up as expected. > > I run dist-upgrade regularly so I expect a number of packages upgrade > recently. > Unfortunately can't

Bug#769946: upgrade-reports: auto-suspend after login (Wheezy->Jessie upgrade)

Control: tags -1 + moreinfo Hi Edward On Mon, 17 Nov 2014 21:48:57 +0200 "Edward J. Shornock" wrote: > Package: upgrade-reports > Severity: normal > > I did the upgrade a month or so ago but didn't have time to properly > troubleshoot the problem until now. > > System: > Manufacturer:

Bug#892321: attempts to suspend failing after crash

Am 18.06.2018 um 09:26 schrieb Daniel Pocock: > The problem: a corrupted swap partition > > Before deciding how systemd should detect that, it may first be > necessary to decide if it is the job of systemd or some other process to > detect the problem How is a swap partition relevant for

Bug#900956: systemd-container: doesn't reboot containter, exit with error "Parent died too early"

Am 07.06.2018 um 12:14 schrieb Antonio: > Package: systemd-container > Version: 238-5 > Severity: normal > > Dear Maintainer, > > start container: > $ systemd-nspawn -b -D /test > > and try to reboot: > root@test:~$ reboot > > container doesn't reboot but exit with error: > Failed

Re: [Pkg-utopia-maintainers] Bug#895261: RFS: dbus-broker/13-2 [ITP] -- Linux D-Bus Message Broker

Am 29.05.2018 um 19:30 schrieb Daniele Nicolodi: > What would it take to have user services managed in a similar way as > system services? Should I look into implementing that in > init-system-helpers or should a new dh helper be created? It would need changes to both init-system-helpers and

Bug#788622: systemd-logind regularly eats over 20% of system resources

Control: tags -1 + moreinfo Hi! On Sat, 13 Jun 2015 20:35:15 +0300 =?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <martin-eric.rac...@iki.fi> wrote: > 2015-06-13 19:52 GMT+03:00 Michael Biebl <bi...@debian.org>: > > Am 13.06.2015 um 18:39 schrieb Martin-Éric Racine: > >&

Bug#900168: systemd: Ignore systemd-machine-id-setup

Control: tags -1 + moreinfo Am 27.05.2018 um 01:28 schrieb Hideki Yamane: > Package: systemd > Severity: wishlist > > Hi, > > During debootstrap autopkgtest, it runs debootstap itself under > systemd-nspawn > environment. And salsa CI runner runs it under docker and it doesn't have > full

Bug#764557: Problem persists

Am 28.05.2018 um 10:44 schrieb Nikolaus Rath: > Hi, > > Did you see the text that I included in the reopening email? Maybe I should > have addressed it differently. I wrote: That doesn't say, if journalctl still hangs or not. Only that you still have a journal file corruption. -- Why is it

Bug#900366: postinst creation of /etc/machine-id breaks CustomFirstBoot unit parameter

Am 29.05.2018 um 16:53 schrieb Matthew Richardson: > Package: systemd > Version: 238-5 > > The postinst for the systemd deb pkg contains the following: > > # Create /etc/machine-id > systemd-machine-id-setup > > This generates /etc/machine-id as the package is installed. > > However the

Bug#832566: systemd-machined breaks automounting nfs shares

On Mon, 26 Mar 2018 07:29:34 +1030 John Pearson wrote: > Hi Michael, > > If I disable libvirtd, systemd-machined isn't started. > > Can't say if this problem also occurs in Stretch - this is the only > machine with this configuration I have access to, and upgrading to >

Bug#764557: Problem persists

Control: tags -1 + moreinfo Hi On Tue, 10 Oct 2017 18:51:33 +0200 Michael Biebl <bi...@debian.org> wrote: > Please reopen or file a new bug report, if you still experience specific > problems with journald. You reopened the bug report in the mean time. Does that mean, journalctl

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 09:18 schrieb Martin Steigerwald: > Package: systemd > Version: 239-1 > Severity: normal > > Dear Michael, dear Maintainers, > > Since using kernel 4.17-rc7 I think (now using self compiled 4.17 vanilla > kernel), I see a strange new behavior on this ThinkPad T520. I did not yet

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Am 27.06.2018 um 14:17 schrieb Joel Cross: > I have attached both logs. Ok, thanks for the logs. So it looks like no proper hibernation image was written to disk. If you run "systemctl hibernate", systemd-logind logind will notify clients via D-Bus that the system is going to hibernate. Then

Re: dh_installsystemd - why deactivate services in postrm instead of prerm?

Am 27.06.2018 um 20:20 schrieb Daniele Nicolodi: > On 6/27/18 11:48 AM, Michael Biebl wrote: >> Hi Daniele >> >> Am 27.06.2018 um 19:39 schrieb Daniele Nicolodi: >>> Hello, >>> >>> I'm working on dh_installsystemduser, the equivalent of >&

Bug#894605: systemd: System fails to suspend.

On Wed, 13 Jun 2018 18:10:41 +0200 Michael Biebl wrote: > On Mon, 9 Apr 2018 23:17:28 +0200 (CEST) "hub...@golembiowski.pl" > wrote: > > > echo "mem" > /sys/power/state suspends system correctly with possibility to > > wake > > up as expected.

Bug#893054: systemd: System failed to boot after upgrade/install systemd from systemd:i386

On Sat, 24 Mar 2018 21:51:21 +0100 Michael Biebl wrote: > Control: tags -1 + moreinfo > On Mon, 19 Mar 2018 09:46:04 -0600 Jeff Ketchum wrote: > > Second issue, I have trouble getting my system to boot reliably after the > > changes. > > It is using systemd:amd64

Bug#892321: attempts to suspend failing after crash

On Mon, 18 Jun 2018 10:38:20 +0200 Daniel Pocock wrote: > > > On 18/06/18 09:51, Michael Biebl wrote: > > Am 18.06.2018 um 09:26 schrieb Daniel Pocock: > > > >> The problem: a corrupted swap partition > >> > >> Before deciding how systemd sh

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Am 27.06.2018 um 16:03 schrieb Michael Biebl: > Joel, can you execute "/lib/systemd/systemd-sleep hibernate" directly > and see what happens then. Make that SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-sleep hibernate This way you should get a more verbose debug output -- Wh

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 15:11 schrieb Michael Biebl: > Am 25.06.2018 um 09:18 schrieb Martin Steigerwald: >> Package: systemd >> Version: 239-1 >> Severity: normal >> >> Dear Michael, dear Maintainers, >> >> Since using kernel 4.17-rc7 I think (now using

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 17:45 schrieb Martin Steigerwald: > Michael Biebl - 25.06.18, 17:20: >> Am 25.06.2018 um 15:11 schrieb Michael Biebl: >>> Am 25.06.2018 um 09:18 schrieb Martin Steigerwald: >>>> Package: systemd >>>> Version: 239-1 >>>> Sev

Bug#898260: systemd: HP notebook ZBook 17 G4 - WLAN hardware button not working

On Wed, 9 May 2018 13:53:29 +0200 Michael Biebl wrote: > Control: reassign -1 udev 238-4 > > Am 09.05.2018 um 12:24 schrieb René Krell: > > When pressing it, the following lines are added to the /var/log/message > > s file: > > May 8 22:22:50 rkrell kernel: [40955.29

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 09:18 schrieb Martin Steigerwald: > Kernel: Linux 4.17.0-tp520-btrfstrim+ (SMP w/4 CPU cores; PREEMPT) I would try a Debian provided kernel as a first step. What happens if you restart chrony when the system is up an running? Does chrony log something itself? The journal log

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 10:14 schrieb Martin Steigerwald: > severity 902336 important > thanks > > Martin Steigerwald - 25.06.18, 09:18: >> Package: systemd >> Version: 239-1 >> Severity: normal > […] >> % systemctl --state=failed >> UNIT LOAD ACTIVE SUBDESCRIPTION >> ● chrony.service

Bug#902185: udev: fails to configure with systemd 238-5

Hi Am 23.06.2018 um 10:40 schrieb Sven Joachim: > , > | $ systemctl status systemd-udevd.service > | ● systemd-udevd.service - udev Kernel Device Manager > |Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static; > vendor preset: enabled) > |Active: failed (Result:

Bug#843497: systemd-networkd block the shutdown process of my nspawn container

Am 23.06.2018 um 04:27 schrieb 张 敬强: > 在 2018年6月23日星期六 CST 上午6:36:42，Michael Biebl 写道： >> >> This sounds like it could be the same issue as in >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901834 >> >> Zhang Jingqiang, could you please test the patch

Re: new version of systemd seems to break autopkgtests of policykit-1, kwin and python-dbusmock

Hi Paul, you are quick! Am 23.06.2018 um 13:30 schrieb Paul Gevers: > Dear systemd maintainers, all, > > With the upload of version 239-1 of systemd the autopkgtests of the > policykit-1, kwin and python-dbusmock started to fail¹. > > It appear that policykit-1 fails to install since the 239-1

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 25.06.2018 um 18:33 schrieb Michael Biebl: > Am 25.06.2018 um 17:45 schrieb Martin Steigerwald: >> So for that booting with Debian kernel would not be necessary I think, >> but in order to check for the upower issues after restoring the original >> service file. > &g

Bug#902336: systemd: sddm login screen does not appear until after more than a minute

Am 26.06.2018 um 12:45 schrieb Martin Steigerwald: > Michael Biebl - 26.06.18, 12:28: >> Am 25.06.2018 um 18:33 schrieb Michael Biebl: >>> Am 25.06.2018 um 17:45 schrieb Martin Steigerwald: >>>> So for that booting with Debian kernel would not be necessary I >

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Am 26.06.2018 um 12:54 schrieb Joel Cross: > Package: systemd > Version: 239-1 > Severity: normal > > Dear Maintainer, > > Over the last few days (since my last system upgrade) I am unable to > successfully hibernate/resume using the `systemctl hibernate` command. This is > what happens: > > -

Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Am 26.06.2018 um 13:20 schrieb Joel Cross: > On Tue, 26 Jun 2018, at 12:12 PM, Michael Biebl wrote: >> Which backend have you configured in pm-hibernate? the in-kernel >> hibernate mechanism, Tux0nIce, uswsusp? > > Sorry, I have no idea how to find that out. I do not re

Bug#897654: libpam-systemd: "Failed to create session: No such process"

On Thu, 3 May 2018 16:31:53 -0400 Michael Gold wrote: > Package: libpam-systemd > Version: 238-4 > Severity: important > > At some point in the past, I was able to shut down my system as a > non-root user: > dbus-send --system --print-reply --dest=org.freedesktop.login1 >

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 03.05.2018 um 23:12 schrieb Michael Gold: > retitle 897654 libpam-systemd: hidepid causes "Failed to create session: No > such process" > thanks > > On Thu, May 03, 2018 at 22:53:34 +0200, Michael Biebl wrote: >> On Thu, 3 May 2018 16:31:53 -0400 Mic

Bug#897654: libpam-systemd: "Failed to create session: No such process"

Am 03.05.2018 um 23:56 schrieb Michael Gold: > On Thu, May 03, 2018 at 23:42:34 +0200, Michael Biebl wrote: >> Am 03.05.2018 um 23:12 schrieb Michael Gold: >>> Is this problem already tracked? >> I'd say this is a duplicate of #892585 > > Agreed. I think t

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 20:11 schrieb Ben Hutchings: > Package: systemd > Version: 239-1 > Severity: serious > > Starting with Linux 4.18, the autofs4 kernel module is renamed > to autofs, but retaining an 'autofs4' alias. > > Despite the presence of the alias, systemd fails to load the > autofs

Bug#902946: Fails to load autofs module through autofs4 alias

Am 03.07.2018 um 23:10 schrieb Ben Hutchings: > On Tue, 2018-07-03 at 23:08 +0200, Michael Biebl wrote: >> Am 03.07.2018 um 20:11 schrieb Ben Hutchings: >>> Package: systemd >>> Version: 239-1 >>> Severity: serious >>> >>> Starting

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

Am 21.06.2018 um 23:34 schrieb Francesco Poli: > On Thu, 21 Jun 2018 22:52:37 +0200 Michael Biebl wrote: > > [...] >> I would check the journal and try to correlate it with other events >> based on the timestamp > > By looking at the journal timestamps and the roo

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

Am 22.06.2018 um 01:24 schrieb Michael Biebl: > Fwiw, I'm aware of > https://github.com/systemd/systemd/issues/7104 > You might also be interested in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895821 -- Why is it that all of the instruments seeking intelligent life in the

Bug#904918: man: clarify KillUserProcesses default configuration for Debian

Control: forcemerge 827159 904918 Hi Am 29.07.2018 um 15:55 schrieb Michael Prokop: > Package: systemd > Version: 239-7 > Severity: minor > > Hi, > > quoting from systemd-run(1): > > | If KillUserProcesses=yes is configured in logind.conf(5), the default, > | the session scope will be

Bug#905381: systemd FTCBFS for arm64: uses the build architecture compiler/linker for src/boot/efi

Hi Am 03.08.2018 um 22:08 schrieb Helmut Grohne: > In any case, the attached patch fixes the cross build problem for arm64. > Please consider applying or improving it. It would be great if you could submit your patch as PR upstream at https://github.com/systemd/systemd -- Why is it that all

Bug#905454: php-common: Update to php-common (1:62) stuck in php.common-post at systemd-tty-ask

Am 05.08.2018 um 09:12 schrieb Michael Biebl: > hm, update-debian.s /home/jaap/bin/update-debian.sh > /home/jaap/bin/update-debian.sh... > How exactly do you trigger the update? > Is system fully booted at this point? > Can you provide us with steps how to reproduce the issue? Ple

Bug#904913: systemd: systemctl cat 'foo*' (using shellglob patterns) only lists active units

Am 29.07.2018 um 15:32 schrieb Michael Prokop: > 1) "systemctl cat ssh.service" NOT list its unit if it's not running, or > 2) "systemctl cat 'ssh*'" *list* its unit file even if it's not running, > but known to the sysstem (since `systemctl cat ssh.service` lists it too)? > > (JFTR, I wanted to

Re: Add interim summary

Am 10.08.2018 um 15:54 schrieb Felipe Sateler: > I'm still not sure why we parse Also= for starting. Michael, do you > remember the rationale? I think this is simply a mistake and should be corrected. Parsing Also= for dh_systemd_enable was done, so the tools behave similar to how "systemctl

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 15.08.2018 um 22:15 schrieb Christoph Anton Mitterer: > On Wed, 2018-08-15 at 22:07 +0200, Michael Biebl wrote: >> Are you sure then that logind is actually restarted? > I just manually tried (actually logind was just a guess to be the cause > for the pop up not appearing... so

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 15.08.2018 um 23:20 schrieb Michael Biebl: > Am 15.08.2018 um 22:59 schrieb Christoph Anton Mitterer: >> On Wed, 2018-08-15 at 22:33 +0200, Michael Biebl wrote: >>> If I restart logind via "systemctl restart systemd-logind", my X >>> session >>&g

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 15.08.2018 um 21:23 schrieb Christoph Anton Mitterer: > Hey Michael. > > On Wed, 2018-08-15 at 21:02 +0200, Michael Biebl wrote: >> I suppose what you are seeing is that Xorg exited. > No,.. my X doesn't exit... the only thing that happens is, that when I > press the po

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 15.08.2018 um 22:59 schrieb Christoph Anton Mitterer: > On Wed, 2018-08-15 at 22:33 +0200, Michael Biebl wrote: >> If I restart logind via "systemctl restart systemd-logind", my X >> session >> is terminated on sid. > Nope... just tried it again (also sid)..

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 15.08.2018 um 23:32 schrieb Christoph Anton Mitterer: > I'm afraid, I have no idea why mine doesn't restart ^^ In any case, this looks like a cinnamon issue. My guess is, that the cinnamon component responsible for power management not deal with the fact that logind goes away and does not

Bug#906231: systemd: restarting systemd-logind causes power-button event to immediately shutdown cinnamon without asking

Am 16.08.2018 um 01:05 schrieb Michael Biebl: > Am 15.08.2018 um 23:32 schrieb Christoph Anton Mitterer: >> I'm afraid, I have no idea why mine doesn't restart ^^ > > In any case, this looks like a cinnamon issue. > My guess is, that the cinnamon component responsible for

Re: Does a generator need to take care of overrides in /etc?

Am 14.08.2018 um 00:09 schrieb Bernhard Schmidt: > Hi, > > on src:openvpn we have recently gotten a bug report about local > modifications of the openvpn@.service file in /etc being ignored when > the instance is started by the systemd generator, because the generator > unconditionally links to

Re: Bug#905528: mount: nofail

Am 12.08.2018 um 20:04 schrieb Chris Hofstaedtler: > Control: reassign -1 systemd-sysv > > * Seamus de Mora [180812 18:02]: >> Package: mount >> Version: 2.29.2-1+deb9u1 >> Severity: normal > > [..] > >> Distributor ID: Raspbian >> Description: Raspbian GNU/Linux 9.4 (stretch) >> Codename:

Bug#905817: UID range of DyanmicUser overlaps with existing definitions in debian-policy

Package: systemd Version: 239-7 Severity: important Currently, DynamicUser gets a uid from within the following range: 61184 - 65519. Those values can be configured during build time via -Ddynamic-uid-min= and -Ddynamic-uid-max. The debian policy has a section about uids and gids:

Bug#905817: UID range of DyanmicUser overlaps with existing definitions in debian-policy

Am 10.08.2018 um 08:23 schrieb Michael Biebl: > CCing Sean to get his input as debian-policy maintainer. > > Sean, you can get more in-detail documentation about DynamicUser at > https://www.freedesktop.org/software/systemd/man/systemd.exec.html#DynamicUser= There is also https:

Re: Add interim summary

Am 10.08.2018 um 13:32 schrieb Christian Ehrhardt: > I think I'd want/need a "dh_systemd_start --no-dependent-services/sockets" > option to intentionally have it generate "just" for libvirt.service and not > the sockets it depends on. > As mentioned, for all of the complexity pulling in the

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:45 schrieb Michael Biebl: > Am 17.08.2018 um 15:37 schrieb Felipe Sateler: > >> Well, as long as we support the --skip-systemd-native, we can't drop the >> check :/  > > I don't understand. > I thought the idea was that dh_installsystemd would gen

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 14:53 schrieb Valentin Vidic: > On Fri, Aug 17, 2018 at 02:40:53PM +0200, Michael Biebl wrote: >> Could you add "set -x" to /usr/sbin/invoke-rc.d, then re-install the >> lldapd package and attach the output please. > > Sure, here it goes: Tha

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:24 schrieb Michael Biebl: > The problem is, that dh_installsystemd enables the service *after* a > start attempt has been made and > systemctl is-enabled checks for the state of the native service unit. > > With dh_systemd_enable/start, the enable part was b

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:27 schrieb Felipe Sateler: > I'll revert the change to unbreak things soon. For the longer term, > maybe we can switch the check to  > > /lib/systemd/systemd-sysv-install is-enabled $service I wouldn't bother introducing new code here and simply revert the change to get the

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Hi Am 17.08.2018 um 14:18 schrieb Valentin Vidic: > After upgrading init-system-helpers from 1.51 to 1.53 services are > not started from package postinst anymore. I noticed this with the > lldpad package, but others like corosync seem to have the same problem. > > Downgrade init-system-helpers

Bug#906421: invoke-rc.d: service not started from package postinst anymore

Am 17.08.2018 um 15:13 schrieb Felipe Sateler: > Hmm. Commit 6f95680ffc9b1605841eb7d3d8eb92c790e6c73a looks like the > culprit of the regression. But I'd like to understand why this happens. > Shouldn't update-rc.d have enabled the service? The lldpad or corosync package ship a native systemd

Bug#907486: libpam-systemd: Depends: systemd-shim (>= 10-4~) but it is not going to be installed

Control: reassign -1 systemd-shim Control: forcemerge 903295 -1 On 8/28/18 18:56, Robbie Harwood wrote: > Package: libpam-systemd > Version: 238-5 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > (This bug has been reported also against systemd-shim: >

Bug#907409: casync: FTBFS with glibc 2.28, header mismatch wih new renameat2()

Control: forwarded -1 https://github.com/systemd/casync/issues/166 Hi Steve On 8/27/18 19:00, Steve Langasek wrote: > Package: casync > Version: 2+20180321-2 > Severity: normal > Tags: patch > User: ubuntu-de...@lists.ubuntu.com > Usertags: origin-ubuntu cosmic ubuntu-patch > > Dear

Bug#905454: It's happened again

On 8/23/18 00:36, Michael Biebl wrote: > On 8/22/18 08:58, Jaap Keuter wrote: >> This time including boot info added as requested. > > Hm, nothing really interesting in there which would give a clue. > > That said, I notice that you still have consolekit installed. > P

Bug#904125: systemd: system startup stops unless root logs in in text mode

Control: reassign -1 sddm Control: forcemerge 898092 -1 Am 20.07.2018 um 10:44 schrieb Ara Keary: >>> Indeed, typing random characters did the job: the system startup >>> continues after enough entropy is created, >>> thanks, >> >> Ok, thanks for confirming. Are you using kdm or sddm? >> Is this

Bug#904125: systemd: system startup stops unless root logs in in text mode

Am 20.07.2018 um 08:31 schrieb Ara Keary: > Package: systemd > Version: 239-6 > Severity: important > > Dear maintainers, > > since upgrading to systemd 239-6, my systems stops during startup, at a text > mode login prompt. Switching to other consoles with alt+ctrl+F1-8 gives no > graphical

Bug#749832: systemd: ignores /run/do-not-hibernate, hibernates after kernel update

On Thu, 29 May 2014 19:11:25 -0700 Nikolaus Rath wrote: > Package: systemd > Version: 204-8 > Severity: grave > Justification: causes non-serious data loss > > 'systemctl hibernate' (and probably other methods to hibernate when > systemd is installed, I tested only the command) hibernates the

Bug#903902: systemd: vlan-id is not reconfigured when restarting systemd-networkd

Control: forwarded -1 https://github.com/systemd/systemd/issues/9627 Am 17.07.2018 um 22:44 schrieb Sebastian Stellingwerff: > Done: https://github.com/systemd/systemd/issues/9627 Thanks, marking the bug report accordingly. > If this gets fixed upstream, will the fix move back to stretch?

Bug#903219: Acknowledgement (journald crashes)

Control: forwarded -1 https://github.com/systemd/systemd/issues/9538 On Sun, 08 Jul 2018 23:05:52 +0200 Yuri D'Elia wrote: > After further debugging I figured this seems to be related to the > internal watchdog. I filed a bug report upstream: > > https://github.com/systemd/systemd/issues/9538

Bug#903807: deb-systemd-helper purge breaks services duplicated between conflicting packages

Am 15.07.2018 um 18:14 schrieb Richard Laager: > On 07/15/2018 04:22 AM, Michael Biebl wrote: >> Fwiw, I think it would be better if ntpsec and ntp would not use the >> same service file name and if ntpsec would use ntpsec.service instead. > > Are you willing to e

Bug#902910: systemd: error message during boot: ...glance.service:3: Invalid URL

Control: reassign -1 glances Control: found -1 2.11.1-5 Am 03.07.2018 um 13:54 schrieb mh: > message during boot: /lib/systemd/system/glances.service:3: Invalid URL > Ignoring (1) That's a bug in the glances service file, thus re-assigning to the correct package Documentation=man:glances (1)

Bug#898530: reducing timesync errors

On Sun, 13 May 2018 13:47:25 +0800 =?utf-8?B?56mN5Li55bC8?= Dan Jacobson wrote: > Package: systemd > Version: 238-4 > Severity: minor > > Upon connecting to the Internet one sees > > (1) systemd-resolved[482]: Server 127.0.0.1 does not support DNSSEC, > downgrading to non-DNSSEC mode. > (2)

Bug#902026: systemd: "systemctl start systemd-timesyncd.service" kills chrony

Am 23.07.2018 um 19:53 schrieb Francesco Poli: > Control: reopen -1 > Control: retitle -1 systemd: systemd-timesyncd should not run, when chronyd > is running > > > On Fri, 22 Jun 2018 23:46:57 +0200 Francesco Poli wrote: > > [...] >> I'll try to keep an eye on the two daemons, to find out

Bug#810608: systemd-sysv: on shutdown, fails to inform users that the system is going down

Control: forwarded -1 https://github.com/systemd/systemd/issues/3700 Am 21.07.2018 um 20:07 schrieb Francesco Poli: > On Sat, 21 Jul 2018 01:21:52 +0200 Michael Biebl wrote: > > [...] >> For remote logins, it might be useful. > > Exactly: it is useful to figure out why yo

Bug#904198: udev 239 breaks network interface naming

Control: forwarded -1 https://github.com/systemd/systemd/issues/9688 Am 21.07.2018 um 14:51 schrieb Wolfgang Walter: > Package: udev > Version: 239-1 > Severity: important > > After upgrading from 238-5 to 239-1 or higher my network setup breaks. > > Basically all interfaces which do NOT have a

Bug#903219: Acknowledgement (journald crashes)

On Wed, 18 Jul 2018 15:55:50 +0200 Michael Biebl wrote: > Control: forwarded -1 https://github.com/systemd/systemd/issues/9538 > > On Sun, 08 Jul 2018 23:05:52 +0200 Yuri D'Elia wrote: > > After further debugging I figured this seems to be related to the > > internal wa

Bug#904285: nss-mymachines: /etc/nsswitch.conf ordering

Hi Am 22.07.2018 um 19:44 schrieb Christoph Anton Mitterer: > When libnss-mymachines it automatically adds the respective > entries to /etc/nsswitch.conf and it seems to place > "mymachines" after "dns". > > This is IMO bad (and actually even a security hole), as it would > resolve DNS names

Re: Bug#892945: Cannot start domain using user session

Control: retitle -1 Please drop 60-qemu-system-common.rules Control: tags -1 + patch Am 23.07.2018 um 09:08 schrieb Guido Günther: > Hi, > On Tue, Jul 10, 2018 at 12:06:13AM +0200, Michael Biebl wrote: >> Am 09.07.2018 um 20:37 schrieb Ben Hutchings: >> >>> It is fair

Bug#904335: systemd-resolved.service: Couldn't add UID/GID reference to unit, proceeding without: Device or resource busy

Am 23.07.2018 um 14:21 schrieb Ryutaroh Matsumoto: > Package: systemd > Version: 239-7 > Severity: minor > > Dear Maintainer, > > journalctl -l -u systemd-resolved.service includes the following line: > > Jul 23 12:02:57 debian-unstable systemd[1]: systemd-resolved.service: > Couldn't add

Bug#904079: systemd: tmpfiles: cleaning up /tmp at boot breaks things

Am 19.07.2018 um 11:47 schrieb Arnaud Rebillout: > Package: systemd > Version: 239-5 > Severity: normal > > Dear Maintainer, > > At the moment Debian carries a patch against /usr/lib/tmpfiles.d/tmp.conf > This patch sets the type for `/tmp` to `D`, causing the content of the > directory to be

  1   2   3   4   5   6   7   8   9   10   >