Responses
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
Upstream Bugs for KDE Packages
Upstream bugs for KDE packages are handled specially in Kubuntu. Here are responses to fit most situations
Upstream Wishes Importance
We send all wishlist items on to KDE. Close these bugs as Invalid, and reply with something similar to:
Hello, |
If the wishlist already has an upstream report linked to it, use this one:
Hello, |
Upstream Bugs Importance
We send all upstream bugs on to KDE. Close these bugs as Invalid, and reply with something similar to:
Hi there! |
If already upstreamed:
Hi there! |
Dead Upstream
Packages with a known dead upstream can be kept in the archive, if this is the case a bug with Triaged/High status will be kept open for reference of this decision. This bug needs to be mentenioned in place of #XXXXXX in the template below. Close bugs for software with dead upstreams as Won't Fix.
Thanks for taking the time to report this bug. Unfortunately this software is no longer maintained by its original developers. The package is kept available because it is considered generally good enough quality in accordance with our Dead Upstream Policy. |
Removed Package
Software that is removed from the archive ought to have their bugs closed with a reference to possible replacement software on apps.ubuntu.com or packages.ubuntu.com. Close these bugs as Invalid.
Thanks for taking the time to report this bug. Unfortunately this package was removed from the Kubuntu software repositories in the meantime. We are closing this bug report because it will not see any resolution for future releases of Kubuntu. |
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, |
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! |
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! |
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. |
13.04
Thanks for taking the time to report this bug. 13.04 reached EOL on January 27, 2014. |
11.10
Thanks for taking the time to report this bug. 11.10 reached EOL on May 9, 2013. |
11.04
Thanks for taking the time to report this bug. 11.04 reached end of life on October 28, 2012. |
10.10
Thanks for taking the time to report this bug. 10.10 reached end of life on April 10, 2012. |
10.04
Thanks for taking the time to report this bug. 10.04 reached end of life on May 9, 2013. |
9.10
Thanks for taking the time to report this bug. 9.10 reached end of life on April 30, 2011. |