Re: systemd 230-7~bpo8+2 (bug causes shutdown freeze)

On Sun, 09 Jul 2017 at 00:30:49 +, garnut992-deb...@yahoo.com wrote: > It says on the Debian Backports webpage (https://backports.debian.org/) > that "backports are packages taken from the next Debian release (called > "testing")." So I'm confused, why can't this be updated from testing? Is > i

Re: systemd 230-7~bpo8+2 (bug causes shutdown freeze)

On Sat, 08 Jul 2017 at 07:20:40 +, garnut992-deb...@yahoo.com wrote: > There is a serious bug is systemd 230-7~bpo8+2 in jessie-backports that > causes the shutdown procedure to hang/freeze, if you have a encrypted disk. If I'm reading the bug correctly, this is more specifically a bug in ud

Re: Bug#854911: dbus fails to start on package installation on very minimal systems

Control: tags -1 wontfix On Sun, 12 Feb 2017 at 00:47:39 +0100, Michael Biebl wrote: > Am 12.02.2017 um 00:39 schrieb Alexander Kurtz: > > The crucial point was, that the package > > installation must happen *before* systemd considers the system fully > > booted, i.e. by installing the package ins

Re: Bug#854911: dbus fails to start on package installation on very minimal systems

On Sat, 11 Feb 2017 at 21:38:42 +0100, Alexander Kurtz wrote: > I have marked this as serious since I experienced other packages (i.e. > avahi-daemon) failing to install because of this. However, please feel > free to downgrade the severity if you think it's appropriate! I'm not sure whether this

Bug#851747: sysvinit-utils: unmaintained package should not be Essential

Package: sysvinit-utils Version: 2.88dsf-59.8 X-Debbugs-Cc: init-system-help...@packages.debian.org, debianut...@packages.debian.org sysvinit appears to be unmaintained, but it builds an Essential package (sysvinit-utils) that must be installed on all Debian systems. This seems like a bad situati

Bug#846944: Installing libnss-resolve before libnss-mdns breaks mDNS name resolution

Control: clone 846944 -2 Control: reassign -2 libnss-mdns 0.10-7 On Thu, 08 Dec 2016 at 15:20:34 +0100, Michael Biebl wrote: > With multiple packages mangling nsswitch.conf, this feels like it's > becoming very brittle and maybe we need a proper API like pam-auth-update. That would be nice, but l

Bug#845161: udev: "mount: invalid option --" when busybox is not installed

On Mon, 21 Nov 2016 at 10:16:50 +, Luca Boccassi wrote: > The context is a squashfs and liveboot/build based ISO. ... > I don't pick the mount utility in any of my scripts or configs, so I do > not know when or where the change happened, could have been anytime > since Jessie was released. But

Bug#845161: udev: "mount: invalid option --" when busybox is not installed

On Mon, 21 Nov 2016 at 09:50:39 +0100, Martin Pitt wrote: > Michael Biebl [2016-11-21 1:15 +0100]: > > Am 21.11.2016 um 00:50 schrieb Simon McVittie: > > > Because udev's initramfs hook now does "mount --move", it doesn't work > > > with >

Bug#845161: udev: "mount: invalid option --" when busybox is not installed

Package: udev Version: 232-5 Severity: important To reproduce: * Build a minimal sid qemu virtual machine for autopkgtest as described in autopkgtest-virt-qemu(1) * Have udev 232-5 (232-4 not tested but should also be affected) * Boot the system Because udev's initramfs hook now does "mount --

Bug#841914: init-system-helpers: please drop dh-systemd transitional package now produced by src:debhelper

Source: init-system-helpers Version: 1.38 Severity: normal src:init-system-helpers produces a dh-systemd transitional binary package versioned 1.x. Since debhelper 10.1, debhelper has also produced a dh-systemd transitional binary package, versioned 10.x. As a result, init-system-helpers' lesser-v

Bug#841740: systemd periodically kills gnome-terminal session

On Sun, 23 Oct 2016 at 16:30:29 +0200, Michael Biebl wrote: > Am 23.10.2016 um 01:18 schrieb luke: > > Oct 22 23:41:42 donbot systemd[1087]: Starting GNOME Terminal Server... > > Oct 22 23:41:42 donbot dbus-daemon[20090]: Successfully activated service > > 'org.gnome.Terminal' > > Oct 22 23:43:12

Bug#833849: systemd: localed fails to start if /etc/default/keyboard is missing

o review :-) S >From d19610c131ba9b317f2ee3b7c142aa193529c6ee Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Mon, 8 Aug 2016 19:26:42 +0100 Subject: [PATCH] x11_read_data: tolerate absence of /etc/default/keyboard Signed-off-by: Simon McVittie --- src/locale/keymap-util.c | 6 +- 1 file changed,

