Bug 1752367

Summary: Type to search entry doesn't show typed letters
Product: Red Hat Enterprise Linux 7 Reporter: Milan Crha <mcrha>
Component: gnome-shellAssignee: Florian Müllner <fmuellner>
Status: CLOSED ERRATA QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.7CC: jadahl, lmiksik, mboisver, rstrode, sdodson, tpelka
Target Milestone: rc   
Target Release: 7.8   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: gnome-shell-3.28.3-23.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-31 19:39:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Milan Crha 2019-09-16 07:48:23 UTC
Using gnome-shell-3.28.3-16.el7.x86_64, the "Type to search" entry in the Activities overview doesn't show typed letters, it shows only dots, like if the entry has set the "password" flag.

Comment 2 Milan Crha 2019-09-16 12:09:02 UTC
I just noticed, it does that only when the gnome-shell process is slowed down, might be due to valgrind (I had it running under valgrind). When I run gnome-shell without valgrind it shows the letters as expected. Maybe some call timeouts due to all valgrind checking. I'm only guessing here.

Comment 3 Michael Boisvert 2019-09-18 16:18:31 UTC
(In reply to Milan Crha from comment #2)
> I just noticed, it does that only when the gnome-shell process is slowed
> down, might be due to valgrind (I had it running under valgrind). When I run
> gnome-shell without valgrind it shows the letters as expected. Maybe some
> call timeouts due to all valgrind checking. I'm only guessing here.

Are you using the new classic mode with the overview re-enabled? I noticed this behavior using that scenario, but I could not reproduce on gnome-shell RHEL7.8 Alpha.

Comment 4 Milan Crha 2019-09-18 16:47:08 UTC
No, no classic mode here, but see comment #2.

Comment 5 Michael Boisvert 2019-09-18 16:49:38 UTC
(In reply to Milan Crha from comment #4)
> No, no classic mode here, but see comment #2.

Yes I saw that, just double checking. I'll try to slow down my shell to see if I can reproduce it.

Comment 6 Milan Crha 2019-09-18 16:57:41 UTC
If you want a little help, then my /usr/bin/gnome-shell looks like this:

-----------------------------------------------------------------------
#!/bin/bash

export G_SLICE=always-malloc
FILESUFFIX=`date +%Y%m%d-%H%M%S`

valgrind --show-leak-kinds=definite --num-callers=15 --leak-check=full --aspace-minaddr=0x100000000 \
/usr/bin/gnome-shell.orig "$@" &>/var/tmp/gs-$FILESUFFIX.log

-----------------------------------------------------------------------

Comment 7 Michael Boisvert 2019-10-23 17:53:08 UTC
I can reproduce this on a slightly older machine by just using GNOME for a while (during shell testing), RHEL7.8 Beta 1.3.

Comment 8 Ray Strode [halfline] 2019-11-15 16:10:30 UTC
so this is probably caused by the same thing that caused bug 1772896

Comment 16 Milan Crha 2019-11-26 08:30:42 UTC
I tried with gnome-shell-3.28.3-23 (and mutter 3.28.3-19) and I do not see the issue with those.

I also tried to go back to mutter-3.28.3-15 and gnome-shell-3.28.3-16 and neither there I see it (still running gnome-shell under valgrind). Weird. Maybe some other package update fixed it/helped.

Comment 17 Michael Boisvert 2019-11-26 15:07:23 UTC
(In reply to Milan Crha from comment #16)
> I tried with gnome-shell-3.28.3-23 (and mutter 3.28.3-19) and I do not see
> the issue with those.
> 
> I also tried to go back to mutter-3.28.3-15 and gnome-shell-3.28.3-16 and
> neither there I see it (still running gnome-shell under valgrind). Weird.
> Maybe some other package update fixed it/helped.

I am having similar results, but we can assume this is fixed I suppose.

Comment 18 Milan Crha 2019-11-26 17:32:52 UTC
> we can assume this is fixed I suppose.

Sure, that works for me too.

Comment 20 errata-xmlrpc 2020-03-31 19:39:53 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:1021