CentOS - Apr 2020 - Weird bug in 389 Directory Server : no spaces in admin console (CentOS 7)

Le 26/04/2020 ? 08:31, Gordon Messmer a ?crit?:
> Are you sure the input lacked a space character, and that this isn't
just a
> font rendering bug?
100 % positive.

I tried it on a different sandbox server without X installed, but only with
xorg-x11-xauth.
>From my workstation running OpenSUSE Leap 15.1, I connected to my admin
console
using the following command:

$ ssh -X microlinux at 192.168.2.5 /usr/bin/389-console -a
http://192.168.2.5:9830

And I have the same problem here. When I try to fill out the "UserID"
field
with "cn=Directory Manager", I can't put in a space after
"cn=Directory". I can
hit the space bar as much as I want, the cursor won't budge.

I'm puzzled.

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32
Mob. : 06 51 80 12 12

Le 26/04/2020 ? 08:45, Nicolas Kovacs a ?crit?:
> 100 % positive.
> 
> I tried it on a different sandbox server without X installed, but only with
> xorg-x11-xauth.
> 
> From my workstation running OpenSUSE Leap 15.1, I connected to my admin
console
> using the following command:
> 
> $ ssh -X microlinux at 192.168.2.5 /usr/bin/389-console -a
http://192.168.2.5:9830
> 
> And I have the same problem here. When I try to fill out the
"UserID" field
> with "cn=Directory Manager", I can't put in a space after
"cn=Directory". I can
> hit the space bar as much as I want, the cursor won't budge.
> 
> I'm puzzled.
I investigated this some more. Here's what I found.

Installed a vanilla CentOS 7 GNOME desktop.

Activated EPEL and installed 389-ds.

Launched the setup script for 389 DS.

Works perfectly bot locally and from my remote workstation with ssh -X.

So far, so good.

Back in 2019 I ran 389 DS on a minimal CentOS 7 installation. Installed 389-ds
from EPEL, installed xorg-x11-xauth, and then opened the graphical admin
console from my workstation.

But when I do this now, I can't seem to use spaces in the admin
console's input
fields.

Any suggestions ?

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32
Mob. : 06 51 80 12 12

Le 26/04/2020 ? 11:43, Nicolas Kovacs a ?crit?:
> I investigated this some more. Here's what I found.
> 
> Installed a vanilla CentOS 7 GNOME desktop.
> 
> Activated EPEL and installed 389-ds.
> 
> Launched the setup script for 389 DS.
> 
> Works perfectly bot locally and from my remote workstation with ssh -X.
After some more experimenting, I can confirm this is a serious bug. After
updating all packages on the system, it just reappeared.

Here's how you can reproduce it.

1. Install CentOS 7.7 but without updating the system.

2. Activate EPEL.

3. Install 389-ds.

3. Setup 389 DS.

4. Launch 389 Admin console.

5. Login as "cn=Directory Manager"

6. Everything works perfectly.

7. Update the system : yum -y update

8. Launch 389 Admin console.

9. Last entry appears as "cn=DirectoryManager" and there is no way to
add a
space between "Directory" and "Manager".


I did what I could to investigate this bug. But at this point, I'm clueless.

Cheers,

Niki

-- 
Microlinux - Solutions informatiques durables
7, place de l'?glise - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info at microlinux.fr
T?l. : 04 66 63 10 32
Mob. : 06 51 80 12 12

On 4/25/20 11:45 PM, Nicolas Kovacs wrote:
> Le 26/04/2020 ? 08:31, Gordon Messmer a ?crit?:
>> Are you sure the input lacked a space character, and that this
isn't just a
>> font rendering bug?
> 100 % positive.  ...   I can
> hit the space bar as much as I want, the cursor won't budge.

(It sounds like you've solved this, but:)

Pressing the space bar and seeing the cursor render in the same place 
doesn't tell you whether the problem is a rendering issue or an 
inability to input spaces.? I meant to suggest that you save the entry 
and look at whether or not the resulting LDAP values contained the 
spaces you couldn't see in the console.

Your description of the problem doesn't suggest that you can't input 
spaces, just that you can't see that you've input them.