From webmaster at ubuntu.com Sun Dec 1 20:39:32 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sun, 01 Dec 2013 20:39:32 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20131201203932.14684.89295@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=250&rev2=251 Comment: Due to LP#1242085 clarified buggy and outdated BIOS would need update despite problems not manifesting themselves in Windows. Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: <
><
> - Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). As well, because BIOS vendors tend test to Windows and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. + Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem. <
><
> From webmaster at ubuntu.com Tue Dec 3 00:02:13 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Tue, 03 Dec 2013 00:02:13 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20131203000213.14368.7879@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=251&rev2=252 Comment: Added BIOS update collatoral damage statement. Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: <
><
> - Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. + Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collatoral damage avoidance. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem. <
><
> From noreply at ubuntu.com Tue Dec 3 12:23:47 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 03 Dec 2013 12:23:47 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToFix=22_by_dholbach?= Message-ID: <20131203122347.2888.19940@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/HowToFix" page has been changed by dholbach: http://wiki.ubuntu.com/Bugs/HowToFix?action=diff&rev1=11&rev2=12 - #REFRESH 0 http://developer.ubuntu.com/packaging/html/fixing-a-bug.html + #REFRESH 1 http://packaging.ubuntu.com/html/fixing-a-bug.html From noreply at ubuntu.com Thu Dec 5 16:29:22 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 05 Dec 2013 16:29:22 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_es20490446?= =?utf-8?q?e?= Message-ID: <20131205162922.20075.97540@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=33&rev2=34 Comment: Simplified <> - 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. + === Undecided === + * No one has '''set priority''' yet. + * We '''don't know''' what importance should it have yet. - 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. + === Wishlist === + * Is an idea for a '''new feature'''. + * Is a requests '''to package''' software for Ubuntu. + * Affect an '''experimental extension''' or non-essential feature. + * Would only be fixed on a '''best-effort''' or outside-contribution basis. + * Is '''non-trivial''' to implement (it should rather be written as a [[FeatureSpecifications|feature specification]]). - 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. + === Low === + * Has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]]. + * Affects '''unusual''' end-user set up. + * Affects a '''non-essential aspect''' of the application. + * Has a '''moderate impact''' on a non-core application. + * Is a '''cosmetic or usability''' issue that doesn't limit the functionality of a non-core application. + * Is a non-ideal default '''configuration'''. - * '''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''. + === Medium === + * '''Most bugs''' fit this importance. - * '''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 + * Has a '''moderate impact''' on a core application. + * Has a '''severe impact''' on a non-core application. + * Impacts '''accessibility''' of a non-core application. - * Cosmetic/usability issues that does not limit the functionality of a non-core application + * Is a '''usability''' issue that doesn't limit the functionality of a core application. - * Non-ideal default configurations + * Affects a '''non-essential hardware''' component (removable network card, camera, web-cam, music player, sound card, power management feature, printer...). - * '''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.|| - ---- + === High === + * Is estimated to have '''severe impact''' on an small portion of Ubuntu users. + * Makes a default Ubuntu installation '''unusable''' for some users. + * Affects an '''essential hardware''' component (disk controller, built-in networking, video card, keyboard, mouse). + * Is estimated to have a moderate impact on a '''large portion''' of Ubuntu users. + * Prevents the application (or a dependent one) from '''functioning correctly''' at all. + * Renders essential features or functionality of the application (or a dependent one) '''broken'''. + * Impacts '''accessibility''' of a core application. + + + === Critical === + * 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 one that causes the flaw. + + == == + This importance '''can be set''' by: + * '''Asking''' someone in {{{#ubuntu-bugs}}} channel at [[https://webchat.freenode.net|FreeNode]] to set it for you to a specific priority. + * '''Becoming''' a member of [[UbuntuBugControl|Ubuntu Bug Control]]. + + + == == || '''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 Thu Dec 5 16:58:15 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 05 Dec 2013 16:58:15 -0000 Subject: =?utf-8?q?New_attachment_added_to_page_Bugs/Bug_importance_on_Ubuntu_Wiki?= Message-ID: <20131205165815.22842.29834@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page "Bugs/Bug importance" for change notification. An attachment has been added to that page by es20490446e. Following detailed information is available: Attachment name: Bug importance.png Attachment size: 56175 Attachment link: http://wiki.ubuntu.com/Bugs/Bug%20importance?action=AttachFile&do=get&target=Bug+importance.png Page link: http://wiki.ubuntu.com/Bugs/Bug%20importance From noreply at ubuntu.com Fri Dec 6 21:29:28 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 06 Dec 2013 21:29:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_jibel?= Message-ID: <20131206212928.26170.80356@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 jibel: http://wiki.ubuntu.com/Bugs/Importance New page: <> 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 sergio.martinezp at infotec.com.mx Wed Dec 11 01:46:15 2013 From: sergio.martinezp at infotec.com.mx (Sergio Edgar Martinez Pacheco) Date: Tue, 10 Dec 2013 19:46:15 -0600 Subject: Kind of silly question.... Message-ID: <0E2EE6D77A0AC8438ABD63FB9A84704C100C30@mbex.dcinfotec.local> Hi, I've got a question, I'm not sure if this is a bug, but I got a very recurrent Warning in the /var/log/syslog Dec 10 08:09:15 serchlap kernel: [45137.987736] ------------[ cut here ]------------ Dec 10 08:09:15 serchlap kernel: [45137.987789] WARNING: at /build/buildd/linux-3.5.0/net/mac80211/sta_info.c:306 sta_info_insert_rcu+0xb1/0xc0 [mac80211]() Dec 10 08:09:15 serchlap kernel: [45137.987794] Hardware name: HP EliteBook 8560w Dec 10 08:09:15 serchlap kernel: [45137.987797] Modules linked in: ipheth ipt_MASQUERADE xt_state ipt_REJECT xt_tcpudp iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables vesafb joydev bnep rfcomm ext2 snd_hda_codec_hdmi arc4 coretemp tpm_infineon kvm_intel snd_hda_codec_idt kvm ghash_clmulni_intel cryptd ppdev hp_wmi sparse_keymap microcode uvcvideo videobuf2_core videodev videobuf2_vmalloc snd_seq_midi videobuf2_memops iwlwifi btusb snd_rawmidi mac80211 bluetooth snd_hda_intel snd_seq_midi_event snd_hda_codec snd_hwdep cfg80211 snd_pcm snd_seq lpc_ich psmouse serio_raw parport_pc snd_timer snd_seq_device tpm_tis video hp_accel lis3lv02d input_polldev wmi fglrx(PO) snd amd_iommu_v2 soundcore mac_hid snd_page_alloc mei lp parport ahci libahci firewire_ohci s Dec 10 08:09:15 serchlap kernel: dhci_pci sdhci firewire_core crc_itu_t e1000e Dec 10 08:09:15 serchlap kernel: [45137.987936] Pid: 2440, comm: kworker/u:0 Tainted: P W O 3.5.0-44-generic #67-Ubuntu Dec 10 08:09:15 serchlap kernel: [45137.987940] Call Trace: Dec 10 08:09:15 serchlap kernel: [45137.987957] [] warn_slowpath_common+0x7f/0xc0 Dec 10 08:09:15 serchlap kernel: [45137.987966] [] warn_slowpath_null+0x1a/0x20 Dec 10 08:09:15 serchlap kernel: [45137.987992] [] sta_info_insert_rcu+0xb1/0xc0 [mac80211] Dec 10 08:09:15 serchlap kernel: [45137.988021] [] ieee80211_ibss_finish_sta+0xe3/0x250 [mac80211] Dec 10 08:09:15 serchlap kernel: [45137.988048] [] ieee80211_ibss_work+0xd6/0x480 [mac80211] Dec 10 08:09:15 serchlap kernel: [45137.988076] [] ieee80211_iface_work+0x1a6/0x360 [mac80211] Dec 10 08:09:15 serchlap kernel: [45137.988084] [] process_one_work+0x149/0x400 Dec 10 08:09:15 serchlap kernel: [45137.988091] [] worker_thread+0x12e/0x2f0 Dec 10 08:09:15 serchlap kernel: [45137.988099] [] ? manage_workers.isra.27+0x200/0x200 Dec 10 08:09:15 serchlap kernel: [45137.988107] [] kthread+0x93/0xa0 Dec 10 08:09:15 serchlap kernel: [45137.988117] [] kernel_thread_helper+0x4/0x10 Dec 10 08:09:15 serchlap kernel: [45137.988126] [] ? kthread_freezable_should_stop+0x70/0x70 Dec 10 08:09:15 serchlap kernel: [45137.988134] [] ? gs_change+0x13/0x13 Dec 10 08:09:15 serchlap kernel: [45137.988138] ---[ end trace 20bbd786cbfc92d8 ]--- should I file a bug? Best regards... Sergio Martinez -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtl131 at gmail.com Wed Dec 11 12:45:07 2013 From: dtl131 at gmail.com (Daniel Letzeisen) Date: Wed, 11 Dec 2013 07:45:07 -0500 Subject: Kind of silly question.... In-Reply-To: <0E2EE6D77A0AC8438ABD63FB9A84704C100C30@mbex.dcinfotec.local> References: <0E2EE6D77A0AC8438ABD63FB9A84704C100C30@mbex.dcinfotec.local> Message-ID: <52A85E53.4080802@gmail.com> On 12/10/2013 08:46 PM, Sergio Edgar Martinez Pacheco wrote: > Kind of silly question.... > > Hi, > > I've got a question, I'm not sure if this is a bug, but I got a very > recurrent Warning in the /var/log/syslog > Sergio, see if the warning is still occurring with a LiveUSB of Ubuntu 13.10 or Ubuntu 14.04 development release. If it still occurs, then file a bug report. From nicholas.skaggs at canonical.com Fri Dec 13 21:43:03 2013 From: nicholas.skaggs at canonical.com (Nicholas Skaggs) Date: Fri, 13 Dec 2013 16:43:03 -0500 Subject: [Sandbox][Work Item] vUDS: Quality community-Run Testing Events In-Reply-To: <528E65E2.3010805@canonical.com> References: <20131121153825.GA2089@sup.lan> <528E65E2.3010805@canonical.com> Message-ID: <52AB7F67.3030509@canonical.com> Ali, so this has simmered for a bit and I think it's ready! Can you please implement this into the wiki directly? I would like it to be a part of the header, but I can help integrate once the subpages are built. We'll follow-up with a calendar once it's setup. That will just be a manual process to sync at first which is fine. Once the page is setup please share. I'd suggest a few of us subscribe to the page so we know when things change. Thanks again for setting this up! Nicholas On 11/21/2013 02:58 PM, Nicholas Skaggs wrote: > Looks nice Ali, I have some feedback I'll type up later. But I wanted > to add that the idea for a calendar has resurfaced, and I think I will > pursue it. Namely, you can get an ical sync of what's going on; > testing events, etc, etc. It should include these, but nothing should > otherwise be affected. > > Cheers, > > Nicholas > > On 11/21/2013 10:49 AM, Ali Linx (amjjawad) wrote: >> Hi, >> >> On Thu, Nov 21, 2013 at 7:38 PM, Javier Lopez > > wrote: >> >> That's a nice wiki!, >> >> >> Thank you :) >> >> just to make it clear, the table is for describing only >> testing event right?, >> >> >> Yes :) >> See: >> http://summit.ubuntu.com/uds-1311/meeting/22064/community-1311-quality-calls-for-testing/ >> >> Work Items (which by mistake, I wrote work times - sorry) : >> http://pad.ubuntu.com/uds-1311-community-1311-quality-calls-for-testing >> >> what about classroom testing events? >> >> https://wiki.ubuntu.com/Testing/Activities/Classroom >> >> Should we include both events in the same wiki? >> >> >> I don't think so because these are two different topics. Those who >> will carry on with Testing Events already know what they need to do >> and they should have learned something from the Classroom Testing >> events :) >> >> The name could be confusing but the idea should be different AFAIK :) >> >> Best Regards >> >> >> Thank you! >> >> >> Remember: "All of us are smarter than any one of us." >> Best Regards, >> amjjawad >> Areas of Involvement >> >> My Projects >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From amjjawad at gmail.com Fri Dec 13 22:16:09 2013 From: amjjawad at gmail.com (Ali Linx (amjjawad)) Date: Sat, 14 Dec 2013 02:16:09 +0400 Subject: [Sandbox][Work Item] vUDS: Quality community-Run Testing Events In-Reply-To: <52AB7F67.3030509@canonical.com> References: <20131121153825.GA2089@sup.lan> <528E65E2.3010805@canonical.com> <52AB7F67.3030509@canonical.com> Message-ID: On Sat, Dec 14, 2013 at 1:43 AM, Nicholas Skaggs < nicholas.skaggs at canonical.com> wrote: > Ali, so this has simmered for a bit and I think it's ready! Can you > please implement this into the wiki directly? I would like it to be a part > of the header, but I can help integrate once the subpages are built. We'll > follow-up with a calendar once it's setup. That will just be a manual > process to sync at first which is fine. Once the page is setup please > share. I'd suggest a few of us subscribe to the page so we know when things > change. > > Thanks again for setting this up! > > Nicholas > Hi, https://wiki.ubuntu.com/QATeam/TestingEvents https://wiki.ubuntu.com/QATeam/TestingEvents/TestingResults Header: https://wiki.ubuntu.com/QATeam/Header ALL set and done :) If you don't like the header, feel free to change it but I thought to do it all and leave the rest to you ;) You most welcome! Please, let me know if you need anything :) Thank you! -- Remember: "All of us are smarter than any one of us." Best Regards, amjjawad Areas of Involvement My Projects -------------- next part -------------- An HTML attachment was scrubbed... URL: From zgiltd at gmail.com Sat Dec 14 02:56:21 2013 From: zgiltd at gmail.com (zgiltd) Date: Sat, 14 Dec 2013 08:26:21 +0530 Subject: ASSIST ME FIX THE PROBLEM WITH MY UPDATE MANAGER : SAIAD OMAR FAROOQ Message-ID: Hello, I am using Ubuntu 12.04 LTS on my DELL Vostro1015 laptop. I have a problem with my Ubuntu update manager as i cannot check or install any updates. As there is red mark alert/indicator on my desktop and also not able to open the Ubuntu software center as it's getting crashed when clicking on it. Following is the message i get when clicked on Ubuntu update manager or Synaptic package manager; " Could not initialize the package information An unresolvable problem occurred while initializing the package information. Please report this bug against the 'update-manager' package and include the following error message: E: Unable to parse package file /var/lib/apt/lists/in.archive.ubuntu.com_ubuntu_dists_precise-updates_universe_i18n_Translation-en (1) E: Problem opening /var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_precise-security_main_binary-i386_Packages E: The package lists or status file could not be parsed or opened. E: _cache->open() failed, please report. " Please assist me fix this problem at the earliest possible. Thanks Saiad Omar Farooq Email: zgiltd at gmail.com Tel +91-809-596-8985 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Thu Dec 19 21:35:11 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 19 Dec 2013 21:35:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_mged?= =?utf-8?q?min?= Message-ID: <20131219213511.32391.98544@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by mgedmin: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=115&rev2=116 Comment: Fix instructions not to omit the main release pocket. I've been bitten by this twice. }}} 1. Stable releases (not alphas and betas) require three more lines adding to the same file, which is done by the following terminal command: {{{ + echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse - echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse + deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list From webmaster at ubuntu.com Fri Dec 20 22:01:31 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 20 Dec 2013 22:01:31 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20131220220131.18942.70353@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=252&rev2=253 Comment: 1) Due to LP# 131094 created new etiquette note about e-mail responses. 2) Misc. wording and bold fixes for emphasis and clarity. = Bug reporting etiquette = - Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: + Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. While this is targeted to the new bug reporter, experienced reporters would find these tips invaluable in getting their bugs looked at by a developer and ultimately fixed: <
><
> - Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collatoral damage avoidance. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. + Before filing any hardware related reports on Launchpad, please '''update your BIOS''', and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collatoral damage avoidance. In summation, if your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem. <
><
> - Please do not speculate on what you think is or isn't a duplicate report (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. + '''Please do not speculate on what you think is or isn't a duplicate report''' (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. <
><
> - Please '''do not quote''' Wikipedia and other non-primary resource information as fact on [[Launchpad]]. + Please '''do not quote Wikipedia''' and other non-primary resource information as fact on [[Launchpad]]. <
><
> Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed. + <
><
> + '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox. <
><
> For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> From noreply at ubuntu.com Tue Dec 24 01:18:02 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 24 Dec 2013 01:18:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/Debugging/Backlight=22_by?= =?utf-8?q?_penalvch?= Message-ID: <20131224011802.16193.13511@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Kernel/Debugging/Backlight" page has been changed by penalvch: http://wiki.ubuntu.com/Kernel/Debugging/Backlight?action=diff&rev1=24&rev2=25 Comment: As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1261853/comments/18 added video.use_native_backlight=1 kernel parameter check request. * ls -la /sys/class/backlight/intel_backlight/ > lslabacklight * {{{echo 8 > /sys/class/backlight/intel_backlight/brightness}}} * Please comment on if the brightness changes. - * Reboot with kernel parameter video.use_bios_initial_backlight=0 and make a comment on if you can now alter the backlight with hotkeys or a brightness applet. + * Reboot with just kernel parameter video.use_bios_initial_backlight=0 and make a comment on if you can now alter the backlight with hotkeys or a brightness applet. + * Reboot with just kernel parameter video.use_native_backlight=1 and and make a comment on if you can now alter the backlight with hotkeys or a brightness applet. * If your backlight hotkeys are Fn+Left and Fn+Right, add kernel parameter atkbd.softraw=0 to /boot/grub/menu.lst . Then, switch to any console, e.g. Ctrl+Alt+F1, login by root account and execute:<
> {{{showkey -s}}} <
> <
> Then, press Fn+Left and Fn+Right key to check the code that shows up on screen. Post the results to the report. For example: <
> <
> Fn+Left: <
> 0xe0 0x4c 0xe0 0xcc <
> <
> Fn+Right: <
> 0xe0 0x54 0xe0 0xd4 === Thinkpads === - * Add kernel parameters thinkpad-acpi.brightness_enable=1 acpi_backlight=vendor to /boot/grub/menu.lst . Execute: <
> {{{sudo update grub}}} <
> <
> Restart, and comment on if brightness may be changed via hotkeys and/or brightness applet. + * Add just kernel parameters thinkpad-acpi.brightness_enable=1 acpi_backlight=vendor to /boot/grub/menu.lst . Execute: <
> {{{sudo update grub}}} <
> <
> Restart, and comment on if brightness may be changed via hotkeys and/or brightness applet. * As well, execute the following and post results to your report: <
> {{{lsmod | grep thinkpad_acpi}}} = Diagnostic Techniques = From noreply at ubuntu.com Mon Dec 30 13:23:00 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 30 Dec 2013 13:23:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_mged?= =?utf-8?q?min?= Message-ID: <20131230132300.31840.99321@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingProgramCrash" page has been changed by mgedmin: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=116&rev2=117 Comment: Revert my incorrect change, I didn't notice the command above #brownpaperbag }}} 1. Stable releases (not alphas and betas) require three more lines adding to the same file, which is done by the following terminal command: {{{ - echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse - deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse + echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \ sudo tee -a /etc/apt/sources.list.d/ddebs.list