What does "Fix Released" mean?

In short it mean there is a "fix" for the specific reported problem and the fix is/will be delivered with packages-updates

I forgot please made regular update using update-manager (press the update-manager verify button to check) on your system...

Do you mean xxxxxx-updates repositories (for example lucid-updates)? It was the first I checked but unfortunately after they say "Fix Released" nothing appears in xxxxxx-updates.

it can mean there is a fix upstream in Debian too as far as i'm aware.

> it can mean there is a fix upstream in Debian too as far as i'm aware.
Could you tell me how can I use such kind of information to get my issue fixed? I can even rebuld the package if necessary and I just would like to know where can I find any details about a "Fixed issue".

Just for example:
https://bugs.launchpad.net/ubuntu/+source/libpixman/+bug/588612

I use lucid (10.04 LTS) and have installed all of the updates (apt-get update and dist-upgrade). But that issue still affects me. So I'm not sure how can I get it fixed because there are no any detailed information related to "Fix Released" message. And I have the same problem any time when I use launchpad.net. Could anybody help?

Here are two more examples:
https://bugs.launchpad.net/ubuntu/+source/unr-meta/+bug/443298
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135

Normally, fix released means the bug got fixed and a new, fixed package is available in your update-manager. The newer bugs got different assignments for every Ubuntu version, see for example https://bugs.launchpad.net/ubuntu/+source/linux/+bug/751689
As you can see, this bug got already fixed in Debian, but not in the different Ubuntu versions. In general, the newest Ubuntu version is getting the most bug fixes. It may happen that only important bug fixes get ported back to older Ubuntu versions.

To your bugs:
#1 The bug got fixed in Ubuntu Maverick, but unfortunately not in Lucid, as I read from the bug comments. So you would need to upgrade your distribution.
#2 This bugs solution was that the package was entirely dropped from Ubuntu, as it was buggy and unneeded (see https://bugs.launchpad.net/ubuntu/+source/unr-meta/+bug/443298/comments/5 ) So, if you still have it installed, you should better remove it ;)
#3 According to https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/207135/comments/37 , the bug was fixed in Pulseaudio package version 0.9.14-0ubuntu11 on Ubuntu Jaunty. If you have this version or any above, the problem should be fixed now.

My suggestion to you: Just wait one week until the new Ubuntu Long Term Stable (LTS) version 12.04 (Precise) arrives and make a dist-upgrade. I'm pretty sure your problems are fixed then :)
If your still experiencing any bugs, open a new bug report and if you think its the same problem as in another report, mention the other one in your new report. That makes it easier for the devs to find a solution or to mark it as a duplicate

Daniel, thank you for the such detailed answer.

I would say I can understand reasons of not fixing some bugs in a current release. At the same time I couldn't understand why "Fix Released"?
"Won't fix" with comment "will be fixed in the next release (let's say karmic)" is okay.
"Won't fix" with comment "fixed in debian upstream http://blablabla or package version" is also okay.
But "Fix Released" make me confused everytime.

Are there any ideas if it can be changed and how we can help to change it?

Maybe ask bug squad on #ubuntu-bugs channel.

Status overview.
https://wiki.ubuntu.com/Bugs/Status

KB Overview.
https://wiki.ubuntu.com/BugSquad/KnowledgeBase

Actually "Fix Released" is clearly assigned to a project.
e.g. if evince was fixed in gnome bugzilla or rather in git that doesn't mean it's fixed in Ubuntu.
The status in evince (ubuntu) can be something else, Ubuntu may commit the fix for current version, backport the fix to previous or won't fix at all and merges the fix into newer version only.

Since a bug reporter also is supposed to manage reported bugs it's possible that he finds a newer package or an update fixed the issue, then the bug reporter refers in a comment and selects 'fix released' from the list.

Thank you Sam.

It looks like system is designed not for users but for developers and it's not clear for users. Since only now I can understand that "Fix Released" means almost nothing for me as for Ubuntu LTS user.

