From webmaster at ubuntu.com Sat Feb 2 09:39:42 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 02 Feb 2013 09:39:42 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130202093942.6423.54176@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by penalvch: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=225&rev2=226 Comment: Due to LP# 852190 added note on filing separate report in order to verify hardware. <
><
> Please do not quote Wikipedia and other non-primary resource information as fact on [[Launchpad]]. <
><
> - Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. Please note not following this can delay your problem being addressed as quickly as possible. + Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed. <
><
> Please do not solicit non-original reporters to post comments, attachments, etc. <
><
> From es20490446e at gmail.com Sun Feb 10 13:01:00 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 10 Feb 2013 14:01:00 +0100 Subject: Ubuntu bug live circle Message-ID: <51179A0C.6070602@gmail.com> I wanted to know when, in the live circle of an Ubuntu release, bugs that aren't critical are stopped of being fixed. Thank you in advance. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From fitoschido at gmail.com Sun Feb 10 15:36:45 2013 From: fitoschido at gmail.com (Adolfo Jayme Barrientos) Date: Sun, 10 Feb 2013 09:36:45 -0600 Subject: Ubuntu bug live circle In-Reply-To: <51179A0C.6070602@gmail.com> References: <51179A0C.6070602@gmail.com> Message-ID: On Sun, Feb 10, 2013 at 7:01 AM, Alberto Salvia Novella wrote: > I wanted to know when, in the live circle of an Ubuntu release, bugs that > aren't critical are stopped of being fixed. Thank you in advance. Well, every bug, whatever its importance is, can be fixed by anyone at any time, they just need to step up! AFAIK, the only limitation is when a release goes EOL and therefore can’t receive updates. For example, a bug targeted to Karmic should be marked “Won’t Fix” *for that release* because it is an obsolete release. -- Adolfo From es20490446e at gmail.com Sun Feb 10 16:36:48 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 10 Feb 2013 17:36:48 +0100 Subject: Ubuntu bug live circle In-Reply-To: References: <51179A0C.6070602@gmail.com> Message-ID: <5117CCA0.3040600@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From corbellini.andrea at gmail.com Sun Feb 10 17:28:06 2013 From: corbellini.andrea at gmail.com (Andrea Corbellini) Date: Sun, 10 Feb 2013 17:29:06 +0001 Subject: Ubuntu bug live circle In-Reply-To: <5117CCA0.3040600@gmail.com> References: <51179A0C.6070602@gmail.com> <5117CCA0.3040600@gmail.com> Message-ID: <5117d8af.44050e0a.6aa3.ffffd632@mx.google.com> On Sun, Feb 10, 2013 at 5:36 PM, Alberto Salvia Novella wrote: Sorry, but this explanation seems not to be in accordance with what is explained in the Ubuntu Wiki Stable Release Updates and Final Freeze pages. It seems that the moment when updates for no critical bugs are forbidden is after the final freeze in the Release Schedule. Is this right? FinalFreeze says that only updates that address "Release critical bugs", "Security critical bugs" or "Exceptional circumstances" can land in Ubuntu. StableReleaseUpdate explains what the exceptional circumstances are (see 2. When). None of the two pages put requirements on the importance of the bugs being fixed. Generally, bugs that get fixed through SRUs are Critical, sometimes High, but this is a consequence of the SRU requirements, but not a constraint. In theory, even a Wishlist bug may be fixed through a stable release update, this is perfectly permitted. For example look here: https://bugs.launchpad.net/ubuntu/quantal/+bugs?orderby=-importance&field.status%3Alist=FIXRELEASED&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST&field.tag=verification-done This is the list of all Low and Wishlist bugs that got fixed in Quantal via SRUs. Obviously that list isn't long, however it shows that bug importance and stable release updates are not strictly related. -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Sun Feb 10 23:32:39 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 11 Feb 2013 00:32:39 +0100 Subject: Ubuntu bug live circle In-Reply-To: <5117d8af.44050e0a.6aa3.ffffd632@mx.google.com> References: <51179A0C.6070602@gmail.com> <5117CCA0.3040600@gmail.com> <5117d8af.44050e0a.6aa3.ffffd632@mx.google.com> Message-ID: <51182E17.4000305@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From teward at ubuntu.com Mon Feb 11 14:00:42 2013 From: teward at ubuntu.com (Thomas Ward) Date: Mon, 11 Feb 2013 09:00:42 -0500 Subject: Ubuntu bug live circle In-Reply-To: <51182E17.4000305@gmail.com> References: <51179A0C.6070602@gmail.com> <5117CCA0.3040600@gmail.com> <5117d8af.44050e0a.6aa3.ffffd632@mx.google.com> <51182E17.4000305@gmail.com> Message-ID: God forbid I sound stupid, but which "release" are we talking about? Are we talking about Raring (the development release), or are we talking about lucid, precise, quantal, etc. (stable releases)? If you are talking about stable releases, then I think bugfixes getting in are dependent on people working on them, and the SRU team's take on whether or not to allow the bugfix in. There's no minimum bug severity that can get in, although if the bug severity will cause a new feature to be added, I believe it has to be checked and thoroughly tested prior to inclusion. Otherwise, I've gotten low/medium things fixed in those releases. Of course, those usually are dependent on community verification, since I work a lot with Universe packages. If you're talking about the development release, I tend to try and get bug fixes in before final freeze. Although its not often I'll handle a bug in the development release, so I'm probably not that qualified to comment on the development release. The lifecycle of a release is also in part the lifecycle of a bugfix: Bugfixes are accepted in any release (dependent on others verifying the "bugfix" submitted works, in -proposed (look for "Verification" on that SRU page that was linked to you earlier)) until it is EOL (End of Life). Heck, even Hardy can still get updates, and its almost End of Life. (Any other bugsquader who knows more is free to correct this, as I am not quoting things, this is mostly what I've picked up over my time working in bugs) ------ Thomas Ubuntu Member Ubuntu BugSquad Member On Sun, Feb 10, 2013 at 6:32 PM, Alberto Salvia Novella < es20490446e at gmail.com> wrote: > Oh, thank you. But the question was rather till which point in time a bug > fix can enter the release. > > > El 10/02/13 18:28, Andrea Corbellini escribió: > > On Sun, Feb 10, 2013 at 5:36 PM, Alberto Salvia Novella > wrote: > > Sorry, but this explanation seems not to be in accordance with what is > explained in the Ubuntu Wiki Stable Release Updatesand Final > Freeze pages. It seems that the > moment when updates for no critical bugs are forbidden is after the final > freeze in the Release Schedule. > Is this right? > > > FinalFreeze says that only updates that address "Release critical bugs", > "Security critical bugs" or "Exceptional circumstances" can land in Ubuntu. > > StableReleaseUpdate explains what the exceptional circumstances are (see > 2. When). > > None of the two pages put requirements on the importance of the bugs > being fixed. Generally, bugs that get fixed through SRUs are Critical, > sometimes High, but this is a consequence of the SRU requirements, but not > a constraint. In theory, even a Wishlist bug may be fixed through a stable > release update, this is perfectly permitted. > > For example look here: > > > https://bugs.launchpad.net/ubuntu/quantal/+bugs?orderby=-importance&field.status%3Alist=FIXRELEASED&field.importance%3Alist=LOW&field.importance%3Alist=WISHLIST&field.tag=verification-done > > This is the list of all Low and Wishlist bugs that got fixed in Quantal > via SRUs. Obviously that list isn't long, however it shows that bug > importance and stable release updates are not strictly related. > > > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Mon Feb 11 11:53:03 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 11 Feb 2013 11:53:03 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Kernel/Debugging/Backlight=22_by?= =?utf-8?q?_xintx-ua?= Message-ID: <20130211115303.26589.62461@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Kernel/Debugging/Backlight" page has been changed by xintx-ua: http://wiki.ubuntu.com/Kernel/Debugging/Backlight?action=diff&rev1=21&rev2=22 Comment: sudo is not needed after sudo su * If you have folder /sys/class/backlight/intel_backlight/ : * type {{{sudo su}}} , and then execute: * ls -la /sys/class/backlight/intel_backlight/ > lslabacklight - * {{{sudo echo 8 > /sys/class/backlight/intel_backlight/brightness}}} + * {{{echo 8 > /sys/class/backlight/intel_backlight/brightness}}} * Please comment on if the brightness changes. * Reboot with kernel parameter video.use_bios_initial_backlight=0 and make a comment on if you can now alter the backlight with hotkeys or a brightness applet. * If your backlight hotkeys are Fn+Left and Fn+Right, add kernel parameter atkbd.softraw=0 to /boot/grub/menu.lst . Then, switch to any console, e.g. Ctrl+Alt+F1, login by root account and execute:<
> {{{showkey -s}}} <
> <
> Then, press Fn+Left and Fn+Right key to check the code that shows up on screen. Post the results to the report. For example: <
> <
> Fn+Left: <
> 0xe0 0x4c 0xe0 0xcc <
> <
> Fn+Right: <
> 0xe0 0x54 0xe0 0xd4 From notgary at ubuntu.com Tue Feb 12 13:11:34 2013 From: notgary at ubuntu.com (Chris Wilson) Date: Tue, 12 Feb 2013 13:11:34 +0000 Subject: Paper cuts and the bug squad Message-ID: Hey there, For those of you who don't know me, my name's Chris Wilson and I'm the leader of the One Hundred Paper Cuts project. We're currently looking for ways to breath new life into the project, and one of the ideas we've had was to work with you, the Bug Squad. The problem we face is that we need a steady supply of new bug reports, approximately 50-100 per month, from which we identify the genuine paper cuts and start working on them. The way the Bug Squad can help us with this is through the 'Hug Days'. In these events, you look through all the bugs for a particular package and touch them in some way. What I was thinking was that you could keep an eye out for candidate paper cuts and forward them to us. Don't worry too much about whether or not it actually is one. We'll handle that. We're not asking you to help us in return for nothing though. The paper cuts project can help the Bug Squad during the same events. One of our goals is to provide an environment in which new Ubuntu contributors can get experience with the different areas of Ubuntu development that we touch, and one of them is bug triage. During the Hug Days we would have the Bug Squad forwarding us candidate paper cuts and the Paper Cut Ninjas triaging Ubuntu bugs, so both teams are getting something out of this. Due to the nature of our work, there's a limited number of packages that we touch, so it wouldn't be every Hug Day. I was thinking one such day in a month, or perhaps even a weekend-long sprint every two or three month. The specifics are still up for discussion, but the jist of it is I would like both our teams to collaborate on each others goals given our work overlaps in many areas (we require the ubuntu task to be triaged before the paper cut task can be triaged, etc). What do you lot think about this? Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From jordannh at fastmail.fm Tue Feb 12 16:01:39 2013 From: jordannh at fastmail.fm (Jordan Hewitt) Date: Tue, 12 Feb 2013 08:01:39 -0800 Subject: Paper cuts and the bug squad In-Reply-To: References: Message-ID: <511A6763.30600@fastmail.fm> Sounds good. I'm always looking for ways to get involved. Can't wait. On Tue 12 Feb 2013 05:11:34 AM PST, Chris Wilson wrote: > Hey there, > > For those of you who don't know me, my name's Chris Wilson and I'm the > leader of the One Hundred Paper Cuts project. We're currently looking > for ways to breath new life into the project, and one of the ideas > we've had was to work with you, the Bug Squad. > > The problem we face is that we need a steady supply of new bug > reports, approximately 50-100 per month, from which we identify the > genuine paper cuts and start working on them. > > The way the Bug Squad can help us with this is through the 'Hug Days'. > In these events, you look through all the bugs for a particular > package and touch them in some way. What I was thinking was that you > could keep an eye out for candidate paper cuts and forward them to us. > Don't worry too much about whether or not it actually is one. We'll > handle that. > > We're not asking you to help us in return for nothing though. The > paper cuts project can help the Bug Squad during the same events. One > of our goals is to provide an environment in which new Ubuntu > contributors can get experience with the different areas of Ubuntu > development that we touch, and one of them is bug triage. > > During the Hug Days we would have the Bug Squad forwarding us > candidate paper cuts and the Paper Cut Ninjas triaging Ubuntu bugs, so > both teams are getting something out of this. > > Due to the nature of our work, there's a limited number of packages > that we touch, so it wouldn't be every Hug Day. I was thinking one > such day in a month, or perhaps even a weekend-long sprint every two > or three month. The specifics are still up for discussion, but the > jist of it is I would like both our teams to collaborate on each > others goals given our work overlaps in many areas (we require the > ubuntu task to be triaged before the paper cut task can be triaged, etc). > > What do you lot think about this? > > Chris > > From marconifabio at hotmail.it Tue Feb 12 16:15:28 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Tue, 12 Feb 2013 17:15:28 +0100 Subject: Paper cuts and the bug squad In-Reply-To: <511A6763.30600@fastmail.fm> References: <511A6763.30600@fastmail.fm> Message-ID: The real problem is that actually we don't have a manager for the hugday and actually seems a sleeping project. I can pick it up, but I need to be mentored by pedro_ or someone other, what do you think ? >> Hey there, >> >> For those of you who don't know me, my name's Chris Wilson and I'm the >> leader of the One Hundred Paper Cuts project. We're currently looking >> for ways to breath new life into the project, and one of the ideas >> we've had was to work with you, the Bug Squad. >> >> The problem we face is that we need a steady supply of new bug >> reports, approximately 50-100 per month, from which we identify the >> genuine paper cuts and start working on them. >> >> The way the Bug Squad can help us with this is through the 'Hug Days'. >> In these events, you look through all the bugs for a particular >> package and touch them in some way. What I was thinking was that you >> could keep an eye out for candidate paper cuts and forward them to us. >> Don't worry too much about whether or not it actually is one. We'll >> handle that. >> >> We're not asking you to help us in return for nothing though. The >> paper cuts project can help the Bug Squad during the same events. One >> of our goals is to provide an environment in which new Ubuntu >> contributors can get experience with the different areas of Ubuntu >> development that we touch, and one of them is bug triage. >> >> During the Hug Days we would have the Bug Squad forwarding us >> candidate paper cuts and the Paper Cut Ninjas triaging Ubuntu bugs, so >> both teams are getting something out of this. >> >> Due to the nature of our work, there's a limited number of packages >> that we touch, so it wouldn't be every Hug Day. I was thinking one >> such day in a month, or perhaps even a weekend-long sprint every two >> or three month. The specifics are still up for discussion, but the >> jist of it is I would like both our teams to collaborate on each >> others goals given our work overlaps in many areas (we require the >> ubuntu task to be triaged before the paper cut task can be triaged, etc). >> >> What do you lot think about this? >> >> Chris >> >> From om26er at ubuntu.com Tue Feb 12 17:32:16 2013 From: om26er at ubuntu.com (Omer Akram) Date: Tue, 12 Feb 2013 22:32:16 +0500 Subject: Announcing the Next Ubuntu Bug Day! - Thursday 14, Feb Message-ID: Hi all! The target of bug triage for this week is Totem. The movie player that we all love ;) If you looking for a way to start giving some love back to your 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! On February 14 we all are going to gather and triage bugs for Totem. Please mark of the bugs that you triage here < https://wiki.ubuntu.com/UbuntuBugDay/20130214> 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 Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Tue Feb 12 17:36:00 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 12 Feb 2013 18:36:00 +0100 Subject: Paper cuts and the bug squad In-Reply-To: References: <511A6763.30600@fastmail.fm> Message-ID: <511A7D80.70201@gmail.com> In my opinion hugdays are very important, so we would like to make them a standard. On the other hand, I think the one hundred paper cuts proposal is mandatory. El 12/02/13 17:15, Fabio Marconi escribió: > The real problem is that actually we don't have a manager for the hugday > and actually seems a sleeping project. > I can pick it up, but I need to be mentored by pedro_ or someone other, > what do you think ? > >>> Hey there, >>> >>> For those of you who don't know me, my name's Chris Wilson and I'm the >>> leader of the One Hundred Paper Cuts project. We're currently looking >>> for ways to breath new life into the project, and one of the ideas >>> we've had was to work with you, the Bug Squad. >>> >>> The problem we face is that we need a steady supply of new bug >>> reports, approximately 50-100 per month, from which we identify the >>> genuine paper cuts and start working on them. >>> >>> The way the Bug Squad can help us with this is through the 'Hug Days'. >>> In these events, you look through all the bugs for a particular >>> package and touch them in some way. What I was thinking was that you >>> could keep an eye out for candidate paper cuts and forward them to us. >>> Don't worry too much about whether or not it actually is one. We'll >>> handle that. >>> >>> We're not asking you to help us in return for nothing though. The >>> paper cuts project can help the Bug Squad during the same events. One >>> of our goals is to provide an environment in which new Ubuntu >>> contributors can get experience with the different areas of Ubuntu >>> development that we touch, and one of them is bug triage. >>> >>> During the Hug Days we would have the Bug Squad forwarding us >>> candidate paper cuts and the Paper Cut Ninjas triaging Ubuntu bugs, so >>> both teams are getting something out of this. >>> >>> Due to the nature of our work, there's a limited number of packages >>> that we touch, so it wouldn't be every Hug Day. I was thinking one >>> such day in a month, or perhaps even a weekend-long sprint every two >>> or three month. The specifics are still up for discussion, but the >>> jist of it is I would like both our teams to collaborate on each >>> others goals given our work overlaps in many areas (we require the >>> ubuntu task to be triaged before the paper cut task can be triaged, etc). >>> >>> What do you lot think about this? >>> >>> Chris >>> >>> > -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From es20490446e at gmail.com Tue Feb 12 17:38:12 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Tue, 12 Feb 2013 18:38:12 +0100 Subject: Paper cuts and the bug squad In-Reply-To: References: <511A6763.30600@fastmail.fm> Message-ID: <511A7E04.9040303@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From noreply at ubuntu.com Tue Feb 12 17:22:27 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 12 Feb 2013 17:22:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Events=22_by_om26er?= Message-ID: <20130212172227.11640.86807@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Events" page has been changed by om26er: http://wiki.ubuntu.com/Bugs/Events?action=diff&rev1=264&rev2=265 || '''Name''' || '''Tag used''' || ## StartHugDayParsing + || [[UbuntuBugDay/20130214| Totem]] hugday-20130214 || || [[UbuntuBugDay/20130117| Transmission]] hugday-20130117 || || [[UbuntuBugDay/20111027| Nautilus]] || hugday-20111027 || || [[UbuntuBugDay/20111020| Bugs without a package]] || hugday-20111020 || From notgary at ubuntu.com Thu Feb 14 14:36:24 2013 From: notgary at ubuntu.com (Chris Wilson) Date: Thu, 14 Feb 2013 14:36:24 +0000 Subject: Paper cuts and the bug squad In-Reply-To: References: <511A6763.30600@fastmail.fm> Message-ID: On 12 February 2013 16:15, Fabio Marconi wrote: > The real problem is that actually we don't have a manager for the hugday > and actually seems a sleeping project. > I can pick it up, but I need to be mentored by pedro_ or someone other, > what do you think ? What sort of workload would be involved in managing the Hug Days? If it's not too great I'd be happy to take it on. -------------- next part -------------- An HTML attachment was scrubbed... URL: From melchiaros at aol.com Thu Feb 14 14:39:52 2013 From: melchiaros at aol.com (melchiaros) Date: Thu, 14 Feb 2013 15:39:52 +0100 Subject: icon for already upstream reported bugs on launchpad Message-ID: <511CF738.6010500@aol.com> May be you sometimes run in reports that are already upstream reported. Unfortunately this could not be seen at a glance before calling the ticket in detail in your browser. I have filed a report against "Launchpad Itself" that faces this problem. My suggestion there is to add a icon specific for this like those ones we have for branches, patches, blueprints and so on. This for summary. The full report and description can be found at: https://bugs.launchpad.net/launchpad/+bug/1125208 If you could agree to this you might give the report a "Also affects me". greetings to all melchiaros From es20490446e at gmail.com Thu Feb 14 17:23:55 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 14 Feb 2013 18:23:55 +0100 Subject: WARNING: "hugday-tools" package cannot be installed in binary format in Ubuntu 12.10 Message-ID: <511D1DAB.4010701@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From es20490446e at gmail.com Thu Feb 14 17:24:20 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 14 Feb 2013 18:24:20 +0100 Subject: WARNING: "hugday-tools" package cannot be installed in binary format in Ubuntu 12.10 Message-ID: <511D1DC4.8080303@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2260 bytes Desc: Firma criptográfica S/MIME URL: From chrisjohnston at ubuntu.com Thu Feb 14 21:21:25 2013 From: chrisjohnston at ubuntu.com (Chris Johnston) Date: Thu, 14 Feb 2013 16:21:25 -0500 Subject: WARNING: "hugday-tools" package cannot be installed in binary format in Ubuntu 12.10 In-Reply-To: <511D1DC4.8080303@gmail.com> References: <511D1DC4.8080303@gmail.com> Message-ID: <511D5555.8070409@ubuntu.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/14/2013 12:24 PM, Alberto Salvia Novella wrote: > STEPS TO REPRODUCE *********************** 1. Open the "Software > Sources" application. 2. In the "Other software" tab, enter the > ppa"ppa:thekorn/ppa > ". 3. In the > terminal type "sudo apt-get update && sudo apt-get install > hugday-tools" and press enter. > > EXPECTED BEHAVIOUR *********************** hugday-tools to be > installed. > > REAL BEHAVIOUR ****************** The terminal prints the following > errors: W: Imposible to obtain > http://ppa.launchpad.net/thekorn/ppa/ubuntu/dists/quantal/main/source/Sources > > 404 Not Found > W: Imposible to obtain > http://ppa.launchpad.net/thekorn/ppa/ubuntu/dists/quantal/main/binary-amd64/Packages > > 404 Not Found > W: Imposible to obtain > http://ppa.launchpad.net/thekorn/ppa/ubuntu/dists/quantal/main/binary-i386/Packages > > 404 Not Found > > RELEVANT DETAILS ******************* - The HughDay wiki > is configured so > that it cannot be edited without hugday-tools. - Users who doesn't > know how to compile from the UTAH Dev team in Launchpad > 's source code will be unable to > contribute to the HughDay. > > > Since there hasn't been a package created for hugday-tools since Jaunty. It seems as though the script was moved over to the ubuntu-qa-tools package. You could try installing it from ppa:utah/stable. FWIW, I was able to edit the HugDay wiki page without having the package installed. - -- Respectfully, Chris Johnston chrisjohnston at ubuntu.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlEdVUwACgkQyDxSNf9BQVxNyACdEYFsIxLFoIYIUFg1rd+g+g/y Z+wAn1lBHUXWOhr0fwGYJK1bjU4qLWax =K+2P -----END PGP SIGNATURE----- From noreply at ubuntu.com Fri Feb 15 17:29:48 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 15 Feb 2013 17:29:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingGNOMEPowerManager=22_by?= =?utf-8?q?_jm-leddy?= Message-ID: <20130215172948.17264.69527@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingGNOMEPowerManager" page has been changed by jm-leddy: http://wiki.ubuntu.com/DebuggingGNOMEPowerManager?action=diff&rev1=34&rev2=35 ||<>|| - == Oneiric == + == Oneiric and Later == - If you're running Oneiric you'll notice that the Power Management was moved to GNOME Settings Daemon, thus all the bugs affecting GNOME Power Manager in Oneiric are about the statistics ui and not the daemon. If you're having issues with Power Management in Oneiric please use this method to report bugs to GNOME Settings Daemon: + If you're running Oneiric or later you'll notice that the Power Management was moved to GNOME Settings Daemon, thus all the bugs affecting GNOME Power Manager in Oneiric are about the statistics ui and not the daemon. If you're having issues with Power Management in Oneiric please use this method to report bugs to GNOME Settings Daemon: Run g-s-d as: From oizhztl at gmail.com Mon Feb 18 18:12:04 2013 From: oizhztl at gmail.com (James Lee) Date: Mon, 18 Feb 2013 10:12:04 -0800 Subject: 12.10 - crash & reboots. Message-ID: <51226EF4.4040107@gmail.com> Hello, I'm glad to find this contact information and hope this is a correct way to seek a help. My kernel is identified as: Linux fx4100 3.5.0-24-generic #37-Ubuntu SMP Thu Feb 7 01:50:30 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux My system randomly crashes during normal tasks such as Firefox web browsing, Thunderbird mail checking, VM machine running and basically anytime unexpected. The symptom is that the screen (the mouse pointer or cursor) freezes all of sudden - no patterns, no specific time, as short as 10 minutes after a boot-up and as long as 2 days last but surely it happens - wait 3 sec, and then reboots without any error message. Therefore, I was never given a chance to the DebuggingProcedures described in here: https://wiki.ubuntu.com/DebuggingProcedures I attach the log files as attachments in a wish to solve this riddle. Should you require further information, I'm willing to submit them. I look forward to seeing Ubuntu team resolve this critical issue in the near future. Thank you! Kind Regards, James Lee -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: auth.log Type: text/x-log Size: 14399 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: syslog.log Type: text/x-log Size: 242633 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: xorg.0.log Type: text/x-log Size: 70394 bytes Desc: not available URL: From noreply at ubuntu.com Fri Feb 22 22:41:24 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 22 Feb 2013 22:41:24 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingBanshee=22_by_dtl131?= Message-ID: <20130222224124.28450.36817@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingBanshee" page has been changed by dtl131: http://wiki.ubuntu.com/DebuggingBanshee?action=diff&rev1=7&rev2=8 Comment: Add .config/banshee-1/always-debug method for intermittent crashing = Debugging procedure = 1. Debugging Banshee from a terminal, please run "banshee --debug" and attach all output information + 3. If the issue is intermittant crash, create a file called ~/.config/banshee-1/always-debug, then the next time banshee crashes, copy out ~/.config/banshee-1/log and upload it. 2. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily 3. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition or http://banshee.fm/support/faq/ From webmaster at ubuntu.com Sat Feb 23 17:52:35 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 23 Feb 2013 17:52:35 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_chris-bainbridge?= Message-ID: <20130223175235.31359.92275@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by chris-bainbridge: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=227&rev2=228 Comment: well apport-cli seems to work }}} Save, close, and try to file the crash report again via: {{{ ubuntu-bug /var/crash/_my_crash_report.crash - }}} (NOTE: this not appear to work on Ubuntu 12.04.2 - once started, ubuntu-bug will state "The application X has closed unexpectedly. [Show details] [Leave Closed] [Relaunch]". There is no option to upload the crash report.'') + }}} (NOTE: this not appear to work on Ubuntu 12.04.2 - once started, ubuntu-bug will state "The application X has closed unexpectedly. [Show details] [Leave Closed] [Relaunch]". There is no option to upload the crash report.'' Instead do 'apport-cli /var/crash/_my_crash_report.crash' whcih does seem to work.) /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. @@ -242, +242 @@ After copying it to a different system you can file that report using the following command:<
>`ubuntu-bug -c` ''``'' - /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad." A possible workaround is detailed above in the section "Reporting an application crash > Stable release" + /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad." A possible workaround is detailed above in the section "Reporting an application crash > Stable release": UPDATE: 'apport-cli -c x.crash' seems to work If this is to be added to an existing bug report, also use the -u option:<
>`ubuntu-bug -c` ''``'' `-u` ''``'' From eugen.hollrotter at arcor.de Sat Feb 23 11:15:53 2013 From: eugen.hollrotter at arcor.de (eh) Date: Sat, 23 Feb 2013 12:15:53 +0100 Subject: eth0: ERROR while getting interface flags Message-ID: <1361618153.2903.2.camel@nulco> Hi is there help for the problem with Ubuntu 10.04, doesn't have a eth0 driver built in. The computer is: ASUS F75A-TY047 purchased February 2013 with no Windows on and Bios access and no UEFI. Linux nco 2.6.32-38-generic #83-Ubuntu SMP Wed Jan 4 11:12:07 UTC 2012 x86_64 GNU/Linux installed and running except eth0. Other distros have the same problem, Knoppix, Debian, assume due to the same kernel. Network/Ethernet 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device 8176 (rev 01) 03:00.0 Ethernet controller: Atheros Communications Device 1091 (rev 10) SIOCSIFADDR: No such device eth0: ERROR while getting interface flags: No such device eth0: ERROR while getting interface flags: No such device Bind socket to interface: No such device Failed to bring up eth0. /etc/network$ sudo route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface nothing, no routing table /etc/network$ sudo dmesg | grep eth0 /etc/network$ // in kernel messages no eth0, no eth1, no eth2 rocky at nco:~$ sudo ifup -a [sudo] password for rocky: Internet Systems Consortium DHCP Client V3.1.3 Copyright 2004-2009 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ The mentioned solution was with:"compat-wireless-2.6.tar.bz2" I found loads of articles about but failed to install the most likely solution: compat-drivers-3.8-1.tar.bz2 I appreciate all help to get it running. Many thanks Eugen From webmaster at ubuntu.com Sat Feb 23 17:34:11 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Sat, 23 Feb 2013 17:34:11 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_chris-bainbridge?= Message-ID: <20130223173411.31691.64045@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by chris-bainbridge: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=226&rev2=227 Comment: workaround for reporting crash reports to launchpad does not appear to work }}} Save, close, and try to file the crash report again via: {{{ ubuntu-bug /var/crash/_my_crash_report.crash + }}} (NOTE: this not appear to work on Ubuntu 12.04.2 - once started, ubuntu-bug will state "The application X has closed unexpectedly. [Show details] [Leave Closed] [Relaunch]". There is no option to upload the crash report.'') + - }}} /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. + /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. === System crash === @@ -238, +240 @@ You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the `.apport` or `.crash` extension. - After copying it to a different system you can file that report using the following command:<
>`ubuntu-bug -c` ''``'' + After copying it to a different system you can file that report using the following command:<
>`ubuntu-bug -c` ''``'' + - (note: this does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad.") + /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases, see [[https://bugs.launchpad.net/apport/+bug/997283|bug #997283]] crash reports "do not get filed to Launchpad any more... we don't want crash reports for the non-development version on Launchpad." A possible workaround is detailed above in the section "Reporting an application crash > Stable release" If this is to be added to an existing bug report, also use the -u option:<
>`ubuntu-bug -c` ''``'' `-u` ''``'' From noreply at ubuntu.com Mon Feb 25 00:42:39 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 25 Feb 2013 00:42:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingBanshee=22_by_mfisch?= Message-ID: <20130225004239.24970.92345@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingBanshee" page has been changed by mfisch: http://wiki.ubuntu.com/DebuggingBanshee?action=diff&rev1=9&rev2=10 = Debugging procedure = 1. Debugging Banshee from a terminal, please run "banshee --debug" and attach all output information - 3. If the issue is intermittent crash, create a file called ~/.config/banshee-1/always-debug, then the next time banshee crashes, copy out ~/.config/banshee-1/log and upload it. - 2. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily + 1. Debugging latest release from daily ppa repository, url is at https://launchpad.net/~banshee-team/+archive/banshee-daily - 3. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition or http://banshee.fm/support/faq/ + 1. Hardware not detected and further information at http://live.gnome.org/Banshee/LibgpodTransition or http://banshee.fm/support/faq/ + 1. If the issue is an intermittent crash, create a file called ~/.config/banshee-1/always-debug, then the next time banshee crashes, copy out ~/.config/banshee-1/log and upload it. = How to Triage Issues related to UbuntuOne extension = From noreply at ubuntu.com Wed Feb 27 04:45:17 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 27 Feb 2013 04:45:17 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22X/Troubleshooting=22_by_shankao?= Message-ID: <20130227044517.22056.44691@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "X/Troubleshooting" page has been changed by shankao: http://wiki.ubuntu.com/X/Troubleshooting?action=diff&rev1=60&rev2=61 Comment: gdm is not the default display manager in Ubuntu these days Booting * [[https://help.ubuntu.com/community/BootOptions|Boot Options]] * [[DebuggingKernelBoot|Debugging Kernel Boot Problems]] - * [[X/NonGraphicalBoot|Non-Graphical Booting]] - Running X manually, without gdm + * [[X/NonGraphicalBoot|Non-Graphical Booting]] - Running X manually, without a display manager (like lightdm, kdm, gdm...) * [[X/Debugging/WirelessWithoutX|Wireless Without X]] - How to get a wireless network connection without X. * [[X/Debugging/WiredWithoutRouter|Direct Wired Without WAP]] - How to connect two laptops with direct ethernet cord. From noreply at ubuntu.com Wed Feb 27 09:54:50 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 27 Feb 2013 09:54:50 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_shan?= =?utf-8?q?kao?= Message-ID: <20130227095450.9959.82382@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/FindRightPackage" page has been changed by shankao: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=123&rev2=124 Comment: Note which package to fill bugs against The Ubuntu graphical environment is provided by a combination of the Linux kernel and the X Window System (aka X.org). - The following symptoms typically are due to GPU issues in the kernel DRM driver: + The following symptoms typically are due to GPU issues in the kernel DRM driver (linux package): * Blank or solid-colored screen instead of login screen, or immediately after login * System freezes completely