[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
Turns out, the missing fsck progress bar is a regression: https://github.com/systemd/systemd/issues/17157 ** Bug watch added: github.com/systemd/systemd/issues #17157 https://github.com/systemd/systemd/issues/17157 -- You received this bug notification because you are a member of Ubuntu

[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
>From my personal POV, I consider the progress bar more important then the >ability to interrupt fsck with CTRL+C. Nowadays, SSDs are much more common and enable_periodic_fsck = 0 has been the default for many years now. So this is much less of an issue today then it was back in 2015, I think.

[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-24 Thread Michael Biebl
As for text-only boot: Maybe we could convince upstream to enable verbose mode once an fsck takes longer then say 30s (similar to how the eye-of-cyclon animation kicks in when services take a long time to start). With something like that implemented, dropping fsckd might be an option, I think. --

[Touch-packages] [Bug 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-09-23 Thread Michael Biebl
I would be happy to see this patch merged upstream. There was an attempt a few years ago: https://lists.freedesktop.org/archives/systemd-devel/2015-March/029186.html Eventually it was removed again: https://github.com/systemd/systemd/commit/96d9117ad2db7d8c13f7898127eee8939e88daf1

[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
It would be good adding this information to the upstream bug tracker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1803993 Title: Password appears on the VT1 screen

[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
Looking at the discussion at https://gitlab.freedesktop.org/xorg/xserver/issues/857#note_201402 this might be a bug in plymouth which is supposedly fixed in plymouth 0.9.4. Could users who can reliably reproduce the issue post if they have plymouth installed and if so, which version? ** Bug

[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-09-05 Thread Michael Biebl
@rbalint if you can reliably reproduce the issue, it would probably be a good idea if you follow up on that upstream bug tracker -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1639050] Re: Wrong package section, should be in "introspection"

2016-11-16 Thread Michael Biebl
In Debian, the values in debian/control are only used when the package is uploaded intially to the archive. The override entry is created from that. Changing the contents of the archive override is done by the ftp-masters. If you later change the contents of debian/control does not have an

[Touch-packages] [Bug 1639050] [NEW] Wrong package section, should be in "introspection"

2016-11-03 Thread Michael Biebl
Public bug reported: Packages shipping gobject introspection should be in the dedicated section "introspection". This archive section was added a while ago, see also the corresponding entry in the debian policy 3.9.3.0: 2.6. Version 3.9.3.0 Released February, 2012.

[Touch-packages] [Bug 1602834] [NEW] obsolete conffiles not cleaned up on upgrade

2016-07-13 Thread Michael Biebl
Public bug reported: Hi, the following conffile is marked as obsolete in my dpkg status db /etc/bash_completion.d/ufw 50de7ccdcddb779093156f133d9c0a5e obsolete Ufw now ships /usr/share/bash-completion/completions/ufw, so the conffile should be removed on upgrades. ProblemType: Bug

[Touch-packages] [Bug 1573296] [NEW] obsolete conffiles not cleaned up on upgrade

2016-04-21 Thread Michael Biebl
Public bug reported: The following files are marked obsolete after the upgrade to 16.04: /etc/init/pulseaudio.conf 6244f8d452b29be7d17219b2db34138f obsolete /etc/init.d/pulseaudio df2873ee4f4673d53e3562a0de6e8aa0 obsolete /etc/default/pulseaudio 777f75f5521eab11c647da5c55544b1b obsolete

[Touch-packages] [Bug 1573299] [NEW] obsolete conffiles not cleaned up on upgrade

2016-04-21 Thread Michael Biebl
Public bug reported: The following conffiles were not cleaned up after the upgrade to 16.04: /etc/bash_completion.d/gdbus 3c6022ac0bf85f2f374358a52456e803 obsolete /etc/bash_completion.d/gsettings ed6dbd29972bb65275e46f1cb1ac5062 obsolete /etc/bash_completion.d/gresource

[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

2016-02-17 Thread Michael Biebl
@pitti: will /etc/systemd/system/tmp.mount override a /tmp mount point from /etc/fstab (/run vs /etc)? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1545707 Title: Error

[Touch-packages] [Bug 1545707] Re: Error message "Operation failed: No such file or directory" on installing/reconfiguring systemd

2016-02-16 Thread Michael Biebl
An explicit reload should not be necessary for "enable". I also can't reproduce the problem: $ cp /usr/share/systemd/tmp.mount /etc/systemd/system/tmp2.mount $ systemctl enable tmp2.mount Created symlink from /etc/systemd/system/local-fs.target.wants/tmp2.mount to

[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
man bootup(7) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1532553 Title: /etc/halt.local has become /usr/sbin/halt.local Status in systemd package in Ubuntu: Fix

[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
fwiw, halt-local.service was hooked up in final.target and contains the following: [Unit] Description=/usr/sbin/halt.local Compatibility ConditionFileIsExecutable=/usr/sbin/halt.local DefaultDependencies=no After=shutdown.target Before=final.target To apply that to my

[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Or make that WantedBy=final.target, if you want to execute it during late shutdown. See man systemd.special(7) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1532553

[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Add a native service file and hook it up in the shutdown.target. That's the cleanest solution. /etc/systemd/system/foo.service [Unit] Description=Run service on shutdown [Service] ExecStart=/bin/true [Install] WantedBy=shutdown.target -- You received this bug notification because you are a

[Touch-packages] [Bug 1532553] Re: /etc/halt.local has become /usr/sbin/halt.local

2016-01-18 Thread Michael Biebl
Before the introduction of systemd in Debian and Ubuntu, /etc/halt.local was not supported at all. Neither sysvinit nor upstart executed that file/script. So I'm mildly suprised, when you say "it always worked". We decided to not introduce support for this legacy, sysv specific service, which

[Touch-packages] [Bug 1518507] [NEW] Drop dependency on systemd-shim (and replace system-services)

2015-11-20 Thread Michael Biebl
Public bug reported: The package declares a dependency on systemd-shim. With systemd being the default init, this dependency is no longer required and actually wanted. The dependency on systemd-services should also either be replaced with a dependency on systemd (or libpam-systemd, depending on

[Touch-packages] [Bug 1438612]

2015-04-02 Thread Michael Biebl
ExecStop=/bin/true was my first idea, but Martin rightfully pointed out, that this doesn't influence KillMode, i.e. we need KillMode=none. With that KillMode setting, I think we can actually drop ExecStop=/bin/true, so what remains is KillMode=none systemd has a final killing spree, before it

[Touch-packages] [Bug 1438612]

2015-04-02 Thread Michael Biebl
(In reply to Simon McVittie from comment #7) (In reply to Simon McVittie from comment #6) Perhaps it would be better to make the stop command exit nonzero? Straw man: ExecStop=/bin/sh -c echo Stopping the system dbus-daemon is not supported. Reboot the system instead.; exit 1 ...

[Touch-packages] [Bug 1438612] Re: remote file systems hang on shutdown, D-BUS stops too early

2015-03-31 Thread Michael Biebl
dbus would be stopped by the final killing spree. This usually looks like this stop individual services in reverse order Sending SIGTERM to remaining processes... Sending SIGKILL to remaining processes... Unmounting file systems. All filesystems unmounted. Deactivating swaps. All swaps

Re: [Touch-packages] [Bug 1437821] [NEW] no proper foreground mode

2015-03-29 Thread Michael Biebl
This is what -n is for. Incidentally, this is also used in rsyslog.service file for systemd. 2015-03-29 14:25 GMT+02:00 Hadmut Danisch had...@danisch.de: Public bug reported: Hi, it's rather a feature request than a bug report: I had to package several network services in docker images

[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

2015-03-14 Thread Michael Biebl
Let me chime in here as maintainer of NM in Debian: The reason why we ship the patch, which removes Wants/Before=network.target is, that this lead to dependency cycles if services/sysv init scripts in rcS (sysinit.target) had Should-Start/Required-Start: $network, like for example

[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target

2015-03-14 Thread Michael Biebl
Sorry, meant Before=network.target, of course... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs