FS#22977 - Errors when loading git related completion using bash-completion

Attached to Project: Arch Linux
Opened by Gal Gur-Arie (gal_ga) - Sunday, 20 February 2011, 15:31 GMT
Last edited by Eric Belanger (Snowman) - Thursday, 24 February 2011, 12:35 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description: The bash-completion file: /etc/bash_completion.d/git has syntax errors.
This has caused me error while trying to login a Gnome session.

I've used the following workaround in order to solve the problem:
- I've edited my ~/.bashrc file
- Commented the block which is using the bash completion:
#if [ -f /etc/bash_completion ]; then
# . /etc/bash_completion
#fi



Additional info:
============================================================
* package version(s): extra/git 1.7.4.1-1
* config and/or log files etc.

cat ~/.xsession-errors
/etc/gdm/Xsession: Beginning session setup...
/etc/bash_completion.d/git: line 128: syntax error near unexpected token `<'
/etc/bash_completion.d/git: line 128: ` done < <(git config -z --get-regexp '^(svn-remote\..*\.url|bash\.showupstream)$' 2>/dev/null | tr '\0\n' '\n ')'
/etc/bash_completion.d/grub: line 417: `_grub_mkpasswd-pbkdf2': not a valid identifier

Steps to reproduce:
1). Install bash-completion (extra/bash-completion 1.3-2)
2). Enable it in your user's bashrc file by adding:
if [ -f /etc/bash_completion ]; then
. /etc/bash_completion
fi

to ~/.bashrc

3). At the GDM screen enter user+password

Expected result:
============================================================
Enter active Gnome (or other) session

Buggy Result:
============================================================
I've returned back to the GDM screen

The local xsession error file had:

cat ~/.xsession-errors
/etc/gdm/Xsession: Beginning session setup...
/etc/bash_completion.d/git: line 128: syntax error near unexpected token `<'
/etc/bash_completion.d/git: line 128: ` done < <(git config -z --get-regexp '^(svn-remote\..*\.url|bash\.showupstream)$' 2>/dev/null | tr '\0\n' '\n ')'
/etc/bash_completion.d/grub: line 417: `_grub_mkpasswd-pbkdf2': not a valid identifier
This task depends upon

Closed by  Eric Belanger (Snowman)
Thursday, 24 February 2011, 12:35 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Problem in user config.
Comment by Ionut Biru (wonder) - Sunday, 20 February 2011, 16:41 GMT
is your system fully up to date? especially filesystem

we had that in the past and is fixed.  FS#20288 
Comment by Gal Gur-Arie (gal_ga) - Sunday, 20 February 2011, 17:10 GMT
Yes. the system is getting updates on daily base, usually even few times a day.
Issue  FS#20288  is from 2010 and my system has been installed on a new machine on January 2011.
Comment by Ionut Biru (wonder) - Sunday, 20 February 2011, 17:15 GMT
the idea was to check that bug, see if you have junks in your setup.

you don't have to load again it again in ~/.bashrc. Is enabled by default if bash-completion is installed. check out that in /etc/bash.bashrc
Comment by Gal Gur-Arie (gal_ga) - Sunday, 20 February 2011, 17:33 GMT
Hi,

I've removed the bash-completion load from my ~/.bashrc and it is loaded by default as you've mentioned.
About the system - it a clean installation:
[2011-01-06 17:28] installed filesystem (2010.12-1)

I had those lines in my ~/.bashrc since I've migrated from Debian GNU/Linux to Arch on January, but with the same configuration I've rebooted the system a few times without any problem to login to a Gnome session.
Last time I've rebooted before today was at the end of January:
[2011-01-31 08:35] upgraded kernel26 (2.6.36.3-2 -> 2.6.37-5)

The system has worked as expected, today I got the upgraded kernel26 (2.6.37-5 -> 2.6.37-6) and rebooted.
This time I've noticed the mentioned problem. so with the same .bashrc the system worked ok more then 2 weeks ago.
Comment by Eric Belanger (Snowman) - Sunday, 20 February 2011, 20:38 GMT
There was recent changes in the bash package. That might explain why it was working before.

Loading...