Yves-Alexis Perez wrote:
> On jeu, 2009-06-18 at 11:33 +0200, Michael Biebl wrote:
>> Yves-Alexis Perez wrote:
>>> What about the non gdm/kdm cases? There'll be an ongoing X11 session,
>>> but I guess it won't be in consolekit session? Even if
>>> libpam-ck-connector is used?
>> Sorry, I don't quit
On jeu, 2009-06-18 at 11:33 +0200, Michael Biebl wrote:
> Yves-Alexis Perez wrote:
> > What about the non gdm/kdm cases? There'll be an ongoing X11 session,
> > but I guess it won't be in consolekit session? Even if
> > libpam-ck-connector is used?
>
> Sorry, I don't quite understand. Could you ex
Yves-Alexis Perez wrote:
> What about the non gdm/kdm cases? There'll be an ongoing X11 session,
> but I guess it won't be in consolekit session? Even if
> libpam-ck-connector is used?
Sorry, I don't quite understand. Could you explain in more detail what you mean.
Cheers,
Michael
--
Why is it
On jeu, 2009-06-18 at 11:22 +0200, Michael Biebl wrote:
> Please test and let me know if it works for you.
> If you run startx from the console (with or without
> libpam-ck-connector
> enabled), you should get an X11 session.
> When you use gdm/kdm, you should *not* get double ck sessions.
I'll tr
Michael Biebl wrote:
> Yves-Alexis Perez wrote:
>> On mer, 2009-04-29 at 08:55 +0200, Michael Biebl wrote:
>
>>> That's why I proposed the idea of an additional/separate env var, that will
>>> only
>>> be set for console logins, so we can easily differentiate X11 from console
>>> logins in Xsessi
Yves-Alexis Perez wrote:
> On mer, 2009-04-29 at 08:55 +0200, Michael Biebl wrote:
>> That's why I proposed the idea of an additional/separate env var, that will
>> only
>> be set for console logins, so we can easily differentiate X11 from console
>> logins in Xsession.d/90consolekit.
>
> That c
On mer, 2009-04-29 at 08:55 +0200, Michael Biebl wrote:
> >
> > The I just fail to see why libpam-ck-connector from oustide of X creates
> > the XDG_SESSION_COOKIE. What is it used for?
>
> Trying to answer both of your questions:
> It's indeed questionable, what a CK session on the console is g
Yves-Alexis Perez wrote:
> On mer, 2009-04-29 at 08:14 +0200, Michael Biebl wrote:
>>> I aggree. I mean, libpam-ck-connector should _only_ sets the variable if
>>> it's indeed an XDG_SESSION. I mean, only if the user logged in through a
>>> CK-enabled DM. (I didn't yet test with slim and libpam-ck-
On mer, 2009-04-29 at 08:14 +0200, Michael Biebl wrote:
> >
> > I aggree. I mean, libpam-ck-connector should _only_ sets the variable if
> > it's indeed an XDG_SESSION. I mean, only if the user logged in through a
> > CK-enabled DM. (I didn't yet test with slim and libpam-ck-connector
> > activate
Yves-Alexis Perez schrieb:
>>> I guess it would be better for all the ConsoleKit-using display managers
>>> to, if they insist on not relying on libpam-ck-connector, to set a
>>> common environment variable that the script can test for.
>
> I aggree. I mean, libpam-ck-connector should _only_ sets
On ven, 2009-04-24 at 17:43 +0200, Michael Biebl wrote:
I'm jumping on this issue because we have the same kind of problems.
90consolekit “ignore” when libpam-connector is enabled bites us at Xfce
because quite a lot of people will use console to login.
> > Alternatively, what do you think about
Sam Morris schrieb:
> On Tue, 2009-03-24 at 19:19 +0100, Michael Biebl wrote:
>> Sam Morris wrote:
what's happening (afaics) is this.
1.) you have libpam-ck-connector installed, which with version 0.3.0-1 is
now
automatically enabled (using pam-auth-update)
2.) When y
On Tue, 2009-03-24 at 19:19 +0100, Michael Biebl wrote:
> Sam Morris wrote:
> >> what's happening (afaics) is this.
> >>
> >> 1.) you have libpam-ck-connector installed, which with version 0.3.0-1 is
> >> now
> >> automatically enabled (using pam-auth-update)
> >> 2.) When you login on the console
Sam Morris wrote:
>> what's happening (afaics) is this.
>>
>> 1.) you have libpam-ck-connector installed, which with version 0.3.0-1 is now
>> automatically enabled (using pam-auth-update)
>> 2.) When you login on the console, XDG_SESSION_COOKIE will be set by the pam
>> module
>> 3.) you then sta
> what's happening (afaics) is this.
>
> 1.) you have libpam-ck-connector installed, which with version 0.3.0-1 is now
> automatically enabled (using pam-auth-update)
> 2.) When you login on the console, XDG_SESSION_COOKIE will be set by the pam
> module
> 3.) you then start your X session via st
Sam Morris wrote:
>> does it help if you logout/login?
>
> Hi Michael,
>
> Logging out does not help. It seems that ck-launch session simply does
> not do anything when launched via the Xsession script when run from
> startx.
Yeah, I only noticed that you were using startx after hitting the send
> does it help if you logout/login?
Hi Michael,
Logging out does not help. It seems that ck-launch session simply does
not do anything when launched via the Xsession script when run from
startx.
I disagree that this is only of 'normal' severity, since it prevents
other things on the system from
Package: gnome-power-manager
Version: 2.24.4-1
Severity: grave
Justification: renders package unusable
After upgrading to the latest consolekit package:
ii consolekit 0.3.0-2framework for defining and tracking users, s
gnome-power-manager no longer wants to suspend my machine when
18 matches
Mail list logo
