New gq unable to connect a ldap server

Bug #110278 reported by Massimo Forti
24
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gq (Ubuntu)
Won't Fix
Undecided
Unassigned
Declined for Feisty by Brian Murray
Declined for Jaunty by Andreas Moog
Declined for Karmic by Andreas Moog

Bug Description

After upadte from 6.04 to 7.04 I was not able to use GQ to connect my notebook with the openLdap server.
When I click on the server name the tool ask me the password, but after not connect with it.
To use it I must inset in /home/user/.gq file the password.

Revision history for this message
Mozg (andrei-arhont) wrote :

I have the same problem with gq 1.2.1-2 on Ubuntu 7.04. After asking for password the program does nothing. I can't even see the connection being made. Tcpdump shows nothing.

Changed in gq:
assignee: nobody → sven-herzberg
status: Unconfirmed → Needs Info
Changed in gq:
assignee: sven-herzberg → nobody
Revision history for this message
Joe Baker (joebaker) wrote :

7.04 Ubuntu i386.
My configs were working under Edgy (6.10).
Now after fresh install I can't get gq to connect to our LDAP server.
Background. Our LDAP server is running on an old Mandrake 9.1 machine.
It likely does not support TLS connections. I usually refer to it by it's IP address.

-Joe Baker

Revision history for this message
Paul De Audney (paul-messinthecorner) wrote :

As per the /usr/share/doc/gq/README.Debian it suggests you manually create your configuration file as there is a known issue with connecting to your ldap server.
And your server configuration disappearing.

I manually edited my ~/.gq file to contain the following <ldapserver> section.

    <ldapserver>
        <name>LDAP Server</name>
        <ldaphost>ldaps://ldapmaster.foo.domain.tld</ldaphost>
        <ldapport>389</ldapport>
        <basedn>dc=domain,dc=net,dc=au</basedn>
        <binddn>cn=Manager,dc=domain,dc=net,dc=au</binddn>
        <search-attribute>cn</search-attribute>
        <ask-pw>True</ask-pw>
        <pw-encoding>Base64</pw-encoding>
    </ldapserver>

Originally my <ask-pw> section was set to False, and there was no <pw-encoding> section.
Add these and restart gq, you client should now connect successfully. (Mine did anyway)

Revision history for this message
Paul De Audney (paul-messinthecorner) wrote :

Feisty i386
gq version 1.2.1-2

Revision history for this message
John Eckersberg (johnny1) wrote :

I also was unable to connect to servers. Adding <ask-pw>True</ask-pw> fixed it for me. Thanks Paul!

Revision history for this message
Joe Baker (joebaker) wrote :

I had to check "Remember Password" at the initial password dialog.
Without checking it I had no success.
Apon selecting the remember password box, then entering the password, next a KeyRing dialog came up. It was the first time I'd seen this behavior in Gnome. I'd seen it in KDE's Wallet applications before.

Here's a snip of my configurations...

    <ldapserver>
        <name>fire2.nelfc.com</name>
        <ldaphost>ldap://fire2.nelfc.com</ldaphost>
        <ldapport>389</ldapport>
        <basedn>dc=nelfc,dc=com</basedn>
        <binddn>cn=root,dc=nelfc,dc=com</binddn>
        <search-attribute>cn</search-attribute>
    </ldapserver>

Thanks for the neat program!
Sincerely,
Joe Baker

Changed in gq:
status: Needs Info → Confirmed
Revision history for this message
Herbert Straub (herbert) wrote :

I can confirm this bug. GQ doesn't work under Kubuntu, because there is no Gnome keyring manager available. Second, gq works only, if i'm using the Password manager. I think, the attached patch fix the problem: Now, I can use gq under Kubuntu and under Gnome without password manager.

Revision history for this message
Herbert Straub (herbert) wrote :

This bug is also registrated in the GQ project on Sourceforge.
BugNr: 1593672 Gq ignores me and doesn't connect to my ldap server
http://sourceforge.net/tracker/index.php?func=detail&aid=1593672&group_id=3805&atid=103805

