On Sun, 25 May 2014 12:59:17 +0200
Laurent Bigonville wrote:
> The systemd-logind executable is in the systemd package. Installing
> this package is not automatically switching your system to systemd as
> PID1 (this is done by the systemd-sysv package).
Ah.. right. Sorry, thought that a package
Michael Biebl wrote:
Am 25.05.2014 17:15, schrieb Michael Biebl:
Am 25.05.2014 15:32, schrieb Woody:
Laurent Bigonville wrote:
Woody wrote:
I see also a broken behaviour. I am doing a dual boot - with and
without systemd.
Till the libpolkit-backend has been linked against systemd, it has
work
Am 25.05.2014 17:15, schrieb Michael Biebl:
> Am 25.05.2014 15:32, schrieb Woody:
>> Laurent Bigonville wrote:
>>> Woody wrote:
I see also a broken behaviour. I am doing a dual boot - with and
without systemd.
Till the libpolkit-backend has been linked against systemd, it has
wo
Am 25.05.2014 15:32, schrieb Woody:
> Laurent Bigonville wrote:
>> Woody wrote:
>>> I see also a broken behaviour. I am doing a dual boot - with and
>>> without systemd.
>>> Till the libpolkit-backend has been linked against systemd, it has
>>> worked just fine.
>>>
>>> The problem is now that back
Laurent Bigonville wrote:
Woody wrote:
I see also a broken behaviour. I am doing a dual boot - with and
without systemd.
Till the libpolkit-backend has been linked against systemd, it has
worked just fine.
The problem is now that backend is trying to blindly use systemd, and
fails if systemd is
Woody wrote:
> I see also a broken behaviour. I am doing a dual boot - with and
> without systemd.
> Till the libpolkit-backend has been linked against systemd, it has
> worked just fine.
>
> The problem is now that backend is trying to blindly use systemd, and
> fails if systemd is not running
Attila Kinali wrote:
> On Sat, 24 May 2014 11:26:50 +0200
> Michael Biebl wrote:
>
> > Am 24.05.2014 11:04, schrieb Attila Kinali:
>
> > > I want to add a little bit on this bug here.
> > > IMHO the bug is valid in the sense that policykit unnecessarily
> > > pulls in systemd.
> >
> > No, it's
I see also a broken behaviour. I am doing a dual boot - with and without
systemd.
Till the libpolkit-backend has been linked against systemd, it has
worked just fine.
The problem is now that backend is trying to blindly use systemd, and
fails if systemd is not running as init. With that change
Package: policykit-1
Version: 0.105-5
Followup-For: Bug #747105
Control: severity #747105 normal
Control: reopen #747105
Hi,
I want to add a little bit on this bug here.
IMHO the bug is valid in the sense that policykit unnecessarily pulls
in systemd. Chosing systemd-shim, as described in bug #7
2014-05-06 from Laurent Bigonville:
> ConsoleKit is dead for years
I wouldn't rather call it "dead for years" --
v0.4.5 relesed 2011-05-02, v0.4.6 released 2013-08-19:
http://www.freedesktop.org/wiki/Software/ConsoleKit/
> it's time IMVHO to start moving away from ConsoleKit
> on linux architectu
Adam Borowski wrote:
> Michael Biebl wrote:
> > non-sense.
>
> Per the policy, severity for "breaks unrelated software" is
> "critical". Thus, this bug is valid.
If you think that systemd is breaking anything on your system please
open a bug against systemd package not policykit.
> Please expla
Package: policykit-1
Version: 0.105-5
Severity: critical
Justification: breaks unrelated software
Hi.
While I'm actualla in favour of systemd, I don't thinkt it's mature enough yet
to be used on
my servers (and actually I have tons of non-critical bugs on the desktop with
it as well).
Anyway,
12 matches
Mail list logo
