[Luma-users] Re: New version for testing

[Wido D. <wi...@us...>]

On Wednesday 07 July 2004 19:16, Fernando Maior wrote:
> I have been unable to help with LUMA for a long time :(
> Now I have some spare time and I will be back at
> translating and any other way I can help :)

Thanks for your help :)

> Now I am running SuSE 9.1 Professional. I would like
> to tell you that SuSE 9.1 Pro has QT 3.3.1, PyQt 3.11,
> Python 2.3.3, python-ldap 2.0.0pre19, sip 3.10 and
> qscintilla 1.54 in native rpm. And OpenLDAP 2.2.6.
> Easy to install LUMA on it :)

Yeah, that looks good. Except for one thing: python-ldap. You need at least 
version 2.0.1. There is a rpm for SuSE 9.1 on the SF.net site: 
http://sourceforge.net/project/showfiles.php?group_id=2072

> 1. If you start LUMA from the console or from KDE with
>    a console for reading error messages, you realize
>    LUMA shows messages complaining some files are
>    missing:
>
>    Debug: Could not open file for plugin defaults.
>    Could not read configuration file.

I'm going to replace the debugging messages with a logging interface, so the 
user will see only really important messages in a dialog. No console will be 
needed.


>    Also, you cannot save plugins preferences unless
>    you have touched your ${HOME}/.luma/plugins file.
>
>    Solution: create all config files for plugins,
>    if possible. Probably, each plugin should create its
>    own config file.

Confirmed, I'll fix that.


>
> BROWSER PLUGIN
>
> 1. I am using OpenLDAP 2.1.22 on a SuSE 9.0 Pro box,
>    with linux 2.4.21, and, when connecting to that
>    server from my machine using ldapsearch response
>    is imediate and correct. With LUMA 1.4pre2 I only
>    can see the origin of the tree, and the plus sign
>    do not run if you click on it. Also, no error msg
>    is displayed on the console.
>
>    There is some light at the end of the tunnel: I
>    ran a tcpdump/ethereal session on the connection.
>    For that I bound to LDAP as anonymous. Results are:
>    MsgId=1 Bind Request DN=(null)
>    MsgID=1 Bind Result
>    MsgID=2 Search Request, Base DN=o=DASA[Short Frame]
>    MsgID=2 Search Entry[Short Frame]
>    MsgID=2 Search Entry[Short Frame]
>
>    The message for Bind Result showed the Result Code
>    as Success (0x00). The two Search Entries showed
>    the DN for two of my OU: Users and Computers. I
>    have two or three more OU at the same level as
>    those.
>
>    Another run with correct password for bind as admin
>    and tcpdump/ethereal showed:
>    MsgId=1 Bind Request DN=(null)
>    MsgID=1 Bind Result
>    Invalid LDAP message (Can't parse sequence header:
>    wrong type for that item)
>    MsgID=2 Search Request, Base DN=o=DASA[Short Frame]
>    MsgID=2 Search Entry[Short Frame]
>    MsgID=2 Search Entry[Short Frame]
>    MsgID=3 Unbind Request
>
>    With the exception of the 'invalid' and 'unbind' messages,
>    everything seems to be very similar to the other execution.
>    I did try it a number of times, and the 'invalid' message
>    allways is showed.
>
>    If I try to connect with the wrong password, LDAP replies
>    with a Bind Result: Invalid credentials (0x31), which is
>    correct.
>
>    I get to the server list and changed the password
>    for binding to LDAP to a wrong one. No differences.
>
>    Wido, I can get you a copy of the tcpdump file, if you
>    wish. It is very small, less then 20 packets.

This is a problem other people have found on their SuSE 9.1 boxes, too. The 
problem is python-ldap which doesn't work with your OpenLDAP version. 
I've installed SuSE 9.1 and with python-ldap 2.0.1 everything works like a 
charm.

> SERVER LIST
>
> 1. There is a message on the console telling me that
>    "Bookmark loading failed". What is that "bookmark"
>    in the Server List?

Are you sure that this message is really comming when you're opening the 
server dialog? The only reference to this string is in the search plugin. 
Booksmarks are simply stored ldap search filter for faster access.

> Many thanks, LUMA is getting better and better :)

Thanks :)
More changes are comming. Now all ldap operations are threaded. This way you 
won't have any gui-freezing during long running searches, slow network, etc.

bye
  Wido