MBF for libsystemd transition

Hi everyone! I just did a mass bug filing for the transition from the split libsystemd-*-dev packages to libsystemd-dev. The bugs are usertagged and can be found at [1] Cheers, Michael [1] https://bugs.debian.org/cgi-bin/pkgreport.cgi?users=pkg-systemd-maintainers@lists.alioth.debian.org;tag=li

Bug#779902: /tmp can be mounted as tmpfs against user's will

Am 06.03.2015 um 10:10 schrieb Martin Pitt: > Control: found -1 215-12 > Control: tag -1 confirmed > > Ça va Didier, > > Didier Roche [2015-03-06 9:36 +0100]: >> In debian, tmp.mount is disabled through a distro-patch by default. It means >> we don't want user's system to get /tmp on tmpfs witho

Bug#779902: /tmp can be mounted as tmpfs against user's will

Am 06.03.2015 um 16:04 schrieb Michael Biebl: > I think, PrivateTmp=yes pulling in tmp.mount is a bug and I would simply > revert b46a529c [1] or replace unit_require_mounts_for with a After > dependency [2] only. The check to add a hard Requires Dependency, is to test for a fragmen

Bug#770644: systemd: can't start dbus if dbus is not running

control: tags -1 moreinfo Am 22.11.2014 um 23:33 schrieb brian m. carlson: > retitle 770644 systemd: systemd is completely unusable after a fatal signal > # Justification: breaks the whole system, not suitable for release > severity 770644 serious > kthxbye > > On Sat, Nov 22, 2014 at 09:34:03PM

Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv

Am 08.03.2015 um 14:37 schrieb Paul Wise: > Package: init > Version: 1.22 > Severity: important > X-Debbugs-CC: debian-rele...@lists.debian.org, Ansgar Burchardt > , syst...@packages.debian.org > > I found an upgrade[1][2] path where sysvinit-core is installed instead > of systemd-sysv, while wit

Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv

Am 08.03.2015 um 21:43 schrieb Michael Biebl: > Am 08.03.2015 um 14:37 schrieb Paul Wise: >> Package: init >> Version: 1.22 >> Severity: important >> X-Debbugs-CC: debian-rele...@lists.debian.org, Ansgar Burchardt >> , syst...@packages.debian.org >> >>

Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv

Am 09.03.2015 um 03:24 schrieb Paul Wise: > On Sun, 2015-03-08 at 21:43 +0100, Michael Biebl wrote: > >> I don't see, how this is a bug in init and what we should do about this. >> Can you elaborate why you filed this against init? > > I wasn't sure which package

Bug#780028: init: aptitude upgrade from wheezy to jessie does not install systemd-sysv

Am 09.03.2015 um 08:55 schrieb Axel Beckert: > Hi, > > Michael Biebl wrote: >>> Whether or not one should use aptitude flips around between releases so >>> I believe people will be using it whether or not we recommend it for a >>> particular release. > &g

Bug#780235: "man init" brings up systemd(8) despite /sbin/init coming from sysvinit-core

control: severity -1 minor Am 10.03.2015 um 23:59 schrieb Samuel Bronson: > Package: systemd > Version: 215-12 > Severity: important > File: /usr/share/man/man1/systemd.1.gz > > Dear Maintainer, > > When I run "man init", I expect to see the manpage corresponding to > /sbin/init; since /sbin/ini

Bug#739814: Fix systemd description in systemd-ui control file

Hi Scott! Am 12.03.2015 um 22:19 schrieb Scott Wakeling: > Hi, > > I was looking for an easy target for my first bug fix when I came > across this and #773830. > > The attached diff closes both. The wording is as agreed above, > and 'apt-cache search systemadm' now returns systemd-ui as a result.

Bug#739814: Fix systemd description in systemd-ui control file

control: tags -1 + pending control: tags 773830 + pending Am 12.03.2015 um 23:32 schrieb Scott Wakeling: >> Can you group the compat information in a separate paragraph as >> suggested by Filipus? I'd say between the general paragraph about >> systemd and the paragraph about systemadm at the end.

Bug#780504: Fix systemd descriptions in debian/control

Source: systemd Version: 215-12 Severity: minor Tags: patch let's turn this into a bug report, so we can track this properly Weitergeleitete Nachricht Betreff: Bug#740372: Fix systemd descriptions in debian/control Weitersenden-Datum: Fri, 13 Mar 2015 23:18:01 + Weitersende

Bug#780520: systemd-sysv: computer restarts after shutdown if connected to an external display

