From noreply at ubuntu.com Fri Jul 10 21:03:32 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 10 Jul 2015 21:03:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22walterorlin/debugging-debian-ins?= =?utf-8?q?taller=22_by_walterorlin?= Message-ID: <20150710210332.32137.24617@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "walterorlin/debugging-debian-installer" page has been changed by walterorlin: http://wiki.ubuntu.com/walterorlin/debugging-debian-installer?action=diff&rev1=2&rev2=3 Comment: Add how to get ot the save debug logs location. The first few times you have to report a problem with a debian installer image not installing can be frustrating as switching to a tty and using ubuntu-bug is not possible in the limited busybox session but this allow for the alternate install for lubuntu on the oldest machines to work. Getting the debug information when this breaks can be frustrating. However, to triage these bugs without logs is really hard to get the developers the info needed. = How to file = + IN debian installer pressing the - With debian-installer ubuntu-bug from a shell will not work. The debian-installer busy box enviorment is quite limited in what commands you can use. Even commands like less are not available. There are a few options available here that work well. 1. Download the debug logs from another computer on the lan. 2. mount a filesystem and attach them after booting into a wor1. >From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run wget -r on the ip address from the machine failing to install. - king system. + With debian-installer ubuntu-bug from a shell will not work. The debian-installer busy box enviorment is quite limited in what commands you can use. Even commands like less are not available. There are a few options available here that work well. 1. Download the debug logs from another computer on the lan. + 2. mount a filesystem save the debug files onto this filesystem boot a working system with that system and attach the saved logs. + + How to get to the menu to enable saving debug logs. After failing the alternate installer will usually flash a red screen saying it had failed. If you still get that you may need to get back to a main menu by pressing the go back button. + + + 1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run wget -r on the ip address from the machine failing to install. 1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run `wget -r` on the ip address from the machine failing to install which will save all the debug files. Otherwise you will need to dowload and save these files manually. From noreply at ubuntu.com Mon Jul 13 02:54:45 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 13 Jul 2015 02:54:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22walterorlin/debugging-debian-ins?= =?utf-8?q?taller=22_by_walterorlin?= Message-ID: <20150713025445.12532.10682@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "walterorlin/debugging-debian-installer" page has been changed by walterorlin: http://wiki.ubuntu.com/walterorlin/debugging-debian-installer?action=diff&rev1=3&rev2=4 How to get to the menu to enable saving debug logs. After failing the alternate installer will usually flash a red screen saying it had failed. If you still get that you may need to get back to a main menu by pressing the go back button. - 1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run wget -r on the ip address from the machine failing to install. + . 1. From another machine on the local network, If debian installer comes up with a red screen saying failed ot install go through and try again and it is still broken at red screen if you use the keyboard to navigate to the go back back button it will bring you to a menu of all of the various steps of the installation. If you go all the way to the bottom of this list there is an option to save debug logs. Press enter with the cursor on this option. Then for a computer on the local network. Press to save debug logs on web. IT will give you an ip address from an embeded webserver. now from another computer on the same network or even the host if it is a virtual machine download all of the debug files. IF it is a linux system and easy way to get all the files and save them to another computer is to run `wget -r` on the ip address from the machine failing to install which will save all the debug files. Otherwise you will need to dowload and save these files manually. From noreply at ubuntu.com Sun Jul 19 16:01:29 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 19 Jul 2015 16:01:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_statuses=22_by_penalvch?= Message-ID: <20150719160129.30411.71061@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug statuses" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Bug%20statuses?action=diff&rev1=75&rev2=76 Comment: Due to LP#1178982 c#38 and others, clarified Status Invalid. * This status is considered an experiment, and will be closely monitored. * '''Invalid''': + * This status means the report is closed, and no further triaging or development will continue towards it. + * This status should be used when: - * This status should be used when the report does not contain adequate information to determine whether or not it is a bug even if it is resolved for the reporter. + * The report does not contain adequate information to determine whether or not it is a bug, even if it is resolved for the reporter. - * This should also be used if the reported problem is not a bug at all. For example, user's lack of knowledge on how something works, hardware failure, or fixed after updating a buggy, and outdated BIOS. + * The reported problem is not a bug at all. For example, the reporter's lack of knowledge on how something works, hardware failure, or fixed after updating a buggy, and outdated BIOS. * It should be used conservatively as reports marked as Invalid no longer show up in default searches. * Be sure to triple-check a report before you invalidate it. From noreply at ubuntu.com Sat Jul 25 15:05:15 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 25 Jul 2015 15:05:15 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_es20490446?= =?utf-8?q?e?= Message-ID: <20150725150515.29486.13150@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Importance" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=7&rev2=8 - <> + /!\ Please, go to [[Bugs/Bug importances]]. - Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs. - - In order to set the Importance field of a bug in [[Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. - - The importance of a bug report can be modified by clicking on the current Status or Importance, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new importance in the drop down box. - - Here are the meanings of the different importance values: - - * '''Undecided''': The default for new bugs. Also means that there is insufficient information to determine importance. - - * '''Wishlist''': Missing functionality. - * These aren't always bugs, but can be ideas for new features which do not yet exist. - * These can also be requests to have software packaged for Ubuntu. - * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications. - * These can be bugs that affect an experimental extension or non-essential feature of a given package/project. - * Bugs that would only be fixed on a best-effort or outside-contribution basis might also be considered ''wishlist''. - - * '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are: - * Bugs that have easy [[http://www.merriam-webster.com/dictionary/work-around|work-arounds]] - * Bugs that affect unusual end-user configurations or uncommon hardware - * Bugs that affect a non-essential aspect and limited scope of the application - * Bugs that have a moderate impact on a non-core application - * Cosmetic/usability issues that does not limit the functionality of a non-core application - * Non-ideal default configurations - - * '''Medium''': Most bugs are of medium importance, examples are: - * A bug that has a moderate impact on a core application. - * A bug that has a severe impact on a non-core application. - * A bug which impacts accessibility of a non-core application. - * A usability issue that does not limit the functionality of a core application. - * A problem with a non-essential hardware component (removable network card, camera, webcam, music player, sound card, power management feature, printer, etc.) - * '''High''': A bug which fulfills one of the following criteria: - * Has a severe impact on a small portion of Ubuntu users (estimated) - * Makes a default Ubuntu installation generally unusable for some users - * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer - * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) - * Has a moderate impact on a large portion of Ubuntu users (estimated) - * Prevents the application or any dependencies from functioning correctly at all - * Renders essential features or functionality of the application or dependencies broken or ineffective - * Impacts accessibility of a core application - * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users - * Causes data corruption - * Crashes the entire operating system - * Renders the system temporarily or permanently unusable - * Severely affects applications beyond the package responsible for the root cause - - ||{{attachment:IconHelp2.png}}If you're not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member, you'll have to ask someone who is to do it for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to importance 'Wishlist / Low / Medium / High / Critical'. Someone will notice your comment and set it for you, although not necessarily immediately.|| - ---- - || '''Footnote:''' || - ||[[http://www.merriam-webster.com/dictionary/work-around|work-around]]:||a plan or method to circumvent a problem ''without'' eliminating it || - ||"core":||A core package can be identified as being part of a task in the apt-cache headers. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| - ||"non-core":||A non-core package can be identified as a package that is not part of a task, and is not in 'main'. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| - ---- - CategoryBugSquad - From noreply at ubuntu.com Sat Jul 25 15:19:49 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 25 Jul 2015 15:19:49 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_es20490446?= =?utf-8?q?e?= Message-ID: <20150725151949.29389.8268@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Importance" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=8&rev2=9 - /!\ Please, go to [[Bugs/Bug importances]]. + <> + Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs. + + In order to set the Importance field of a bug in [[Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. + + The importance of a bug report can be modified by clicking on the current Status or Importance, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new importance in the drop down box. + + Here are the meanings of the different importance values: + + * '''Undecided''': The default for new bugs. Also means that there is insufficient information to determine importance. + + * '''Wishlist''': Missing functionality. + * These aren't always bugs, but can be ideas for new features which do not yet exist. + * These can also be requests to have software packaged for Ubuntu. + * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications. + * These can be bugs that affect an experimental extension or non-essential feature of a given package/project. + * Bugs that would only be fixed on a best-effort or outside-contribution basis might also be considered ''wishlist''. + + * '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are: + * Bugs that have easy [[http://www.merriam-webster.com/dictionary/work-around|work-arounds]] + * Bugs that affect unusual end-user configurations or uncommon hardware + * Bugs that affect a non-essential aspect and limited scope of the application + * Bugs that have a moderate impact on a non-core application + * Cosmetic/usability issues that does not limit the functionality of a non-core application + * Non-ideal default configurations + + * '''Medium''': Most bugs are of medium importance, examples are: + * A bug that has a moderate impact on a core application. + * A bug that has a severe impact on a non-core application. + * A bug which impacts accessibility of a non-core application. + * A usability issue that does not limit the functionality of a core application. + * A problem with a non-essential hardware component (removable network card, camera, webcam, music player, sound card, power management feature, printer, etc.) + * '''High''': A bug which fulfills one of the following criteria: + * Has a severe impact on a small portion of Ubuntu users (estimated) + * Makes a default Ubuntu installation generally unusable for some users + * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer + * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) + * Has a moderate impact on a large portion of Ubuntu users (estimated) + * Prevents the application or any dependencies from functioning correctly at all + * Renders essential features or functionality of the application or dependencies broken or ineffective + * Impacts accessibility of a core application + * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users + * Causes data corruption + * Crashes the entire operating system + * Renders the system temporarily or permanently unusable + * Severely affects applications beyond the package responsible for the root cause + + ||{{attachment:IconHelp2.png}}If you're not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member, you'll have to ask someone who is to do it for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to importance 'Wishlist / Low / Medium / High / Critical'. Someone will notice your comment and set it for you, although not necessarily immediately.|| + ---- + || '''Footnote:''' || + ||[[http://www.merriam-webster.com/dictionary/work-around|work-around]]:||a plan or method to circumvent a problem ''without'' eliminating it || + ||"core":||A core package can be identified as being part of a task in the apt-cache headers. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| + ||"non-core":||A non-core package can be identified as a package that is not part of a task, and is not in 'main'. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| + ---- + CategoryBugSquad + From noreply at ubuntu.com Sat Jul 25 15:20:45 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 25 Jul 2015 15:20:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_importances=22_by_es204?= =?utf-8?q?90446e?= Message-ID: <20150725152045.29533.60369@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug importances" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Bug%20importances?action=diff&rev1=43&rev2=44 + /!\ Please, go to [[Bugs/Importance]]. - ## page was renamed from Bugs/Bug importance - <> - Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs. - - In order to set the Importance field of a bug in [[Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. - - The importance of a bug report can be modified by clicking on the current Status or Importance, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new importance in the drop down box. - - Here are the meanings of the different importance values: - - * '''Undecided''': The default for new bugs. Also means that there is insufficient information to determine importance. - - * '''Wishlist''': Missing functionality. - * These aren't always bugs, but can be ideas for new features which do not yet exist. - * These can also be requests to have software packaged for Ubuntu. - * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications. - * These can be bugs that affect an experimental extension or non-essential feature of a given package/project. - * Bugs that would only be fixed on a best-effort or outside-contribution basis might also be considered ''wishlist''. - - * '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are: - * Bugs that have easy [[http://www.merriam-webster.com/dictionary/work-around|work-arounds]] - * Bugs that affect unusual end-user configurations or uncommon hardware - * Bugs that affect a non-essential aspect and limited scope of the application - * Bugs that have a moderate impact on a non-core application - * Cosmetic/usability issues that does not limit the functionality of a non-core application - * Non-ideal default configurations - - * '''Medium''': Most bugs are of medium importance, examples are: - * A bug that has a moderate impact on a core application. - * A bug that has a severe impact on a non-core application. - * A bug which impacts accessibility of a non-core application. - * A usability issue that does not limit the functionality of a core application. - * A problem with a non-essential hardware component (removable network card, camera, webcam, music player, sound card, power management feature, printer, etc.) - * '''High''': A bug which fulfills one of the following criteria: - * Has a severe impact on a small portion of Ubuntu users (estimated) - * Makes a default Ubuntu installation generally unusable for some users - * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer - * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) - * Has a moderate impact on a large portion of Ubuntu users (estimated) - * Prevents the application or any dependencies from functioning correctly at all - * Renders essential features or functionality of the application or dependencies broken or ineffective - * Impacts accessibility of a core application - * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users - * Causes data corruption - * Crashes the entire operating system - * Renders the system temporarily or permanently unusable - * Severely affects applications beyond the package responsible for the root cause - - ||{{attachment:IconHelp2.png}}If you're not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member, you'll have to ask someone who is to do it for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to importance 'Wishlist / Low / Medium / High / Critical'. Someone will notice your comment and set it for you, although not necessarily immediately.|| - ---- - || '''Footnote:''' || - ||[[http://www.merriam-webster.com/dictionary/work-around|work-around]]:||a plan or method to circumvent a problem ''without'' eliminating it || - ||"core":||A core package can be identified as being part of a task in the apt-cache headers. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| - ||"non-core":||A non-core package can be identified as a package that is not part of a task, and is not in 'main'. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| - ---- - CategoryBugSquad - From noreply at ubuntu.com Sat Jul 25 14:58:01 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 25 Jul 2015 14:58:01 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_es20490446?= =?utf-8?q?e?= Message-ID: <20150725145801.26151.7240@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Importance" page has been changed by es20490446e: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=6&rev2=7 - #REFRESH 0 https://wiki.ubuntu.com/Bugs/Bug%20importances + <> + Ubuntu uses the following guidelines for assigning importance. The importance of the bug signifies the priority that it should be given by people fixing bugs. + + In order to set the Importance field of a bug in [[Launchpad]], you need to be a member of [[UbuntuBugControl]] either through direct membership or because of your membership in another team. The importance of the bug should be set as soon as possible. + + The importance of a bug report can be modified by clicking on the current Status or Importance, in the yellow line and under the "Affects" column header, which will reveal a sub menu. You can then choose a new importance in the drop down box. + + Here are the meanings of the different importance values: + + * '''Undecided''': The default for new bugs. Also means that there is insufficient information to determine importance. + + * '''Wishlist''': Missing functionality. + * These aren't always bugs, but can be ideas for new features which do not yet exist. + * These can also be requests to have software packaged for Ubuntu. + * If it is non-trivial to implement, it should rather be written as a feature specification, see FeatureSpecifications. + * These can be bugs that affect an experimental extension or non-essential feature of a given package/project. + * Bugs that would only be fixed on a best-effort or outside-contribution basis might also be considered ''wishlist''. + + * '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are: + * Bugs that have easy [[http://www.merriam-webster.com/dictionary/work-around|work-arounds]] + * Bugs that affect unusual end-user configurations or uncommon hardware + * Bugs that affect a non-essential aspect and limited scope of the application + * Bugs that have a moderate impact on a non-core application + * Cosmetic/usability issues that does not limit the functionality of a non-core application + * Non-ideal default configurations + + * '''Medium''': Most bugs are of medium importance, examples are: + * A bug that has a moderate impact on a core application. + * A bug that has a severe impact on a non-core application. + * A bug which impacts accessibility of a non-core application. + * A usability issue that does not limit the functionality of a core application. + * A problem with a non-essential hardware component (removable network card, camera, webcam, music player, sound card, power management feature, printer, etc.) + * '''High''': A bug which fulfills one of the following criteria: + * Has a severe impact on a small portion of Ubuntu users (estimated) + * Makes a default Ubuntu installation generally unusable for some users + * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer + * A problem with an essential hardware component (disk controller, built-in networking, video card, keyboard, mouse) + * Has a moderate impact on a large portion of Ubuntu users (estimated) + * Prevents the application or any dependencies from functioning correctly at all + * Renders essential features or functionality of the application or dependencies broken or ineffective + * Impacts accessibility of a core application + * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users + * Causes data corruption + * Crashes the entire operating system + * Renders the system temporarily or permanently unusable + * Severely affects applications beyond the package responsible for the root cause + + ||{{attachment:IconHelp2.png}}If you're not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member, you'll have to ask someone who is to do it for you. Paste the bug number in {{{#ubuntu-bugs}}} channel at [[https://wiki.ubuntu.com/FreeNode|FreeNode]] and say you think the bug should be set to importance 'Wishlist / Low / Medium / High / Critical'. Someone will notice your comment and set it for you, although not necessarily immediately.|| + ---- + || '''Footnote:''' || + ||[[http://www.merriam-webster.com/dictionary/work-around|work-around]]:||a plan or method to circumvent a problem ''without'' eliminating it || + ||"core":||A core package can be identified as being part of a task in the apt-cache headers. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| + ||"non-core":||A non-core package can be identified as a package that is not part of a task, and is not in 'main'. You can see the apt-cache headers by running `apt-cache show [package]` in a terminal, and looking at the "Task: " field in the output.|| + ---- + CategoryBugSquad +