As I see so far the only way to get necessary informatoin (I mean information about "where it was exactly fixed?") is "ask bug squad on #ubuntu-bugs channel". It's not easy and takes a lot of time to get a simple answer for a simple question. It would be good if it chaged in someway in order to give more infromation for end users and I'm not sure how can I help to make it happen.

Regarding "where it was exactly fixed?" please post bug number which you're referring to, thanks.
Or just click on the package/project -> overview -> trunk to find the package. Also the changelog can be found in overview.
Or search at packages.ubuntu.com

The example in #6 was apparently fixed in 10.10 and never backported to 10.04, hence nothing to find there, except to install a newer version of evince manually or installing an alternative application.

The 'ask bug squad' referred to
> how can I help to make it happen

in case you'd like to contribute or make a suggestion.

LTS necessarily doesn't get every update which is available out there.
https://wiki.ubuntu.com/LTS

The example bug 588612 affected 4 people which influence priority and proportionality.
There also might be other reasons why a package doesn't get backported, for example simply the lack of man-power.
https://wiki.ubuntu.com/ContributeToUbuntu

> Regarding "where it was exactly fixed?" please post bug number which you're referring to, thanks. Or just click on the package/project -> overview -> trunk to find the package. Also the changelog can be found in overview. Or search at packages.ubuntu.com

Thank you Sam, I'll try to go that way in future. It's a general question because I've got the the same situation many times and would like to know what can I do in future.

> The example in #6 was apparently fixed in 10.10 and never backported to 10.04, hence nothing to find there, except to install a newer version of evince manually or installing an alternative application.

It's understandable, I just would like usually to know:
- what it the current state of fixing particular bug in my version of Ubuntu
- if it won't be fixed I would like also to know:
-- in what verstion of Ubuntu it will be or has already been fixed?
-- where, for example, I can download a patch (it's not usually a big deal to download sources of a package, patch it and rebuild with "dpkg-buildpackage")
Such kind of information is probably exist somewhere but it's not easy (takes a lot of time) to find it for a particular bug.

> The example bug 588612 affected 4 people which influence priority and proportionality. There also might be other reasons why a package doesn't get backported, for example simply the lack of man-power.
Not backporting and not fixed but are not usually problems (for me), problem is lack of information especially when I see "Fix Released". If fix isn't released I'll go to google/forums or even dowload sources and try to fix, but if "Fix Released" I'm trying to find that fix and each time I'm not sure "where it is", is it already in repository of my Ubuntu version or not, or ...

> The 'ask bug squad' referred to
>> how can I help to make it happen
Do you mean I should ask 'bug squad' about lack of infromation?

> Again, "Fix Released" tag is assigned to the project/package, what is the problem to click on that project/package and review the changelog, code, source via overview?

I'm not a developer, I'm just a user. I don't spent much time on launchpad and I go there if only I have a problem. So I didn't know that I should/can "click on that project/package and review the changelog, code, source via overview?". Since now I know that and I'll try to go this way next time but I suppose there are still a lot of users who have the same questions.

Thank you. I'm closing this question.

Thanks Sam_, that solved my question.

> I'm not a developer, I'm just a user.

Me too.

> didn't know that I should/can "click on that project/package and review

Stanislav, this is why it's called *open source* or FOSS.
https://en.wikipedia.org/wiki/Alternative_term_for_free_software

> Stanislav, this is why it's called *open source* or FOSS.
Yes, sure Sam :)
It's usually clear with mozilla/redmine/archlinux/proxmox. I can always see something like "fixed in 12.1" or "is going to be fixed in 13.6". Same thing with interfaces and changelogs - they are clear. But launchpad isn't clear for me. "Answers" section I also found unintentionally.

Well then share your suggestions with the launchpad team. Below this inbox is 'Read the Guide' when you click on that it opens up the front page of the 'launchpad world' which also incl. contact information.

> Well then share your suggestions with the launchpad team. Below this inbox is 'Read the Guide' when you click on that it opens up the front page of the 'launchpad world' which also incl. contact information.

Sam, could you give me a hint where exactly should make a suggestion? I opened "Read the guide" but not sure where to go.