Control: tags -1 moreinfo unreproducible Control: severity -1 normal Hi! Am 15.03.2015 um 15:02 schrieb Harven: > I am using debian jessie with the kde desktop. > When my laptop (HP probook 650) is connected to an external screen, > I can't shutdown properly. When I halt the computer, either usi

Bug#780520: systemd-sysv: computer restarts after shutdown if connected to an external display

For testing purposes, can you install the "sysvinit" package, run update-grub, then choose the sysvinit option in the grub advanced option on next reboot. Does the problem happen under sysvinit as well? -- Why is it that all of the instruments seeking intelligent life in the universe are point

Bug#762343: systemd: timesyncd should run in VMware

Control: tags -1 fixed-upstream Control: forwarded -1 http://lists.freedesktop.org/archives/systemd-devel/2015-March/029427.html Am 20.09.2014 um 21:47 schrieb Christian Hofstaedtler: > Package: systemd > Version: 215-4 > Severity: normal > > Dear Maintainers, > > timesyncd carries a setting of

Bug#740372: Fix systemd descriptions in debian/control

Control: forcemerge 780504 740372 Am 15.03.2015 um 20:49 schrieb Scott Wakeling: >> let's turn this into a bug report, so we can track this properly > > Isn't 740372 already tracking this issue against the systemd package? Oh, right. Let's merge the two then. Thanks for noticing. -- Why is

wpa_supplicant.service needs Before=network.target to ensure proper ordering on shutdown

Package: wpasupplicant Version: 2.3-1 Severity: important Hi, please add a Before=network.target dependency to the [Unit] section of wpa_supplicant.service. This ensures, that wpa_supplicant is stopped on shutdown *after* remote mount points have been unmounted. See also the discussion at [1]. P

Bug#780520: systemd-sysv: computer restarts after shutdown if connected to an external display)

Control: reassign -1 linux-image-3.16.0-4-amd64 Am 16.03.2015 um 10:16 schrieb har...@free.fr: >> For testing purposes, can you install the "sysvinit" package, >> run update-grub, then choose the sysvinit option in the grub advanced >> option on next reboot. > >> Does the problem happen under sys

Bug#777164: systemd: libvirt cgroups start to disappear from machine.slice after systemctl daemon-reload

Am 15.03.2015 um 12:33 schrieb Christian Seiler: > Control: severity -1 serious > Control: tags -1 + patch > > Dear Maintainers, > > this doesn't only affect libvirt/KVM somewhat, but it also breaks LXC, > which also uses its own cgropus. lxc-attach will stop working once > systemctl daemon-reloa

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

control: tags -1 moreinfo control: tags -1 unreproducible Am 17.03.2015 um 18:14 schrieb Robert Pumphrey: > Package: systemd > Version: 215-12 > Severity: critical > Justification: breaks the whole system > > Dear Maintainer, > > running systemctl daemon-reload causes systemd to segfault : > >

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Am 17.03.2015 um 18:52 schrieb Michael Biebl: > gdb --core=/core /lib/systemd/systemd > > The type "set logging on" and run "bt full" afterwards, hit return until the gdb prompt shows up again and attach > gdb.txt to the bug report. -- Why is it tha

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Am 17.03.2015 um 19:05 schrieb Robert Pumphrey: > > > On 17/03/15 17:52, Michael Biebl wrote: >> control: tags -1 moreinfo >> control: tags -1 unreproducible >> >> Am 17.03.2015 um 18:14 schrieb Robert Pumphrey: >>> Package: systemd >>> Versi

Bug#780636: (no subject)

control: tags -1 moreinfo Am 17.03.2015 um 10:42 schrieb Christoph Pleger: > > after changing the configuration of my eth0 network interface from > network-manager-configured (with dhcp) > to statically configured by creating a file /etc/network/interfaces.d/eth0 > with > > auto eth0 > iface e

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Am 17.03.2015 um 19:05 schrieb Robert Pumphrey: > > > On 17/03/15 17:52, Michael Biebl wrote: >> control: tags -1 moreinfo >> control: tags -1 unreproducible >> >> Am 17.03.2015 um 18:14 schrieb Robert Pumphrey: >>> Package: systemd >>> Versi

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Am 17.03.2015 um 19:35 schrieb Michael Biebl: > Am 17.03.2015 um 19:05 schrieb Robert Pumphrey: >> #0 0x7f8d3e06779b in raise (sig=11) at >> ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37 >> resultvar = 0 >> pid = >> #1 0x7f8d3e4bd3d8

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Am 17.03.2015 um 23:02 schrieb Robert Pumphrey: > I have identified a duff init.d script (one of our own that previously > worked in wheezy) that is at the root of this problem. I have removed > the script, rebooted and the I can now run systemctl daemon-reload > withough a seg fault. > This bug m

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Control: tags -1 = confirmed Control: severity -1 serious Am 18.03.2015 um 16:29 schrieb Robert Pumphrey: > 2. put the following into /etc/init.d/firewall > #!/bin/bash > ### BEGIN INIT INFO > # Provides: iptables > # Required-Start:$network $remote_fs $syslog > # Required-Stop:

