From cyan.spam at gmail.com Thu Jul 1 01:07:38 2010 From: cyan.spam at gmail.com (David Tombs) Date: Wed, 30 Jun 2010 21:07:38 -0400 Subject: bug squad join requests In-Reply-To: <1277848709.4229.22.camel@xango2> References: <4C166E67.1060406@gmail.com> <20100629193249.GL8308@murraytwins.com> <1277844662.4229.17.camel@xango2> <20100629211740.GP8308@murraytwins.com> <1277848709.4229.22.camel@xango2> Message-ID: <4C2BEA5A.4060004@gmail.com> On 06/29/2010 05:58 PM, C de-Avillez wrote: > > Just did it. Of course, it still needs some loving ;-) > > Direct result -- no longer requiring email to the ML to ask for it. I am > also updating the wiki [1] to reflect this change. > > [1] https://wiki.ubuntu.com/BugSquad > > Thanks a lot Brian and C, I appreciate your streamlining the process like this. :) David From cyan.spam at gmail.com Thu Jul 1 01:13:00 2010 From: cyan.spam at gmail.com (David Tombs) Date: Wed, 30 Jun 2010 21:13:00 -0400 Subject: docs/clarification on confirming In-Reply-To: <20100630141158.GB8771@hallyn.com> References: <20100623183250.GB15843@hallyn.com> <4C22B947.1090604@gmail.com> <1277345276.3737.11.camel@xango2> <20100624192653.GU29399@murraytwins.com> <20100624192900.GA27172@hallyn.com> <20100629194753.GN8308@murraytwins.com> <20100630141158.GB8771@hallyn.com> Message-ID: <4C2BEB9C.8000206@gmail.com> On 06/30/2010 10:11 AM, Serge E. Hallyn wrote: > Quoting Brian Murray (brian at ubuntu.com): >> On Thu, Jun 24, 2010 at 02:29:00PM -0500, Serge E. Hallyn wrote: >>> The situation I'm referring to is where upstream requires email list >>> interaction, and we are asking the launchpad bug submitter to forward >>> the patch. Do we then set it to 'Confirmed' until the submitter >>> forwards to the appropriate list, and then set it to 'Triaged'? Or >>> still just set it to 'Triaged' immediately? >> >> Triaged is most appropriate. > > Great, thanks! > > -serge > Hi all, Updated the wiki to include this.[1] Everyone good with the wording? David [1] https://wiki.ubuntu.com/Bugs/Status?action=diff&rev2=41&rev1=40 From xteejyx at googlemail.com Thu Jul 1 18:49:10 2010 From: xteejyx at googlemail.com (Roy Jamison) Date: Thu, 01 Jul 2010 19:49:10 +0100 Subject: Facebook group In-Reply-To: References: Message-ID: <1278010150.1753.7.camel@teej-laptop> Hi BugSquad!! I have started an Ubuntu BugSquad group on Facebook. It is kept up to date with the latest Hug Days, meetings, etc. This will keep everyone updated with all the latest goings-on and help to advertise Ubuntu in general where your friends will be able to see it, and perhaps get involved and help our cause. Please don't think this is spam, it's really not, just an idea to get triaging "out there" with the wider community through the biggest social networking site there is! Link to group: http://www.facebook.com/group.php?gid=88568611005 PS If any Canonical guys or experienced triagers with good karma want to help administrate the group, just scribble a message to me and I'll look into it no problem at all :) -------------------------------- Roy Jamison (Teej) Ubuntu Bug Control http://www.launchpad.net/~xteejx From danielcastaneda2010 at gmail.com Fri Jul 2 15:37:14 2010 From: danielcastaneda2010 at gmail.com (=?ISO-8859-1?Q?Daniel_Casta=F1eda?=) Date: Fri, 2 Jul 2010 11:37:14 -0400 Subject: join Message-ID: Hello, my name is Daniel Castañeda. I'd like to join to the bug squad team. I studied computing at college, have been using Linux since 2003 and i think this way i can make my little contribution to Ubuntu. I can work for bug squad one hour a day. I have read the triadge guide, there is a thing I couldn't understand. About the upstream developers, are you talking about the original developers of the software? Daniel -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Fri Jul 2 16:46:55 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Fri, 02 Jul 2010 11:46:55 -0500 Subject: join In-Reply-To: References: Message-ID: <1278089215.2518.64.camel@xango2> On Fri, 2010-07-02 at 11:37 -0400, Daniel Castañeda wrote: > Hello, my name is Daniel Castañeda. I'd like to join to the bug squad > team. Welcome in! > I studied computing at college, have been using Linux since 2003 and i > think this way i can make my little contribution to Ubuntu. > I can work for bug squad one hour a day. Thank you. You will probably profit from joining us at IRC: #ubuntu-bugs, on irc.freenode.org. All help is appreciated. > I have read the triadge guide, there is a thing I couldn't understand. > About the upstream developers, are you talking about the original > developers of the software? Yes -- either the original developers (if they are still active), or whoever took over development. Cheers, -- C de-Avillez IRC: hggdh -------------- 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 pedro at ubuntu.com Mon Jul 5 12:37:52 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 05 Jul 2010 08:37:52 -0400 Subject: QA Team Meeting Reminder - July 07 2010, 1900 UTC Message-ID: <1278333472.2145.15.camel@wombat> Hello Folks, Just a reminder that the Wednesday 07 of July at 1900 UTC we're having our weekly QA meeting at #ubuntu-quality on FreeNode. If there's anything else you'd like to discuss, please add it to: * https://wiki.ubuntu.com/QATeam/Meetings So far the agenda looks like: * review previous action items (all) * SRU testing -- sbeattie (Steve Beattie) * Bug Day status -- pvillavi * Blueprints update -- all * Selection of new chair - pvillavi Thanks!, pedro. From bilalakhtar96 at yahoo.com Mon Jul 5 15:47:46 2010 From: bilalakhtar96 at yahoo.com (Bilal Akhtar) Date: Mon, 05 Jul 2010 18:47:46 +0300 Subject: Ubuntu Branch reviewers Message-ID: <1278344866.1938.3.camel@bilal-laptop> Hi all, I think it would be a *lot* better to set the reviewer of all ubuntu branches to ubuntu-sponsors. This would prevent confusion among people who wish to fix bugs in Ubuntu or merge packages. Such people propose a merge and the value of reviewer is set to ubuntu-branches, while, according to https://wiki.ubuntu.com/Bugs/HowToFix and others, the reviewer should be ubuntu-sponsors. A merge proposal that has this mistake is https://code.edge.launchpad.net/~joel-auterson/ubuntu/maverick/shotwell/menu_rename/+merge/28598 where I had to comment in order to get this change done. What are your opinions? Cheers, Bilal Akhtar -------------- 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 kamusin at gmail.com Tue Jul 6 15:16:53 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 6 Jul 2010 11:16:53 -0400 Subject: Announcing the Next Ubuntu Bug Day! - July 8th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Bugs without a package!, the task is to assign to the right package and triage those as well: * 100 New bugs without a package need a hug * 100 Confirmed bugs without a package need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 8th July 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100708 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 and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud: -33.439177,-70.625267 Santiago, Chile. From brunogirin at gmail.com Wed Jul 7 09:48:24 2010 From: brunogirin at gmail.com (Bruno Girin) Date: Wed, 07 Jul 2010 10:48:24 +0100 Subject: How to use the new Launchpad status? Message-ID: <1278496104.1813.2.camel@nuuk> Hi BugSquad, Any idea when and how we should use the new Launchpad status [1] when triaging bugs? [1] http://blog.launchpad.net/bug-tracking/new-bugs-status-opinion Bruno From ben.root at ou.edu Wed Jul 7 14:53:01 2010 From: ben.root at ou.edu (Benjamin Root) Date: Wed, 7 Jul 2010 09:53:01 -0500 Subject: How to use the new Launchpad status? In-Reply-To: <1278496104.1813.2.camel@nuuk> References: <1278496104.1813.2.camel@nuuk> Message-ID: Sounds like to me that it is a finer grained version of "Invalid". The idea being that rather than possibly insulting the OP with an "Invalid" statement, one could mark it as "Opinion" where it is effectively closed, but leaves open the possibility that it might have to be revisited later. I guess this helps to distinguish between the bugs that are blatantly Invalid and the bugs that might be a little bit more ambiguous. At least, that is my interpretation... WeatherGod On Wed, Jul 7, 2010 at 4:48 AM, Bruno Girin wrote: > Hi BugSquad, > > Any idea when and how we should use the new Launchpad status [1] when > triaging bugs? > > [1] http://blog.launchpad.net/bug-tracking/new-bugs-status-opinion > > Bruno > > > > -- > 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 brunogirin at gmail.com Wed Jul 7 15:21:59 2010 From: brunogirin at gmail.com (Bruno Girin) Date: Wed, 07 Jul 2010 16:21:59 +0100 Subject: How to use the new Launchpad status? In-Reply-To: References: <1278496104.1813.2.camel@nuuk> Message-ID: <1278516119.2774.48.camel@nuuk> On Wed, 2010-07-07 at 09:53 -0500, Benjamin Root wrote: > Sounds like to me that it is a finer grained version of "Invalid". > The idea being that rather than possibly insulting the OP with an > "Invalid" statement, one could mark it as "Opinion" where it is > effectively closed, but leaves open the possibility that it might have > to be revisited later. > > I guess this helps to distinguish between the bugs that are blatantly > Invalid and the bugs that might be a little bit more ambiguous. > > At least, that is my interpretation... Thanks, that sounds like a sensible interpretation. So in terms of triaging, if the bug is one that we would normally set to invalid because even though the software does not behave as the OP thinks it should, the reasons for changing it are not clear cut, we would assign it the Opinion status rather than the Invalid status. I suspect that in this case, bugs in that status should also have a severity of Wishlist? A new standard response to use when setting bugs to that status would be good. What about the following? Thank you for taking the time to report this bug and helping to make Ubuntu better. While we appreciate that the software does not behave as you expect, we consider that it is a matter of opinion whether it should be changed to accommodate your requirement. This bug is being set to "Opinion" to indicate that, although we do not consider it invalid, we will not start work on resolving it until we are satisfied that there are enough details on how to change the software without compromising usability or existing features. Bruno From noreply at ubuntu.com Thu Jul 1 01:12:21 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 01 Jul 2010 01:12:21 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_cyan-spam?= Message-ID: <20100701011221.21068.97109@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/Status?action=diff&rev1=40&rev2=41 The comment on the change is: clarification of Traiged and upstream ------------------------------------------------------------------------------ * '''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 * Use this when you are confident that it should be looked at by a developer '''and''' has enough information + * Ideally a bug's Ubuntu task will be Triaged before any upstream activity occurs * '''In Progress''': * If '''you''' are working on fixing a bug, set it to {{{In Progress}}} so people know what's going on * {{{In Progress}}} bugs should be assigned to the person working on them From noreply at ubuntu.com Fri Jul 2 20:06:16 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 02 Jul 2010 20:06:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20100702200616.16424.36541@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=53&rev2=54 ------------------------------------------------------------------------------ 5. Press Ctrl-C to stop the logging. 6. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: <
> {{{$ lsusb}}} <
> Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed. 7. Check whether the device files for the printer get created and the ownerships ("root lp") and permissions (non-HP: "crw-rw-r--", HP: "crw-rw-r--+") correctly set: <
> {{{$ ls -l /dev/usb/lp* /dev/bus/usb/*/*}}} - 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_deviceid /dev/usb/lp0}}} <
> {{{$ sudo usb_deviceid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines) + 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_deviceid /dev/usb/lp0}}} <
> {{{$ sudo usb_deviceid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines). + 9. For HP printers: Check whether HPLIP connects to them: <
> {{{$ hp-makeuri :}}}
Replace "" and "" by the bus and device numbers from the "lsusb" output (not vendor and product ID). The numbers must be supplied with three digits, zero-padded from the left, like "008:015". 9. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 10. Attach the output of the above commands to the bug report. + + Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), libusb, HPLIP (package "hplip"), and several third-party printer drivers. == Parallel port printer == @@ -33, +36 @@ 3. Check if the kernel detected the parallel port during bootup: <
> {{{$ dmesg | grep par }}} 4. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 5. Attach the output of the above commands to the bug report. + + Note that problems cannot only caused by CUPS but also by the kernel (package "linux"), HPLIP (package "hplip"), and several third-party printer drivers. = CUPS web interface = From virtualtom at gmail.com Thu Jul 1 17:13:11 2010 From: virtualtom at gmail.com (Thomas Alexander) Date: Thu, 1 Jul 2010 13:13:11 -0400 Subject: Compiz Fusion Icon Message-ID: Hello There, I have a puzzling issue, which may be a bug, I don't know. I am running ubuntu 10.04 on an AMD Quad with 4GB of ram and a 8500 GT Nvidia card. Asus MB. All works fine, no driver issues or crashes to speak of. I have Compiz-fusion installed with the Compiz-fusion manager installed, so I've turned on lots of bling like the 3D cube, couple of Screenlets, Cairo Dock GLX version I have the Fusion Icon installed and it works with the Dock Applet, opens Emerald Themes, restarts the Window Manager... all without issue. I can not get the icon to appear in the task bar, if I manually run fusion-icon from the CLI it restarts the Compiz session and things run as normal, but I can't get the icon... I'm stumped by this issue. Any help files I could dig up were unhelpful. I'd like advice on how to troubleshoot this and (if necessary) what to provide you guys for bug investigation? Thanks, Virtualtom -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sat Jul 3 01:27:18 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sat, 03 Jul 2010 01:27:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22BugSquad/GettingInvolved=22_by_d?= =?utf-8?q?rumperson?= Message-ID: <20100703012718.12809.76752@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 drumperson: http://wiki.ubuntu.com/BugSquad/GettingInvolved?action=diff&rev1=23&rev2=24 The comment on the change is: Added a link to Bug Control's page ------------------------------------------------------------------------------ * Timezone * Time when available - Members of the Bug Squad, Bug Control, and Canonical employees are available in #ubuntu-bugs to answer any questions you might have. + Members of the Bug Squad, [[https://wiki.ubuntu.com/UbuntuBugControl|Bug Control]], and Canonical employees are available in #ubuntu-bugs to answer any questions you might have. == Assigning Packages == From noreply at ubuntu.com Mon Jul 5 18:37:36 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 05 Jul 2010 18:37:36 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Upstream/GNOME=22_by_pvilla?= =?utf-8?q?vi?= Message-ID: <20100705183736.24695.56452@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/Upstream/GNOME?action=diff&rev1=16&rev2=17 ------------------------------------------------------------------------------ * Keywords * etc ... - '''Examples:''' - - ToDo - === Advanced === There's also functionality that allows you do to advanced searches which you can find here at the [[http://bugzilla.gnome.org/query.cgi?format=advanced|Advanced Search]] page. Read [[http://bugzilla.gnome.org/page.cgi?id=quicksearch.html|this]] for more information on search. @@ -51, +47 @@ * Choose the [[http://bugzilla.gnome.org/page.cgi?id=bug-status.html#op_sys|OS]] - in most of the cases Linux, unless the bug affects all OS'. * Set the correct [[http://bugzilla.gnome.org/page.cgi?id=bug-status.html#priority|priority]] and [[http://bugzilla.gnome.org/page.cgi?id=bug-status.html#bug_severity|severity]] * If needed set a [[http://bugzilla.gnome.org/describekeywords.cgi|keyword]]. This is very important for reports with a complete stacktrace, remember that if you're submitting a report with a good stacktrace (otherwise don't submit it), please add the STACKTRACE keyword. - * ''What if it's a usability bug, or another bug that doesn't make the application crash/leave a stacktrace? -- MartinAhnelöv'' - * ''in that case you should add the usability keyword to it. -- PedroVillavicencio'' * Provide a complete description and a link to our bug in Launchpad. * Add the URL to the report on Launchpad in the '''Add Bug URLs:''' field. @@ -68, +62 @@ After you have forwarded the bug to GNOME's bugzilla you will want to create a "Bug Watch" in Launchpad that links the Ubuntu bug to the GNOME bug. This bug watch will be updated regularly and reflect the status of the upstream bug report. Details on creating one are found at [[Bugs/Watches]]. + == FAQ == + + 1. ''What if it's a usability bug, or another bug that doesn't make the application crash/leave a stacktrace? -- MartinAhnelöv'' + * ''in that case you should add the usability keyword to it. -- PedroVillavicencio'' ##== States == ##== Following up == From pancho at mined.rimed.cu Thu Jul 1 13:13:26 2010 From: pancho at mined.rimed.cu (Francisco Davila) Date: Thu, 1 Jul 2010 09:13:26 -0400 Subject: Problema con el Ubuntu 10.04 en una laptop Compaq Message-ID: <000601cb191f$31a33050$1800010a@usuario> Saludos a todos: Disculpen les escriba en español pero mi ingles no es nada bueno. Deseaba consultarles el siguiente problema: Tengo una laptop Compaq Presario 1215US (40Gb disco, 320Mb RAM CPU Athlon 4 1Ghz chiset VIA686A) a la cual necesito por situaciones de estudio instalarle el sistema GNU Ubuntu. Como la laptop esta algo limitada en recursos no utilice la instalacion grafica y opte por realizar la instalacion utilizando la version Alternate de Ubuntu 10.04 instalando en modo de linea de comando. Posteriormente instale los paquetes adecuados (Gnome Office, el navegador Midori, el gestor de correo Sylpheed y otras aplicaciones ligeras. Concluida la instalacion de los paquetes al reiniciar comienza la carga del sistema, pero inesperadamente la laptop "se cuelga". El problema no ocurre siempre en el mismo punto, a veces logro llegar a la pantalla de login, otras veces logro incluso entrar al sistema y entonces se cuelga al intentar abrir cualquier programa. Repeti la instalacion varias veces utilizando el desktop XFCE (Xubuntu 10.04) y sucede lo mismo. Llegue a probar con LXDE (Lubuntu 10.04) y lo mismo. Consulte el log y en el inicio de la carga del sistema me aparece lo siguiente: [8.828369] ACPI: I/O resource vt596_smbus [0x8100-0x8107] conflicts with ACPI region SMIO [0x8100-0x8106] [8.965801] via686a 0000:00:07.4: base adress not set - upgrade BIOS or use force_addr=0xaddr En una prueba ulterior con la base ubuntu 10.04 y el entorno lxde instalado (solo el paquete lxde, sin instalar el paquete de lubuntu-desktop completo) con algunas aplicaciones (Abiword, Gnumeric, Sylpheed y Midori) arranque en modo recuperacion, inicie una sesion de consola como root y cargue el sistema con el comando startx y todo funciona bien, puedo utilizar la laptop por horas sin que ocurra ningun problema. Reinicie en el modo normal y de nuevo se cuelga. Esperando puedan ayudarme gracias a todos desde ya. Saludos cordiales. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Fri Jul 2 19:59:12 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 02 Jul 2010 19:59:12 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20100702195912.9572.86627@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=52&rev2=53 ------------------------------------------------------------------------------ 3. Unplug the USB printer cable from your computer and enter this command: <
> {{{$ tail -f /var/log/messages }}} 4. Reconnect the USB printer cable, you should see some messages appearing. 5. Press Ctrl-C to stop the logging. + 6. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: <
> {{{$ lsusb}}} <
> Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed. + 7. Check whether the device files for the printer get created and the ownerships ("root lp") and permissions (non-HP: "crw-rw-r--", HP: "crw-rw-r--+") correctly set: <
> {{{$ ls -l /dev/usb/lp* /dev/bus/usb/*/*}}} + 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_deviceid /dev/usb/lp0}}} <
> {{{$ sudo usb_deviceid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines) - 6. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} + 9. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} - 7. Attach the output of the above commands to the bug report. + 10. Attach the output of the above commands to the bug report. == Parallel port printer == From kangarooo at gmail.com Sat Jul 3 21:11:24 2010 From: kangarooo at gmail.com (Kangarooo) Date: Sun, 4 Jul 2010 00:11:24 +0300 Subject: Better Apport Crashes Message-ID: Hello! 1. if i understand correct then installing all -dbg and -dbgsym packages for packages i have installed will be running on programm start. yes no? what does gdb and gdbsym and what other are there? are they slowing comp? are they writing all the time so some folder gdb`s? 2. how with one command install all needed packages that does that? one aptitude command. example sudo aptitude install (check all installed programms) + to name -gdb penguin42 gave command for listing all dpkg -l | awk -F' ' '/^ii/ {print $2"-dbgsym"}' mabe that gives some idea. 3. next time when i install some programms what command will install noninstalled theese gdb tpye packages witch help get better crash report? example sudo aptitude install (check all installed programms add -gdb) - (all installed -gdb) -- BB seko man https://twitter.com/kangarooo rakst man https://twitter.com/direct_messages/create/Kangarooo mana vizit http://card.ly/kangarooo https://launchpad.net/~kangarooo https://wiki.ubuntu.com/kangarooo From marcelcoding at googlemail.com Wed Jul 7 15:53:36 2010 From: marcelcoding at googlemail.com (Marcel Stimberg) Date: Wed, 7 Jul 2010 17:53:36 +0200 Subject: How to use the new Launchpad status? In-Reply-To: <1278516119.2774.48.camel@nuuk> References: <1278496104.1813.2.camel@nuuk> <1278516119.2774.48.camel@nuuk> Message-ID: I think „Opinion“ might also be a sensible status for „A suggestion for changing default applications or preferences“: https://wiki.ubuntu.com/Bugs/Responses#A%20suggestion%20for%20changing%20default%20applications%20or%20preferences Marcel From ben.root at ou.edu Wed Jul 7 16:00:29 2010 From: ben.root at ou.edu (Benjamin Root) Date: Wed, 7 Jul 2010 11:00:29 -0500 Subject: How to use the new Launchpad status? In-Reply-To: <1278516119.2774.48.camel@nuuk> References: <1278496104.1813.2.camel@nuuk> <1278516119.2774.48.camel@nuuk> Message-ID: On Wed, Jul 7, 2010 at 10:21 AM, Bruno Girin wrote: > On Wed, 2010-07-07 at 09:53 -0500, Benjamin Root wrote: > > Sounds like to me that it is a finer grained version of "Invalid". > > The idea being that rather than possibly insulting the OP with an > > "Invalid" statement, one could mark it as "Opinion" where it is > > effectively closed, but leaves open the possibility that it might have > > to be revisited later. > > > > I guess this helps to distinguish between the bugs that are blatantly > > Invalid and the bugs that might be a little bit more ambiguous. > > > > At least, that is my interpretation... > > Thanks, that sounds like a sensible interpretation. So in terms of > triaging, if the bug is one that we would normally set to invalid > because even though the software does not behave as the OP thinks it > should, the reasons for changing it are not clear cut, we would assign > it the Opinion status rather than the Invalid status. > > I suspect that in this case, bugs in that status should also have a > severity of Wishlist? > > A new standard response to use when setting bugs to that status would be > good. What about the following? > > Thank you for taking the time to report this bug and helping to > make Ubuntu better. While we appreciate that the software does > not behave as you expect, we consider that it is a matter of > opinion whether it should be changed to accommodate your > requirement. This bug is being set to "Opinion" to indicate > that, although we do not consider it invalid, we will not start > work on resolving it until we are satisfied that there are > enough details on how to change the software without > compromising usability or existing features. > > Personally, I would probably avoid the word "appreciate" as it might get translated poorly to someone else's language to indicate that we like it when the software does not work as expected... Maybe "understand"? Ben Root > Bruno > > > > -- > 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 Wed Jul 7 19:15:47 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Wed, 7 Jul 2010 20:15:47 +0100 Subject: Problema con el Ubuntu 10.04 en una laptop Compaq In-Reply-To: <000601cb191f$31a33050$1800010a@usuario> References: <000601cb191f$31a33050$1800010a@usuario> Message-ID: Hi Fransico, This being translated by google translation, so it will probably not read quite correctly. I appreciate you have a bug but I do not think the bug-squad can look into it, until you have registered it as bug using https://help.ubuntu.com/community/ReportingBugs_es while that happens I'd like to suggest that you try a minimal installation and then add the lubuntu desktop onto that. There are instructions for that at https://wiki.ubuntu.com/Lubuntu/DocumentationHelp#Minimal Install If you would like me to run google translate over them for you, please ask. Hi BugSquad, I've suggested something that may help, and also copied this to the lubuntu mailing list. I'm still new at bug squad things, so please forgive me if I have done something wrong Regards, Phill. Hola Fransico, esta siendo traducido por traducción de Google, por lo que probablemente no lea toda la razón. Le agradezco que haya un error, pero no creo que el error de los escuadrones pueden mirar en él, hasta que se ha registrado como fallo usando https://help.ubuntu.com/community/ReportingBugs_es mientras eso sucede me gustaría sugerir que trate de una instalación mínima y luego añadir el escritorio lubuntu en eso. Hay instrucciones para que en la dirección https://wiki.ubuntu.com/Lubuntu/DocumentationHelp#Minimal Install Si me gusta correr traductor Google sobre ellos para usted, por favor pregunte. Hola BugSquad, he sugerido algo que puede ayudar, y copian esto a la lista de correo lubuntu. Todavía estoy en las cosas nuevas escuadrón de errores, así que por favor me perdone si he hecho algo mal Un cordial saludo, Phill. 2010/7/1 Francisco Davila > Saludos a todos: > Disculpen les escriba en español pero mi ingles no es nada bueno. Deseaba > consultarles el siguiente problema: > Tengo una laptop Compaq Presario 1215US (40Gb disco, 320Mb RAM CPU Athlon 4 > 1Ghz chiset VIA686A) a la cual necesito por situaciones de estudio > instalarle el sistema GNU Ubuntu. Como la laptop esta algo limitada en > recursos no utilice la instalacion grafica y opte por realizar la > instalacion utilizando la version Alternate de Ubuntu 10.04 instalando en > modo de linea de comando. Posteriormente instale los paquetes adecuados > (Gnome Office, el navegador Midori, el gestor de correo Sylpheed y otras > aplicaciones ligeras. Concluida la instalacion de los paquetes al reiniciar > comienza la carga del sistema, pero inesperadamente la laptop "se cuelga". > El problema no ocurre siempre en el mismo punto, a veces logro llegar a la > pantalla de login, otras veces logro incluso entrar al sistema y entonces se > cuelga al intentar abrir cualquier programa. Repeti la instalacion varias > veces utilizando el desktop XFCE (Xubuntu 10.04) y sucede lo mismo. Llegue a > probar con LXDE (Lubuntu 10.04) y lo mismo. Consulte el log y en el inicio > de la carga del sistema me aparece lo siguiente: > > [8.828369] ACPI: I/O resource vt596_smbus [0x8100-0x8107] conflicts with > ACPI region SMIO [0x8100-0x8106] > [8.965801] via686a 0000:00:07.4: base adress not set - upgrade BIOS or use > force_addr=0xaddr > > En una prueba ulterior con la base ubuntu 10.04 y el entorno lxde instalado > (solo el paquete lxde, sin instalar el paquete de lubuntu-desktop completo) > con algunas aplicaciones (Abiword, Gnumeric, Sylpheed y Midori) arranque en > modo recuperacion, inicie una sesion de consola como root y cargue el > sistema con el comando startx y todo funciona bien, puedo utilizar la laptop > por horas sin que ocurra ningun problema. Reinicie en el modo normal y de > nuevo se cuelga. > Esperando puedan ayudarme gracias a todos desde ya. Saludos cordiales. > Frank > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Francisco Davila 2010/7/1 Greetings to all: Sorry I write in Spanish, but my English is not good. He wanted to consult the following problem: I have a Compaq Presario 1215US laptop (40GB drive, 320MB RAM 1Ghz CPU Athlon 4 chiset via686) to which I need to study situations putting on Ubuntu GNU system. As the laptop is somewhat limited in resources do not use the graphical installer and choose to install using the Alternate version of Ubuntu 4.10 installed in command line mode. Then install the appropriate packages (Gnome Office, Midori browser, Sylpheed mail manager and other lightweight applications. After the installation of packages when you restart the system begins loading, but suddenly the laptop "hangs." The problem does not occur always in the same spot, sometimes made it to the login screen, sometimes achieving even enter the system and then hangs when trying to open any program. I repeated the installation several times using the XFCE desktop (Xubuntu 10.04) and same thing happens . Get to try out LXDE (Lubuntu 10.04) and the same. View the log and the start of loading of the system I get the following: [8.828369] ACPI: I/O resource vt596_smbus [0x8100-0x8107] conflicts with ACPI region SMIO [0x8100-0x8106] [8.965801] via686a 0000:00:07.4: base adress not set - upgrade BIOS or use force_addr=0xaddr In a subsequent test with the base ubuntu lxde 10.04 and the environment installed (only lxde package, without installing the package lubuntu full-desktop) with some applications (Abiword, Gnumeric, Sylpheed and Midori) boot in recovery mode, log console as root and load the system with the command startx and everything works fine, I can use the laptop for hours without any problem occurs. Reboot into normal mode and again hangs. Hoping you can help me thank you all from now on. Best Regards. Frank -------------- next part -------------- An HTML attachment was scrubbed... URL: From hggdh2 at ubuntu.com Wed Jul 7 21:28:26 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Wed, 07 Jul 2010 16:28:26 -0500 Subject: How to use the new Launchpad status? In-Reply-To: References: <1278496104.1813.2.camel@nuuk> <1278516119.2774.48.camel@nuuk> Message-ID: <1278538106.7182.10.camel@xango2> On Wed, 2010-07-07 at 11:00 -0500, Benjamin Root wrote: > > > On Wed, Jul 7, 2010 at 10:21 AM, Bruno Girin > wrote: > > A new standard response to use when setting bugs to that status > > would be good. What about the following? > > > Thank you for taking the time to report this bug and helping > > make Ubuntu better. While we appreciate that the software does > > not behave as you expect, we consider that it is a matter of > > opinion whether it should be changed to accommodate your > > requirement. This bug is being set to "Opinion" to indicate > > that, although we do not consider it invalid, we will not > > start work on resolving it until we are satisfied that there > > are enough details on how to change the software without > > compromising usability or existing features. > > > > > Personally, I would probably avoid the word "appreciate" as it might > get translated poorly to someone else's language to indicate that we > like it when the software does not work as expected... > > Maybe "understand"? Actually, the idea is that the bug is closed -- but marking INVALID carries a bad connotation. So we want to state that we will not work on this anymore, but please keep on discussing it. New proposal: Thank you for taking the time to report this bug and help make Ubuntu better. This bug is being marked OPINION; this indicates we will not work on it, but all are free to express their opinions. It is possible that, in the future, we may revisit this bug. @Bruno: If everybody is in agreement, would you mind adding this to the Responses? Cheers, ..C.. -- C de-Avillez IRC: hggdh -------------- 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 brunogirin at gmail.com Wed Jul 7 22:38:51 2010 From: brunogirin at gmail.com (Bruno Girin) Date: Wed, 07 Jul 2010 23:38:51 +0100 Subject: How to use the new Launchpad status? In-Reply-To: <1278538106.7182.10.camel@xango2> References: <1278496104.1813.2.camel@nuuk> <1278516119.2774.48.camel@nuuk> <1278538106.7182.10.camel@xango2> Message-ID: <1278542331.1835.6.camel@nuuk> On Wed, 2010-07-07 at 16:28 -0500, C de-Avillez wrote: > On Wed, 2010-07-07 at 11:00 -0500, Benjamin Root wrote: > > > > > > On Wed, Jul 7, 2010 at 10:21 AM, Bruno Girin > > wrote: > > > > > > A new standard response to use when setting bugs to that status > > > would be good. What about the following? > > > > > Thank you for taking the time to report this bug and helping > > > make Ubuntu better. While we appreciate that the software does > > > not behave as you expect, we consider that it is a matter of > > > opinion whether it should be changed to accommodate your > > > requirement. This bug is being set to "Opinion" to indicate > > > that, although we do not consider it invalid, we will not > > > start work on resolving it until we are satisfied that there > > > are enough details on how to change the software without > > > compromising usability or existing features. > > > > > > > > > > Personally, I would probably avoid the word "appreciate" as it might > > get translated poorly to someone else's language to indicate that we > > like it when the software does not work as expected... > > > > Maybe "understand"? > > Actually, the idea is that the bug is closed -- but marking INVALID > carries a bad connotation. So we want to state that we will not work on > this anymore, but please keep on discussing it. > > New proposal: > > Thank you for taking the time to report this bug and help make Ubuntu > better. This bug is being marked OPINION; this indicates we will not > work on it, but all are free to express their opinions. It is possible > that, in the future, we may revisit this bug. > > @Bruno: If everybody is in agreement, would you mind adding this to the > Responses? No problem. If everybody agrees, I'll update the Reponses page. So if I understand it properly, the idea is that OPINION is less "final" than INVALID or WON'T FIX? Bruno From brian at ubuntu.com Wed Jul 7 23:12:22 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 7 Jul 2010 16:12:22 -0700 Subject: How to use the new Launchpad status? In-Reply-To: <1278496104.1813.2.camel@nuuk> References: <1278496104.1813.2.camel@nuuk> Message-ID: <20100707231222.GD5959@murraytwins.com> On Wed, Jul 07, 2010 at 10:48:24AM +0100, Bruno Girin wrote: > Hi BugSquad, > > Any idea when and how we should use the new Launchpad status [1] when > triaging bugs? > > [1] http://blog.launchpad.net/bug-tracking/new-bugs-status-opinion Keep in mind that "we're treating Opinion as an experiment". As such I would not add it to any standard responses. Additionally, I think this should only be used as a last resort when a bug deals with an issue that "cannot be resolved". N.B. cannot is different than will not (Won't Fix). As an example there might be a bug about Ubuntu bug reports not being fixed which will not stay in an Invalid status because that issue happens to be an important matter to a lot of people. Subsequently, setting a bug like that to Opinion may be a useful thing to do. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Wed Jul 7 20:46:32 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 07 Jul 2010 20:46:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20100707204632.12915.60884@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=54&rev2=55 ------------------------------------------------------------------------------ 5. Press Ctrl-C to stop the logging. 6. Check whether the printer gets correctly detected by the USB subsystem and determine its USB vendor/product IDs and the USB bus and device addresses: <
> {{{$ lsusb}}} <
> Note: The USB bus and device addresses change if you turn off or unplug the printer. Please re-run this command if needed. 7. Check whether the device files for the printer get created and the ownerships ("root lp") and permissions (non-HP: "crw-rw-r--", HP: "crw-rw-r--+") correctly set: <
> {{{$ ls -l /dev/usb/lp* /dev/bus/usb/*/*}}} - 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_deviceid /dev/usb/lp0}}} <
> {{{$ sudo usb_deviceid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines). + 8. Determine the printer's device ID strings: <
> {{{$ sudo usb_printerid /dev/usb/lp0}}} <
> {{{$ sudo usb_printerid /dev/usb/lp1}}} <
> {{{...}}} <
> For HP printers also use <
> {{{$ hp-info -i}}} <
> and choose the printer with the problem from the text menu, then copy the "deviceid" entry from the output (can be several lines). 9. For HP printers: Check whether HPLIP connects to them: <
> {{{$ hp-makeuri :}}}
Replace "" and "" by the bus and device numbers from the "lsusb" output (not vendor and product ID). The numbers must be supplied with three digits, zero-padded from the left, like "008:015". 9. Find out if your printer gets detected by CUPS: <
> {{{$ lpinfo -v}}} 10. Attach the output of the above commands to the bug report. From noreply at ubuntu.com Wed Jul 7 22:53:47 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 07 Jul 2010 22:53:47 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/CommonTasks=22_by_maco=2Em?= Message-ID: <20100707225347.9612.93263@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 maco.m: http://wiki.ubuntu.com/Bugs/CommonTasks?action=diff&rev1=68&rev2=69 The comment on the change is: JFo says kernel team now has a "no dups" policy ------------------------------------------------------------------------------ Bugs are duplicates when they have the same root cause. Determining this is a skill that you'll pick up as you become more familiar with a particular package or subsystem. Bugs are ''not'' necessarily duplicates if they have the same effects. For example, many different bugs can cause X not to start. Determining which bug a particular report refers to is part of triaging. If in doubt, ask for a second opinion. It is probably also sensible to ask the reporter to take look at the possible duplicate and to help with the decision. Reporters are normally interested in helping with their own bug reports! + '''For the above reason, bugs filed on the "linux" package should not be marked as duplicates.''' + When you first look at a new bug, try to find an existing bug in the system that describes the new one. Here's how: * Click the "List open bugs" link at the bottom of the bug page '''or''' From abhi_navale at live.in Thu Jul 8 10:50:21 2010 From: abhi_navale at live.in (Abhijit Navale) Date: Thu, 8 Jul 2010 16:20:21 +0530 Subject: New Member Message-ID: Hello!! This is Abhijit from India. I have read triage guide and subscribe to mailing list. My launchpad id is here: https://launchpad.net/~abhi-navale Please approve my membership to bug squad. _________________________________________________________________ Bollywood This Decade http://entertainment.in.msn.com/bollywoodthisdecade/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhi_navale at live.in Thu Jul 8 10:54:49 2010 From: abhi_navale at live.in (Abhijit Navale) Date: Thu, 8 Jul 2010 16:24:49 +0530 Subject: FW: New Member Message-ID: This is my email id: abhi_navale at live.in _________________________________________________________________ See the news as it happens on MSN videos http://video.in.msn.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Thu Jul 8 12:12:17 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Thu, 8 Jul 2010 13:12:17 +0100 Subject: New recruit Message-ID: Hi everyone, I'm still not entirely sure how I have gotten more closely involved with bugs... mission creep I guess, as I get copies of the ones that affect lubuntu and it was via replying to bugs that I became involved in the doc-team, but that's another story. My wiki page is over at https://wiki.ubuntu.com/phillw so you can all pop over and have a laugh :-) So, to make things official, I apply for membership of the bug-squad team. I signed the C-o-C a while back, I have read the triage document and signed up to the mailing list. Regards, Phill. -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedro at ubuntu.com Thu Jul 8 13:44:32 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Thu, 08 Jul 2010 09:44:32 -0400 Subject: New Member In-Reply-To: References: Message-ID: <1278596672.1947.18.camel@wombat> Hola, El jue, 08-07-2010 a las 16:20 +0530, Abhijit Navale escribió: > Hello!! > This is Abhijit from India. > I have read triage guide and subscribe to mailing list. > My launchpad id is here: https://launchpad.net/~abhi-navale > > Please approve my membership to bug squad. Thanks for helping to make Ubuntu even better and welcome to the team! Have a nice day, pedro. From pedro at ubuntu.com Thu Jul 8 13:46:23 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Thu, 08 Jul 2010 09:46:23 -0400 Subject: New recruit In-Reply-To: References: Message-ID: <1278596783.1947.20.camel@wombat> Hola, El jue, 08-07-2010 a las 13:12 +0100, Phillip Whiteside escribió: > Hi everyone, > > > I'm still not entirely sure how I have gotten more closely involved > with bugs... mission creep I guess, as I get copies of the ones that > affect lubuntu and it was via replying to bugs that I became involved > in the doc-team, but that's another story. > > > My wiki page is over at https://wiki.ubuntu.com/phillw so you can all > pop over and have a laugh :-) > > > So, to make things official, I apply for membership of the bug-squad > team. I signed the C-o-C a while back, I have read the triage > document and signed up to the mailing list. Thanks for helping to make Ubuntu even better and welcome to the team! Have a great day, pedro. From debian at jwiltshire.org.uk Thu Jul 8 14:18:56 2010 From: debian at jwiltshire.org.uk (Jonathan Wiltshire) Date: Thu, 8 Jul 2010 15:18:56 +0100 Subject: Applying to bugsquad Message-ID: <20100708141856.GA14443@lupin.powdarrmonkey.net> Hi, I'd like to be considered for bugsquad membership, primarily to start taking care of the Ubuntu packages flowing from me in Debian. I've read the guides and I'm subscribed to the list. Thanks, -- Jonathan Wiltshire 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: From rkucharski83 at gmail.com Thu Jul 8 14:54:35 2010 From: rkucharski83 at gmail.com (Robert Kucharski) Date: Thu, 8 Jul 2010 10:54:35 -0400 Subject: Logging in and out with multiple users. Message-ID: Hello, I was experimenting with Ubuntu (and Mint) and I noticed some glitches with the logging in and out system (with multiple users). I made a youtube video of it a week ago, but I figured it would be better if one of you guys see it. Thank you for your time Rob http://www.youtube.com/watch?v=avWsDKWrplg -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Thu Jul 8 12:20:32 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 08 Jul 2010 12:20:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20100708122032.32634.82490@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=231&rev2=232 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100701| bugs without a package]] || hugday-20100708 || || [[UbuntuBugDay/20100701| Xkeyboard-config]] || hugday-20100701 || || [[UbuntuBugDay/20100624| Fontconfig]] || hugday-20100624 || || [[UbuntuBugDay/20100617| USB Creator]] || hugday-20100617 || From jeremy.foshee at canonical.com Thu Jul 8 19:05:28 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Thu, 8 Jul 2010 15:05:28 -0400 Subject: Call For Testing: New Kernel Firewire stack in Maverick Message-ID: <20100708190528.GB4064@yoshimitsu> Folks, The Ubuntu Kernel Team would like your help testing the new firewire stack for Maverick. Please let us know the results of your testing via this e-mail thread. The new stack is already enabled in the latest Maverick kernel so all that is needed is the testing at this point. Please note, this is only for the Maverick kernel. The changes have not been made in Lucid Further details can be found on the Call for Testing pages of the Kernel wiki [1]. Thanks! ~JFo [1] https://wiki.ubuntu.com/Kernel/Testing/FirewireStack From phillw at phillw.net Thu Jul 8 19:42:30 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Thu, 8 Jul 2010 20:42:30 +0100 Subject: Call For Testing: New Kernel Firewire stack in Maverick In-Reply-To: <20100708190528.GB4064@yoshimitsu> References: <20100708190528.GB4064@yoshimitsu> Message-ID: Hi Jeremy, can you also make a posting to http://ubuntuforums.org/forumdisplay.php?f=385 As that is where the Meerkat testers live on the main forum. They do not bite, and I'm sure those with firewire would be happy to contribute (I'm sure if you ask, you can get the posting made into a stickie). If this is not possible, I'm happy to post the request up on to there & keep you updated with replies. Regards, Phill. On Thu, Jul 8, 2010 at 8:05 PM, Jeremy Foshee wrote: > Folks, > The Ubuntu Kernel Team would like your help testing the new firewire > stack for Maverick. Please let us know the results of your testing via > this e-mail thread. > > The new stack is already enabled in the latest Maverick kernel so all > that is needed is the testing at this point. Please note, this is only > for the Maverick kernel. The changes have not been made in Lucid > > Further details can be found on the Call for Testing pages of the Kernel > wiki [1]. > > Thanks! > > ~JFo > > [1] https://wiki.ubuntu.com/Kernel/Testing/FirewireStack > > -- > 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 hggdh2 at ubuntu.com Thu Jul 8 19:42:35 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 8 Jul 2010 14:42:35 -0500 Subject: Better Apport Crashes In-Reply-To: References: Message-ID: <20100708144235.3a3b9037@xango2> (I had a slightly longer version of this reply sent earlier on, but my email client had some problems contacting the SMTP server, and decided to unilaterally give up and delete the reply.) On Sun, 2010-07-04 at 00:11 +0300, Kangarooo wrote: > Hello! Hi Kangaroo, Wow! Lots of questions ;-) > 1. if i understand correct then installing all -dbg and -dbgsym > packages for packages i have installed will be running on programm > start. yes no? No. -dbg an -dbgsym are the packages containing the symbols (for gdb usage). None of them are used until you start a debugger. > what does gdb and gdbsym and what other are there? I guess you mean Dbg and Dbgsym, and I guess you meant 'what does dbg and dbgsym mean'. dbg -- DeBuG dbgsym -- DeBugSYMbols Some packages -- mostly those from Debian -- create a separate symbols package during build time. These are called '-dbg'. In this case we will have one single '-dbg' package per *source* package. '-dbgsym's are packages created locally by us, via a back-office process. Here we will have one '-dbgsym' package per *binary* package. You can use either one, but *not* both. And yes, you can mix them -- get the '-dbg' from one package, and '-dbgsym's from different packages. > are they slowing comp? Generically speaking, no. They just use disc space. Depending on how many packages you have installed, you may have from a few 100s MB to a few GB of disc usage. > are they writing all the time so some folder gdb`s? I do not understand what you mean here. > 2. how with one command install all needed packages that does that? > one aptitude command. example sudo aptitude install (check all > installed programms) + to name -gdb > penguin42 gave command for listing all dpkg -l | awk -F' ' '/^ii/ > {print $2"-dbgsym"}' mabe that gives some idea. Frankly, I have no idea why you want to install *all* debug packages. I hope you have a large filesystem (they will be installed, usually, under /usr/lib/debug). But yes, you could play around listing installed packages, and then trying to install the package name + '.dbgsym'. Or you can let apport do the work for you. Still not a single command, but at least you will load *only* the debug pacakges related to what you want to debug. You have to activate apport for that (it is, by default, inactive on released versions of Ubuntu; see [1]. After foloowing the instructions on [1]... lo and behold, all needed (and existing/compatible) debug packages will be installed. > 3. next time when i install some programms what command will install > noninstalled theese gdb tpye packages witch help get better crash > report? example sudo aptitude install (check all installed programms > add -gdb) - (all installed -gdb) No, dbgsyms are not installed automatically. Hope it helps a bit. ..C.. [1] https://wiki.ubuntu.com/DebuggingWithApportRetrace -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From noreply at ubuntu.com Thu Jul 8 19:39:48 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 08 Jul 2010 19:39:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingWithApportRetrace=22_by?= =?utf-8?q?_hggdh2?= Message-ID: <20100708193948.19198.49178@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/DebuggingWithApportRetrace?action=diff&rev1=12&rev2=13 The comment on the change is: do not run GDB as root! ------------------------------------------------------------------------------ == Using apport-retrace == Now, for any package to be installed, you must be running as root (or under a ''fakeroot'' environment, not discussed here). So we run: {{{ - cerdea at xango2:~$ sudo apport-retrace -g /var/crash/_usr_bin_gcalctool.1000.crash + cerdea at xango2:~$ sudo apport-retrace -o trash /var/crash/_usr_bin_gcalctool.1000.crash WARNING: package libsepol1-dbgsym not available }}} + + /!\ we could also run 'sudo apport-retrace -g /var/crash/_usr_bin_gcalctool.1000.crash', but it is not a very good idea to run GDB under root -- unless really needed. + (...) those are the debug symbols packages that would be needed, but could not be found. Hopefully, they will not matter. Keeping on. {{{ WARNING: package perl-base-dbgsym not available @@ -59, +62 @@ Unpacking busybox-initramfs-dbgsym (from .../busybox-initramfs-dbgsym_1%3a1.13.3-1ubuntu9_amd64.ddeb) ... }}} (...) humongous list of symbols packages cut off for sanity + + Now we can run, under our common userId, a GDB session on the crash: {{{ + apport-retrace -g /var/crash/_usr_bin_gcalctool.1000.crash + Setting up libvorbisfile3-dbgsym (1.2.3-3ubuntu1) ... GNU gdb (GDB) 7.1-ubuntu Copyright (C) 2010 Free Software Foundation, Inc. From manoj.iyer at canonical.com Thu Jul 8 20:00:41 2010 From: manoj.iyer at canonical.com (manoj.iyer at canonical.com) Date: Thu, 8 Jul 2010 15:00:41 -0500 (CDT) Subject: Call For Testing: New Kernel Firewire stack in Maverick In-Reply-To: <20100708190528.GB4064@yoshimitsu> References: <20100708190528.GB4064@yoshimitsu> Message-ID: Updated wiki page with testing information. Cheers --- manjo On Thu, 8 Jul 2010, Jeremy Foshee wrote: > Folks, > The Ubuntu Kernel Team would like your help testing the new firewire > stack for Maverick. Please let us know the results of your testing via > this e-mail thread. > > The new stack is already enabled in the latest Maverick kernel so all > that is needed is the testing at this point. Please note, this is only > for the Maverick kernel. The changes have not been made in Lucid > > Further details can be found on the Call for Testing pages of the Kernel > wiki [1]. > > Thanks! > > ~JFo > > [1] https://wiki.ubuntu.com/Kernel/Testing/FirewireStack > > -- > kernel-team mailing list > kernel-team at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/kernel-team > From noreply at ubuntu.com Thu Jul 8 22:43:27 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 08 Jul 2010 22:43:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingSamba=22_by_hggdh2?= Message-ID: <20100708224327.31288.35634@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/DebuggingSamba?action=diff&rev1=11&rev2=12 ------------------------------------------------------------------------------ 1. '''libpam-smbpass''' specific issues. Sharing a folder from the GUI installs libpam-smbpass, which stacks a PAM module that maintains sync between system and samba passwords. Failure in libpam-smbpass may result in inability to login on the system. 1. '''winbind''' specific issues. Winbind allows to get user/group info from a Windows DC. It is sometimes installed by unsuspecting users as a recommended package from Wine. + Also, it is a very good idea to have a look at the official Samba [[ http://samba.org/samba/docs/man/Samba-HOWTO-Collection|HOWTO ]]. You will find there not only a how-to, but also common errors. + = How to file = ## Useful for bug-filers and as a boiler-plate advice for triagers. This is the minimum information required for a bug report. First figure out if the bug falls under one of the generic categories: - 1. samba as a client - 1. samba as a server - 1. install/upgrade failure + 1. [[ #samba-client|samba as a client ]] + 1. [[ #samba-server|samba as a server ]] + 1. [[ samba-pkg-fail|install/upgrade failure ]] 1. libpam-smbpass related 1. winbind related From cyan.spam at gmail.com Thu Jul 8 23:35:04 2010 From: cyan.spam at gmail.com (David Tombs) Date: Thu, 08 Jul 2010 19:35:04 -0400 Subject: Logging in and out with multiple users. In-Reply-To: References: Message-ID: <4C3660A8.6040806@gmail.com> Hi Rob, Sorry for your troubles. The asking for password bug sounds like this bug.[1] Feel free to add a comment that you're experiencing it as well to confirm the bug. The blank screen issue is weirder. I suggest trying one of the support options at (such as the IRC chat) to debug the issue before you file a report. Thanks for your time, David [1] On 07/08/2010 10:54 AM, Robert Kucharski wrote: > Hello, > > I was experimenting with Ubuntu (and Mint) and I noticed some glitches > with the logging in and out system (with multiple users). > I made a youtube video of it a week ago, but I figured it would be > better if one of you guys see it. > > Thank you for your time > > Rob > > > http://www.youtube.com/watch?v=avWsDKWrplg > From phillw at phillw.net Fri Jul 9 00:38:14 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Fri, 9 Jul 2010 01:38:14 +0100 Subject: Call For Testing: New Kernel Firewire stack in Maverick In-Reply-To: References: <20100708190528.GB4064@yoshimitsu> Message-ID: Hi, As you were asking for testing, I have posted it to http://ubuntuforums.org/showthread.php?t=1527050 i will cc my replies from there to this email thread. Regards, Phill. On Thu, Jul 8, 2010 at 9:00 PM, wrote: > > Updated wiki page with testing information. > > > Cheers > --- manjo > > On Thu, 8 Jul 2010, Jeremy Foshee wrote: > > > Folks, > > The Ubuntu Kernel Team would like your help testing the new firewire > > stack for Maverick. Please let us know the results of your testing via > > this e-mail thread. > > > > The new stack is already enabled in the latest Maverick kernel so all > > that is needed is the testing at this point. Please note, this is only > > for the Maverick kernel. The changes have not been made in Lucid > > > > Further details can be found on the Call for Testing pages of the Kernel > > wiki [1]. > > > > Thanks! > > > > ~JFo > > > > [1] https://wiki.ubuntu.com/Kernel/Testing/FirewireStack > > > > -- > > kernel-team mailing list > > kernel-team at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/kernel-team > > > > -- > 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 pedro at ubuntu.com Fri Jul 9 15:20:18 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Fri, 09 Jul 2010 11:20:18 -0400 Subject: Bugsquad Meeting Reminder - Tuesday 13th July 2010 Message-ID: <1278688818.2950.7.camel@wombat> Hello Folks, Just a reminder that the Tuesday 13th of July 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: * Mentorship program update from Mentors * Update/Make new Triage videos * Open Discussions. 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 brian at ubuntu.com Fri Jul 9 20:33:58 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 9 Jul 2010 13:33:58 -0700 Subject: docs/clarification on confirming In-Reply-To: <4C2BEB9C.8000206@gmail.com> References: <20100623183250.GB15843@hallyn.com> <4C22B947.1090604@gmail.com> <1277345276.3737.11.camel@xango2> <20100624192653.GU29399@murraytwins.com> <20100624192900.GA27172@hallyn.com> <20100629194753.GN8308@murraytwins.com> <20100630141158.GB8771@hallyn.com> <4C2BEB9C.8000206@gmail.com> Message-ID: <20100709203358.GK13668@murraytwins.com> On Wed, Jun 30, 2010 at 09:13:00PM -0400, David Tombs wrote: > On 06/30/2010 10:11 AM, Serge E. Hallyn wrote: > > Quoting Brian Murray (brian at ubuntu.com): > >> On Thu, Jun 24, 2010 at 02:29:00PM -0500, Serge E. Hallyn wrote: > >>> The situation I'm referring to is where upstream requires email list > >>> interaction, and we are asking the launchpad bug submitter to forward > >>> the patch. Do we then set it to 'Confirmed' until the submitter > >>> forwards to the appropriate list, and then set it to 'Triaged'? Or > >>> still just set it to 'Triaged' immediately? > >> > >> Triaged is most appropriate. > > > > Great, thanks! > > > > -serge > > > > Hi all, > > Updated the wiki to include this.[1] Everyone good with the wording? Thanks for doing this! I made a slight change to the wording in the hopes that Bug Squad members would not feel that a bug has to be Triaged to be forwarded. -- 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 marconifabio at hotmail.it Fri Jul 9 20:33:47 2010 From: marconifabio at hotmail.it (Fabio Marconi) Date: Fri, 09 Jul 2010 22:33:47 +0200 Subject: Presentation Message-ID: Hello everybody, I'm a new member (pending approval) and i would try if i will be a valid help in bug triaging. So I hope in my approval in bugsquad group I'm an active member of iso testing locoteam-it. Do you want some news of today ? Ubuntu Alternate amd64 fail install cause imagemagik unmet dependencies, xubuntu amd64, install Ok, resume from screensaver don't ask password and mouse is invisible. probably work in progress, but if in three days nothing change, i'll report the bugs. ;)Fabio From brian at ubuntu.com Fri Jul 9 20:37:25 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 9 Jul 2010 13:37:25 -0700 Subject: Why don't we ask for kern.log? In-Reply-To: References: Message-ID: <20100709203725.GL13668@murraytwins.com> On Fri, Jun 25, 2010 at 10:27:48PM -0400, Steven wrote: > Hi, I was curious why I haven't seen anyone ask for kern.log, especially for > kernel or graphics bugs. Is there sensitive information in there? Is the > computer name too private? > > It seems much easier to ask for kern.log than dmesg, since: > 1) If the system freezes and you have to reboot, dmesg and /var/log/dmesg > aren't relevant anymore, so uploading kern.log guarantees you have the > correct dmesg for the bug. > 2) The timestamps make it very easy to pinpoint where the error should be > and lessen the chance to misinterpret irrelevant messages as messages that > are related to the bug. This is a great question and hopefully Jeremy, who I am cc'ing, can shed some light on 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 ilidrissiamine at gmail.com Fri Jul 9 20:55:04 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Fri, 9 Jul 2010 21:55:04 +0100 Subject: Presenting myself Message-ID: Hi, I'm Mohamed Amine IL Idrissi, and I'm a Moroccan user of Ubuntu since 2006. I'm writing this just to introduce myself to the team :) I just joined the bug squad though (by proposal of Pedro Villavicencio, a really nice guy btw), so excuse me if I'm not up to the task of bug triaging :( So, that's all for now. I hope I can now contribute more to Ubuntu, especially since I joined the Bug Squad :) devildante -------------- next part -------------- An HTML attachment was scrubbed... URL: From rohangarg at ubuntu.com Fri Jul 9 20:57:45 2010 From: rohangarg at ubuntu.com (Rohan Garg) Date: Sat, 10 Jul 2010 02:27:45 +0530 Subject: Presentation In-Reply-To: References: Message-ID: Hi Fabio Please report any bugs that you find ASAP,that way the other testers know about them and can provide more feedback,this also gives the devs and idea of what might be going wrong ;) Regards Rohan Garg On Sat, Jul 10, 2010 at 2:03 AM, Fabio Marconi wrote: > Hello everybody, > I'm a new member (pending approval) > and i would try if i will be a valid help in bug triaging. > So I hope in my approval in bugsquad group > I'm an active member of iso testing locoteam-it. > Do you want some news of today ? > Ubuntu Alternate amd64 fail install cause imagemagik unmet > dependencies, > xubuntu amd64, install Ok, resume from screensaver don't ask password > and mouse is invisible. > probably work in progress, but if in three days nothing change, i'll > report the bugs. > ;)Fabio > > > -- > 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 cjk at teamcharliesangels.com Fri Jul 9 21:13:03 2010 From: cjk at teamcharliesangels.com (Charlie Kravetz) Date: Fri, 9 Jul 2010 15:13:03 -0600 Subject: Presentation In-Reply-To: References: Message-ID: <20100709151303.1634cb61@teamcharliesangels.com> On Sat, 10 Jul 2010 02:27:45 +0530 Rohan Garg wrote: > Hi Fabio > Please report any bugs that you find ASAP,that way the other testers know > about them and can provide more feedback,this also gives the devs and idea > of what might be going wrong ;) > > Regards > Rohan Garg Actually, standard procedure when testing the daily images is to not report the bugs immediately, but rather to wait at least 24 hours to see if it does get fixed. This prevents wasting time for both the tester and the developers, when the bug being reported is a "less then 24 hour" bug. > > On Sat, Jul 10, 2010 at 2:03 AM, Fabio Marconi wrote: > > > Hello everybody, > > I'm a new member (pending approval) > > and i would try if i will be a valid help in bug triaging. > > So I hope in my approval in bugsquad group > > I'm an active member of iso testing locoteam-it. > > Do you want some news of today ? > > Ubuntu Alternate amd64 fail install cause imagemagik unmet > > dependencies, > > xubuntu amd64, install Ok, resume from screensaver don't ask password > > and mouse is invisible. > > probably work in progress, but if in three days nothing change, i'll > > report the bugs. > > ;)Fabio > > > > > > -- > > Ubuntu-bugsquad mailing list > > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -- Charlie Kravetz Linux Registered User Number 425914 [http://counter.li.org/] Never let anyone steal your DREAM. [http://keepingdreams.com] From rohangarg at ubuntu.com Fri Jul 9 21:17:15 2010 From: rohangarg at ubuntu.com (Rohan Garg) Date: Sat, 10 Jul 2010 02:47:15 +0530 Subject: Presentation In-Reply-To: <20100709151303.1634cb61@teamcharliesangels.com> References: <20100709151303.1634cb61@teamcharliesangels.com> Message-ID: Oh.. i didnt know that,sorry for the confusion i created there. On Sat, Jul 10, 2010 at 2:43 AM, Charlie Kravetz wrote: > On Sat, 10 Jul 2010 02:27:45 +0530 > Rohan Garg wrote: > > > Hi Fabio > > Please report any bugs that you find ASAP,that way the other testers know > > about them and can provide more feedback,this also gives the devs and > idea > > of what might be going wrong ;) > > > > Regards > > Rohan Garg > > Actually, standard procedure when testing the daily images is to not > report the bugs immediately, but rather to wait at least 24 hours to > see if it does get fixed. This prevents wasting time for both the > tester and the developers, when the bug being reported is a "less then > 24 hour" bug. > > > > > On Sat, Jul 10, 2010 at 2:03 AM, Fabio Marconi >wrote: > > > > > Hello everybody, > > > I'm a new member (pending approval) > > > and i would try if i will be a valid help in bug triaging. > > > So I hope in my approval in bugsquad group > > > I'm an active member of iso testing locoteam-it. > > > Do you want some news of today ? > > > Ubuntu Alternate amd64 fail install cause imagemagik unmet > > > dependencies, > > > xubuntu amd64, install Ok, resume from screensaver don't ask password > > > and mouse is invisible. > > > probably work in progress, but if in three days nothing change, i'll > > > report the bugs. > > > ;)Fabio > > > > > > > > > -- > > > Ubuntu-bugsquad mailing list > > > Ubuntu-bugsquad at lists.ubuntu.com > > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > > > > > > -- > Charlie Kravetz > Linux Registered User Number 425914 [http://counter.li.org/] > Never let anyone steal your DREAM. [http://keepingdreams.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 noreply at ubuntu.com Fri Jul 9 20:32:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 09 Jul 2010 20:32:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_brian-murray?= Message-ID: <20100709203234.28657.88720@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The following page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=41&rev2=42 ------------------------------------------------------------------------------ * '''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 * Use this when you are confident that it should be looked at by a developer '''and''' has enough information - * Ideally a bug's Ubuntu task will be Triaged before any upstream activity occurs + * While not a requirement a bug's Ubuntu task status will be Triaged before any upstream forwarding occurs * '''In Progress''': * If '''you''' are working on fixing a bug, set it to {{{In Progress}}} so people know what's going on * {{{In Progress}}} bugs should be assigned to the person working on them From noreply at ubuntu.com Fri Jul 9 21:46:19 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 09 Jul 2010 21:46:19 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_hggdh2?= Message-ID: <20100709214619.11876.94067@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/DebuggingProcedures?action=diff&rev1=99&rev2=100 The comment on the change is: added MySQL and Samba ------------------------------------------------------------------------------ * [[DebuggingApache2|Apache 2]] * [[DebuggingLTSP|LTSP]] * [[DebuggingKVM|KVM]] + * [[DebuggingMySQL|MySQL]] + * [[DebuggingSamba|Samba]] == Hardware == From noreply at ubuntu.com Fri Jul 9 22:01:21 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 09 Jul 2010 22:01:21 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingMySQL=22_by_hggdh2?= Message-ID: <20100709220121.17888.36385@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/DebuggingMySQL?action=diff&rev1=13&rev2=14 ------------------------------------------------------------------------------ Thank you for taking the time to report this bug and helping to make Ubuntu better. Could you please provide the following information: - * content of /var/log/daemon.log related to mysql processes: - /var/log/daemon.log - * apparmor audit messages related to mysqld. The output of the command: + grep audit /var/log/kern.log - - egrep 'audit\(|apparmor|selinux|security' /var/log/kern.log - - * mysqld apparmor profile: + * mysqld apparmor profile and abstraction: - /etc/apparmor.d/usr.sbin.mysqld - + /etc/apparmor.d/abstractions/mysqld * list of mysqld apparmor profiles: - ls -l /etc/apparmor.d/usr.sbin.mysqld* - * mysql configuration stripped of private information (such as password): - /etc/mysql/my.cnf - * extra mysql configuration from the conf.d directory: - /etc/mysql/conf.d/ - * directory listing of mysql datadir (by default /var/lib/mysql): - - ls -l /var/lib/mysql + sudo ls -l /var/lib/mysql ======================= From brian at ubuntu.com Fri Jul 9 22:32:40 2010 From: brian at ubuntu.com (Brian Murray) Date: Fri, 9 Jul 2010 15:32:40 -0700 Subject: New Launchpad Bug Mail Header Message-ID: <20100709223240.GM13668@murraytwins.com> I wanted to let you all know about a new header that you can find in emails from Launchpad bug reports. It is "X-Launchpad-Reporter" and identifies the person who originally opened a bug report. Full details and another change can be found at my blog[1]. http://www.murraytwins.com/blog/?p=77 I use this header to filter on bugs that I've reported. -- 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 wondershot at verizon.net Sat Jul 10 00:15:07 2010 From: wondershot at verizon.net (Sean McGowan) Date: Fri, 09 Jul 2010 20:15:07 -0400 Subject: intro Message-ID: <1278720907.1774.8.camel@hp1> Hello all, I recently requested a mentor and am looking to help out in the community. I work on a Solaris system at work and have been running Ubuntu at home since Intrepid. I tinkered with various other distros and have come to the conclusion that I will be sticking with Ubuntu for the time being. I hope to be assigned a mentor at this Tuesday's meeting; however, I will be unable to attend. I can answer any questions regarding my background upon request so that I can be put to use. -- Sean McGowan // Chuck Norris can divide by zero. From noreply at ubuntu.com Fri Jul 9 22:15:07 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 09 Jul 2010 22:15:07 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_hggdh2?= Message-ID: <20100709221507.17992.8799@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/DebuggingProcedures?action=diff&rev1=100&rev2=101 The comment on the change is: added OpenLDAP ------------------------------------------------------------------------------ * [[DebuggingLTSP|LTSP]] * [[DebuggingKVM|KVM]] * [[DebuggingMySQL|MySQL]] + * [[DebuggingOpenldap]] * [[DebuggingSamba|Samba]] == Hardware == From noreply at ubuntu.com Fri Jul 9 22:34:22 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 09 Jul 2010 22:34:22 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProcedures=22_by_hggdh2?= Message-ID: <20100709223422.25017.42669@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/DebuggingProcedures?action=diff&rev1=101&rev2=102 ------------------------------------------------------------------------------ * [[DebuggingLTSP|LTSP]] * [[DebuggingKVM|KVM]] * [[DebuggingMySQL|MySQL]] - * [[DebuggingOpenldap]] + * [[DebuggingOpenldap|Open LDAP]] * [[DebuggingSamba|Samba]] == Hardware == From braiamp at gmail.com Sun Jul 11 14:24:21 2010 From: braiamp at gmail.com (Braiam Peguero) Date: Sun, 11 Jul 2010 10:24:21 -0400 Subject: Problema con el Ubuntu 10.04 en una laptop Compaq In-Reply-To: References: <000601cb191f$31a33050$1800010a@usuario> Message-ID: <4C39D415.5080706@gmail.com> El 07/07/10 15:15, Phillip Whiteside escribió: > Hi Fransico, This being translated by google translation, so it will > probably not read quite correctly. I appreciate you have a bug but I > do not think the bug-squad can look into it, until you have registered > it as bug using https://help.ubuntu.com/community/ReportingBugs_es > while that happens I'd like to suggest that you try a minimal > installation and then add the lubuntu desktop onto that. There are > instructions for that > at https://wiki.ubuntu.com/Lubuntu/DocumentationHelp#Minimal Install > If > you would like me to run google translate over them for you, please ask. > > Hi BugSquad, I've suggested something that may help, and also copied > this to the lubuntu mailing list. I'm still new at bug squad things, > so please forgive me if I have done something wrong > > Regards, > > Phill. > > Hola Fransico, esta siendo traducido por traducción de Google, por lo > que probablemente no lea toda la razón. Le agradezco que haya un > error, pero no creo que el error de los escuadrones pueden mirar en > él, hasta que se ha registrado como fallo > usando https://help.ubuntu.com/community/ReportingBugs_es > mientras eso sucede me gustaría sugerir que trate de una instalación > mínima y luego añadir el escritorio lubuntu en eso. Hay instrucciones > para que en la > dirección https://wiki.ubuntu.com/Lubuntu/DocumentationHelp#Minimal > Install > Si > me gusta correr traductor Google sobre ellos para usted, por favor > pregunte. > > Hola BugSquad, he sugerido algo que puede ayudar, y copian esto a la > lista de correo lubuntu. Todavía estoy en las cosas nuevas escuadrón > de errores, así que por favor me perdone si he hecho algo mal > Un cordial saludo, > > Phill. > > 2010/7/1 Francisco Davila > > > Saludos a todos: > Disculpen les escriba en español pero mi ingles no es nada bueno. > Deseaba consultarles el siguiente problema: > Tengo una laptop Compaq Presario 1215US (40Gb disco, 320Mb RAM CPU > Athlon 4 1Ghz chiset VIA686A) a la cual necesito por situaciones > de estudio instalarle el sistema GNU Ubuntu. Como la laptop esta > algo limitada en recursos no utilice la instalacion grafica y opte > por realizar la instalacion utilizando la version Alternate de > Ubuntu 10.04 instalando en modo de linea de comando. > Posteriormente instale los paquetes adecuados (Gnome Office, el > navegador Midori, el gestor de correo Sylpheed y otras > aplicaciones ligeras. Concluida la instalacion de los paquetes al > reiniciar comienza la carga del sistema, pero inesperadamente la > laptop "se cuelga". El problema no ocurre siempre en el mismo > punto, a veces logro llegar a la pantalla de login, otras > veces logro incluso entrar al sistema y entonces se cuelga al > intentar abrir cualquier programa. Repeti la instalacion varias > veces utilizando el desktop XFCE (Xubuntu 10.04) y sucede lo > mismo. Llegue a probar con LXDE (Lubuntu 10.04) y lo mismo. > Consulte el log y en el inicio de la carga del sistema me aparece > lo siguiente: > > [8.828369] ACPI: I/O resource vt596_smbus [0x8100-0x8107] > conflicts with ACPI region SMIO [0x8100-0x8106] > [8.965801] via686a 0000:00:07.4: base adress not set - upgrade > BIOS or use force_addr=0xaddr > > En una prueba ulterior con la base ubuntu 10.04 y el entorno lxde > instalado (solo el paquete lxde, sin instalar el paquete de > lubuntu-desktop completo) con algunas aplicaciones (Abiword, > Gnumeric, Sylpheed y Midori) arranque en modo recuperacion, inicie > una sesion de consola como root y cargue el sistema con el comando > startx y todo funciona bien, puedo utilizar la laptop por horas > sin que ocurra ningun problema. Reinicie en el modo normal y de > nuevo se cuelga. > Esperando puedan ayudarme gracias a todos desde ya. Saludos > cordiales. Frank > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > Francisco Davila > 2010/7/1 > Greetings to all: > Sorry I write in Spanish, but my English is not good. He wanted to > consult the following problem: > I have a Compaq Presario 1215US laptop (40GB drive, 320MB RAM 1Ghz CPU > Athlon 4 chiset via686) to which I need to study situations putting on > Ubuntu GNU system. As the laptop is somewhat limited in resources do > not use the graphical installer and choose to install using the > Alternate version of Ubuntu 4.10 installed in command line mode. Then > install the appropriate packages (Gnome Office, Midori browser, > Sylpheed mail manager and other lightweight applications. After the > installation of packages when you restart the system begins loading, > but suddenly the laptop "hangs." The problem does not occur always in > the same spot, sometimes made it to the login screen, sometimes > achieving even enter the system and then hangs when trying to open any > program. I repeated the installation several times using the XFCE > desktop (Xubuntu 10.04) and same thing happens . Get to try out LXDE > (Lubuntu 10.04) and the same. View the log and the start of loading of > the system I get the following: > > [8.828369] ACPI: I/O resource vt596_smbus [0x8100-0x8107] conflicts > with ACPI region SMIO [0x8100-0x8106] > [8.965801] via686a 0000:00:07.4: base adress not set - upgrade BIOS or > use force_addr=0xaddr > > In a subsequent test with the base ubuntu lxde 10.04 and the > environment installed (only lxde package, without installing the > package lubuntu full-desktop) with some applications (Abiword, > Gnumeric, Sylpheed and Midori) boot in recovery mode, log console as > root and load the system with the command startx and everything works > fine, I can use the laptop for hours without any problem > occurs. Reboot into normal mode and again hangs. > Hoping you can help me thank you all from now on. Best Regards. Frank Hopefully, I can talk the both languages, so I can make a better translation that Google, for at least more comprehensible because the original was a disaster. Hola Francisco, Lo que Phill deseo decirte es que el Bugsquad, no puede rastrear el error para ayudarte hasta que no lo reportes como tal en launchpad.net, para lo cual encontraras útil https://help.ubuntu.com/community/ReportingBugs_es, tendrás que registrarte en Launchpad y llenar un informe con el error. Mientras tanto el sugiere una instalación minima y luego que le instales lubuntu-desktop. Aunque podria decirte que por el mensaje de error, indica que probablemente el BIOS de tu equipo este desactualizado y por lo tanto causando problemas con el sistema que tratas de instalar. -- Braiam Peguero launchpad.net/~braiamp -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 294 bytes Desc: OpenPGP digital signature URL: From noreply at ubuntu.com Sun Jul 11 06:44:34 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 11 Jul 2010 06:44:34 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/UpstreamHeader=22_by_vish?= Message-ID: <20100711064434.14854.778@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/UpstreamHeader?action=diff&rev1=6&rev2=7 The comment on the change is: updating debian link ------------------------------------------------------------------------------ - ||{{attachment:ubuntu.png}}||[[Bugs|Bugs]]||||{{attachment:gnome.png}}||[[Bugs/Upstream/GNOME|GNOME]]||||{{attachment:kde.png}}||[[Bugs/Upstream/KDE|KDE]]||||||{{attachment:mozilla.png}}||[[Bugs/Upstream/Mozilla|Mozilla]]||||||{{attachment:openoffice.png}}||[[Bugs/Upstream/OpenOffice|OpenOffice]]||||{{attachment:kernel.png}}||[[Bugs/Upstream/kernel|Kernel]]||||{{attachment:freedesktop.png}}||[[Bugs/Upstream/Freedesktop|FreeDesktop]]||||||{{attachment:debian.png}}||[[Bugs/Upstream/Debian|Debian]]|| + ||{{attachment:ubuntu.png}}||[[Bugs|Bugs]]||||{{attachment:gnome.png}}||[[Bugs/Upstream/GNOME|GNOME]]||||{{attachment:kde.png}}||[[Bugs/Upstream/KDE|KDE]]||||||{{attachment:mozilla.png}}||[[Bugs/Upstream/Mozilla|Mozilla]]||||||{{attachment:openoffice.png}}||[[Bugs/Upstream/OpenOffice|OpenOffice]]||||{{attachment:kernel.png}}||[[Bugs/Upstream/kernel|Kernel]]||||{{attachment:freedesktop.png}}||[[Bugs/Upstream/Freedesktop|FreeDesktop]]||||||{{attachment:debian.png}}||[[Debian/Bugs|Debian]]|| From ddecator at gmail.com Sun Jul 11 20:02:52 2010 From: ddecator at gmail.com (Draycen DeCator) Date: Sun, 11 Jul 2010 16:02:52 -0400 Subject: Proposed Wiki Style Message-ID: Hey everyone! After fighting with the formatting for a while, I finally found a way to make the BugSquad wiki pages more closely match the awesome style Pedro came up with for https://wiki.ubuntu.com/BugSquad Unfortunately, there are some complications. In order to make the style work, the Table of Contents needs to be manually made. As a result, removing/adding sections will be more complicated than before when the TOC was automatically created. The style is also different from most other wiki pages, but I like it better so I don't think that is as big of a deal. I applied the styling to https://wiki.ubuntu.com/Bugs/HowToTriage so everyone can give feedback on whether we want to stick with the new style or not. I'm willing to do the work to apply the style to the different pages, I just want us to agree on the idea before I do any more. I can also add to /HowToTriage so more headers are in the new style. Please let me know what you think, and I hope you are all having a great weekend. Dray [ddecator] -------------- next part -------------- An HTML attachment was scrubbed... URL: From abhijit.foss at gmail.com Sun Jul 11 20:44:19 2010 From: abhijit.foss at gmail.com (Abhijit Navale) Date: Mon, 12 Jul 2010 02:14:19 +0530 Subject: New email Message-ID: Hello! This is my new Email. :) -- *Abhijit Navale.* -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sun Jul 11 19:58:11 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Sun, 11 Jul 2010 19:58:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/HowToTriage=22_by_ddecator?= Message-ID: <20100711195811.7524.3376@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 ddecator: http://wiki.ubuntu.com/Bugs/HowToTriage?action=diff&rev1=129&rev2=130 The comment on the change is: Changed the style to better match /BugSquad, will email ML to get feedback on whether to keep the changes or not ------------------------------------------------------------------------------ <> - ||<>|| + ||Contents<
>    1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20Types|Bug Types]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20reports|Apport reports]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Apport%20crash%20reports|Apport crash reports]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirmed%20bugs|Confirmed bugs]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Feature%20Requests|Feature Requests]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Regressions|Regressions]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Untriaged%20bugs|Untriaged bugs]]<
>        6. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Bug%20reports%20not%20in%20English|Bug reports not in English]]<
>        7. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Special%20types%20of%20bugs|Special types of bugs]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Developer%20Process%20Bugs|Developer Process Bugs]]<
>            2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Needs%20Packaging%20Bugs|Needs Packaging Bugs]]<
>            3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Security%20Bugs|Security Bugs]]<
>            4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Translation%20Bugs%20and%20Launchpad%20integration|Translation Bugs and Launchpad integration]]<
>    2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Actions|Actions]]<
>        1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Confirming|Confirming]]<
>        2. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Forwarding%20upstream|Forwarding upstream]]<
>            1. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20a%20Bug%20as%20Requiring%20Forwarding|Marking a Bug as Requiring Forwarding]]<
>        3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Marking%20duplicate|Marking duplicate]]<
>        4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Improving%20a%20bug%20report|Improving a bug report]]<
>        5. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Invalidating|Invalidating]]<
>    3. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Status%20and%20Importance|Status and Importance]]<
>    4. [[https://wiki.ubuntu.com/Bugs/HowToTriage#Looking%20through%20your%20bugs|Looking through your bugs]]|| In a hospital, triage happens the instant a patient arrives through the emergency room doors. His vital signs are checked, his status assessed, and he gets sorted in amongst all the other patients waiting for treatment. @@ -14, +14 @@ Working on simple, untriaged bugs is a good way to get started and become acquainted with the triaging procedure since you'll have to deal with every aspect of the life cycle of a bug. The section [[#untriaged|Untriaged bugs]] explains where to find them. - = Bug types = + <> + ||{{attachment:bugsquad.png}}||'''Bug Types'''|| == Apport reports == @@ -82, +83 @@ Once tagged, the bugs will appear on the [[http://qa.ubuntu.com/reports/regression/regression_tracker.html|regression tracking page]] and will from there be escalated to the development teams. See [[QATeam/RegressionTracking]] for more information. - <> == Untriaged bugs == Untriaged bugs are bugs that haven't been touched by any triager yet. These bugs were reported and have yet to be touched since. @@ -171, +171 @@ Apart from opening the 'ubuntu-translations' task to let the [[Translations]] team know the bug exists the bug should be handled like any bug. When its status in the 'ubuntu' project is [[#Confirmed_bugs|set to 'Triaged']] they know the report is ready for them to work on. - = Actions = + <> + ||{{attachment:actions.png}}||'''Actions'''|| Below are some common actions you will perform while Triaging. The [[https://launchpad.net/launchpad-gm-scripts |Launchpad Greasemonkey scripts]] can be a great time-saver while performing the below actions! @@ -195, +196 @@ The 'Triaged' status is used to show you are done with triaging the bug. Only members of the Ubuntu Bug Control team can set this status. Only set this status if the cause of the bug has been found and the developers can start fixing the problem right away. - <> == Forwarding upstream == Forwarding bugs upstream is an important part of being a triager. Without telling them, upstream developers might never know of the bug you've been triaging so studiously. @@ -249, +249 @@ ---- CategoryBugSquad - <> == Improving a bug report == Only valid and well described bugs can be processed efficiently and swiftly by the developers. A small guide at [[Bugs/Improving]] helps with handing over a good bug to the developers when setting the status 'Triaged'. @@ -266, +265 @@ <> - = Status and Importance = + <> + ||{{attachment:importance.png}}||'''Status and Importance'''|| The default meanings of Importances and Statuses are explained at [[Bugs/Importance]] and [[Bugs/Status]]. Make sure you've read these pages thoroughly. If in doubt, the maintainer (or the one working on the bug) should change the Status and Importance. It usually reflects the status of this work or reflects how the bug fits into her/his working time. - = Looking through your bugs = + <> + ||{{attachment:bugsquad.png}}||'''Looking through your bugs'''|| Perhaps you want to look at a list of bugs you are working on to see if anyone has replied and to make sure you haven't forgotten one. From noreply at ubuntu.com Mon Jul 12 07:12:58 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Mon, 12 Jul 2010 07:12:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingProgramCrash=22_by_yann?= =?utf-8?q?ubuntu?= Message-ID: <20100712071258.27985.98291@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 yannubuntu: http://wiki.ubuntu.com/DebuggingProgramCrash?action=diff&rev1=104&rev2=105 The comment on the change is: missing space ------------------------------------------------------------------------------ 1. Stable releases (not alphas and betas) require three more lines adding to the same file, which is done by the following terminal command: {{{ echo "deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse - deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse + deb http://ddebs.ubuntu.com $(lsb_release -cs)-security main restricted universe multiverse deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list }}} From txwikinger at ubuntu.com Mon Jul 12 14:20:07 2010 From: txwikinger at ubuntu.com (Ralph Janke) Date: Mon, 12 Jul 2010 10:20:07 -0400 Subject: Announcing the Next Kubuntu Bug Day! - July 12th 2010 Message-ID: <4C3B2497.10908@ubuntu.com> Fellow Ubuntu Triagers! This week's Kubuntu Bug Day target is K3bBugs. * 45 New bugs * 23 Incomplete nugs * 23 Confirmed bugs need a hug. 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 or #kubuntu-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 pagehttps://wiki.ubuntu.com/UbuntuBugDay/Planning If you're new to all this and you want to know more about ubuntu?, head tohttp://wiki.ubuntu.com/Bugs Have a nice day, txwikinger [From the BugSquad] -------------- next part -------------- An HTML attachment was scrubbed... URL: From pedro at ubuntu.com Mon Jul 12 14:37:46 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 12 Jul 2010 10:37:46 -0400 Subject: Proposed Wiki Style In-Reply-To: References: Message-ID: <1278945466.2115.31.camel@wombat> Hello Dray, On dom, 2010-07-11 at 16:02 -0400, Draycen DeCator wrote: > Hey everyone! > > After fighting with the formatting for a while, I finally found a way > to make the BugSquad wiki pages more closely match the awesome style > Pedro came up with for https://wiki.ubuntu.com/BugSquad > > Unfortunately, there are some complications. In order to make the > style work, the Table of Contents needs to be manually made. As a > result, removing/adding sections will be more complicated than before > when the TOC was automatically created. The style is also different > from most other wiki pages, but I like it better so I don't think that > is as big of a deal. I don't think is a big deal either, we could put a note on the wiki pages to say they need to add the new content (if applies) to the TOC. > > I applied the styling to https://wiki.ubuntu.com/Bugs/HowToTriage so > everyone can give feedback on whether we want to stick with the new > style or not. I'm willing to do the work to apply the style to the > different pages, I just want us to agree on the idea before I do any > more. I can also add to /HowToTriage so more headers are in the new > style. > > Please let me know what you think, and I hope you are all having a > great weekend. Looks awesome to me!, thanks for working on it Dray! let's see what the other BugSquad members say about it ;-) Have a great day, pedro. From nigelbabu at gmail.com Mon Jul 12 15:35:26 2010 From: nigelbabu at gmail.com (Nigel Babu) Date: Mon, 12 Jul 2010 21:05:26 +0530 Subject: Proposed Wiki Style In-Reply-To: <1278945466.2115.31.camel@wombat> References: <1278945466.2115.31.camel@wombat> Message-ID: Hi Dray: I think its awesome. Its a bit of work and I appreciate you taking the challenge of doing it! Warm Regards Nigel Babu On Mon, Jul 12, 2010 at 8:07 PM, Pedro Villavicencio Garrido wrote: > Hello Dray, > > On dom, 2010-07-11 at 16:02 -0400, Draycen DeCator wrote: >> Hey everyone! >> >> After fighting with the formatting for a while, I finally found a way >> to make the BugSquad wiki pages more closely match the awesome style >> Pedro came up with for https://wiki.ubuntu.com/BugSquad >> >> Unfortunately, there are some complications. In order to make the >> style work, the Table of Contents needs to be manually made. As a >> result, removing/adding sections will be more complicated than before >> when the TOC was automatically created. The style is also different >> from most other wiki pages, but I like it better so I don't think that >> is as big of a deal. > > I don't think is a big deal either, we could put a note on the wiki > pages to say they need to add the new content (if applies) to the TOC. > >> >> I applied the styling to https://wiki.ubuntu.com/Bugs/HowToTriage so >> everyone can give feedback on whether we want to stick with the new >> style or not. I'm willing to do the work to apply the style to the >> different pages, I just want us to agree on the idea before I do any >> more. I can also add to /HowToTriage so more headers are in the new >> style. >> >> Please let me know what you think, and I hope you are all having a >> great weekend. > > Looks awesome to me!, thanks for working on it Dray! let's see what the > other BugSquad members say about it ;-) > > Have a great day, > > pedro. > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > From gomyhr at gmail.com Mon Jul 12 17:24:54 2010 From: gomyhr at gmail.com (Geir Ove Myhr) Date: Mon, 12 Jul 2010 19:24:54 +0200 Subject: Proposed Wiki Style In-Reply-To: References: <1278945466.2115.31.camel@wombat> Message-ID: Draycen, I think the page looks great, but I would still like to voice the other opinion. To me, it is more valuable to have a wiki page that is easy to edit than one that has a better look. For "portal like" pages like https://wiki.ubuntu.com/BugSquad have great look at the expense of more workload is fine, but regular pages I don't think it is worth it. Just my opinion. Happy to see this change happen if the majority thinks otherwise. Geir Ove From ilidrissiamine at gmail.com Mon Jul 12 20:14:57 2010 From: ilidrissiamine at gmail.com (Mohammed Amine IL Idrissi) Date: Mon, 12 Jul 2010 21:14:57 +0100 Subject: Proposed Wiki Style In-Reply-To: References: <1278945466.2115.31.camel@wombat> Message-ID: Hi Dray, Just saw this wiki page, and I must say that it's amazing! I really liked the BugSquad design, so I'm really looking forward to have other BugSquad pages be redesigned. Keep up the good work, Mohamed Amine -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Mon Jul 12 23:07:58 2010 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 12 Jul 2010 19:07:58 -0400 Subject: Proposed Wiki Style In-Reply-To: References: <1278945466.2115.31.camel@wombat> Message-ID: <4C3BA04E.9050805@gmail.com> On 07/12/2010 01:24 PM, Geir Ove Myhr wrote: > Draycen, I think the page looks great, but I would still like to voice > the other opinion. To me, it is more valuable to have a wiki page that > is easy to edit than one that has a better look. For "portal like" > pages like https://wiki.ubuntu.com/BugSquad have great look at the > expense of more workload is fine, but regular pages I don't think it > is worth it. > > Just my opinion. Happy to see this change happen if the majority > thinks otherwise. > > Geir Ove > I concur. I appreciate your efforts, Dray, but I think the maintenance effort spent on keeping TOC's updated would be much better spent on the page content. Regards, David From marc.tardif at ubuntu.com Tue Jul 13 13:49:30 2010 From: marc.tardif at ubuntu.com (Marc Tardif) Date: Tue, 13 Jul 2010 09:49:30 -0400 Subject: QA Team Meeting Reminder - July 14 2010, 1700 UTC Message-ID: <20100713134930.GC1984@jrrr.montreal> Hello Folks, Just a reminder that the Wednesday 14 of July at 1700 UTC we're having our weekly QA meeting at #ubuntu-quality on FreeNode. If there's anything else you'd like to discuss, please add it to: * https://wiki.ubuntu.com/QATeam/Meetings So far the agenda looks like: * review previous action items (all) * SRU testing -- sbeattie (Steve Beattie) * Bug Day status -- pvillavi * Blueprints update -- all * Selection of new chair - cr3 Thanks!, Marc From kamusin at gmail.com Tue Jul 13 18:32:18 2010 From: kamusin at gmail.com (Kamus) Date: Tue, 13 Jul 2010 14:32:18 -0400 Subject: Announcing the Next Ubuntu Bug Day! - July 15th 2010 Message-ID: Fellow Ubuntu Triagers! This week's Bug Day target is *drum roll please* Pidgin! * 100 New bugs need a hug * 78 Incompletes bugs need a status check * 100 Confirmed bugs need a review Bookmark it, add it to your calendars, turn over those egg-timers! * Thursday 15th July 2010 * https://wiki.ubuntu.com/UbuntuBugDay/20100715 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 and you want to know more about ubuntu?, head to http://wiki.ubuntu.com/Bugs Have a nice day, Kamus [From the BugSquad] -- Victor Vargas B. Latitud:  -33.439177,-70.625267 Santiago, Chile. From noreply at ubuntu.com Tue Jul 13 20:33:05 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 13 Jul 2010 20:33:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingOpenldap=22_by_hggdh2?= Message-ID: <20100713203305.837.11950@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/DebuggingOpenldap?action=diff&rev1=8&rev2=9 The comment on the change is: added FAQ link for using TLS/SSL ------------------------------------------------------------------------------ = Introduction = Bugs relating to openldap typically fall into 1 category: - 1. SSL connections not working. + 1. SSL connections not working (it is most probably a good idea to read the OpenLDAP FAQ about [[http://www.openldap.org/faq/data/cache/185.html|using TLS/SSL]]). = How to file = From noreply at ubuntu.com Tue Jul 13 21:37:09 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 13 Jul 2010 21:37:09 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_brad-figg?= Message-ID: <20100713213709.16323.43461@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 brad-figg: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=158&rev2=159 ------------------------------------------------------------------------------ == Kernel Specific == + For Kernel specific tags please check [[Kernel/Tagging|Kernel Tagging]] with all the official kernel tags. - || '''Tag''' || '''Use case''' || - || [[https://launchpad.net/ubuntu/+bugs?field.searchtext=linux&field.tag=bitesize|`bitesize` ]] || With regards to the kernel, this includes things like enabling modules and changing kernel config options || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=cherry-pick|`cherry-pick`]] || A kernel bug that has a git commit SHA from the upstream kernel || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-bug|`kernel-bug`]] || A "BUG:" message output was noted in the logs but it did not contain an Oops || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-oops|`kernel-oops`]] || This bug causes a kernel Oops message || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-kerneloops|`apport-kerneloops`]] || This Kernel Oops was reported using apport. || - || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=suspend+resume|`suspend resume`]] || This bug was triggered by a suspend/resume failure || - || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=hibernate+resume|`hibernate resume`]] || This bug was triggered by a hibernate/resume failure || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=xorg-needs-kernel-fix|`xorg-needs-kernel-fix`]] || This is an xorg bug which is dependent on a kernel patch || - || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-testing|`needs-upstream-testing`]] || This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds || == SRU Specific == From noreply at ubuntu.com Tue Jul 13 20:35:26 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 13 Jul 2010 20:35:26 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingOpenldap=22_by_hggdh2?= Message-ID: <20100713203526.854.93614@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/DebuggingOpenldap?action=diff&rev1=9&rev2=10 ------------------------------------------------------------------------------ Bugs relating to openldap typically fall into 1 category: 1. SSL connections not working (it is most probably a good idea to read the OpenLDAP FAQ about [[http://www.openldap.org/faq/data/cache/185.html|using TLS/SSL]]). + A good reference for common errors is [[http://www.openldap.org/faq/data/cache/53.html|here]]. = How to file = ## Useful for bug-filers and as a boiler-plate advice for triagers. This is the minimum information required for a bug report. From noreply at ubuntu.com Tue Jul 13 21:11:37 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 13 Jul 2010 21:11:37 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_hggdh2?= Message-ID: <20100713211137.8507.60042@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/Tags?action=diff&rev1=157&rev2=158 The comment on the change is: adding work-intensive tag for triaging (on request from the server team, but generic) ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tag=indicator-application|`indicator-application`]] || Bugs that are related to [[ https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationIndicators | application indicators ]] in Lucid || || [[https://launchpad.net/ubuntu/+bugs?field.tag=units-policy|`units-policy`]] || A bug that violates the UnitsPolicy || || [[https://launchpad.net/ubuntu/+bugs?field.tag=touch|`touch`]] || an issue with touch support in applications or X || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=work-intensive|`work-intensive`]] || triaging requires intensive work to validate/reproduce || == Ayatana == Specific bugs concerning parts of the [[https://launchpad.net/ayatana|Ayatana project]]. From noreply at ubuntu.com Tue Jul 13 21:40:07 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 13 Jul 2010 21:40:07 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_brad-figg?= Message-ID: <20100713214007.16233.61328@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 brad-figg: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=159&rev2=160 ------------------------------------------------------------------------------ == Kernel Specific == - For Kernel specific tags please check [[Kernel/Tagging|Kernel Tagging]] with all the official kernel tags. + || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.searchtext=linux&field.tag=bitesize|`bitesize` ]] || With regards to the kernel, this includes things like enabling modules and changing kernel config options || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=cherry-pick|`cherry-pick`]] || A kernel bug that has a git commit SHA from the upstream kernel || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-bug|`kernel-bug`]] || A "BUG:" message output was noted in the logs but it did not contain an Oops || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=kernel-oops|`kernel-oops`]] || This bug causes a kernel Oops message || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=apport-kerneloops|`apport-kerneloops`]] || This Kernel Oops was reported using apport. || + || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=suspend+resume|`suspend resume`]] || This bug was triggered by a suspend/resume failure || + || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=hibernate+resume|`hibernate resume`]] || This bug was triggered by a hibernate/resume failure || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=xorg-needs-kernel-fix|`xorg-needs-kernel-fix`]] || This is an xorg bug which is dependent on a kernel patch || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-testing|`needs-upstream-testing`]] || This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds || == SRU Specific == From noreply at ubuntu.com Wed Jul 14 06:26:58 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 14 Jul 2010 06:26:58 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100714062658.25083.45205@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 simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=12&rev2=13 ------------------------------------------------------------------------------ <> - == In case your touchpad doesn't work at all == + == In case your touchpad doesn't work at all (No response from the touchpad) == 1. File the bug against '''linux''' 1. Provide the [[#generalinfo|general information]]. From noreply at ubuntu.com Wed Jul 14 13:38:42 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 14 Jul 2010 13:38:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_trothigar?= Message-ID: <20100714133842.32389.85189@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 trothigar: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=296&rev2=297 ------------------------------------------------------------------------------ If you have already pointed out that the reported bug is an upstream one, but there hasn't been any feedback about the requested upstream bug for 2 weeks, the reporter (or someone else affected by the bug) might have forgotten it. If that's the case, you should ask if someone has already forwarded the bug upstream and can tell you the number of the upstream bug: - || Are there any news about this bug? Has someone affected by this bug sent the report upstream? May you tell us the bug number? Thanks in advance. || + || Is there any news about this bug? Has someone affected by this bug sent the report upstream? May you tell us the bug number? Thanks in advance. || However, if you have already sent the bug upstream, you should leave a comment stating where the upstream bug can be found: From bnicolotti at siapcn.it Wed Jul 14 12:15:28 2010 From: bnicolotti at siapcn.it (Bartolomeo Nicolotti) Date: Wed, 14 Jul 2010 14:15:28 +0200 Subject: bug-reporter crashed Message-ID: <1279109728.6406.21.camel@LxPC37> Hello, I was trying to report this bug, but bug-reporter crashed, please see attachment, ... I'm using evolution as mail client at work. The problem is that the mails I send are not visible on some outlook or send it in loop, or sometimes the attachment is not downloadable, but... The mail server we use is Zimbra, that has a web-mail, so I use it to send mails to someone i know as a wonderful outlook, but... If I've written something in evolution and then I try to copy-past the body from evolution to the zimbra compose form in firefox, I cannot, but if I open gedit, then I paste to gedit then select, then copy then paste to zimbra composer it works! wonderful how simple is to send a mail from ubuntu to windows (this is probably due to a but in outlook, of course...)! Ubuntu 8.04 (I haven't had time/courage to upgrade to 10.4 LTS) Evolution 2.22.3.1 Zimbra ? the attached e-mail outlook.txt is not seenable on Outlook version 6.0.0.29 many thanks! bye -------------- next part -------------- A non-text attachment was scrubbed... Name: SchermataBugReport.png Type: image/png Size: 169513 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: outlook.txt Type: application/mbox Size: 108059 bytes Desc: not available URL: From pedro at ubuntu.com Wed Jul 14 19:19:48 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Wed, 14 Jul 2010 15:19:48 -0400 Subject: Latest Updates from Mentors Message-ID: <1279135188.2082.35.camel@wombat> Hello folks, At our last BugSquad meeting we asked for Mentors updates to see how their students are doing it, the updates we got during the meeting: om26er: His student is working on Empathy bugs since om26er adopted that package, he said the student is a learner and get things done in no time. qense: The student was focusing on the Synaptics input driver, but he felt a bit lonely there. There weren't much people working on those kind of drivers. He's a quick learner as well. hggdh: Didn't heard from his student since 3 weeks, the student was unassigned and he's looking for another one. pedro: Currently working with elopio and njin, the first one is focusing on gwibber, gnome-media and working on bugs without a package. njin just started with the program a day ago and he's working on bugs without a package. We encourage all the mentors on the list that are currently working with a student to send a short update to know what's going on on their side, please reply to this email mentors ;-). If you're looking for a new student to mentor please have a look to: https://wiki.ubuntu.com/BugSquad/Mentors/Students And let us know which student you'd like to help. Looking forward to read your updates ;-) Have a nice day, pedro. From txwikinger at ubuntu.com Thu Jul 15 05:26:10 2010 From: txwikinger at ubuntu.com (Ralph Janke) Date: Thu, 15 Jul 2010 01:26:10 -0400 Subject: Latest Updates from Mentors In-Reply-To: <1279135188.2082.35.camel@wombat> References: <1279135188.2082.35.camel@wombat> Message-ID: <201007150126.11542.txwikinger@ubuntu.com> Where should we send those updates? On July 14, 2010 03:19:48 pm Pedro Villavicencio Garrido wrote: > Hello folks, > > At our last BugSquad meeting we asked for Mentors updates to see how > their students are doing it, the updates we got during the meeting: > > om26er: His student is working on Empathy bugs since om26er adopted that > package, he said the student is a learner and get things done in no > time. > > qense: The student was focusing on the Synaptics input driver, but he > felt a bit lonely there. There weren't much people working on those kind > of drivers. He's a quick learner as well. > > hggdh: Didn't heard from his student since 3 weeks, the student was > unassigned and he's looking for another one. > > pedro: Currently working with elopio and njin, the first one is focusing > on gwibber, gnome-media and working on bugs without a package. njin just > started with the program a day ago and he's working on bugs without a > package. > > We encourage all the mentors on the list that are currently working with > a student to send a short update to know what's going on on their side, > please reply to this email mentors ;-). > > If you're looking for a new student to mentor please have a look to: > > https://wiki.ubuntu.com/BugSquad/Mentors/Students > > And let us know which student you'd like to help. > > Looking forward to read your updates ;-) > > Have a nice day, > > pedro. From ddecator at gmail.com Thu Jul 15 06:27:57 2010 From: ddecator at gmail.com (Draycen DeCator) Date: Thu, 15 Jul 2010 02:27:57 -0400 Subject: [Ubuntu-bugcontrol] Latest Updates from Mentors In-Reply-To: <1279135188.2082.35.camel@wombat> References: <1279135188.2082.35.camel@wombat> Message-ID: Sorry I missed the meeting, something unexpected came up and I'm not sure how much I'll be on during the next week and a half. My first student is drew212, who has done a lot of work with Firefox bugs and is interested in potentially working on the kernel later. He has made a lot of progress and shows a lot of initiative. Drew will be ready for BC soon. My second student is trinikrono, who has worked a lot on bug days and older bugs. He has done a lot of good work with smaller packages and also shows a lot of enthusiasm. Kurt is always willing to learn, and is definitely on the right path for BC membership. Hope this is what you were looking for, Dray [ddecator] On Wed, Jul 14, 2010 at 3:19 PM, Pedro Villavicencio Garrido < pedro at ubuntu.com> wrote: > Hello folks, > > At our last BugSquad meeting we asked for Mentors updates to see how > their students are doing it, the updates we got during the meeting: > > om26er: His student is working on Empathy bugs since om26er adopted that > package, he said the student is a learner and get things done in no > time. > > qense: The student was focusing on the Synaptics input driver, but he > felt a bit lonely there. There weren't much people working on those kind > of drivers. He's a quick learner as well. > > hggdh: Didn't heard from his student since 3 weeks, the student was > unassigned and he's looking for another one. > > pedro: Currently working with elopio and njin, the first one is focusing > on gwibber, gnome-media and working on bugs without a package. njin just > started with the program a day ago and he's working on bugs without a > package. > > We encourage all the mentors on the list that are currently working with > a student to send a short update to know what's going on on their side, > please reply to this email mentors ;-). > > If you're looking for a new student to mentor please have a look to: > > https://wiki.ubuntu.com/BugSquad/Mentors/Students > > And let us know which student you'd like to help. > > Looking forward to read your updates ;-) > > Have a nice day, > > pedro. > > > _______________________________________________ > 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 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vish at ubuntu.com Thu Jul 15 08:20:28 2010 From: vish at ubuntu.com (Vishnoo) Date: Thu, 15 Jul 2010 13:50:28 +0530 Subject: Latest Updates from Mentors In-Reply-To: <201007150126.11542.txwikinger@ubuntu.com> References: <1279135188.2082.35.camel@wombat> <201007150126.11542.txwikinger@ubuntu.com> Message-ID: <1279182028.14812.50.camel@vish-laptop> On Thu, 2010-07-15 at 01:26 -0400, Ralph Janke wrote: > Where should we send those updates? You can just reply to the list here, preferably , so all can follow progress unless it needs to be private reply If you prefer you can send private reply to any of the Admins: https://wiki.ubuntu.com/BugSquad/Mentors/AdminList There are a few students *eagerly* waiting and we need to sort out the inactive students first, before assigning them mentors. So , mentors kindly reply soon. -- Cheers, Vish From txwikinger at ubuntu.com Thu Jul 15 13:36:39 2010 From: txwikinger at ubuntu.com (Ralph Janke) Date: Thu, 15 Jul 2010 09:36:39 -0400 Subject: Latest Updates from Mentors In-Reply-To: <1279182028.14812.50.camel@vish-laptop> References: <1279135188.2082.35.camel@wombat> <201007150126.11542.txwikinger@ubuntu.com> <1279182028.14812.50.camel@vish-laptop> Message-ID: <4C3F0EE7.2030002@ubuntu.com> My student (genux) has contacted me last week via IRC. I asked him to look at some bugs that he is interested in that we can go through them, and I am waiting for him to contact me with it again. txwikinger On 07/15/2010 04:20 AM, Vishnoo wrote: > On Thu, 2010-07-15 at 01:26 -0400, Ralph Janke wrote: > >> Where should we send those updates? >> > You can just reply to the list here, preferably , so all can follow > progress unless it needs to be private reply > If you prefer you can send private reply to any of the Admins: > https://wiki.ubuntu.com/BugSquad/Mentors/AdminList > > There are a few students *eagerly* waiting and we need to sort out the > inactive students first, before assigning them mentors. > So , mentors kindly reply soon. > > From hggdh2 at ubuntu.com Thu Jul 15 15:36:56 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 15 Jul 2010 10:36:56 -0500 Subject: bug-reporter crashed In-Reply-To: <1279109728.6406.21.camel@LxPC37> References: <1279109728.6406.21.camel@LxPC37> Message-ID: <20100715103656.4e60f9db@xango2> On Wed, 14 Jul 2010 14:15:28 +0200 Bartolomeo Nicolotti wrote: > Hello, Ciao Bartolomeo, > I was trying to report this bug, but bug-reporter crashed, please see > attachment, ... A quick note here: error 110 -- "connessione scaduta", "connection timed out" -- it sounds like there is a firewall blocking your access to the apport servers. It is not a crash on bug-reporter, but most probably your network setup. Unfortunately, I have no experience with Zimbra, or interfacing with Windows servers for email, so I cannot help you on this part. Cheers, -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From noreply at ubuntu.com Thu Jul 15 14:47:16 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 15 Jul 2010 14:47:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_pvillavi?= Message-ID: <20100715144716.29729.12090@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=232&rev2=233 ------------------------------------------------------------------------------ || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20100715| Pidgin]] || hugday-20100715 || || [[UbuntuBugDay/20100701| bugs without a package]] || hugday-20100708 || || [[UbuntuBugDay/20100701| Xkeyboard-config]] || hugday-20100701 || || [[UbuntuBugDay/20100624| Fontconfig]] || hugday-20100624 || From bnicolotti at siapcn.it Thu Jul 15 16:52:47 2010 From: bnicolotti at siapcn.it (Bartolomeo Nicolotti) Date: Thu, 15 Jul 2010 18:52:47 +0200 Subject: bug-reporter crashed In-Reply-To: <20100715103656.4e60f9db@xango2> References: <1279109728.6406.21.camel@LxPC37> <20100715103656.4e60f9db@xango2> Message-ID: <1279212767.6453.24.camel@LxPC37> Hello, yes, I imagined that this was the problem, but between lines I'm saying that i've NOT been able to report a problem probably due to a firewall that's not under my control and so now I've to ask to one collegue. Wouldn't it be simple to have a plain web page in which one can report bugs? Many thanks best regards. bartolomeo Il giorno gio, 15/07/2010 alle 10.36 -0500, C de-Avillez ha scritto: > On Wed, 14 Jul 2010 14:15:28 +0200 > Bartolomeo Nicolotti wrote: > > > Hello, > > > Ciao Bartolomeo, > > > I was trying to report this bug, but bug-reporter crashed, please see > > attachment, ... > > A quick note here: error 110 -- "connessione scaduta", "connection > timed out" -- it sounds like there is a firewall blocking your access > to the apport servers. It is not a crash on bug-reporter, but most > probably your network setup. > > Unfortunately, I have no experience with Zimbra, or interfacing with > Windows servers for email, so I cannot help you on this part. > > Cheers, -- ____________________________________________________________ Bartolomeo Nicolotti - Reparto Sviluppo - SIAP s.r.l. Via Sant'Albano, 13 - 12049 Trinità (CN) Italy Tel. (+39) 0172 652511 - Fax (+39) 0172 652519 E-mail: bnicolotti at siapcn.it - URL: www.siapcn.it Codice Fiscale, Partita IVA, Iscr. Reg. Imprese di Cuneo: 01871320048 Capitale Sociale: € 99.000,00 i.v. - R.E.A. CN 141311 ____________________________________________________________ Le informazioni contenute nella presente comunicazione e i relativi allegati possono essere riservate e sono, comunque, destinate esclusivamente alle persone o alla Società sopraindicati. La comunicazione, diffusione, distribuzione e/o copiatura del documento trasmesso nonché qualsiasi forma di trattamento dei dati ivi contenuti da parte di qualsiasi soggetto diverso dal destinatario è proibita, sia ai sensi dell'art. 616 c.p., che ai sensi del D. Lgs. n. 196/2003, ed in ogni caso espressamente inibita. Se avete ricevuto questo messaggio per errore, vi preghiamo di distruggerlo e di informarci immediatamente per telefono allo 0172/652511 o inviando un messaggio all'indirizzo: info at siapcn.it ____________________________________________________________ This electronic mail transmission, including any accompanying documents or attachments, may contain information that is confidential, privileged, proprietary, or otherwise legally exempt from disclosure and it's intended solely for the addressee(s). Access to this Internet electronic mail message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this electronic mail erroneously, we ask you to to destroy it and let us know immediately by phone at 0172/652511 or by sending an e-mail at info at siapcn.it ____________________________________________________________ From hggdh2 at ubuntu.com Thu Jul 15 17:48:01 2010 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Thu, 15 Jul 2010 12:48:01 -0500 Subject: bug-reporter crashed In-Reply-To: <1279212767.6453.24.camel@LxPC37> References: <1279109728.6406.21.camel@LxPC37> <20100715103656.4e60f9db@xango2> <1279212767.6453.24.camel@LxPC37> Message-ID: <20100715124801.1e73e1a6@xango2> On Thu, 15 Jul 2010 18:52:47 +0200 Bartolomeo Nicolotti wrote: > Hello, > > yes, I imagined that this was the problem, but between lines I'm > saying that i've NOT been able to report a problem probably due to a > firewall that's not under my control and so now I've to ask to one > collegue. > > Wouldn't it be simple to have a plain web page in which one can report > bugs? It might be simpler, but did not work out as well. But you can do it, even now -- Please look at the "Filing bugs at Launchpad.net" entry on https://help.ubuntu.com/community/ReportingBugs. We do not like it because a good number of the bugs reported directly misses a *LOT* of important data (*), so we made direct reporting a bit more involved to get to. Cheers, (*) things like package affected, version of same, Ubuntu version, logs, backtraces, etc; a lot of times an useful description of the issue is also missing ("xyz is not working. Please fix"). -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From nigelbabu at ubuntu.com Fri Jul 16 04:08:04 2010 From: nigelbabu at ubuntu.com (Nigel Babu) Date: Fri, 16 Jul 2010 09:38:04 +0530 Subject: How to work with Debian BTS In-Reply-To: References: Message-ID: Hello folks: If you've been following the UDW, you'll see that Pedro had talked about forwarding bugs upstream on bugzilla based bug trackers using the specific example of Gnome bugzilla.  This Thursday at 1800 UTC, Rhonda, a long time DD and recent MOTU will talk about the Debian BTS.  Please join us in #ubuntu-classroom for the session. Warm Regards Nigel Babu From bnicolotti at siapcn.it Fri Jul 16 06:50:36 2010 From: bnicolotti at siapcn.it (Bartolomeo Nicolotti) Date: Fri, 16 Jul 2010 08:50:36 +0200 Subject: bug-reporter crashed In-Reply-To: <20100715124801.1e73e1a6@xango2> References: <1279109728.6406.21.camel@LxPC37> <20100715103656.4e60f9db@xango2> <1279212767.6453.24.camel@LxPC37> <20100715124801.1e73e1a6@xango2> Message-ID: <1279263036.6404.5.camel@LxPC37> Hello, yes, I know that this kind of information is important, but it's more important in my opinion to have the best feed-back from users, a geek user will report every details, dummy users at least they're not able to do something, but also this information is very important, as for 1 geek there're 10 normal users and 100 dummies... By the waym, another example, yesterday gedit launched by a shell script we use to examine logs crashed, then it was impossible to open a new one or even to use the 0/1 red button to switch off, so i've had to ctrl+alt +f1, login as root in tty1 and reboot, probably a bug in gnome, how can I report that? What would have reported a dummy user? Many thanks bye Il giorno gio, 15/07/2010 alle 12.48 -0500, C de-Avillez ha scritto: > On Thu, 15 Jul 2010 18:52:47 +0200 > Bartolomeo Nicolotti wrote: > > > Hello, > > > > yes, I imagined that this was the problem, but between lines I'm > > saying that i've NOT been able to report a problem probably due to a > > firewall that's not under my control and so now I've to ask to one > > collegue. > > > > Wouldn't it be simple to have a plain web page in which one can report > > bugs? > > It might be simpler, but did not work out as well. > > But you can do it, even now -- Please look at the "Filing bugs at > Launchpad.net" entry on https://help.ubuntu.com/community/ReportingBugs. > > We do not like it because a good number of the bugs reported directly > misses a *LOT* of important data (*), so we made direct reporting a bit > more involved to get to. > > Cheers, > > > (*) things like package affected, version of same, Ubuntu version, logs, > backtraces, etc; a lot of times an useful description of the issue is > also missing ("xyz is not working. Please fix"). From pedro at ubuntu.com Mon Jul 19 08:48:29 2010 From: pedro at ubuntu.com (Pedro Villavicencio Garrido) Date: Mon, 19 Jul 2010 10:48:29 +0200 Subject: Call for BugSquad Video topics! Message-ID: <1279529309.2166.8.camel@thylacine> Hello Folks, During the last UDS we discussed about having Videos that might help new triagers to understand a bit better our processes and we also review this topic during our last BugSquad Monthly Meeting, so in order to record those videos we need topics! so if you have something in mind please add those ideas to https://wiki.ubuntu.com/BugSquad/ProposedVideos so we can later decide based on that list which ones are we are going to record. If you're also willing to help to record the videos please add your name to the Volunteer column. Have a great day, pedro. From jeremy.foshee at canonical.com Mon Jul 19 10:37:43 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Mon, 19 Jul 2010 06:37:43 -0400 Subject: Why don't we ask for kern.log? In-Reply-To: <20100709203725.GL13668@murraytwins.com> References: <20100709203725.GL13668@murraytwins.com> Message-ID: <20100719103743.GA1627@yoshimitsu> On Fri, Jul 09, 2010 at 01:37:25PM -0700, Brian Murray wrote: > On Fri, Jun 25, 2010 at 10:27:48PM -0400, Steven wrote: > > Hi, I was curious why I haven't seen anyone ask for kern.log, especially for > > kernel or graphics bugs. Is there sensitive information in there? Is the > > computer name too private? > > > > It seems much easier to ask for kern.log than dmesg, since: > > 1) If the system freezes and you have to reboot, dmesg and /var/log/dmesg > > aren't relevant anymore, so uploading kern.log guarantees you have the > > correct dmesg for the bug. > > 2) The timestamps make it very easy to pinpoint where the error should be > > and lessen the chance to misinterpret irrelevant messages as messages that > > are related to the bug. > > This is a great question and hopefully Jeremy, who I am cc'ing, can shed > some light on it. > So, I took some time to talk to the team face-to-face on this. Apologies for the delay that caused. :) The long answer is that we generally get what we need from dmesg. Even given your argument that kern.log is persistent when the system crashes, the consensus is that we would not really get anything useful from kern.log in those cases. As to the timestamps, we ask that the collection occur at the time of the error in most cases. This allows us to have the current information in a much smaller log to review. At some point in the recent past, the logging that we requested was discussed and the most useful logs were selected for inclusion in bugs for the apport-collect command to gather. We periodically review this listing, much like we have just done as a result of this query :). I hope this information is useful. I've written this rather quickly, so please feel free to let me know if it isn't making sense somewhere. :-) ~JFo > -- > Brian Murray > Ubuntu Bug Master From thekorn at gmx.de Mon Jul 19 10:38:05 2010 From: thekorn at gmx.de (markus korn) Date: Mon, 19 Jul 2010 12:38:05 +0200 Subject: Latest Updates from Mentors In-Reply-To: <1279135188.2082.35.camel@wombat> References: <1279135188.2082.35.camel@wombat> Message-ID: Hi there, here is my report for my two students: forsakenpariah (forsaken_pariah) ************************************* After some initial conversations about bugtriaging in ubuntu we agreed to take a small break until (at least) end of this month, because of some lack of time he is having right now. Zachary Richey (mach1723) ******************************** He did not answer to my initial mail, and to two other mails. And I also was not able to get in contact with him via launchpad or irc. So I think it is safe to drop this student, and if he returns at some point, we could always try to find a free slot for him. So given the fact that vish convinced me to take two students, I think I'm free for another one. Have a nice day, and sorry for being a bit late with this report. Markus From jesusguy50 at gmail.com Mon Jul 19 14:24:14 2010 From: jesusguy50 at gmail.com (Todd Davenport) Date: Mon, 19 Jul 2010 10:24:14 -0400 Subject: No subject Message-ID: I would a mentor to help me. But I need to set up a Ubuntu Wiki-page, how would I go about doing that. Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: From mstngdrew212 at gmail.com Mon Jul 19 16:04:17 2010 From: mstngdrew212 at gmail.com (Drew Cross) Date: Mon, 19 Jul 2010 11:04:17 -0500 Subject: No subject In-Reply-To: References: Message-ID: <4C447781.4010407@gmail.com> On 07/19/2010 09:24 AM, Todd Davenport wrote: > I would a mentor to help me. But I need to set up a Ubuntu Wiki-page, > how would I go about doing that. Thanks You can do this by going to https://wiki.ubuntu.com/FindPage and going to to the box that says "Or you can go directly to a page, or create a new page by entering its name here:" Then you can type in http://wiki.ubuntu.com/[add name here] and add your name, or whatever you want your page to be called, usually your name is easiest. -- Drew Cross UIN 678073908 CS Major, Photographer, IT Specialist, Linux Distributor, Linux Debugger, Hardware Tech. From roopesh.majeti at gmail.com Mon Jul 19 16:10:59 2010 From: roopesh.majeti at gmail.com (Roopesh Majeti) Date: Mon, 19 Jul 2010 21:40:59 +0530 Subject: Looking for a Mentor Message-ID: Hi, Iam new to ubuntu bug-squad.Got registered successfully for the membership as well. I went through the documentation given. Currently looking for a mentor, so that I can clarify my bunch of doubts as well as, get the direction/guidelines for my contribution. launghpad link : https://launchpad.net/~roopesh-majeti Looking forward, for the same. Regards Roopesh M. [ irc : stanley_robertso ]. -------------- next part -------------- An HTML attachment was scrubbed... URL: From phillw at phillw.net Mon Jul 19 17:59:25 2010 From: phillw at phillw.net (Phillip Whiteside) Date: Mon, 19 Jul 2010 18:59:25 +0100 Subject: No subject In-Reply-To: References: Message-ID: Hi Todd, If you're new to wiki pages, then I'd suggest having a look over on https://wiki.ubuntu.com/BeginnersTeam/Structure Part way down, you will find details of creating your wiki page. If you have any questions please feel to ask on #ubuntu-beginners or for wiki specific things #ubuntu-beginners-wiki They will be more than happy to help, (I'm usually on both those channels as well). Else, I will happily create you a template for you to fill all the details in. Regards, Phill. https://wiki.ubuntu.com/phillw On Mon, Jul 19, 2010 at 3:24 PM, Todd Davenport wrote: > I would a mentor to help me. But I need to set up a Ubuntu Wiki-page, how > would I go about doing that. Thanks > > -- > 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 stenten at gmail.com Tue Jul 20 04:29:16 2010 From: stenten at gmail.com (Steven) Date: Tue, 20 Jul 2010 00:29:16 -0400 Subject: Why don't we ask for kern.log? In-Reply-To: <20100719103743.GA1627@yoshimitsu> References: <20100709203725.GL13668@murraytwins.com> <20100719103743.GA1627@yoshimitsu> Message-ID: Thanks JFo, great response as always :) My main question was whether there was a specific reason for me *not* to ask for kern.log, such as personal info or other rules it would break or problems it would cause. Good to know that's not the case. I work triaging xserver-xorg-video-intel bugs, so when X freezes, you usually can't switch to another VT, so the only way to get dmesg is to ask the reporter to SSH in, which requires another computer and a good deal of technical know-how. Thus I find it easier to just ask for kern.log after they recover. Technically I guess I could ask for dmesg.0 instead, but drm.debug makes this so verbose that it fills the buffer too quickly and only contains the boot info, so we usually lose the dmesg for the actual error, since it usually occurs after the buffer's already filled up. So asking for kern.log is rather foolproof in these cases. Thanks again for the detailed response. -Steven On Mon, Jul 19, 2010 at 6:37 AM, Jeremy Foshee wrote: > On Fri, Jul 09, 2010 at 01:37:25PM -0700, Brian Murray wrote: > > On Fri, Jun 25, 2010 at 10:27:48PM -0400, Steven wrote: > > > Hi, I was curious why I haven't seen anyone ask for kern.log, > especially for > > > kernel or graphics bugs. Is there sensitive information in there? Is > the > > > computer name too private? > > > > > > It seems much easier to ask for kern.log than dmesg, since: > > > 1) If the system freezes and you have to reboot, dmesg and > /var/log/dmesg > > > aren't relevant anymore, so uploading kern.log guarantees you have the > > > correct dmesg for the bug. > > > 2) The timestamps make it very easy to pinpoint where the error should > be > > > and lessen the chance to misinterpret irrelevant messages as messages > that > > > are related to the bug. > > > > This is a great question and hopefully Jeremy, who I am cc'ing, can shed > > some light on it. > > > So, I took some time to talk to the team face-to-face on this. Apologies > for the delay that caused. :) > > The long answer is that we generally get what we need from dmesg. Even > given your argument that kern.log is persistent when the system crashes, > the consensus is that we would not really get anything useful from > kern.log in those cases. As to the timestamps, we ask that the > collection occur at the time of the error in most cases. This allows us > to have the current information in a much smaller log to review. > At some point in the recent past, the logging that we requested was > discussed and the most useful logs were selected > for inclusion in bugs for the apport-collect command to gather. We > periodically review this listing, much like we have just done as a > result of this query :). > > I hope this information is useful. I've written this rather quickly, so > please feel free to let me know if it isn't making sense somewhere. :-) > > ~JFo > > -- > > Brian Murray > > Ubuntu Bug Master > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From vish at ubuntu.com Tue Jul 20 07:37:06 2010 From: vish at ubuntu.com (Vishnoo) Date: Tue, 20 Jul 2010 13:07:06 +0530 Subject: Latest Updates from Mentors In-Reply-To: References: <1279135188.2082.35.camel@wombat> Message-ID: <1279611426.12396.11.camel@vish-laptop> On Mon, 2010-07-19 at 12:38 +0200, markus korn wrote: [...] > > Zachary Richey (mach1723) > ******************************** > He did not answer to my initial mail, and to two other mails. [...] Thanks for the update. Dropped your inactive student. And there is no one available in your time slot. So,you are free , for now ;) We still have 4 students waiting: https://wiki.ubuntu.com/BugSquad/Mentors/Students @ students who are waiting, once we have an update from mentors: Greg Grossmeier Maco Morgan Their students seem inactive too. Once we get the confirmation from them , you'll get a mentor assigned too. Thanks for your patience! -- Cheers, Vish From jeremy.foshee at canonical.com Tue Jul 20 10:27:33 2010 From: jeremy.foshee at canonical.com (Jeremy Foshee) Date: Tue, 20 Jul 2010 12:27:33 +0200 Subject: Why don't we ask for kern.log? In-Reply-To: References: <20100709203725.GL13668@murraytwins.com> <20100719103743.GA1627@yoshimitsu> Message-ID: <20100720102733.GA2173@yoshimitsu> On Tue, Jul 20, 2010 at 12:29:16AM -0400, Steven wrote: > Thanks JFo, great response as always :) > > My main question was whether there was a specific reason for me *not* to ask > for kern.log, such as personal info or other rules it would break or problems > it would cause. Good to know that's not the case. > > I work triaging xserver-xorg-video-intel bugs, so when X freezes, you usually > can't switch to another VT, so the only way to get dmesg is to ask the reporter > to SSH in, which requires another computer and a good deal of technical > know-how. Thus I find it easier to just ask for kern.log after they recover. > > Technically I guess I could ask for dmesg.0 instead, but drm.debug makes this > so verbose that it fills the buffer too quickly and only contains the boot > info, so we usually lose the dmesg for the actual error, since it usually > occurs after the buffer's already filled up. So asking for kern.log is rather > foolproof in these cases. > Actually, kern.log would be perfect in those situations, as you point out. The team agrees. This is oen of those use cases that wasn't thought of at the time. The consensus is, kern.log is perfect for your use case, but we probably won't add it to the apport log collection due to it being extra for most of the bugs that get filed. Hope that helps. :-) > Thanks again for the detailed response. My pleasure, as always. > > -Steven > ~JFo > > On Mon, Jul 19, 2010 at 6:37 AM, Jeremy Foshee > wrote: > > On Fri, Jul 09, 2010 at 01:37:25PM -0700, Brian Murray wrote: > > On Fri, Jun 25, 2010 at 10:27:48PM -0400, Steven wrote: > > > Hi, I was curious why I haven't seen anyone ask for kern.log, > especially for > > > kernel or graphics bugs. Is there sensitive information in there? Is > the > > > computer name too private? > > > > > > It seems much easier to ask for kern.log than dmesg, since: > > > 1) If the system freezes and you have to reboot, dmesg and /var/log/ > dmesg > > > aren't relevant anymore, so uploading kern.log guarantees you have the > > > correct dmesg for the bug. > > > 2) The timestamps make it very easy to pinpoint where the error should > be > > > and lessen the chance to misinterpret irrelevant messages as messages > that > > > are related to the bug. > > > > This is a great question and hopefully Jeremy, who I am cc'ing, can shed > > some light on it. > > > So, I took some time to talk to the team face-to-face on this. Apologies > for the delay that caused. :) > > The long answer is that we generally get what we need from dmesg. Even > given your argument that kern.log is persistent when the system crashes, > the consensus is that we would not really get anything useful from > kern.log in those cases. As to the timestamps, we ask that the > collection occur at the time of the error in most cases. This allows us > to have the current information in a much smaller log to review. > At some point in the recent past, the logging that we requested was > discussed and the most useful logs were selected > for inclusion in bugs for the apport-collect command to gather. We > periodically review this listing, much like we have just done as a > result of this query :). > > I hope this information is useful. I've written this rather quickly, so > please feel free to let me know if it isn't making sense somewhere. :-) > > ~JFo > > -- > > Brian Murray > > Ubuntu Bug Master > > > > From brian at canonical.com Tue Jul 20 13:17:24 2010 From: brian at canonical.com (Brian Murray) Date: Tue, 20 Jul 2010 06:17:24 -0700 Subject: Why don't we ask for kern.log? In-Reply-To: <20100720102733.GA2173@yoshimitsu> References: <20100709203725.GL13668@murraytwins.com> <20100719103743.GA1627@yoshimitsu> <20100720102733.GA2173@yoshimitsu> Message-ID: <20100720131724.GA18613@murraytwins.com> On Tue, Jul 20, 2010 at 12:27:33PM +0200, Jeremy Foshee wrote: > On Tue, Jul 20, 2010 at 12:29:16AM -0400, Steven wrote: > > Thanks JFo, great response as always :) > > > > My main question was whether there was a specific reason for me *not* to ask > > for kern.log, such as personal info or other rules it would break or problems > > it would cause. Good to know that's not the case. > > > > I work triaging xserver-xorg-video-intel bugs, so when X freezes, you usually > > can't switch to another VT, so the only way to get dmesg is to ask the reporter > > to SSH in, which requires another computer and a good deal of technical > > know-how. Thus I find it easier to just ask for kern.log after they recover. > > > > Technically I guess I could ask for dmesg.0 instead, but drm.debug makes this > > so verbose that it fills the buffer too quickly and only contains the boot > > info, so we usually lose the dmesg for the actual error, since it usually > > occurs after the buffer's already filled up. So asking for kern.log is rather > > foolproof in these cases. > > > Actually, kern.log would be perfect in those situations, as you point > out. The team agrees. This is oen of those use cases that wasn't thought > of at the time. The consensus is, kern.log is perfect for your use case, > but we probably won't add it to the apport log collection due to it > being extra for most of the bugs that get filed. However, perhaps kern.log should be added to the log files that X packages gather since it seems to be particularly useful there. -- 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 noreply at ubuntu.com Tue Jul 20 13:18:40 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 20 Jul 2010 13:18:40 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22simar/Touchpad=22_by_simar?= Message-ID: <20100720131840.19042.85516@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 simar: http://wiki.ubuntu.com/simar/Touchpad?action=diff&rev1=1&rev2=2 ------------------------------------------------------------------------------ This is in general a wrong detection by the kernel itself. So xserver-xorg-input-synaptics has nothing to do with it. In this case file a bug against the kernel('''linux''').Also note that you should not mark the bug as duplicate even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a new policy of Kernel Team and it help them to handle the bugs better. Include the outputs of the following commands: + - 1.cat /proc/bus/input/devices >~/devices + {{{cat /proc/bus/input/devices >~/devices - 2.sudo lspci -vvnn > ~/lspci + sudo lspci -vvnn > ~/lspci}}} - 3, + + 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 your are unsure file it against xserver-xorg-input-synaptics, somebody will change to kernel if is so. - == In case touchpad is detected correctly by the kernel but some features such as scrolling, additional buttons, dragging does not work. + == In case touchpad is detected correctly by the kernel but some features such as scrolling, additional buttons, dragging does not work.== === In case your all features work but does not work as expected === From greg at grossmeier.net Wed Jul 21 02:15:24 2010 From: greg at grossmeier.net (Greg Grossmeier) Date: Tue, 20 Jul 2010 22:15:24 -0400 Subject: Latest Updates from Mentors In-Reply-To: <1279135188.2082.35.camel@wombat> References: <1279135188.2082.35.camel@wombat> Message-ID: <20100721021524.GE15118@grossmeier.net> > Hello folks, > > At our last BugSquad meeting we asked for Mentors updates to see how > their students are doing it, the updates we got during the meeting: My Update is: * Worked with "flyin" on one or two bugs. Haven't had much contact since. * Have yet to contact Vork. That is my fault. * Realized my time for mentorship is not what it should be to do this effectively. I am sorry. * I will, of course, still lurk on the -bugs IRC channel and comment/help when I can, but the usual issues are pressing on my time (expanding job, evolution of home life time committments, etc). My apologies. Best, Greg -- | Greg Grossmeier | | http://grossmeier.net | From noreply at ubuntu.com Wed Jul 21 13:26:14 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 21 Jul 2010 13:26:14 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/Netconsole=22_by_jeremyfo?= =?utf-8?q?shee?= Message-ID: <20100721132614.12516.51339@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 jeremyfoshee: http://wiki.ubuntu.com/Kernel/Netconsole New page: <> <> = Introduction = Sometimes it's hard to capture a kernel panic: You don't know how to reproduce the kernel panic and/or once you have rebooted your system, there are no clues in the logfiles. This is where netconsole might help out. Netconsole is a ''kernel module that logs kernel printk messages over UDP allowing debugging of problems where disk logging fails''. This is just a techno-way of saying that the kernel messages will get send over the network in certain packets (UDP packets). There are a couple of disadvantages though: * Since netconsole needs to send it's UDP packets to some other host, you need to setup a "receiver" as well * Netconsole initializes when modules are loaded into the kernel. This doesn't allow capture of early kernel panics - for example when booting * The driver for the network card must support polling (netpoll api) * Only IP networks, UDP packets and ethernet devices are supported = Setup netconsole = This document will guide you through the steps to setup netconsole for Ubuntu {*}. There are 5 steps to set it all up! Good luck! :)) == Step 1: Determine remote mac address == We need to know a mac address where the UDP packets will get sent to (also known as the "receiver"). This "receiver" can or can't be in the same subnet: === When "receiver" is in same subnet === In this example I would like to send the UDP packets to 192.168.1.103 (which is in the same subnet as the sender is). {{{ pet at sender:~$ ping -c 1 192.168.1.103 > /dev/null pet at sender:~$ arp -n 192.168.1.103 Address HWtype HWaddress Flags Mask Iface 192.168.1.103 ether 08:00:46:d4:1d:82 C eth0 }}} In this example '''08:00:46:d4:1d:82''' is the mac address we need. === When "receiver" isn't in the same subnet === Okay, when that's the case, you need to determine the default gateway first: {{{ pet at sender:~$ netstat -rn | grep ^0.0.0.0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 }}} In this case, that's '''192.168.1.1'''. Now, we need to figure out which mac address our default gateway has: {{{ pet at sender:~$ ping -c 1 192.168.1.1 > /dev/null pet at sender:~$ arp -n 192.168.1.1 Address HWtype HWaddress Flags Mask Iface 192.168.1.1 ether 00:0f:66:5b:2a:3c C eth0 }}} In this example '''00:0f:66:5b:2a:3c''' is the mac address we need. == Step 2: Change kernel options at boot time == Okay, let's assume you use grub as your bootloader. In this case grub will boot the kernel with (at least) the "`quiet splash`" options by default. We don't want that. === Grub 0.97: if you are using Ubuntu 9.04 or older === Just to be sure, create a backup of `/boot/grub/menu.lst` first: {{{ pet at sender:~$ sudo cp /boot/grub/menu.lst /root/menu.lst.backup }}} Now, open your favorite editor to edit `/boot/grub/menu.lst`. * For vi: {{{ sudo vi /boot/grub/menu.lst }}} * For gedit (to edit this file within Gnome): {{{ gksudo gedit /boot/grub/menu.lst }}} Locate the line that starts with "`# defoptions=quiet splash`" (don't get mislead by the fact the line starts with a "#") and replace this line with "`# defoptions=debug ignore_loglevel`". Tell grub to update accordingly: {{{ pet at sender:~$ sudo update-grub }}} === Grub 2: if you are using Ubuntu 9.10 or newer === Just to be sure, create a backup of `/etc/default/grub` first: {{{ pet at sender:~$ sudo cp /etc/default/grub /etc/default/grub.backup }}} Now, open your favorite editor to edit `/etc/default/grub`. * For vi: {{{ sudo vi /etc/default/grub }}} * For gedit (to edit this file within Gnome): {{{ gksudo gedit /etc/default/grub }}} Locate the line `GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"` and replace this line with `GRUB_CMDLINE_LINUX_DEFAULT="debug ignore_loglevel"`. Tell grub to update accordingly: {{{ pet at sender:~$ sudo update-grub }}} == Step 3: Initialize netconsole at boot time == Okay, that went well. Three more steps to go! Now we need to know the: * ip address and interface of the "sender" (use the following commands to determine these) {{{ ifconfig -a }}} * ip address and mac address of the "receiver" (these were already gathered in [[#Step 1: Determine remote mac address]]) In the following example, the part that starts with "netconsole=" is setup like this: `netconsole=@/,@/` In this example, I use 6666 for both and . {{{ $ sudo sh -c 'echo netconsole >> /etc/modules' $ sudo sh -c 'echo options netconsole netconsole=6666 at 192.168.1.102/eth0,6666 at 192.168.1.103/08:00:46:d4:1d:82 > /etc/modprobe.d/netconsole.conf' }}} == Step 4: Setup receiver == There are several ways to retrieve the netconsole packets: === Syslog-ng (Linux) === Easiest way probably is to boot the receiver with an Ubuntu LiveCD. Setup networking and gain shell access. {{{ pet at receiver:~$ sudo apt-get install syslog-ng }}} Edit `/etc/syslog-ng/syslog-ng.conf` with your favorite editor and append these lines at the very end of the file: {{{ source net { udp(ip("0.0.0.0") port(6666)); }; destination netconsole { file("/var/log/$HOST-netconsole.log"); }; log { source(net); destination(netconsole); }; }}} Now restart syslog-ng: {{{ pet at receiver:~$ sudo /etc/init.d/syslog-ng restart }}} Continue with [[#Step 5: Check if it works]]. Once you are done, the logging will be in `/var/log/-netconsole.log`. === Netcat (Linux) === If you have the luxury of having a Linux machine as "receiver", you just might want to try this: In this example 192.168.1.103 is the same as "" (see [[#Step 3: Initialize netconsole at boot time]]) {{{ pet at receiver:~$ netcat -l -u 192.168.1.103 6666 | tee ~/netconsole.log }}} Just let it sit there. Continue with [[#Step 5: Check if it works]]. Once you are done, press "Control-C". The messages you want are in `~/netconsole.log`. If this doesn't work, also try without the IP address specifically listed: {{{ pet at receiver:~$ netcat -l -u 6666 | tee ~/netconsole.log }}} === Netcat (Linux, alternative) === Some versions of Linux, such as Ubuntu Hardy (8.04), use a different version of Netcat that uses a different syntax. If you use a Linux receiver that has a different version of Netcat, it will print the following error message when you try the commands above: {{{ UDP listen needs -p arg }}} In this case, you need to issue the following command: {{{ pet at receiver:~$ netcat -l -p 6666 -u | tee ~/netconsole.log }}} === Netcat (Mac OS-X) === Unsurprisingly, as OS-X is a BSD UNIX derivative, Netcat is available out of the box on this platform with the minor difference from Linux that the command is actually called `nc` rather than `netcat`. In this example 192.168.1.103 is the same as "" (see [[#Step 3: Initialize netconsole at boot time]]) {{{ receiver:~ pet$ nc -l -u 192.168.1.103 6666 | tee ~/netconsole.log }}} Just let it sit there. Continue with [[#Step 5: Check if it works]]. Once you are done, press "Control-C". The messages you want are in `~/netconsole.log`. If this doesn't work, also try without the IP address specifically listed: {{{ receiver:~ pet$ nc -l -u 6666 | tee ~/netconsole.log }}} === Netcat (Windows) === There's a netcat for Windows available [[http://joncraton.org/files/nc111nt.zip|here]] or [[http://www.vulnwatch.org/netcat/nc111nt.zip|here]]. Unpack it somewhere (i.e. `C:\Users\Pet\Desktop\nc\`) Open a dosprompt (Start -> Run -> cmd). In this example 192.168.1.103 is the same as . {{{ cd C:\Users\Pet\Desktop\nc\ nc -u -l -p 6666 192.168.1.103 > netconsole.txt }}} Just let it sit there. Continue with [[#Step 5: Check if it works]]. Once you are done, press "Control-C". The messages you want are in `netconsole.txt`. === Syslog (Windows) === There's an open source syslog tool [[http://tftpd32.jounin.net/tftpd32_download.html|here]]. In the version currently available (2009, Jan), there is no way to change the port syslog listens on. You'll have to change the to port 514 (which is the default syslog port). == Step 5: Check if it works == Reboot the "sender". Once rebooted execute the command below. {{{ $ dmesg | grep netcon [ 21.048406] netconsole: local port 6666 [ 21.048410] netconsole: local IP 192.168.1.102 [ 21.048411] netconsole: interface eth0 [ 21.048413] netconsole: remote port 6666 [ 21.048415] netconsole: remote IP 192.168.1.103 [ 21.048418] netconsole: remote ethernet address 08:00:46:d4:1d:82 [ 21.048421] netconsole: device eth0 not up yet, forcing it [ 22.908106] console [netcon0] enabled [ 22.911536] netconsole: network logging started }}} Seems to be working! {OK} Now check your "receiver" to see whether the kernel messages were received! If that's the case, continue to use the "sender" until it crashes, hopefully the "receiver" receives some useful information about the crash. You don't actually need to reboot the sender if you don't want to. You can manually load netconsole via: {{{ $ sudo modprobe netconsole netconsole=6666 at 192.168.1.102/eth0,6666 at 192.168.1.103/08:00:46:d4:1d:82 }}} One way to test whether logging is working correctly or not is to insert some removable media like a CD, DVD or usb stick. = Remove netconsole = Once you retrieved the information you needed, we need to clean things up again. == Revert Grub to its original configuration == === Grub 0.97: if you are using Ubuntu 9.04 or older === {{{ pet at sender:~$ sudo mv /root/menu.lst.backup /boot/grub/menu.lst pet at sender:~$ sudo update-grub }}} === Grub 2: if you are using Ubuntu 9.10 or newer === {{{ pet at sender:~$ sudo mv /etc/default/grub.backup /etc/default/grub pet at sender:~$ sudo update-grub }}} == Remove netconsole itself == {{{ pet at sender:~$ sudo sed -i '/^netconsole/d' /etc/modules pet at sender:~$ sudo rm -f /etc/modprobe.d/netconsole.conf }}} = Note from author = Do you have comments on the content above? Something incomplete or incorrect? Please don't hesitate to [[https://launchpad.net/~petski/+contactuser|drop me a few lines]]. I would like to say thanks to [[https://launchpad.net/~pveerman|Peter Veerman]] and [[https://launchpad.net/~leannogasawara|Leann Ogasawara]] for reviewing this document. A big thanks to [[https://launchpad.net/~brunogirin|Bruno Girin]] for adding the grub-2 instructions = See also = https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Problems%20in%20capturing%20information [[http://www.cyberciti.biz/tips/linux-netconsole-log-management-tutorial.html|Another netconsole tuturial]] [[http://www.cyberciti.biz/files/linux-kernel/Documentation/networking/netconsole.txt|Netconsole documentation]] [[http://www.novell.com/communities/node/4753/netconsole-howto-send-kernel-boot-messages-over-ethernet|Netconsole tutorial for SuSe]] ---- CategoryDebugging From noreply at ubuntu.com Thu Jul 22 10:21:01 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Thu, 22 Jul 2010 10:21:01 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_diwic?= Message-ID: <20100722102101.26723.38608@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 diwic: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=160&rev2=161 The comment on the change is: Added link to Kernel/Tagging ------------------------------------------------------------------------------ || [[https://launchpad.net/ubuntu/+bugs?field.tags_combinator=ALL&field.tag=hibernate+resume|`hibernate resume`]] || This bug was triggered by a hibernate/resume failure || || [[https://launchpad.net/ubuntu/+bugs?field.tag=xorg-needs-kernel-fix|`xorg-needs-kernel-fix`]] || This is an xorg bug which is dependent on a kernel patch || || [[https://launchpad.net/ubuntu/+bugs?field.tag=needs-upstream-testing|`needs-upstream-testing`]] || This bug needs to be tested with the upstream kernel - https://wiki.ubuntu.com/KernelMainlineBuilds || + + For more tags see [[Kernel/Tagging|Kernel/Tagging]]. == SRU Specific == From brian at ubuntu.com Thu Jul 22 21:42:38 2010 From: brian at ubuntu.com (Brian Murray) Date: Thu, 22 Jul 2010 14:42:38 -0700 Subject: [Ubuntu-bugcontrol] How to work with Debian BTS In-Reply-To: References: Message-ID: <20100722214238.GB21771@murraytwins.com> On Fri, Jul 16, 2010 at 09:38:04AM +0530, Nigel Babu wrote: > Hello folks: > > If you've been following the UDW, you'll see that Pedro had talked > about forwarding bugs upstream on bugzilla based bug trackers using > the specific example of Gnome bugzilla.  This Thursday at 1800 UTC, > Rhonda, a long time DD and recent MOTU will talk about the Debian BTS. >  Please join us in #ubuntu-classroom for the session. For anybody who missed this very useful class the log can be found at: http://irclogs.ubuntu.com/2010/07/22/%23ubuntu-classroom.html -- 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 phamngoctuuk at gmail.com Sat Jul 24 16:07:37 2010 From: phamngoctuuk at gmail.com (Tu Pham Ngoc) Date: Sat, 24 Jul 2010 23:07:37 +0700 Subject: Bug with Intel e1000e driver kernel module on new Intel Gigabit Ethernet Chipset Message-ID: Dear Ubuntu Bugs Squad team, I have installed Ubuntu Server 10.04 Lucid on a SuperMicro server using X8SIE motherboard. The integrated LAN solution use Intel® 82574L Gigabit Ethernet Controllers, the system automatically detect & install kernel module for this chipset. But the kernel module (e1000e) which is included with Lucid was a little bit outdated and it give me a lot of trouble on this system. When I started to install the system, the OS was very hard to get IP from DHCP server. After few tries and reset, I could install the system. It running for few days OK, but one time I found out that the interface was freeze, no traffic could go through it. Try to reset network stack, the interface could not get IP from DHCP, static IP also not work. I use ethtools to test it and it failed, both eth0 & eth1. Reset server (reboot) and eth0 disappeared, shutdown & turn it on again, eht0 continue to work. The kernel module included with Lucid is 1.02 as far as I could remember. I have loaded two version of e1000e kernel module source from sourceforge. One is 1.2.8 stable & one is 1.1.9 stable. The 1.2.8 give out some error when compiling, from my google result, it may due to it was written against the newer kernel version (2.6.34 or something like that). The 1.1.9 compiled without error. I did install & rebuild the initrd image. Restart for sometimes to test, and upto now my server has up for over 16 days without any eht0 error & it is in production now (as cache, database & webserver). Please check & fix the bug with this kernel module. I do hope this report would help people out there. What happened with me was a crazy head-ache as it very hard to conclude the error is a result of hardware failure or software (most people would think it is from hardware!) The newest CentOS system also faces the same issues. If it is possible please send my report to them. Thank you & hope it help, Tu Pham Ngoc -------------------------------- Skype: phamngoctuuk YM/MSN: phamngoctuuk at hotmail.com HP: +84 90 446 1132 -------------------------------- Anh Ngoc Co., Ltd. 56 Trung Hoa Street, Cau Giay District Hanoi, Vietnam www.anhngoc.vn -------------- next part -------------- An HTML attachment was scrubbed... URL: From cyan.spam at gmail.com Tue Jul 27 00:06:09 2010 From: cyan.spam at gmail.com (David Tombs) Date: Mon, 26 Jul 2010 20:06:09 -0400 Subject: Bug with Intel e1000e driver kernel module on new Intel Gigabit Ethernet Chipset In-Reply-To: References: Message-ID: <4C4E22F1.8070502@gmail.com> Hi there, Thank you for writing such a detailed report, but unfortunately this is not the place to /file/ bug reports, just to talk about handling them. Please file a report at the bug tracker, see the instructions at . Thanks! David On 07/24/2010 12:07 PM, Tu Pham Ngoc wrote: > Dear Ubuntu Bugs Squad team, > > I have installed Ubuntu Server 10.04 Lucid on a SuperMicro server using > X8SIE motherboard. The integrated LAN solution use Intel® 82574L Gigabit > Ethernet Controllers, the system automatically detect & install kernel > module for this chipset. But the kernel module (e1000e) which is > included with Lucid was a little bit outdated and it give me a lot of > trouble on this system. > > When I started to install the system, the OS was very hard to get IP > from DHCP server. After few tries and reset, I could install the system. > It running for few days OK, but one time I found out that the interface > was freeze, no traffic could go through it. Try to reset network stack, > the interface could not get IP from DHCP, static IP also not work. I use > ethtools to test it and it failed, both eth0 & eth1. Reset server > (reboot) and eth0 disappeared, shutdown & turn it on again, eht0 > continue to work. The kernel module included with Lucid is 1.02 as far > as I could remember. > > I have loaded two version of e1000e kernel module source from > sourceforge. One is 1.2.8 stable & one is 1.1.9 stable. The 1.2.8 give > out some error when compiling, from my google result, it may due to it > was written against the newer kernel version (2.6.34 or something like > that). The 1.1.9 compiled without error. I did install & rebuild the > initrd image. Restart for sometimes to test, and upto now my server has > up for over 16 days without any eht0 error & it is in production now (as > cache, database & webserver). > > Please check & fix the bug with this kernel module. I do hope this > report would help people out there. What happened with me was a crazy > head-ache as it very hard to conclude the error is a result of hardware > failure or software (most people would think it is from hardware!) > > The newest CentOS system also faces the same issues. If it is possible > please send my report to them. > > Thank you & hope it help, > Tu Pham Ngoc > -------------------------------- > Skype: phamngoctuuk > YM/MSN: phamngoctuuk at hotmail.com > HP: +84 90 446 1132 > -------------------------------- > Anh Ngoc Co., Ltd. > 56 Trung Hoa Street, Cau Giay District > Hanoi, Vietnam > www.anhngoc.vn > From brian at ubuntu.com Tue Jul 27 15:39:13 2010 From: brian at ubuntu.com (Brian Murray) Date: Tue, 27 Jul 2010 08:39:13 -0700 Subject: Bug with Intel e1000e driver kernel module on new Intel Gigabit Ethernet Chipset In-Reply-To: <4C4E22F1.8070502@gmail.com> References: <4C4E22F1.8070502@gmail.com> Message-ID: <20100727153913.GD20051@murraytwins.com> On Mon, Jul 26, 2010 at 08:06:09PM -0400, David Tombs wrote: > Hi there, > > Thank you for writing such a detailed report, but unfortunately this is > not the place to /file/ bug reports, just to talk about handling them. > > Please file a report at the bug tracker, see the instructions at > . The proper package for this bug is linux and it should be reported using 'ubuntu-bug linux' so we will have detailed information about your system and kernel. -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Tue Jul 27 17:00:55 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Tue, 27 Jul 2010 17:00:55 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKVM=22_by_mathiaz?= Message-ID: <20100727170055.5404.54733@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 mathiaz: http://wiki.ubuntu.com/DebuggingKVM?action=diff&rev1=6&rev2=7 ------------------------------------------------------------------------------ <> ||<>|| + + = Bug importance = + + * critical: eats your data + * high: crashes the host + * medium: crashes the guest (and most other "normal" bugs) + * low: doesn't crash host or guest, but has undesirable, clearly buggy behavior, or if it does cause crashes, can be worked around + * wishlist: feature requests, everything else lower priority = Debugging procedure = From phamngoctuuk at gmail.com Tue Jul 27 19:49:13 2010 From: phamngoctuuk at gmail.com (Tu Pham Ngoc) Date: Wed, 28 Jul 2010 02:49:13 +0700 Subject: Bug with Intel e1000e driver kernel module on new Intel Gigabit Ethernet Chipset In-Reply-To: <20100727153913.GD20051@murraytwins.com> References: <4C4E22F1.8070502@gmail.com> <20100727153913.GD20051@murraytwins.com> Message-ID: Installed apport & report sent. Hope it help. https://bugs.launchpad.net/ubuntu/+source/linux/+filebug/dd741030-99b6-11df-8a20-002481e7f48a Twelve hours ago I have tried to file a bug in launchpad but there is alway an error, it seems that the service is overload. Until now I also could not add more detail to the bug report in the link above (I try to add the tag name & more detail description like what I have written in previous email) Tu Pham Ngoc -------------------------------- Skype: phamngoctuuk YM/MSN: phamngoctuuk at hotmail.com HP: +84 90 446 1132 -------------------------------- Anh Ngoc Co., Ltd. 56 Trung Hoa Street, Cau Giay District Hanoi, Vietnam www.anhngoc.vn On Tue, Jul 27, 2010 at 10:39 PM, Brian Murray wrote: > On Mon, Jul 26, 2010 at 08:06:09PM -0400, David Tombs wrote: > > Hi there, > > > > Thank you for writing such a detailed report, but unfortunately this is > > not the place to /file/ bug reports, just to talk about handling them. > > > > Please file a report at the bug tracker, see the instructions at > > . > > The proper package for this bug is linux and it should be reported using > 'ubuntu-bug linux' so we will have detailed information about your > system and kernel. > > -- > Brian Murray > Ubuntu Bug Master > > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkxO/aAACgkQDTAwc5ER+zW+ggCeNIApH9ZEVteXT/XWy5zpEQcs > +lcAoOtm4kvxvfxBHNuW5rQGCQ5AIo/A > =yAZP > -----END PGP SIGNATURE----- > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Wed Jul 28 21:55:46 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Wed, 28 Jul 2010 21:55:46 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/MarkingDuplicate=22_by_hggd?= =?utf-8?q?h2?= Message-ID: <20100728215546.6524.77969@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/MarkingDuplicate?action=diff&rev1=23&rev2=24 The comment on the change is: Added link to kernel policy (no duplicates) ------------------------------------------------------------------------------ When you first look at a new bug, try to find an existing bug in the system that describes the new one. Here's how: + /!\ Kernel Team policy requires that only a kernel maintainer can set a kernel bug as a duplicate of another bug. See the [[ Kernel/Policies/DuplicateBugs|kernel policy ]] for details. * Click the "List open bugs" link at the bottom of the bug page '''or''' * Click the "Bugs" tab at the top of the page * Both ways will produce a list of bugs about the same package From brian at ubuntu.com Wed Jul 28 22:21:05 2010 From: brian at ubuntu.com (Brian Murray) Date: Wed, 28 Jul 2010 15:21:05 -0700 Subject: [Ubuntu Wiki] Update of "Bugs/MarkingDuplicate" by hggdh2 In-Reply-To: <20100728215546.6524.77969@jostaberry.canonical.com> References: <20100728215546.6524.77969@jostaberry.canonical.com> Message-ID: <20100728222105.GQ20051@murraytwins.com> On Wed, Jul 28, 2010 at 09:55:46PM -0000, Ubuntu Wiki wrote: > 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/MarkingDuplicate?action=diff&rev1=23&rev2=24 > > The comment on the change is: > Added link to kernel policy (no duplicates) > > ------------------------------------------------------------------------------ > > When you first look at a new bug, try to find an existing bug in the system that describes the new one. Here's how: > > + /!\ Kernel Team policy requires that only a kernel maintainer can set a kernel bug as a duplicate of another bug. See the [[ Kernel/Policies/DuplicateBugs|kernel policy ]] for details. > * Click the "List open bugs" link at the bottom of the bug page '''or''' > * Click the "Bugs" tab at the top of the page > * Both ways will produce a list of bugs about the same package What is process for getting a "kernel maintainer" to look at bug that may possibly may a duplicate of another? -- 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 braiamp at gmail.com Fri Jul 30 08:10:40 2010 From: braiamp at gmail.com (Braiam Peguero) Date: Fri, 30 Jul 2010 04:10:40 -0400 Subject: [Ubuntu Wiki] Update of "Bugs/MarkingDuplicate" by hggdh2 In-Reply-To: <20100728222105.GQ20051@murraytwins.com> References: <20100728215546.6524.77969@jostaberry.canonical.com> <20100728222105.GQ20051@murraytwins.com> Message-ID: <4C528900.6020200@gmail.com> El 28/07/10 18:21, Brian Murray escribió: > On Wed, Jul 28, 2010 at 09:55:46PM -0000, Ubuntu Wiki wrote: > >> 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/MarkingDuplicate?action=diff&rev1=23&rev2=24 >> >> The comment on the change is: >> Added link to kernel policy (no duplicates) >> >> ------------------------------------------------------------------------------ >> >> When you first look at a new bug, try to find an existing bug in the system that describes the new one. Here's how: >> >> + /!\ Kernel Team policy requires that only a kernel maintainer can set a kernel bug as a duplicate of another bug. See the [[ Kernel/Policies/DuplicateBugs|kernel policy ]] for details. >> * Click the "List open bugs" link at the bottom of the bug page '''or''' >> * Click the "Bugs" tab at the top of the page >> * Both ways will produce a list of bugs about the same package >> > What is process for getting a "kernel maintainer" to look at bug that > may possibly may a duplicate of another? > > > -- > Brian Murray > Ubuntu Bug Master > I had see a tags that refers to need-duplicate-check on another packages, may this could be the best option, adding a comment with the possible duplicate should work indeed. -- Braiam Peguero launchpad.net/~braiamp -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 294 bytes Desc: OpenPGP digital signature URL: From noreply at ubuntu.com Fri Jul 30 01:57:04 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 30 Jul 2010 01:57:04 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_jk-ozl?= =?utf-8?q?abs?= Message-ID: <20100730015704.1648.46094@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 jk-ozlabs: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=7&rev2=8 The comment on the change is: Expand boot option editing section ------------------------------------------------------------------------------ == Boot Options == When trying to capture relevant error messages that appear at boot it is often useful to boot with the '''quiet''' and '''splash''' options removed. This will hopefully allow you to see any messages that come across your screen. To edit boot option parameters, do the following: - 1. Press 'Escape' key at the 3 second pause by Grub bootloader. - 1. Then press 'e' (edit) on the buggy kernel entry, followed by 'e' again on the kernel line. + 1. Boot the machine + 1. Once the BIOS screen goes away, press the left shift key and hold it down. You should get the GRUB menu. + 1. Navigate to the kernel entry you want to boot, and press 'e' + 1. Select the line with the boot options on it (it should start with "linux" or "kernel") and press 'e' again. 1. Then remove the '''splash''' and '''quiet''' keywords and press 'b' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand. From noreply at ubuntu.com Fri Jul 30 14:58:16 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 30 Jul 2010 14:58:16 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100730145816.17362.22104@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 simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=13&rev2=14 ------------------------------------------------------------------------------ = Introduction = - Problems with touchpad detection typically fall into one off these categories: + Problems with touchpad detection typically fall into one of these categories: 1. Your touchpad doesn't work at all. 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. 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. + + == General information before filing the bug == + This information should be provided in the bug description itself: + 1. Laptop model. + 1. Manufacturer of the Touchpad. + 1. When the symptom first appeared. + + 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 emit 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) == 1. File the bug against '''linux''' @@ -36, +51 @@ $ 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 some features of your touchpad like scrolling, tapping, dragging don't work (as expected) == + == In case your touchpad features like scrolling, tapping, etc does not work at all. == + This happens when 'Touchpad' Tab is not there in System>Preferences>Mouse. - 1. File bug against '''xserver-xorg-input-synaptics''' - 1. Provide the [[#generalinfo|general information]]. - 1. Open a terminal and enter the following commands: {{{ - $ cat /proc/bus/input/devices > ~/devices - $ dmesg > ~/dmesg }}} - 1. Attach your {{{/var/log/Xorg.0.log}}}, {{{~/devices}}} and {{{~/dmesg}}} to the bug report in separate attachments. + This may be a wrong detection by the '''xserver''' or the '''kernel''' itself. So xserver-xorg-input-synaptics has nothing to do with it. In case, filing a bug against the kernel('''linux'''), please note that you should not mark the bug as duplicate even if you can find a closely related bug and you have a strong feeling that the bug should be duplicate. This is a new policy of Kernel Team and it help them to handle the bugs better. + + 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 '''Xserver'''. + + In any case, include the outputs of the following commands: {{{ + $ cat /proc/bus/input/devices >~/devices + $ sudo lspci -vvnn > ~/lspci + $ xinput --list > ~/xinput + $ cat /var/log/Xorg.0.log > Xorg.0.log }}} + + Attach all four, to the bug report in separate attachments. + + '''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 == + + eg - Jumpy cursor, scrolling problems, touchpad area is misdetected, circular scrolling, buttons not correctly mapped. + + 1. Enter the following command in a terminal/console: {{{ + $ synclient -l > ~/synclient + $ xmodmap -pp + $ xinput --list-props }}} + 2. Attach {{{~/synclient}}} and your {{{/var/log/Xorg.0.log}}} to the bug report in separate attachments. + + In {{{ xinput --list-props }}}, is of your touchpad in {{{ xinput --list }}}. + + === In case your multitouch features does not work === + + 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 {{{ xinpit --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. + + '''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. + + For any other case, include the outputs in the bug report in separate comments. {{{ + $ synclient -l > ~/synclient + $ xinput --list-props }}} + + Take your pointer in the windows and hold down your two fingres on the touchpad and raise. Also try to tap with two fingers. + {{{ $ xev | grep -i button > ~/xev}}} + + Attach these outputs in separate attachments, in the bug report. + + In {{{ xinput --list-props }}}, is of your touchpad in xinput --list. + + Before filing new bug please look in the common bugs section. + + = 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. + + 1. Check weather 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. + '''Name="SynPS/2 Synaptics TouchPad"''' + + 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. {{{ + $ xinput --list }}} + 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 }}} + + + + + For problems such as scrolling area, touch area, button wrong mapping, multitouch try investigating with + {{{ + $ synclient -m 100 + $ xev }}} + + + Look for name in xinput --list eg - for ↳ TouchPad id=6 [slave pointer (2)], then type + {{{ + $ xinput --list-props 6 }}} + + + = Help regarding using debug utilities = + + + In case when using {{{ synclient -m 100 }}} reports ''SHMConfig'' disabled. Try adding these lines to your xorg.conf file in respective sections. Please make a backup copy of your xorg.conf file before trying this. + + Section "Module" + Load "synaptics" + EndSection + #... + 4 Section "InputDevice" + Driver "synaptics" + Identifier "TouchPad" + Option "Protocol" "auto-dev" + Option "SHMConfig" "on" + EndSection + #... + Section "ServerLayout" + InputDevice "TouchPad" "CorePointer" + EndSection + + + + = Known bugs = + + Synaptics Touchpad Multitouch https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/308191 + + Jumpy cursor https://bugs.edge.launchpad.net/xorg-driver-synaptics/+bug/365943 + + Synaptics Touchpad is incorrectly detected by kernel https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/565543 ---- CategoryBugSquad CategoryDebugging From noreply at ubuntu.com Fri Jul 30 16:46:29 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 30 Jul 2010 16:46:29 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingTouchpadDetection=22_by?= =?utf-8?q?_simar?= Message-ID: <20100730164629.6443.9615@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 simar: http://wiki.ubuntu.com/DebuggingTouchpadDetection?action=diff&rev1=15&rev2=16 ------------------------------------------------------------------------------ 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 '''Xserver'''. + 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 In any case, include the outputs of the following commands: {{{ $ cat /proc/bus/input/devices >~/devices From noreply at ubuntu.com Fri Jul 30 17:22:32 2010 From: noreply at ubuntu.com (=?utf-8?q?Ubuntu_Wiki_?=) Date: Fri, 30 Jul 2010 17:22:32 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_stente?= =?utf-8?q?n?= Message-ID: <20100730172232.13022.88390@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 stenten: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=8&rev2=9 The comment on the change is: Fixed some errors in grub editing (updated instructions to grub2?) and also made the instructions easier to follow. ------------------------------------------------------------------------------ == Boot Options == When trying to capture relevant error messages that appear at boot it is often useful to boot with the '''quiet''' and '''splash''' options removed. This will hopefully allow you to see any messages that come across your screen. To edit boot option parameters, do the following: - 1. Boot the machine + 1. Boot the machine. - 1. Once the BIOS screen goes away, press the left shift key and hold it down. You should get the GRUB menu. + 1. During the BIOS screen, press the shift key and hold it down. You should get the GRUB menu after the BIOS loads. - 1. Navigate to the kernel entry you want to boot, and press 'e' + 1. Navigate to the kernel entry you want to boot, and press 'e'. - 1. Select the line with the boot options on it (it should start with "linux" or "kernel") and press 'e' again. - 1. Then remove the '''splash''' and '''quiet''' keywords and press 'b' to boot. + 1. Then remove the '''quiet''' and '''splash''' keywords and press 'Ctrl+x' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand.