some garbage on name resolution failure

Bug #31028 reported by chastell
8
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

When aptitude 0.2.15.9-3ubuntu6 can’t resolve the domain name of the repository, the error shows as

Temporary failure resolving \uffff~@~Xarchive.ubuntu.com\uffff~@~Y

(the \uffff parts show as empty Unicode squares).

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

I think this is fixed in dapper, I wasn't able to reproduce it there (tried to run:
# aptitude update
with a invalid domain name in sources.list).

Was that the correct way to reproduce it?

It would be great if you could confirm that (e.g. with a recent live-cd).

Cheers,
 Michael

Changed in aptitude:
status: Unconfirmed → Needs Info
Revision history for this message
chastell (chastell) wrote :

Running `sudo aptitude update` in gnome-terminal from the terminal gives the proper (for en_GB.UTF-8 locale) line of (note the curly quotes)

Could not resolve ‘niema.takiego.numeru’

but running aptitude in the ncurses interface and doing an ‘u’ for update gives

Could not resolve \uffff~@~Xniema.takiego.numeru\uffff~@~Y

It might be a ncurses bug, but, for example, the interface’s semigraphic boxes (e.g. for the ‘Downloaded 4B in 1s (3B/s)’ box) are painted properly.

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for this additional information.

aptitude in dapper is using utf8 all over the place now in the gui. So this problem should be gone (and I can't reproduce it on my dapper box).

Thanks,
 Michael

Revision history for this message
chastell (chastell) wrote :

FWIW, sid’s aptitude 0.4.1-1 works ok on my Debian box; sorry for not checking this earlier.

Thanks, I’ll close this bug.

Revision history for this message
chastell (chastell) wrote :

Fixed in Dapper’s aptitude 0.4.

Changed in aptitude:
status: Needs Info → Fix Committed
Revision history for this message
Carthik Sharma (carthik) wrote :

Thank you for reporting this bug.

I am changing the Status to "Fix Released" (and closing the bug) since, indeed, this fix is now available to everyone, as confirmed by the reporter.

Changed in aptitude:
status: Fix Committed → Fix Released
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.