Bug#780675: systemd: segfault in systemd when running systemctl daemon-reload

Control: fixed -1 219-4 Am 18.03.2015 um 18:00 schrieb Michael Biebl: > Thanks for sharing the contents of the file. I can confirm the crash and > we have enough information now to debug this issue properly. > Marking the bug accordingly. Can't reproduce the issue with th

Bug#780705: udev: floating net device number on devices with ro rootfs

Am 19.03.2015 um 04:34 schrieb You-Sheng Yang: > On Wed, 18 Mar 2015 18:46:00 +0100 Michael Biebl wrote: >> Dear You-Sheng Yang, >> >> first of all, the bug report was filed against the wrong package. The >> package dealing with the network renaming is udev. There

Bug#755722: systemd must sync systemclock to RTC on shutdown

Am 19.03.2015 um 09:03 schrieb pav ka: > root@pa:/var/log# cat /etc/debian_version > 8.0 > > > root@pa:/var/log# cat daemon.log | grep fsck > Mar 17 06:15:15 pa systemd-fsck[170]: root: Superblock last write time is > in the future. > Mar 17 06:15:15 pa systemd-fsck[170]: (by less than a day, pro

Bug#769356: netfilter-persistent.service shouldn't require systemd-modules-load.service

control: tags -1 moreinfo On Wed, 12 Nov 2014 16:28:47 -0700 Rother That wrote: > Package: netfilter-persistent > Source: iptables-persistent > Version: 1.0.2 > Severity: important > Tags: jessie > > I'm running Debian Jessie on Linode's kernel on multiple VM. It works > great. However, I starte

Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable

Am 09.03.2015 um 08:48 schrieb Julien Cristau: > On Sun, Mar 8, 2015 at 12:45:28 +0100, Jonas Meurer wrote: > >> Hi Gordon, >> >> thanks for the bugreport. I escalate this bugreport to the >> debian-release team, asking for advice: would you accept another >> cryptsetup upload targeted to jessie

Bug#770734: How to reproduce

control: reassign -1 intltool Am 29.01.2015 um 20:54 schrieb Lennart Sorensen: > Create jessie chroot (I used debootstrap --variant=buildd jessie jessie) > > Install build-deps for systemd and then build systemd. It works. > > Then do 'touch /usr/bin/intltool-merge' > > Try build again. It fa

Bug#771188: multi-user.target boots to graphical mode

control: reassign -1 kdm control: forcemerge 755359 -1 Am 28.11.2014 um 06:16 schrieb Michael Biebl: > Am 28.11.2014 um 06:10 schrieb Michael Biebl: >> Am 27.11.2014 um 13:39 schrieb Marc Haber: >>> Package: systemd >>> Severity: normal >>> >>> Hi,

Bug#770644: systemd: can't start dbus if dbus is not running

Am 08.03.2015 um 15:30 schrieb brian m. carlson: > On Sat, Mar 07, 2015 at 12:47:33AM +0100, Michael Biebl wrote: >> Can you provide steps how this issue can be reproduced? > > Actually, I just discovered a set of steps on how to reproduce this: > > Run kill -s ABR

Re: [Jessie] Status on the RC bugs in systemd

Am 20.03.2015 um 04:25 schrieb Michael Biebl: > Then there are a few more fixes which are not RC, which we'd like to get in. I forgot https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=759001, which you sort of pre-acked already, so I'd include that in the upload as well -- Why i

Re: [Jessie] Status on the RC bugs in systemd

Am 20.03.2015 um 04:25 schrieb Michael Biebl: > Hi Niels, > > Am 17.03.2015 um 17:25 schrieb Niels Thykier: >> Hi Systemd maintainers, >> >> Can you help me with a status with the following: >> >> * Are there some of the remaining RC bugs that you b

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Am 03.03.2015 um 16:48 schrieb Christian Seiler: > Am 2015-03-03 16:26, schrieb Michael Biebl: >> I did a couple more reboots and did indeed run into the problem, that >> systemd-sysctl.service was started after syslog.socket, so I got the >> "missed XXX messages&q

Bug#776863: Bug#776859: systemd-cron: uninstalling package dumps core and seemingly disturbs systemd