Revision history for this message
Herbert Straub (herbert) wrote :

I'm using gq nearly every day and this error is not fixed. I created a dpatch file for the gq 1.2.1 package. I also build this gq version for feisty and gutsy. You can install
the gutsy i386 packages, for example, direct from:

http://apt-get.linuxhacker.at/ubuntu/dists/gutsy/universe/pool/gq_1.2.1-2hs1_i386.deb

details on

http://www.linuxhacker.at/opensource-projects/ldap-browser-gq-1-2.1/

It would be nice, if this patch (or another equivalent) attached to the Hardy Version. Thanks, Herbert

Revision history for this message
Sven Herzberg (herzi) wrote :

An update to gq-1.2.2 would include that patch as well...

Revision history for this message
Herbert Straub (herbert) wrote :

Sven, I cannot connect with GQ 1.2.2 under KDE(no Gnome keyring manager available) to the ldap server without my patch. I build the package for the version 1.2.2 for Gutsy:

http://apt-get.linuxhacker.at/ubuntu/dists/gutsy/universe/pool/gq_1.2.2-1hs2_i386.deb

Revision history for this message
Herbert Straub (herbert) wrote :

I found the same bug description in GQ LDAP client Sourceforge Bugtracker with the Nr: 1753419

http://sourceforge.net/tracker/index.php?func=detail&aid=1753419&group_id=3805&atid=103805

and added the patch for this problem.

Revision history for this message
Sven Herzberg (herzi) wrote :

Herbert, I have 2 things to tell:

1. I'm totally sorry. I haven't checked well enough. The patch that I said it was included in 1.2.2 was actually the _only_ change in the 1.2 branch after releasing 1.2.2. Sorry. Really sorry.

2. Thanks for really testing this and providing proper research. Could you go on and try gq from trunk now to make sure 1.4.0 won't have bugs like this one?

Revision history for this message
Herbert Straub (herbert) wrote :

I build and test GQ 1.2.3 with success. I try the Launchpad PPA and build GQ for Feisty, see

https://launchpad.net/~herbert/+archive

Next, we should try to get 1.2.3 in Hardy.

Second, I checked out the SVN and build the trunk. First impression: can connect to the ldap server :-), and browse the tree. But gq hangs, consuming memory and CPU, if i access an object -> killed manually. I think, I need more time to check the situation.

Revision history for this message
Herbert Straub (herbert) wrote :

I fixed the gq hang bug in the trunk version of gq (see sf Request ID: 1875301). The patch:

http://src.linuxhacker.at/patches/gqclient-svn-20080118-formfill-error.patch

Revision history for this message
FRLinux (frlinux) wrote :

I have the same problem. Upgraded to hardy today and version is still 1.2.1 which is clearly old. Compiling from sources using a more recent version fixes my connection issue to the LDAP server. Our workplace is Ubuntu here and we all have to recompile GQ to make it work, pain in the bum.

Revision history for this message
sles (slesru) wrote :

Hello!

After upgrade to hardy gq crashes with segfault when I try to connect to ldap server :-(
Is there solution?

Revision history for this message
Herbert Straub (herbert) wrote :

Hardy containing the buggy version 1.2.1. You can download the version 1.2.3 from my PPA and rebuild the package for hardy: dpkg-buildpackage -uc -us -rfakeroot. This version works without problems.

Revision history for this message
Alex Mauer (hawke) wrote :

It would be nice to eventually see a new GQ version that actually works. Maybe in Karmic?

Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. I noticed the package your bugging against is updated in Lucid. Please update via http://releases.ubuntu.com/lucid/ repost detailed error report, and update the bug status. Thanks!

Revision history for this message
Thomas Schweikle (tps) wrote :

gq is removed from repositories an adequate replacement seems luma.

Revision history for this message
Andreas Moog (ampelbein) wrote : Package removed from the archive

Setting to Won't Fix as the package 'gq' has been removed in Oneiric and Precise and there are better alternatives in the archives. I'm sorry that your report hasn't been dealt with in time, but please continue to report any other bugs you might encounter.

Changed in gq (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.