aptitude display corruption in jaunty

Bug #324731 reported by Antony Shen on 2009-02-03
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
aptitude (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: aptitude

This is similar to Bug #324728, occurs in jaunty. My locale is zh_TW.UTF-8, and desktop is gnome. When I use aptitude in gnome-terminal, the display would corrupt when I press F10 to display menu, as shown in the attached pic.

Rolf Leggewie (r0lf) wrote :

FWIW, looks fine for me in a Japanese locale. Sorry, I don't have a Chinese locale installed to test.

Still an issue?

Yes, even if upgrade whole system to current state.

2009/2/23 Rolf Leggewie <email address hidden>:
> FWIW, looks fine for me in a Japanese locale. Sorry, I don't have a
> Chinese locale installed to test.
>
> Still an issue?
>
> --
> aptitude display corruption in jaunty
> https://bugs.launchpad.net/bugs/324731
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
---
Best Regards,
Antony Shen

Antony Shen (antony-shen) wrote :

I found corruption only occurs in gnome-terminal or libvte derivates, konsole is ok in running mc or aptitude.

WangLu (coolwanglu) wrote :

also confirmed in en_US.UTF-8 (my locale envs are all en_US.UTF-8, except LC_CTYPE & LC_TIME are zh_CN.UTF-8),

However, `LC_ALL=en_US.UTF-8 aptitude' won't help, but `LC_ALL=C aptitude' would

Changed in aptitude (Ubuntu):
status: New → Incomplete
BlueLight (bluelight-auroville) wrote :

the bug occured in Jaunty, there was no update on it since 2009, so I wanted to clean up and see if it's actually valid by setting it to Incomplete, marked back to NEW, sorry.

Changed in aptitude (Ubuntu):
status: Incomplete → New
Daniel Hartwig (wigs) wrote :

> the bug occured in Jaunty, there was no update on it since 2009,

Indeed. It could use some triage which for this issue I can not provide (I do not run a full Ubuntu desktop).

Did you try to reproduce it with the mentioned locale and gnome-terminal?

> so I
> wanted to clean up and see if it's actually valid by setting it to
> Incomplete,

Incomplete is for bugs without enough information. In this case (without further testing) it looks like we do have enough information, but need someone to do the testing and find out what is (was) going on.

> marked back to NEW, sorry.

Thanks, this is the correct state for bugs which are not triaged/confirmed.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers