Automated greasemonkey responses

Easy way

This only works with Firefox:

sudo add-apt-repository ppa:gm-dev-launchpad/ppa
sudo apt-get update
sudo apt-get firefox-lp-improvements

restart firefox

Go to a bug on launchpad and click the down arrow as if you are going to change the status of a bug

Below the comment field you will find a bunch of dynamic buttons which will auto fill the comment field.

At the end of the list, cilck the [+edit+] button. Now, either modify the responses that are there, or scroll to the bottom of the really long list of replies and click "[Add New Stock Reply]" . click [save] when you're done.

Manual steps:

http://azloco.com/node/64

-or-

install the lp_stockreplies.user.js greasemonkey script that you can find on ~gm-dev-launchpad page. There are other scripts as well.

Guidelines

  • Try to always set bug importance based upon your best guess. Do this even for incomplete bugs
  • Bugs submitted upstream belong in mythtv or mythtv-plugins. Once submitted upstream, mark the ubuntu mythtv/mythtv-plugins task as triaged and then link to that bug by clicking "Also affects project" and entering the URI of the upstream
  • Bugs in the Mythbuntu bucket should be marked triaged if the solution is relatively obvious (or if someone has provided a reasonable looking patch). Otherwise mark it as confirmed.
  • Bugs for Mythbuntu tasks should not be in mythtv/mythtv-plugins, and vice versa (unlikely a bug would be valid for both)
  • Try to provide complete answers, especially if closing a ticket or suggesting a work-around. Whenever possible, provide URI's to point to the solution rather than just talking about the solution
  • Try to always set bug importance based upon your best guess. Do this even for incomplete and invalid bugs
  • Be polite

Replies

Needs steps to reproduce

Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately it is missing some items necessary to understand or reproduce the problem. Could you provide the specific steps necessary to reproduce it including what actually occurs and what should occur. Logs are often very useful as well.

If you would prefer then we can always wait for someone with more experience debugging this product to come along and offer some assistance.

(probably mark as incomplete. Go ahead and mark importance based upon what it *might* be if it were a complete report)

Need version information to reproduce

Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately it is missing some items necessary to understand or reproduce the problem. Could you please provide the full version of MythTV and what version of Mythbuntu you are using? Please also let us know if this is a Mythbuntu install, or if you installed Ubuntu and added MythTV.

If you would prefer then we can always wait for someone with more experience debugging this product to come along and offer some assistance.

Need logs and/or someone to reproduce

Thank you for helping to improve Mythbuntu by reporting this issue.

