Responses

Differences between revisions 10 and 12 (spanning 2 versions)
⇤ ← Revision 10 as of 2009-11-06 15:07:43 →
Size: 8742
Editor: d-65-175-172-80
Comment:
← Revision 12 as of 2009-11-06 15:19:22 → ⇥
Size: 8723
Editor: d-65-175-172-80
Comment:
Deletions are marked like this. Additions are marked like this.
Line 13: Line 13:
||<tablestyle="background-color: #eee"> Hello,<<BR>><<BR>> Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. This wish would best be reported and tracked at https://bugs.kde.org, so that it can be implemented by the KDE developers themselves. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu. <<BR>><<BR>>Thanks! || ||<tablestyle="background-color: #eee"> Hello,<<BR>><<BR>> Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. This wish would best be reported and tracked at https://bugs.kde.org, so that it can be implemented by the KDE developers themselves. Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu. <<BR>><<BR>>Thanks! ||
Line 21: Line 21:
||<tablestyle="background-color: #eee"> Hi there!<<BR>><<BR>> Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: <insert url>. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu. <<BR>><<BR>>Thanks! || ||<tablestyle="background-color: #eee"> Hi there!<<BR>><<BR>> Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging. <<BR>><<BR>>Thanks! ||
Line 25: Line 25:
||<tablestyle="background-color: #eee"> Hi there!<<BR>><<BR>> Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging. <<BR>><<BR>>Thanks! || ||<tablestyle="background-color: #eee"> Hi there!<<BR>><<BR>> Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: <insert url>. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu. <<BR>><<BR>>Thanks! ||

These are pre-made replies with a KDE focus for dealing with commonly-reported bugs or for when you need to deal with a large amount of a certain type of bug. While these were designed to sound natural and non-canned, it always is nice for a bug reporter to get a uniquely-composed response to their bug, especially if the pre-made response does not exactly fit the situation. It gives the reporter assurance that the developer did indeed read the bug and does know what he is talking about. A list of general (and in some cases more canned-sounding) replied can be found at Bugs/Responses

To switch things up, it is also advised to switch you greeting/ending line. In the future we may have something automatic-ish to mix-n-match salutations and endings. Where "KDE program" is said in the responses, it is advisable to replace this with the program name.

Contents

  1. Upstream Bugs for KDE Packages
    1. Upstream Bugs of "Wishlist" Importance
    2. Upstream Bugs of "Low" Importance
    3. Upstream Bugs of "Medium" Importance or Greater
    4. Upstream Bugs of "Medium" Importance or Greater Which Are Not SRU-able
  2. Incomplete Bugs Without Response
  3. Debugging Xorg
  4. Hard Drive Full Errors
  5. Corrupted Package Errors
  6. Distro has reached EOL

Upstream Bugs for KDE Packages

Upstream bugs for KDE packages are handled specially in Kubuntu. Here are responses to fit most situations

Upstream Bugs of "Wishlist" Importance

We send all wishlist items on to KDE. Close these bugs as invalid, and reply with something similar to:

Hello,

Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. This wish would best be reported and tracked at https://bugs.kde.org, so that it can be implemented by the KDE developers themselves. Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

If the wishlist already has an upstream report linked to it, use this one:

Hello,

Thanks for reporting this feature request! Unfortunately, at this time Kubuntu does not have the developer manpower needed to implement and maintain many features at the Kubuntu level. But don't worry! This issue is being tracked by the KDE developers at: <insert url>. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu.

Thanks!

Upstream Bugs of "Low" Importance

We send all low-importance upstream bugs on to KDE. Close these bugs as invalid, and reply with something similar to:

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https://bugs.kde.org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.

Thanks!

If already upstreamed:

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: <insert url>. Once implemented in KDE, it will be included in Kubuntu once the KDE version the feature is implemented in reaches Kubuntu.

Thanks!

Upstream Bugs of "Medium" Importance or Greater

