unable to handle error-condition: bad proxy setting

Bug #200579 reported by infoape
2
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: command-not-found

I know this is low on the prioirty list and indicative of my bad typing skillz but all the same I thought I should report it. This is not a graceful way of handling an error condition. I need to manually control my /etc/apt/apt.conf file with a Proxy setting because of th e nature of my companies Internet access control. If I have the proxy setting commented out and I type in an unknown command, "command-not-found" seems to have a problem parsing the apt.conf file and barfs. Output is below.

ifocnfig -a

KABOOOM!!!

Whoops, command-not-found has crashed! Please file a bug report at:
https://bugs.launchpad.net/ubuntu/+source/command-not-found
Please include the following information with the report:
E:Syntax error /etc/apt/apt.conf:1: Unsupported directive 'Acquire::http::Proxy'
Traceback (most recent call last):
  File "/usr/lib/command-not-found", line 24, in <module>
    CommandNotFound(options.data_dir).advise(args[0])
  File "/usr/lib/python2.5/site-packages/CommandNotFound/CommandNotFound.py", line 72, in __init__
    self.sources_list = self._getSourcesList()
  File "/usr/lib/python2.5/site-packages/CommandNotFound/CommandNotFound.py", line 93, in _getSourcesList
    apt_pkg.init()
SystemError: E:Syntax error /etc/apt/apt.conf:1: Unsupported directive 'Acquire::http::Proxy'
Python version: 2.5.1 final 0
bash: ifocnfig: command not found

cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=7.10
DISTRIB_CODENAME=gutsy
DISTRIB_DESCRIPTION="Ubuntu 7.10"

apt-cache policy command-not-found
command-not-found:
  Installed: 0.2.8ubuntu2
  Candidate: 0.2.8ubuntu2
  Version table:
 *** 0.2.8ubuntu2 0
        500 http://us.archive.ubuntu.com gutsy/main Packages
        100 /var/lib/dpkg/status

Revision history for this message
Daniel T Chen (crimsun) wrote :

Is this symptom still reproducible in 8.10 or 9.04?

Changed in command-not-found:
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

Changed in command-not-found:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.