From noreply at ubuntu.com Tue Mar 1 16:25:10 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 16:25:10 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/Debugging/Backlight=22_by?= =?utf-8?q?_brian-murray?= Message-ID: <20110301162510.31119.58784@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Kernel/Debugging/Backlight?action=diff&rev1=8&rev2=9 The comment on the change is: reformat situations paragraph and add in thinkpad_apci info ------------------------------------------------------------------------------ There are a lot of different issues with backlight control which can be generally put into these classes: - * Hotkeys change the brightness, but no OSD feedback and the brightness applet does not work. This normally is not a problem in Linux. If there is no vendor specific control mechanism and the generic ACPI interface is not defined (or not defined correctly), there is no way Linux can interact. In those cases the hotkeys are directly wired to the backlight control and no events are passed on to the OS. + * Hotkeys change the brightness, but no OSD feedback and the brightness applet does not work. + * There is nothing that the kernel can do to resolve this situation. Since there is no vendor specific control mechanism and the generic ACPI interface is not defined (or not defined correctly), there is no way Linux can interact. In those cases the hotkeys are directly wired to the backlight control and no events are passed on to the OS. + * Backlight control works through the brightness applet but not via hotkeys. - * Backlight control works through the brightness applet but not via hotkeys. This is most likely a hotkey issue which might be further debugged looking at [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|debugging hotkeys]]. + * This is most likely a hotkey issue which might be further debugged looking at [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|debugging hotkeys]]. - * Backlight control does not work, but there are entries in {{{/sys/class/backlight}}}. Might require the ACPI backlight driver to not take control to give a vendor specific driver a chance to register (see below). + * Backlight control does not work, but there are entries in {{{/sys/class/backlight}}}. + * This may require the ACPI backlight driver to not take control so that a vendor specific driver will have a chance to register (see below). + * Backlight control does not work and there are no entries in {{{/sys/class/backlight}}}. - * Backlight control does not work and there are no entries in {{{/sys/class/backlight}}}. Neither the ACPI backlight driver nor any vendor specific driver were able to find a valid interface. Either requires a new vendor driver (which is unlikely) or the ACPI BIOS is broken (see below). Updates to the ACPI BIOS are rare as well but in some cases it is possible to work with upstream to extend the Linux side to handle some of that brokenness. + * Neither the ACPI backlight driver nor any vendor specific driver were able to find a valid interface. Either requires a new vendor driver (which is unlikely) or the ACPI BIOS is broken (see below). Updates to the ACPI BIOS are rare as well but in some cases it is possible to work with upstream to extend the Linux side to handle some of that brokenness. = Filing Bugs = @@ -32, +36 @@ {{{ thinkpad-acpi.brightness_enable=1 + }}} + + You can check to see if your system uses the '''thinkpad-acpi''' driver by using the following command: + + {{{ + lsmod | grep thinkpad_acpi }}} === Disabling ACPI brightness adjustments === From noreply at ubuntu.com Tue Mar 1 14:26:54 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 14:26:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20110301142654.12675.9369@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by pvillavi: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=247&rev2=248 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20110303| USB Creator]] || hugday-20110303 || || [[UbuntuBugDay/20110210| OpenOffice/LibreOffice]] || hugday-20110210 || || [[UbuntuBugDay/20110203| Rhythmbox]] || hugday-20110203 || || [[UbuntuBugDay/20110120| Pidgin]] || hugday-20110120 || From noreply at ubuntu.com Tue Mar 1 16:13:28 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 16:13:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_brian-?= =?utf-8?q?murray?= Message-ID: <20110301161328.29450.6799@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=10&rev2=11 The comment on the change is: Add in vt.handoff=7 ------------------------------------------------------------------------------ When trying to capture relevant error messages that appear at boot it is often useful to boot with the '''quiet''' and '''splash''' options removed. This will hopefully allow you to see any messages that come across your screen. To edit boot option parameters, do the following: 1. Boot the machine. - 1. During the BIOS screen, press the shift key and hold it down. You should get the GRUB menu after the BIOS loads. + 1. During the BIOS screen, press the shift key and hold it down. You should see the GRUB menu after the BIOS loads. 1. Navigate to the kernel entry you want to boot, and press 'e'. - 1. Then remove the '''quiet''' and '''splash''' keywords (found in the line starting with linux) and press 'Ctrl+x' to boot. + 1. Then remove the '''quiet''' and '''splash''' keywords (found in the line starting with linux) + 1. If running Natty (Ubuntu 11.04) also remove the parameter '''vt.handoff=7'''. + 1. Press 'Ctrl+x' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand. From brian at ubuntu.com Tue Mar 1 16:40:35 2011 From: brian at ubuntu.com (Brian Murray) Date: Tue, 1 Mar 2011 08:40:35 -0800 Subject: Kernel Team's Debugging Documentation Message-ID: <20110301164035.GH2525@murraytwins.com> The Ubuntu Kernel Team has written a fair bit of debugging documentation which can be quite helpful for us when we triage kernel bug reports. They've asked for us review the documentation, by reading and following it, so that we can help improve it by making it clearer and easier to follow. As an example I was reading the Debugging Kernel Boot and noticed that there is a new boot parameter, vt.handoff=7, in Natty that needs to be removed to see kernel boot messages. I confirmed with the kernel team by emailing their mailing list (kernel-team at lists.ubuntu.com) and then updated the page. I also noticed a couple of pages were missing the debugging category and have been adding those. If you get a chance please lend a hand. Their debugging documentation can be found at: https://wiki.ubuntu.com/Kernel/Debugging [1] https://wiki.ubuntu.com/DebuggingKernelBoot Thanks! -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Tue Mar 1 21:22:05 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 21:22:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/DebuggingSchedulingWhileA?= =?utf-8?q?tomic=22_by_brian-murray?= Message-ID: <20110301212205.898.16197@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Kernel/DebuggingSchedulingWhileAtomic?action=diff&rev1=1&rev2=2 The comment on the change is: Trace file is owned by root ------------------------------------------------------------------------------ These bugs occur typically in an interrupt context. I tried to come up with a simple description for what this means and why it's bad, but it was too cumbersome and honestly, you probably just want your bug fixed so you can get on with your life! = Debugging = - With normal kernel bugs, an !OopsText.txt log file is attached to the bug report at launchpad.net. This often contains enough information for us to get started on resolving the issue. However, the information in this log file usually is not enough for scheduling while atomic bugs. What we need in this case is called a function trace. When you are ready, perform the following to retrieve a trace: + With normal kernel bugs, an !OopsText.txt log file is attached to the bug report at Launchpad. This often contains enough information for us to get started on resolving the issue. However, the information in this log file usually is not enough for scheduling while atomic bugs. What we need in this case is called a function trace. When you are ready, perform the following to retrieve a trace: 1. Set the appropriate tracing output: {{{ @@ -21, +21 @@ 3. Do whatever you need to do to trigger the bug 4. Save the trace log: {{{ - $ bzip2 -c /sys/kernel/debug/tracing/trace > trace.bz2 + $ sudo sh -c "bzip2 -c /sys/kernel/debug/tracing/trace > trace.bz2" }}} - 5. Upload the trace.bz2 file to launchpad so a kernel developer can work on the issue + 5. Upload the trace.bz2 file to Launchpad so a kernel developer can work on the issue This should be all the information needed to begin work on a resolution for these types of bugs. The Ubuntu kernel developers sincerely appreciate your work to help us fix your issue! + ---- + CategoryDebugging From noreply at ubuntu.com Tue Mar 1 23:40:14 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 23:40:14 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspendHibernateR?= =?utf-8?q?esume=22_by_brian-murray?= Message-ID: <20110301234014.23450.6806@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume?action=diff&rev1=15&rev2=16 The comment on the change is: Removed redundant boot parameter stuff ------------------------------------------------------------------------------ Please indicate in the bug whether it worked, and if so include the contents of /proc/version_signature from that release (or the Ubuntu version number if you do not have it). - === Do you end up with flashing caps-lock or similar? === + === Do you end up with flashing Caps Lock light or similar? === - If you have flashing caps-lock lights then very likely you are experiencing a kernel panic. + If you have a flashing Caps Lock light then very likely you are experiencing a kernel panic. Please indicate that in the bug. @@ -91, +91 @@ https://help.ubuntu.com/community/EncryptedHome - Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap. It is important to note that Hibernation will not work with an encrypted swap at this time. Actually, hibernation will work just fine, but resume will fail. There are ways around this, but it involves choosing a password to use for your swap encryption, and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system. This is a known, wishlist issue that we hope to solve for Ubuntu 10.04. If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help: + Users installing from Ubuntu 9.10 and selecting the Encrypted Home option will automatically have encrypted swap space. Other users may have also ran sudo ecryptfs-setup-swap. It is important to note that Hibernation will work with an encrypted swap but resume will fail. There are ways around this, but theyinvolve choosing a password to use for your encrypted swap and entering that password every time you boot your system, and sharing that password with anyone else that might want to resume the system. This is a known, wishlist [[ https://bugs.launchpad.net/ecryptfs/+bug/432785 | issue ]] that we hope to solve. If you happen to report or triage this type of issue, please tag the bug '''encrypted-swap'''. For triagers, posting the following comment to a bug may help: {{{ - Thank you for taking the time to report this bug and helping to make Ubuntu better. It is currently a known issue that Hibernation will fail to resume due to an encrypted swap. Developers are hoping to resolve this issue for the Lucid Lynx 10.04 release. Please refer to https://help.ubuntu.com/community/EncryptedHome for more information. We will tag this bug "encrypted-swap" so that we can track this issue going forward and possibly request additional testing. Thanks in advance for your patience and cooperation. + Thank you for taking the time to report this bug and helping to make Ubuntu better. It is currently a known issue that Hibernation will fail to resume due to an encrypted swap. Please refer to https://help.ubuntu.com/community/EncryptedHome for more information. We will tag this bug "encrypted-swap" so that we can track this issue going forward and possibly request additional testing. Thanks in advance for your patience and cooperation. }}} == Hibernating from text mode == - The first step for debugging hibernate is to determine if the issue occurs when triggered using the pm-hibernate command. If possible you should reboot the system with the no_console_suspend option (see Note 1 below for help with this). You should then switch to VT1 by pressing Ctrl-Alt-F1. Login at the prompt there and then run the following commands: + The first step for debugging hibernate is to determine if the issue occurs when triggered using the pm-hibernate command. If possible you should reboot the system with the '''no_console_suspend''' boot parameter. See DebuggingKernelBoot for instructions on how to modify boot parameters. You should then switch to VT1 by pressing Ctrl-Alt-F1. Login at the prompt there and then run the following commands: {{{ setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz @@ -162, +162 @@ = Notes = - == Note 1: adding and removing options to the kernel command line == - - Assuming you are using the default boot loader {{{grub}}} you will very likely see the text below straight after the BIOS messages: - - {{{ - GRUB loading stage 1.5. - - GRUB loading, please wait ... - Press 'ESC' to enter the menu ... - }}} - - If you see this you should hit ESC to enter the kernel selection menu. In some cases GRUB will enter the menu directly, in either case you will see something like this: - - {{{ - +-------------------------------------------------------------+ - | Ubuntu jaunty (stable), kernel 2.6.28-11-generic | - | Ubuntu jaunty (stable), kernel 2.6.28-11-generic (recovery) | - | Ubuntu jaunty (stable), kernel 2.6.28-8-generic | - | Ubuntu jaunty (stable), kernel 2.6.28-8-generic (recovery) | - | Ubuntu jaunty (stable), memtest86+ | - +-------------------------------------------------------------+ - Use the ^ and v keys to select which entry is highlighted. - Press enter to boot the selected OS, 'e' to edit the - commands before booting, or 'c' for a command line. - }}} - - At this point you should use the up and down cursor keys to select the kernel you normally use (if you do not know leave the cursor where it is). Next hit 'e' to edit the line. You will then see something similar to this: - - {{{ - +-------------------------------------------------------------+ - | uuid 123456789012345678901234567890 | - | kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=12345678> | - | initrd /boot/initrd.img-2.6.28-11-generic | - | quiet | - ... - }}} - - At this point you should cursor down until the line which starts kernel is highlighted, and hit 'e' to edit it. You will then see something like this: - - {{{ - [ Minimal BASH-like line editing is supported. For - the first word, TAB lists possible command - completions. Anywhere else TAB lists the possible - completions of a device/filename. ESC at any time - exits. ] - - <123456789 ro quiet splash _ - }}} - - You can now cursor about in the line using left and right arrows, use delete to remove things you have been asked to get rid of and simply add new options at the end ensuring there is a space between each option. If you make a mistake you can abort all edits with ESC. When you are happy with the new options, hit Return, and then 'b' to boot the system. - == Battery drained whilst suspended stock reply == {{{ Thank you for taking the time to report this bug and helping to make Ubuntu better. This report seems to indicate that your battery drained while the machine was suspended. In this case a false bug report is generated, we are therefore closing this bug Invald. Please see https://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume#Is%20this%20really%20a%20failure? for more information. }}} * Set status to Incomplete ---- - CategoryKernel + CategoryKernel CategoryDebugging From noreply at ubuntu.com Tue Mar 1 21:46:58 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 21:46:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_bri?= =?utf-8?q?an-murray?= Message-ID: <20110301214658.14052.7263@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=33&rev2=34 ------------------------------------------------------------------------------ This page describes how to debug Suspend to RAM/Resume problems on your computer. Do not confuse this with Suspend to disk (also known as hibernate). [[UnderstandingSuspend]] may have useful background information on where problems can occur. - Suspend and Resume use facilities within your BIOS called ACPI, or Advanced Configuration and Power Interface. Linux provides an ACPI subsystem that manages the suspend and resume process. The usual problem occurs when resuming, and normally the culprit is a device driver that does not recover from a powered down state. If your computer successfully performs a suspend, then it is quite likely any resume problems are due to another device driver and not the ACPI subsystem. + Suspend and Resume use facilities within your BIOS called ACPI, or Advanced Configuration and Power Interface. Linux provides an ACPI subsystem that manages the suspend and resume process. Usually problems occur when resuming, and normally the culprit is a device driver that does not recover from a powered down state. If your computer successfully performs a suspend, then it is quite likely any resume problems are due to another device driver and not the ACPI subsystem. - The debugging procedure described below requires a linux kernel 2.6.20 (and newer) for the ability of "/sys/power/pm_trace". FeistyFawn and later release have a new enough kernel version. You can check the version of the kernel you are running by {{{uname -r}}} from a terminal. You can also just look in the directory /sys/power/ (from a terminal type {{{ls /sys/power/}}}) - to see if a file called pm_trace exists; it will only do so if the kernel supports the following debugging procedure. + 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. = "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 it 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. - Caveat Emptor: Using the following debug suggestions will radically change the values in your RTC chip, so much so that your file system will think it has been eons since the last fsck. You can avoid a long fsck delay by using 'tune2fs'. For example, 'tune2fs -i 0 /dev/sda1' disables fsck on boot. But first you'll want to use 'tune2fs -l ' to get the current information of your settings - look at the "Check interval" setting. + 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. + Caveat Emptor: Using the following debug suggestions will radically change the values in your RTC chip, so much so that your file system will think it has been eons since the last fsck. You can avoid a long fsck delay by using 'tune2fs'. For example, 'tune2fs -i 0 /dev/sda1' disables fsck on boot. But first you'll want to use 'tune2fs -l ' to find your current settings - look at the "Check interval" setting. + - From a fresh Hardy install, the default time interval is 15552000, which is 6 months. + From a fresh install, the default time interval is 15552000, which is 6 months. Remember that when you are all done, you'll want to set your RTC clock back. Note that NTP by itself is not sufficient to recover the correct time of day, since by default NTP is configured to do nothing if the time is off by more than 1000 seconds. You must first use the 'ntpdate' or 'date' command to get the clock close. @@ -35, +36 @@ dmesg > dmesg.txt }}} - You can edit this file and find line similar to these: + You can edit this file and find lines similar to these: {{{ [ 11.323206] Magic number: 0:798:264 From noreply at ubuntu.com Tue Mar 1 23:55:09 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 01 Mar 2011 23:55:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspendHibernateR?= =?utf-8?q?esume=22_by_brian-murray?= Message-ID: <20110301235509.29924.27823@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelSuspendHibernateResume?action=diff&rev1=16&rev2=17 ------------------------------------------------------------------------------ For resume from Hibernate failures, please include the output from the following commands from the boot following the hibernate, this includes information on the search for the resume device etc: 1. {{{dmesg}}} - 2. {{{cat /proc/cmdline}}} + 1. {{{cat /proc/cmdline}}} - 3. {{{cat /etc/initramfs-tools/conf.d/resume}}} + 1. {{{cat /etc/initramfs-tools/conf.d/resume}}} === Other information === - Please include any information as to the circumstances leading up to this failure, anything unsual for example did your battery run out? Did any messages come out? + Please include any information as to the circumstances leading up to this failure, anything unusual for example did you see any eror messages? = Debugging Suspend = == Suspending from text mode == - The first step for debugging suspend is to determine if the issue occurs when triggered using the pm-suspend command. If possible you should reboot the system with the no_console_suspend option (see Note 1 below for help with this). You should then switch to VT1 by pressing Ctrl-Alt-F1. Login at the prompt there and then run the following commands: + The first step for debugging suspend is to determine if the issue occurs when triggered using the pm-suspend command. If possible you should reboot the system with the '''no_console_suspend''' boot parameter. See DebuggingKernelBoot for instructions on how to modify boot parameters. You should then switch to VT1 by pressing Ctrl-Alt-F1. Login at the prompt there and run the following commands: - {{{ + {{{ setfont /usr/share/consolefonts/Uni1-VGA8.psf.gz sudo pm-suspend }}} - This will select a much smaller font so that you can see more messages should they come out, and then initate the suspend. + This will select a much smaller font so that you can see more messages should they come out, and then initiate the suspend. Please report whether you got any additional messages. Digital photos of the screen are a sensible way to get this into the bug. From kamusin at gmail.com Wed Mar 2 18:21:33 2011 From: kamusin at gmail.com (Kamus) Date: Wed, 2 Mar 2011 15:21:33 -0300 Subject: Announcing the Next Ubuntu Bug Day! March 3rd 2011 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day targets are *drum roll please* usb-creator! * 56 New bugs need a hug * 2 Incomplete bugs need a status check * 42 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * 03 March 2011 * https://wiki.ubuntu.com/UbuntuBugDay/20110303 Are you looking for a way to start giving some love back to your adorable Ubuntu Project? Did you ever wonder what Triage is? Want to learn about that? This is a perfect time!, Everybody can help in a Bug Day! open your IRC Client and go to #ubuntu-bugs (FreeNode) the BugSquad will be happy to help you to start contributing! Wanna be famous? Is easy! remember to use 5-A-day so if you do a good work your name could be listed at the top 5-A-Day Contributors in the Ubuntu Hall of Fame page! We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the Planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [from bugsquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile From brian at ubuntu.com Wed Mar 2 21:06:01 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 2 Mar 2011 13:06:01 -0800 Subject: Audio Apport Symptom Message-ID: <20110302210601.GP2525@murraytwins.com> I was just testing 'ubuntu-bug audio', which uses the audio apport symptom, and was really impressed by the questions it asked and how it identified the jacks on my systems. The symptom seems to have recently received quite a rewrite and is worth checking out but don't submit a bug if you aren't encountering one! And of course reviewing alsa-driver bug reports regarding Natty and having people submit a new bug (if there's is rather incomplete) would be a good idea too. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Mar 2 18:25:57 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 02 Mar 2011 18:25:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelOops=22_by_brian-?= =?utf-8?q?murray?= Message-ID: <20110302182557.21342.70719@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelOops?action=diff&rev1=8&rev2=9 The comment on the change is: Reworking Tainted section ------------------------------------------------------------------------------ EIP: 0060:[] Not tainted VLI }}} + ==== Tainted Kernels ==== + - This is also a good time to mention Tainted Kernels. Some Oops reports contain the string 'Tainted: ' after the EIP. This indicates that the kernel has been tainted by some mechanism. The string is followed by a series of position-sensitive characters, each representing a particular tainted value. + This is also a good time to mention Tainted Kernels. Some Oops reports contain the string 'Tainted: ' after the EIP. This indicates that the kernel has been tainted by some mechanism. 'Tainted: ' is followed by a series of position-sensitive characters, each representing a particular tainted value. If the letter does not appear the kernel is not tainted in that fashion. 1. 'G' if all modules loaded have a GPL or compatible license 1. 'P' if any proprietary module has been loaded. Modules without a MODULE_LICENSE or with a MODULE_LICENSE that is not recognised by insmod as GPL compatible are assumed to be proprietary. - 1. 'F' if any module was force loaded by "insmod -f", ' ' if all modules were loaded normally. + 1. 'F' if any module was force loaded by "insmod -f". 1. 'S' if the Oops occurred on an SMP kernel running on hardware that hasn't been certified as safe to run multiprocessor. Currently this occurs only on various Athlons that are not SMP capable. - 1. 'R' if a module was force unloaded by "rmmod -f", ' ' if all modules were unloaded normally. + 1. 'R' if a module was force unloaded by "rmmod -f". - 1. 'M' if any processor has reported a Machine Check Exception, ' ' if no Machine Check Exceptions have occurred. + 1. 'M' if any processor has reported a Machine Check Exception. 1. 'B' if a page-release function has found a bad page reference or some unexpected page flags. - 1. 'U' if a user or user application specifically requested that the Tainted flag be set, ' ' otherwise. + 1. 'U' if a user or user application specifically requested that the Tainted flag be set. 1. 'D' if the kernel has died recently, i.e. there was an OOPS or BUG. + 1. 'W' if a warning has previously been issued by the kernel. + + 1. 'C' if a staging module / driver has been loaded. + + 1. 'I' if the kernel is working around a sever bug in the platform's firmware (BIOS or similar). + + An example output of a tainted line: + + {{{ + [187487.973317] Pid: 810, comm: iwl3945 Tainted: P M 2.6.35-22-generic #33-Ubuntu + }}} + The primary reason for the 'Tainted: ' string is to tell kernel debuggers if this is a clean kernel or if anything unusual has occurred. Tainting is permanent: even if an offending module is unloaded, the tainted value remains to indicate that the kernel is not trustworthy. + + ==== Call Stack Details ==== {{{ Stack: 00000000 00000000 d0b97e60 00008080 c01c4390 d0b97e60 00000000 00000000 @@ -112, +128 @@ Sometimes you'll need to derive even more information from the Call Stack. This trace shows you how you got to where the code broke. You'll notice that '''[thinkpad_acpi]''' trails some of the Call Trace output. This indicates the module for which the code of the calling routine resides in. This is often helpful in narrowing down which module contains the issue. == Submitting a Kernel Oops Bug Report == - Learning to debug and fix a kernel Oops is not an easy task for the average user. However, any user should be able to gather the appropriate information to help the kernel team debug and fix the issue. If you ever witness a kernel Oops please file a launchpad bug report. The following steps help guide you through this reporting process: + Learning to debug and fix a kernel Oops is not an easy task for the average user. However, any user should be able to gather the appropriate information to help the kernel team debug and fix the issue. If you ever witness a kernel Oops please file a linux bug report in Launchpad. The following steps help guide you through this reporting process: 1. Search to see if someone else has already reported this issue. However, make sure you are experiencing the _same_ Oops (ie Call Trace looks the same, EIP is at the same location, you have similar hardware, you use the same steps to reproduce the Oops, etc.) * If you are convinced the report is the same, please add any further useful information to the existing bug report. It will also help if you subscribe youself to that report so you are notified of any updates regarding the bug. * If the report is not the same Oops you are experiencing, please proceed to Step 2. - 1. Make sure the report is filed against the proper package. For a kernel Oops this will typically be 'linux-source-2.6.xx' or just 'linux'. + 1. Make sure the report is filed against the proper package. For a kernel Oops this will be 'linux'. 1. Please be sure to tag your report as 'kernel-oops'. This can be done be clicking on the "Edit description/tags" link and entering the tag 'kernel-oops' into the Tags field. - 1. Please provide a descriptive Subject for your bug + 1. Please provide a descriptive Subject / Title for your bug. * BAD example - "Kernel Oops" * GOOD example - "Kernel Oops - unable to handle kernel NULL pointer dereference; EIP is at acpi_ns_internalize_name+0xd/0x83" 1. Please provide the kernel team as much information as possible: * If you are able to consistently trigger the kernel Oops, please document the exact steps to reproduce it. * Capture the full output of the kernel Oops as well as any output that leads up to the kernel Oops. This can usually be found in the dmesg output. * {{{ dmesg > dmesg.log }}} - * attach this file to the bug report + * attach dmesg.log to the bug report * Also attach the following information: * {{{ uname -a > uname-a.log }}} * {{{ cat /proc/version_signature > version.log }}} From noreply at ubuntu.com Wed Mar 2 22:38:44 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 02 Mar 2011 22:38:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSoundProblems=22_by_bri?= =?utf-8?q?an-murray?= Message-ID: <20110302223844.6072.69529@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingSoundProblems?action=diff&rev1=64&rev2=65 The comment on the change is: Fixing the FIX ME because I'm a fixer yeah! ------------------------------------------------------------------------------ * {{{ options snd slots=,snd-usb-audio }}} - The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth. In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device. For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Rhythmbox, but your other applications will play through your other soundcard. FIXME PLEASE: for more information go to the ALSA-Configuration kernel document. + The index numbers (0, 1, ... 7) signify the priority of the device, with the highest priority device being 0, then 1, and so forth. In theory, applications should first attempt to use the highest priority device first, but if for some reason the application is unable to use the device, it will use the next highest priority device. For example, if you have a USB sound card that can get picked up with OSS, which browsers, flash, and skype may not output, if you set your USB card at first priority, it will play when using, say, Rhythmbox, but your other applications will play through your other soundcard. For more information see Documentation/sound/alsa/ALSA-Configuration.txt in the kernel source. == Checking permissions and resources == From noreply at ubuntu.com Wed Mar 2 22:48:48 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 02 Mar 2011 22:48:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingACPI=22_by_brian-murray?= Message-ID: <20110302224848.12605.39884@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingACPI?action=diff&rev1=29&rev2=30 ------------------------------------------------------------------------------ = Debugging procedure = - (See [[http://www.lesswatts.org/projects/acpi/debug.php|LessWatts.org]] for more information.) + (See [[http://www.lesswatts.org/projects/acpi/debug.php|LessWatts.org]] for more information regarding ACPI debugging in general.) 1. Make sure your BIOS is up to date. * To find the version of the BIOS you currently have, run {{{sudo dmidecode}}}. The version of your BIOS should be listed in the BIOS Information section of the output. + * Check to see if your hardware's manufacturer has provided a newer BIOS version. === Trouble Booting === From noreply at ubuntu.com Wed Mar 2 16:29:46 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 02 Mar 2011 16:29:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110302162946.21125.7183@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=30&rev2=31 ------------------------------------------------------------------------------ == Design Bugs == - Some bugs are not technical defects, but behavioral, or visual ones. These often require input from the design team before they can be fixed. When a bug is determined to be a design bug, it should have an ''Ayatana design'' task added to it, and its Unity status should be set to ''opinion''. After a design decision has been reached the Unity status should be set to ''triaged'' as there is then enough information for the bug to be fixed. See also the ''Blocked waiting for design decision'' canned response. + Some bugs are not technical defects, but behavioral, or visual ones. These often require input from the design team before they can be fixed. When a bug is determined to be a design bug, it should have an ''Ayatana design'' task added to it, and its Unity status should be set to ''incomplete'' with the tag ''needs-design''. After a design decision has been reached the Unity status should be set to ''triaged'' as there is then enough information for the bug to be fixed. See also the ''Blocked waiting for design decision'' canned response. An example (real world) design bug: [[https://bugs.launchpad.net/unity/+bug/649560]] == Canned Responses == || '''Situation''' || '''Response''' || '''Note''' || || Patch needs author to sign Canonical Contributer agreement || Looks good but before we merge it we need you to sign the Canonical contributer agreement. It's a quick, but necessary step to getting your code into the tree. Luckily you only need to sign it once and it will apply to all other Canonical project contributions you may make in the future. http://www.canonical.com/contributors Make sure to CC David Barth when you send it in. || || - || Blocked waiting for design decision || This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward. || Mark status as ''opinion'' until design gives feedback || + || Blocked waiting for design decision || This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward. || Mark status as ''incomplete'', and tag ''needs-design'' until design gives feedback. || || Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to invalid, and let the user reopen it || = Bug Tags = From noreply at ubuntu.com Wed Mar 2 19:03:43 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 02 Mar 2011 19:03:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_gruemaster?= Message-ID: <20110302190343.6097.45554@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by gruemaster: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=171&rev2=172 ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=macbookpro|`macbookpro`]] || These bugs deal with Mac Book Pro systems || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ps3|`ps3`]] || Some bug reports are about people running Ubuntu on a Playstation 3 || || [[https://launchpad.net/ubuntu/+bugs?field.tag=ume|`ume`]] || These bugs deal with Ubuntu Mobile and Embeded systems || - + || [[https://launchpad.net/ubuntu/+bugs?field.tag=armel|`armel`]] || These bugs deal with Ubuntu arm systems || === Historical Tags === These tags were relevant previously for Ubuntu bugs and may still appear in some bugs. The needs retracing tags are added automatically for Gutsy. From noreply at ubuntu.com Thu Mar 3 18:28:30 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 03 Mar 2011 18:28:30 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingACPI=22_by_brian-murray?= Message-ID: <20110303182830.10686.58469@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingACPI?action=diff&rev1=30&rev2=31 ------------------------------------------------------------------------------ === Trouble Booting === + For detailed instructions regarding how to modify boot parameters see DebuggingKernelBoot. - {{{sudo cp /boot/grub/menu.lst /boot/grub/menu.lst.bck}}} - - {{{sudo gedit /boot/grub/menu.lst}}} 1. Try booting with the "acpi=off" kernel parameter - * This will disable ACPI support. If the error is the same with acpi enabled and disabled, this may not be an ACPI issue. + * This will disable ACPI support. If the error is the same with ACPI enabled and disabled, this may not be an ACPI issue. 1. If "acpi=off" allows the system to boot, try to isolate the ACPI issue with the following boot parameters * Try booting with "acpi=ht" * This disables all of ACPI except just enough to enable Hyper Threading. If acpi=off works and acpi=ht fails, then the issue is in the ACPI table parsing code itself, or perhaps the SMP code. @@ -35, +33 @@ * Try booting with "noapic" * Disables the IO-APIC for IRQ routing or PCI scanning. * Try booting with "nolapic" - * Disables the local APIC + * Disables the local APIC. === Fan Issues === - These usually relate to the fan spinning too much or too fast. Another indication may be that the temperature remains high even when the fans are spinning. + These usually relate to the fan spinning too often or too fast. Another indication may be that the temperature remains high even when the fans are spinning. 1. Determine if the system has ACPI-based fan control * if /proc/acpi/fan is empty and /proc/acpi/thermal_zone/*/trip_points has no active trip points (those starting with "AC") then there is no ACPI-based fan control on your system @@ -51, +49 @@ * Output of {{{uname -a}}} * Output of {{{sudo lspci -vvnn}}} - * Output of {{{sudo dmidecode}}} + * Output of {{{sudo dmidecode > dmidecode.txt }}} * Try to hibernate/suspend and then restart the system and attach {{{/var/log/kern.log.0}}} * Tarball of /proc/acpi directory. You can't just tar all files because their content sometimes changes etc. * {{{cp -r /proc/acpi /tmp}}} * {{{tar -cvjf ~/acpi.tar.bz /tmp/acpi}}} - Such bugs should be reported against the appropriate linux-source-2.6.xx package. For example, the correct package in Malone for Dapper is linux-source-2.6.15, for Feisty it is linux-source-2.6.20 and for Gutsy it is linux-source-2.6.22, for Hardy it is just linux. + Such bugs should be reported against the linux package. Sometimes, everything works except resume (that is, all ACPI functions work, the user can hibernate and restart their computer, etc.). In this case, the DebuggingKernelSuspend procedure can be useful. UnderstandingSuspend can also provide some useful information. From noreply at ubuntu.com Thu Mar 3 18:36:38 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 03 Mar 2011 18:36:38 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingACPI=22_by_brian-murray?= Message-ID: <20110303183638.19019.87359@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingACPI?action=diff&rev1=31&rev2=32 ------------------------------------------------------------------------------ These usually relate to the fan spinning too often or too fast. Another indication may be that the temperature remains high even when the fans are spinning. 1. Determine if the system has ACPI-based fan control - * if /proc/acpi/fan is empty and /proc/acpi/thermal_zone/*/trip_points has no active trip points (those starting with "AC") then there is no ACPI-based fan control on your system + * if '''/proc/acpi/fan''' is empty and '''/proc/acpi/thermal_zone/*/trip_points''' has no active trip points (those starting with "AC") then there is no ACPI-based fan control on your system 1. If the system does have an ACPI-based fan control try booting with kernel parameter options listed above = Filing a Bug Report = From noreply at ubuntu.com Sun Mar 6 05:12:02 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 06 Mar 2011 05:12:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_jeanaustinr?= Message-ID: <20110306051202.2961.39127@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jeanaustinr: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=320&rev2=321 The comment on the change is: changed "We appreciate the difficulties you are facing" to "We understand the difficulties you are facing" under the response for A Support Request. ------------------------------------------------------------------------------ Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems. - || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We appreciate the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .|| + || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .|| It is also a good idea to change the source package beforehand if it's set incorrectly, so that the question will be associated with the correct package in the answer tracker, or edit the question afterwards and assign it to the correct package. If it doesn't pertain to a specific package, change it to "Ubuntu". From noreply at ubuntu.com Sun Mar 6 11:35:43 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 06 Mar 2011 11:35:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_mdke?= Message-ID: <20110306113543.9943.6127@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by mdke: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=31&rev2=32 The comment on the change is: add link to Ayatana Design bug page ------------------------------------------------------------------------------ Because Unity is a user interface, all bugs that relate to user facing functionality need to be reported to the [[http://design.canonical.com/|Unity design team]]. To report a user facing bug: - * Report the bug against the 'Ayatana Design' project (NOT the 'Unity' project) + * Report the bug against the [[https://bugs.launchpad.net/ayatana-design|Ayatana Design]] project (NOT the 'Unity' project) * Set the importance as you see fit * If the bug is urgent ping JohnLea on #ayatana on freenode. From jeremy.foshee at canonical.com Mon Mar 7 17:06:58 2011 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Mon, 7 Mar 2011 12:06:58 -0500 Subject: Kernel Bug Day Tuesday, 8 March 2011 Message-ID: <20110307170658.GA2456@nightcrawler> Hi Folks! We are near another Kernel Bug Day [0]. Tomorrow we will be working once again on bugs in the new state. My goal is for us to get as many of these in the correct status with the proper level of information. I'd like for us to perform the basic triage along with any additional steps as needed. A few of the additional steps are outlined in the kernel bug day pages [1]. I've announced on the kernel voices blog, but if you know anyone who may be interested, please feel free to forward this along or provide them the link to the post [2]. Thank you all for your help in the past. I am looking forward to yet another successful Kernel Bug Day!. :-) ~JFo [0] https://wiki.ubuntu.com/Kernel/BugTriage/BugDay [1] https://wiki.ubuntu.com/Kernel/BugTriage/Process [2] http://voices.canonical.com/kernelteam/?p=6208 From noreply at ubuntu.com Wed Mar 9 12:41:40 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 09 Mar 2011 12:41:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_jeanaustinr?= Message-ID: <20110309124140.18970.38882@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jeanaustinr: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=321&rev2=322 ------------------------------------------------------------------------------ Determining whether a bug report is actually a support request can be quite challenging, but if you decide the bug is a support request you can convert it to such by clicking "Convert to a question" at the top of the bug's web page. This will mark the bug as "Invalid", create a new question in the answer tracker and link it to the bug. In the comment dialog that you receive, post a comment to inform the reporter about your action, and advise them to use the support tracker for any future problems. - || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs .|| + || Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it would make more sense to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs.|| It is also a good idea to change the source package beforehand if it's set incorrectly, so that the question will be associated with the correct package in the answer tracker, or edit the question afterwards and assign it to the correct package. If it doesn't pertain to a specific package, change it to "Ubuntu". From noreply at ubuntu.com Wed Mar 9 15:32:29 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 09 Mar 2011 15:32:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110309153229.28910.24414@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=32&rev2=33 ------------------------------------------------------------------------------ ... (gdb) set logging file 'unity.log' + (gdb) set logging on + (gdb) b _exit + Function "_exit" not defined. + Make breakpoint pending on future shared library load? (y or [n]) + [Answer yes (y)] + (gdb) run [ and when compiz/unity crash, do...] From jonathan at ubuntu.com Wed Mar 9 17:54:13 2011 From: jonathan at ubuntu.com (Jonathan Carter (highvoltage)) Date: Wed, 09 Mar 2011 12:54:13 -0500 Subject: Edubuntu Bug Hug Day Message-ID: <4D77BEC5.2020608@ubuntu.com> Hi Bugsquashers! Tomorrow is the Bug day for... Edubuntu! The announcement from the Edubuntu website is right here: http://edubuntu.org/2011-02-23/edubuntu-bug-day-10-march List of bugs currently tracked in Edubuntu: https://bugs.edge.launchpad.net/~edubuntu-bugs/+packagebugs You do not need to be using Edubuntu in order to test or fix issues, since Edubuntu and Ubuntu shares the same package archives. You could install any Edubuntu related package in Ubuntu to test a package or file a bug. Find us in #ubuntu-bugs and #edubuntu tomorrow, most of the Edubuntu folk are in a US'ish timezone so if you're from a European timezone, you might have to start without us or join us when it's afternoon :) (either is fine) Thanks for your support! -Jonathan From noreply at ubuntu.com Thu Mar 10 02:35:48 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 10 Mar 2011 02:35:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_brian-?= =?utf-8?q?murray?= Message-ID: <20110310023548.12962.75362@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=11&rev2=12 ------------------------------------------------------------------------------ Additionally, being able to extract log files from the system would be helpful. Once dropped into an initramfs shell, you can type '''httpd'''. You should then be able to point a web browser to the IP address of the system and view the contents of /var/log . - There is another initramfs boot parameter which can purposely drop you into the initramfs shell during different stages of the initial boot sequence. The parameter is '''break=[option]''' where option can be: top, modules, premount, mount, bottom, or init. The default is premount if no options are specified. + There is another initramfs boot parameter which can purposely drop you into the initramfs shell during different stages of the initial boot sequence. The parameter is '''break=[option]''' where option can be: top, modules, premount, mount, bottom, or init. The default is premount if no options are specified. More information about the break= parameters can be found in "/usr/share/initramfs-tools/init" on your Ubuntu system. ---- CategoryBugSquad CategoryDebugging From glory.praise at gmail.com Thu Mar 10 15:10:03 2011 From: glory.praise at gmail.com (=?windows-1256?B?IMPjzM8=?=) Date: Thu, 10 Mar 2011 17:10:03 +0200 Subject: Problem while opening kmail Message-ID: Greetings.. Everytime I open my kmail i get an error with the following content. So I saved it and here I'm sending it. I hope you can help Regards -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- Akonadi Server Self-Test Report =============================== Test 1: SUCCESS -------- Database driver found. Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi server configuration and was found on your system. File content of '/home/vostro/.config/akonadi/akonadiserverrc': [QMYSQL] Name=akonadi Host= Options="UNIX_SOCKET=/home/vostro/.local/share/akonadi/socket-vostro-pc/mysql.socket" ServerPath=/usr/sbin/mysqld-akonadi StartServer=true [Debug] Tracer=null [%General] Driver=QMYSQL Test 2: SUCCESS -------- Akonadi is not running as root Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system. Test 3: SUCCESS -------- MySQL server found. Details: You have currently configured Akonadi to use the MySQL server '/usr/sbin/mysqld-akonadi'. Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called 'mysqld'; its location varies depending on the distribution. Test 4: SUCCESS -------- MySQL server is executable. Details: MySQL server found: /usr/sbin/mysqld-akonadi Ver 5.1.49-1ubuntu8.1 for debian-linux-gnu on x86_64 ((Ubuntu)) Test 5: SUCCESS -------- MySQL server log contains no errors. Details: The MySQL server log file '/home/vostro/.local/share/akonadi/db_data/mysql.err' does not contain any errors or warnings. File content of '/home/vostro/.local/share/akonadi/db_data/mysql.err': 110307 8:23:12 [Note] Plugin 'FEDERATED' is disabled. 110307 8:23:13 InnoDB: Started; log sequence number 0 362308 110307 8:23:13 [Note] /usr/sbin/mysqld-akonadi: ready for connections. Version: '5.1.49-1ubuntu8.1' socket: '/home/vostro/.local/share/akonadi/socket-vostro-pc/mysql.socket' port: 0 (Ubuntu) Test 6: SUCCESS -------- MySQL server default configuration found. Details: The default configuration for the MySQL server was found and is readable at /etc/akonadi/mysql-global.conf. File content of '/etc/akonadi/mysql-global.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=utf8 collation_server=utf8_general_ci table_cache=200 thread_cache_size=3 #log_bin=mysql-bin #expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=1296000 [client] default-character-set=utf8 Test 7: SKIP -------- MySQL server custom configuration not available. Details: The custom configuration for the MySQL server was not found but is optional. Test 8: SUCCESS -------- MySQL server configuration is usable. Details: The MySQL server configuration was found at /home/vostro/.local/share/akonadi/mysql.conf and is readable. File content of '/home/vostro/.local/share/akonadi/mysql.conf': # # Global Akonadi MySQL server settings, # These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf # # Based on advice by Kris Köhntopp # [mysqld] skip_grant_tables skip_networking # strict query parsing/interpretation # TODO: make Akonadi work with those settings enabled #sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat #sql_mode=strict_trans_tables # use InnoDB for transactions and better crash recovery default_storage_engine=innodb # case-insensitive table names, avoids trouble on windows lower_case_table_names=1 character_set_server=utf8 collation_server=utf8_general_ci table_cache=200 thread_cache_size=3 #log_bin=mysql-bin #expire_logs_days=3 #sync_bin_log=0 # error log file name, relative to datadir log_error=mysql.err log_warnings=2 # log all queries, useful for debugging but generates an enormous amount of data #log=mysql.full # log queries slower than n seconds, log file name relative to datadir (for debugging only) #log_slow_queries=mysql.slow #long_query_time=1 # log queries not using indices, debug only, disable for production use #log_queries_not_using_indexes=1 # maximum blob size max_allowed_packet=32M max_connections=256 # makes sense when having the same query multiple times # makes no sense with prepared statements and/or transactions query_cache_type=0 query_cache_size=0 innodb_file_per_table=1 innodb_log_buffer_size=1M innodb_additional_mem_pool_size=1M # messure database size and adjust # SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema"); innodb_buffer_pool_size=80M # size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables) innodb_log_file_size=64M innodb_flush_log_at_trx_commit=2 # Do not drop the connection to the DB after 8 hours of inactivity wait_timeout=1296000 [client] default-character-set=utf8 Test 9: SUCCESS -------- akonadictl found and usable Details: The program '/usr/bin/akonadictl' to control the Akonadi server was found and could be executed successfully. Result: Akonadi 1.5.0 Test 10: SUCCESS -------- Akonadi control process registered at D-Bus. Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational. Test 11: SUCCESS -------- Akonadi server process registered at D-Bus. Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational. Test 12: ERROR -------- Nepomuk search service not registered at D-Bus. Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup. Test 13: SKIP -------- Protocol version check not possible. Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements. Test 14: SUCCESS -------- Resource agents found. Details: At least one resource agent has been found. Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Directory listing of '/usr/share/akonadi/agents': birthdaysresource.desktop contactsresource.desktop icalresource.desktop imapresource.desktop kabcresource.desktop kcalresource.desktop knutresource.desktop kolabproxyresource.desktop localbookmarksresource.desktop maildirresource.desktop maildispatcheragent.desktop mboxresource.desktop microblog.desktop mtdummyresource.desktop nepomukcalendarfeeder.desktop nepomukcontactfeeder.desktop nepomuktagresource.desktop nntpresource.desktop notesresource.desktop pop3resource.desktop vcarddirresource.desktop vcardresource.desktop Environment variable XDG_DATA_DIRS is set to '/usr/share:/usr/share:/usr/local/share' Test 15: SUCCESS -------- No current Akonadi server error log found. Details: The Akonadi server did not report any errors during its current startup. Test 16: ERROR -------- Previous Akonadi server error log found. Details: The Akonadi server reported errors during its previous startup. The log can be found in /home/vostro/.local/share/akonadi/akonadiserver.error.old. File content of '/home/vostro/.local/share/akonadi/akonadiserver.error.old': D-Bus session bus went down - quitting Database error: Cannot open database. Last driver error: "QMYSQL: Unable to connect" Last database error: "Lost connection to MySQL server at 'reading initial communication packet', system error: 104" Test 17: ERROR -------- Current Akonadi control error log found. Details: The Akonadi control process reported errors during its current startup. The log can be found in /home/vostro/.local/share/akonadi/akonadi_control.error. File content of '/home/vostro/.local/share/akonadi/akonadi_control.error': void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_birthdays_resource" from file "/usr/share/akonadi/agents/birthdaysresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_contacts_resource" from file "/usr/share/akonadi/agents/contactsresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_ical_resource" from file "/usr/share/akonadi/agents/icalresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_imap_resource" from file "/usr/share/akonadi/agents/imapresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kabc_resource" from file "/usr/share/akonadi/agents/kabcresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kcal_resource" from file "/usr/share/akonadi/agents/kcalresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_knut_resource" from file "/usr/share/akonadi/agents/knutresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kolabproxy_resource" from file "/usr/share/akonadi/agents/kolabproxyresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_localbookmarks_resource" from file "/usr/share/akonadi/agents/localbookmarksresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_maildir_resource" from file "/usr/share/akonadi/agents/maildirresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_maildispatcher_agent" from file "/usr/share/akonadi/agents/maildispatcheragent.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_mbox_resource" from file "/usr/share/akonadi/agents/mboxresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_microblog_resource" from file "/usr/share/akonadi/agents/microblog.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_mailtransport_dummy_resource" from file "/usr/share/akonadi/agents/mtdummyresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuk_calendar_feeder" from file "/usr/share/akonadi/agents/nepomukcalendarfeeder.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuk_contact_feeder" from file "/usr/share/akonadi/agents/nepomukcontactfeeder.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuktag_resource" from file "/usr/share/akonadi/agents/nepomuktagresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nntp_resource" from file "/usr/share/akonadi/agents/nntpresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_notes_resource" from file "/usr/share/akonadi/agents/notesresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_pop3_resource" from file "/usr/share/akonadi/agents/pop3resource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_vcarddir_resource" from file "/usr/share/akonadi/agents/vcarddirresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_vcard_resource" from file "/usr/share/akonadi/agents/vcardresource.desktop" Test 18: ERROR -------- Previous Akonadi control error log found. Details: The Akonadi control process reported errors during its previous startup. The log can be found in /home/vostro/.local/share/akonadi/akonadi_control.error.old. File content of '/home/vostro/.local/share/akonadi/akonadi_control.error.old': void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_birthdays_resource" from file "/usr/share/akonadi/agents/birthdaysresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_contacts_resource" from file "/usr/share/akonadi/agents/contactsresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_ical_resource" from file "/usr/share/akonadi/agents/icalresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_imap_resource" from file "/usr/share/akonadi/agents/imapresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kabc_resource" from file "/usr/share/akonadi/agents/kabcresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kcal_resource" from file "/usr/share/akonadi/agents/kcalresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_knut_resource" from file "/usr/share/akonadi/agents/knutresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_kolabproxy_resource" from file "/usr/share/akonadi/agents/kolabproxyresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_localbookmarks_resource" from file "/usr/share/akonadi/agents/localbookmarksresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_maildir_resource" from file "/usr/share/akonadi/agents/maildirresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_maildispatcher_agent" from file "/usr/share/akonadi/agents/maildispatcheragent.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_mbox_resource" from file "/usr/share/akonadi/agents/mboxresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_microblog_resource" from file "/usr/share/akonadi/agents/microblog.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_mailtransport_dummy_resource" from file "/usr/share/akonadi/agents/mtdummyresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuk_calendar_feeder" from file "/usr/share/akonadi/agents/nepomukcalendarfeeder.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuk_contact_feeder" from file "/usr/share/akonadi/agents/nepomukcontactfeeder.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nepomuktag_resource" from file "/usr/share/akonadi/agents/nepomuktagresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_nntp_resource" from file "/usr/share/akonadi/agents/nntpresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_notes_resource" from file "/usr/share/akonadi/agents/notesresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_pop3_resource" from file "/usr/share/akonadi/agents/pop3resource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_vcarddir_resource" from file "/usr/share/akonadi/agents/vcarddirresource.desktop" void AgentManager::readPluginInfos(const QDir&) Duplicated agent identifier "akonadi_vcard_resource" from file "/usr/share/akonadi/agents/vcardresource.desktop" From bugsquad at whamra.com Thu Mar 10 17:22:26 2011 From: bugsquad at whamra.com (Waleed Hamra) Date: Thu, 10 Mar 2011 19:22:26 +0200 Subject: Problem while opening kmail In-Reply-To: References: Message-ID: <4D7908D2.1010407@whamra.com> On 03/10/2011 05:10 PM, أمجد wrote: > Greetings.. > > Everytime I open my kmail i get an error with the following content. > > So I saved it and here I'm sending it. > > > I hope you can help > > > Regards > thank you for your interest in helping us resolve more bugs, but this list is for discussions between bugsquad members about methods of bug triaging, rather than the actual solving of bugs. a better method of reporting bugs would be, in this case for kmail, is to click the "help" menu in kmail, and choose "report bug", the bug reporting wizard should start, and guide you through the rest of the process. for other programs, the non-KDE ones, or the programs that don't have an included "report bug" button, you can use the program "ubuntu-bug" to report the problem, such as: ubuntu-bug hope this helps. -- Waleed K. Hamra Manager of Hamra Information Systems -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 262 bytes Desc: OpenPGP digital signature URL: From noreply at ubuntu.com Fri Mar 11 19:36:49 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 11 Mar 2011 19:36:49 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_vish?= Message-ID: <20110311193649.21916.15756@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by vish: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=25&rev2=26 The comment on the change is: explain work-around ------------------------------------------------------------------------------ * 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 * '''Low''': Bugs which affect functionality, but to a lesser extent than most bugs, examples are: - * Ones that can be easily worked around + * A bug that has an easy [[http://www.merriam-webster.com/dictionary/work-around|work-around]] * Ones that affect unusual configurations or uncommon hardware * A bug that has a moderate impact on a non-core application * A cosmetic/usability issue that does not limit the functionality of an application @@ -34, +34 @@ * '''Critical''': A bug which has a severe impact on a large portion of Ubuntu users ||{{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 || ---- CategoryBugSquad From brian at ubuntu.com Sat Mar 12 00:11:42 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 11 Mar 2011 16:11:42 -0800 Subject: Next Meeting - 15 March Message-ID: <20110312001142.GB2525@murraytwins.com> There wasn't much turn out for the Bug Squad meeting on the 8th and the 15th seemed like a more interesting day[1] to have one. It'll be at 1700 UTC in #ubuntu-bugs. There isn't much on the agenda page[2] yet so feel free to add anything you are interested in or want to talk about or even just stop by and say hi! [1] http://en.wikipedia.org/wiki/Ides_of_march [2] https://wiki.ubuntu.com/BugSquad/Meeting Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From micahg at ubuntu.com Sun Mar 13 02:03:17 2011 From: micahg at ubuntu.com (Micah Gersten) Date: Sat, 12 Mar 2011 20:03:17 -0600 Subject: Discussion about filing RFPs in Debian for Needs Packaging bugs Message-ID: <4D7C25E5.1030701@ubuntu.com> I added a meeting item for this, but wanted to give the backstory and relative links in advanced so this can be a 5 minute discussion. At UDS-M it was mentioned that RFPs rot in Debian for the most part. I sent an E-Mail [0] to debian-derivatives at l.d.o asking if we should continue to create RFPs for needs-packaging bugs in Launchpad for Ubuntu per current policy on wiki [1]. The response seemed vague and wanted to bring this up to the team based on the responses if we should change the policy or not. Thanks, Micah [0] http://lists.debian.org/debian-derivatives/2011/02/msg00010.html [1] https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs From noreply at ubuntu.com Mon Mar 14 10:56:01 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 14 Mar 2011 10:56:01 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_jeanaustinr?= Message-ID: <20110314105601.16425.23980@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by jeanaustinr: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=322&rev2=323 ------------------------------------------------------------------------------ This response is appropriate when a bug is not reported in English or some error messages are not in English. - || I noticed that some of the sentences in this bug report are not in English. If they were translated to English they would be accessible to more triagers. Could you please translate them?|| + || We noticed that some of the sentences in this bug report are not in English. If they were translated in English they would be more understandable to triagers. Could you please translate them?|| == Suspected bad ISO download == From geoffmcc at digitaltrainwreck.com Mon Mar 14 19:32:10 2011 From: geoffmcc at digitaltrainwreck.com (Geoff McClinsey) Date: Mon, 14 Mar 2011 15:32:10 -0400 Subject: Needs marked Wish List Message-ID: <4D7E6D3A.6030506@digitaltrainwreck.com> Good Afternoon all. Here is a few wish list items. I messaged the Ubuntuone-control-panel item in #ubuntu-bugs yesterday and noticed still not marked so I decided best to also send out this email, not trying to rush, just trying to be thorough. 1. 2. Bug #734917 - Gwibber Wish List Bug #734269 - Ubuntuone-control-panel Wish List* * Have a good day team, Geoff McClinsey -------------- next part -------------- An HTML attachment was scrubbed... URL: From om26er at ubuntu.com Mon Mar 14 19:38:54 2011 From: om26er at ubuntu.com (Omer Akram) Date: Tue, 15 Mar 2011 00:38:54 +0500 Subject: Needs marked Wish List In-Reply-To: <4D7E6D3A.6030506@digitaltrainwreck.com> References: <4D7E6D3A.6030506@digitaltrainwreck.com> Message-ID: Hey Geoff! About the gwibber bug its something that gwibber devs might want to fix so I had already marked it as medium. and for the ubuntu-one-control-panel I have marked it as wishlist. Thanks. On Tue, Mar 15, 2011 at 12:32 AM, Geoff McClinsey < geoffmcc at digitaltrainwreck.com> wrote: > Good Afternoon all. > > Here is a few wish list items. I messaged the Ubuntuone-control-panel item > in #ubuntu-bugs yesterday and noticed still not marked > so I decided best to also send out this email, not trying to rush, just > trying to be thorough. > > 1. > 2. > > Bug #734917 - Gwibber Wish List > Bug #734269 - Ubuntuone-control-panel Wish List* > > * > Have a good day team, > Geoff McClinsey > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Mon Mar 14 22:18:08 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 14 Mar 2011 22:18:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_brian-murray?= Message-ID: <20110314221808.28816.84389@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=174&rev2=175 The comment on the change is: page was renamed from https:/wiki.ubuntu.com/Bugs/Tags ------------------------------------------------------------------------------ + ## page was renamed from https:/wiki.ubuntu.com/Bugs/Tags ## page was renamed from linex ## page was renamed from Bugs/Tags ## page was renamed from BugSquad/Tags From noreply at ubuntu.com Tue Mar 15 02:17:53 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 15 Mar 2011 02:17:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUpdateManager=22_by_red?= =?utf-8?q?singularity?= Message-ID: <20110315021753.21877.46805@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by redsingularity: http://wiki.ubuntu.com/DebuggingUpdateManager?action=diff&rev1=39&rev2=40 ------------------------------------------------------------------------------ || [[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/571743|571743]] || xubuntu-desktop and ubuntu-desktop can not be upgraded if installed in parallel || duplicate, no solution yet || + '''Triaged''' + || '''Bug''' || '''Description''' || '''Action''' || + || [[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/721306]] || Cant upgrade from 10.04 to 10.10 || Master bug || + '''Closed''' || '''Bug''' || '''Description''' || '''Action''' || From noreply at ubuntu.com Tue Mar 15 02:18:43 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 15 Mar 2011 02:18:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUpdateManager=22_by_red?= =?utf-8?q?singularity?= Message-ID: <20110315021843.21923.54841@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by redsingularity: http://wiki.ubuntu.com/DebuggingUpdateManager?action=diff&rev1=40&rev2=41 ------------------------------------------------------------------------------ '''Triaged''' || '''Bug''' || '''Description''' || '''Action''' || - || [[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/721306]] || Cant upgrade from 10.04 to 10.10 || Master bug || + || [[https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/721306|721306]] || Cant upgrade from 10.04 to 10.10 || Master bug || '''Closed''' From brian at ubuntu.com Tue Mar 15 15:17:19 2011 From: brian at ubuntu.com (Brian Murray) Date: Tue, 15 Mar 2011 08:17:19 -0700 Subject: Needs marked Wish List In-Reply-To: <4D7E6D3A.6030506@digitaltrainwreck.com> References: <4D7E6D3A.6030506@digitaltrainwreck.com> Message-ID: <20110315151719.GM2525@murraytwins.com> On Mon, Mar 14, 2011 at 03:32:10PM -0400, Geoff McClinsey wrote: > Good Afternoon all. > > Here is a few wish list items. I messaged the > Ubuntuone-control-panel item in #ubuntu-bugs yesterday and noticed > still not marked > so I decided best to also send out this email, not trying to rush, > just trying to be thorough. Thanks for doing that! I think this process (if no one responds in #ubuntu-bugs - email the Bug Squad mailing list) makes sense as a standard procedure. Otherwise things might get lost. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From fco.plj at gmail.com Tue Mar 15 21:37:34 2011 From: fco.plj at gmail.com (Francisco Javier P.L.) Date: Tue, 15 Mar 2011 15:37:34 -0600 Subject: Alpha Group Message-ID: <4D7FDC1E.1080605@gmail.com> Bom día, I've heard that the ubuntu bugsquad team has just opened an alpha group to integrate mentors/students in a mailing list and being so, I'd like to be added to the list, I've tried to do it by myself using lp but the group seems restricted. I joined the mentoring program 1 cicle ago, but for some personal stuff I couldn't keep in close touch with my mentor (mrand which is a really nice person btw). My wiki page is at: https://wiki.ubuntu.com/~chilicuil & my id in lp is: https://launchpad.net/~chilicuil flw mermaos! From vish at ubuntu.com Wed Mar 16 09:41:36 2011 From: vish at ubuntu.com (Vishnoo) Date: Wed, 16 Mar 2011 15:11:36 +0530 Subject: Alpha Group In-Reply-To: <4D7FDC1E.1080605@gmail.com> References: <4D7FDC1E.1080605@gmail.com> Message-ID: <1300268496.28679.14.camel@Aspire-5670> On Tue, 2011-03-15 at 15:37 -0600, Francisco Javier P.L. wrote: > Bom día, > > I've heard that the ubuntu bugsquad team has just opened an alpha group > to integrate mentors/students in a mailing list and being so, I'd like > to be added to the list, I've tried to do it by myself using lp but the > group seems restricted. I joined the mentoring program 1 cicle ago, but > for some personal stuff I couldn't keep in close touch with my mentor > (mrand which is a really nice person btw). > > My wiki page is at: https://wiki.ubuntu.com/~chilicuil > & my id in lp is: https://launchpad.net/~chilicuil > > flw mermaos! > Welcome back and Hello, I've included you to the launchpad team [1]. As you are already aware, this team will have around mentees and mentors ; the idea is to: (1) have a mailing list that does not go beyond the mentee-mentor relationship. This ML should be used for any email contact. (Usually the doubts of one mentee are common to others.) (2) get a better ratio mentor/mentee. (3) provide a better assurance that a mentee question will be timely addressed. The list of things you *need* to follow: - Make sure you read the 'How to Triage' wiki [2] pages well before starting to work on bugs! - You *should* subscribe to group's Mailing List. - Any doubts or questions you have, you should send email to the group's Mailing List, not directly to mentors. - You should use IRC whenever possible: a direct contact is better for interaction than email exchange. - On IRC *any* of us on #ubuntu-bugs can help. You can query either one of the mentors, or anyone in the channel. Querying the channel usually provides a better response (what 1 mentor does not know, another mentor will probably know). Please do not hesitate in contacting us if you have any doubts or questions. [1] https://launchpad.net/~bugsquad-mentorship-group-alpha [2] https://wiki.ubuntu.com/Bugs/HowToTriage -- Cheers, Vish From brian at ubuntu.com Wed Mar 16 15:40:53 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 16 Mar 2011 08:40:53 -0700 Subject: New Bug Control Members Message-ID: <20110316154053.GR2525@murraytwins.com> Hello all, We are happy to announce that Robert Roth[1] and Christopher M. Penalver[2] have joined the Ubuntu Bug Control[3] team this week. Robert has been active with Gnome desktop applications and Christopher has been active with OpenOffice.org and LibreOffice bug reports. Both of them are welcome additions to the team! I would like to thank both Christopher and Robert for helping to make Ubuntu even better, and look forward to their continued contributions. [1] https://launchpad.net/~evfool [2] https://launchpad.net/~penalvch [3] https://launchpad.net/~ubuntu-bugcontrol Cheers, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From trinikrono at gmail.com Wed Mar 16 18:05:08 2011 From: trinikrono at gmail.com (kurt belgrave) Date: Wed, 16 Mar 2011 14:05:08 -0400 Subject: Alpha Group In-Reply-To: <1300268496.28679.14.camel@Aspire-5670> References: <4D7FDC1E.1080605@gmail.com> <1300268496.28679.14.camel@Aspire-5670> Message-ID: I would like to apply to the new alpha group also I am almost ready to apply to the bug control but i have a few things i would like to be sure about before i do so. https://launchpad.net/~trinikrono Cheers -------------- next part -------------- An HTML attachment was scrubbed... URL: From marconifabio at ubuntu-it.org Wed Mar 16 22:04:16 2011 From: marconifabio at ubuntu-it.org (njin) Date: Wed, 16 Mar 2011 23:04:16 +0100 Subject: Alpha Group In-Reply-To: <1300268496.28679.14.camel@Aspire-5670> References: <4D7FDC1E.1080605@gmail.com> <1300268496.28679.14.camel@Aspire-5670> Message-ID: Hello I want to be added to a dozen of mentors because i like everythings but i don't understand anythings :) Seriously I prefere the lower levels, kernel, xorg, but i don't have the needed connaissance, then choose you for me. Fabio :P From vish at ubuntu.com Thu Mar 17 07:48:47 2011 From: vish at ubuntu.com (Vishnoo) Date: Thu, 17 Mar 2011 13:18:47 +0530 Subject: Alpha Group In-Reply-To: References: <4D7FDC1E.1080605@gmail.com> <1300268496.28679.14.camel@Aspire-5670> Message-ID: <1300348127.28679.78.camel@Aspire-5670> On Wed, 2011-03-16 at 23:04 +0100, njin wrote: Hello > I want to be added to a dozen of mentors because i like everythings but > i don't understand anythings :) > Seriously I prefere the lower levels, kernel, xorg, but i don't have the > needed connaissance, then choose you for me. > Fabio :P > > On Wed, 2011-03-16 at 14:05 -0400, kurt belgrave wrote: > I would like to apply to the new alpha group also > I am almost ready to apply to the bug control but i have a few things > i would like to be sure about before i do so. > > https://launchpad.net/~trinikrono > > Cheers Hello, You guys have been around for a while, but since you'd like to be sure before you apply to BC, I've included the two of you to the launchpad team [1]. However, I would encourage you guys to clear your doubts and apply for BugControl soonish .. :-) So, Gentlemen Start Your Questions .... ;-) To be clear, this team will have mentees and mentors ; the idea is to: (1) have a mailing list that does not go beyond the mentee-mentor relationship. This ML should be used for any email contact. (Usually the doubts of one mentee are common to others.) (2) get a better ratio mentor/mentee. (3) provide a better assurance that a mentee question will be timely addressed. The list of things you *need* to follow: - Make sure you read the 'How to Triage' wiki [2] pages well before starting to work on bugs! - You *should* subscribe to group's Mailing List. - Any doubts or questions you have, you should send email to the group's Mailing List, not directly to mentors. - You should use IRC whenever possible: a direct contact is better for interaction than email exchange. - On IRC *any* of us on #ubuntu-bugs can help. You can query either one of the mentors, or anyone in the channel. Querying the channel usually provides a better response (what 1 mentor does not know, another mentor will probably know). Please do not hesitate in contacting us if you have any doubts or questions. [1] https://launchpad.net/~bugsquad-mentorship-group-alpha [2] https://wiki.ubuntu.com/Bugs/HowToTriage -- Cheers, Vish From noreply at ubuntu.com Wed Mar 16 21:02:04 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 16 Mar 2011 21:02:04 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110316210204.1278.68051@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=34&rev2=35 ------------------------------------------------------------------------------ || '''Situation''' || '''Response''' || '''Note''' || || Patch needs author to sign Canonical Contributer agreement || Looks good but before we merge it we need you to sign the Canonical contributer agreement. It's a quick, but necessary step to getting your code into the tree. Luckily you only need to sign it once and it will apply to all other Canonical project contributions you may make in the future. http://www.canonical.com/contributors Make sure to CC David Barth when you send it in. || || || Blocked waiting for design decision || This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward. || Mark status as ''incomplete'', and tag ''needs-design'' until design gives feedback. || - || Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to invalid, and let the user reopen it || + || Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to WONTFIX, and let the user reopen it || || Bugs that don't appear to be Unity related at all || The issue you're describing doesn't sound related to Unity. Could you log into a Gnome 2 session and see if this issue persists? || || = Bug Tags = From noreply at ubuntu.com Thu Mar 17 15:42:53 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 17 Mar 2011 15:42:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_hggdh2?= Message-ID: <20110317154253.2412.81761@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=27&rev2=28 ------------------------------------------------------------------------------ <> 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 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. + 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. From noreply at ubuntu.com Thu Mar 17 15:40:39 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 17 Mar 2011 15:40:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_hggdh2?= Message-ID: <20110317154039.2412.59591@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by hggdh2: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=26&rev2=27 ------------------------------------------------------------------------------ <> 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 in [[Malone| 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. + In order to set the Importance field 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. From ddecator at ubuntu.com Sun Mar 20 14:41:37 2011 From: ddecator at ubuntu.com (Draycen DeCator) Date: Sun, 20 Mar 2011 09:41:37 -0500 Subject: New Wiki Structure Proposal Message-ID: Hello fellow triagers! There has been a lot of discussion on IRC between the BugSquad and the Ubuntu Beginners Team about how the BugSquad wiki can be improved so it's more streamlined and user-friendly. As it stands now, the HowToTriage page is the primary place for people to go and dump any information related to triage. This has resulted in the page just being a wall of text that is overwhelming to new users who are just getting started. To improve this, the information will need to be spread out in a logical way that walks new users through the process from beginning to end. Attached is a mindmap showing what my proposal is for how this can be done (I've included an image for those who just want to view it, and the Freemind file if you want to make any changes). For a new user, they would follow the whole setup from the top down, so it would walk them through the entire process. For those with some experience, hopefully it will be easy to get to the information that they need. As for the HowToTriage page, it would be more of an expansion of the flowcharts that are on the wiki. This way, it will become a step-by-step guide or a checklist for the triage process that anybody can follow. Take a look and let me know what you think. Once an initial structure is decided on, I will make at least a few PDFs showing a concept of how the actual pages will be setup. Those will then be sent to both the BugSquad and the UBT mailing lists for further input. Eventually, the UBT Wiki group will be helping us implement the changes. Hope you're all having a great weekend! Dray -- Draycen DeCator BugSquad/UBT https://wiki.ubuntu.com/ddecator https://launchpad.net/~ddecator -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Wiki structure.mm Type: application/x-freemind Size: 5213 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Wiki structure.png Type: image/png Size: 61928 bytes Desc: not available URL: From noreply at ubuntu.com Sat Mar 19 19:12:13 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 19 Mar 2011 19:12:13 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_yofe?= =?utf-8?q?l?= Message-ID: <20110319191213.4164.31094@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by yofel: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=112&rev2=113 ------------------------------------------------------------------------------ === Applications === Applications in released versions of Ubuntu no longer have a "Report a Problem" menu item. Thus, you must first determine the executable name for the application and then find the package to which the executable belongs. + + ==== Apport ==== + + Since Natty Narwhal (11.04) you can call ubuntu-bug with -w or --window which makes it possible for you to click on the window of the application and apport will identify the package name by itself. ==== Determining the Executable Path ==== From trinikrono at gmail.com Sun Mar 20 16:08:55 2011 From: trinikrono at gmail.com (kurt belgrave) Date: Sun, 20 Mar 2011 12:08:55 -0400 Subject: New Wiki Structure Proposal In-Reply-To: References: Message-ID: +1 from me What about the Responses Page, can that be more visible since new guys normally get in trouble for not using standard Responses. On Sun, Mar 20, 2011 at 10:41 AM, Draycen DeCator wrote: > Hello fellow triagers! > > There has been a lot of discussion on IRC between the BugSquad and the > Ubuntu Beginners Team about how the BugSquad wiki can be improved so it's > more streamlined and user-friendly. As it stands now, the HowToTriage page > is the primary place for people to go and dump any information related to > triage. This has resulted in the page just being a wall of text that is > overwhelming to new users who are just getting started. > > To improve this, the information will need to be spread out in a logical > way that walks new users through the process from beginning to end. Attached > is a mindmap showing what my proposal is for how this can be done (I've > included an image for those who just want to view it, and the Freemind file > if you want to make any changes). For a new user, they would follow the > whole setup from the top down, so it would walk them through the entire > process. For those with some experience, hopefully it will be easy to get to > the information that they need. > > As for the HowToTriage page, it would be more of an expansion of the > flowcharts that are on the wiki. This way, it will become a step-by-step > guide or a checklist for the triage process that anybody can follow. > > Take a look and let me know what you think. Once an initial structure is > decided on, I will make at least a few PDFs showing a concept of how the > actual pages will be setup. Those will then be sent to both the BugSquad and > the UBT mailing lists for further input. Eventually, the UBT Wiki group will > be helping us implement the changes. > > Hope you're all having a great weekend! > Dray > > -- > Draycen DeCator > BugSquad/UBT > https://wiki.ubuntu.com/ddecator > https://launchpad.net/~ddecator > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ddecator at ubuntu.com Sun Mar 20 18:14:43 2011 From: ddecator at ubuntu.com (Draycen DeCator) Date: Sun, 20 Mar 2011 13:14:43 -0500 Subject: New Wiki Structure Proposal In-Reply-To: References: Message-ID: Yah, we'll definitely want the responses page somewhere, but I'm not sure where the best place would be. Dray On Mar 20, 2011 12:08 PM, "kurt belgrave" wrote: > +1 from me > What about the Responses Page, can that be more visible since new guys > normally get in trouble for not using standard Responses. > > On Sun, Mar 20, 2011 at 10:41 AM, Draycen DeCator wrote: > >> Hello fellow triagers! >> >> There has been a lot of discussion on IRC between the BugSquad and the >> Ubuntu Beginners Team about how the BugSquad wiki can be improved so it's >> more streamlined and user-friendly. As it stands now, the HowToTriage page >> is the primary place for people to go and dump any information related to >> triage. This has resulted in the page just being a wall of text that is >> overwhelming to new users who are just getting started. >> >> To improve this, the information will need to be spread out in a logical >> way that walks new users through the process from beginning to end. Attached >> is a mindmap showing what my proposal is for how this can be done (I've >> included an image for those who just want to view it, and the Freemind file >> if you want to make any changes). For a new user, they would follow the >> whole setup from the top down, so it would walk them through the entire >> process. For those with some experience, hopefully it will be easy to get to >> the information that they need. >> >> As for the HowToTriage page, it would be more of an expansion of the >> flowcharts that are on the wiki. This way, it will become a step-by-step >> guide or a checklist for the triage process that anybody can follow. >> >> Take a look and let me know what you think. Once an initial structure is >> decided on, I will make at least a few PDFs showing a concept of how the >> actual pages will be setup. Those will then be sent to both the BugSquad and >> the UBT mailing lists for further input. Eventually, the UBT Wiki group will >> be helping us implement the changes. >> >> Hope you're all having a great weekend! >> Dray >> >> -- >> Draycen DeCator >> BugSquad/UBT >> https://wiki.ubuntu.com/ddecator >> https://launchpad.net/~ddecator >> >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> -------------- next part -------------- An HTML attachment was scrubbed... URL: From vish at ubuntu.com Sun Mar 20 19:54:50 2011 From: vish at ubuntu.com (Vishnoo) Date: Mon, 21 Mar 2011 01:24:50 +0530 Subject: New Wiki Structure Proposal In-Reply-To: References: Message-ID: <1300650891.32594.5.camel@Aspire-5670> On Sun, 2011-03-20 at 12:08 -0400, kurt belgrave wrote: > +1 from me > What about the Responses Page, can that be more visible since new guys > normally get in trouble for not using standard Responses. Nobody is supposed to "get in trouble" for not using the standard responses. :-) Those are _just_ to help everyone, since several of the members are not native English Speakers and having a set of formatted replies for the common scenarios helps everyone reply quicker than typing it each time. You dont need to use those. If you do have your own better response format, do share with others and improve the existing ones. -- Cheers, Vish From brian at ubuntu.com Mon Mar 21 20:58:23 2011 From: brian at ubuntu.com (Brian Murray) Date: Mon, 21 Mar 2011 13:58:23 -0700 Subject: New ubuntu-bug option Message-ID: <20110321205823.GH2525@murraytwins.com> Its now possible, in Natty, to use ubuntu-bug with a -w option, 'ubuntu-bug -w', to report a bug about a running application by then clicking on an open window. Thanks go to Abhinav Upadhyay for adding this functionality. This would be useful information to add to any bug reporting documentation you know of as its lots more accessible than trying to figure out the name of some applications. Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From er.abhinav.upadhyay at gmail.com Mon Mar 21 21:02:57 2011 From: er.abhinav.upadhyay at gmail.com (Abhinav Upadhyay) Date: Tue, 22 Mar 2011 02:32:57 +0530 Subject: New ubuntu-bug option In-Reply-To: <20110321205823.GH2525@murraytwins.com> References: <20110321205823.GH2525@murraytwins.com> Message-ID: Yaay!! Thanks Brian for giving me the credit :-) .It feels really great. Although I must say that Martin helped me a lot by answering questions and also cleaning up the patch after I submitted it. And yes, its really a great add on to apport. Thanks On Tue, Mar 22, 2011 at 2:28 AM, Brian Murray wrote: > Its now possible, in Natty, to use ubuntu-bug with a -w option, > 'ubuntu-bug -w', to report a bug about a running application by then > clicking on an open window. Thanks go to Abhinav Upadhyay for adding > this functionality. > > This would be useful information to add to any bug reporting > documentation you know of as its lots more accessible than trying to > figure out the name of some applications. > > Thanks, > -- > Brian Murray > Ubuntu Bug Master > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAk2Hu+8ACgkQDTAwc5ER+zUQXwCg3f3ZVo37+uRyI0DuerZ+VAkR > KsQAoOHAD2i0nrWIik3Of0/vKKtfHxkN > =IsvN > -----END PGP SIGNATURE----- > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Wed Mar 23 15:20:11 2011 From: brian at ubuntu.com (Brian Murray) Date: Wed, 23 Mar 2011 08:20:11 -0700 Subject: Ubuntu Bug Day - March 24, 2011 Message-ID: <20110323152011.GO2525@murraytwins.com> Hello fellow Ubuntu Bug Triagers! This week's Bug Day target is your friendly neighborhood installer ubiquity! * 150 New bugs need a hug We are trying something different this week and specifically focusing on recreating New bug reports about ubiquity. Our goal is to move them to the Confirmed status after having improved the bug report by recreating it and documenting the steps to recreate it. So download your latest daily CD image of choice[1], setup your favorite installer testing system (real or virtual) and get ready for the Bug Day on March 24th, 2011! * http://wiki.ubuntu.com/UbuntuBugDay/20110324 * join us on irc in #ubuntu-bugs on Freenode We are always looking for new tasks or ideas for the Bug Days, if you have one add it to the planning page https://wiki.ubuntu.com/UbuntuBugDay/Planning. If you're new to all this, head to http://wiki.ubuntu.com/Bugs [1] http://cdimage.ubuntu.com/ For example, see the daily-live directory for Ubuntu desktop images with ubiquity Have a nice day, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Mar 23 17:07:08 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 23 Mar 2011 17:07:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Unity/FilingBugs=22_by_alexlauni?= Message-ID: <20110323170708.1887.98503@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by alexlauni: http://wiki.ubuntu.com/Unity/FilingBugs?action=diff&rev1=35&rev2=36 ------------------------------------------------------------------------------ || Blocked waiting for design decision || This bug is awaiting design feedback before progress can be made. Confirming that there is a question to be answered. Will be marked triaged when design gives a suitable direction forward. || Mark status as ''incomplete'', and tag ''needs-design'' until design gives feedback. || || Bug reported from clutter based Unity || This bug was reported against an old version of Unity. The new version of Unity is almost an entire rewrite based on very different technologies. Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status. || Set the bug to WONTFIX, and let the user reopen it || || Bugs that don't appear to be Unity related at all || The issue you're describing doesn't sound related to Unity. Could you log into a Gnome 2 session and see if this issue persists? || || + || Crashers for which you'd like the user to get a stack trace || Could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting%20a%20stack%20trace and attach unity.log to this bug report? || || = Bug Tags = From cjk at teamcharliesangels.com Thu Mar 24 15:47:23 2011 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Thu, 24 Mar 2011 09:47:23 -0600 Subject: Invalid due to package removal in development release Message-ID: <20110324094723.1c2112e8@teamcharliesangels.com> Has there been a policy change I missed? As of 2011-03-23, all bugs against "usplash" were closed as invalid because the package was removed from Natty Narwhal. This package is still present in all active releases, according to rmadison: rmadison usplash usplash | 0.2-4 | dapper | source, amd64, i386, powerpc usplash | 0.5.19 | hardy | source, amd64, i386 usplash | 0.5.49 | karmic | source, amd64, i386 usplash | 0.5.51 | lucid/universe | source, amd64, i386 usplash | 0.5.52 | maverick/universe | source, amd64, i386 I was unaware that as packages are removed from the development release, every bug against that package is now invalid. -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From hggdh2 at ubuntu.com Thu Mar 24 15:55:58 2011 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 24 Mar 2011 10:55:58 -0500 Subject: Invalid due to package removal in development release In-Reply-To: <20110324094723.1c2112e8@teamcharliesangels.com> References: <20110324094723.1c2112e8@teamcharliesangels.com> Message-ID: <4D8B698E.4010502@ubuntu.com> On 03/24/2011 10:47 AM, Charlie Kravetz wrote: > Has there been a policy change I missed? As of 2011-03-23, all bugs > against "usplash" were closed as invalid because the package was > removed from Natty Narwhal. This package is still present in all active > releases, according to rmadison: > > rmadison usplash > usplash | 0.2-4 | dapper | source, amd64, i386, powerpc > usplash | 0.5.19 | hardy | source, amd64, i386 > usplash | 0.5.49 | karmic | source, amd64, i386 > usplash | 0.5.51 | lucid/universe | source, amd64, i386 > usplash | 0.5.52 | maverick/universe | source, amd64, i386 > > I was unaware that as packages are removed from the development > release, every bug against that package is now invalid. Charlie, I am also unaware of this change. This may have been a result of bug 727517 [1]; I am looking at the bugs now, trying to find out what happened. Thank yo for the heads up. ..C.. [1] https://bugs.edge.launchpad.net/bugs/727517 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 900 bytes Desc: OpenPGP digital signature URL: From brian at ubuntu.com Fri Mar 25 21:07:24 2011 From: brian at ubuntu.com (Brian Murray) Date: Fri, 25 Mar 2011 14:07:24 -0700 Subject: Invalid due to package removal in development release In-Reply-To: <20110324094723.1c2112e8@teamcharliesangels.com> References: <20110324094723.1c2112e8@teamcharliesangels.com> Message-ID: <20110325210724.GA2525@murraytwins.com> On Thu, Mar 24, 2011 at 09:47:23AM -0600, Charlie Kravetz wrote: > Has there been a policy change I missed? As of 2011-03-23, all bugs > against "usplash" were closed as invalid because the package was > removed from Natty Narwhal. This package is still present in all active > releases, according to rmadison: > > rmadison usplash > usplash | 0.2-4 | dapper | source, amd64, i386, powerpc > usplash | 0.5.19 | hardy | source, amd64, i386 > usplash | 0.5.49 | karmic | source, amd64, i386 > usplash | 0.5.51 | lucid/universe | source, amd64, i386 > usplash | 0.5.52 | maverick/universe | source, amd64, i386 > > I was unaware that as packages are removed from the development > release, every bug against that package is now invalid. In Launchpad when we look at a bug report and the bug task listing table the default task (one with out a specific release identified) is considered to affect the development release of Ubuntu. Right now, this happens to be Natty but two months from now it will be Oneiric. Because more often than not bugs are carried over from release to release we leave all bugs reported during a previous release cycle open rather than closing them all. However, the software in the development release changes over time and packages are added and removed. As packages are removed their default task does in fact become Invalid - there is no way that it can be fixed in a release the package doesn't exist in. This doesn't mean we should write a script to invalidate all the bug reports about packages that have been removed from the development release or previous releases. Rather each bug report should be looked at individually because it is possible that the bug is worthy of fixing in a stable release of Ubuntu and a stable release task should be opened. Additionally, when closing these bug reports about packages that have been removed we should be very verbose about why the bug is being closed and communicate how someone can go about getting the bug report fixed in a stable release. We have tools for replying with a standard response and there is no reason not to make those responses incredibly informative. I think it would be useful, but not a high priority, to review the bug reports about packages that have been removed from Natty or previous releases if there is someone or a group of people interested in doing that. Before reviewing these type of bug reports though we should come up with a good standard reply and discuss the criteria for whether or not something is SRU worthy. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Mar 30 19:05:39 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 30 Mar 2011 19:05:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_era?= Message-ID: <20110330190539.13184.89249@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by era: http://wiki.ubuntu.com/DebuggingProcedures?action=diff&rev1=108&rev2=109 The comment on the change is: Add entry for DebuggingEmacs -- about to create this page ------------------------------------------------------------------------------ * [[Unity/FilingBugs|Unity]] * [[DebuggingAyatana|Ayatana project]] * [[DebuggingBanshee|Banshee]] - * [[DebuggingFirefox|Firefox Web Browser]] + * [[DebuggingEmacs|Emacs]] * [[DebuggingEvince|Evince Document Viewer]] * [[DebuggingEvolution|Evolution Mail]] + * [[DebuggingFirefox|Firefox Web Browser]] * [[DebuggingGNOME|GNOME applications]] * [[DebuggingGNOMEApplets|GNOME applets]] * [[DebuggingGNOMEPowerManager|GNOME power manager]] From noreply at ubuntu.com Wed Mar 30 19:48:51 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 30 Mar 2011 19:48:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=22_by_era?= Message-ID: <20110330194851.1475.89658@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by era: http://wiki.ubuntu.com/DebuggingEmacs The comment on the change is: Middle save, not yet finished New page: <> ||'''Contents'''<
><>|| = Introduction = There are multiple Emacs packages, collectively referred to as "Emacsen". They all depend on a package called `emacsen-common`, and they are divided into "flavors". The main flavors are GNU Emacs (AKA FSF Emacs; `emacs23` and `emacs-snapshot`) and `xemacs21`. These in turn are divided into multiple packages, in order to separate architecture-independent components (for which only one package is needed) from architecture-dependent ones (which need to be built separately for each architecture), and mandatory components from optional ones. If you only need one Emacs flavor, the stable GNU Emacs (currently `emacs23`) is recommended. `xemacs21` is rather old and not very actively maintained; `emacs-snapshot` contains a relatively recent non-release version of the developer sources, though you might want to obtain a more recent version from a PPA or other non-Ubuntu source if you want the really latest and greatest. There is a plethora of Emacs add-on packages. Most of these are supported on all flavors, but there are notable exceptions. Some add-ons are not needed on some flavors, and some add-ons provide newer and / or different versions of components which are also included with a base Emacs install (e.g. Gnus). = How to file = You can file bugs against Emacs using Apport. There is also the built-in`M-x emacs-bug-report` but it is not fully customized for sending bug reports to Ubuntu. = Bug tags = (Developers: please update this section) = Debugging procedure = If Emacs doesn't behave like you expect, try running `emacs -Q` and see if the problem goes away. This disables the reading of your `.emacs` file and other local modifications. If the problem goes away, the problem is most likely in a local customization. If you get an error message from Emacs, you may be able to trigger a backtrace which shows which Lisp functions were being processed when the error hit. Enable backtraces with `M-: (setq debug-on-error t)` and attach the `*Backtrace*` buffer to your bug report. == Package Installation Errors == Apparent Emacs errors are often caused by an add-on package which contains a bug or incompatibility with the installed Emacs flavor. If `dpkg` prints an error message indicating that the package `postinst` failed, the actual error message is probably a few lines before this message in the `dpkg` output. == Byte Compilation Errors == A particular type of installation error is the byte compilation error. With `emacs22` and `emacs-snapshot` the terminal log will contain a message like this: `!! Byte-compilation for <> failed!`<
> `!! This indicates a bug in one of the add-on packages`<
> `!! installed on your system, or a bug in Emacs itself.`<
> `!! Please file a bug report against <>`<
> `!! and attach the file /tmp/<>.<>` The file name will be different each time. This file is required in order to analyze the problem. = How to Triage = Apport bugs are generally triggered by a package failing to install, and usually include DpkgTerminalLog or VarDistUpgradeTermLog as an attachment; this log file is usually the first one to examine. Typically, it will contain an error message near the end which indicate which package failed installation and why. If this file is missing, it should be requested. See a canned reply below for example. If the message indicates a byte-compilation error in an add-on package (see above), the temporary file in the error message should be attached to the bug report. If it is not, it should be requested. See a canned reply below for example. == Stock Replies == '''TODO''' How to produce and attach a backtrace === Missing Terminal Log === ||Thank you for taking the time to report this bug and helping to make Ubuntu better. In order for us to be able to analyze this problem, we would like you to attach the contents of the file /var/log/apt/term.log to this bug report. You will need sudo privileges to read or copy this file.<
><
>If you got this error during an upgrade from an earlier version of Ubuntu, the log file's name will instead be /var/log/dist-upgrade.log<
><
>Thanks in advance!|| === Missing Byte Compilation Log === ||If you still have this file on your system, please attach it to this bug report. However, files in the /tmp directory are purged on reboot; if the file has already been removed from your system, you may be able to recreate a similar file by attempting to repeat the operation which failed when you got the error message. However, the name of the generated temporary file will be slightly different each time; refer to near the end of your /var/log/apt/term.log to see the exact generated file name. You will need sudo privileges to read the terminal log file.|| '''TODO''' The Bugs/Responses page should include these replies. == How to Forward == The standard upstream for FSF Emacs bugs is http://debbugs.gnu.org/ which is running the same software as the Debian BTS. The Ubuntu packages are generally merged from Debian, so for packaging bugs, Debian is the upstream. = Known bugs = Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'. '''Open''' || '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... || '''Closed''' || '''Bug''' || '''Subject''' || '''Symptom''' || || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... || = 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 noreply at ubuntu.com Thu Mar 31 10:59:58 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 31 Mar 2011 10:59:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=22_by_era?= Message-ID: <20110331105958.13299.7629@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by era: http://wiki.ubuntu.com/DebuggingEmacs?action=diff&rev1=5&rev2=6 The comment on the change is: Link to unrelated bug #512096 ------------------------------------------------------------------------------ = 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. + To the best of our knowledge, this is not an Emacs bug, but it appears to manifest a lot when installing Emacs: + + || '''Bug''' || '''Subject''' || '''Symptom''' || + || [[https://launchpad.net/bugs/512096| 512096]] || Exec format error: package failed to install/remove || Seems to often affect `emacsen-common` -- `00debian-vars.el` or similar file missing even though package apparently installed || ---- CategoryBugSquad From noreply at ubuntu.com Thu Mar 31 11:54:43 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 31 Mar 2011 11:54:43 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=22_by_era?= Message-ID: <20110331115443.5703.12875@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by era: http://wiki.ubuntu.com/DebuggingEmacs?action=diff&rev1=8&rev2=9 The comment on the change is: Clarify and reword upstream forwarding notes ------------------------------------------------------------------------------ == How to Forward == - The standard upstream for FSF Emacs bugs is http://debbugs.gnu.org/ which is running the same software as the Debian BTS. The Ubuntu packages are generally merged from Debian, so for packaging bugs, Debian is the upstream. + The ultimate upstream for GNU Emacs bugs is http://debbugs.gnu.org/ which is running the same software as the Debian BTS. The Ubuntu packages are generally merged from Debian, so Debian is generally a suitable upstream; and of course, for packaging bugs, Debian is usually the sole upstream. = Known bugs = From noreply at ubuntu.com Thu Mar 31 11:28:42 2011 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 31 Mar 2011 11:28:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingEmacs=22_by_era?= Message-ID: <20110331112842.25838.11619@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by era: http://wiki.ubuntu.com/DebuggingEmacs?action=diff&rev1=6&rev2=7 The comment on the change is: Link to known bugs #467446, #464587, #222870, #396038, #582341 ------------------------------------------------------------------------------ '''Closed''' || '''Bug''' || '''Subject''' || '''Symptom''' || - || [[https://launchpad.net/bugs/8896|8896]] || The subject from LP || This bug can be identified by ... || + || [[https://launchpad.net/bugs/467446|467446]] || update-alternatives: error: alternative path /usr/bin/xemacs21 doesn't exist || Fixed in a recent version of `xemacs21` but still affects people runnng older Ubuntu releases || + || [[https://launchpad.net/bugs/464587|464587]] || ocaml-mode: Invalid syntax description flag: "()1n" || Fixed in a recent version of `ocaml` but still affects people runnng older Ubuntu releases and `xemacs21` || + || [[https://launchpad.net/bugs/222870|222870]] || anjsp: Wrong number of arguments: require, 3 || `anjsp` is not compatible with `xemacs21`. It no longer ships with Ubuntu but still affects people running older Ubuntu releases || + || [[https://launchpad.net/bugs/396038|396038]] || Group `staff` missing; Emacs installation failed || This rare error was never properly debugged, but it did occur more than once || = Non-bugs = To the best of our knowledge, this is not an Emacs bug, but it appears to manifest a lot when installing Emacs: || '''Bug''' || '''Subject''' || '''Symptom''' || - || [[https://launchpad.net/bugs/512096| 512096]] || Exec format error: package failed to install/remove || Seems to often affect `emacsen-common` -- `00debian-vars.el` or similar file missing even though package apparently installed || + || [[https://launchpad.net/bugs/512096|512096]] || Exec format error: package failed to install/remove || Seems to often affect `emacsen-common` -- `00debian-vars.el` or similar file missing even though package apparently installed. See also bug [[https://launchpad.net/bugs/582341|#582341]] || ---- CategoryBugSquad