Package: libapparmor1
Version: 2.9.0-3+exp1
Severity: important
Tags: patch
Hi,
in version 2.9.0-3+exp1, the libraries were moved to /lib and Martin
(re)enabled apparmor support in systemd. While doing that, he also added
a hard-coded, versioned dependency on libapparmor1 (>= 2.9.0-3+exp1) to
ens
Am 14.04.2015 um 18:59 schrieb Julien Cristau:
> On Mon, Apr 13, 2015 at 22:56:45 +0200, Michael Biebl wrote:
>
>> Julien, do you want me to make a followup upload fixing that (pending
>> confirmation from Zbigniew)?
>>
> Let's delay that to 8.1. Unblocked the cur
Am 14.04.2015 um 20:50 schrieb Simon Richter:
> Package: systemd-sysv,plymouth
> Severity: normal
>
> Hi,
>
> I've recently installed jessie on a netbook (Acer Aspire One 725), with
> systemd as init and plymouth to hide the startup process from the user.
>
> The boot process is about as quick a
Am 14.04.2015 um 21:20 schrieb Simon Richter:
> Hi,
>
> On 14.04.2015 21:03, Michael Biebl wrote:
>
>>>> From a technical point of view, of course all packages behave
>>>> exactly as
>>> intended, however the combination gives a bad result.
>
>
Control: reassign -1 plymouth
Am 14.04.2015 um 21:43 schrieb Simon Richter:
> Hi,
>
> On 14.04.2015 21:34, Michael Biebl wrote:
>
>> I don't see systemd involved here. The interaction is between the
>> display manager/X and plymouth.
>
> systemd needs to ge
Hi,
Am 15.04.2015 um 09:29 schrieb Kartik Mistry:
> Lots of such messages in dmesg output:
>
> [ 4052.385213] systemd-sysv-generator[10194]: Failed to read configuration
> file '/etc/init.d/log': Is a directory
> [ 4052.824814] systemd-sysv-generator[10208]: Failed to read configuration
> file
Hi,
Am 14.04.2015 um 21:56 schrieb Michael Stapelberg:
> On Tue, Apr 14, 2015 at 8:59 PM, Ian Campbell wrote:
>
>> On Tue, 2015-04-14 at 10:02 +0200, Michael Stapelberg wrote:
>>
>>> > Apr 02 12:08:28 hostname systemd[1]: Started LSB: Start
>>> qcontrol daemon.
>>>
>>>
>>> This l
On Mon, 16 Feb 2015 20:37:26 +0100 Miklos Quartus wrote:
> Package: libpam-systemd
> Version: 215-11
> Followup-For: Bug #732209
>
> Hi Vlad,
>
> Yes, I am still able to reproduce this bug in my GNOME session in my
> latest Jessie, indeed. After opening the root terminal window and in
> focus, I
Am 17.04.2015 um 22:49 schrieb Rick Thomas:
>
> I’ve seen this bug today.
>
> System drops into emergency mode for reasons that have nothing to do with
> this bug. Network is active when in emergency shell. I type root password
> then immediately exit, system continues to boot. When boot is
Am 17.04.2015 um 23:43 schrieb Rick Thomas:
> Package: systemd
> Version: 215-16
> Severity: important
>
> When /etc/fstab has an ext4 filesystem on a logical volume which is itself
> on a software raid, the system times out waiting for (I think!) fsck on that
> filesystem.
> This causes the boot
Am 18.04.2015 um 00:36 schrieb Rick Thomas:
>
> On Apr 17, 2015, at 3:17 PM, Michael Biebl wrote:
>
>> Am 17.04.2015 um 23:43 schrieb Rick Thomas:
>>> Package: systemd
>>> Version: 215-16
>>> Severity: important
>>>
>>> When /etc/fsta
Am 28.02.2015 um 09:30 schrieb Chris:
> A draft for such a central systemd unit file:
>
> [Unit]
> Description=Trigger all block device udev rules on resume, to re-apply all
> non-permanent device settings (e.g. smartctl and hdparm rules).
> After=suspend.target After=hibernate.target
> After=hy
control: tags -1 moreinfo unreproducible
Am 18.04.2015 um 02:02 schrieb Rick Thomas:
>
> On Apr 17, 2015, at 3:44 PM, Michael Biebl wrote:
>>
>> Thanks for the data.
>> Looks like an lvm issue to me:
>>
>> root@cube:~# lvscan
>> inactive '
Am 22.04.2015 um 16:36 schrieb chrysn:
> hello,
>
> i've encountered a very similar situation (log files attached), tricky
> to debug because booting would only occasionally fail.
>
> it is my current impression that things fail when there are nested mount
> points, and the outer mount point need
Am 22.04.2015 um 12:10 schrieb Rick Thomas:
> This works. Interestingly, without the sleep loop the vgchange
> fails.
>
> Now, you say that a VM with two virtual disks configured as RAID1
> with a logical volume works fresh out of the box. This makes me
> wonder if it’s some kind of a timing pro
Am 23.04.2015 um 09:21 schrieb Rick Thomas:
>
> On Apr 22, 2015, at 8:17 AM, Michael Biebl wrote:
>
>> Am 22.04.2015 um 12:10 schrieb Rick Thomas:
>>> This works. Interestingly, without the sleep loop the vgchange
>>> fails.
>>>
>>> Now, you
Am 23.04.2015 um 11:45 schrieb Holger Levsen:
> clone 783088 -1
> retitle -1 "systemd should document distinction between $FOO and ${FOO}
> reassign -1 systemd
> tags -1 + upstream
> thanks
>
> Hi Rian,
>
> On Mittwoch, 22. April 2015, Rian Hunter wrote:
>>> thanks for your bugreport. Can you con
Package: lvm2
Version: 2.02.111-2.2
Severity: normal
File: /lib/udev/rules.d/69-lvm-metad.rules
/lib/udev/rules.d/69-lvm-metad.rules contains the following line:
ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run /sbin/lvm
pvscan --cache $major:$minor", GOTO="lvm_end"
In Debian, sy
Hi everyone!
I talked to the release team and they prefer to postpone a fix to 8.1.
I therefor would like to see a short paragraph added to the d-i 8.0
errata [1].
Afaics, the issue so far only happened for automated installations.
There is no real solution/workaround ttbomk besides rebuilding d
Hi Jörg!
just a quick remark, when re-assigning a bug, please always CC the new
package, in that case syst...@packages.debian.org
On Thu, 23 Apr 2015 22:50:05 +0200
=?ISO-8859-1?Q?J=F6rg_Frings-F=FCrst?= wrote:
> reassign 782971 systemd
> thanks
>
>
>
> Hello Vincent,
>
> thank you for spend
Am 23.04.2015 um 22:22 schrieb Cyril Brulebois:
> Michael Biebl (2015-04-23):
>> netboot install writes duplicate entries to 70-persistent-net.rules
>> ~~~
>
> It might be better not to embed the “netboot inst
Am 23.04.2015 um 21:47 schrieb Rick Thomas:
>
> On Apr 23, 2015, at 1:29 AM, Michael Biebl wrote:
>
>> There might be a race somewhere, i.e. lvm2-activation(-early).service
>> being run *before* mdadm has assembled the RAID.
>>
>> You could test this theory,
Am 03.04.2015 um 23:00 schrieb Christoph Egger:
> Christoph Egger writes:
>
>> Michael Biebl writes:
>>> I assume the f2fs-tools package is installed?
>>> What output (and return code) do you get, if you run
>>> fsck.f2fs /dev/disk/by-uuid/691d5901-2f6b-4
Am 24.04.2015 um 07:55 schrieb Jörg Frings-Fürst:
> At end of December / beginning of January sane over network works fine
> with the "StandardInput=socket". Now sane in the same version don't work
> anymore over network.
>
> So my question: Has systemd any changes, so that StandardInput=socket is
Am 24.04.2015 um 02:07 schrieb Mike Kupfer:
> Hi, I have
>
> $ dpkg -l initramfs-tools systemd
> Desired=Unknown/Install/Remove/Purge/Hold
> | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
> |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
> ||/ Name
Package: hw-detect
Version: 1.108
Severity: normal
Tags: patch
Hi!
While installing a jessie (GNOME) desktop with the latest RC3 installer,
I noticed that we still install acpid and acpi-support-base.
A while ago, I already filed a bug to have acpid and acpi-support-base
removed from tasksel [1]
Am 24.04.2015 um 17:27 schrieb Mike Kupfer:
> Michael Biebl wrote:
>
>> Ok, so sda1 is your /, what is the status of
>> $ systemctl status systemd-fsck-root.service
>
> $ systemctl status systemd-fsck-root.service
> ● systemd-fsck-root.service - File System Check
Am 25.04.2015 um 08:25 schrieb Carlo Marchiori:
> Package: systemd
> Version: 215-17
> Severity: normal
>
> At about 25 seconds gdm3 starts, so the problem is at least shared with gdm3
> which is much slower then before.
Please include the output of
"systemd-analyze blame" and "systemd-analyze cr
Am 25.04.2015 um 14:22 schrieb Michael Biebl:
> Am 25.04.2015 um 08:25 schrieb Carlo Marchiori:
>> Package: systemd
>> Version: 215-17
>> Severity: normal
>>
>> At about 25 seconds gdm3 starts, so the problem is at least shared with gdm3
>> which is much slow
Am 25.04.2015 um 14:54 schrieb Carlo Marchiori:
> Please find attached the requested information.
> Thanks, Carlo.
>
>
> systemd-analyze blame.txt
>
>
> 17.335s nmbd.service
> 16.773s samba-ad-dc.service
Do you need the samba package?
If not, try uninstalling the package.
I'm
Am 25.04.2015 um 15:23 schrieb Carlo Marchiori:
> I have removed the 6 packages you suggested but the boot time hasn't
> improved a lot,
> maybe a couple of seconds.
>
> I takes about 30 seconds to the blank screen, and other 20 seconds from the
> blank screen to the gnome login screen.
> Please f
Am 25.04.2015 um 14:21 schrieb Michael Biebl:
> I can reproduce the missing /bin/touch if I build the initramfs without
> busybox support. Can you check your /etc/initramfs-tools/initramfs.conf
> if it contains BUSYBOX=n or if you have a snippet in
> /etc/initramfs-tools/conf.d/ which
clone 743158 -1
reassign -1 cryptsetup
retitle -1 crpytsetup: sends private information without confirmation
thanks
Am 31.03.2014 um 03:33 schrieb Norbert Preining:
> Package: systemd
> Version: 204-8
> Severity: grave
> Tags: security
> Justification: user security hole
>
> Sending /etc/fstab wi
Control: reassign -1 dbus
Am 26.04.2015 um 00:05 schrieb Dmitry Katsubo:
> Package: systemd
> Version: 215-16
>
> Hello,
>
> I run Debian jessie in single mode (recovery mode). In this mode I would
> like to start gpm service:
>
> # /etc/init.d/gpm start
>
> Afterwards the process systemd open
Am 26.04.2015 um 00:36 schrieb Michael Biebl:
> Am 26.04.2015 um 00:05 schrieb Dmitry Katsubo:
>>
>> Afterwards the process systemd opens a file in /var/run, thus not
>> allowing me to unmount /var:
>> systemd opens a file in /run, thus allowing the administrator to umo
On Sat, 20 Sep 2014 10:45:03 +0900 Norbert Preining
wrote:
> Sep 20 10:35:41 wienerschnitzel systemd-gpt-auto-generator[112]: Failed to
> determine block device of root file system: No such file or directory
> Sep 20 10:35:41 wienerschnitzel systemd[102]:
> /lib/systemd/system-generators/systemd
Am 26.04.2015 um 14:12 schrieb Dmitry Katsubo:
> On 26/04/2015 01:05, Michael Biebl wrote:
>> Am 26.04.2015 um 00:36 schrieb Michael Biebl:
>>> Am 26.04.2015 um 00:05 schrieb Dmitry Katsubo:
>>>>
>>>> Afterwards the process systemd opens a file in /var
Control: forcemerge 760524 -1
Am 26.04.2015 um 14:25 schrieb Thorsten Alteholz:
> Package: systemd
> Severity: normal
> User: alteh...@debian.org
> thanks
>
> Dear Maintainer,
>
> according to /etc/systemd/timesyncd.conf one should:
> "See timesyncd.conf(5) for details"
> but:
> $ LANG=C man
Hi Marco
Am 26.04.2015 um 15:59 schrieb Marco d'Itri:
> On Apr 26, Michael Biebl wrote:
>
>> The problem with /var/run/dbus/system_bus_socket is, that it's
>> hard-coded in so many locations (as you can see on codesearch), one
>> could even consider it ABI, th
Am 26.04.2015 um 20:40 schrieb Martin Pitt:
> Hello Mike, Michael,
>
> Michael Biebl [2015-04-25 15:55 +0200]:
>> Am 25.04.2015 um 14:21 schrieb Michael Biebl:
>>> I can reproduce the missing /bin/touch if I build the initramfs without
>>> busybox support. Can yo
Am 26.04.2015 um 21:24 schrieb Cyril Brulebois:
> Michael Biebl (2015-04-26):
>> How do you configure your network? ifupdown, allow-hotpluto, auto?
>>
>> network-online.target should actually be mostly functional if you use
>> ifupdown.
>
> # The loopback netwo
Michael Biebl wrote:
> Package: initramfs-tools
> Version: 0.120
> Severity: important
>
> systemd-fsck [1] knows the following kernel command line parameters
>
> fsck.mode=
>
> One of "auto", "force", "skip". Controls the mode of operatio
Am 27.04.2015 um 10:48 schrieb Tomasz Buchert:
> (cont.)
> as suspected adding "After=network.target" in
> /lib/systemd/system/systemd-sysctl.service
> actually helps
It seems more likely, that /etc/init.d/networking changes the sysctl
knobs when it starts.
Can you investigate, if this is the cas
Am 27.04.2015 um 15:03 schrieb Martin Pitt:
> Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=88401
> Control: fixed -1 219-6
>
> Hello again,
>
> Martin Pitt [2015-04-02 10:48 +0200]:
>> Hey Michael,
>>
>> Michael Biebl [2015-03-03 1:05 +
Am 27.04.2015 um 18:15 schrieb Andreas Metzler:
> Package: systemd
> Version: 215-17
> Severity: normal
>
> Hello,
>
> I am not sure for how long but I guess less than two months (jessie),
> systemd has started purging my /tmp on every reboot, although I have
> these settings:
>
> /etc/default/r
Am 27.04.2015 um 19:15 schrieb Andreas Metzler:
> On 2015-04-27 Michael Biebl wrote:
>> Am 27.04.2015 um 18:15 schrieb Andreas Metzler:
>>> Package: systemd
>>> Version: 215-17
>>> Severity: normal
>
>>> I am not sure for how long but I gues
Am 27.04.2015 um 19:15 schrieb Andreas Metzler:
> Looking at the respective changelog, only the fix for 779902 ("/tmp
> can be mounted as tmpfs against user's will") seems to be
> tmpfs-related.
That change is actually making it less likely that tmp.mount is
activated accidentally, by not making P
Am 27.04.2015 um 20:30 schrieb Andreas Metzler:
> On 2015-04-27 Michael Biebl wrote:
>> So you're saying, with 215-12, tmp.mount was not automatically mounted?
> Yes, unless the logfile has suddenly increased in verbosity ATM. The
> "Mounting Temporary Directory...&q
Control: tags -1 confirmed
Control: retitle -1 tmp.mount activated accidentally via bind mount
Am 27.04.2015 um 20:30 schrieb Andreas Metzler:
> On 2015-04-27 Michael Biebl wrote:
>> Who is creating those mounts? Maybe they didn't exist when you have -12
>> installed? How a
Control: found -1 215-13
Am 27.04.2015 um 21:14 schrieb Michael Biebl:
> Control: tags -1 confirmed
> Control: retitle -1 tmp.mount activated accidentally via bind mount
>
> Am 27.04.2015 um 20:30 schrieb Andreas Metzler:
>> On 2015-04-27 Michael Biebl wrote:
>>> W
Am 27.04.2015 um 21:56 schrieb Michael Biebl:
>> Ok, I can confirm that adding such a bind mount to /tmp activates
>> tmp.mount, even if tmp.mount has been disabled. Retitling the bug report
>> accordingly.
>
> I can also confirm, that this is a regression from -12 to -
Am 28.04.2015 um 22:39 schrieb Raphaël Halimi:
> Le 28/04/2015 22:34, Michael Biebl a écrit :
>> Fixed upstream by
>>
>> commit a48a62a1af02aec4473c9deed98dd5b89d210f93
>> Author: Zbigniew Jędrzejewski-Szmek
>> Date: Sun Jan 18 15:05:40 2015 -0500
>>
&g
Am 28.04.2015 um 22:49 schrieb Michael Biebl:
> Am 28.04.2015 um 22:39 schrieb Raphaël Halimi:
>> Le 28/04/2015 22:34, Michael Biebl a écrit :
>>> Fixed upstream by
>>>
>>> commit a48a62a1af02aec4473c9deed98dd5b89d210f93
>>> Author: Zbigniew Jędrzejewsk
Am 30.04.2015 um 01:47 schrieb Karl Kornel:
> Package: systemd
> Version: 215-17
> Severity: normal
>
> Hello!
>
> I have a system, with a third-party network card using non-free firmware,
> where
> systemd does not wait for the interface to come up before continuing boot.
>
> The card uses th
control: severity -1 important
control: tags -1 - security
Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz:
> Severity: critical
> Package: systemd
> Tags: security
>
> Restarting emergency.service (as done by needsrestart) within the
> emergency.service leads to a prompt for the root password to en
Am 04.05.2015 um 13:41 schrieb Michael Biebl:
> control: severity -1 important
> control: tags -1 - security
>
> Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz:
>> Severity: critical
>> Package: systemd
>> Tags: security
>>
>> Restarting emergency.se
control: severity -1 important
Am 04.05.2015 um 13:53 schrieb Bernd Zeimetz:
> control: severity -1 grave
>
> On 05/04/2015 01:41 PM, Michael Biebl wrote:
>>> Restarting emergency.service (as done by needsrestart) within the
>>> emergency.service leads to a prompt for
Control: forwarded -1
http://lists.freedesktop.org/archives/systemd-devel/2015-May/031482.html
Am 04.05.2015 um 14:26 schrieb Michael Biebl:
> No, not really. What we probably should do is mark
> emergency.service as
> RefuseManualStart=yes
> RefuseManualStop=yes
I forwarded this s
Am 04.05.2015 um 15:56 schrieb Bernd Zeimetz:
> Please learn that single user mode is perfectly fine for doing all weird
> things tou could imagine, including installing or removing things
> because one doesn't want to boot a full system.
single user mode != emergency mode
Please stop trying to
Am 05.05.2015 um 18:19 schrieb Josh Triplett:
> On Tue, May 05, 2015 at 06:07:56PM +0200, Michael Biebl wrote:
>> Am 05.05.2015 um 17:57 schrieb Josh Triplett:
>>> On Tue, May 05, 2015 at 02:08:56PM +0200, Michael Biebl wrote:
>>>> On Thu, 02 Apr 2015 11:24:53 -
Am 05.05.2015 um 19:24 schrieb Michael Biebl:
> Am 05.05.2015 um 18:19 schrieb Josh Triplett:
>> Personally, in the stretch timeframe, I plan to work on making it
>> possible to remove the initscripts and sysv-rc packages from a systemd
>> system.
[..]
> e/ /lib/init/var
Am 06.05.2015 um 01:14 schrieb j...@joshtriplett.org:
> On Tue, May 05, 2015 at 07:28:49PM +0200, Michael Biebl wrote:
>> Dropping sysv-rc will be tricky, since it provides update-rc.d and
>> invoke-rc.d.
>
> Might be possible if we moved towards packages depending on thos
Am 06.05.2015 um 01:38 schrieb j...@joshtriplett.org:
> On Tue, May 05, 2015 at 07:24:41PM +0200, Michael Biebl wrote:
>> d/ insserv needs to be fixed to not barf if the facilities provided by
>> the initscripts package are not around and handle this gracefully (by
>>
reassign: -1 aiccu
Am 06.05.2015 um 04:43 schrieb Daniel Albers:
> This is a critical bug of either aiccu or systemd as explained by
> Pascal.
>
> Assigning also to systemd as the aiccu maintainer considers this a
> systemd bug, although I think message #26 <
> 546673f0.1040...@localhost.localdom
Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz:
> Even worse, pressing enter shows the prompt from the former shell and
> I'm able to get 'bash ... command not found errors'
This looks like a bug in /sbin/sulogin, which does not properly cleanup
it's children, when being killed.
Our /sbin/sulogin im
clone 784238 -1
reassign -1 needrestart
retitle -1 please don't restart emergency.service/rescue.service
thanks
Am 04.05.2015 um 13:45 schrieb Michael Biebl:
> Am 04.05.2015 um 13:41 schrieb Michael Biebl:
>> control: severity -1 important
>> control: tags -1 - security
>&
clone: 784238 -1 -2
reassign: -1 util-linux
reassign: -2 sysvinit-utils
retitle: -1 Please ship sulogin, last(b), mesg
retitle: -2 Please let util-linux provide sulogin, last(b), mesg
thanks
Am 06.05.2015 um 12:53 schrieb Michael Biebl:
> Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz:
>
Hi,
Am 07.05.2015 um 12:38 schrieb Mathieu Malaterre:
>
> After migrating my MacMini G4 from wheezy to jessie[*], here is what I can
> see in dmesg output:
>
> [ 18.191059] systemd[1]: Failed to start Load Kernel Modules.
>
> More specfically:
>
> # systemctl status systemd-modules-load.ser
Control: tags -1 + moreinfo unreproducible
Am 07.05.2015 um 06:38 schrieb Brian May:
> root@scrooge:/# apt-get remove systemd-sysv
When you've been running that command, was systemd the active PID 1 or
did you boot with init=/lib/sysvinit/init (having the sysvinit package
installed?)
> Reading p
Am 07.05.2015 um 06:38 schrieb Brian May:
> Unpacking systemd-shim (9-1) ...
> Processing triggers for systemd (215-17) ...
> Failed to get D-Bus connection: No such file or directory
> dpkg: error processing package systemd (--unpack):
> subprocess installed post-installation script returned erro
Control: reassign -1 snappy
Control: severity -1 serious
Control: affects -1 systemd
Control: forwarded -1 https://bugzilla.redhat.com/show_bug.cgi?id=948417
Am 07.05.2015 um 19:38 schrieb Stefan Schmidt:
> Package: systemd
> Version: 215-17
>
> I just came across an issue with journald being una
Am 08.05.2015 um 05:22 schrieb Brian May:
> On Thu, 7 May 2015 at 22:30 Michael Biebl wrote:
>
>> So, systemd.postinst seems to fail in the trigger
>> We do not call systemctl uncondionally here:
>>
>> _systemctl() {
>> if [ -d /run/systemd/system ]; then
Am 08.05.2015 um 13:34 schrieb Michael Biebl:
> Which kernel version is that? Does it satisfy all requirements as listed
> in /usr/share/doc/systemd/README.gz?
>
> I assume, you can reproduce the uninstallation failure on real iron or
can *not* reproduce...
--
Why is it tha
Am 08.05.2015 um 14:19 schrieb Brian May:
> On Fri, 8 May 2015 at 21:34 Michael Biebl wrote:
>
>> I think the failure on uninstallation is just a red herring or just an
>> aspect of a bigger issue, i.e. your systemd installation is not fully
>> functional, most likely du
Control: tags -1 - moreinfo unreproducible
Control: reassign -1 man-db
Am 08.04.2015 um 12:13 schrieb Michael Biebl:
> Control: tags -1 moreinfo unreproducible
>
> Am 10.03.2015 um 23:59 schrieb Samuel Bronson:
>> Package: systemd
>> Version: 215-12
>> Severity: import
On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings
wrote:
> Control: reassign -1 clock-setup
> Control: retitle -1 Missing support for systems without battery-backed RTC
>
> On Sun, 2015-05-03 at 17:40 +0200, Geert Stappers wrote:
> > Debian installations on hardware with no (battery-backuped) RTC
Am 09.05.2015 um 03:32 schrieb Michael Biebl:
> On Sun, 03 May 2015 17:23:30 +0100 Ben Hutchings
>> 1. Install/enable NTP client
>> 2. Disable hwclock-save.service
See below for the changes in systemd
>> 3. Disable e2fsck time check
What exactly do you mean here?
>&
Am 09.05.2015 um 03:59 schrieb Ben Hutchings:
> On Sat, 2015-05-09 at 03:32 +0200, Michael Biebl wrote:
>> FWIW:
>> http://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?h=experimental&id=929bece53261ddd2797d4f3518a05a88704c5b01
>
> So what happens if another n
Am 09.05.2015 um 13:16 schrieb Brian May:
> On Fri, 8 May 2015 at 22:26 Michael Biebl wrote:
>
>> Ok, this particular issue, as mentioned earlier, is probably solved by
>> simply using "|| true" in the dpkg trigger. I think it's safe to ignore
>> errors fro
Am 09.05.2015 um 13:16 schrieb Brian May:
> On Fri, 8 May 2015 at 22:26 Michael Biebl wrote:
>
>> Ok, this particular issue, as mentioned earlier, is probably solved by
>> simply using "|| true" in the dpkg trigger. I think it's safe to ignore
>> errors fro
Am 06.05.2015 um 12:53 schrieb Michael Biebl:
> Am 04.05.2015 um 13:15 schrieb Bernd Zeimetz:
>> Even worse, pressing enter shows the prompt from the former shell and
>> I'm able to get 'bash ... command not found errors'
>
> This looks like a bug in /sbin/sulo
Am 10.05.2015 um 14:46 schrieb Ian Campbell:
> Hello,
>
> In adding systemd unit support to the qcontrol package (#781886) I
> needed to add a udev rule (60-qcontrol.rules):
> KERNELS=="gpio-keys", SUBSYSTEMS=="platform", DRIVERS=="gpio-keys",
> TAG+="systemd"
>
> In order to tag /dev/in
Am 10.05.2015 um 15:37 schrieb Michael Biebl:
> Am 10.05.2015 um 14:46 schrieb Ian Campbell:
>> Hello,
>>
>> In adding systemd unit support to the qcontrol package (#781886) I
>> needed to add a udev rule (60-qcontrol.rules):
>> KERNELS=="gpio-keys&qu
Am 10.05.2015 um 18:02 schrieb Ian Campbell:
> On Sun, 2015-05-10 at 15:37 +0200, Michael Biebl wrote:
>> Am 10.05.2015 um 14:46 schrieb Ian Campbell:
>>> Hello,
>>>
>>> In adding systemd unit support to the qcontrol package (#781886) I
>>>
Am 10.05.2015 um 18:03 schrieb Ian Campbell:
> On Sun, 2015-05-10 at 15:39 +0200, Michael Biebl wrote:
>> Am 10.05.2015 um 15:37 schrieb Michael Biebl:
>>> Am 10.05.2015 um 14:46 schrieb Ian Campbell:
>>>> Hello,
>>>>
>>>> In adding sy
Am 10.05.2015 um 18:38 schrieb Michael Biebl:
> Am 10.05.2015 um 18:02 schrieb Ian Campbell:
>> The unit file, which was contributed upstream, contains:
>>
>>
>> Requires=dev-input-by\x2dpath-platform\x2dgpio\x2dkeys\x2devent.device
>> After=dev-
Control: tags -1 + patch
Am 12.05.2015 um 13:45 schrieb Michael Biebl:
> On Mon, 30 Mar 2015 04:02:01 +0200 Christoph Anton Mitterer
>> As for sd_notify,... a simply google query didn't turn up any existing
>> patches for that and it may be hard to convince upstream to do it
Am 12.05.2015 um 17:07 schrieb Michael Biebl:
> root@pluto:~# echo foobar >> /etc/ssh/sshd_config
>
> root@pluto:~# systemctl restart ssh.service
> Job for ssh.service failed. See 'systemctl status ssh.service' and
> 'journalctl -xn' for details.
>
Am 12.05.2015 um 17:42 schrieb Michael Biebl:
> Am 12.05.2015 um 17:07 schrieb Michael Biebl:
>> As you can see, systemd tries to repeatedly start the service until it hits
>> start-limit.
>> We should use sd_notify in that case to pass a correct error code to systemd.
>
Control: severity -1 wishlist
Control: forcemerge -1 783692
Control: tags -1 upstream
Am 15.05.2015 um 07:26 schrieb Jari Aalto:
> Package: systemd
> Version: 208-6
> Severity: normal
>
> The standard output of systemctl(1) is in color.
>
> Please
>
> - Make no-color the default
I happen to
Control: tags -1 moreinfo unreproducible
Am 16.05.2015 um 23:34 schrieb Johannes Rohr:
> Package: systemd
> Version: 215-17
> Severity: important
>
> Dear Maintainer,
>
> This concerns Raspbian upgraded to Jessie on the Raspberry Pi B+ (Model 1)
>
> Here, several services fail if systemd is bei
Am 17.05.2015 um 01:14 schrieb Michael Biebl:
> Control: tags -1 moreinfo unreproducible
>
> Am 16.05.2015 um 23:34 schrieb Johannes Rohr:
>> Package: systemd
>> Version: 215-17
>> Severity: important
>>
>> Dear Maintainer,
>>
>> This concern
Am 17.05.2015 um 14:59 schrieb Thibaut Varène:
> A footnote in the release/upgrade instructions would have been nice. If that
> machine had been remote without OOB access, I'd have been screwed over,
> because something that never broke previous upgrades.
It would have been nice if people actual
Hi
Am 18.05.2015 um 00:33 schrieb Facundo Gaich:
> While trying to debug issues related to systemd unmounting NFS shares way
> after the network has gone down, I ran into problems trying to stop services
> before wpa_supplicant initiated deauth.
>
> Even tying my service (autofs.service) to Netwo
Am 16.05.2015 um 23:34 schrieb Johannes Rohr:
> May 15 22:20:04 raspbian systemd[1]: dbus.service: main process exited,
> code=exited, status=219/CGROUP
> May 15 22:20:04 raspbian systemd[1]: rsyslog.service: main process
> exited, code=exited, status=219/CGROUP
> May 15 22:20:04 raspbian system
Am 18.05.2015 um 15:27 schrieb Johannes Rohr:
> Am 18.05.2015 um 13:32 schrieb Michael Biebl:
>
>> Do you have any tools installed, which mess around with cgroups, like
>> cgmanager, lxc, etc?
> cgmanager, cgroup-bin and cgroup-tools were installed. After removing
> them,
reassign 785484 cgroup-bin
severity 785484 grave
found 785484 0.41-6
retitle 785484 cgroup-bin: breaks boot with systemd
thanks
Thanks for the further information, Bernhard.
I'm going to re-assign this bug report to cgroup-bin.
Am 18.05.2015 um 19:04 schrieb Bernhard Übelacker:
> Hello,
> as I g
Am 18.05.2015 um 19:11 schrieb Facundo Gaich:
> In conclusion and based on the bug you posted a passable fix in the
> meantime would be to add After=dbus.service to wpa_supplicant.service.
Yes, we tried to discuss a more general solution with upstream but
Lennart prefers, if those services which n
Am 18.05.2015 um 22:01 schrieb Rainer Dorsch:
> root@nanette:~# systemctl status rc-local.service
> ● rc-local.service - /etc/rc.local Compatibility
>Loaded: loaded (/lib/systemd/system/rc-local.service; static)
>Active: failed (Result: exit-code) since Mon 2015-05-18 14:29:04 CEST; 7h
>
Am 21.05.2015 um 00:40 schrieb Patrick Schleizer:
> Hi!
>
> Can one somehow distinguish if,
>
> a) the daemon was started during boot or,
> b) (re)started by an apt-get install or upgrade?
>
> Can this be distinguished from within the daemon itself?
Not afaik.
> The use case is here to
401 - 500 of 2654 matches
Mail list logo
