[Prev] Thread [Next]  |  [Prev] Date [Next]

Re: [e-users] Setting up Elsa as the Default Display Manager mh Tue Sep 20 02:01:05 2011

On Sep 19, 2011, at 4:25 AM, Cedric BAIL wrote:

> On Mon, Sep 19, 2011 at 9:47 AM, Christian Apeltauer <[EMAIL PROTECTED]> 
> wrote:
>> Am Mon, 19 Sep 2011 12:40:22 +1000
>> schrieb David Seikel <[EMAIL PROTECTED]>:
>>> On Sun, 18 Sep 2011 10:30:47 -0400 mh <[EMAIL PROTECTED]> wrote:
>>>> Don't know. Tried everything, all the suggestions and hints from
>>>> googling, reinstalling everything from svn, at 63455 now. Elsa
>>>> starts, can't type in user name but can select it from the user
>>>> list, can't type in password. Can reboot etc from Elsa.
>>>> In /var/log/elsa.log still see "ERR<2324>: edge edge_tuil.c:2442
>>>> edge_object_size_min_restricted_calc()
>>>> file /usr/local/sare/elsa/themes/default.edj, group elsa has a
>>>> non-fixed part 'password'. Adding 'fined: 1 1;' to source EDC may
>>>> help. Continuing discarding faulty part." No idea on that.
>>>> Elsa looks great, gdm3 awful. This class is very hard.
>>>> On Sep 16, 2011, at 5:04 PM, mh wrote:
>>>>> I found that there was a  /usr/local/etc/pam.d/elsa file. e17 is
>>>>> installed here in /usr/local, so that makes sense. I saved this
>>>>> file to elsa.orig and then copied my /etc/pam.d/gdm file
>>>>> to /usr/local/etc/pam.d/elsa as Jeff suggested, but still had the
>>>>> same result. If it's a pam issue, is there some other path or env
>>>>> that needs to be changed because of the install to /usr/local/?
>>> You may have done that the wrong way
>>> around.  /usr/local/etc/pam.d/elsa would be where compiling elsa put
>>> it's own PAM file, but your system is likely looking for PAM files
>>> in /etc/pam.d.  So copy the first (the one you saved) into the second.
>>> On the other hand, sounds like you just can't type stuff, user name OR
>>> password.  I'll give the standard advice - compile all the EFL AND
>>> elsa from the same SVN revision, and make sure to clean out ALL old
>>> versions of both first.  Might be useful to keep an eye on the
>>> [EMAIL PROTECTED] mailing list, see if there are
>>> any new bug fixes.
>> Since Friday 9th September I am suffering from the same problem as mh.
>> Neither the user nor the password entry accept any input. I have rebuild all 
>> of EFL and elsa twice since then, so far
>> without success. Adding the line suggested by elsa.log to beaumonts.edc
>> did not resolve the problem either. But all entries work fine under
>> elementary_test.
> Yes, there is a bug introduced somewhere in elementary or below that
> broke elsa use of elm entry. Michael is aware of that, but it would
> help, if you could point to the previous svn version that worked and
> the first one that was borked.
> Regards,
> -- 
> Cedric BAIL

Ah, broken package. It was suggested to me to subscribe to enlightenment-svn 
mailing list, which I've done. When a possible fix is made, will there be an 
announcement there so I can know to test it, or maybe another list?



All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
enlightenment-users mailing list