trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: February 2014

Re: [trinity-devel] Bug 1902 - pam.d and preprocessor checks surrounding consolekit may be part of issue

From: Slávek Banko <slavek.banko@...>
Date: Thu, 27 Feb 2014 02:06:11 +0100
On Thursday 27 of February 2014 01:53:58 David C. Rankin wrote:
> On 02/26/2014 06:08 PM, David C. Rankin wrote:
> > On 02/26/2014 05:06 PM, David C. Rankin wrote:
> >>>> I'll rebuild - this time actually tripping the WITH_SYSTEMD
> >>>> preprocessor flag...
> >>>>
> >>>>
> >>>> Slavek, Francios,
> >>>>
> >>>>   Here is an updated patch that sets the WITH_SYSTEMD preprocessor
> >>>> flag
> >>
> >> Added as:
> >>
> >> http://bugs.pearsoncomputing.net/attachment.cgi?id=1962&action=edit
> >
> > tdebase build with WITH_SYSTEMD preprocessor flag explicitly set with
> > add_definitions(-DWITH_SYSTEMD). I included in as follows:
> >
> > ##### check if systemd is installed #############
> > find_package(Systemd)
> > if(SYSTEMD_FOUND)
> >   add_definitions(-DWITH_SYSTEMD)
> >   message( STATUS "*****  Systemd preprocessor flag WITH_SYSTEMD set 
> > *****" ) else()
> >   message( STATUS "*****  Systemd preprocessor flag WITH_SYSTEMD -- NOT
> > set *****" )
> > endif()
> >
> > testing to follow
>
> The good news - it builds -> the bad news -> I still have a tone of tdeio
> processes open everywhere and loginctl show-session $XDG_USER_SESSION is
> unchanged.
>
> Slavek, you and Francios will need to work on this. It would be 2016 before
> I made it through the process.
>
> For debugging, are you simply adding fprinf(stderr statements or are you
> using a kde utility for log output? I'll go back and load the file with
> fprintf statements and see if I can figure anything else out.
>
> THIS MUST BE DONE BEFORE THE SOFT FREEZE OR TDE WILL NOT WORK ON SYSTEMD
> BASED DISTROS WITH NO CONSOLE KIT -- THIS NEEDS PRIORITY AND SKILLED
> ATTENTION.
>
> Tim this could use your eyes as well....

Moment - in command loginctl show-session you use variable $XDG_USER_SESSION 
instead of $XDG_SESSION_ID? Variable $XDG_USER_SESSION contains something? 
When you try to extractly the same command with variable $XDG_SESSION_ID?

-- 
Slavek