From noreply+wiki at ubuntu.com Thu Jul 14 06:24:28 2022 From: noreply+wiki at ubuntu.com (Ubuntu Wiki) Date: Thu, 14 Jul 2022 06:24:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_vanvugt?= Message-ID: <165777986838.18895.6186836944025233676@juju-2c96a9-prod-ubuntu-web-frontends-6.None> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by vanvugt: https://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=398&rev2=399 = Release has reached End of Life (EOL) = If the specific release has reached End of Life per https://wiki.ubuntu.com/Releases and there is not enough information to work on the bug, then you can set to '''Incomplete''' and use the following response (just delete the lines that are not relevant): - || Thank you for reporting this bug to Ubuntu.<
><
>Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.<
>Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.<
>Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.<
>Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.<
>Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.<
>Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.<
>Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.<
>Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.<
>Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.<
>Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.<
>Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.<
>Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.<
>Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.<
>Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.<
>Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.<
>Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.<
>Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.<
>Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.<
>Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.<
>Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.<
>Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.<
>Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.<
>Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.<
>Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.<
>Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.<
>Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.<
>Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.<
><
>See this document for currently supported Ubuntu releases:<
>https://wiki.ubuntu.com/Releases <
><
>We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. || + || Thank you for reporting this bug to Ubuntu.<
><
>Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022.<
>Ubuntu 21.04 (hirsute) reached end-of-life on January 20, 2022.<
>Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.<
>Ubuntu 19.10 (eoan) reached end-of-life on July 17, 2020.<
>Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.<
>Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.<
>Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.<
>Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.<
>Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.<
>Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.<
>Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.<
>Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.<
>Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.<
>Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.<
>Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.<
>Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.<
>Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.<
>Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.<
>Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.<
>Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.<
>Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.<
>Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.<
>Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.<
>Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.<
>Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.<
>Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.<
>Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.<
>Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.<
><
>See this document for currently supported Ubuntu releases:<
>https://wiki.ubuntu.com/Releases <
><
>We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. || = Patch attachment not flagged as a patch = When reviewing bug attachments you might find an attachment that is a [[ Bugs/Patches | patch ]], but is not flagged. Let people know what a patch is! From noreply+wiki at ubuntu.com Thu Jul 14 06:27:39 2022 From: noreply+wiki at ubuntu.com (Ubuntu Wiki) Date: Thu, 14 Jul 2022 06:27:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_vanvugt?= Message-ID: <165778005936.30930.9935508666601257208@juju-2c96a9-prod-ubuntu-web-frontends-6.None> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by vanvugt: https://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=399&rev2=400 || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/. Thanks again and we appreciate your help.|| = Missing a crash report or having a .crash attachment = - || Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:<
><
>1. Look in `/var/crash` for crash files and if found run:<
>` ubuntu-bug YOURFILE.crash`<
>Then tell us the ID of the newly-created bug.<
><
>2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file `/var/lib/whoopsie/whoopsie-id` on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.<
><
>3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.<
><
>Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:<
><
>1. Look in `/var/crash` for crash files and if found run:<
>` ubuntu-bug YOURFILE.crash`<
>Then tell us the ID of the newly-created bug.<
><
>2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file `/var/lib/whoopsie/whoopsie-id` on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.<
><
>Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. || = A duplicate = When making a bug report a duplicate of another it is important to communicate to the reporter that any discussion regarding the bug should take place in the master bug. Keep in mind that NUMBER is a placeholder and should be the number of the master bug report.