From jian.h222 at gmail.com Fri Oct 1 02:20:42 2010 From: jian.h222 at gmail.com (Jian H) Date: Fri, 1 Oct 2010 10:20:42 +0800 Subject: A bug of ubuntu Message-ID: the upgrade I used the command.But it can't enter the login page when I restart. From jordon at envygeeks.com Fri Oct 1 23:53:07 2010 From: jordon at envygeeks.com (Jordon Bedwell) Date: Fri, 01 Oct 2010 18:53:07 -0500 Subject: A way to email bugs like upstream? Message-ID: <1285977187.21339.10.camel@loc> Is there a way we can email or submit simple bugs without the need to use apport and collect? I was hoping that much like the Debian email alternative using the pseudo headers (Package and Version) to submit at bugs.debian.org we could submit bugs to Ubuntu... The problem is, there are two bugs that should not need to do a complete collect and I would never provide a complete collect on the second bug, the first is still up in the air. The first: is for a problem with the way the fglrx package maintainer patched for backwards compatibility and dpkg says exactly that so I just need to submit a bug asking him to find a more elegant way to handle backwards compatibility with older kernels, I would even be willing to help with that bug if it takes that. The second: is with a script provided by apache2 (which still doesn't need a full collect), I've already prepared a patch to fix it on live servers and would be willing to provide a patch to fix it when it comes down from upstream, it's also being reported to upstream. From macoafi at gmail.com Sat Oct 2 00:04:48 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Fri, 1 Oct 2010 20:04:48 -0400 Subject: A way to email bugs like upstream? In-Reply-To: <1285977187.21339.10.camel@loc> References: <1285977187.21339.10.camel@loc> Message-ID: <201010012004.49242.macoafi@gmail.com> On Friday, October 01, 2010 07:53:07 pm Jordon Bedwell wrote: > Is there a way we can email or submit simple bugs without the need to > use apport and collect? https://help.launchpad.net/Bugs/EmailInterface From arche1 at gmx.at Sun Oct 3 14:06:22 2010 From: arche1 at gmx.at (Noah Essl) Date: Sun, 3 Oct 2010 14:06:22 +0000 (UTC) Subject: Bug from GNOME maybe reffered to bug from UBUNTU References: <20100908175906.108170@gmx.net> Message-ID: Mackenzie Morgan writes: > > On Wed, Sep 8, 2010 at 1:59 PM, Noah Essl wrote: > > Dear Bugsquad, > > > > I reportet a bug to bugzilla.gnome.org and was told that this might not be a bug of GNOME but of UBUNTU and > that I should contakt you. > > > > https://bugzilla.gnome.org/show_bug.cgi?id=628751 > > > > Would you mind reading through the comments there, and tell me how to continue the bug report? > > I do not know if I can report a bug caused by a application in GNOME via Launchpad to the UBUNTU buglist. > > To file a bug in Ubuntu against any package, just run: > ubuntu-bug > > So like: > ubuntu-bug gnome-bluetooth > > Do you still have the .crash from this in your /var/crash/ directory? > If so, Launchpad can automatically perform a retrace with debug > symbols on it. > It took me some time to find this page and your reply (i did not get an e-mail reply message) and since I update my system every day I can not reproduce this bug which means is must have been fixed during some other fixing. Everything works, thanks so far From alessandro.aragione at gmail.com Sun Oct 3 22:34:45 2010 From: alessandro.aragione at gmail.com (Alessandro Aragione) Date: Sun, 03 Oct 2010 22:34:45 -0000 Subject: thanks and presentation by Layn (Alessandro Aragione) Message-ID: <20101003223445.27428.20606.launchpad@potassium.ubuntu.com> Thank you for accepting me in your team. My name Alessandro Aragione, nik. Layn. Italian a long time Ubuntu user since I met its first release I've never stopped loving them with love and I dedicate myself to the community. My job? Oracle DBA. I'm reading the guide as you suggested. See you soon Layn -- This message was sent from Launchpad by Alessandro Aragione (https://edge.launchpad.net/~layn) using the "Contact this team" link on the Ubuntu BugSquad team page (https://edge.launchpad.net/~bugsquad). For more information see https://help.launchpad.net/YourAccount/ContactingPeople From macoafi at gmail.com Mon Oct 4 01:01:24 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sun, 3 Oct 2010 21:01:24 -0400 Subject: Bug from GNOME maybe reffered to bug from UBUNTU In-Reply-To: References: <20100908175906.108170@gmx.net> Message-ID: <201010032101.25390.macoafi@gmail.com> On Sunday, October 03, 2010 10:06:22 am Noah Essl wrote: > It took me some time to find this page and your reply (i did not get an > e-mail reply message) and since I update my system every day I can not > reproduce this bug which means is must have been fixed during some other > fixing. Are you not subscribed to the mailing list? -- Mackenzie From noreply at ubuntu.com Mon Oct 4 13:06:52 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 04 Oct 2010 13:06:52 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Upstream/UpstreamReport=22_?= =?utf-8?q?by_dholbach?= Message-ID: <20101004130652.5451.86065@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 dholbach: http://wiki.ubuntu.com/Bugs/Upstream/UpstreamReport?action=diff&rev1=24&rev2=25 ------------------------------------------------------------------------------ == What happens next == - Launchpad watches are awesome for one simple reason: When a bug is fixed upstream we know about it. When we know about it we can target them with resources. Launchpad watches feed the [[http://daniel.holba.ch/harvest/handler.py?pkg=rhythmbox|Harvest]] machine - which is useful because developers can find these low hanging fruit and fix them. + Launchpad watches are awesome for one simple reason: When a bug is fixed upstream we know about it. When we know about it we can target them with resources. Launchpad watches feed the [[http://harvest.ubuntu.com/opportunities/package/rhythmbox|Harvest]] machine - which is useful because developers can find these low hanging fruit and fix them. == Why you should care == From noreply at ubuntu.com Tue Oct 5 16:27:46 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 16:27:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_cprofitt?= Message-ID: <20101005162746.3384.46319@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 cprofitt: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=135&rev2=136 ------------------------------------------------------------------------------ * Does another distribution have a complete and confirmed bug? * Does the upstream author have a complete and confirmed bug? + ||note: do not confirm your own bugs, we always ask that a second person replicates and confirms a bug.|| + If '''ANY''' of these conditions are satisfied, you can Confirm the report. To do this: * Change the "Status" field to "Confirmed". From deryck.hodge at canonical.com Tue Oct 5 19:15:30 2010 From: deryck.hodge at canonical.com (deryck.hodge at canonical.com) Date: Tue, 05 Oct 2010 19:15:30 -0000 Subject: Launchpad Bugs Re-enabling Auto Expiring Bugs Message-ID: <20101005191530.4244.54982.launchpad@loganberry.canonical.com> Bug expiry in Launchpad is changing ------------------------------------ The way Launchpad handles inactive bugs is changing. This affects your project indubuntu at https://launchpad.net/10n-linuxme What's going to change ----------------------- Right now, the bug expiry option is enabled for indubuntu but is inactive across all of Launchpad. We weren't happy with the way bug expiry worked, so we turned it off. However, now we're ready to switch it back on. In about two weeks, we will re-enable automatic bug expiry in Launchpad. However, we are going to deselect the bug expiry option on each project, including indubuntu . What this means for your project -------------------------------- If you want Launchpad to automatically expire bugs that appear to be inactive, you need to select the 'Expire "Incomplete" bug reports when they become inactive' option on this page: https://bugs.launchpad.net/10n-linuxme/+configure-bugtracker For more detail on how Launchpad determines if a bug is inactive, visit our help page: https://help.launchpad.net/Bugs/Expiry If you enable automatic bug expiry, Launchpad will start to automatically apply the new 'Expired' status to inactive bugs from around 18 October 2010. If you do not want Launchpad to automatically expire inactive bugs, you should do nothing. Why we're doing this --------------------- Most projects have some bugs that languish with no activity. They clutter bug listings and, let's face it, are unlikely to ever come back to life. Automatic bug expiry lets you hand Launchpad the burden of dealing with these. We're disabling the feature on your project, and others, so that Launchpad continues to work for you in the way it does now -- i.e. without automatic bug expiry. If you do want to re-enable bug expiry, it'll take just a few seconds. Deryck Hodge Launchpad Bugs Team Lead From noreply at ubuntu.com Tue Oct 5 22:41:22 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 22:41:22 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/KnownHardwareIssues/10=2E10?= =?utf-8?q?=22_by_ubuntu-treblig?= Message-ID: <20101005224122.10038.99338@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 ubuntu-treblig: http://wiki.ubuntu.com/Bugs/KnownHardwareIssues/10.10 New page: This page is intended to list known issues about specific hardware on Maverick. Try and keep each entry to clearly identify the hardware, any workarounds, a basic explanation of why and a link to the bug. Try and keep it approximately sorted by name. * Asus EeePC 1001HA - Hangs on reboot or shutdown. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/653732 | bug 653732 ]] * ASRock P55M Pro motherboard - Requires nointremap flag to kernel - Problems with interrupt remapping support that was enabled in Maverick. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605686 | bug 605686 ]] From noreply at ubuntu.com Tue Oct 5 22:52:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 22:52:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/KnownHardwareIssues/10=2E10?= =?utf-8?q?=22_by_ubuntu-treblig?= Message-ID: <20101005225234.9833.75504@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 ubuntu-treblig: http://wiki.ubuntu.com/Bugs/KnownHardwareIssues/10.10?action=diff&rev1=2&rev2=3 ------------------------------------------------------------------------------ + = Known hardware specific issues on Maverick (10.10) = + This page is intended to list known issues about specific hardware. Try and keep each entry to clearly identify the hardware, any workarounds, a basic explanation of why and a link to the bug. Try and keep it approximately sorted by name. + + * ASRock P55M Pro motherboard - Requires nointremap flag to kernel - Problems with interrupt remapping support that was enabled in Maverick. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605686 | bug 605686 ]] * Asus EeePC 1001HA - Hangs on reboot or shutdown. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/653732 | bug 653732 ]] - * ASRock P55M Pro motherboard - Requires nointremap flag to kernel - Problems with interrupt remapping support that was enabled in Maverick. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/605686 | bug 605686 ]] - From noreply at ubuntu.com Tue Oct 5 22:41:58 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 22:41:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/KnownHardwareIssues/10=2E10?= =?utf-8?q?=22_by_ubuntu-treblig?= Message-ID: <20101005224158.10023.54995@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 ubuntu-treblig: http://wiki.ubuntu.com/Bugs/KnownHardwareIssues/10.10?action=diff&rev1=1&rev2=2 ------------------------------------------------------------------------------ - This page is intended to list known issues about specific hardware on Maverick. Try and keep each entry to clearly identify the hardware, any workarounds, a basic explanation of why and a link to the bug. Try and keep it approximately sorted by name. + This page is intended to list known issues about specific hardware. Try and keep each entry to clearly identify the hardware, any workarounds, a basic explanation of why and a link to the bug. Try and keep it approximately sorted by name. * Asus EeePC 1001HA - Hangs on reboot or shutdown. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/653732 | bug 653732 ]] From noreply at ubuntu.com Tue Oct 5 22:56:32 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 22:56:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/KnownHardwareIssues/10=2E10?= =?utf-8?q?=22_by_hggdh2?= Message-ID: <20101005225632.16651.4179@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/KnownHardwareIssues/10.10?action=diff&rev1=3&rev2=4 ------------------------------------------------------------------------------ * Asus EeePC 1001HA - Hangs on reboot or shutdown. [[ https://bugs.launchpad.net/ubuntu/+source/linux/+bug/653732 | bug 653732 ]] + + CategoryBugSquad + From noreply at ubuntu.com Tue Oct 5 23:53:20 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 05 Oct 2010 23:53:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_cyan-spam?= Message-ID: <20101005235320.25486.69701@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 cyan-spam: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=136&rev2=137 The comment on the change is: better integrate Confirming warning into flow ------------------------------------------------------------------------------ * Does another distribution have a complete and confirmed bug? * Does the upstream author have a complete and confirmed bug? - ||note: do not confirm your own bugs, we always ask that a second person replicates and confirms a bug.|| - - If '''ANY''' of these conditions are satisfied, you can Confirm the report. To do this: + If '''ANY''' of these conditions are satisfied and ''you are not the original reporter'', you can Confirm the report. To do this: * Change the "Status" field to "Confirmed". * Assign the appropriate "Importance" value, according to [[Bugs/Importance]]. From noreply at ubuntu.com Wed Oct 6 03:10:33 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 06 Oct 2010 03:10:33 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Debugging/WirelessWithoutX=22_?= =?utf-8?q?by_mathieu-tl?= Message-ID: <20101006031033.6570.86242@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 mathieu-tl: http://wiki.ubuntu.com/X/Debugging/WirelessWithoutX?action=diff&rev1=3&rev2=4 ------------------------------------------------------------------------------ This page describes how to set up your system so that a wireless connection is available without needing to log in to the desktop. == NetworkManager == + + === Command-line === + + NetworkManager now comes with a command-line utility to do some amounts of configuration. + + You can list the connections you have previously created: + + {{{ + $ nmcli con + NAME UUID TYPE SCOPE TIMESTAMP-REAL + Auto eth0 af1d8c7f-be09-478c-baf7-8fc894aa4cff 802-3-ethernet system never + NAME UUID TYPE SCOPE TIMESTAMP-REAL + Auto Ubuntu 0e539a80-5b84-4b2b-9bdb-add530e32cd5 802-11-wireless user Mon Oct 4 12:18:47 2010 + }}} + + To connect, you can then use a connection's ID/UUID: + + {{{ + $ nmcli con up uuid 0e539a80-5b84-4b2b-9bdb-add530e32cd5 + }}} + + There is help available by way of the {{{nmcli help}}} command. + === GNOME === 1. ''Right'' click on the network applet in your panel, and select ''Edit Connections…'' @@ -24, +47 @@ == ConnMan == For Maverick, the Ubuntu Netbook Edition images plan to use network-indicator and ConnMan. Currently there is no GUI support for setting up system-wide network connections. + === Command-line === + + Connman (with the 'indicator-network' package) includes a basic command-line application called {{{cmcc}}}. + + ---- CategoryDebugging From noreply at ubuntu.com Wed Oct 6 03:13:09 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 06 Oct 2010 03:13:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Debugging/WirelessWithoutX=22_?= =?utf-8?q?by_serge-hallyn?= Message-ID: <20101006031309.6729.1916@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 serge-hallyn: http://wiki.ubuntu.com/X/Debugging/WirelessWithoutX?action=diff&rev1=4&rev2=5 ------------------------------------------------------------------------------ Connman (with the 'indicator-network' package) includes a basic command-line application called {{{cmcc}}}. + == Wicd == + + An alternatice to using network-manager is to use wicd. It has applet and curses-based clients. To use this, you should first install wicd, then remove network-manager: + + {{{ + apt-get install wicd wicd-curses wicd-cli wicd-gtd + apt-get remove network-manager + }}} + + == ifupdown and iwconfig == + + If you mainly use your home wireless, you can simply set up your wireless interface through /etc/network/interfaces. (See 'man 5 interfaces'). An example would be: + + {{{ + auto lo + iface lo inet loopback + + auto wlan0 + iface wlan0 inet static + address 192.168.254.2 + netmask 255.255.255.0 + gateway 192.168.254.254 + pre-up iwconfig wlan0 essid MyEssid + pre-up iwconfig wlan0 enc XXXXXXXXXXXXXXXXXXXXXXXXXX + }}} + + You can get a list of access points using + + {{{ + iwlist wlan0 scan + }}} + + and connect using + + {{{ + iwconfig wlan0 essid MyEssid + iwconfig wlan0 enc XXXXXXXXXXXXXXXXXXXXXXXXXX + dhclient wlan0 + }}} + + Note that you can't really use iwconfig when using network-manager (or wicd), because the daemon will keep trampling over your changes. ---- CategoryDebugging From noreply at ubuntu.com Wed Oct 6 03:12:57 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 06 Oct 2010 03:12:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Debugging=22_by_raof?= Message-ID: <20101006031257.6570.91449@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 raof: http://wiki.ubuntu.com/X/Debugging?action=diff&rev1=63&rev2=64 ------------------------------------------------------------------------------ I. [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes == Other Resources == - * [[https://wiki.ubuntu.com/X/Debugging/WirelessWithoutX]] - How to get a wireless network connection without X. + * [[https://wiki.ubuntu.com/X/Debugging/WirelessWithoutX|Wireless Without X]] - How to get a wireless network connection without X. * [[https://help.ubuntu.com/community/Video|Video Resources]] at help.ubuntu.com * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia * [[Bugs/AtiDriver]] From noreply at ubuntu.com Wed Oct 6 03:02:21 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 06 Oct 2010 03:02:21 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Debugging=22_by_raof?= Message-ID: <20101006030221.6732.66143@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 raof: http://wiki.ubuntu.com/X/Debugging?action=diff&rev1=62&rev2=63 ------------------------------------------------------------------------------ I. [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes == Other Resources == + * [[https://wiki.ubuntu.com/X/Debugging/WirelessWithoutX]] - How to get a wireless network connection without X. * [[https://help.ubuntu.com/community/Video|Video Resources]] at help.ubuntu.com * [[https://help.ubuntu.com/community/BinaryDriverHowto|BinaryDriverHowto]] - for installing fglrx or nvidia * [[Bugs/AtiDriver]] From pedro at ubuntu.com Wed Oct 6 14:03:34 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Wed, 06 Oct 2010 10:03:34 -0400 Subject: Bugsquad Meeting Reminder - Tuesday 12th October 2010 Message-ID: <1286373814.1997.49.camel@wombat> Hello Folks, Just a reminder that the Tuesday 12th of October 2010 at 1700 UTC we're having our Monthly BugSquad Meeting at #ubuntu-bugs, as always everybody is welcome to join us, the agenda[1] so far looks like: * Intro to new meeting bot. * Mentorship program update from Mentors. * Review the re-writes of the wiki. It is now using two different headers and triage pages are missing the meeting and BugDay headers. Example: https://wiki.ubuntu.com/Bugs/HowToTriage and https://wiki.ubuntu.com/Bugs/FindRightPackage * Open Discussions. * Chair for next meeting. As always don't hesitate to add or modify the topics as needed. If you're a Mentor or Student in the BugSquad mentoring program please attend since we'd like to hear updates on how's everything working for you (how is your student/mentor doing), if you have updates but cannot attend to the meeting please send an email to any of the Mentors admins[2]. 1- https://wiki.ubuntu.com/BugSquad/Meeting 2- https://wiki.ubuntu.com/BugSquad/Mentors/AdminList Have a great day!, pedro. From noreply at ubuntu.com Thu Oct 7 13:18:50 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 07 Oct 2010 13:18:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Debugging/WirelessWithoutX=22_?= =?utf-8?q?by_serge-hallyn?= Message-ID: <20101007131850.7434.63439@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 serge-hallyn: http://wiki.ubuntu.com/X/Debugging/WirelessWithoutX?action=diff&rev1=6&rev2=7 The comment on the change is: Use my actual working interfaces file ------------------------------------------------------------------------------ == ifupdown and iwconfig == - If you mainly use your home wireless, you can simply set up your wireless interface through /etc/network/interfaces. (See 'man 5 interfaces'). An example would be: + If you mainly use your home wireless, you can simply set up your wireless interface through /etc/network/interfaces. (See 'man 5 interfaces'). A working example is: {{{ auto lo @@ -70, +70 @@ auto wlan0 iface wlan0 inet static + wireless-essid MyEssid + wireless-key XXXXXXXXXXXXXXXXXXXXXXXXXX - address 192.168.254.2 + address 192.168.254.3 - netmask 255.255.255.0 + netmask 255.255.255.0 - gateway 192.168.254.254 + gateway 192.168.254.254 + - pre-up iwconfig wlan0 essid MyEssid - pre-up iwconfig wlan0 enc XXXXXXXXXXXXXXXXXXXXXXXXXX }}} You can get a list of access points using From noreply at ubuntu.com Thu Oct 7 14:14:36 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 07 Oct 2010 14:14:36 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20101007141436.28318.18642@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 till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=55&rev2=56 ------------------------------------------------------------------------------ = AppArmor Protection of the printing system = From Gutsy on the security of the CUPS printing system is improved by using App``Armor. Unfortunately, the configuration is not perfect yet, especially if third-party printer drivers are used. If you have any problems with printing, try deactivating the App``Armor protection with {{{sudo aa-complain cupsd}}}. If this helps, look for messages containing '''audit''' in the {{{/var/log/messages}}} file. These show which components are accessed by the printing system for which there is no explicit permission given in {{{/etc/apparmor.d/usr.sbin.cupsd}}}. You can re-activate App``Armor via {{{sudo aa-enforce cupsd}}}. Report a bug, about the package '''cups''' ('''cupsys''' on 8.04 and older), so that we can correct the default configuration of App``Armor. + = Capturing print job data = + Oftenn it is needed to find out what actually got sent to the printer in order to determine whether the problem is caused by the application or by the printing subsystem. For that it is the easiest way to capture the job data from the application so that it can analyzed whether it is already broken or not. To do so, follow these steps: <
> + + 1. Clear the print queues from old jobs. Either use the job viewer or run the command <
> {{{$ cancel -a}}} <
> in a terminal window. + 2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <
> {{{$ cupsdisable }}} <
> in a terminal window (Replace "" by the name of the print queue). This makes jobs staying in the queue so that you can capture them. + 3. Now print the job from your application. When the application has finished sending the job, check via the job viewer or the command <
> {{{$ lpstat -o}}} <
> whether it is in the queue. + 4. Display the content of CUPS' spool directory using the command <
> {{{$ sudo ls -1 /var/spool/cups}}} <
> (Enter your password when getting asked). + 5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <
> {{{$ sudo cp /var/spool/cups/d... ~/printout + }}} <
> {{{$ sudo chmod 777 ~/printout}}} + 6. Re-enable the print queue: <
> {{{$ cupsenable }}} <
> + 7. If the file gets correctly printed now, try the above procedure with another file, we need a file where the problem occurs. + 8. Check via the command <
> {{{$ file ~/printout}}} <
> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package. + 9. Attach the original file of your application and the ~/printout file to your bug report. + = Known bugs = Description of known issues, how to recognise them and stock responses/actions. ## '''Open''' - || '''Bug#''' || '''Description''' || '''Action''' || + ##|| '''Bug#''' || '''Description''' || '''Action''' || - || [[https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/29050|29050]] || Parallel/LPT printer not detected in Dapper and Edgy. Fixed in Feisty. || add "ppdev" to {{{/etc/modules}}} || + ##|| [[https://bugs.launchpad.net/ubuntu/+source/cupsys/+bug/29050|29050]] || Parallel/LPT printer not detected in Dapper and Edgy. Fixed in Feisty. || add "ppdev" to {{{/etc/modules}}} || ## '''Closed''' ## || '''Bug#''' || '''Description''' || '''Action''' || From noreply at ubuntu.com Thu Oct 7 14:15:56 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 07 Oct 2010 14:15:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20101007141556.28350.67256@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 till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=56&rev2=57 ------------------------------------------------------------------------------ 2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <
> {{{$ cupsdisable }}} <
> in a terminal window (Replace "" by the name of the print queue). This makes jobs staying in the queue so that you can capture them. 3. Now print the job from your application. When the application has finished sending the job, check via the job viewer or the command <
> {{{$ lpstat -o}}} <
> whether it is in the queue. 4. Display the content of CUPS' spool directory using the command <
> {{{$ sudo ls -1 /var/spool/cups}}} <
> (Enter your password when getting asked). - 5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <
> {{{$ sudo cp /var/spool/cups/d... ~/printout + 5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <
> {{{$ sudo cp /var/spool/cups/d... ~/printout}}} <
> {{{$ sudo chmod 777 ~/printout}}} - }}} <
> {{{$ sudo chmod 777 ~/printout}}} 6. Re-enable the print queue: <
> {{{$ cupsenable }}} <
> 7. If the file gets correctly printed now, try the above procedure with another file, we need a file where the problem occurs. 8. Check via the command <
> {{{$ file ~/printout}}} <
> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package. From noreply at ubuntu.com Thu Oct 7 20:10:45 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 07 Oct 2010 20:10:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingScreenLocking=22_by_mde?= =?utf-8?q?slaur?= Message-ID: <20101007201045.30399.87217@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 mdeslaur: http://wiki.ubuntu.com/DebuggingScreenLocking?action=diff&rev1=14&rev2=15 ------------------------------------------------------------------------------ || [[https://launchpad.net/bugs/270781]] || unix_chkpwd crashes on gnome-screensaver || || [[https://launchpad.net/bugs/387189]] || /dev/null corrupted (/dev/null.1) || + == gnome-screensaver authentication failure with incorrect /etc/shadow permissions == + + Sometimes, gnome-screensaver will not unlock with a correct password. + + Examining the /var/log/auth.log file shows error similar to the following: + + {{{ + Jul 14 19:04:34 desktop unix_chkpwd[1760]: check pass; user unknown + }}} + + This is caused by the /etc/shadow file having the wrong permissions. Doing "ls -l /etc/shadow" should display the following: + + {{{ + -rw-r----- 1 root shadow 1241 2010-08-22 12:43 /etc/shadow + }}} + + || '''Bug''' || '''Subject''' || + || [[https://launchpad.net/bugs/600631]] || Password does not unlock screen || = Also see = From tuxmaster at geekstogo.com Sat Oct 9 08:01:10 2010 From: tuxmaster at geekstogo.com (tuxmaster geekstogo) Date: Sat, 9 Oct 2010 02:01:10 -0600 Subject: Question about expired bugs. Message-ID: I have been away for a while. For multiple reasons. I was thinking of getting back and helping out due to I am going to renew my effort to use Linux as my primary OS. So I decided to try out the release of 10.10. Well that magnifecently failed. I had no audio. Already submitted Bug 654920. So I decided the community desperately needs some help due to the fact that Ubuntu Is still having regression problems with audio issues. So I desided to jump back on the ubuntu Bugsqad bandwagon. I have a bunch of bugs that I was helping with that are in Incomplete mode. I noticed I had a bunch of subscribed bugs that state "This bug report was marked for expiration X days ago." Does that mean that the bug is expired? When does the bug get marked as expired? More or less do I need to do anything with these. Do I need to do the I thought once they were expired they got taken off the list should I go though the process of invalidating these bugs? Anazenketh -------------- next part -------------- An HTML attachment was scrubbed... URL: From macoafi at gmail.com Sat Oct 9 08:28:30 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sat, 9 Oct 2010 04:28:30 -0400 Subject: Question about expired bugs. In-Reply-To: References: Message-ID: <201010090428.31550.macoafi@gmail.com> On Saturday, October 09, 2010 04:01:10 am tuxmaster geekstogo wrote: > I noticed I had a bunch of subscribed bugs that state "This bug report was > marked for expiration X days ago." > > Does that mean that the bug is expired? > When does the bug get marked as expired? Bugs used to be closed automatically when they expired. This was disabled. So now it's saying "if that feature were enabled, this would have been closed due to the reporter ignoring it." > More or less do I need to do anything with these. Do I need to do the I > thought once they were expired they got taken off the list should I go > though the process of invalidating these bugs? Check what the last few comments were. Were they "can you please respond or do you just not care and we should close this?" or were they the original "hey can you give a screenshot?" If the latter, prompt for a response. If the former and it's been months since that prompt, then closing is ok. -- Mackenzie Morgan http://mackenzie.morgan.name http://ubuntulinuxtipstricks.blogspot.com From tuxmaster at geekstogo.com Sat Oct 9 08:37:13 2010 From: tuxmaster at geekstogo.com (tuxmaster geekstogo) Date: Sat, 9 Oct 2010 02:37:13 -0600 Subject: Question about expired bugs. In-Reply-To: <201010090428.31550.macoafi@gmail.com> References: <201010090428.31550.macoafi@gmail.com> Message-ID: Thanks that answered my question that I should follow the invalidating process. Still would like to know when the bugs automatically get marked for expired. On Sat, Oct 9, 2010 at 2:28 AM, Mackenzie Morgan wrote: > On Saturday, October 09, 2010 04:01:10 am tuxmaster geekstogo wrote: > > I noticed I had a bunch of subscribed bugs that state "This bug report > was > > marked for expiration X days ago." > > > > Does that mean that the bug is expired? > > When does the bug get marked as expired? > > Bugs used to be closed automatically when they expired. This was disabled. > So > now it's saying "if that feature were enabled, this would have been closed > due > to the reporter ignoring it." > > > More or less do I need to do anything with these. Do I need to do the I > > thought once they were expired they got taken off the list should I go > > though the process of invalidating these bugs? > > Check what the last few comments were. Were they "can you please respond > or > do you just not care and we should close this?" or were they the original > "hey > can you give a screenshot?" If the latter, prompt for a response. If the > former and it's been months since that prompt, then closing is ok. > > -- > Mackenzie Morgan > http://mackenzie.morgan.name > http://ubuntulinuxtipstricks.blogspot.com > > -- > 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 marcelcoding at googlemail.com Sat Oct 9 08:39:23 2010 From: marcelcoding at googlemail.com (Marcel Stimberg) Date: Sat, 9 Oct 2010 10:39:23 +0200 Subject: Question about expired bugs. In-Reply-To: <201010090428.31550.macoafi@gmail.com> References: <201010090428.31550.macoafi@gmail.com> Message-ID: > Bugs used to be closed automatically when they expired. This was disabled. So > now it's saying "if that feature were enabled, this would have been closed due > to the reporter ignoring it." Actually, the feature is back again: http://blog.launchpad.net/general/enabling-automatic-bug-expiry As I understood it, for Ubuntu projects auto-expiry will be activated by default. Best, Marcel From macoafi at gmail.com Sat Oct 9 15:22:12 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sat, 9 Oct 2010 11:22:12 -0400 Subject: Question about expired bugs. In-Reply-To: References: <201010090428.31550.macoafi@gmail.com> Message-ID: <201010091122.13188.macoafi@gmail.com> On Saturday, October 09, 2010 04:39:23 am Marcel Stimberg wrote: > > Bugs used to be closed automatically when they expired. This was > > disabled. So now it's saying "if that feature were enabled, this would > > have been closed due to the reporter ignoring it." > > Actually, the feature is back again: > http://blog.launchpad.net/general/enabling-automatic-bug-expiry > As I understood it, for Ubuntu projects auto-expiry will be activated > by default. The emails that were sent out said the feature was back but that all the teams' auto-expire settings were being reset to off and would have to be re- enabled manually. Did someone do that? -- Mackenzie Morgan http://mackenzie.morgan.name http://ubuntulinuxtipstricks.blogspot.com From marcelcoding at googlemail.com Sat Oct 9 15:36:39 2010 From: marcelcoding at googlemail.com (Marcel Stimberg) Date: Sat, 9 Oct 2010 17:36:39 +0200 Subject: Question about expired bugs. In-Reply-To: <201010091122.13188.macoafi@gmail.com> References: <201010090428.31550.macoafi@gmail.com> <201010091122.13188.macoafi@gmail.com> Message-ID: > The emails that were sent out said the feature was back but that all the > teams' auto-expire settings were being reset to off and would have to be re- > enabled manually.  Did someone do that? I have no idea, I was just referring to this sentence in the launchpad blog post: "For maintainers of Ubuntu packages in Launchpad, we have left this option enabled." I understood that in all "normal" launchpad projects it is disabled and has to be enabled manually, the exception being Ubuntu projects where it is already enabled. But I might be wrong and I do not manage any launchpad projects so I can't check... Marcel From macoafi at gmail.com Sat Oct 9 15:49:35 2010 From: macoafi at gmail.com (Mackenzie Morgan) Date: Sat, 9 Oct 2010 11:49:35 -0400 Subject: Question about expired bugs. In-Reply-To: References: <201010091122.13188.macoafi@gmail.com> Message-ID: <201010091149.35753.macoafi@gmail.com> On Saturday, October 09, 2010 11:36:39 am Marcel Stimberg wrote: > > The emails that were sent out said the feature was back but that all the > > teams' auto-expire settings were being reset to off and would have to be > > re- enabled manually. Did someone do that? > > I have no idea, I was just referring to this sentence in the launchpad > blog post: > "For maintainers of Ubuntu packages in Launchpad, we have left this > option enabled." > > I understood that in all "normal" launchpad projects it is disabled > and has to be enabled manually, the exception being Ubuntu projects > where it is already enabled. But I might be wrong and I do not manage > any launchpad projects so I can't check... Oh, ok. I saw Kubuntu Devel get an email claiming it was off, so I got confused, but I guess that was just an automated send-out to every team or something. -- Mackenzie Morgan http://mackenzie.morgan.name http://ubuntulinuxtipstricks.blogspot.com From tuxmaster at geekstogo.com Sat Oct 9 23:58:26 2010 From: tuxmaster at geekstogo.com (tuxmaster geekstogo) Date: Sat, 9 Oct 2010 17:58:26 -0600 Subject: Unable to reproduce and Submitter has purchased new hardware. Message-ID: But 528277. The bug sumbitter is no longer able to reproduce. There is 5 people effected by this bug. Should I set this to invalid. anzenketh. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordon at envygeeks.com Sun Oct 10 00:00:10 2010 From: jordon at envygeeks.com (Jordon Bedwell) Date: Sat, 09 Oct 2010 19:00:10 -0500 Subject: Unable to reproduce and Submitter has purchased new hardware. In-Reply-To: References: Message-ID: <1286668810.14661.19.camel@envygeeks> On Sat, 2010-10-09 at 17:58 -0600, tuxmaster geekstogo wrote: > But 528277. The bug sumbitter is no longer able to reproduce. There is > 5 people effected by this bug. Should I set this to invalid. > > anzenketh. I would just ask for an elaboration. If other people are affected then other people can help provide more details. That's just my opinion on the subject though. From tuxmaster at geekstogo.com Sun Oct 10 00:44:41 2010 From: tuxmaster at geekstogo.com (tuxmaster geekstogo) Date: Sat, 9 Oct 2010 18:44:41 -0600 Subject: Should A bug be set to triaged. Message-ID: Trying to figure out what do with bug 529270. Reporter has found out how to get it working. Would this still be a bug or considered invalid. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/529270 -- ~anzenketh -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Sun Oct 10 01:41:45 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sat, 09 Oct 2010 21:41:45 -0400 Subject: Should A bug be set to triaged. In-Reply-To: References: Message-ID: <4CB119D9.8040104@gmail.com> Sounds like it's still a bug to me. If it was detected before and not detected now, that's a regression. Hope it helps, David On 10/09/2010 08:44 PM, tuxmaster geekstogo wrote: > Trying to figure out what do with bug 529270. Reporter has found out how > to get it working. Would this still be a bug or considered invalid. > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/529270 > > -- > ~anzenketh > From hggdh2 at ubuntu.com Sun Oct 10 01:55:21 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sat, 9 Oct 2010 20:55:21 -0500 Subject: Unable to reproduce and Submitter has purchased new hardware. In-Reply-To: References: Message-ID: <20101009205521.44869ddb@xango2> On Sat, 9 Oct 2010 17:58:26 -0600 tuxmaster geekstogo wrote: > But 528277. The bug sumbitter is no longer able to reproduce. There > is 5 people effected by this bug. Should I set this to invalid. Usually, since you have just asked for more data, we should wait two weeks (at least) before closing INVALID, if no others pipe in. But Pedro has already asked for more data on 2010-08-24, and nobody else answered. As such, please go ahead and close INVALID, with a blurb like: ---begin blurb--- Given that: * you cannot reproduce anymore * video issues should each have its own bugs (since it is quite uncommon for the hardware to *exactly* match) We are closing this bug INVALID. @all: if you are still experiencing issues with the video card, please open a new bug using ubuntu-bug/apport. Thank you. ---end blurb--- Cheers, -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From hggdh2 at ubuntu.com Sun Oct 10 01:59:39 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sat, 9 Oct 2010 20:59:39 -0500 Subject: Should A bug be set to triaged. In-Reply-To: <4CB119D9.8040104@gmail.com> References: <4CB119D9.8040104@gmail.com> Message-ID: <20101009205939.3abb2a7e@xango2> On Sat, 09 Oct 2010 21:41:45 -0400 David Tombs wrote: > Sounds like it's still a bug to me. If it was detected before and not > detected now, that's a regression. > > Hope it helps, > David > > On 10/09/2010 08:44 PM, tuxmaster geekstogo wrote: > > Trying to figure out what do with bug 529270. Reporter has found > > out how to get it working. Would this still be a bug or considered > > invalid. > > > > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/529270 Indeed. We need the make and model, plus a 'lsusb -v -d 12d1:1003', and then we need to check if the kernel lists this hardware. Cheers, -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From abhijit.foss at gmail.com Sun Oct 10 15:33:54 2010 From: abhijit.foss at gmail.com (Abhijit Navale) Date: Sun, 10 Oct 2010 21:03:54 +0530 Subject: Mentorship expiry Message-ID: Hello. I am having my exams in december. So I will be unable to participate actively on regular basis on bug squad. So I request that let the mentorship membership be expire for now, and I will again join the mentorship after my exams in January. I am writing this email after a little chat in #ubuntu-bugs with hggdh. Please let me know what you have decided. Thank you. -- Abhijit Navale. Blog | Ubuntu | Free Softwares Simplicity is the ultimate sophistication - Leonardo Da Vinci. -------------- next part -------------- An HTML attachment was scrubbed... URL: From andrey at dunin.us Sun Oct 10 17:33:07 2010 From: andrey at dunin.us (Dunin, Andrey) Date: Sun, 10 Oct 2010 17:33:07 +0000 (UTC) Subject: Good day, im new Message-ID: <13885781421286731987654@fastmobile.com> Good day! Im new to the group and would like to be an active member in the quality/bug squad. In the future I would like to take on a role in the development team as well. I have been an ubuntu user ever since the early stages of it and I am pleased to have an oppurtunity to give back to the hard working ubuntu community! Andrey From cyan.spam at gmail.com Sun Oct 10 20:42:15 2010 From: cyan.spam at gmail.com (David Tombs) Date: Sun, 10 Oct 2010 16:42:15 -0400 Subject: Good day, im new In-Reply-To: <13885781421286731987654@fastmobile.com> References: <13885781421286731987654@fastmobile.com> Message-ID: <4CB22527.6050407@gmail.com> Hi Andrey, Welcome, we're glad to have you! Please feel free to ask any questions you may have. David On 10/10/2010 01:33 PM, Dunin, Andrey wrote: > Good day! > > Im new to the group and would like to be an active member in the quality/bug squad. In the future I would like to take on a role in the development team as well. > > I have been an ubuntu user ever since the early stages of it and I am pleased to have an oppurtunity to give back to the hard working ubuntu community! > > Andrey > > From brian at ubuntu.com Mon Oct 11 14:51:16 2010 From: brian at ubuntu.com (Brian Murray) Date: Mon, 11 Oct 2010 07:51:16 -0700 Subject: Question about expired bugs. In-Reply-To: References: <201010090428.31550.macoafi@gmail.com> <201010091122.13188.macoafi@gmail.com> Message-ID: <20101011145116.GC20251@murraytwins.com> On Sat, Oct 09, 2010 at 05:36:39PM +0200, Marcel Stimberg wrote: > > The emails that were sent out said the feature was back but that all the > > teams' auto-expire settings were being reset to off and would have to be re- > > enabled manually.  Did someone do that? > I have no idea, I was just referring to this sentence in the launchpad > blog post: > "For maintainers of Ubuntu packages in Launchpad, we have left this > option enabled." > > I understood that in all "normal" launchpad projects it is disabled > and has to be enabled manually, the exception being Ubuntu projects > where it is already enabled. But I might be wrong and I do not manage > any launchpad projects so I can't check... The exception is actually the Ubuntu distribution in Launchpad which did not have bug expiration turned off for it. -- 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 cyan.spam at gmail.com Mon Oct 11 23:27:47 2010 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 11 Oct 2010 19:27:47 -0400 Subject: Question about expired bugs. In-Reply-To: <20101011145116.GC20251@murraytwins.com> References: <201010090428.31550.macoafi@gmail.com> <201010091122.13188.macoafi@gmail.com> <20101011145116.GC20251@murraytwins.com> Message-ID: <4CB39D73.50905@gmail.com> Thanks, Brian. Do you have a reference for that? David On 10/11/2010 10:51 AM, Brian Murray wrote: > On Sat, Oct 09, 2010 at 05:36:39PM +0200, Marcel Stimberg wrote: >>> The emails that were sent out said the feature was back but that all the >>> teams' auto-expire settings were being reset to off and would have to be re- >>> enabled manually. Did someone do that? >> I have no idea, I was just referring to this sentence in the launchpad >> blog post: >> "For maintainers of Ubuntu packages in Launchpad, we have left this >> option enabled." >> >> I understood that in all "normal" launchpad projects it is disabled >> and has to be enabled manually, the exception being Ubuntu projects >> where it is already enabled. But I might be wrong and I do not manage >> any launchpad projects so I can't check... > > The exception is actually the Ubuntu distribution in Launchpad which > did not have bug expiration turned off for it. > > From alans002 at gmail.com Tue Oct 12 08:36:33 2010 From: alans002 at gmail.com (Alans) Date: Tue, 12 Oct 2010 11:36:33 +0300 Subject: 10.10 Evolution and ppp connection Message-ID: <4CB41E11.6010003@gmail.com> Hello, I'm new here, there is 2 things i noticed in Ubuntu 10.10 RC first, when i click on date on the panel the calendar shows in the middle on the screen not on top of the panel bar! second, when i use gnome-ppp (wvdial), ubuntu network manager doesn't recognize that it's connected to internet so Evolution starts in Offline mode and I can't make it go online, before upgrading to 10.10 i was able to make Evolution go online by clicking on the plug icon down left. regards, Alans From par.sarnblad at gmail.com Tue Oct 12 08:10:43 2010 From: par.sarnblad at gmail.com (=?iso-8859-1?Q?P=E4r_S=E4rnblad?=) Date: Tue, 12 Oct 2010 10:10:43 +0200 Subject: Touchpad on MacBook Pro Message-ID: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> Hi I tried out 10.10 and the touch/track pad works but some problems arise. Two finger clicks generates a rightclick but while pressed there is no way to move the cursor. Another thing is that there seems that the pad generates a right click if two fingers are on the pad, which is troublesome instead of checking the distance between the fingers like it is done in MacOS. Also macos seems to ignore the leftmost finger if two of them are on the pad. /P From noreply at ubuntu.com Tue Oct 12 07:55:54 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 12 Oct 2010 07:55:54 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_heymrdjd?= Message-ID: <20101012075554.23043.87476@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 heymrdjd: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=20&rev2=21 The comment on the change is: corrected various grammatical/spelling errors, capitalized Touchpad to provide consistency throughout page ------------------------------------------------------------------------------ = Introduction = Problems with touchpad detection typically fall into one of these categories: - 1. Your touchpad doesn't work at all. + 1. Your Touchpad doesn't work at all. - 1. Your touchpad stops working after a while. + 1. Your Touchpad stops working after a while. - 1. Features of Mouse works but features of Touchpad(like Tapping, Scrolling) does not work at all. + 1. Features of Mouse works but features of Touchpad (like Tapping, Scrolling) does not work at all. - 1. Some features of your touchpad like scrolling, tapping, dragging don't work as expected. + 1. Some features of your Touchpad like scrolling, tapping, dragging don't work as expected. <> = How to file the bug report = - Consider this document on filing touchpad bugs with relevant information. Before filing a bug please check the list of known bugs at the end of this document. If your are unsure to which package the bug should be filed or your problem is not listed in any of the categories then, in general file your touchpad related bugs against '''xserver-xorg-input-synaptics'''. If the bug turns out to be a bug related to kernel('''linux''') or any other package, bug triagers will assign your bug additionally to that package and mark the task related to xserver-xorg-input-synaptics, as invalid. + Consider this document on filing Touchpad bugs with relevant information. Before filing a bug please check the list of known bugs at the end of this document. If your are unsure to which package the bug should be filed or your problem is not listed in any of the categories then, in general file your touchpad related bugs against '''xserver-xorg-input-synaptics'''. If the bug turns out to be a bug related to kernel('''linux''') or any other package, bug triagers will assign your bug additionally to that package and mark the task related to xserver-xorg-input-synaptics, as invalid. == General information before filing the bug == This information should be provided in the bug description itself: @@ -25, +25 @@ Sample Description - 'ALPS Touchpad' incorrectly detected as PS/2 mouse in 'Sony Vaio VPCCW16FG' after the kernel upgrade. - However if you think that the bug is a general one with the type of the touchpad and is irrespective of the Laptop model you could omit mentioning the Laptop model in the description. But only consider doing this, when you are very sure that the bug is affecting all laptops with that touchpad model. + However if you think that the bug is a general one with the type of the Touchpad and is irrespective of the Laptop model you could omit mentioning the Laptop model in the description. But only consider doing this, when you are very sure that the bug is affecting all laptops with that Touchpad model. - == In case your touchpad doesn't work at all (No response from the touchpad) == + == In case your Touchpad doesn't work at all (No response from the Touchpad) == This is generally a case of kernel('''linux''') or '''xorg''' bug. Check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} 4. Press Crtl+Alt+F7 to switch back to X. 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. - Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} @@ -60, +60 @@ $ dmesg > ~/dmesg }}} 1. Attach {{{~/dmesg}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. - == In case your touchpad stops working after a while == + == In case your Touchpad stops working after a while == This is generally a case of kernel('''linux''') or '''xorg''' bug. In this case, in description field, specify the steps to make the touchpad stop working. eg- hit a key, drag or something. Now check by connecting a mouse that if it works or not. If no, then you should file the bug against '''HAL''' and follow the steps below. 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. {{{ + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. {{{ $ cp /var/log/Xorg.0.log ~/Xorg.0.log }}} 4. Press Crtl+Alt+F7 to switch back to X. - 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in seperate attachments. + 3. Add {{{~/evtest}}} and {{{Xorg.o.log}}} to the bug report in separate attachments. - Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} @@ -101, +101 @@ $ diff -ns ~/Xorg.0.log ~/Xorg.0.log_tmp > ~/Xorg.0.log_diff }}} 1. Attach {{{~/dmesg_boot}}}, {{{~/dmesg_diff}}}, {{{~/Xorg.0.log}}} and {{{~/Xorg.0.log_diff}}} to the bug report in separate attachments. - == In case your touchpad features like scrolling, tapping, etc does not work at all. == + == In case Touchpad features like scrolling, tapping, etc do not work at all. == This happens when 'Touchpad' Tab is not there in System>Preferences>Mouse. @@ -109, +109 @@ To check whether to report for kernel or not {{{ $ cat /proc/bus/input/devices >~/devices }}} - If this include the name of your touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal + If the output includes the name of your Touchpad eg Name="SynPS/2 Synaptics TouchPad", then kernel has detected it right. In this case, please don't report the bug against the kernel, rather report it against '''HAL'''. For more information on reporting bugs against HAL, refer DebuggingHal In any case, include the outputs of the following commands: {{{ $ cat /proc/bus/input/devices >~/devices @@ -120, +120 @@ '''IMP :''' Please do not file bug against the kernel unless you are very sure that it should be filed and do it only after reading this whole document. If you are unsure, file it against xserver-xorg-input-synaptics, somebody will change to kernel if is so. - == In case your atleast one of touchpad features works but does not work correctly and as expected == + == In case at least one of Touchpad features works but does not work correctly and as expected == - eg - Jumpy cursor, scrolling problems, touchpad area is misdetected, circular scrolling, buttons not correctly mapped. + eg - Jumpy cursor, scrolling problems, Touchpad area is misdetected, circular scrolling, buttons not correctly mapped. 1. Enter the following command in a terminal/console: {{{ $ xmodmap -pp >~/xmodmap $ xinput --list-props >~/xinput }}} 1. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 2. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 2. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. 4. Press Crtl+Alt+F7 to switch back to X. 5. Attach {{{~/xmodmap}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. - In {{{ xinput --list-props }}}, is of your touchpad in {{{ xinput --list }}}. + In {{{ xinput --list-props }}}, is of your Touchpad in {{{ xinput --list }}}. - Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} @@ -154, +154 @@ This bug is common in Synaptics Touchpad V7.2 where multitouch works perfect in windows but not in linux. This is not a bug related to xserver-xorg-input-synaptics. Multitouch capabilities are not detected but the kernel itself as evident in {{{ xinput --list-props }}} shows {{{ Synaptics Capabilities (277): 1, 1, 1, 0, 0 }}} - This bug is already known (see the '''Known bugs''' below). In this case please don't file any new bugs and instead add a comment in the existing bug for any relevent information that you have. + This bug is already known (see the '''Known bugs''' below). In this case please don't file any new bugs and instead add a comment in the existing bug for any relevant information that you have. - '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. + '''NOTE :''' Synaptics is not willing to disclose the protocol it uses for the multitouch support for its newer Touchpads. As soon as Synaptics come up with its protocol, this issue will be fixed. So this is not a bug in general. So it has been classified as a wishlist. 1. For any other case, include the outputs in the bug report in separate comments. {{{ $ xinput --list-props >~/xinput }}} 2. Switch to a VT using Crtl+Alt+F2 and enter following in your terminal {{{ $ sudo evtest /dev/input/eventX > ~/evtest }}} - 3. Scroll, tap, drag, press buttons and create various other possible events on the touchpad and then press CTRL+C to exit. + 3. Scroll, tap, drag, press buttons and create various other possible events on the Touchpad and then press CTRL+C to exit. 4. Press Crtl+Alt+F7 to switch back to X. - 5. Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. {{{ + 5. Take your pointer in the windows and hold down your two fingers on the Touchpad and raise. Also try to tap with two fingers. {{{ $ xev | grep -i button > ~/xev}}} 6. Attach {{{~/xev}}}, {{{~/xinput}}} and your {{{~/evtest}}} to the bug report in separate attachments. In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. - Check your {{{ /dev/input/eventX }}} for your touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this + Check your {{{ /dev/input/eventX }}} for your Touchpad in {{{ cat /proc/bus/input/devices }}} , you may see something like this {{{ I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 }}} {{{ N: Name="SynPS/2 Synaptics TouchPad" }}} @@ -188, +188 @@ = Some general work flow for Triagers = - If the features of your touchpad (like Tapping, Scrolling) does '''not''' work at all. In this case user will not see the '''Touchpad''' Tab in System>Administration>Mouse in Main menu. This means that Touchpad is misdetected as PS/2 mouse. Here the following workflow must be followed. + If the features of your Touchpad (like Tapping, Scrolling) do '''not''' work at all. In this case, user will not see the '''Touchpad''' Tab in System>Administration>Mouse in Main menu. This means that Touchpad is misdetected as PS/2 mouse. Here the following workflow must be followed. - 1. Check weather Kernel has detected the touchpad or not by the following. {{{ + 1. Check whether Kernel has detected the Touchpad or not by the following. {{{ $ cat /proc/bus/input/devices }}} - If a touchpad is detected, then something like following will appear. + If a Touchpad is detected, then something like following will appear. '''Name="SynPS/2 Synaptics TouchPad"''' - If touchpad is not detected then following will appear. In this case the bug must be a kernel issue. + If Touchpad is not detected then following will appear. In this case the bug must be a kernel issue. '''Name="ImPS/2 Generic Wheel Mouse"''' - 2. Check weather xserver has detected the touchpad correctly by. {{{ + 2. Check whether xserver has detected the Touchpad correctly by. {{{ $ xinput --list }}} - You will see the same name of touchpad as above. + You will see the same name of Touchpad as above. 3. Check weather synaptics module is correctly loaded in xserver or not in. {{{ $cat /var/log/Xorg.0.log | grep -i synaptics }}} @@ -229, +229 @@ Synaptics Touchpad is incorrectly detected by kernel https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/565543 ---- - CategoryBugSquad CategoryDebugging + CategoryBugSquad CategoryDebugging CategoryCleanup From brian at ubuntu.com Tue Oct 12 14:28:33 2010 From: brian at ubuntu.com (Brian Murray) Date: Tue, 12 Oct 2010 07:28:33 -0700 Subject: Question about expired bugs. In-Reply-To: <4CB39D73.50905@gmail.com> References: <201010090428.31550.macoafi@gmail.com> <201010091122.13188.macoafi@gmail.com> <20101011145116.GC20251@murraytwins.com> <4CB39D73.50905@gmail.com> Message-ID: <20101012142833.GJ20251@murraytwins.com> On Mon, Oct 11, 2010 at 07:27:47PM -0400, David Tombs wrote: > Thanks, Brian. Do you have a reference for that? Not really as I just looked at the configuration option in Launchpad. -- 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 andrey at dunin.us Tue Oct 12 14:44:54 2010 From: andrey at dunin.us (Andrey Dunin) Date: Tue, 12 Oct 2010 10:44:54 -0400 Subject: Touchpad on MacBook Pro In-Reply-To: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> References: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> Message-ID: Pär Särnblad, Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the time it would be beneficial for you to run a live cd (or usb) of Ubuntu 9.04 or 10.04 and see if the problem persists there. On Tue, Oct 12, 2010 at 4:10 AM, Pär Särnblad wrote: > Hi > > I tried out 10.10 and the touch/track pad works but some problems arise. > Two finger clicks generates a rightclick but while pressed there is no way > to move the cursor. > Another thing is that there seems that the pad generates a right click if > two fingers are on the pad, which is > troublesome instead of checking the distance between the fingers like it > is done in MacOS. Also macos seems to > ignore the leftmost finger if two of them are on the pad. > > /P > -- > 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 henriqueqc at gmail.com Tue Oct 12 17:10:14 2010 From: henriqueqc at gmail.com (Henrique Camargo) Date: Tue, 12 Oct 2010 14:10:14 -0300 Subject: Touchpad on MacBook Pro In-Reply-To: References: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> Message-ID: 10.10 is the first with multitouch. -- Henrique Camargo On Tue, Oct 12, 2010 at 11:44 AM, Andrey Dunin wrote: > Pär Särnblad, > > Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the > time it would be beneficial for you to run a live cd (or usb) of Ubuntu 9.04 > or 10.04 and see if the problem persists there. > > On Tue, Oct 12, 2010 at 4:10 AM, Pär Särnblad > wrote: >> >> Hi >> >> I tried out 10.10 and the touch/track pad works but some problems arise. >> Two finger clicks generates a rightclick but while pressed there is no way >> to move the cursor. >> Another thing is that there seems that the pad generates a right click if >> two fingers are on the pad, which is >> troublesome instead of checking the distance  between the fingers like it >> is done in MacOS. Also macos seems to >> ignore the leftmost finger if two of them are on the pad. >> >> /P >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > From firas at fkraiem.org Tue Oct 12 17:15:37 2010 From: firas at fkraiem.org (Firas Kraiem) Date: Tue, 12 Oct 2010 19:15:37 +0200 Subject: Touchpad on MacBook Pro In-Reply-To: References: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> Message-ID: <4CB497B9.5060000@fkraiem.org> On 12/10/2010 19:10, Henrique Camargo wrote: > 10.10 is the first with multitouch. Two-finger scrolling and right-clicking worked for me in Lucid. (Right now my Maverick is broken so I can't say if I also have this problem, I'll reinstall soon-ish.) Firas > > -- > Henrique Camargo > > > > On Tue, Oct 12, 2010 at 11:44 AM, Andrey Dunin wrote: >> Pär Särnblad, >> >> Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the >> time it would be beneficial for you to run a live cd (or usb) of Ubuntu 9.04 >> or 10.04 and see if the problem persists there. >> >> On Tue, Oct 12, 2010 at 4:10 AM, Pär Särnblad >> wrote: >>> >>> Hi >>> >>> I tried out 10.10 and the touch/track pad works but some problems arise. >>> Two finger clicks generates a rightclick but while pressed there is no way >>> to move the cursor. >>> Another thing is that there seems that the pad generates a right click if >>> two fingers are on the pad, which is >>> troublesome instead of checking the distance between the fingers like it >>> is done in MacOS. Also macos seems to >>> ignore the leftmost finger if two of them are on the pad. >>> >>> /P >>> -- >>> Ubuntu-bugsquad mailing list >>> Ubuntu-bugsquad at lists.ubuntu.com >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> >> > From henriqueqc at gmail.com Tue Oct 12 17:36:22 2010 From: henriqueqc at gmail.com (henriqueqc at gmail.com) Date: Tue, 12 Oct 2010 14:36:22 -0300 Subject: Touchpad on MacBook Pro In-Reply-To: <4CB497B9.5060000@fkraiem.org> References: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> <4CB497B9.5060000@fkraiem.org> Message-ID: Didn't know that, sorry for the miss-information. -- Henrique Camargo On Tue, Oct 12, 2010 at 2:15 PM, Firas Kraiem wrote: > On 12/10/2010 19:10, Henrique Camargo wrote: >> 10.10 is the first with multitouch. > > Two-finger scrolling and right-clicking worked for me in Lucid. (Right > now my Maverick is broken so I can't say if I also have this problem, > I'll reinstall soon-ish.) > > Firas > >> >> -- >> Henrique Camargo >> >> >> >> On Tue, Oct 12, 2010 at 11:44 AM, Andrey Dunin wrote: >>> Pär Särnblad, >>> >>> Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the >>> time it would be beneficial for you to run a live cd (or usb) of Ubuntu 9.04 >>> or 10.04 and see if the problem persists there. >>> >>> On Tue, Oct 12, 2010 at 4:10 AM, Pär Särnblad >>> wrote: >>>> >>>> Hi >>>> >>>> I tried out 10.10 and the touch/track pad works but some problems arise. >>>> Two finger clicks generates a rightclick but while pressed there is no way >>>> to move the cursor. >>>> Another thing is that there seems that the pad generates a right click if >>>> two fingers are on the pad, which is >>>> troublesome instead of checking the distance  between the fingers like it >>>> is done in MacOS. Also macos seems to >>>> ignore the leftmost finger if two of them are on the pad. >>>> >>>> /P >>>> -- >>>> Ubuntu-bugsquad mailing list >>>> Ubuntu-bugsquad at lists.ubuntu.com >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> >>> >>> -- >>> Ubuntu-bugsquad mailing list >>> Ubuntu-bugsquad at lists.ubuntu.com >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >>> >>> >> > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From bcurtiswx at ubuntu.com Tue Oct 12 18:07:26 2010 From: bcurtiswx at ubuntu.com (Brian Curtis) Date: Tue, 12 Oct 2010 14:07:26 -0400 Subject: Meeting Minutes: 2010 10 12 Message-ID: Hey all, Thanks to those who attended and added great discussion to todays meeting. The following if the log from today's meeting. Thanks to our new meeting bot, minutes are simple. If you wish to continue a discussion from here, please create a new thread for it as it will make following it very easy. http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt Best, ~Brian Curtis (bcurtiswx) -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" ---------------------------------------------------------------- The Statement Below is True The Statement Above is False ---------------------------------------------------------------- From noreply at ubuntu.com Tue Oct 12 18:14:56 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 12 Oct 2010 18:14:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/Meeting/Minutes=22_by_b?= =?utf-8?q?curtiswx?= Message-ID: <20101012181456.28086.40987@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 bcurtiswx: http://wiki.ubuntu.com/BugSquad/Meeting/Minutes?action=diff&rev1=9&rev2=10 ------------------------------------------------------------------------------ <> == 2010 == - + * [[http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt|2010-10-12]] <--- Started using meetingology a meeting bot. * [[BugSquad/Meeting/Minutes/2010-01-19]] == 2009 == From ilidrissiamine at gmail.com Tue Oct 12 19:27:09 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Tue, 12 Oct 2010 19:27:09 +0000 Subject: Handling bugs from foreign language speakers Message-ID: Hi all, Currently, we (bug triagers and users of Launchpad in general) only accept bug reports and comments in English. This can cause a problem, since it's nearly impossible for speakers of a language other than English to post a bug report ; in the end, we're losing an opportunity to improve Ubuntu by fixing nasty bugs. So how can we improve this situation? In our recent meeting, two possibilities (I think) were discussed: - Include the option of translating the bug via Google Translate's API. I don't think this is a good idea, since the translation isn't guaranteed to be good, which can lead to confusion in technical talks IMO. - Have a small group of bug triagers in each local community, who would triage bugs from native/foreign speakers and then send them to Launchpad with the appropriate translation. So what's your point of view? Please share it :) Thank you, Mohamed Amine IL Idrissi From andrey at dunin.us Tue Oct 12 19:54:11 2010 From: andrey at dunin.us (Andrey Dunin) Date: Tue, 12 Oct 2010 15:54:11 -0400 Subject: Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: All, Mohammed brings up a very good point! Ubuntu has a user-base in almost every country around the world. Not everyone can explain their problem well in English thus it can cause many bugs not fixed. Here is how I would handle this issue: 1. Conduct a survey to find out the ammount of users there are whose dominant language is other than English. 2. Assign ACTIVE cordinators for each one of these languages, if a language does not have many users, assign 1. For more widespread languages like Spanish - Multiple will be needed. 3. Bugs are submitted through a general form, but the user is able to chose his native language which will then send the bug over to a translator. 4. Translator translates the bug and it is released to the general public for viewing. An issue with the above can be that the translator can in one point decide that he doesnt feel like translating no more. If he is the only translator for the language -- we are stuck. I am willing to take on the translation for the Ukrainian and Russian languages since I speak them fluently. This is not something that she be ignored since there are MANY non-english speaking users around the world and I know many of them which is funny since I live in the United States :) Lets hear some more feedback! Andrey On Tue, Oct 12, 2010 at 3:27 PM, Mohammed Amine IL Idrissi < ilidrissiamine at gmail.com> wrote: > Hi all, > > Currently, we (bug triagers and users of Launchpad in general) only > accept bug reports and comments in English. This can cause a problem, > since it's nearly impossible for speakers of a language other than > English to post a bug report ; in the end, we're losing an opportunity > to improve Ubuntu by fixing nasty bugs. > > So how can we improve this situation? In our recent meeting, two > possibilities (I think) were discussed: > - Include the option of translating the bug via Google Translate's API. > I don't think this is a good idea, since the translation isn't > guaranteed to be good, which can lead to confusion in technical talks > IMO. > - Have a small group of bug triagers in each local community, who > would triage bugs from native/foreign speakers and then send them to > Launchpad with the appropriate translation. > > So what's your point of view? Please share it :) > > Thank you, > Mohamed Amine IL Idrissi > > -- > 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 rkeidel at gmail.com Tue Oct 12 20:14:37 2010 From: rkeidel at gmail.com (Robert Keidel) Date: Tue, 12 Oct 2010 13:14:37 -0700 Subject: Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: Hello, my name is Robert and I attended the meeting the first time today. I followed the conversation with interested. I am dual language (English/German), with German as my native language. A few years back my English was not as good as today, and I found myself trying very had to explain something in English that would be so easy to do in my native language. I believe there are more people that have similar experience. I like the approach of Andrey and I willing to participate for the translation of German language. Robert On Tue, Oct 12, 2010 at 12:54 PM, Andrey Dunin wrote: > All, > > Mohammed brings up a very good point! Ubuntu has a user-base in almost > every country around the world. Not everyone can explain their problem well > in English thus it can cause many bugs not fixed. > Here is how I would handle this issue: > > 1. Conduct a survey to find out the ammount of users there are whose > dominant language is other than English. > > 2. Assign ACTIVE cordinators for each one of these languages, if a language > does not have many users, assign 1. For more widespread languages like > Spanish - Multiple will be needed. > > 3. Bugs are submitted through a general form, but the user is able to chose > his native language which will then send the bug over to a translator. > > 4. Translator translates the bug and it is released to the general public > for viewing. > > > An issue with the above can be that the translator can in one point decide > that he doesnt feel like translating no more. If he is the only translator > for the language -- we are stuck. > > I am willing to take on the translation for the Ukrainian and Russian > languages since I speak them fluently. > > This is not something that she be ignored since there are MANY non-english > speaking users around the world and I know many of them which is funny since > I live in the United States :) > > > Lets hear some more feedback! > > Andrey > > On Tue, Oct 12, 2010 at 3:27 PM, Mohammed Amine IL Idrissi < > ilidrissiamine at gmail.com> wrote: > >> Hi all, >> >> Currently, we (bug triagers and users of Launchpad in general) only >> accept bug reports and comments in English. This can cause a problem, >> since it's nearly impossible for speakers of a language other than >> English to post a bug report ; in the end, we're losing an opportunity >> to improve Ubuntu by fixing nasty bugs. >> >> So how can we improve this situation? In our recent meeting, two >> possibilities (I think) were discussed: >> - Include the option of translating the bug via Google Translate's API. >> I don't think this is a good idea, since the translation isn't >> guaranteed to be good, which can lead to confusion in technical talks >> IMO. >> - Have a small group of bug triagers in each local community, who >> would triage bugs from native/foreign speakers and then send them to >> Launchpad with the appropriate translation. >> >> So what's your point of view? Please share it :) >> >> Thank you, >> Mohamed Amine IL Idrissi >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad >> > > > -- > 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 braiamp at gmail.com Tue Oct 12 21:24:34 2010 From: braiamp at gmail.com (Braiam Miguel Peguero Novo) Date: Tue, 12 Oct 2010 17:24:34 -0400 Subject: Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: Hi, About it, apport and launchpad can handle this better for us, because it can tag the reports as they arrive as it need translation, and in the case of apport use the en locale always that it send a crash report. Hopping that this help. Braiam Peguero launchpad ID ~braiamp -------------- next part -------------- An HTML attachment was scrubbed... URL: From ilidrissiamine at gmail.com Tue Oct 12 21:29:00 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Tue, 12 Oct 2010 21:29:00 +0000 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: <1286913266.2180.16.camel@teej-Aspire-M1640> References: <1286913266.2180.16.camel@teej-Aspire-M1640> Message-ID: On Tue, Oct 12, 2010 at 7:54 PM, Roy Jamison wrote: > > Just BugControl, what about BugSquad? :) > > To reiterate what I said on IRC; I do think it would be a good idea if > the Loco-bug-filing people/teams are willing to keep it at, otherwise > it's a futile effort. > > Google translate may be another option; I know that it isn't perfect and > not the ideal solution, but it can usually give you a good idea of the > jist of the sentence. > > > The big question is, either way, how would this be implemented? It would > demand a restructure of bug reporting, creation of LP teams, mailing > lists, changing the wiki, etc. This is all assuming that people are > going to do what you tell them (they don't), i.e. "you need to contact > if you speak and they will report the bug for you". > It doesn't mean that the reporter will bother, especially if they are > considerably peed off about a bug; ending up filing it in > Google-translate-elngnlish (intentional) anyway. > > What about obscure languages with one or two users? > > Don't get me wrong, it'd be a great idea if it works, but truthfully I > can't see it at the moment. > > Teej > > > > On Tue, 2010-10-12 at 19:27 +0000, Mohammed Amine IL Idrissi wrote: >> Hi all, >> >> Currently, we (bug triagers and users of Launchpad in general) only >> accept bug reports and comments in English. This can cause a problem, >> since it's nearly impossible for speakers of a language other than >> English to post a bug report ; in the end, we're losing an opportunity >> to improve Ubuntu by fixing nasty bugs. >> >> So how can we improve this situation? In our recent meeting, two >> possibilities (I think) were discussed: >> - Include the option of translating the bug via Google Translate's API. >>   I don't think this is a good idea, since the translation isn't >> guaranteed to be good, which can lead to confusion in technical talks >> IMO. >> - Have a small group of bug triagers in each local community, who >> would triage bugs from native/foreign speakers and then send them to >> Launchpad with the appropriate translation. >> >> So what's your point of view? Please share it :) >> >> Thank you, >> Mohamed Amine IL Idrissi >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~ubuntu-bugcontrol >> Post to     : ubuntu-bugcontrol at lists.launchpad.net >> Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol >> More help   : https://help.launchpad.net/ListHelp > > (Forwarded ; please send to all the list next time) Here's one approach: (Taking the French community as an example) 1. Foreign user wants to report a bug ; the community documentation redirects him to a bugzilla set by the community. 2. Bug triagers from the French community triages the bug according to the usual guidelines that we follow in Launchpad. The French bug triager group can contain members from the BugSquad team that understands French (like me ;)), and other members that will know over due time how to triage efficiently (but they have to have some experience though). 3. When the bug is fully triaged, it is translated and sent to Launchpad, with a bug watcher set to follow the bug in the above bugzilla. What do you think of this? Thank you, Mohamed Amine IL Idrissi From costamagnagianfranco at yahoo.it Tue Oct 12 21:36:35 2010 From: costamagnagianfranco at yahoo.it (Gianfranco Costamagna) Date: Tue, 12 Oct 2010 22:36:35 +0100 (BST) Subject: Ubuntu-bugsquad Digest, Vol 52, Issue 14 In-Reply-To: References: Message-ID: <255733.24585.qm@web26701.mail.ukl.yahoo.com> I'm italian but I speak fluently French and English... I could help :) ----- Messaggio originale ----- > Da: "ubuntu-bugsquad-request at lists.ubuntu.com" > > A: ubuntu-bugsquad at lists.ubuntu.com > Inviato: Mar 12 ottobre 2010, 23:24:38 > Oggetto: Ubuntu-bugsquad Digest, Vol 52, Issue 14 > > Send Ubuntu-bugsquad mailing list submissions to > ubuntu-bugsquad at lists.ubuntu.com > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > or, via email, send a message with subject or body 'help' to > ubuntu-bugsquad-request at lists.ubuntu.com > > You can reach the person managing the list at > ubuntu-bugsquad-owner at lists.ubuntu.com > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Ubuntu-bugsquad digest..." > > > Today's Topics: > > 1. Re: Touchpad on MacBook Pro (henriqueqc at gmail.com) > 2. Meeting Minutes: 2010 10 12 (Brian Curtis) > 3. [Ubuntu Wiki] Update of "BugSquad/Meeting/Minutes" by > bcurtiswx (Ubuntu Wiki) > 4. Handling bugs from foreign language speakers > (Mohammed Amine IL Idrissi) > 5. Re: Handling bugs from foreign language speakers (Andrey Dunin) > 6. Re: Handling bugs from foreign language speakers (Robert Keidel) > 7. Re: Handling bugs from foreign language speakers > (Braiam Miguel Peguero Novo) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Oct 2010 14:36:22 -0300 > From: "henriqueqc at gmail.com" > Subject: Re: Touchpad on MacBook Pro > To: Firas Kraiem > Cc: ubuntu-bugsquad at lists.ubuntu.com > Message-ID: > > Content-Type: text/plain; charset=UTF-8 > > Didn't know that, sorry for the miss-information. > > -- > Henrique Camargo > > > > On Tue, Oct 12, 2010 at 2:15 PM, Firas Kraiem wrote: > > On 12/10/2010 19:10, Henrique Camargo wrote: > >> 10.10 is the first with multitouch. > > > > Two-finger scrolling and right-clicking worked for me in Lucid. (Right > > now my Maverick is broken so I can't say if I also have this problem, > > I'll reinstall soon-ish.) > > > > Firas > > > >> > >> -- > >> Henrique Camargo > >> > >> > >> > >> On Tue, Oct 12, 2010 at 11:44 AM, Andrey Dunin wrote: > >>> P?r S?rnblad, > >>> > >>> Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the > >>> time it would be beneficial for you to run a live cd (or usb) of Ubuntu >9.04 > >>> or 10.04 and see if the problem persists there. > >>> > >>> On Tue, Oct 12, 2010 at 4:10 AM, P?r S?rnblad > >>> wrote: > >>>> > >>>> Hi > >>>> > >>>> I tried out 10.10 and the touch/track pad works but some problems arise. > >>>> Two finger clicks generates a rightclick but while pressed there is no >way > >>>> to move the cursor. > >>>> Another thing is that there seems that the pad generates a right click if > >>>> two fingers are on the pad, which is > >>>> troublesome instead of checking the distance ?between the fingers like it > >>>> is done in MacOS. Also macos seems to > >>>> ignore the leftmost finger if two of them are on the pad. > >>>> > >>>> /P > >>>> -- > >>>> Ubuntu-bugsquad mailing list > >>>> Ubuntu-bugsquad at lists.ubuntu.com > >>>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>> > >>> > >>> -- > >>> Ubuntu-bugsquad mailing list > >>> Ubuntu-bugsquad at lists.ubuntu.com > >>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >>> > >>> > >> > > > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Oct 2010 14:07:26 -0400 > From: Brian Curtis > Subject: Meeting Minutes: 2010 10 12 > To: Ubuntu BugSquad , Ubuntu Bug > Control > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hey all, > > Thanks to those who attended and added great discussion to todays > meeting. The following if the log from today's meeting. Thanks to > our new meeting bot, minutes are simple. If you wish to continue a > discussion from here, please create a new thread for it as it will > make following it very easy. > >http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt >t > > Best, > ~Brian Curtis (bcurtiswx) > > -- > Research is what I'm doing when I don't know what I'm doing. > --Wernher Von Braun > "The second law of thermodynamics: If you think things are in a mess > now, JUST WAIT!!" > ---------------------------------------------------------------- > The Statement Below is True > The Statement Above is False > ---------------------------------------------------------------- > > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Oct 2010 18:14:56 -0000 > From: Ubuntu Wiki > Subject: [Ubuntu Wiki] Update of "BugSquad/Meeting/Minutes" by > bcurtiswx > To: Ubuntu Wiki > Message-ID: <20101012181456.28086.40987 at jostaberry.canonical.com> > Content-Type: text/plain; charset="utf-8" > > 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 bcurtiswx: > http://wiki.ubuntu.com/BugSquad/Meeting/Minutes?action=diff&rev1=9&rev2=10 > > ------------------------------------------------------------------------------ > <> > > == 2010 == > - > + * >[[http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt|2010-10-12]] > <--- Started using meetingology a meeting bot. > * [[BugSquad/Meeting/Minutes/2010-01-19]] > > == 2009 == > > > > ------------------------------ > > Message: 4 > Date: Tue, 12 Oct 2010 19:27:09 +0000 > From: Mohammed Amine IL Idrissi > Subject: Handling bugs from foreign language speakers > To: Ubuntu Bug Squad , > ubuntu-bugcontrol at lists.launchpad.net > Message-ID: > > Content-Type: text/plain; charset=ISO-8859-1 > > Hi all, > > Currently, we (bug triagers and users of Launchpad in general) only > accept bug reports and comments in English. This can cause a problem, > since it's nearly impossible for speakers of a language other than > English to post a bug report ; in the end, we're losing an opportunity > to improve Ubuntu by fixing nasty bugs. > > So how can we improve this situation? In our recent meeting, two > possibilities (I think) were discussed: > - Include the option of translating the bug via Google Translate's API. > I don't think this is a good idea, since the translation isn't > guaranteed to be good, which can lead to confusion in technical talks > IMO. > - Have a small group of bug triagers in each local community, who > would triage bugs from native/foreign speakers and then send them to > Launchpad with the appropriate translation. > > So what's your point of view? Please share it :) > > Thank you, > Mohamed Amine IL Idrissi > > > > ------------------------------ > > Message: 5 > Date: Tue, 12 Oct 2010 15:54:11 -0400 > From: Andrey Dunin > Subject: Re: Handling bugs from foreign language speakers > To: Mohammed Amine IL Idrissi > Cc: ubuntu-bugcontrol at lists.launchpad.net, Ubuntu Bug Squad > > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > All, > > Mohammed brings up a very good point! Ubuntu has a user-base in almost every > country around the world. Not everyone can explain their problem well in > English thus it can cause many bugs not fixed. > Here is how I would handle this issue: > > 1. Conduct a survey to find out the ammount of users there are whose > dominant language is other than English. > > 2. Assign ACTIVE cordinators for each one of these languages, if a language > does not have many users, assign 1. For more widespread languages like > Spanish - Multiple will be needed. > > 3. Bugs are submitted through a general form, but the user is able to chose > his native language which will then send the bug over to a translator. > > 4. Translator translates the bug and it is released to the general public > for viewing. > > > An issue with the above can be that the translator can in one point decide > that he doesnt feel like translating no more. If he is the only translator > for the language -- we are stuck. > > I am willing to take on the translation for the Ukrainian and Russian > languages since I speak them fluently. > > This is not something that she be ignored since there are MANY non-english > speaking users around the world and I know many of them which is funny since > I live in the United States :) > > > Lets hear some more feedback! > > Andrey > > On Tue, Oct 12, 2010 at 3:27 PM, Mohammed Amine IL Idrissi < > ilidrissiamine at gmail.com> wrote: > > > Hi all, > > > > Currently, we (bug triagers and users of Launchpad in general) only > > accept bug reports and comments in English. This can cause a problem, > > since it's nearly impossible for speakers of a language other than > > English to post a bug report ; in the end, we're losing an opportunity > > to improve Ubuntu by fixing nasty bugs. > > > > So how can we improve this situation? In our recent meeting, two > > possibilities (I think) were discussed: > > - Include the option of translating the bug via Google Translate's API. > > I don't think this is a good idea, since the translation isn't > > guaranteed to be good, which can lead to confusion in technical talks > > IMO. > > - Have a small group of bug triagers in each local community, who > > would triage bugs from native/foreign speakers and then send them to > > Launchpad with the appropriate translation. > > > > So what's your point of view? Please share it :) > > > > Thank you, > > Mohamed Amine IL Idrissi > > > > -- > > 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: >https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20101012/d130b29c/attachment-0001.htm > > > ------------------------------ > > Message: 6 > Date: Tue, 12 Oct 2010 13:14:37 -0700 > From: Robert Keidel > Subject: Re: Handling bugs from foreign language speakers > To: ubuntu-bugcontrol at lists.launchpad.net, Ubuntu Bug Squad > > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Hello, > > my name is Robert and I attended the meeting the first time today. I > followed the conversation with interested. I am dual language > (English/German), with German as my native language. A few years back my > English was not as good as today, and I found myself trying very had to > explain something in English that would be so easy to do in my native > language. I believe there are more people that have similar experience. I > like the approach of Andrey and I willing to participate for the translation > of German language. > > Robert > > > > On Tue, Oct 12, 2010 at 12:54 PM, Andrey Dunin wrote: > > > All, > > > > Mohammed brings up a very good point! Ubuntu has a user-base in almost > > every country around the world. Not everyone can explain their problem well > > in English thus it can cause many bugs not fixed. > > Here is how I would handle this issue: > > > > 1. Conduct a survey to find out the ammount of users there are whose > > dominant language is other than English. > > > > 2. Assign ACTIVE cordinators for each one of these languages, if a language > > does not have many users, assign 1. For more widespread languages like > > Spanish - Multiple will be needed. > > > > 3. Bugs are submitted through a general form, but the user is able to chose > > his native language which will then send the bug over to a translator. > > > > 4. Translator translates the bug and it is released to the general public > > for viewing. > > > > > > An issue with the above can be that the translator can in one point decide > > that he doesnt feel like translating no more. If he is the only translator > > for the language -- we are stuck. > > > > I am willing to take on the translation for the Ukrainian and Russian > > languages since I speak them fluently. > > > > This is not something that she be ignored since there are MANY non-english > > speaking users around the world and I know many of them which is funny since > > I live in the United States :) > > > > > > Lets hear some more feedback! > > > > Andrey > > > > On Tue, Oct 12, 2010 at 3:27 PM, Mohammed Amine IL Idrissi < > > ilidrissiamine at gmail.com> wrote: > > > >> Hi all, > >> > >> Currently, we (bug triagers and users of Launchpad in general) only > >> accept bug reports and comments in English. This can cause a problem, > >> since it's nearly impossible for speakers of a language other than > >> English to post a bug report ; in the end, we're losing an opportunity > >> to improve Ubuntu by fixing nasty bugs. > >> > >> So how can we improve this situation? In our recent meeting, two > >> possibilities (I think) were discussed: > >> - Include the option of translating the bug via Google Translate's API. > >> I don't think this is a good idea, since the translation isn't > >> guaranteed to be good, which can lead to confusion in technical talks > >> IMO. > >> - Have a small group of bug triagers in each local community, who > >> would triage bugs from native/foreign speakers and then send them to > >> Launchpad with the appropriate translation. > >> > >> So what's your point of view? Please share it :) > >> > >> Thank you, > >> Mohamed Amine IL Idrissi > >> > >> -- > >> Ubuntu-bugsquad mailing list > >> Ubuntu-bugsquad at lists.ubuntu.com > >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > >> > > > > > > -- > > 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: >https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20101012/b7c6a7c7/attachment-0001.htm > > > ------------------------------ > > Message: 7 > Date: Tue, 12 Oct 2010 17:24:34 -0400 > From: Braiam Miguel Peguero Novo > Subject: Re: Handling bugs from foreign language speakers > To: Andrey Dunin > Cc: Ubuntu-bugsquad at lists.ubuntu.com > Message-ID: > > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > About it, apport and launchpad can handle this better for us, because it can > tag the reports as they arrive as it need translation, and in the case of > apport use the en locale always that it send a crash report. > > Hopping that this help. > > Braiam Peguero > launchpad ID ~braiamp > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: >https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20101012/bcd97ed8/attachment.htm > > > ------------------------------ > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > End of Ubuntu-bugsquad Digest, Vol 52, Issue 14 > *********************************************** > From kamusin at gmail.com Tue Oct 12 23:01:18 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 12 Oct 2010 20:01:18 -0300 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: On Tue, Oct 12, 2010 at 4:27 PM, Mohammed Amine IL Idrissi wrote: > Hi all, > Hey! > Currently, we (bug triagers and users of Launchpad in general) only > accept bug reports and comments in English. This can cause a problem, > since it's nearly impossible for speakers of a language other than > English to post a bug report ; in the end, we're losing an opportunity > to improve Ubuntu by fixing nasty bugs. > So how can we improve this situation? In our recent meeting, two > possibilities (I think) were discussed: > - Include the option of translating the bug via Google Translate's API. >  I don't think this is a good idea, since the translation isn't > guaranteed to be good, which can lead to confusion in technical talks > IMO. We could add a link/use an api/ linked to a website like Google Translate, Babelfish, etc, with the original message translated in our 'Universal' language English (Previously Launchpad or something need detect that original paragraphs are not in English). Additionally we can add a special tag such needs-translations-LANGUAGE, for example: "needs-translation-es" and then we can assign to the appropiate Translation team. Then they can add a translated edition or attached a translated version conserving the original report for the record (native spokens could read both versions). > - Have a small group of bug triagers in each local community, who > would triage bugs from native/foreign speakers and then send them to > Launchpad with the appropriate translation. > yeah, why not :) > So what's your point of view? Please share it :) > > Thank you, > Mohamed Amine IL Idrissi > Regards, Victor -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From ben.root at ou.edu Tue Oct 12 23:47:52 2010 From: ben.root at ou.edu (Benjamin Root) Date: Tue, 12 Oct 2010 18:47:52 -0500 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: Just a thought, could we use one of the translation APIs to automatically identify and tag a report according to language? Ben Root On Tue, Oct 12, 2010 at 6:01 PM, Kamus wrote: > On Tue, Oct 12, 2010 at 4:27 PM, Mohammed Amine IL Idrissi > wrote: > > Hi all, > > > Hey! > > > Currently, we (bug triagers and users of Launchpad in general) only > > accept bug reports and comments in English. This can cause a problem, > > since it's nearly impossible for speakers of a language other than > > English to post a bug report ; in the end, we're losing an opportunity > > to improve Ubuntu by fixing nasty bugs. > > So how can we improve this situation? In our recent meeting, two > > possibilities (I think) were discussed: > > - Include the option of translating the bug via Google Translate's API. > > I don't think this is a good idea, since the translation isn't > > guaranteed to be good, which can lead to confusion in technical talks > > IMO. > We could add a link/use an api/ linked to a website like Google > Translate, Babelfish, etc, with the original message translated in our > 'Universal' language English (Previously Launchpad or something need > detect that original paragraphs are not in English). Additionally we > can add a special tag such needs-translations-LANGUAGE, for example: > "needs-translation-es" and then we can assign to the appropiate > Translation team. Then they can add a translated edition or attached a > translated version conserving the original report for the record > (native spokens could read both versions). > > > - Have a small group of bug triagers in each local community, who > > would triage bugs from native/foreign speakers and then send them to > > Launchpad with the appropriate translation. > > > yeah, why not :) > > > So what's your point of view? Please share it :) > > > > Thank you, > > Mohamed Amine IL Idrissi > > > > Regards, > Victor > > -- > Victor Vargas B. > Latitud: -33.439177,-70.625267 > Santiago, Chile. > > -- > 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 kamusin at gmail.com Wed Oct 13 01:46:50 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 12 Oct 2010 22:46:50 -0300 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: On Tue, Oct 12, 2010 at 8:47 PM, Benjamin Root wrote: > Just a thought, could we use one of the translation APIs to automatically > identify and tag a report according to language? > Technically we can use http://code.google.com/intl/en/apis/ajaxlanguage/ for translations (theorically), but in the side of Launchpad I'm not sure how to do it, appart of doing manually (maybe add a rutine to Launchpad Bots?). > Ben Root > > On Tue, Oct 12, 2010 at 6:01 PM, Kamus wrote: >> >> On Tue, Oct 12, 2010 at 4:27 PM, Mohammed Amine IL Idrissi >> wrote: >> > Hi all, >> > >> Hey! >> >> > Currently, we (bug triagers and users of Launchpad in general) only >> > accept bug reports and comments in English. This can cause a problem, >> > since it's nearly impossible for speakers of a language other than >> > English to post a bug report ; in the end, we're losing an opportunity >> > to improve Ubuntu by fixing nasty bugs. >> > So how can we improve this situation? In our recent meeting, two >> > possibilities (I think) were discussed: >> > - Include the option of translating the bug via Google Translate's API. >> >  I don't think this is a good idea, since the translation isn't >> > guaranteed to be good, which can lead to confusion in technical talks >> > IMO. >> We could add a link/use an api/  linked to a website like Google >> Translate, Babelfish, etc, with the original message translated in our >> 'Universal'  language English (Previously Launchpad or something need >> detect that original paragraphs are not in English). Additionally we >> can add a special tag such needs-translations-LANGUAGE, for example: >> "needs-translation-es" and then we can assign to the appropiate >> Translation team. Then they can add a translated edition or attached a >> translated version conserving the original report for the record >> (native spokens could read both versions). >> >> > - Have a small group of bug triagers in each local community, who >> > would triage bugs from native/foreign speakers and then send them to >> > Launchpad with the appropriate translation. >> > >> yeah, why not :) >> >> > So what's your point of view? Please share it :) >> > >> > Thank you, >> > Mohamed Amine IL Idrissi >> > >> >> Regards, >> Victor >> >> -- >> Victor Vargas B. >> Latitud:  -33.439177,-70.625267 >> Santiago, Chile. >> >> -- >> Ubuntu-bugsquad mailing list >> Ubuntu-bugsquad at lists.ubuntu.com >> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From par.sarnblad at gmail.com Wed Oct 13 05:52:15 2010 From: par.sarnblad at gmail.com (=?iso-8859-1?Q?P=E4r_S=E4rnblad?=) Date: Wed, 13 Oct 2010 07:52:15 +0200 Subject: Touchpad on MacBook Pro In-Reply-To: References: <1763334B-B90E-4E1A-A4BA-79E8729C5A87@gmail.com> Message-ID: <47D73B0E-16C3-47C7-8CDF-81145817EFB0@gmail.com> Hi I've been thinking a bit. Since using 2 fingers for right-clicking AND scrolling this might be the problem I'm facing with the right-click menu since the application thinks I'm scrolling when I want to move the cursor. Simplified a few rules that may apply: if tracking with two fingers if right or left button is pressed move cursor else scroll "tracking with two fingers" should be defined as Two fingers moving (or in the case of clicking just being - ) around (2.5cm / 1 inch or less apart. One finger is stationary on the pad, usually my left thumb and should be ignored. Currently I don't have much time for testing due to a kitchen rebuild but as mentioned 10.10 is the first release with multitouch support and testing with earlier versions might not be very useful. /P On Oct 12, 2010, at 4:44 PM, Andrey Dunin wrote: > Pär Särnblad, > > Any idea if this issue occurs on Ubuntu 10.04 or earlier? If you have the time it would be beneficial for you to run a live cd (or usb) of Ubuntu 9.04 or 10.04 and see if the problem persists there. > > On Tue, Oct 12, 2010 at 4:10 AM, Pär Särnblad wrote: > Hi > > I tried out 10.10 and the touch/track pad works but some problems arise. > Two finger clicks generates a rightclick but while pressed there is no way to move the cursor. > Another thing is that there seems that the pad generates a right click if two fingers are on the pad, which is > troublesome instead of checking the distance between the fingers like it is done in MacOS. Also macos seems to > ignore the leftmost finger if two of them are on the pad. > > /P > -- > 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 jean-baptiste at ubuntu.com Wed Oct 13 09:06:20 2010 From: jean-baptiste at ubuntu.com (Jean-Baptiste Lallement) Date: Wed, 13 Oct 2010 11:06:20 +0200 Subject: Meeting Minutes: 2010 10 12 In-Reply-To: References: Message-ID: <4CB5768C.4010208@ubuntu.com> On 10/12/2010 08:07 PM, Brian Curtis wrote: > Hey all, > > Thanks to those who attended and added great discussion to todays > meeting. The following if the log from today's meeting. Thanks to > our new meeting bot, minutes are simple. If you wish to continue a > discussion from here, please create a new thread for it as it will > make following it very easy. > > http://mootbot.libertus.co.uk/ubuntu-bugs/2010/ubuntu-bugs.2010-10-12-16.57.moin.txt > Thanks for the minutes. I'll take the actions: ** to prepare a bug day excepting kernel ** to clean up the Regression wiki pages One other point, I think it's worth copy/pasting the minutes to the wiki because we have control over the document (edit it, keep it forever if we want, ...) -- Jean-Baptiste irc: jibel From jean-baptiste at ubuntu.com Wed Oct 13 09:30:48 2010 From: jean-baptiste at ubuntu.com (Jean-Baptiste Lallement) Date: Wed, 13 Oct 2010 11:30:48 +0200 Subject: Proposing regression bugs process simplification. In-Reply-To: <4CA1AC1A.9080006@ubuntu.com> References: <4CA1AC1A.9080006@ubuntu.com> Message-ID: <4CB57C48.4000100@ubuntu.com> On 09/28/2010 10:49 AM, Jean-Baptiste Lallement wrote: > Hello all! > > Some of us on the QA Team, have been thinking about the current process > with regression tags. One of our goals is to make bug reporting and bug > triage as least complicated as possible. We have been reviewing the bugs > with a regression-* tag and it appears that we need a change to make it > simpler. > > The report [1] gives an overview of the state of regression bugs. We > have found that many regression-potential bugs are filed against a > released version and need to be promoted or demoted and targeted to the > right release(s). At release time we should have evaluated what to > convert from regression-potential to regression-release, but it's hard > to keep track once the release is out and change all tags. > > Most of the time the regression-potential tag is used as a backseat to > regression-release or interpreted as a 'regression to be confirmed'. So > using regression-potential requires extra work: > - mark it as regression-potential > - confirm it is a regression > - nominate > - confirm it is *not* a regression > - remove tag from bug > - when the release is out, verify all 'regression-potential' > - change to 'regression-release' if correct > - nominate > - otherwise, remove tag. > > We feel this could be made easier. > > So, we have studied many ways to make it simpler and are proposing the > following change to the current process: > keep only 3 tags: > - regression-release, > - regression-updates > - regression-proposed > > depending on the pocket - and nominating / targeting to every release > the regression as it is today whatever the release is (development or > released). We think that's all what we need for a nice clean regression > work flow. > With the feedback we received and the release of 10.10 we are going to implement the changes: - Mark regressions as regression-(release|proposed|update) followed by the version we found it in - promote/demote regression reports tagged as regression-potential We will organize a bug day soon to triage the reports marked as regression-potential. If you have any question/comment/complaint or whatever about this change, don't hesitate to comment. > > > [1] https://wiki.ubuntu.com/JeanBaptisteLallement/RegressionReport > > -- Jean-Baptiste irc: jibel From xteejyx at googlemail.com Wed Oct 13 10:18:32 2010 From: xteejyx at googlemail.com (Roy Jamison) Date: Wed, 13 Oct 2010 11:18:32 +0100 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: <1286965112.2178.7.camel@teej-Aspire-M1640> Actually, I've just had a thought and it incorporates both ideas. There is no reason why we couldn't do both, i.e. if someone *only* speaks English, there is no reason why they couldn't translate it themselves. Use Google translate or Babelfish or whatever, and translate the "broken English" output from that into something legible. Then everyone can do a bit and play their part. Obviously obscure languages with <100 Ubuntu users would need to be done manually by a human. Just an idea :) -- Roy Jamison (xteejx) Ubuntu Bug Squad Ubuntu Bug Control www.ubuntu.com From jordon at envygeeks.com Wed Oct 13 10:24:31 2010 From: jordon at envygeeks.com (Jordon Bedwell) Date: Wed, 13 Oct 2010 05:24:31 -0500 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: <1286965112.2178.7.camel@teej-Aspire-M1640> References: <1286965112.2178.7.camel@teej-Aspire-M1640> Message-ID: <1286965471.31965.3.camel@envygeeks> On Wed, 2010-10-13 at 11:18 +0100, Roy Jamison wrote: > Actually, I've just had a thought and it incorporates both ideas. > There is no reason why we couldn't do both, i.e. if someone *only* > speaks English, there is no reason why they couldn't translate it > themselves. Use Google translate or Babelfish or whatever, and translate > the "broken English" output from that into something legible. > > Then everyone can do a bit and play their part. Obviously obscure > languages with <100 Ubuntu users would need to be done manually by a > human. > > Just an idea :) Or... automatically: http://code.google.com/apis/ajaxlanguage recently I had the chance to work with a company that was using that exact API to do on the fly translations of their entire website. Mixing Google Ajax API with JQuery you get some pretty powerful results. From xteejyx at googlemail.com Wed Oct 13 10:42:33 2010 From: xteejyx at googlemail.com (Roy Jamison) Date: Wed, 13 Oct 2010 11:42:33 +0100 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers In-Reply-To: <1286965471.31965.3.camel@envygeeks> References: <1286965112.2178.7.camel@teej-Aspire-M1640> <1286965471.31965.3.camel@envygeeks> Message-ID: <1286966553.2178.20.camel@teej-Aspire-M1640> I think the point was not to have machine translated garble, as it's not 100% foolproof and sometimes technical things can be erroneous. :) Not a bad idea if we can tag it with something like "tr-needs-verification-de" or whatever language it is and clean it up afterwards, whether that be a native speaker or English. On Wed, 2010-10-13 at 05:24 -0500, Jordon Bedwell wrote: > On Wed, 2010-10-13 at 11:18 +0100, Roy Jamison wrote: > > Actually, I've just had a thought and it incorporates both ideas. > > There is no reason why we couldn't do both, i.e. if someone *only* > > speaks English, there is no reason why they couldn't translate it > > themselves. Use Google translate or Babelfish or whatever, and translate > > the "broken English" output from that into something legible. > > > > Then everyone can do a bit and play their part. Obviously obscure > > languages with <100 Ubuntu users would need to be done manually by a > > human. > > > > Just an idea :) > > Or... automatically: http://code.google.com/apis/ajaxlanguage recently I > had the chance to work with a company that was using that exact API to > do on the fly translations of their entire website. Mixing Google Ajax > API with JQuery you get some pretty powerful results. > -- Roy Jamison (xteejx) Ubuntu Bug Squad Ubuntu Bug Control www.ubuntu.com From noreply at ubuntu.com Wed Oct 13 07:44:13 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 13 Oct 2010 07:44:13 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_era?= Message-ID: <20101013074413.32630.36453@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/Bugs/Responses?action=diff&rev1=306&rev2=307 The comment on the change is: Moving Firefox and ffmpeg into package-specific section ------------------------------------------------------------------------------ ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't start working on it yet, because your bug report didn't include enough information.<
><
>Please include the information requested at https://wiki.ubuntu.com/DebuggingNetworkManager. If you have trouble, do not hesitate to ask for more assistance. Thanks in advance.|| + === Debugging Firefox === + + ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs? Also, please answer these questions:<
>Is this crash reproducible? If so, which are the steps that lead to it?<
>Which flash package do you have installed?<
>Which Java package do you have installed?<
>Which Firefox extensions do you have installed?<
><
>This will greatly aid us in tracking down your problem.|| + + ==== Firefox crash report that fails retrace ==== + Firefox bug triaging policy is to close (set to "invalid") crash reports from apport that fail retracing. + + ||Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashes again with the latest available version of the package. Thanks in advance for your cooperation and understanding. || + === Debugging Samba === <> @@ -94, +103 @@ === Debugging Openldap === <> + + === Debugging ffmpeg (mostly libavcodec and libavformat bugs) === + + ||Thank you for taking the time to report this bug and helping to make Ubuntu better. You have reported a crash that actually happened in the libavcodec or libavformat library. In order to be able to actually fix this bug, we must be able to:<
><
>1. Reproduce it;<
>2. Check if it happens with the latest version; and<
>3. Understand where it actually crashes.<
><
>You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote sites that are password protected or otherwise restricted (services like rapidshare.com) are absolutely not acceptable. If your file is too large, try to reproduce with the first few MB only. See http://ffmpeg.org/bugreports.html section "Submitting Sample Media" for guidelines.<
><
>Please also make sure that your file crashes with the commandline application ''ffplay'' from the '''ffmpeg''' package. If the crash does not happen with that tool, the bug does not belong to the '''ffmpeg''' package, but to some higher-level package like '''libxine1-ffmpeg''' or '''gstreamer0.10-ffmpeg''' (depending on what player has been used)|| === Debugging SCIM related issues === @@ -145, +158 @@ || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.<
><
>If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.<
><
>If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your {{{/var/crash}}} directory and double click on the crash report you wish to submit.<
>If you are using Kubuntu or Xubuntu you can file the crash using {{{/usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash}}} in a terminal - where _my_crash_report.crash is the crash you would like to report.<
><
>I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.|| - == Firefox crash report that fails retrace == - Firefox bug triaging policy is to close (set to "invalid") crash reports from apport that fail retracing. - - ||Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report didn't yield the required information. Please go ahead and submit a new crash report if it crashes again with the latest available version of the package. Thanks in advance for your cooperation and understanding. || == A duplicate == When making a bug report a duplicate of another it is important to communicate to the reporter that any discussion regarding the bug should take place in the master bug. Keep in mind that NUMBER is a placeholder and should be the number of the master bug report. @@ -197, +206 @@ ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || - == ffmpeg (mostly libavcodec and libavformat) bugs == - - ||Thank you for taking the time to report this bug and helping to make Ubuntu better. You have reported a crash that actually happened in the libavcodec or libavformat library. In order to be able to actually fix this bug, we must be able to:<
><
>1. Reproduce it;<
>2. Check if it happens with the latest version; and<
>3. Understand where it actually crashes.<
><
>You can help with the first point by attaching an example file to this bug report. Please note that a proper attachment is preferred over a link to some remote site. Remote sites that are password protected or otherwise restricted (services like rapidshare.com) are absolutely not acceptable. If your file is too large, try to reproduce with the first few MB only. See http://ffmpeg.org/bugreports.html section "Submitting Sample Media" for guidelines.<
><
>Please also make sure that your file crashes with the commandline application ''ffplay'' from the '''ffmpeg''' package. If the crash does not happen with that tool, the bug does not belong to the '''ffmpeg''' package, but to some higher-level package like '''libxine1-ffmpeg''' or '''gstreamer0.10-ffmpeg''' (depending on what player has been used)|| == Packages not provided by Ubuntu == @@ -275, +281 @@ || Thank you for taking the time to report this bug and helping to make Ubuntu better. Translations in Ubuntu are handled by the [[https://launchpad.net/ubuntu-translations|Ubuntu Translations]] project, so we are going to move this bug report over to that project. || + - == Firefox == - ||Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please try to obtain a backtrace by following the instructions on https://wiki.ubuntu.com/MozillaTeam/Bugs? Also, please answer these questions:<
>Is this crash reproducible? If so, which are the steps that lead to it?<
>Which flash package do you have installed?<
>Which Java package do you have installed?<
>Which Firefox extensions do you have installed?<
><
>This will greatly aid us in tracking down your problem.|| == Incomplete Package Request == ||Thank you for taking the time to request this package and helping to make Ubuntu better. Unfortunately you have not provided enough information for a developer to start packaging this application. Please make sure this bug meets the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages. An example of a complete package request is available at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages/ExamplePackageRequest.|| From noreply at ubuntu.com Wed Oct 13 12:26:26 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 13 Oct 2010 12:26:26 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_yofel?= Message-ID: <20101013122626.27769.25885@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/Responses?action=diff&rev1=307&rev2=308 The comment on the change is: update devel release name ------------------------------------------------------------------------------ Before using this, ''please'' check "rmadison " to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Natty Narwhal. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| == Missing a crash report or having a .crash attachment == From bcurtiswx at ubuntu.com Wed Oct 13 13:17:57 2010 From: bcurtiswx at ubuntu.com (Brian Curtis) Date: Wed, 13 Oct 2010 09:17:57 -0400 Subject: Meeting Minutes: 2010 10 12 In-Reply-To: <4CB5768C.4010208@ubuntu.com> References: <4CB5768C.4010208@ubuntu.com> Message-ID: On Wed, Oct 13, 2010 at 5:06 AM, Jean-Baptiste Lallement wrote: > Thanks for the minutes. > I'll take the actions: >  ** to prepare a bug day excepting kernel >  ** to clean up the Regression wiki pages Look through the logs, talk with the people who volunteered at the meeting. I'm sure they can use the help, but they will be able to explain the tasks better to you. > One other point, I think it's worth copy/pasting the minutes to the wiki > because we have control over the document (edit it, keep it forever if > we want, ...) Feel Free, IDK how long those logs will last. I originally presumed indefinitely. ~Brian -- Research is what I'm doing when I don't know what I'm doing. --Wernher Von Braun "The second law of thermodynamics: If you think things are in a mess now, JUST WAIT!!" ---------------------------------------------------------------- The Statement Below is True The Statement Above is False ---------------------------------------------------------------- From yabruss at gmail.com Wed Oct 13 14:19:26 2010 From: yabruss at gmail.com (y baruss) Date: Wed, 13 Oct 2010 16:19:26 +0200 Subject: [Ubuntu-bugcontrol] Handling bugs from foreign language speakers Message-ID: Hello, Because some are talking about possible improvement into Launchpad bugtracker, I also note that it presents several differences with a "usual" bugtracker: * Users that report a bug cannot fill a version field that would help to sort item relevance (Hardy / Gusty / Lucid ...). * The same for the platform used (Intel / AMD / Nvidia / ATI ...). * Also it would certainly help if user could tick computer parts he feels to be related with its bug: Wireless / USB / Network / Mouse / Keyboard / Audio / Video ... (there a drawing can be perfect). For "other than English" language used for bug reporting discussion I would say: * Drawing and icons are international (music also ;o). * If for many people it is difficult to write into English, for most of them it as acceptable to read English and to select a multiple choice dialog box. * A language choice could be proposed to bug reporter and being just translated later (a sort of pre-New bug state). Regards. -------------- next part -------------- An HTML attachment was scrubbed... URL: From ilidrissiamine at gmail.com Wed Oct 13 15:18:51 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Wed, 13 Oct 2010 15:18:51 +0000 Subject: Feedback on HowToTriage Message-ID: Hi all, In our recent meeting, it was decided that I revamp the HowToTriage page to be clearer for newcomers. First of all, I'd like some feedback: - Is there something that is not well explained on the page? - Do you think there should be more images? - Is there something that should be plain removed? - ... Please give as much details as possible. Thank you, Mohamed Amine IL Idrissi From xteejyx at googlemail.com Wed Oct 13 16:23:47 2010 From: xteejyx at googlemail.com (Roy Jamison) Date: Wed, 13 Oct 2010 17:23:47 +0100 Subject: [Ubuntu-bugcontrol] Feedback on HowToTriage In-Reply-To: References: Message-ID: <1286987027.2201.20.camel@teej-Aspire-M1640> Hi Mohammed, I think it was decided during the meeting that it was going to be split into Basic and Advanced. Perhaps the Basic can have things like explanations and links to the Debugging Procedures wiki page, the different bug statuses, our workflow (to show *how* things work here), and package assignment. That's all I can think of right now, hope it helps a bit :) On Wed, 2010-10-13 at 15:18 +0000, Mohammed Amine IL Idrissi wrote: > Hi all, > > In our recent meeting, it was decided that I revamp the HowToTriage > page to be clearer for newcomers. First of all, I'd like some > feedback: > - Is there something that is not well explained on the page? > - Do you think there should be more images? > - Is there something that should be plain removed? > - ... > Please give as much details as possible. > > Thank you, > Mohamed Amine IL Idrissi > > _______________________________________________ > Mailing list: https://launchpad.net/~ubuntu-bugcontrol > Post to : ubuntu-bugcontrol at lists.launchpad.net > Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol > More help : https://help.launchpad.net/ListHelp -- Roy Jamison (xteejx) Ubuntu Bug Squad Ubuntu Bug Control www.ubuntu.com From noreply at ubuntu.com Wed Oct 13 16:38:23 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 13 Oct 2010 16:38:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_vish?= Message-ID: <20101013163823.28042.31716@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/Status?action=diff&rev1=52&rev2=53 The comment on the change is: Will this flood #ubuntu-bugs with more requests or encourage more new triagers? ;-) ------------------------------------------------------------------------------ * This helps ensure that the bug is applicable to Ubuntu in general, and not a problem with the reporter's system, therefore... * Please don't confirm your own bugs! * '''Triaged''': - * A member of [[UbuntuBugControl]] believes that the report describes a genuine bug in enough detail that a developer could start working on a fix + * A member of [[UbuntuBugControl]] believes that the report describes a genuine bug in enough detail that a developer could start working on a fix. ''(also see tip below)'' * Use this when you are confident that it should be looked at by a developer '''and''' has enough information * While not a requirement a bug's Ubuntu task status will be Triaged before any upstream forwarding occurs * '''In Progress''': @@ -72, +72 @@ * What should a triager do if a bug needs more information, including steps to reproduce, but the original reporter is not available to provide it? * Mark the bug as Invalid with a comment that the reporter should provide the information and reopen the bug by resetting its status to 'New'. + ||{{attachment:IconHelp2.png}}Not yet an [[https://wiki.ubuntu.com/UbuntuBugControl|Ubuntu Bug Control]] member? If you notice a bug having sufficient information and has not yet been set to Triaged, you'll have to ask someone who is to set the bug to ''Triaged'' 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 'Triaged' with importance 'Wishlist / Low / Medium / High / Critical' according to [[Bugs/Importance]]. Someone will notice your comment and set it for you, although not necessarily immediately.|| ---- CategoryBugSquad From marconifabio at hotmail.it Tue Oct 12 19:53:02 2010 From: marconifabio at hotmail.it (Fabio Marconi) Date: Tue, 12 Oct 2010 21:53:02 +0200 Subject: Handling bugs from foreign language speakers In-Reply-To: References: Message-ID: Il giorno Tue, 12/10/2010 alle 19.27 +0000, Mohammed Amine IL Idrissi ha scritto: > Hi all, > > Currently, we (bug triagers and users of Launchpad in general) only > accept bug reports and comments in English. This can cause a problem, > since it's nearly impossible for speakers of a language other than > English to post a bug report ; in the end, we're losing an opportunity > to improve Ubuntu by fixing nasty bugs. > > So how can we improve this situation? In our recent meeting, two > possibilities (I think) were discussed: > - Include the option of translating the bug via Google Translate's API. > I don't think this is a good idea, since the translation isn't > guaranteed to be good, which can lead to confusion in technical talks > IMO. > - Have a small group of bug triagers in each local community, who > would triage bugs from native/foreign speakers and then send them to > Launchpad with the appropriate translation. > > So what's your point of view? Please share it :) > > Thank you, > Mohamed Amine IL Idrissi > Hello Mohamed I think that local iso testing team can also help in triaging foreign languages bug. Seems to me a good idea. Fabio From cjk at teamcharliesangels.com Wed Oct 13 18:31:57 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Wed, 13 Oct 2010 12:31:57 -0600 Subject: Feedback on HowToTriage In-Reply-To: References: Message-ID: <20101013123157.58fc4ee0@teamcharliesangels.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 13 Oct 2010 15:18:51 +0000 Mohammed Amine IL Idrissi wrote: > Hi all, > > In our recent meeting, it was decided that I revamp the HowToTriage > page to be clearer for newcomers. First of all, I'd like some > feedback: > - Is there something that is not well explained on the page? > - Do you think there should be more images? > - Is there something that should be plain removed? > - ... > Please give as much details as possible. > > Thank you, > Mohamed Amine IL Idrissi > We have an excellent header we use to advertise when the next bugsquad meeting will be. It should be placed on all of our pages. Unfortunately, the way it is currently written may need changing. Perhaps the meeting header could be split out as its own header? We could have both https://wiki.ubuntu.com/BugSquad/Header and https://wiki.ubuntu.com/Header/Meetings , since there are two headers being used. Or, can we have the same header on all bugsquad pages? [1] <> - -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQEcBAEBAgAGBQJMtfsdAAoJEFNEIRz9dxbASjEH/RivTluhL5eSQOsC+KcJ5DtD CtXUvCzznE+tLlNhXjPaW/MjZQM6GWo0dWfb/ibR+A80NrjdPef2EFXTEak/ppBu iLwZLLY1L83mEojE4ugPKKJWJoQP7bvIZHywVBu9bQfXoQMm4iNYCN0jM9LUQpO1 BiDjh6fq6jf2X/lKUypbvObQ2UAsLAKtPmqiG/mTVZ+1X6c7I238S3LWguZhU90K ZVUZTOkrw7jP98Z2MNLrysA0XBnBi0ptlticLr+ZaKcwNWOz9DdZ/zmsZsyjReu1 Ii4QuAUHN2pQl0K3+PJlysR5o8Vm6r2XV0WcaoJ+o4QOTzE6xnfvLIledxM+gb0= =DMaF -----END PGP SIGNATURE----- From RedSingularity at gmx.com Wed Oct 13 19:44:07 2010 From: RedSingularity at gmx.com (RedSingularity) Date: Wed, 13 Oct 2010 15:44:07 -0400 Subject: Feedback on HowToTriage In-Reply-To: References: Message-ID: <4CB60C07.6060308@gmx.com> On 10/13/2010 11:18 AM, Mohammed Amine IL Idrissi wrote: > Hi all, > > In our recent meeting, it was decided that I revamp the HowToTriage > page to be clearer for newcomers. First of all, I'd like some > feedback: > - Is there something that is not well explained on the page? > - Do you think there should be more images? > - Is there something that should be plain removed? > - ... > Please give as much details as possible. > > Thank you, > Mohamed Amine IL Idrissi > > I am new to the scene and I think a step by step guide would be great! I know you cannot cover all situations but a general guide on working a bug from start to finish would be awesome. I know I have looked all over for such a guide. From noreply at ubuntu.com Fri Oct 15 20:36:00 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 15 Oct 2010 20:36:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_ilidrissi?= =?utf-8?q?=2Eamine?= Message-ID: <20101015203600.28164.60538@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 ilidrissi.amine: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=308&rev2=309 The comment on the change is: Removed "ubuntu-bug -p" and Jaunty reference. ------------------------------------------------------------------------------ The following packages or type of bugs require the specific debugging information: === Debugging Kernel General === - || Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.<
><
>Please run the following command which will attach necessary information:<
><
>{{{apport-collect BUGNUMBER}}}<
>if you are using Karmic Koala (9.10) or newer, or<
><
>{{{apport-collect -p linux-image-`uname -r` BUGNUMBER}}}<
>if you are using Jaunty Jackalope (9.04)<
><
>Bear in mind that you may need to install the python-launchpadlib package from the universe repository with '{{{sudo apt-get install python-launchpadlib}}}'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.<
><
>If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):<
>First run the following commands:<
>{{{1) uname -a > uname-a.log}}}<
>{{{2) dmesg > dmesg.log}}}<
>{{{3) sudo lspci -vvnn > lspci-vvnn.log}}}<
>{{{4) cat /proc/version_signature > version.log}}}<
>then '''attach''' the files separately to the bug report (not pasted into comments or tar/zip-ed).<
><
>For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.<
><
>Please run the following command which will attach necessary information:<
><
>{{{apport-collect BUGNUMBER}}}<
>if you are using Karmic Koala (9.10) or newer, or<
><
>{{{apport-collect -p linux-image-`uname -r` BUGNUMBER}}}<
>if you are using Hardy Heron (8.04)<
><
>Bear in mind that you may need to install the python-launchpadlib package from the universe repository with '{{{sudo apt-get install python-launchpadlib}}}'. Additionally, when prompted to give apport-collect permissions for Launchpad you will need to give it at least the ability to "Change Non-Private" data as it will be adding information to your bug report.<
><
>If you are using an older release or cannot use apport please at least add the following information (pay attention to lspci's additional options):<
>First run the following commands:<
>{{{1) uname -a > uname-a.log}}}<
>{{{2) dmesg > dmesg.log}}}<
>{{{3) sudo lspci -vvnn > lspci-vvnn.log}}}<
>{{{4) cat /proc/version_signature > version.log}}}<
>then '''attach''' the files separately to the bug report (not pasted into comments or tar/zip-ed).<
><
>For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies. Thanks in advance!|| === Debugging Sound Problems === - || Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.<
><
>Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.<
><
>If you are using Jaunty or later this information can be gathered for you automatically using the command ''apport-collect -p alsa-base BUGNUMBER''' where BUGNUMBER is the number of the bug you've reported.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. We need some more information from you before we can start working on this bug.<
><
>Please include the information requested from the "Reporting Sound Bugs" section of https://wiki.ubuntu.com/DebuggingSoundProblems as separate attachments.<
><
>If you are using Karmic or later this information can be gathered for you automatically using the command ''apport-collect -p alsa-base BUGNUMBER''' where BUGNUMBER is the number of the bug you've reported.|| === Debugging ACPI === From jimx89 at yahoo.com Mon Oct 18 22:48:58 2010 From: jimx89 at yahoo.com (Jim Gleason) Date: Mon, 18 Oct 2010 15:48:58 -0700 (PDT) Subject: annoying bug Message-ID: <113748.52076.qm@web114705.mail.gq1.yahoo.com> so i just restarted my computer, which i have been dualbooting ubuntu 10.10 and win7 on, and all of the sudden it told me that it was missing a file /dev/sfds2 and kept going into shell, ive tried safe mode but still the same thing. i love ubuntu and want to keep using it but if it is something that will happen normally i wont use it. im trying to get away from all those problems that windows has and this is even worse. as a note the hardware my computer is using is the same as when i restarted. SPC James T. GleasonVA Nat'l GuardCell (540)-842-5559 -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Oct 19 11:54:57 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 19 Oct 2010 11:54:57 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20101019115457.12263.84279@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=239&rev2=240 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20101021| regression-potential]] || hugday-20101021 || || [[UbuntuBugDay/20100930| Jaunty bugs]] || hugday-20100930 || || [[UbuntuBugDay/20100916| brasero]] || hugday-20100916 || || [[UbuntuBugDay/20100914| upgrades]] || hugday-20100914 || From jean-baptiste at ubuntu.com Tue Oct 19 19:25:24 2010 From: jean-baptiste at ubuntu.com (Jean-Baptiste Lallement) Date: Tue, 19 Oct 2010 21:25:24 +0200 Subject: Announcing the Next Ubuntu Bug Day! - 2010-10-21 Message-ID: <4CBDF0A4.4080406@ubuntu.com> Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* regression-potential bugs! * 37 New bugs need a hug * 14 Incomplete bugs need a status check * 47 Confirmed bugs need a review Following the recent discussion on bugsquad and ubuntu-devel, we have simplified the regression bugs process and dropped the regression-potential tag. It's time to implement the changes and review those potential regressions. Bookmark it, add it to your calendars, turn over those egg-timers! * Oct. 21rst 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20101021 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, -- jibel from the BugSquad From jordon at envygeeks.com Tue Oct 19 20:07:50 2010 From: jordon at envygeeks.com (Jordon Bedwell) Date: Tue, 19 Oct 2010 15:07:50 -0500 Subject: annoying bug In-Reply-To: <113748.52076.qm@web114705.mail.gq1.yahoo.com> References: <113748.52076.qm@web114705.mail.gq1.yahoo.com> Message-ID: <4CBDFA96.5070806@envygeeks.com> On 10/18/2010 05:48 PM, Jim Gleason wrote: > so i just restarted my computer, which i have been dualbooting ubuntu 10.10 and win7 on, and all of the sudden it told me that it was missing a file /dev/sfds2 and kept going into shell, ive tried safe mode but still the same thing. i love ubuntu and want to keep using it but if it is something that will happen normally i wont use it. im trying to get away from all those problems that windows has and this is even worse. as a note the hardware my computer is using is the same as when i restarted. > > SPC James T. GleasonVA Nat'l GuardCell (540)-842-5559 This is not launchpad and this is not ubuntu-user. From hggdh2 at ubuntu.com Tue Oct 19 20:23:43 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Tue, 19 Oct 2010 15:23:43 -0500 Subject: annoying bug In-Reply-To: <4CBDFA96.5070806@envygeeks.com> References: <113748.52076.qm@web114705.mail.gq1.yahoo.com> <4CBDFA96.5070806@envygeeks.com> Message-ID: <20101019152343.0a33fa69@xango2> On Tue, 19 Oct 2010 15:07:50 -0500 Jordon Bedwell wrote: > This is not launchpad and this is not ubuntu-user. Nevertheless, we *do* strive to be civil and point to the correct places. Please be nice. Your comment does not help anybody, and really is not acceptable here. Cheers, -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From adam.kosik at atlas.cz Wed Oct 20 07:28:17 2010 From: adam.kosik at atlas.cz (Adam =?iso-8859-1?Q?Kos=EDk?=) Date: Wed, 20 Oct 2010 09:28:17 +0200 Subject: ncmpcpp Message-ID: <20101020072608.GA11743@bonifac> Dear Madam/Sir, I am using Ubuntu 10.04 and I installed program ncmpcpp 0.4.1. from Ubuntu repositories. There's bug described on the page http://unkart.ovh.org/ncmpcpp/: ATTENTION: Feature, that allows you to physically remove directories from your disk while being in browser is BROKEN IN ALL VERSIONS < 0.5.4 and may, under some random circumstances, cause UNWANTED DELETION OF OTHER FILES. It needs to be manually enabled in configuration file though, so if you don't use it, you're fine. Otherwise you should upgrade to 0.5.4 or higher version immediately. I used the feature, that can cause UNWANTED DELETION OF OTHER FILES. (I read the ATTENTION notice too late.) It removed about 1/2 of my HOME folder!!!!! I would like to ask you, if you can remove this program from all repositories, where it is included or fix the bug or use another version. Yours sincerely Adam Kosik From hggdh2 at ubuntu.com Wed Oct 20 14:34:06 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 20 Oct 2010 09:34:06 -0500 Subject: ncmpcpp In-Reply-To: <20101020072608.GA11743@bonifac> References: <20101020072608.GA11743@bonifac> Message-ID: <20101020093406.326f6a7f@xango2> On Wed, 20 Oct 2010 09:28:17 +0200 Adam Kosík wrote: > Dear Madam/Sir, > > I am using Ubuntu 10.04 and I installed program ncmpcpp 0.4.1. from > Ubuntu repositories. There's bug described on the page > http://unkart.ovh.org/ncmpcpp/: > > ATTENTION: Feature, that allows you to physically remove directories > from your disk while being in browser is BROKEN IN ALL VERSIONS < > 0.5.4 and may, under some random circumstances, cause UNWANTED > DELETION OF OTHER FILES. It needs to be manually enabled in > configuration file though, so if you don't use it, you're fine. > Otherwise you should upgrade to 0.5.4 or higher version immediately. > > I used the feature, that can cause UNWANTED DELETION OF OTHER FILES. > (I read the ATTENTION notice too late.) > > It removed about 1/2 of my HOME folder!!!!! > > I would like to ask you, if you can remove this program from all > repositories, where it is included or fix the bug or use another > version. Thank you for this information. I have opened bug 663925 [1] about this, and I hope we will have a position soon. In the future please report these issues directly to the Ubuntu bug tracking system [2], using 'ubuntu-bug ncmpcpp' (or whatever is the affected package). Again, thank you, ..C.. [1] https://bugs.launchpad.net/ubuntu/+source/ncmpcpp/+bug/663925 [2] https://bugs.launchpad.net -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From rkeidel at gmail.com Wed Oct 20 17:01:58 2010 From: rkeidel at gmail.com (Robert Keidel) Date: Wed, 20 Oct 2010 10:01:58 -0700 Subject: Like to help!! Message-ID: Hello, I've used various Linux distributions for a few years and using Ubuntu for the last 4 years. I'm interested now to pay back for the help I received all the time. I would like to help and start in the bug squad. I followed the steps in the wiki and I am looking for a mentor that would help me to get my feet wet. Thanks Robert -------------- next part -------------- An HTML attachment was scrubbed... URL: From marconifabio at ubuntu-it.org Wed Oct 20 20:35:20 2010 From: marconifabio at ubuntu-it.org (njin) Date: Wed, 20 Oct 2010 22:35:20 +0200 Subject: Please assign importance to these bugs . Message-ID: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/634211 ---> Medium https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/656745 ---> Hight https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642091 ---> Medium https://bugs.launchpad.net/ubuntu/+source/linux/+bug/650567 ---> Medium https://bugs.launchpad.net/ubuntu/+source/linux/+bug/467223 ---> Medium https://bugs.launchpad.net/ubuntu/+bug/530236 ---> Low -------------- next part -------------- An HTML attachment was scrubbed... URL: From andreas at noteng.no Wed Oct 20 21:06:36 2010 From: andreas at noteng.no (Andreas Noteng) Date: Wed, 20 Oct 2010 23:06:36 +0200 Subject: Please assign importance to these bugs . In-Reply-To: References: Message-ID: <4CBF59DC.4080101@noteng.no> On 10/20/2010 10:35 PM, njin wrote: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/634211 ---> Medium > https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/656745 > ---> Hight > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/642091 ---> Medium > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/650567 ---> Medium > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/467223 ---> Medium > https://bugs.launchpad.net/ubuntu/+bug/530236 ---> Low > Done. Andreas Noteng -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: OpenPGP digital signature URL: From hggdh2 at ubuntu.com Wed Oct 20 21:21:16 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 20 Oct 2010 16:21:16 -0500 Subject: Like to help!! In-Reply-To: References: Message-ID: <20101020162116.23c72fa5@xango2> On Wed, 20 Oct 2010 10:01:58 -0700 Robert Keidel wrote: > Hello, > > I've used various Linux distributions for a few years and using > Ubuntu for the last 4 years. > I'm interested now to pay back for the help I received all the time. > I would like to help and > start in the bug squad. I followed the steps in the wiki and I am > looking for a mentor > that would help me to get my feet wet. > Thanks Hello Robert, We indeed received your mentorship request but, right now, we are waiting for available slots. Meanwhile, please do not hesitate in contacting us on IRC (channel: #ubuntu-bugs, on FreeNode), or via email (even directly to me) with your doubts. We do appreciate your interest in helping. Cheers, -- C de-Avillez IRC: hggdh This email (and any attachments) is digitally signed using GNUpg (http://gnupg.org). The public key is available at http://pgp.mit.edu. The key Id is 0xD3133E56. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From cyan.spam at gmail.com Fri Oct 22 00:02:00 2010 From: cyan.spam at gmail.com (David Tombs) Date: Thu, 21 Oct 2010 20:02:00 -0400 Subject: annoying bug In-Reply-To: <113748.52076.qm@web114705.mail.gq1.yahoo.com> References: <113748.52076.qm@web114705.mail.gq1.yahoo.com> Message-ID: <4CC0D478.10002@gmail.com> On 10/18/2010 06:48 PM, Jim Gleason wrote: > so i just restarted my computer, which i have been dualbooting ubuntu > 10.10 and win7 on, and all of the sudden it told me that it was missing > a file /dev/sfds2 and kept going into shell, ive tried safe mode but > still the same thing. i love ubuntu and want to keep using it but if it > is something that will happen normally i wont use it. im trying to get > away from all those problems that windows has and this is even worse. as > a note the hardware my computer is using is the same as when i restarted. > > SPC James T. Gleason > VA Nat'l Guard > Cell (540)-842-5559 > > Hi Jim, I'm sorry for the inconvenience. As this is not a support channel, however, I recommend checking out one of the support options at . Hope it helps, David From cyan.spam at gmail.com Fri Oct 22 00:34:48 2010 From: cyan.spam at gmail.com (David Tombs) Date: Thu, 21 Oct 2010 20:34:48 -0400 Subject: won't fix for bug Message-ID: <4CC0DC28.2080305@gmail.com> Hi all, Would someone mind setting Won't Fix on for me? Thanks, David From hggdh2 at ubuntu.com Fri Oct 22 01:49:56 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Fri, 22 Oct 2010 01:49:56 -0000 Subject: [Bug 569063] Re: icon/text support for new appointment References: <20100423153454.4782.32559.malonedeb@palladium.canonical.com> Message-ID: <20101022014956.1330.90056.malone@gandwana.canonical.com> Please do not assign bugs to other persons/teams. Thank you. ** Changed in: evolution (Ubuntu) Assignee: Ubuntu BugSquad (bugsquad) => (unassigned) -- icon/text support for new appointment https://bugs.launchpad.net/bugs/569063 You received this bug notification because you are a member of Ubuntu BugSquad, which is a bug assignee. From mrooney at gmail.com Fri Oct 22 02:04:21 2010 From: mrooney at gmail.com (Mike Rooney) Date: Thu, 21 Oct 2010 19:04:21 -0700 Subject: won't fix for bug In-Reply-To: <4CC0DC28.2080305@gmail.com> References: <4CC0DC28.2080305@gmail.com> Message-ID: Sounds good, done! While your link was specifically the g-p-m task, I attempted to infer from context what was intended and assumed you meant the linux task, so I marked that one was Won't Fix. Please let me know if I've done the wrong thing and will correct it. Thanks! On Thu, Oct 21, 2010 at 5:34 PM, David Tombs wrote: > Hi all, > > Would someone mind setting Won't Fix on > > > for me? > > Thanks, > David > > -- > 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 phillw at phillw.net Fri Oct 22 07:48:48 2010 From: phillw at phillw.net (Phill Whiteside) Date: Fri, 22 Oct 2010 08:48:48 +0100 Subject: annoying bug In-Reply-To: <20101019152343.0a33fa69@xango2> References: <113748.52076.qm@web114705.mail.gq1.yahoo.com> <4CBDFA96.5070806@envygeeks.com> <20101019152343.0a33fa69@xango2> Message-ID: +1 To Jim, if you pop onto #ubuntu-beginners (It's a bit less hectic than #ubuntu) and be patient, one of the good people on there will assist you, else log on to the forum area http://ubuntuforums.org/index.php and ask on there. I've not seen the error before. Regards, Phill. On 19 October 2010 21:23, C de-Avillez wrote: > On Tue, 19 Oct 2010 15:07:50 -0500 > Jordon Bedwell wrote: > > > > This is not launchpad and this is not ubuntu-user. > > Nevertheless, we *do* strive to be civil and point to the correct > places. > > Please be nice. Your comment does not help anybody, and really is not > acceptable here. > > Cheers, > > -- > C de-Avillez > IRC: hggdh > > This email (and any attachments) is digitally signed using GNUpg > (http://gnupg.org). The public key is available at http://pgp.mit.edu. > The key Id is 0xD3133E56. > > -- > 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 marcelcoding at googlemail.com Sun Oct 24 09:58:41 2010 From: marcelcoding at googlemail.com (Marcel Stimberg) Date: Sun, 24 Oct 2010 11:58:41 +0200 Subject: Keeping bugs visible after package change Message-ID: Hi bugsquad, I was debugging an evince printing bug ( https://bugs.launchpad.net/ubuntu/+source/evince/+bug/661724 ) that turned out to be a bug in the cairo library. Now of course the affected package should be changed to reflect this. But what is the recommended procedure to leave this bug visible in evince (users will certainly not look at the cairo bugs)? And what is the exact role of the "metabug" tag ( = "This bug has a high probability of duplicate reports being filed.")? Thanks, best Marcel From mrooney at gmail.com Sun Oct 24 18:44:50 2010 From: mrooney at gmail.com (Mike Rooney) Date: Sun, 24 Oct 2010 11:44:50 -0700 Subject: Keeping bugs visible after package change In-Reply-To: References: Message-ID: Hi Marcel, When you want something to still be visible in a certain package such as this, I believe the best way is to mark the existing task Invalid for evince, and use the "Also affects distro" to open up a "cairo (Ubuntu)" task. And since there is an upstream bug, it would then make sense to mark that new task as Triaged. As far as the tags go, check out https://wiki.ubuntu.com/Bugs/Tags. In this case it sounds like a potential fit: "This bug has a high probability of duplicate reports being filed.". - Mike On Sun, Oct 24, 2010 at 2:58 AM, Marcel Stimberg < marcelcoding at googlemail.com> wrote: > Hi bugsquad, > > I was debugging an evince printing bug ( > https://bugs.launchpad.net/ubuntu/+source/evince/+bug/661724 ) that > turned out to be a bug in the cairo library. Now of course the > affected package should be changed to reflect this. But what is the > recommended procedure to leave this bug visible in evince (users will > certainly not look at the cairo bugs)? And what is the exact role of > the "metabug" tag ( = "This bug has a high probability of duplicate > reports being filed.")? > > Thanks, best > Marcel > > -- > 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 chrisccoulson at ubuntu.com Sun Oct 24 19:00:32 2010 From: chrisccoulson at ubuntu.com (Chris Coulson) Date: Sun, 24 Oct 2010 15:00:32 -0400 Subject: Keeping bugs visible after package change In-Reply-To: References: Message-ID: <1287946832.6598.2.camel@chris-laptop> On Sun, 2010-10-24 at 11:44 -0700, Mike Rooney wrote: > Hi Marcel, > > > When you want something to still be visible in a certain package such > as this, I believe the best way is to mark the existing task Invalid > for evince, and use the "Also affects distro" to open up a "cairo > (Ubuntu)" task. And since there is an upstream bug, it would then make > sense to mark that new task as Triaged. > > > As far as the tags go, check out https://wiki.ubuntu.com/Bugs/Tags. In > this case it sounds like a potential fit: "This bug has a high > probability of duplicate reports being filed.". > > > - Mike I would generally advise against doing this, as this ends up with people who aren't particularly interested in that bug being spammed because they are watching the bugs for the package you invalidated. Regards Chris -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: This is a digitally signed message part URL: From marcelcoding at googlemail.com Mon Oct 25 14:40:47 2010 From: marcelcoding at googlemail.com (Marcel Stimberg) Date: Mon, 25 Oct 2010 16:40:47 +0200 Subject: Keeping bugs visible after package change In-Reply-To: References: Message-ID: Hi Mike, > When you want something to still be visible in a certain package such as > this, I believe the best way is to mark the existing task Invalid for > evince, and use the "Also affects distro" to open up a "cairo (Ubuntu)" > task. that would work, but given Chris' comment I did not do this, but simply changed the package. Hopefully it should be soon fixed anyway, until then I'll manually mark the evince bugs as duplicates. > And since there is an upstream bug, it would then make sense to mark > that new task as Triaged. I'd love to do that, but I'm only bugsquad not bugcontrol. For anyone who can do it: please feel free to do mark the bug as triaged: https://bugs.edge.launchpad.net/ubuntu/+source/cairo/+bug/661724 > As far as the tags go, check out https://wiki.ubuntu.com/Bugs/Tags. In this > case it sounds like a potential fit: "This bug has a high probability of > duplicate reports being filed.". Yes, that's what I thought as well. But how does it work, what does change when I add this tag? Will it go up in the possible duplicates list or something? Thanks for your help, Marcel From noreply at ubuntu.com Tue Oct 26 17:36:02 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 26 Oct 2010 17:36:02 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Importance=22_by_cprofitt?= Message-ID: <20101026173602.17816.41465@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 cprofitt: http://wiki.ubuntu.com/Bugs/Importance?action=diff&rev1=24&rev2=25 The comment on the change is: change approved at UDS-N : jono, hggdh, charlie-tca ------------------------------------------------------------------------------ * '''Medium''': most bugs are of medium importance, examples are: * A bug that has a moderate impact on a core application. * A bug that has a severe impact on a non-core application. + * A bug which impacts accessibility of a non-core application. * A problem with a non-essential hardware component (network card, camera, webcam, music player, sound card, power management feature, printer, etc.) * '''High''': A bug which fulfills one of the following criteria: * Has a severe impact on a small portion of Ubuntu users (estimated) @@ -29, +30 @@ * For example, if the system fails to boot, or X fails to start, on a certain make and model of computer * A problem with an essential hardware component (disk controller, laptop built-in wireless, video card, keyboard, mouse) * Has a moderate impact on a large portion of Ubuntu users (estimated) + * A bug which impacts accessibility of a core application * '''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.|| From noreply at ubuntu.com Fri Oct 29 14:29:45 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 29 Oct 2010 14:29:45 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUpdateManager=22_by_mis?= =?utf-8?q?trynitesh?= Message-ID: <20101029142945.10133.75469@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 mistrynitesh: http://wiki.ubuntu.com/DebuggingUpdateManager?action=diff&rev1=37&rev2=38 The comment on the change is: added tag lucid2maverick ------------------------------------------------------------------------------ = Bug Tags = || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=lucid2maverick |`lucid2maverick`]] || Bugs related to upgrades from Lucid Lynx (10.04) to Maverick Meerkat (10.10) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=hardy2lucid|`hardy2lucid`]] || Bugs related to upgrades from Hardy Heron (8.04) to Lucid Lynx (10.04) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=karmic2lucid|`karmic2lucid`]] || Bugs related to upgrades from Karmic Koala (9.10) to Lucid Lynx (10.04) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=jaunty2karmic|`jaunty2karmic`]] || Bugs related to upgrades from Jaunty Jackalope (9.04) to Karmic Koala (9.10) || From brian at ubuntu.com Sat Oct 30 14:33:47 2010 From: brian at ubuntu.com (Brian Murray) Date: Sat, 30 Oct 2010 07:33:47 -0700 Subject: New Launchpad Greasemonkey Script Message-ID: <20101030143347.GR16179@murraytwins.com> I'm currently working on a new Launchpad Greasemonkey script[1] that would expand the bug filters portlet on bug listing pages to make searches easier. The portlet currently contains links to searches like Open bugs, Bugs assigned to me, etc.... However, Carlos mentioned to me the pain of creating an advanced search and how it would be neat to have saved ones. This script will contain these saved searches and currently includes the following: Incomplete w/ response bugs Fix Released bugs Expired bugs Bugs with branches Bugs I reported Bugs I am subscribed to Bugs I commented on I'm looking for other ideas of saved searches that might be useful before adding this to the firefox-lp-improvements ppa. [1] For the impatient it is lp_more_bug_links.user.js in http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/files Thanks, -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From marconifabio at ubuntu-it.org Sun Oct 31 16:41:37 2010 From: marconifabio at ubuntu-it.org (njin) Date: Sun, 31 Oct 2010 17:41:37 +0100 Subject: please assign importance. Message-ID: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/660746 ---hight https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/668800 ---critical https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658672 ---hight https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659444 --low https://bugs.launchpad.net/linux/+bug/663806 --hight https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/655078 ---hight https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/649374 --low https://bugs.launchpad.net/ubuntu/+source/partman-target/+bug/653880 ---critical https://bugs.launchpad.net/ubuntu/+source/linux/+bug/654791 ---hight -------------- next part -------------- An HTML attachment was scrubbed... URL: From simar.i3r at gmail.com Sun Oct 31 18:09:33 2010 From: simar.i3r at gmail.com (Gursimran singh) Date: Sun, 31 Oct 2010 23:39:33 +0530 Subject: please assign importance. In-Reply-To: References: Message-ID: On Sun, Oct 31, 2010 at 10:11 PM, njin wrote: > https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/660746 > ---hight ----Not sure, but I think its not high > https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/668800 > ---critical > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658672 ---hight > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659444 --low --- > Done > https://bugs.launchpad.net/linux/+bug/663806 --hight > > https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/655078 > ---hight > https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/649374 --low > --- Done > https://bugs.launchpad.net/ubuntu/+source/partman-target/+bug/653880 > ---critical > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/654791 ---hight > > Assigned the low ones, of High and Critical, I'm not sure whether they are assigned to that or not. Let some expert in that field make the right move... > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Warm Regards, Gursimran singh Mohar -------------- next part -------------- An HTML attachment was scrubbed... URL: From thekorn at gmx.de Sun Oct 31 18:54:20 2010 From: thekorn at gmx.de (markus korn) Date: Sun, 31 Oct 2010 19:54:20 +0100 Subject: please assign importance. In-Reply-To: References: Message-ID: On Sun, Oct 31, 2010 at 7:09 PM, Gursimran singh wrote: > > > On Sun, Oct 31, 2010 at 10:11 PM, njin wrote: >> >> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/660746 >> ---hight   ----Not sure, but I think its not high >> >> https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/668800 >> ---critical >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/658672  ---hight >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659444  --low  --- >> Done >> >> https://bugs.launchpad.net/linux/+bug/663806  --hight >> >> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/655078 >> ---hight >> https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/649374  --low >> ---  Done >> >> https://bugs.launchpad.net/ubuntu/+source/partman-target/+bug/653880 >> ---critical >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/654791  ---hight > > Assigned the low ones, of High and Critical, I'm not sure whether they are > assigned to that or not. Let some expert in that field make the right > move... > >> Hi njin, I just had a quick look at the bugs for which you requested High or Critical importance, I somehow don't see how they qualify for major importance. Can you please elaborate a bit more on your decissions. Thank you, Markus