Am 03.02.2015 um 00:24 schrieb Jonas Smedegaard: > Quoting Alexandre Detiste (2015-02-02 18:23:38) >> - most (all ?) packages that depends on cron should instead depends on >> cron-daemon >> backintime-common is on my list: >> http://users.teledisnet.be/ade15809/cron-daemon.html >> >> but th

Bug#779902: /tmp can be mounted as tmpfs against user's will

[adding the bug to CC] Am 20.03.2015 um 08:46 schrieb Didier Roche: > Le 20/03/2015 08:39, Michael Biebl a écrit : >> thanks for the patch. I had something like this in mind. >> We could be extra nice and only add the After=tmp.mount if tmp.mount is >> actually enabled, bec

Bug#776863: Bug#776859: systemd-cron: uninstalling package dumps core and seemingly disturbs systemd

Am 20.03.2015 um 09:59 schrieb Jonas Smedegaard: > Quoting Michael Biebl (2015-03-20 09:07:37) >> Am 20.03.2015 um 09:01 schrieb Jonas Smedegaard: >> >>> Quoting Michael Biebl (2015-03-20 06:38:10) >> >>>> Atm, we don't have nearly enough informatio

Re: [Jessie] Status on the RC bugs in systemd

Am 2015-03-20 03:25, schrieb Michael Biebl: I'll see to it, that I'll get a package ready this weekend for the 4 RC bug fixes at least and maybe include the one for [0]. Bah, my SSD decided to throw bad sectors left and right just a couple of hours ago. I do have a backup

Bug#781151: boot often stalls with two "A start job is running" messages: binfmt and schroot sessions

Control: tags -1 moreinfo Dear Thibaud, Am 25.03.2015 um 10:39 schrieb Thibaut Paumard: > About each time I reboot my computer, boot stalls with two start jobs unable > to > complete: > > A start job is running for Enable support for additional binary formats ([...] > / no limit) > > A start j

Bug#781151: boot often stalls with two "A start job is running" messages: binfmt and schroot sessions

Am 25.03.2015 um 16:55 schrieb Thibaut Paumard: > Le 25/03/2015 14:52, Michael Biebl a écrit : > >> >> If your system hang during boot, please switch to tty9, then save the >> output of >> ps aux >> systemctl list-jobs >> systemd-cgls > > Th

Bug#781151: boot often stalls with two "A start job is running" messages: binfmt and schroot sessions

Am 25.03.2015 um 17:10 schrieb Michael Biebl: > Am 25.03.2015 um 16:55 schrieb Thibaut Paumard: >> Le 25/03/2015 14:52, Michael Biebl a écrit : >> >>> >>> If your system hang during boot, please switch to tty9, then save the >>> output of >>&

Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable

Am 25.03.2015 um 17:40 schrieb Gordon Morehouse: > On 03/25/2015 09:29 AM, Jonas Meurer wrote: > [snip] >> >> Seems like there's some more discussion needed in order to fix the >> reported bug: >> >> a) do we want cryptsetup to recommend plymouth? this way at least >> for manual installation of

Bug#772272: systemd: Journalctl fail to print logs from user session

Am 25.03.2015 um 17:54 schrieb Jameson Graef Rollins: > Package: systemd > Version: 215-12 > Followup-For: Bug #772272 > > I am also experiencing this issue. I have multiple services running > as systemd user services, and I don't have access to the logs of any > of them: > > music@rippy:~ 1$ sy

Bug#779612: [pkg-cryptsetup-devel] Bug#779612: systemd-sysv,cryptsetup: systemd-sysv, cryptsetup should recommend plymouth; without plymouth cryptsetup prompts are unusable

Am 25.03.2015 um 18:04 schrieb Michael Biebl: > New installation, when choosing the LVM+cryptsetup setup, will have a > single cryptsetup prompt, which is run in the initramfs. So new > installations are not affected, i.e, this only affects custom setups. > > As for upgrades, we d

Bug#781287: systemd: dirty pages are no longer flushed

Systemd does not fiddle with those settings. It's more likely a tool like laptop-mode-tools or pm-utils. I suggest looking in that direction. Am 26. März 2015 23:26:19 MEZ, schrieb Simon Richter : >Package: systemd >Version: 215-12 >Severity: normal > >Hi, > >suspecting systemd, as it worked bef

Bug#781151: boot often stalls with two "A start job is running" messages: binfmt and schroot sessions

Am 27.03.2015 um 17:40 schrieb Thibaut Paumard: > Le 27/03/2015 10:33, Thibaut Paumard a écrit : >> >> I'm going to disable binfmt-support, just for checking, and report when >> boot stalls again. >> > > I confirm that even with binfmt-support disabled, boot "stalls". > Actually the system is boot

Bug#781287: systemd: dirty pages are no longer flushed

Control: tags -1 moreinfo unreproducible Am 27.03.2015 um 00:42 schrieb Michael Biebl: > Systemd does not fiddle with those settings. It's more likely a tool like > laptop-mode-tools or pm-utils. I suggest looking in that direction. Did you find anything? -- Why is it that

Bug#762700: systemd: journald fails to forward most boot messages to syslog

Hi Martin, Am 28.03.2015 um 08:15 schrieb Martin Pitt: > Hey Christian, Michael, > > Michael Biebl [2015-03-20 6:25 +0100]: >> So I guess I'll merge your patch as is, including the upstream commit. >> >> I've been running with both patches applied for a whi

Bug#776755: marked as done (systemd: Adding a feature to get systemctl ((re?)start|stop|...) output also on terminal)

Am 29.03.2015 um 04:03 schrieb Debian Bug Tracking System: >> > A good solution would be, I think, to call systemctl ${SERVICE} status just >> > after the restart/start/stop/reload/... command returns (that would be >> > possible >> > if systemctl waits for the end of the reload/... procedure of t

Re: Superblock time check causes problems for fsck in initramfs

Hi Ben! On Mon, 27 Oct 2014 22:51:53 + Ben Hutchings wrote: > Package: e2fsprogs > Version: 1.42.12-1 > Severity: important > Tags: upstream > > We discussed this previously in person, but unfortunately the proposed > solution doesn't work. > > The plan for jessie (yes I know it's late) is

Bug#742802: Bug#771523: systemd: Add build dependency for libmicrohttpd-dev

Am 29.03.2015 um 04:31 schrieb Marco d'Itri: > Control: forcemerge 742802 771523 > > On Nov 30, Michael Biebl wrote: > >> This would also mean a library dependency on libmicrohttpd unless we >> split the package. Both things I'm not particular keen about.

Bug#753790: systemd: process 1 should load new versions of shared objects

Am 05.07.2014 um 05:02 schrieb Michael Biebl: > Am 05.07.2014 04:40, schrieb Michael Biebl: >> I'm not convinced that a package-individual trigger is the right answer >> for this (we also discussed this possibility within the team). Every >> package providing a long ru

Bug#761658: Please do not default to using Google nameservers

Am 29.03.2015 um 06:35 schrieb Christoph Anton Mitterer: > I'm really not inclined to start another security discussion, since > that's already lost cause in Debian... but the appropriate way would be > to reopen this bug, solve it so that no data/privacy leakage happen... > or perhaps to retitle D

Re: Bug#778913: openssh-server: init (at least systemd) doesn't notice when sshd fails to start and reports success

Am 22.02.2015 um 19:45 schrieb Russ Allbery: > That's the problem with forking services that don't have status > notification. The default is Type=simple, which per systemd.service(5): > > If set to simple (the default value if neither Type= nor BusName= > are specified), it is expected t

Bug#765577: netboot install writes duplicates to 70-persistent-net.rules

Control: tags -1 confirmed Am 18.03.2015 um 19:50 schrieb Michael Biebl: > Am 18.03.2015 um 18:52 schrieb Michael Biebl: >> Am 18.03.2015 um 18:15 schrieb Faidon Liambotis: >>> Another less arbitrary/racy workaround I suggesed was a grep near the >>> top of write_net_r

Bug#765577: netboot install writes duplicates to 70-persistent-net.rules

Am 30.03.2015 um 04:56 schrieb Michael Biebl: > Looks like a found a simple reproducer (this is on my work laptop) done > during normal runtime of the system: > > $ rm /etc/udev/rules.d/70-persistent-net.rules > $ while true ; do echo add > /sys/class/net/eth0/uevent ; done &

Re: Bug#778913: openssh-server: init (at least systemd) doesn't notice when sshd fails to start and reports success

Am 30.03.2015 um 01:17 schrieb Michael Biebl: > So I suggest using the Type=forking option but also setting > RestartPreventExitStatus=255 [1], since 255 seems to be the return code > on config errors and I don't think it makes sense to restart in that case. > > The resulti

Bug#618862: systemd: ignores keyscript in crypttab

Am 30.03.2015 um 19:39 schrieb Ivan Jager: > On Mon, Mar 30, 2015 at 11:28 AM, Marco d'Itri wrote: >> I should add some code to preinst to abort the installation if the >> keyscript directive is used in crypttab. > > Would that still leave the system in a broken state though? Is preinst > early e

Re: Superblock time check causes problems for fsck in initramfs

