IndexError in Volume Control: list index out of range

Have you reported this as a bug?

Hello Eliah,

Not as yet. I wanted to find out if it was related to any existing bugs before filing a new one.

It might be related to (or a duplicate of) one or more existing bugs--one of the steps to take in reporting a bug is to search for related bugs. If you report a bug using Apport, and Apport is launched automatically from a crash, then when you report the bug, Launchpad will automatically search for related bugs. (This doesn't always find all related bugs, but if it doesn't find anything, then generally you should go ahead and report the bug. You should also be aware that it may find related bugs, or related-seeming bugs, that are *not* the same bug that you are trying to report. You have to review the matches to see.)

To report a bug--including the step of searching for related bugs--please first read https://help.ubuntu.com/community/ReportingBugs carefully. Your bug looks like a crash, so I recommend enabling Apport (if it's not enabled already), and then reproducing the bug. You can enable Apport by following the instructions at https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport. After having carefully read the instructions on reporting bugs and having enabled Apport, try to make the crash happen again, and Apport will automatically launch, collect information about the crash, and open a browser window/tab where you can view potentially related bug reports and either indicate that one of them applies, or report it as a new bug.

After you've reported your bug--or found it already reported--you can link the bug and this question to each other by using the "Link existing bug" link on this question page. While it's a good idea to do that, your bug report should be self-contained--the Ubuntu developers should not have to refer to this question page, in order to fully understand and appreciate your bug report.

Hi Eliah,

Many thanks for taking the trouble to reply with such a full (and helpful)
answer,

I will follow your suggestions,

Cheers,

Greg

On Tue, 01 Mar 2011 19:11:17 +1300, Eliah Kagan
<email address hidden> wrote:

> Your question #147202 on awn-extras-applets in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/awn-extras-applets/+question/147202
>
> Status: Open => Answered
>
> Eliah Kagan proposed the following answer:
> It might be related to (or a duplicate of) one or more existing bugs--
> one of the steps to take in reporting a bug is to search for related
> bugs. If you report a bug using Apport, and Apport is launched
> automatically from a crash, then when you report the bug, Launchpad will
> automatically search for related bugs. (This doesn't always find all
> related bugs, but if it doesn't find anything, then generally you should
> go ahead and report the bug. You should also be aware that it may find
> related bugs, or related-seeming bugs, that are *not* the same bug that
> you are trying to report. You have to review the matches to see.)
>
> To report a bug--including the step of searching for related bugs--
> please first read https://help.ubuntu.com/community/ReportingBugs
> carefully. Your bug looks like a crash, so I recommend enabling Apport
> (if it's not enabled already), and then reproducing the bug. You can
> enable Apport by following the instructions at
> https://wiki.ubuntu.com/Apport#How%20to%20enable%20apport. After having
> carefully read the instructions on reporting bugs and having enabled
> Apport, try to make the crash happen again, and Apport will
> automatically launch, collect information about the crash, and open a
> browser window/tab where you can view potentially related bug reports
> and either indicate that one of them applies, or report it as a new bug.
>
> After you've reported your bug--or found it already reported--you can
> link the bug and this question to each other by using the "Link existing
> bug" link on this question page. While it's a good idea to do that, your
> bug report should be self-contained--the Ubuntu developers should not
> have to refer to this question page, in order to fully understand and
> appreciate your bug report.
>

--
Using Opera's revolutionary email client: http://www.opera.com/mail/

Sounds good. Please post again if you need help at any point while following those instructions, or (after reporting the bug) if you want help trying to work around the problem.

(The bug reporting process may reveal a similar bug with workarounds already established, which is why I'm saying that it's a good idea to report it before searching for a workaround. Otherwise, we might be "reinventing the lightbulb.")