[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#757341: marked as done (ulatencyd conflicts with default systemd configuration)

Your message dated Tue, 03 Sep 2019 05:34:27 +0000
with message-id <[🔎] E1i51SV-0003YP-3x@fasolo.debian.org>
and subject line Bug#938749: Removed package(s) from unstable
has caused the Debian Bug report #757341,
regarding ulatencyd conflicts with default systemd configuration
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
757341: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=757341
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: ulatency
Version: 0.5.0-9
Severity: important
User: pkg-systemd-maintainers@lists.alioth.debian.org
Usertags: integration


Please see #756375 and related bug reports:


Am 07.08.2014 11:07, schrieb Michael Biebl:
> Am 07.08.2014 11:00, schrieb johnw:
>> After upgrade systemd-* to 208-7, I still have this problem.
>> Please help, thank you.
>
> Have you tried uninstalling/purging the ulatencyd package?
>

Or tried the instructions at [1]


4   Does it work with systemd

    Since Version 0.4.5 ulatencyd works with systemd under two conditions:

            DefaultControllers should be unset. In
/etc/systemd/system.conf set DefaultControllers=
            JoinControllers should be unset. In /etc/systemd/system.conf
set JoinControllers=
            The PAM-systemd module should be disabled, or set "controllers="

    Both options would cause constant moving of processes as the layout
of systemd and ulatencyd (in the default configuration) differs.



Disabling the pam module will break a lot of functionality modern
desktops require, so we can certainly not ship that in Debian as default
configuration for systemd.

I guess there is not a lot we can do about this in the systemd package.
We could add a Conflicts: ulatencyd to make sure the package is not
installed. But given that systemd will be the default init system for
Jessie, this will make the ulatencyd package mostly useless.
Maybe the ulatencyd package should ship the service as disabled by
default. With clear instructions how to enable it under systemd and what
consequences that has.
In any case, bringing the ulatencyd package maintainer into the loop
here and clonging the bug.


Michael

[1] https://github.com/poelzi/ulatencyd/wiki/Faq#does-it-work-with-systemd



-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (200, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

--- End Message ---
--- Begin Message --- 
Version: 0.5.0-9+rm

Dear submitter,

as the package ulatencyd has just been removed from the Debian archive
unstable we hereby close the associated bug reports.  We are sorry
that we couldn't deal with your issue properly.

For details on the removal, please see https://bugs.debian.org/938749

The version of this package that was in Debian prior to this removal
can still be found using http://snapshot.debian.org/.

This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
ftpmaster@ftp-master.debian.org.

Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)

--- End Message ---
Reply to: