Can somebody tell me why when i enter “$.*” into my terminal it comes up with this weird error? really not sure what i am looking at here .
I can repo the bug. Please raise a bug against bash in the fedora bug tracker.
You would need to specify what the expression $.* expands to, as that would be important for determining what program is having the error. It won’t be glibc as specified in your subject line.
You can run set -x and then run your command again. Bash will then tell you excatly what it was trying to start.
Since the error happened right after a “command not found”, this is probably the PackageKit-command-not-found package in action. I’ll also note that /usr/libexec/pk-command-not-found is linked with libglib. You should probably file a bug against PackageKit.
2 Likes
It tells you the program in the error message which you can confirm with
‘$.*’
Which avoids any expansion in bash and also triggers the bug.
thanks for redirecting me to the correct resource. raising a bug report now 
You should probably change the title of this topic as glib and glibc are two completely different things and that error is coming from glib though there’s a good chance the real problem is in the program that is using glib rather than in the library itself.