Am 31.03.2015 um 04:14 schrieb Ben Hutchings: > On Sun, 2015-03-29 at 04:29 +0200, Michael Biebl wrote: >> On Mon, 27 Oct 2014 22:51:53 + Ben Hutchings >> I was wondering, if an alternative to disabling the superblock time >> check in e2fsprogs, Well, it dawned to m

Bug#765013: systemd: Spews all over terminal while it's waiting for input

Control: fixed -1 219-1 On Sun, 12 Oct 2014 18:26:52 -0500 John Goerzen wrote: > Package: systemd > Version: 215-5+b1 > Severity: normal > > I've several times had system try to bring up an emergency console and > prompt for password. The prompt for password has been clobbered all > over by, va

Bug#761899: systemd: crash (free(): invalid pointer) while disabling a service

Control: tags -1 moreinfo unreproducible On Tue, 16 Sep 2014 17:42:29 +0200 l.bonn...@laposte.net wrote: > Package: systemd > Version: 215-4 > Severity: important > > > Dear Maintainer, > > to reproduce this problem you need to set the following environment variables: > > MALLOC_CHECK_=3 > MAL

Bug#751845: seems to run fsck twice

Control: tags -1 moreinfo unreproducible Hi, On Tue, 17 Jun 2014 09:29:05 +0200 Michael Meskes wrote: > Package: systemd > Version: 204-10 > Severity: normal > > >From systemd's journal: > > Jun 17 09:19:13 feivel systemd-fsck[636]: /dev/mapper/feivel-home: [...] > [...] > Jun 17 09:19:13 feiv

Bug#781604: `journalctl /dev/sda` shows empty log

Control: severity -1 normal Am 31.03.2015 um 16:08 schrieb Chris Bainbridge: > Package: systemd > Version: 215-12 > Severity: serious > > `man journalctl` says: > > Show all logs of the kernel device node /dev/sda: > >journalctl /dev/sda > > But: > > debian # journalctl /dev/sda >

Bug#781604: `journalctl /dev/sda` shows empty log

Am 31.03.2015 um 16:34 schrieb Chris Bainbridge: >> >> Are you running the command as root? > > Yes. The error if you run journalctl as a regular user is different: > "No journal files were found." Whereas this just shows an empty log. > > This will potentially break any scripts or monitoring too

Bug#781602: systemd: Invalid DBus call causes systemd to stop responding to DBus alltogether

Am 31.03.2015 um 15:52 schrieb Christian Seiler: > Package: systemd > Version: 215-12 > Severity: normal > > Dear Maintainers, > > while I was trying to set a different log level for systemd via DBus, I > accidentally forgot that the 'Set' method for DBus properties expects a > variant as a data

Bug#781615: systemd: Only boots in rescue mode

Am 31.03.2015 um 17:45 schrieb Christoph Egger: > Package: systemd > Version: 215-14 > Severity: important > > Hi! > > This system boots only in rescue mode (and sometimes with > break=premount mount rootfs +Ctrl-D) but never "normally". I have a > full bootlog in debug mode attached. > Hi Chri

Bug#781615: systemd: Only boots in rescue mode

