On Tue, 17 Jan 2017 13:35:14 + Ian Jackson
wrote:
> [1] AIUI this is when your laptop suspends to RAM, but after a timeout
> or when the battery is low, wakes up so that it can suspend to disk.
Linux implements hybrid sleep by going ahead and writing the hibernation
image out, then suspendin
Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things
[and 1 more messages]"):
> This seems to solve the problem for me, thank you very much! (And I hope
> you can get this in for stretch!)
Thanks to everyone for their reports. This is very helpfu
On So, Jan 15, 2017 at 04:43:11 +, Ian Jackson wrote:
I have just uploaded systemd-shim 10-3~exp1 to experimental. I seems
to fix the problem for me. Depending on feedback, I will upload this
to sid in the next few days.
Thank you very much. I don’t have problems either.
Stephan
On 15/01/17 13:43, Ian Jackson wrote:
> Ian Jackson writes ("Re: "not authorised" doing various desktoppy things [and
> 1 more messages]"):
>> More news later today.
>
> I have just uploaded systemd-shim 10-3~exp1 to experimental. I seems
> to fix the
Ian Jackson writes ("Re: "not authorised" doing various desktoppy things [and 1
more messages]"):
> More news later today.
I have just uploaded systemd-shim 10-3~exp1 to experimental. I seems
to fix the problem for me. Depending on feedback, I will upload this
to s
tl;dr
TYVM to Michael Biebl
I intend QA upload of systemd-shim with Michael's wrapper
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and
1 more messages]"):
> Am 05.01.2017 um 19:56 schrieb Michael Biebl:
> > Then copy the a
Martín Ferrari writes ("Re: "not authorised" doing various desktoppy things"):
> On 03/01/17 17:05, Ian Jackson wrote:
> > Recently, my nm-applet can no longer control my network-manager
> > daemon. I get a message saying[1]:
>
> Did you ever get to the
On 03/01/17 17:05, Ian Jackson wrote:
> Recently, my nm-applet can no longer control my network-manager
> daemon. I get a message saying[1]:
Did you ever get to the root of this?
I am having the same kind of problem (no way to control networking,
removable media, power settings) and a similar se
On Fri, Jan 06, 2017 at 01:58:50PM +0100, Ansgar Burchardt wrote:
> > > Including access to devices (which X wants these days)?
> >
> > That's just for ancient graphics cards (ie, with no KMS/DRM support)
> > without xserver-xorg-legacy, right?
>
> logind is required for drivers using KMS and *no
On Fri, 2017-01-06 at 07:48 +0100, Adam Borowski wrote:
> On Thu, Jan 05, 2017 at 12:19:08PM +0100, Ansgar Burchardt wrote:
> > With elogind do you mean https://github.com/wingo/elogind? That
> > project doesn't look very active.
> >
> > Is there any active project trying to reimplement the login
On Thu, Jan 05, 2017 at 12:19:08PM +0100, Ansgar Burchardt wrote:
> On Thu, 2017-01-05 at 11:22 +0100, Adam Borowski wrote:
> > Neither systemd-shim nor consolekit are solutions that are viable in
> > the long term, the sooner we get rid of both, the better. I don't
> > know what's a good alternat
Am 05.01.2017 um 19:56 schrieb Michael Biebl:
> Then copy the attached wrapper script to /usr/lib/x86_64-linux-gnu/
> and make it executable.
Obviously, the wrapper script should start systemd-shim.orig.
Fixed one attached.
--
Why is it that all of the instruments seeking intelligent life in t
Am 04.01.2017 um 20:12 schrieb Ian Jackson:
> Michael Biebl writes ("Re: "not authorised" doing various desktoppy things
> [and 1 more messages]"):
>> Am 04.01.2017 um 12:07 schrieb Ian Jackson:
>>> I think #844785 needs a fix though.
>>
>> Ag
On Thu, 2017-01-05 at 11:22 +0100, Adam Borowski wrote:
> Neither systemd-shim nor consolekit are solutions that are viable in
> the long term, the sooner we get rid of both, the better. I don't
> know what's a good alternative, though. Loginkit is
> vapourware. Elogind maybe?
With elogind do y
Adam Borowski writes ("Re: "not authorised" doing various desktoppy things [and
1 more messages]"):
> In my experience, systemd-shim never worked in the first place, so this is
> no regression. I see results that Ian observes since the day policykit and
> friends w
On Wed, Jan 04, 2017 at 07:21:42PM +0100, Michael Biebl wrote:
> Am 04.01.2017 um 12:07 schrieb Ian Jackson:
> > I think #844785 needs a fix though.
>
> Agreed. Does anyone who uses sysvinit want to look into this?
In my experience, systemd-shim never worked in the first place, so this is
no reg
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things [and
1 more messages]"):
> Am 04.01.2017 um 12:07 schrieb Ian Jackson:
> > I think #844785 needs a fix though.
>
> Agreed. Does anyone who uses sysvinit want to look into this?
Um, me
Am 04.01.2017 um 12:07 schrieb Ian Jackson:
> I think #844785 needs a fix though.
Agreed. Does anyone who uses sysvinit want to look into this?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP d
On Wed, 04 Jan 2017 at 02:10:56 +, Ian Jackson wrote:
> Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> > Check if your session is marked as active and local
> > $ loginctl show-session $XDG_SESSION_ID
>
> I see
Ansgar Burchardt writes ("Re: "not authorised" doing various desktoppy things
[and 1 more messages]"):
> Ian Jackson writes:
> > In fact I didn't have libpam-systemd installed for some strange
> > reason, but installing it hasn't helped. (All the symp
Ian Jackson writes:
> Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> I'm not sure I need "logind integration" in my X server but perhaps I
> do ?
Only if you want to start X as non-root.
> Simon McVittie writes
On Jan 03 2017, Ian Jackson wrote:
> Recently, my nm-applet can no longer control my network-manager
> daemon. I get a message saying[1]:
>
> "org.freedesktop.NetworkManager.network-control-request failed: not
> authorized"
>
> I think this is related to a similar problem in *-power-manager,
Michael Biebl writes ("Re: "not authorised" doing various desktoppy things"):
> Check if your session is marked as active and local
> $ loginctl show-session $XDG_SESSION_ID
I see (amongst other things):
Remote=no
Active=yes
State=active
> Might be #844785
On Tue, 03 Jan 2017 at 21:59:05 +, Sune Vuorela wrote:
> If I recall correctly, for most
> networky (and removable media things), the default policykit
> configuration is that 'local logged in users' are allowed to do this.
They must usually be active as well as locally logged in. (This means
On 2017-01-03, Ian Jackson wrote:
> Can someone please help explain to me how these things are supposed to
> work ? Specifically, how is (presumably as a consequence of me
> logging in using a display manager) my session supposed to be granted
> the ability to manage various system resources like
Am 03.01.2017 um 21:05 schrieb Ian Jackson:
> Recently, my nm-applet can no longer control my network-manager
> daemon. I get a message saying[1]:
>
> "org.freedesktop.NetworkManager.network-control-request failed: not
> authorized"
>
> I think this is related to a similar problem in *-power
Recently, my nm-applet can no longer control my network-manager
daemon. I get a message saying[1]:
"org.freedesktop.NetworkManager.network-control-request failed: not
authorized"
I think this is related to a similar problem in *-power-manager,
#848623.
I am running:
* sysvinit
* lightdm
27 matches
Mail list logo