We keep bugs deemed as "Medium" tracked in Launchpad (2 or 3 duplicates or so for crashes, a bit of common sense helps here. When in doubt ask somebody in #kubuntu-devel). We want to upstream these ones and mark them as "Triaged".

Hello there!

We appreciate you reporting this bug! This is an issue with the KDE application itself of considerable severity. As such, it has been reported to KDE. You can track and make further comments at:

Thanks!

Upstream Bugs of "Medium" Importance or Greater Which Are Not SRU-able

Unfortunately we cannot SRU all upstream crashes that have fixes. Some fixes are just too intrusive. Detailed SRU guidelines can be found here. Hopefully we should not have too many of these, so it should be fine to track them until we release a fix. (For user visibility more than anything). Set 'em to fix committed and respond with something like:

Hi,

While this bug has been fixed by KDE, the fix is too intrustive to provide as a Stable Release Update (SRU). This is unfortunate, as this bug is not exactly nominal. Fortunately the fix will be made in the development version of Kubuntu 10.04, and will be available at 10.04's release.

Thanks for your patience and understanding

Incomplete Bugs Without Response

When a user has not responded to a request for information after around a month, we close the bug as invalid.

We are closing this bug report because it lacks the information we need to investigate the problem, as requested in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the "Status" column, and change the status back to "New". Thanks again!

Debugging Xorg

Oftentimes we will receive bugs against the KDE packages that are really video driver bugs. In this case the best thing to do is pass this on to the appropriate driver package. Unfortunately it's usually not possible to tell from the report what driver the reporter is using. To determine this, set the bug to incomplete and respond thusly:

Hello,

This appears to be a problem with the video driver for your card. Could you please provide the output of lspci -vvnn and a copy of /var/log/Xorg.0.log as separate attachments? This will help us determine which driver package this bug should be assigned to, as well as help the graphics people more efficiently handle this bug.

Thanks in advance!

Hard Drive Full Errors

When a user runs out of hard drive space on his Kubuntu partition, dpkg will quite often report errors. These errors usually all have one key similarity: All give the errors: "$PACKAGE failed to install/upgrade: failed in buffer_write(fd) (10, ret=-1) installing $FILE" and in the dpkg log contains a line saying "No space left on device". You can convert these to support questions and give the following response:

Hi there!

It appears that you have run out of hard drive space on the partition you installed Kubuntu on. We cannot fix this from our end, but since this is probably a quite serious problem for you we are turning this report into a support ticket so that you can get the help you need.

Thanks for your patience and understanding

Corrupted Package Errors

Similar to the above error, sometimes packages fail to install because the package was corrupted while the user was downloading it. Convert these to questions with the following response:

Hi there!

It appears that somehow the package you were trying to install was corrupted during download.. We cannot fix this from our end, but since this is probably a quite serious problem for you we are turning this report into a support ticket so that you can get the help you need.

As a suggestion, you could try removing the package (sudo rm /var/cache/apt/$PATH-TO-PACKAGE and re-upgrading.

Thanks for your patience and understanding

You can usually find the path to the package that is failing in the dpkg log attached to the bug. Please be careful about throwing about sudo rm commands though...

Distro has reached EOL

If the distro has reached EOL per https://wiki.ubuntu.com/Releases (Kubuntu 8.04 support has ended, though) and you are pretty sure that this should be fixed in more recent releases. (Note DISTRO and DATE are variables):

Thanks for taking the time to report this bug. DISTRO reached EOL on DATE.
Please see this document for currently supported Kubuntu releases:
https://wiki.ubuntu.com/Releases

Unfortunately this means that there will be no more bugfixes for DISTRO. It is also recommended that you upgrade, if you have not already.

Please feel free to report any other bugs you may find, and thanks for your understanding.

Kubuntu/Bugs/Responses (last edited 2014-04-23 08:31:34 by 178-191-13-52)