Unfortunately the developers do not have this equipment to reproduce the issue, so we need to ask one or more of you, preferably someone running builds from the MythTV updates repo (http://www.mythbuntu.org/repos), to please attach your logs to this ticket. Logs from more than one person are welcome.

Please reproduce the issue, then use mythbuntu-log-grabber to grab the logs and attach them to this ticket.

It would be helpful if it was not the whole log, but rather starting from a few entries before changing the channel (full verbose logs from startup can be painful to sort through).

For these logs to be truly useful, they need to have some extra verbose options enabled (-v record,channel,siparser) on the backend command line.

<for mythtv-setup problems/logs, you need the following>

sudo /etc/init.d/mythtv-backend stop
and then

sudo mythtv-setup.real --verbose channelscan,siparser,channel,record,extra > mythtv-setup.log
You can replace stop with restart to relaunch the backend.

Report is complete

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers understand the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

(probably mark as confirmed Go ahead and mark importance based upon best guess)

Report complete, and user provided solution

Thank you for helping to improve Mythbuntu by opening this ticket. I am marking this ticket as confirmed because it appears to have enough information to help the developers quickly resolve the problem. It is possible I am wrong and another more experienced triager or developer may adjust the status of the ticket to "incomplete" and request additional information.

(probably mark as triaged. Go ahead and mark importance based upon best guess)

Bad backtrace

Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately, through no fault of your own, attached stacktrace is not useful to the developers. Could you please update to the latest version of the debug packages by following the "basic backtrace" directions outlined here:

http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages

The above process should result in a new ticket being opened if you can reproduce the issue, so I'm going to close this ticket.

(probably mark as invalid. Go ahead and mark importance based upon best guess - probably "medium" or "high")

Patches accepted

Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately the Mythbuntu team does not foresee a time when they will be able to tackle this issue, so I am closing this ticket. With that being said, if someone else wants to write a patch for this, we will be happy to help push it upstream. Please do not let that action deter you from opening tickets on other issues that you find!

(probably mark as won't fix. Go ahead and mark importance based upon best guess)

Alternative wording:

Thank you for helping to improve Mythbuntu by opening this ticket. The work required to resolve this ticket is too much considering the complexity of the issue / rarity of the problem / man power of the Mythbuntu team. With that being said,
if someone else could write a patch, we will do our best to see that upstream adopts a fix.

(probably mark as won't fix. Go ahead and mark importance based upon best guess)

upstream lirc

Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately the Mythbuntu team does not have the resources to handle the constant stream of new devices such as this. Since the lirc team does not have a bug tracker, the most efficient way to get the device supported would be for you to contact the lirc team on their mailng list and describe everything you know about the remote and any data that you have collected. If they do add support, please feel free to re-open this ticket with the information about what they called the device so that it can be considered for import into Mythbuntu as a patch.

(probably mark as won't fix. Go ahead and mark importance based upon best guess)

laundry list

(remove and renumber the items that you don't need in each report)

Thank you for helping to improve Mythbuntu by taking the time to open this ticket.

I am closing this ticket for the following reasons:

1. It is missing symbol information needed to help debug the issue
2. QT related functions were totally re-written with QT4 for 0.23, so it is likely this is fixed
3. There are no other reports of this issue
4. This issue would need to be reproduced on 0.23 with a new stack trace since the mythtv developers are no longer working on 0.22 issues

If you can reproduce this on 0.23, please attach traces to a new ticket and we can try to forward this bug upstream to get the right eyes focused on it. We have builds of mythtv 0.23 available on a PPA to test. Please follow the directions at http://mythbuntu.org/repos to enable them.

WARNING: If you think that you may want or need to revert back to your current version after testing, you will need to back up your database before upgrading. Once you upgrade, the only method to down-grade is to perform a database restore from your backup.

Thanks again!

Old version - likely fixed

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that the MythTV developers have turned their efforts to newer versions and and are no longer fixing bugs on this version of MythTV.

The Mythbuntu team has builds of newer versions of MythTV available on a PPA if you are interested in upgrading. Please follow the directions at http://mythbuntu.org/repos to enable them. Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

WARNING: If you need to have the ability to revert back to your current version, you will need to back up your database before upgrading so that you can later restore it, since newer databases can not be downgraded.

Thanks!

Try latest version

Thank you for helping to improve Mythbuntu by opening this ticket. Is there any way that you can test a newer revision by choosing 0.23 after activating the autobuilds (per http://www.mythbuntu.org/repos)? We need to verify the problem still exists there before moving further.

Please be sure to back up your database before doing this though, because you can't downgrade back to your current version unless you drop the database and restore a backup.

***Possibly include the following comment: Upstream suspects that this should be fixed in a newer version. Can you then provide feedback at that bug upstream?

(probably mark as incomplete. Go ahead and mark importance based upon what it *might* be if it were a complete report)

Fixed

This has been fixed upstream. It will be seen in the next 0.23 autobuilds trunk build. This bug will be automatically closed when a
new build containing the fix is uploaded to the current development release (Lucid Lynx).

(probably mark as fix committed. Go ahead and mark importance based upon what it *might* be if it were a complete report)

Other stock ubuntu responses

See https://wiki.ubuntu.com/Bugs/Responses