Am 31.03.2015 um 19:07 schrieb Michael Biebl: > Am 31.03.2015 um 17:45 schrieb Christoph Egger: >> Package: systemd >> Version: 215-14 >> Severity: important >> >> Hi! >> >> This system boots only in rescue mode (and sometimes with >> break=pre

Bug#781602: systemd: Invalid DBus call causes systemd to stop responding to DBus alltogether

Control: fixed -1 219-5 Control: tags -1 fixed-upstream Am 31.03.2015 um 17:46 schrieb Christian Seiler: > On 03/31/2015 04:44 PM, Michael Biebl wrote: >> Hm, that's indeed nasty. Have you tried if v219 is affected by this as >> well? If so, it would be worth raising this up

Bug#781615: systemd: Only boots in rescue mode

Am 01.04.2015 um 00:20 schrieb Christoph Egger: > Hi! > > Michael Biebl writes: >> Am 31.03.2015 um 19:07 schrieb Michael Biebl: >>> Am 31.03.2015 um 17:45 schrieb Christoph Egger: >>> >>> That looks odd: While the fsck is running, a reboot w

Bug#781615: systemd: Only boots in rescue mode

Am 01.04.2015 um 14:55 schrieb Christoph Egger: > Hi! > > Michael Biebl writes: >> Could you blacklist the ipmi_si driver, just to be sure? > > Will do in the evening. > >> That aside, I wonder if it's related to the use of f2fs for / >> >> [

Bug#781730: systemd: Instance variable %i not available for ReadWriteDirectories

Hi Bernhard, Am 02.04.2015 um 11:07 schrieb Bernhard Schmidt: > We're trying to run multiple DHCP processes on one system. They have > their data in a instance-specific configuration directory and we'd like > to limit (r/w for now) filesystem access to that directory for security > reasons. > > =

Bug#779606: daemon-reexec starts plymouth-start.service service

Hi! Am 02.04.2015 um 10:48 schrieb Martin Pitt: > Michael Biebl [2015-03-03 1:05 +0100]: >> I have plymouth installed and enabled (via "splash" on the kernel >> command line"). >> >> When I run "systemctl daemon-reexec", plymouth is (re)start

Bug#781836: systemd: Systemd fails to notice services have died,

Am 03.04.2015 um 18:03 schrieb Dennis Boone: > Package: systemd > Version: 215-5+b1 > Severity: important > > Systemd fails to notice a service has died. Thereafter, when > asked to start it, it reports success, but the service still > isn't running. It is necessary to manually stop and then sta

Bug#781836: systemd: Systemd fails to notice services have died,

Am 03.04.2015 um 18:47 schrieb Dennis Boone: > > Does bacula ship a native service file? > > Could you attach the service file you're using? > > Michael, > > Not that I can find. It would be *.service, right? > > I've attached the init script, in case that's useful. > > De > > > #!/bin/sh

Bug#779606: daemon-reexec starts plymouth-start.service service

Am 06.04.2015 um 13:49 schrieb Martin Pitt: > Hello Michael, > > Michael Biebl [2015-04-02 12:32 +0200]: >> Have you run a git bisect on the v219-stable branch to find the relevant >> commit? > > I didn't yet. I couldn't reliably reproduce it before ei

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

Am 07.04.2015 um 14:27 schrieb Eric Valette: > Package: systemd > Version: 219-6 > Severity: important > > Dear Maintainer, > > > When upgrading to the latests version of systemd, I was asked if I wanted to > keep my own modified version of /etc/systemd/logind.conf were I had been > forced to ad

Bug#782077: systemd: /etc/systemd/logind.conf HandleLidSwitchDocked not honred

Am 07.04.2015 um 21:17 schrieb Michael Biebl: > Am 07.04.2015 um 14:27 schrieb Eric Valette: >> How does systemd detect the docked status? > > http://cgit.freedesktop.org/systemd/systemd/tree/src/login/logind-core.c#n538 > > Systemd counts the number of attached displays.

Bug#761658: Please do not default to using Google nameservers

Am 07.04.2015 um 22:57 schrieb Marco d'Itri: >> We don't enable AVAHI nor do we install cups-browsed to make things >> work out of the box. > Don't we? Then we probably should do it on desktop systems, since > autoconfiguration greatly improves the user experience. The printer task does actually

Bug#761658: Please do not default to using Google nameservers

Am 08.04.2015 um 09:55 schrieb martin f krafft: > also sprach Marco d'Itri [2015-04-07 22:57 +0200]: >>> We don't enable AVAHI nor do we install cups-browsed to make things >>> work out of the box. >> Don't we? Then we probably should do it on desktop systems, since >> autoconfiguration greatly i

Bug#761658: Please do not default to using Google nameservers

Am 08.04.2015 um 11:33 schrieb martin f krafft: > also sprach Michael Biebl [2015-04-08 10:45 +0200]: >> Just like resolved needs explicit opt in by the admin (the service is >> disabled by default). >> Also, it writes the resolv.conf to /run/systemd/resolve/resolv.conf. >

Bug#780235: "man init" brings up systemd(8) despite /sbin/init coming from sysvinit-core

Control: tags -1 moreinfo unreproducible Am 10.03.2015 um 23:59 schrieb Samuel Bronson: > Package: systemd > Version: 215-12 > Severity: important > File: /usr/share/man/man1/systemd.1.gz > > Dear Maintainer, > > When I run "man init", I expect to see the manpage corresponding to > /sbin/init; s

Bug#782134: systemctl TAB-completion for unit names does not work when not root

Hi Zack! Am 08.04.2015 um 12:26 schrieb Stefano Zacchiroli: > When as non root, I do this: > > $ systemctl start l > > I get this error: > > Failed to list units: Access denied > > and TAB completion fail to complete. ("l" is just a sample prefix, TAB > completion for unit names doesn't w

Bug#782134: systemctl TAB-completion for unit names does not work when not root

Am 08.04.2015 um 12:45 schrieb Stefano Zacchiroli: > On Wed, Apr 08, 2015 at 12:38:29PM +0200, Michael Biebl wrote: >> Do you have systemd-shim installed or had it installed in the past >> without purging it? >> I remember an old bug report where the dbus policy shipped by

Bug#782142: systemd: Tries to mount NFS shares twice (?)

Am 08.04.2015 um 13:33 schrieb Santiago Vila: > Package: systemd > Version: 215-14 > > After a recent upgrade in a lab where I use NFS, I see messages like this: > > ifup[370]: mount.nfs: /home/nfs is busy or already mounted > > but this didn't happen before. I suspect of recent changes in syste

Bug#782142: systemd: Tries to mount NFS shares twice (?)

Am 08.04.2015 um 13:51 schrieb Santiago Vila: > On a computer which is a little bit faster than the others I see this > instead: > > ifup[429]: /sbin/ifup: interface eth0 already configured > > I can even reproduce it after *every* reboot: > > * One computer (faster than the others) says "eth0 a

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

Am 20.11.2014 um 22:40 schrieb Simon McVittie: > 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 > t

Bug#782377: systemd: hwclock-save.service should not be run inside containers

Am 11.04.2015 um 12:14 schrieb Christian Seiler: > Package: systemd > Version: 215-15 > Severity: minor > Tags: patch > > Dear Maintainers, > > with 215-13, hwclock-save.service was added to sync the system clock > with the hardware clock on shutdown. This will fail in containers which > don't ha

Bug#782377: systemd: hwclock-save.service should not be run inside containers

Control: tags -1 pending Am 11.04.2015 um 16:44 schrieb Christian Seiler: > On 04/11/2015 03:28 PM, Michael Biebl wrote: >> Am 11.04.2015 um 12:14 schrieb Christian Seiler: >>> Package: systemd >>> Version: 215-15 >>> Severity: minor >>> Tags: patch

Bug#782479: systemd fails to merge CapabilityBoundingSet config lines

Hi, Am 12.04.2015 um 23:24 schrieb Nusenu: > Package: systemd > Version: 215-14 > > Hi, > > from systemd 215-14's man page about CapabilityBoundingSet: > This option may appear more than once in which case the bounding sets > are merged. > > So > CapabilityBoundingSet = cap1 cap2 > > should be

Re: Superblock time check causes problems for fsck in initramfs

Am 09.04.2015 um 04:02 schrieb Ben Hutchings: > I've also uploaded a version of initramfs-tools to > (version 0.120~bwh.1) which > creates the stamp files: > > /run/initramfs/fsck-root > /run/initramfs/fsck-usr > > If you think you have time to

Bug#782496: Acknowledgement (is-enabled fails for legacy sysv services)

Control: forcemerge 751638 -1 Am 13.04.2015 um 10:16 schrieb Nusenu: > > duplicate > > Sorry I just saw: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=751638 > np, merging with existing bug report(s) -- Why is it that all of the instruments seeking intelligent life in the universe are

Bug#782522: Skip file system check if already done by initramfs

Package: systemd Version: 215-15 Severity: important Tags: patch Since version 0.117, initramfs-tools will fsck and mount / (and /usr, if on a separate file system) in the initramfs. These changes will be part of jessie. With ext[234] this has some unpleasant side-effects though, if the RTC is se

Re: Superblock time check causes problems for fsck in initramfs

Am 13.04.2015 um 02:35 schrieb Ben Hutchings: > On Mon, 2015-04-13 at 02:05 +0200, Michael Biebl wrote: >> Am 09.04.2015 um 04:02 schrieb Ben Hutchings: >>> I've also uploaded a version of initramfs-tools to >>> <https://people.debian.org/~benh/packages/> (

Re: Bug#782426: unblock: systemd/215-15

[ Christian Seiler ] | * Don't run hwclock-save.service in containers. (Closes: #782377) http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=c22859a6897e9d6e5483bd0164b687875442f10a The hwclock-save.service is a recent addition and this is an obvious one-line fix. Didn't

Re: Bug#782426: unblock: systemd/215-15

Hi Julien, Am 13.04.2015 um 22:18 schrieb Julien Cristau: > On Mon, Apr 13, 2015 at 22:03:51 +0200, Michael Biebl wrote: > >> ++static int manager_dispatch_ask_password_fd(sd_event_source *source, >> ++int fd, uint32_t revents,

Bug#750019: systemd: systemctl rescue does not work on virtual console

Am 01.06.2014 um 17:12 schrieb Francois Mescam: > > > On 01/06/2014 14:43, Michael Biebl wrote: >> Am 31.05.2014 20:24, schrieb Michael Biebl: >>> severity 750019 normal >>> tags 750019 + moreinfo unreproducible >>> thanks >>> >>>

<    1   2   3   4   5   6   7   8   9   10   >