From noreply at ubuntu.com Wed Oct 3 07:56:44 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 03 Oct 2012 07:56:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_jibe?= =?utf-8?q?l?= Message-ID: <20121003075644.10072.97519@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by jibel: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=121&rev2=122 === When upgrading Ubuntu (or derivatives) === - If you encounter a bug while upgrading Ubuntu (for example, from 11.04 to 11.10), the problem package is `update-manager`. Please attach the log files contained in "/var/log/dist-upgrade/". + If you encounter a bug while upgrading Ubuntu (for example, from 11.10 to 12.04), the problem package is `update-manager` for releases until 11.10 (upgrades up to 12.04) and `ubuntu-release-upgrader-core` starting from 12.04 ( 12.04 to 12.10 onwards). Please attach the log files contained in "/var/log/dist-upgrade/". === During boot === From noreply at ubuntu.com Wed Oct 3 16:47:40 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 03 Oct 2012 16:47:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_stefanor?= Message-ID: <20121003164740.27804.59896@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Status" page has been changed by stefanor: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=59&rev2=60 Comment: Triaged for process bugs * Use this when you are confident that it should be looked at by a developer '''and''' has enough information * While not a requirement a bug's Ubuntu task status will be Triaged before any upstream forwarding occurs * With bugs about '''linux''' Triaged means that the bug has been tested with the upstream mainline kernel + * For process bugs (e.g. [[FreezeExceptionProcess|FFes]] and [[SyncRequestProcess|syncs]]) triaged means the action has been approved by the relevant developers. * '''In Progress''': * If '''you''' are working on fixing a bug, set it to {{{In Progress}}} so people know what's going on * {{{In Progress}}} bugs should be assigned to the person working on them From notgary at ubuntu.com Mon Oct 8 12:53:19 2012 From: notgary at ubuntu.com (Chris Wilson) Date: Mon, 8 Oct 2012 13:53:19 +0100 Subject: Hundred Papercuts project ideas Message-ID: Hi there all, Sorry for the blanket email to so many lists, but this is an area where I think many different people in the community would be able to contribute many different great ideas. Over the month of October, a discussion is taking place into how best to revive the Hundred Papercuts project, and ideas are being gathered on this wiki page and discussed on the mailing list of the Papercuts Ninja Launchpad team. We already have a lot of great ideas to try out, but we want as many as we can get, and different people from across the community can bring different points of view to the table. Everybody in the community is invited to suggest ideas on the wiki page, no matter how crazy or radical they may sound - we're not discarding anything until it's first been discussed. Please head on over to the wiki page, have a read through the existing ideas and add your own to the bottom. At the end of this month, we're going to go through what's there and pick out the best ones to become the foundation of the new Hundred Papercuts project. Thanks, Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Mon Oct 8 14:51:56 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 08 Oct 2012 14:51:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_trekcaptain?= =?utf-8?q?usa-tw?= Message-ID: <20121008145156.27130.32870@mangaba.canonical.com> 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 trekcaptainusa-tw: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=359&rev2=360 ||Thanks for your interest in helping to resolve this issue. There is no need to subscribe anyone to this bug, as it generates unnecessary emails and will not resolve the issue any faster. Your bug will be looked at by a developer as time permits. || + == Bug Filed Against EndOfLife Release == + + ||Thank you for taking the time to make Ubuntu better. Unfortunately, this bug is filed against an EndOfLife release of Ubuntu. This means that the release of Ubuntu this bug is filed against is no longer supported or updated. If this bug exists in a later release of Ubuntu that is supported (https://wiki.ubuntu.com/Releases contains a list of all releases of Ubuntu, both supported and EndOfLife), you may refile against the package using information from the package in that version of Ubuntu. || + == Links == Other projects have standard responses as well: From noreply at ubuntu.com Sun Oct 14 15:47:59 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 14 Oct 2012 15:47:59 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_pen?= =?utf-8?q?alvch?= Message-ID: <20121014154759.14181.80915@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=35&rev2=36 Comment: Due to LP bug 1066060: Added "As well, please attach your dmesg.txt to your bug report." One is unable to confirm the reporter is correct when one cannot see the full dmesg. If you get a device number rather than name, lspci and /sys/devices/pci* are your friends. + As well, please attach your dmesg.txt to your bug report. + = Further hints = [[http://ubuntuforums.org/showthread.php?p=3066404|Detailed analysis of ACPI kernel code for debugging a suspend problem]] From joseeantonior at ubuntu.com Mon Oct 15 05:35:42 2012 From: joseeantonior at ubuntu.com (=?ISO-8859-1?Q?Jos=E9_Antonio_Rey?=) Date: Mon, 15 Oct 2012 00:35:42 -0500 Subject: [OpenWeek] Call for Instructor Message-ID: <507BA0AE.2070502@ubuntu.com> Hello, guys! I'm organizing this OpenWeek, which will run from 24 to 26 October. I'd like to invite you guys to participate. Having a session about the BugSquad would be great. You just need to introduce yourself, explain what you do for the team, and how can people contribute to it, all of this in a 1-hour session. The schedule, with the open slots, are here: . Let me know any of you is interested in running it, and I'll put it in the schedule ASAP. Note that the 26th is the On Air! day, which means the sessions will be Live, in a G+ Hangout On Air. Thanks for your help! -- José Antonio Rey From rickadt at gmail.com Wed Oct 17 18:33:50 2012 From: rickadt at gmail.com (Carlos Henrique) Date: Wed, 17 Oct 2012 15:33:50 -0300 Subject: Fixed bug with icons in the launcher Message-ID: I realized that there is a bug in setting the icon of the launcher Mozilla Firefox when you have an icon on the desktop with a shortcut to a web site, for example, I have an icon on my desktop that points to a website email. and when I fixed the Firefox icon to the Unity launcher he is pointing to the site email also. From btkdpl at yahoo.fr Fri Oct 19 08:18:54 2012 From: btkdpl at yahoo.fr (btkdpl) Date: Fri, 19 Oct 2012 09:18:54 +0100 (BST) Subject: failure of update manager 12.04 Message-ID: <1350634734.74988.YahooMailNeo@web132301.mail.ird.yahoo.com> Hello! Update manager fails with: "Failed to load the package list" To report a bug, you use the update manager, which fails (recursive call). How can one now report a bug? I have appended the information I gleaned about the problem, if anyone can help. Thanks in advance Alvin Bampton -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: bugReport.odt Type: application/vnd.oasis.opendocument.text Size: 29153 bytes Desc: not available URL: From davmor2 at davmor2.co.uk Fri Oct 19 14:12:10 2012 From: davmor2 at davmor2.co.uk (Dave Morley) Date: Fri, 19 Oct 2012 15:12:10 +0100 Subject: failure of update manager 12.04 In-Reply-To: <1350634734.74988.YahooMailNeo@web132301.mail.ird.yahoo.com> References: <1350634734.74988.YahooMailNeo@web132301.mail.ird.yahoo.com> Message-ID: <50815FBA.7010008@davmor2.co.uk> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 19/10/12 09:18, btkdpl wrote: > Hello! Update manager fails with: "Failed to load the package > list" To report a bug, you use the update manager, which fails > (recursive call). > > How can one now report a bug? I have appended the information I > gleaned about the problem, if anyone can help. > > Thanks in advance Alvin Bampton > > ubuntu-bug update-manager will trigger the bug reporting process - -- You make it, I'll break it! I love my job :) http://www.ubuntu.com http://www.canonical.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlCBX7oACgkQT5xqyT+h3OjacQCgxvvzK8vLrGpbOW6oGd1ODzcT rhAAnRG2TddqMeR+ngMCE0d7hqnj7w5r =4cY7 -----END PGP SIGNATURE----- From lars.duesing at camelotsweb.de Fri Oct 19 14:20:20 2012 From: lars.duesing at camelotsweb.de (Lars Duesing) Date: Fri, 19 Oct 2012 16:20:20 +0200 Subject: failure of update manager 12.04 In-Reply-To: <50815FBA.7010008@davmor2.co.uk> References: <1350634734.74988.YahooMailNeo@web132301.mail.ird.yahoo.com> <50815FBA.7010008@davmor2.co.uk> Message-ID: <508161A4.60500@camelotsweb.de> Alvin, Dave, problem was maybe that archive.ubuntu.com didn't resolve for a few minutes this day... Lars Am 19.10.2012 16:12, schrieb Dave Morley: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 19/10/12 09:18, btkdpl wrote: >> Hello! Update manager fails with: "Failed to load the package >> list" To report a bug, you use the update manager, which fails >> (recursive call). >> >> How can one now report a bug? I have appended the information I >> gleaned about the problem, if anyone can help. >> >> Thanks in advance Alvin Bampton >> >> > ubuntu-bug update-manager will trigger the bug reporting process > > - -- > You make it, I'll break it! > > I love my job :) > http://www.ubuntu.com > http://www.canonical.com > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ > > iEYEARECAAYFAlCBX7oACgkQT5xqyT+h3OjacQCgxvvzK8vLrGpbOW6oGd1ODzcT > rhAAnRG2TddqMeR+ngMCE0d7hqnj7w5r > =4cY7 > -----END PGP SIGNATURE----- > From webmaster at ubuntu.com Fri Oct 19 22:01:40 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 19 Oct 2012 22:01:40 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20121019220140.31608.97762@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=191&rev2=192 Comment: 1) 10.10 EOL -link & +Quantal. 2) + periph. info. 3) Multiple hotkey probs separate reports LP# 815419. 4) ] Deutsch. 5) Redid dup chk. 6) Fold lnx/xorg/sound caveat prior sect. 6) Misc grammar fixes. = 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: + <
><
> + Please do not stack multiple issues into one report. For example, jamming suspend and hibernate into one report, reporting multiple [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] problems into one report (ex. FN+F3 doesn't turn off my laptop WiFi and FN+Right doesn't turn the brightness on my [[https://wiki.ubuntu.com/Kernel/Debugging/Backlight|backlight]] down). Make one report for each individual problem. + <
><
> - - Please do not stack multiple issues into one report. For example, many jam suspend and hibernate into one report. Please do not do this. Make one report for each against the Linux package via a terminal: - {{{ - ubuntu-bug linux - }}}<
> Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", XYZ person(s) do not care about fixing bugs, etc. Especially, if you have not followed the directions mentioned in this article, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources. <
><
> Please keep the bug objective as possible. It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large. @@ -29, +27 @@ = How to report bugs = - Ubuntu uses Launchpad to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report. + Ubuntu uses [[Launchpad]] to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report. == Using Kubuntu? == @@ -53, +51 @@ == 3. Make sure the bug hasn't already been reported == - When filing a non-[[https://launchpad.net/ubuntu/+source/linux|linux]] package bug, please make sure it has not already been reported by searching through the [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]] and the release notes for your version of Ubuntu: + First, check the release notes for your version of Ubuntu: * [[http://www.ubuntu.com/getubuntu/releasenotes/804|Ubuntu 8.04 LTS (Hardy Heron)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1004|Ubuntu 10.04 LTS (Lucid Lynx)]] - * [[http://www.ubuntu.com/getubuntu/releasenotes/1010|Ubuntu 10.10 (Maverick Meerkat)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1104|Ubuntu 11.04 (Natty Narwhal)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1110|Ubuntu 11.10 (Oneiric Ocelot)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/1210|Ubuntu 12.10 (Quantal Quetzal)]] - If the problem is not in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you have further information about an already reported bug, add this information to the existing report, rather than opening a new one. - If the problem is in the package [[https://launchpad.net/ubuntu/+source/linux|linux]], and you are the original reporter, here are the ways to maximize the speed with which your bug is fixed: - * Check for the problem in the earliest release that works for your hardware and the lastest. Report your testing results in the report. - * If your bug is a regression, commit bisect it following https://wiki.ubuntu.com/Kernel/KernelBisection . Report your bisect results in the report. - * Test for this problem in the mainline kernel following https://wiki.ubuntu.com/Kernel/MainlineBuilds . Report your mainline testing results in the report. + === Linux kernel, X.Org, and Sound === + + For bugs in the packages [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel (which includes sound), [[https://launchpad.net/ubuntu/+source/xorg|xorg]], [[https://launchpad.net/ubuntu/+source/xorg-server|xorg]], [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]], [[https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel|xserver-xorg-video-intel]] (and other xserver-xorg-video-* like nouveau, radeon, ati, openchrome, geode, etc.]], you are welcome to check for duplicates. However, depending on if you are the original reporter or not, determines what to do next. + + ==== You are not the original report ==== + + * Please open a '''new''' report instead of adding debugging information, attachments, apport-collect'ing, or "Me too!" comments on what may appear to be a similar bug. Chances are that your hardware does not match the existing bug's hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug. * Please do not assume because you have the same desktop or laptop model line as another original reporter's bug report, that your problem is the same. Frequently, computer vendors use different parts under the hood within the same model line. + * Regarding peripherals, please do not assume because you have the same peripheral, and similar problems, it is the same bug. Please file a new bug report. - === Sound, X drivers, Linux kernel bugs === + ==== You are the original reporter ==== - /!\ '''For sound, X drivers, and [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel bugs''': please open a '''new''' report instead of adding debugging information, attachments, apport-collect'ing, or "Me too!" comments on what may appear to be a similar bug: chances are that your hardware does not match the existing bug's hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug. + If you are the original reporter, here are the ways to maximize the speed with which your bug is fixed: + * Check for the problem in the earliest release that works for your hardware and the latest. Report your testing results in the report. + * Test for this problem in the mainline kernel following [[https://wiki.ubuntu.com/Kernel/MainlineBuilds]] . Report your mainline testing results in the report. + * If your bug is a regression, bisect it following [[https://wiki.ubuntu.com/Kernel/KernelBisection]] . Report your bisect results in the report. + + === User Space === + + First, please make sure it has not already been reported by searching through [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]]. If you find an already reported bug that is exactly like the problem you have, please feel free to add this information to the existing report, rather than opening a new one. + However, if you have any doubt as to it being the same or not, please file a separate report. [[#Top|Back to top]] @@ -259, +268 @@ * [[ReportingBugs_ru|Русский]] * [[ReportingBugs_zh-cn|中文（中国）－－ 建设中]] * [[ReportingBugs-it|Italiano]] - * [[https://help.ubuntu.com/community/ReportingBugs_de|Deutsch] + * [[https://help.ubuntu.com/community/ReportingBugs_de|Deutsch]] [[#Top|Back to top]] = See Also = From webmaster at ubuntu.com Sat Oct 20 17:08:35 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 20 Oct 2012 17:08:35 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20121020170835.17175.19409@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=195&rev2=196 Comment: 1) Added package specific info due to https://bugs.launchpad.net/fglrx/+bug/1068661. 2) RM'd română link as no article. * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]] * [[http://www.ubuntu.com/getubuntu/releasenotes/1210|Ubuntu 12.10 (Quantal Quetzal)]] - === Linux kernel, X.Org, and Sound === + === Hardware driver bugs (e.g. Sound, Linux kernel, X.Org, and Nvidia / AMD proprietary drivers) === - For bugs in the packages [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel (which includes sound), [[https://launchpad.net/ubuntu/+source/xorg|xorg]], [[https://launchpad.net/ubuntu/+source/xorg-server|xorg-server]], [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]], [[https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel|xserver-xorg-video-intel]] (and other xserver-xorg-video-* like nouveau, radeon, ati, openchrome, geode, etc.), you are welcome to check for duplicates. However, depending on if you are the original reporter or not, determines what to do next. + * For hardware driver bugs you are welcome to check for duplicates. However, depending on if you are the original reporter or not, determines what to do next. The following is a list of hardware packages: + * For sound bugs please see [[https://wiki.ubuntu.com/DebuggingSoundProblems]]. + * [[https://launchpad.net/ubuntu/+source/linux|Linux]] kernel (e.g. suspend, hibernate, and other [[https://wiki.ubuntu.com/DebuggingProcedures#Kernel|potential kernel issues]]). + * [[https://launchpad.net/ubuntu/+source/xorg|xorg]] and [[https://launchpad.net/ubuntu/+source/xorg-server|xorg-server]] + * [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]] (e.g. [[https://wiki.ubuntu.com/DebuggingTouchpadDetection|certain Touchpad issues]]). + * [[https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel|xserver-xorg-video-intel]] and other xserver-xorg-video-* like nouveau, radeon, ati, openchrome, geode, etc. + * Nvidia proprietary driver software: [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers|nvidia-graphics-drivers]] , [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173|graphics-drivers-173]] , [[https://launchpad.net/ubuntu/+source/nvidia-settings|nvidia-settings]] , and [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180|nvidia-graphics-drivers-180]] . + * AMD proprietary drivers: [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer|fglrx-installer]] and [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates|fglrx-installer-updates]]. ==== You are not the original report ==== @@ -72, +79 @@ * Test for this problem in the mainline kernel following [[https://wiki.ubuntu.com/Kernel/MainlineBuilds]] . Report your mainline testing results in the report. * If your bug is a regression, bisect it following [[https://wiki.ubuntu.com/Kernel/KernelBisection]] . Report your bisect results in the report. - === User Space === + === Desktop Applications === + For [[https://wiki.ubuntu.com/DebuggingProcedures#Desktop_Applications|desktop applications]] , please make sure it has not already been reported by searching through [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]]. If you find an already reported bug that is exactly like the problem you have, please feel free to add this information to the existing report, rather than opening a new one. However, if you have any doubt as to it being the same or not, please file a separate report. - First, please make sure it has not already been reported by searching through [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]]. If you find an already reported bug that is exactly like the problem you have, please feel free to add this information to the existing report, rather than opening a new one. - However, if you have any doubt as to it being the same or not, please file a separate report. [[#Top|Back to top]] @@ -110, +116 @@ If your system lockups up, freezes, logs you out, etc., then this is not an application crash, but a system crash. Please see below, and consult the following article for these types of problems [[https://help.ubuntu.com/community/DebuggingSystemCrash]]. - === Non-crash bugs === + === Non-crash hardware and desktop application bugs === The method for reporting bugs in Ubuntu is by using the tool "ubuntu-bug", otherwise known as '''Apport'''. When reporting a bug, you must tell Apport which program or [[https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?|package]] is at fault. @@ -299, +305 @@ = Other languages = * [[ReportingBugs_es|Español]] - * [[http://www.ubuntu.ro/documentatie/comunitate/RaportareErori |română]] * [[ReportingBugs_ru|Русский]] * [[ReportingBugs_zh-cn|中文（中国）－－ 建设中]] * [[ReportingBugs-it|Italiano]] From noreply at ubuntu.com Sun Oct 21 04:10:23 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 21 Oct 2012 04:10:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingHardwareDetection=22_by?= =?utf-8?q?_penalvch?= Message-ID: <20121021041023.19182.44186@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingHardwareDetection" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingHardwareDetection?action=diff&rev1=23&rev2=24 Comment: 1) lsusb -> lsusb -v. 2) RM'd request for lspci -vvnn, dmesg, and cat proc/version_signature as redudant. See ## wiki comments. <> - ## 20121020 https://launchpad.net/~penalvch This article is obsolete. Now that we are in the apport era, when one files an bug against the linux package via ubuntu-bug linux, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information all of the information, the information requested in this article is filed: - ## BootDmesg.txt + ## 20121021 https://launchpad.net/~penalvch Now that we are in the apport era, when one files a bug using it against the linux package via ubuntu-bug linux, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information , the following attachments (that requesting is redundant) are automatically attached to the bug report: + ## BootDmesg.txt -> dmesg, gives very similar info as uname -a, and gives exactly same as cat - ## CurrentDmesg.txt + ## CurrentDmesg.txt -> dmesg + ## Lspci.txt -> lspci ---vvnn - ## Lspci.txt - ## Lsusb.txt - ## As well as other helpful attachments: - ## AlsaInfo.txt - ## CRDA.txt - ## Dependencies.txt - ## IwConfig.txt - ## ProcCpuinfo.txt - ## ProcInterrupts.txt - ## ProcModules.txt - ## PulseList.txt - ## UdevDb.txt - ## UdevLog.txt - ## WifiSyslog.txt ||<>|| = Debugging procedure = - = Reporting a bug = + == Reporting a bug == + * When reporting a problem with hardware detection, you should report the bug against the [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel package. - When reporting a problem with hardware detection, you should report the bug against the kernel. Beginning with the Hardy release, all kernel bugs should be reported against the '''linux''' kernel source package. - - Also, all reports should contain the following information. Please be sure to '''attach''' these files to the bug report. - - * uname -a > uname-a.log - * cat /proc/version_signature > proc_version_signature.log - * sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w) - * dmesg > dmesg.log - - If the system is not correctly detecting a USB device, also '''attach''' the output of: + * If the system is not correctly detecting a USB device, also '''attach''' the output of: - - * lsusb > lsusb.log + * lsusb -v > lsusb-v.log ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Sun Oct 21 03:56:54 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 21 Oct 2012 03:56:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKeyboardDetection=22_by?= =?utf-8?q?_penalvch?= Message-ID: <20121021035654.14436.46651@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKeyboardDetection" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKeyboardDetection?action=diff&rev1=18&rev2=19 Comment: 1) Please see ## wiki comments. 2) Misc. minor syntax fixes. 3) RM'd stale comments. 4) RM'd stale kernel team link. 5) Add hotkey link in key don't work (as expected) ||'''This page is potentially out of date as of Intrepid due to input-hotplug'''. Please remove this message if you update the page.|| + ## 20121020 https://launchpad.net/~penalvch I don't feel comfortable removing above message as I'm not familiar enough with this statement to believe I have updated it sufficiently. Despite this, asking for the == General information == is mostly redundant. Now that we are in the Apport era, when one files a bug by it, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information , against the xorg package, the following attachments (that requesting is redundant) are automatically attached to the bug report and then shifted to xserver-xorg-input-evdev by bugbot (ex. https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1064265 ) Otherwise, reporting against evdev only gives dependencies.txt: + ## BootDmesg.txt -> gives very similar info as uname -a, and gives exactly same as cat /proc/version_signature + ## Lspci.txt -> same as lspci -vvnn <> + ||<>|| = Introduction = - Problems with keyboard detection typically fall into one off these categories: + Problems with keyboard detection typically fall into one of these categories: 1. Your keyboard doesn't work at all. 1. Your USB keyboard stops working after a while. 1. Some keys of your keyboard don't work (as expected). = How to file a bug report = + Keyboard related bugs should initially be filed against '''[[https://launchpad.net/ubuntu/+source/xorg|xorg]]''', as [[https://launchpad.net/~bugbot|bugbot]] will switch it to the correct package (ex. [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-evdev|xserver-xorg-input-evdev]]). If the bug turns out to be a kernel bug or a bug in another package, bug triagers can assign the bug additionally to that package and mark the xserver-xorg-input-evdev task as invalid. - ## Before filing a bug please check the list of [#knownbugs known bugs] at the end of this document. - - Keyboard related bugs should initially be filed against '''xserver-xorg-input-evdev'''. - If the bug turns out to be a kernel bug or a bug in another package, bug triagers can assign the bug additionally to that package and mark the xserver-xorg-input-evdev task as invalid. <> + == General information == For all bug categories the following general information should be provided: - 1. What brand and model is your keyboard.<
>How is your keyboard connected to your PC: DIN, PS/2, USB, USB wireless, ... + 1. What brand and model is your keyboard.<
>How is your keyboard connected to your PC: DIN, PS/2, USB, bluetooth, etc. - 1. For a USB keyboard enter the following command on a terminal/console: {{{ + 1. For a USB keyboard, enter the following command in a terminal: {{{ - lsusb -v > ~/lsusb-v }}} + lsusb -v > ~/lsusb-v + }}} + * Attach as separate attachment to your bug report ~/lsusb-v. - 1. Open a terminal/console and enter the following commands (minimal information as described in KernelTeamBugPolicies): {{{ - uname -a > ~/uname-a - cat /proc/version_signature > ~/version_signature - sudo lspci -vvnn > ~/lspci-vvnn }}} - 1. Attach {{{~/lsusb-v}}}, {{{~/uname-a}}}, {{{~/version_signature}}} and {{{~/lspci-vvnn}}} to the bug report as separate attachments. == In case your keyboard doesn't work at all == 1. Provide the [[#generalinfo|general information]]. 1. If you have a PS/2 keyboard make sure it was connected before booting Ubuntu. To complete the steps below you will need to connect a USB keyboard. - 1. If you have a USB keyboard unplug it an replug it to see if it starts working. If it doesn't you should have connected a PS/2 keyboard before booting Ubuntu in addition to your USB keyboard to complete the steps below. + 1. If you have a USB keyboard, unplug and replug it to see if it starts working. If it doesn't, you should have connected a PS/2 keyboard before booting Ubuntu in addition to your USB keyboard to complete the steps below. - 1. Enter the following command in a terminal/console: {{{ + 1. Enter the following command in a terminal: {{{ dmesg > ~/dmesg }}} - 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. + 1. Attach as separate attachments to your bug report {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}}. == In case your USB keyboard stops working after a while == For debugging this problem you either need a PS/2 keyboard or 2 computers in a network.<
>If the second machine runs Windows you need to install putty.exe from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html. - 1. Provide the [[#generalinfo|general information]]. 1. If you don't have a PS/2 keyboard install the openssh-server package on the machine with the keyboard problem. If you have a PS/2 keyboard connect it addition to your USB keyboard before booting Ubuntu. 1. Direct after logging in to GNOME, KDE or Xfce open a terminal and enter the following commands: {{{ @@ -60, +58 @@ diff -ns ~/dmesg_boot ~/dmesg > ~/dmesg_diff cp /var/log/Xorg.0.log ~/Xorg.0.log_tmp diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff }}} - 1. Attach {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments. + 1. Attach as separate attachments to your bug report {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}}. == In case some keys of your keyboard don't work (as expected) == @@ -68, +66 @@ 1. Open a terminal/console and enter the following commands: {{{ xprop -root | grep XKB > ~/xkb gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd > ~/gconf }}} + 1. Attach as separate attachments to your bug report {{{~/xkb}}} and {{{~/gconf}}}. + 1. Check the [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] debugging article for any more relevant information to provide. - 1. Attach {{{~/xkb}}} and {{{~/gconf}}} to the bug report in separate attachments. - - ##[[Anchor(knownbugs)]] - ##= Known bugs = - - ##Description of known issues, how to recognise them and stock responses/actions. - - ##'''Open''' - ##|| '''Bug#''' || '''Description''' || '''Action''' || - ##|| [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 #9068] || Back and Forward keys don't work || If you want your serial mouse to be autodetected in future versions of Ubuntu, please help by following the steps described here: https://lists.ubuntu.com/archives/ubuntu-devel/2006-February/015020.html and attach the requested information to [https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/9068 bug #9068]. || - - ##'''Closed''' - ##|| '''Bug#''' || '''Description''' || '''Action''' || - ##|| [https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896 #8896] ##|| This bug can be identified by ... || blabla || - - ## = Non-bugs = - - ## How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses. ---- CategoryBugSquad CategoryDebugging From hggdh2 at ubuntu.com Wed Oct 24 20:19:07 2012 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 24 Oct 2012 15:19:07 -0500 Subject: Question In-Reply-To: <20121023184426.12969.54598.launchpad@wampee.canonical.com> References: <20121023184426.12969.54598.launchpad@wampee.canonical.com> Message-ID: <50884D3B.5060105@ubuntu.com> On 23/10/12 13:44, Ricardo Luiz wrote: > Hi, I am Ricardo Luiz and I have a question: > In the BugSquad´s page on Launchpad I can read the intsruction: "* > Subscribe to the Bug Squad Mailing List", > but "This team does not use Launchpad to host a mailing list. " > Please, edit the wrong information! The LP data did not specify *where* to sign up. Ricardo's comment is correct -- it could be inferred that we were talking about a LP mailing list. I updated the description, providing a direct link to the BugSquad's subscription page at https://lists.ubuntu.com. Thanks to Ricardo for the heads up. Cheers, ..C.. p.s. this just shows how a bug can be live for a few years, without anyone noticing. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 897 bytes Desc: OpenPGP digital signature URL: From tecnonotec at gmail.com Thu Oct 25 03:36:52 2012 From: tecnonotec at gmail.com (Ricardo Luiz) Date: Thu, 25 Oct 2012 01:36:52 -0200 Subject: Question In-Reply-To: <50884D3B.5060105@ubuntu.com> References: <20121023184426.12969.54598.launchpad@wampee.canonical.com> <50884D3B.5060105@ubuntu.com> Message-ID: <5088B3D4.9050507@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 All right! Thanks - -- - -- Ricardo Luiz Ubuntu-Br-SP member http://launchpad.net/~tecnonotec skype: ricaldre jabber: rluiz at jabber.org gtalk: tecnonotec at gmail.com msn: rluiz at live.com On 24-10-2012 18:19, C de-Avillez wrote: > On 23/10/12 13:44, Ricardo Luiz wrote: >> Hi, I am Ricardo Luiz and I have a question: >> In the BugSquad´s page on Launchpad I can read the intsruction: "* >> Subscribe to the Bug Squad Mailing List", >> but "This team does not use Launchpad to host a mailing list. " >> Please, edit the wrong information! > > > The LP data did not specify *where* to sign up. Ricardo's comment is > correct -- it could be inferred that we were talking about a LP > mailing list. > > I updated the description, providing a direct link to the BugSquad's > subscription page at https://lists.ubuntu.com. > > Thanks to Ricardo for the heads up. > > Cheers, > > ..C.. > > p.s. this just shows how a bug can be live for a few years, > without anyone noticing. > - -- - -- Ricardo Luiz Ubuntu-Br-SP member http://launchpad.net/~tecnonotec skype: ricaldre jabber: rluiz at jabber.org gtalk: tecnonotec at gmail.com msn: rluiz at live.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBAgAGBQJQiLPCAAoJEIPzO37RCYpT/oYH/RJ4kTfdNK/87vmyh+Va0lFv 4DLE7B0KBGUa5EiyG0+XjDGwywxClsgvM06NDcW4txa4kcnVab/NuShpF06BtZVA y8RK7YdtWWWDbFFMnaHbpBy316T5TjDdlG4LdY2r74GgJjy1/hXUhfkHVdhu2vOZ mwUfu0DAHXW1MNYLOa5KapmKXteSeEuoiyu2Xyfa25SUyNAfd5EUf0ZJJsM1jY3e IIrNhsHsjP2PiJVtzNLcd0rWXnyH1PfAOucmp1Ela8X71p77SmoWHfse4NpzMwvD 8e2qCH1I8+0fgSEoYw7gZkgktBHa39iJRJWAPDrUjRt9RWdrOwJCOvzKt/fdFcM= =wKl1 -----END PGP SIGNATURE----- From noreply at ubuntu.com Fri Oct 26 19:50:17 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 26 Oct 2012 19:50:17 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Troubleshooting=22_by_bryce?= Message-ID: <20121026195017.14913.5126@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "X/Troubleshooting" page has been changed by bryce: http://wiki.ubuntu.com/X/Troubleshooting?action=diff&rev1=58&rev2=59 * [[X/HybridGraphics|Hybrid Graphics is Unsupported]] - Not officially supported, but the community has workarounds Input Issues - * [[X/Troubleshooting/HalBreaksKeyboardAndMouse|Keyboard and mouse quit working]] * [[Hotkeys/Troubleshooting|Multimedia hotkey problems]] * [[DebuggingKeyboardDetection|Keyboard detection]] * [[DebuggingTouchpadDetection|Touchpad detection]] From noreply at ubuntu.com Sun Oct 28 22:37:20 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 28 Oct 2012 22:37:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_pen?= =?utf-8?q?alvch?= Message-ID: <20121028223720.21094.1453@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=36&rev2=37 Comment: Due to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1070627 added request for full computer model and BIOS update. The debugging procedure described below requires a linux kernel with the capability of "/sys/power/pm_trace". You can ensure that pm_trace'ing is possible by looking in the directory /sys/power/ (from a terminal type {{{ls /sys/power/}}}) to see if a file called pm_trace exists. + = Debugging information to provide in your bug report = + + 1. Full computer manufacturer and model. + 1. If you upgrade your BIOS to the newest version available, does this change anything? + 1. Resume trace mentioned below. + - = "resume-trace" debugging procedure for finding buggy drivers = + == "resume-trace" debugging procedure for finding buggy drivers == Resume problems are difficult to debug. The approach used here needs to make notes on progress during resume and be able to recover them after a manual reboot. But there is no non-volatile storage available at the time resume is bringing up your computer. The only hardware on a PC motherboard that retains information across power cycles is the real time clock (RTC), so that is what is used. For those that want to know the details, read Documentation/power/s2ram.txt in your kernel sources. The implementation of suspend/resume debug trace is in drivers/base/power/trace.c. From melchiaros at aol.com Mon Oct 29 12:02:43 2012 From: melchiaros at aol.com (melchiaros) Date: Mon, 29 Oct 2012 13:02:43 +0100 Subject: Invisible crasher of cheese - some open accessible dublicates Message-ID: <508E7063.9090500@aol.com> Hi, on one of my reports filed during Quantal development phase, some more people come around now on Quantal final and report that they are also affected: https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1044711 The problem is that cheese freezes immediatelly on video recording. On the original report apport was not able to catch the problem and with this the report has no stacktrace. I gave it a retest on my system, which shows the error again, but this time apport was able to detect it. Unfortunally in meantime there was created a private report, which prevents me to get the stacktrace. You know the GNOME project would like to have it. Could anybody mark bug #1062282 as puplic. The upstream report for cheese can be found on : https://bugzilla.gnome.org/show_bug.cgi?id=687106 greetings melchiaros -------------- next part -------------- An HTML attachment was scrubbed... URL: From melchiaros at aol.com Mon Oct 29 12:49:55 2012 From: melchiaros at aol.com (melchiaros) Date: Mon, 29 Oct 2012 13:49:55 +0100 Subject: Invisible crasher of cheese - some open accessible dublicates In-Reply-To: <508E7063.9090500@aol.com> References: <508E7063.9090500@aol.com> Message-ID: <508E7B73.20105@aol.com> Am 29.10.2012 13:02, schrieb melchiaros: > Hi, > > on one of my reports filed during Quantal development phase, some > more people come around now on Quantal final and report that they are > also affected: > > https://bugs.launchpad.net/ubuntu/+source/cheese/+bug/1044711 > > The problem is that cheese freezes immediatelly on video recording. > > On the original report apport was not able to catch the problem and > with this the report has no stacktrace. > > I gave it a retest on my system, which shows the error again, but this > time apport was able to detect it. > > Unfortunally in meantime there was created a private report, > > which prevents me to get the stacktrace. > > You know the GNOME project would like to have it. > > Could anybody mark bug #1062282 > as puplic. > > The upstream report for cheese can be found on : > > https://bugzilla.gnome.org/show_bug.cgi?id=687106 > > greetings > > melchiaros > > Done. No further help needed. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Mon Oct 29 21:12:48 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 29 Oct 2012 21:12:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=5Fit=22_by_fabiom?= =?utf-8?q?arconi?= Message-ID: <20121029211248.26203.40319@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEmacs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEmacs_it?action=diff&rev1=2&rev2=3 = Come eseguire il Triage = - I bug riconosciuti da Apport sono generalmente dovuti a pacchetti che hanno fallito l'installazionee solitamente includono allegati i file Dpkg``Terminal``Log o Var``DistUpgrade``Term``Log; Questi file sono i primi da esaminare. + I bug riconosciuti da Apport sono generalmente dovuti a pacchetti che hanno fallito l'installazionee solitamente includono allegati i file DpkgTerminalLog o VarDistUpgradeTermLog; Questi file sono i primi da esaminare. Molto probabilmente conterranno un messaggio d'errore, circa alla fine, che indicherà quale pacchetto ha fallito l'installazione e perchè. From noreply at ubuntu.com Mon Oct 29 21:25:22 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 29 Oct 2012 21:25:22 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=5Fit=22_by_fabiom?= =?utf-8?q?arconi?= Message-ID: <20121029212522.26179.9634@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingEmacs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/DebuggingEmacs_it?action=diff&rev1=3&rev2=4 == Errori dovuti all'installazione di pacchetti == Un apparente errore di Emacs è spesso dovuto all'installazione di qualche pacchetto aggiuntivo che contiene un bug o è incompatibile con la versione di Emacs installata. + {{{ `emacs-install: /usr/lib/emacsen-common/packages/install/ecb emacs23 ` failed at /usr/lib/emacsen-common/emacs-install line 28, line 17. `dpkg: error processing emacs23 (--configure): ` subprocess installed post-installation script returned error exit status 1 + }}} - Che afferma che `ecb` ne è la causa (bug || [[https://launchpad.net/bugs/466531|466531]] + Che afferma che `ecb` ne è la causa (bug || [[https://launchpad.net/bugs/466531|466531]]) + {{{ `dpkg: dependency problems prevent configuration of emacs: ` emacs depends on emacs23 | emacs23-lucid | emacs23-nox; however: ` Package emacs23 is not configured yet. @@ -40, +43 @@ ` Package emacs23-nox is not installed. `dpkg: error processing emacs (--configure): ` dependency problems - leaving unconfigured - + }}} Ciò significa che un problema precedente ha impedito l'installazione di emacs. È necessario andare a ritroso nel log file per capire cosa è successo. == Errori Byte-compilation == @@ -101, +104 @@ '''Aperti''' || '''Bug''' || '''Soggetto''' || '''Sintomo''' || - || [[https://launchpad.net/bugs/8896|8896]] || Il soggetto da LP || questo bug può essere identificato da ... || + || [[https://launchpad.net/bugs/466531|466531]] ||ecb incompatibile con emacs-23|| Il processo di post-installazione ha fornito un codice d'uscita diverso da zero. Ovviamente questa potrebbe non essere l'unica ragione. '''Chiusi''' || '''Bug''' || '''Soggetto''' || '''Sintomo''' || From noreply at ubuntu.com Wed Oct 31 08:02:05 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 08:02:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20121031080205.27757.68396@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=23&rev2=24 * Questa funzionalità non è supportata da nessun altro componente coinvolto nel funzionamento della barra menu (es. dbusmenu, unity ed anche GTK) e quindi nessun cambiamento può essere fatto in firefox per ottenere questa funzionalità nella barra globale. Vi preghiamo di non segnalare questo problema. + + ==== La funzionalità type-ahead non funziona con la barra memù globale ==== + + + + Gecko ha una funzionalità che cosente la selezione del segnalibro da un menù utilizzando la tastiera, utilizzando una funzionalità simile a type-ahead.s a feature that allows you to select bookmark items from a menu with the keyboard, using a type-ahead like feature. Other toolkits lack this feature though, so this won't work with the global menubar. Please don't report this as a bug against Firefox, as it isn't. This is functionality that needs to be added to the toolkit responsible for drawing the menu === La voce "Apri con" non offre una scelta di applicazioni === From noreply at ubuntu.com Wed Oct 31 08:30:16 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 08:30:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20121031083016.1012.98592@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=24&rev2=25 - Gecko ha una funzionalità che cosente la selezione del segnalibro da un menù utilizzando la tastiera, utilizzando una funzionalità simile a type-ahead.s a feature that allows you to select bookmark items from a menu with the keyboard, using a type-ahead like feature. Other toolkits lack this feature though, so this won't work with the global menubar. Please don't report this as a bug against Firefox, as it isn't. This is functionality that needs to be added to the toolkit responsible for drawing the menu + Gecko ha una funzionalità che cosente la selezione del segnalibro da un menù utilizzando la tastiera, utilizzando una funzionalità simile a type-ahead. L'altro strumento non ha questa funzionalità, quindi non può funzionare con la barra menù globale. Siete pertanto invitati a non riportare questo bug contro Firefox, perchè non è pertinente. Qesta funzionalità dovrà essere implementata nello strumento responsabile del disegno del menù. === La voce "Apri con" non offre una scelta di applicazioni === From noreply at ubuntu.com Tue Oct 30 21:32:50 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 30 Oct 2012 21:32:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20121030213250.19004.34120@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=22&rev2=23 Ovviamente per Thunderbird sostituire firefox con thunderbird. Se il medesimo problema può essere ricreato anche nella versione di mozilla, allora potete aiutare gli sviluppatori di Ubuntu segnalando il bug direttamente upstream a Mozilla seguendo queste linee guida: [[https://developer.mozilla.org/en/Bug_writing_guidelines|bug reporting guidelines]]. + + == Controllare la console degli errori == + + Alcuni errori potrebbero derivare da una mancata gestione di un'eccezione JS o altri errori che potrebbero essere loggati nella console degli errori e che fornirebbero un'indizio decisivo per identificare la causa del bug. + Per visualizzarli, aprire la console degli errori tramite: Strumenti > Sviluppo web > Console degli errori > Errori. + Nota, potrebbe essere necessario abilitarla tramite "about:config", ed impostare "devtools.errorconsole.enabled" su "true". == Problemi con uno specifico sito web == @@ -228, +234 @@ == Eccessivo utilizzo della memoria == - Quando si segnala un bug inerente un eccessivo utilizzo della memoria, si '''deve''' copiare ed incollare il contenuto di "about:memory" eseguita tramite Apport. Vi preghiamo di non segnalare anomalie inerenti un eccessivo utilizzo di memoria senza avar allegato questa informazione, dato che sarà la prima cosa che lo sviluppatore vi chiederà. + Quando si segnala un bug inerente un eccessivo utilizzo della memoria, si '''deve''' copiare ed incollare il contenuto di "about:memory" alla segnalazione eseguita tramite Apport. Vi preghiamo di non segnalare anomalie inerenti un eccessivo utilizzo di memoria senza avar allegato questa informazione, dato che sarà la prima cosa che lo sviluppatore vi chiederà. In futuro speriamo di poter rendere automatico questo passaggio. @@ -236, +242 @@ Si tenga presente che Firefox resta abbastanza coinvolto nel debugging di carenze di memoria. Se vi sentite avventurosi, consultare [[https://developer.mozilla.org/en/Debugging/Debugging_memory_leaks|Debugging memory leaks]] e [[https://developer.mozilla.org/en/Debugging_Mozilla_with_Valgrind|Debugging Mozilla with Valgrind]] - == Controllare la console degli errori == - - Alcuni bug possono scaturire da eccezioni JS non gestite "unhandled JS exceptions" o altri messaggi d'errore visibili nella console degli errori, e questi ultimi possono fornire un valido indizio sulla causa di un bug. Per visualizzarli, aprire la console degli errori da "Strumenti -> Sviluppo web -> Console degli errori" e selezionare "Errori". - - Nota: potrebbe essere necessario abilitare la voce nel menù per poter accedere alla console degli errori. per fare ciò, aprire "about:config" ed impostare "devtools.errorconsole.enabled" su "true" == Altri problemi specifici == === Problemi coi menù in un sistema che usa una barra globale per i menù === - Per impostazione predefinita, Unity visualizza la barra menù delle applicazioni nel pannello superiore. Anche altri ambienti desktop potrebbero fornire questa funzionalità (un plasmoide KDE fornisce appunto questa funzionalità). + Per impostazione predefinita, Unity visualizza i menu della finestra nel pannello superiore. Anche altri ambienti desktop potrebbero fornire questa funzionalità (un plasmoide KDE fornisce appunto questa funzionalità). In questo tipo di ambienti i problemi con i menù non sono sempre bug nelle applicazioni. - Se si sperimenta un problema con il '''contenuto''' della barra menù, il menù o le sue voci (es. ciò che dice il testo, cosa mostrano le icone o lo stato di un bottone radio o check), questo potrebbe essere segnalato come un bug in un'applicazione (es.Firefox o Thunderbird). Se invece si sperimenta un difetto nelle '''azioni''' (es, ciò che succede quando si clicca una voce del menù), anche questo potrebbe essere un bug nell'applicazione. + Se si sperimenta un problema con il '''contenuto''' della barra menù, il menù o le sue voci (es. ciò che dice il testo, cosa mostrano le icone o lo stato di un bottone radio o check), questo potrebbe essere segnalato come un bug in un'applicazione (es.Firefox o Thunderbird). Se invece si sperimenta un difetto nelle '''azioni''' (es, ciò che succede quando si clicca una voce del menù o si richiama una scorciatoia), anche questo potrebbe essere un bug nell'applicazione. In generale, qualsiasi problema di '''visualizzazione''' della barra menù, menù o suoi componenti (voci o icone) è invece un bug in Unity o inerente applicazione in un diverso ambiente desktop. Alcuni esempi potrebbero essere: * Allineamento degli elementi nel menù @@ -293, +294 @@ Vedere [[http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/|http://blog.clickssl.com/2010/12/rapidssl-error-on-firefox-this-connection-is-untrusted/]] [[https://knowledge.geotrust.com/support/knowledge-base/index?page=content&actp=CROSSLINK&id=SO9557|Questo]] strumento di validazione online potrebbe riferire informazioni su chi intermedia un server. + + === Problemi nell'avvio di applicazioni esterne === From noreply at ubuntu.com Wed Oct 31 18:46:05 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 18:46:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22LibreOfficeBugWrangling=5Fit=22_?= =?utf-8?q?by_fabiomarconi?= Message-ID: <20121031184605.6914.26010@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "LibreOfficeBugWrangling_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/LibreOfficeBugWrangling_it?action=diff&rev1=5&rev2=6 Comment: update ita translation = Come fare una segnalazione = * Vi preghiamo di non segnalare bug inerenti LibreOffice senza avere prima letto questa pagina ed avere eseguito le necessarie azioni riportate in seguito. La mancata inosservanza causerà ritardi nell'indirizzamento della vostra segnalazione. + * Innanzitutto, prima di segnalare un bug, assicurarsi di avere installato tuta la suite LibreOffice onde evitare [[https://blueprints.launchpad.net/ubuntu/+spec/desktop-q-libreoffice-split|package split collateral damage]], eseguendo nel terminale: + || {{{sudo apt-get -y install libreoffice}}}|| * Vi preghiamo di segnalare tutti i vostri bug in LibreOffice eseguendo nel terminale: <
> {{{ubuntu-bug }}} <
> <
> dove è lo specifico pacchetto nel quale è stato rinvenuto il problema. Per esempio, se si ha un problema importando un documento con Writer: <
> {{{ubuntu-bug libreoffice-writer}}} - * Un semplice modello di segnalazione di bug: <
> + == Modello di segnalazione di bug == || 1) lsb_release -rd <
> <
> 2) apt-cache policy libreoffice-writer <
> <
> 3) What is expected to happen in Writer is (cosa dovrebbe succedere) . <
> <
> 4) What happened instead is...(cosa invece accade...) <
> <
> I have the following extensions installed: lo-menubar, libreoffice-nlpsolver, ... (le seguenti estensioni risultano installate: lo-menubar, libreoffice-nlpsolver,...<
> <
> WORKAROUND: Perform the following steps:...|| * Per cortesia non riportare più di un bug per ogni segnalazione. * Per cortesia evitare commenti sul tempo necessario alla riparazione, specialmente se non si sono seguiti i fondamentali passi di debugging in seguito descritti. Siate consapevoli che noi tutti vorremmo vedere i bug riparati immediatamente, ma purtroppo gli ostacoli maggiori si incontrano nella riproducibilità e chiarezza della segnalazione. @@ -41, +43 @@ === Il sistema si blocca o compare la schermata di login === * Nel caso in cui, utilizzando LibreOffice, il sistema si blocca o si riavvia la sessione si è di fronte ad un bug relativo a Xorg o al kernel. Si prega di consultare https://help.ubuntu.com/community/DebuggingSystemCrash . Inoltre, se ciò accade durante l'apertura o la lavorazione di un particolare documento, vi preghiamo di allegarlo alla segnalazione fornendo anche una dettagliata descrizione, click per click, su come riprodurre il crash. + === Possibili soluzioni === + + Provare a spostare .libreoffice e ~/.config/libreoffice. Se avete installato qualche estensione provte a rimuoverla e controllate se il proble è ancora riproducibile. Commentate il risultato di queste prove nel report. Comment on the results of performing these techniques in your report. Tenete le succitate directory a portata di mano, se spostare le directory è stato di aiuto. Lo sviluppatore potrebbe essere interesato a scoprire cosa avevano di errato. == Regressioni == * Per le regressioni, è di valido aiuto eseguire un binary bisect ("bibisect") per isolare la specifica commit che ha introdotto il bug. Per istruzioni vedere http://sweetshark.livejournal.com/7683.html . From noreply at ubuntu.com Wed Oct 31 19:50:56 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 19:50:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Chromium/Debugging=5Fit=22_by_fa?= =?utf-8?q?biomarconi?= Message-ID: <20121031195056.17215.76917@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Chromium/Debugging_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Chromium/Debugging_it Comment: italian translation New page: <> ## page was renamed from Chromium/Debug Se in caso di un crash di Chromium si vuole riportare un bug upstream, utilizzare il crashe loro [[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|modello linux]]. Includere sempre il risultato del comando: {{{ $ dpkg -l | grep chromium- }}} Sarà inoltre necessario fornire una [[https://wiki.ubuntu.com/Backtrace|backtrace]]. È possibile ottenerla utilizzando gdb con l'ausilio dei simboli di debug. == Ottenere una backtrace == I simboli di debug si installano tramite un apposito pacchetto, chiamato ''chromium-browser-dbg'' installabile come un normale pacchetto. Una volta installato, aprire il terminale ed eseguire: {{{ $ chromium-browser --debug 2>&1 | tee gdb-chromium.txt (gdb) handle SIG33 pass nostop noprint (gdb) set pagination 0 (gdb) run }}} Eseguire le operazioni per riprodurre il crash, quindi: {{{ (gdb) backtrace (gdb) thread apply all backtrace (gdb) quit }}} Nel caso la backtrace mostri molti punti interrogativi (tipo "#5 0x083949e0 in ?? ()"), significa che si necessitano ulteriori pacchetti con la simbologia di debugging. Per vedere quali librerie Chromium sta utilizzando, provare: {{{ $ ldd /usr/lib/chromium-browser/chromium-browser }}} Quindi cercare il corrispondente pacchetto -dbg o -dbgsym, vedere [[https://wiki.ubuntu.com/DebuggingProgramCrash_it#Pacchetti_contenenti_i_simboli_di_debug| come abilitarne i repository specifici]]. == Debugging dei processi figli == Siccome Chromium normalmente produce molti processi secondari (come le sandbox ed i renderers), la backtrace del processo browser potrebbe non essere utile ( a meno che non sia il processo principale a crashare). Per tracciare i processi figlio bisogna eseguire Chromium con --single-process: {{{ $ chromium-browser --debug --single-process 2>&1 | tee gdb-chromium.txt }}} Quindi procedere come spiegato con gdb. Una volta che si ritiene di avere una backtrace sufficiente (gdb-chromium.txt) allegarla al bug report. == Link esterni == * [[http://code.google.com/p/chromium/wiki/LinuxDebugging|Upstream debugging instructions]] ---- CategoryDebugging CategoryDebugging From noreply at ubuntu.com Wed Oct 31 18:10:41 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 18:10:41 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22MozillaTeam/Bugs=5Fit=22_by_fabi?= =?utf-8?q?omarconi?= Message-ID: <20121031181041.1705.11103@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "MozillaTeam/Bugs_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/MozillaTeam/Bugs_it?action=diff&rev1=25&rev2=26 Comment: update Gecko ha una funzionalità che cosente la selezione del segnalibro da un menù utilizzando la tastiera, utilizzando una funzionalità simile a type-ahead. L'altro strumento non ha questa funzionalità, quindi non può funzionare con la barra menù globale. Siete pertanto invitati a non riportare questo bug contro Firefox, perchè non è pertinente. Qesta funzionalità dovrà essere implementata nello strumento responsabile del disegno del menù. + + Vedi [[https://launchpad.net/bugs/917753|bug 917753]] === La voce "Apri con" non offre una scelta di applicazioni === From noreply at ubuntu.com Wed Oct 31 19:52:30 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 31 Oct 2012 19:52:30 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Chromium/Debugging=5Fit=22_by_fa?= =?utf-8?q?biomarconi?= Message-ID: <20121031195230.17215.88620@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Chromium/Debugging_it" page has been changed by fabiomarconi: http://wiki.ubuntu.com/Chromium/Debugging_it?action=diff&rev1=1&rev2=2 - <> ## page was renamed from Chromium/Debug Se in caso di un crash di Chromium si vuole riportare un bug upstream, utilizzare il crashe loro [[http://code.google.com/p/chromium/issues/entry?template=Defect%20on%20Linux|modello linux]]. Includere sempre il risultato del comando: