[Maverick] Errors whenever opening a terminal

[Delan Azabani]

With the latest Maverick dev updates as of today, I've started receiving new errors at the top of any terminal I open:

bash: /etc/bash_completion.d/apt: line 32: syntax error near unexpected token `;'
bash: /etc/bash_completion.d/apt: line 32: ` 2> /dev/null ); $( apt-cache --no-generate pkgnames "lib$cur" \'
bash: /etc/bash_completion.d/apt: line 33: syntax error near unexpected token `)'
bash: /etc/bash_completion.d/apt: line 33: ` 2> /dev/null); )'

After these errors I am faced with the normal prompt and can continue working normally:

delan@delan-desktop:~$

[Jean-Baptiste Lallement (jibel)]

confirmed in maverick.

[Jean-Baptiste Lallement (jibel)]

The fix is to remove the semi colons

--- apt 2010-05-28 11:45:21.000000000 +0200
+++ /etc/bash_completion.d/apt 2010-05-28 11:59:45.000000000 +0200
@@ -29,8 +29,8 @@
                 ;;
             *)
                 COMPREPLY=( $( apt-cache --no-generate pkgnames "$cur" \
- 2> /dev/null ); $( apt-cache --no-generate pkgnames "lib$cur" \
- 2> /dev/null); )
+ 2> /dev/null ) $( apt-cache --no-generate pkgnames "lib$cur" \
+ 2> /dev/null) )
                 return 0
                 ;;
         esac

[Delan Azabani (azabani)]

Thanks Jean-Baptiste, that worked perfectly.

[Jimmy Xu (jimmyxu)]

Should this be a duplicate of bug #546794?

[Anders Kaseorg (andersk)]

Here is the patch I posted in bug #546794.

[Adam Conrad (adconrad)]

Please see the mentioned bug for arguments about reverting this instead of fixing it. Tempted to revert it myself, but I'd rather have a consensus with the original uploader than start and archive war. :)