Bug#822996: systemd: Shutdown/reboot hang and eventually complete

Control: retitle 822996 systemd: shutdown takes multiple minutes: A stop job is running for Avahi mDNS/DNS-SD Stack On Sat, 30 Apr 2016 at 01:44:16 +0630, Kyaw Thu Soe wrote: > The system nevertheless is sometimes randomly and intermittently taking > 2 to 3 minutes to reboot/shutdown. ... > After

Re: Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

On Fri, 16 Oct 2015 at 20:45:35 +0100, Simon McVittie wrote: > The systemd maintainers wondered whether this might be > https://bugs.debian.org/801354 which had similar symptoms. https://bugs.debian.org/794723 is another possibility. I haven't seen any other reports of this behavi

Re: Bug#794723: Policykit crashes systemd

On Sun, 11 Oct 2015 at 14:28:41 +0100, Simon McVittie wrote: > I can reproduce something very like this in a smaller stretch VM After upgrading to current stretch package versions and rebooting (to rule out #801354), I can still reproduce the "Connection timed out" messages (appare

Re: Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

Control: tags 801425 + unreproducible Control: block 801425 by 801354 On 16/10/15 20:03, Gabriel Filion wrote: > fwiw, dbus was upgraded again to 1.10.0-3 and later I downgraded > policykit-1 to 0.105-12, the version from sid. And I haven't seen the > same kind of error reproducing. Did you upgra

Re: Bumping dbus depends (Re: systemd-boot (Re: PR: fsateler/coredump))

On 14/10/15 14:21, Michael Biebl wrote: > CCed Simon for this thoughts on this. Maybe it's too early to move the > policy files around Please keep policy files in /etc/dbus-1/s*.d until I work out what needs to be done to make it safe to move them. S

Re: Bug#794723: Policykit crashes systemd

On Wed, 05 Aug 2015 at 19:37:47 -0400, Carlos Kosloff wrote: > I am installing a fresh version of testing, no desktop, just standard system > utilities in a VM, the underlying software is virtualbox (from Oracle) > Version 5.0.0r101573. > After a dist-upgrade I installed xserver-xorg and then proce

Re: Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

On 10/10/15 17:38, Gabriel Filion wrote: > Laptop was booted and working fine since previous afternoon. > The upgrade/dist-upgrade that brought in dbus 1.10.0-3 was done on the > morning of oct 9th around 7:something, then I shutdown around 8:00, and > booted again around 9:40 and I was seeing the

Re: Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

On 10/10/15 13:17, Simon McVittie wrote: > some bad interaction going on between recent systemd, policykit-1 and dbus Any recent warning/error messages in your syslog from those three components would also be interesting. S ___ Pkg-syst

Re: Bug#801425: dbus: upgrade from dbus 1.10.0-2 to 1.10.0-3 breaks policykit

Control: tags 801425 + moreinfo On 10/10/15 00:51, Gabriel Filion wrote: > I'm running sid and this morning I performed an apt-get upgrade and a > dist-upgrade. This pulled in dbus 1.10.0-3. I'm surprised by the upgrade from 1.10.0-2 to 1.10.0-3 having an effect, because very little changed betwe

Re: Bug#783321: systemd opens file in /var/run and not in /run

On 26/04/15 13:12, Dmitry Katsubo wrote: > Indeed other files could be opened from /var, but in single mode that > is very limited. The only service that lock it is NFS mount (rpcbind). > And I can always stop these services, thus allowing me to unmount > /var. But that is not the case with process

Re: Bug#783321: systemd opens file in /var/run and not in /run

On 25/04/15 23:36, Michael Biebl wrote: > Simon, do you expect any breakage if we move the socket file to /run? > /var/run should typically be a symlink to /var/run, so it should still > be accessible under the old name. /var/run/dbus/system_bus_socket is the canonical interoperable path, hard-cod

Re: Bug#622394: systemd: nfs-common and rpcbind unit files to fix systemd NFS issues properly

Control: clone 622394 -2 -3 Control: retitle -2 NFS mounts from /etc/fstab do not work Control: submitter -2 m...@mattgrant.net.nz Control: retitle -3 NFS exports fail due to rpcbind not starting before nfs-common and nfs-kernel-server Control: submitter -3 m...@mattgrant.net.nz Control: tags -3 m

Bug#770504: systemd: log all members of cyclic dependencies (loops)

On Fri, 05 Dec 2014 at 07:27:35 +0100, Martin Pitt wrote: > But still exists in unstable's/testing's 215 version, but < important > bugs don't qualify for jessie any more as per freeze policy. If > someone wants to convince the release team, by all means go ahead, of > course -- I'm happy to cherry

Bug#773183: (pre-approval) unblock: systemd with #770504 fixed

Package: release.debian.org Severity: wishlist User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: pkg-systemd-maintainers@lists.alioth.debian.org Would you be willing to let the systemd maintainers cherry-pick the attached into a jessie-targeted version? It is a trivial

Re: vt2-6 still not available with base system

On 12/12/14 16:55, Michael Biebl wrote: > Am 12.12.2014 um 17:18 schrieb Simon McVittie: >> Any reason not to prefer "Wants=getty@tty2.service ... >> getty@tty6.service" and "ExecStart=/bin/true"? > > The issue apparently is, that Conditions are evaluate

Re: vt2-6 still not available with base system

On 12/12/14 15:26, Michael Biebl wrote: > Since apparently Conditions can't be used on targets, I came up with a > slightly different idea, using a service, which triggers the start of > getty on tty2-6 in absence of /usr/bin/dbus-daemon. Any reason not to prefer "Wants=getty@tty2.service ... gett

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

Control: reassign 760142 dbus Control: forcemerge 769069 760142 On 01/12/14 19:58, Andreas Messer wrote: > Am Sonntag, den 23.11.2014, 14:43 +0100 schrieb Andreas Messer: >> Am Samstag, den 22.11.2014, 10:20 + schrieb Simon McVittie: >>> That effectively reverts the probl

Re: The inittab interface - Re: Bug#766187: runit: Fails to install runit after fresh install of jessie beta2

On 24/11/14 21:41, Gerrit Pape wrote: > Better than (2) would be to make the existence of /etc/inittab still > essential for jessie, by moving the corresponding code from > sysvinit-core into the essential init package. What do you think? If you go this route, I think initscripts might be a bette

Bug#761951: systemd: Did not start network in default

On Mon, 22 Sep 2014 at 15:30:00 +0900, K.Ohta wrote: > 007_dump_network.txt.lz : systemd-analyze dump (lzipped). I tried using my script from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763315 to find the dependency cycles, but its answers make no sense, because neither do the dependencies i

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

On Wed, 19 Nov 2014 at 21:29:33 +0100, Andreas Messer wrote: > I'm observing the same behavior on an x86_64 wheezy system running my > HTPC setup after updating the system some weeks ago. Andreas, I think your bug is #769069, which is a recent regression: your system is presumably much less slow t

Bug#770504: systemd: log all members of cyclic dependencies (loops)

Control: tags 770504 + patch fixed-upstream On Sat, 22 Nov 2014 at 00:53:46 +0100, Zbigniew Jędrzejewski-Szmek wrote: > C.f. http://cgit.freedesktop.org/systemd/systemd/commit/?id=14fe721b5f6d Thanks! Corresponding patch attached. S >From 14fe721b5f6d8457cc8737fa75f2ed79e7fa534b Mon Sep 17 0

Bug#770504: systemd: log all members of cyclic dependencies (loops)

Package: systemd Version: 215-6 Severity: wishlist (Bug carefully titled to include both "cycl" and "loop" since those are the searches I've been using to find related bugs :-) Looking at , which involved a cyclic dependency: systemd logs that there was a loop, and

Re: systemd LSB compat vs. $network and the rc2/rcS distinction

On 21/11/14 13:49, Patrick Matthäi wrote: > please CC me in your e-mails, I'm not subscribed to this list. (Same for me.) > Am 20.11.2014 um 17:31 schrieb Simon McVittie: >> It seems to me as though your dependency cycle is caused by >> vmware-tools.service. ... >&g

Bug#763315: systemd: Dependency loop between basic.target, nfs-common, rpcbind, ...

On Mon, 29 Sep 2014 at 11:06:06 +0200, Laurent Bigonville wrote: > Apparently there is still some kind of loop here. Piping the output of the attached script to tsort(1) says: tsort: -: input contains a loop: tsort: firewalld.service tsort: network.target tsort: network-online.target tsort: rpcbi

Bug#769069: systemd: Failed to start Login Service

On 15/11/14 00:16, Paul Menzel wrote: > Am Freitag, den 14.11.2014, 10:18 + schrieb Simon McVittie: >> It looks as though the system might have been having performance >> issues in general: ... >> which might have contributed to timeouts, possibly? I happened to notice

Bug#769069: systemd: Failed to start Login Service

Unfortunately I don't see a "smoking gun" in your log. It looks as though the system might have been having performance issues in general: On 13/11/14 23:36, Paul Menzel wrote: > Nov 11 07:45:44 asrock-e350m1 systemd[1]: Looping too fast. > Throttling execution a little. which might have contri

Bug#769069: systemd: Failed to start Login Service

On 12/11/14 13:33, Michael Biebl wrote: > Not quite, all it shows is that the problem is most likely in dbus and > not systemd itself. Based on the log you quoted, I'm not sure I agree. The problem is certainly in the interaction between dbus and systemd, but it doesn't look as though systemd is d

Re: vt2-6 still not available with base system

On 09/11/14 18:56, Michael Biebl wrote: > Running for i in `seq 2 6` ; do systemctl enable > getty@tty$i.service; done on a system without dbus, would > statically enable a getty on vt2-6. So we could simply document > this fact (in README.Debian, release notes etc). I'm very tempted to say system

Re: git-dpm vs gbp-pq: new upstream and patch refresh (long)

On 05/09/14 15:53, Barry Warsaw wrote: > On Sep 05, 2014, at 01:21 PM, Simon McVittie wrote: > >> It might also be worth noting that the systemd maintainers switched from >> git-dpm to gbp-pq recently (between 204 and 208, I think), so they >> obviously didn't think

Bug#758111: installation-reports: Please consider dbus for the core files

On 05/09/14 06:04, Michael Biebl wrote: > Am 20.08.2014 14:50, schrieb Michael Biebl: >> Since systemd already depends on libdbus-1-3, I'd bump >> libdbus-1-3 to important and dbus to standard. Does that sound >> ok? > > Just a quick followup: Since systemd v209 and later no longer uses > libdbus

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

Chris, your Debian root filesystem appears to be on a USB-attached disk (device ID 067b:2507, which according to seems to be a "Prolific Technology, Inc. PL2507 Hi-speed USB to IDE bridge controller"). Please confirm whether this is the case? (Rele

Bug#760168: dh-systemd: support for -X option

On 02/09/14 08:34, Michael Stapelberg wrote: > Did you try whether it actually works already? Yes I did, and no it doesn't. > In dh_compress and dh_fixperms I see -X is documented but I don’t see > special code to support it. Library code in Debian::Debhelper parses -X options and $DH_ALWAYS_EXC

Bug#760142: systemd: Assertions from systemd-logind on powerpc during login, with continuing loop

On 01/09/14 22:55, Chris Tillman wrote: > Sep 02 09:44:00 debian dbus[767]: [system] Failed to activate service > 'org.freedesktop.Avahi': timed out > Sep 02 09:44:01 debian dbus[767]: [system] Failed to activate service > 'org.freedesktop.PolicyKit1': timed out > Sep 02 09:44:25 debian dbus[767]:

Bug#760168: dh-systemd: support for -X option

Package: dh-systemd Version: 1.21 Severity: wishlist debhelper(7) says: COMMON DEBHELPER OPTIONS The following command line options are supported by some debhelper programs [...] -Xitem, --exclude=item Exclude an item from processing. This option may be used multip

Re: Bug#759293: override: dbus:admin/important or :admin/standard

On 25/08/14 22:30, Ansgar Burchardt wrote: > Please increase the priority of dbus to important or standard (not sure > which): it is needed by systemd-logind. If dbus is not available, > systems running systemd will not spawn gettys on tty2-6 by default. 'important' seems excessive. I don't think

Bug#758914: [dbus] Refuses to complete installation, blocking other pkgs

On 23/08/14 16:30, B wrote: > This raises a question: shall I assume that systemd will turn > machines administration into a kinda ISO-9001 long and painful > procedures to _absolutely_ apply, with a "sanction" each > time things aren't completely right? (and if so, will there > be an alternat

Bug#758914: [dbus] Refuses to complete installation, blocking other pkgs

On 23/08/14 15:57, B wrote: > Effectively, I did not care formerly because it caused no problem, > but it was tagged 'auto'. To be clear: that's "auto" in the filesystem column, i.e. automatically detect a filesystem. "auto" (the default) or "noauto" in the options column (the one with "user"

Bug#758914: [dbus] Refuses to complete installation, blocking other pkgs

On 23/08/14 14:29, B wrote: > Hmm, -ba was refused (Failed to parse boot descriptor 'a') but -ab > was accepted (sounds normal from the man point of view) - > journal.txt is attached. Yes, my mistake, -ba is parsed as "messages from the boot named 'a'"; -ab or -a -b is "unabbreviated messages

Bug#758111: [Pkg-utopia-maintainers] installation-reports: Please consider dbus for the core files

On Thu, 14 Aug 2014 at 13:24:34 +0200, Michael Biebl wrote: > Two possible outcomes then > > 1/ Make systemd recommend/depend on dbus (recommend would probably be > sufficient) According to the initial bug report, the base system is installed without Recommends, so no, Recommends is not sufficien

Bug#753589: systemd: missing pre-dependencies for runlevel(8) etc.

Policy says new Pre-Depends should be discussed on debian-devel so let's try that. (Please do not derail this thread into discussing whether systemd is a good thing or not, everyone is tired of that.) Quick summary of #753589 for debian-devel readers: Essential:yes packages are expected to provide

Bug#754404: /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory

On 13/07/14 09:51, Michael Biebl wrote: > Now that I think of it, that looks like a bug in the dbus.postinst. > > Since it installs a file trigger, it should guard the reload > accordingly, i.e. when being triggered do the reload only and then exit. Feel free to reassign to dbus and commit the di

Bug#754404: /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory

severity 754404 minor thanks On 10/07/14 21:51, Michael Biebl quoted: >> Processing triggers for dbus (1.8.6-1) ... >> /usr/sbin/invoke-rc.d: line 288: /sbin/runlevel: No such file or directory >> [] system message bus already started; not starting.?25l1G[32m ok >> 39;49m?12l?25h. For what i