From es20490446e at gmail.com Thu May 9 14:04:38 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 09 May 2013 16:04:38 +0200 Subject: [Papercuts-ninja] Paper Cuts in 13.10 In-Reply-To: <1368103517.59182.YahooMailNeo@web163405.mail.gq1.yahoo.com> References: <1368103517.59182.YahooMailNeo@web163405.mail.gq1.yahoo.com> Message-ID: <518BACF6.9060609@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 Sun May 12 14:54:01 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 12 May 2013 14:54:01 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_gie?= =?utf-8?q?crilj?= Message-ID: <20130512145401.429.88771@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by giecrilj: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=39&rev2=40 Comment: proceed only if successful OK. With that understood.... In order to simulate your suspend/resume process, enter the following commands: {{{ - sudo sh -c "sync; echo 1 > /sys/power/pm_trace; pm-suspend" + sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend" }}} At this point your computer should enter the suspend state within a few seconds. Usually the power LED will slowly flash when in the suspended state. When that has happened, initiate the resume process by pressing the power button. Observe closely if the disk light comes on briefly. This indicates that resume has begun. If resume fails to complete, then press the power button until the computer turns off. Power on your computer making sure that it loads the same kernel that exhibited the resume problem. You have about 3 minutes to start this boot process before the information saved in the RTC gets corrupted. From bkerensa at ubuntu.com Mon May 13 08:36:41 2013 From: bkerensa at ubuntu.com (Benjamin Kerensa) Date: Mon, 13 May 2013 01:36:41 -0700 Subject: firefox-lp-improvements Message-ID: So as many of you are probably aware the firefox-lp-improvements add-on has stopped working and I have talked to Brian Murray about it and apparently we have hit a roadblock on trying to fix it. Is there anyone who might be able to fix it on the mailing list? Perhaps someone familiar with making Firefox Add-Ons. Here is the PPA https://launchpad.net/~gm-dev-launchpad/+archive/ppa and source package https://launchpad.net/~gm-dev-launchpad/+archive/ppa/+files/firefox-lp-improvements_0.99.93-0ubuntu1%7Eppa1.tar.gz -- Benjamin Kerensa http://benjaminkerensa.com "I am what I am because of who we all are" - Ubuntu From brian at ubuntu.com Mon May 13 16:13:15 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 13 May 2013 09:13:15 -0700 Subject: firefox-lp-improvements In-Reply-To: References: Message-ID: <20130513161314.GR2977@murraytwins.com> On Mon, May 13, 2013 at 01:36:41AM -0700, Benjamin Kerensa wrote: > So as many of you are probably aware the firefox-lp-improvements > add-on has stopped working and I have talked to Brian Murray about it > and apparently we have hit a roadblock on trying to fix it. Is there > anyone who might be able to fix it on the mailing list? Perhaps > someone familiar with making Firefox Add-Ons. To be clear, the whole add-on has not stopped working rather the functionality of reloading the standard responses and tags to add has stopped working. Additionally, the greasemonkey scripts, of which the Firefox add-on is a compilation, continues to work. > Here is the PPA https://launchpad.net/~gm-dev-launchpad/+archive/ppa > and source package > https://launchpad.net/~gm-dev-launchpad/+archive/ppa/+files/firefox-lp-improvements_0.99.93-0ubuntu1%7Eppa1.tar.gz I looked at this a bit more just now and as I've already mentioned the issue is with loading the bug tags or standard responses. (It is still possible to tag the bugs using the add-on.) You can view the specific code that does this here: http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/view/head:/lp_buttontags.user.js#L76 Using the error console, accessible in the Tools menu under Web Developer, in Firefox I see a message regarding 'syntax error' and 'undefined'. That wasn't very helpful to me at least. -- 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 dwoodcock1 at cogeco.ca Tue May 14 13:29:24 2013 From: dwoodcock1 at cogeco.ca (David E Woodcock EE) Date: Tue, 14 May 2013 09:29:24 -0400 Subject: Touch pad options grayed out Message-ID: <51923C34.5060901@cogeco.ca> Hello Hp dv8000 ....... After upgrading to 13.04 the touch pad options are grayed out, the tap to click function is making my life miserable. Please help if can. David -- -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: address.PNG Type: image/png Size: 50091 bytes Desc: not available URL: From gnu699 at gmail.com Wed May 15 21:40:16 2013 From: gnu699 at gmail.com (Francois Gnu) Date: Wed, 15 May 2013 16:40:16 -0500 Subject: Locker killed to resolve a deadlock Message-ID: Hi masters, Since yesterday, i have that error in my log /var/log/syslog: slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "objectClass" index add failure slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "objectClass" index add failure slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure slapd[861]: <= bdb_equality_candidates: (mail) not indexed slapd[861]: <= bdb_equality_candidates: (mail) not indexed slapd[861]: => bdb_idl_insert_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure slapd[861]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryCSN" index delete failure slapd[861]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryCSN" index delete failure slapd[861]: => bdb_idl_insert_key: c_get failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) slapd[861]: conn=-1 op=0: attribute "entryUUID" index add failure That, causes the size of logs increases very quickly, 10Mo every minute. I used slapindex, but the problem persists. I use ubuntu 12.04 with slapd 2.4.28. I have 15 ldap servers (MMR) and its affects all the 15 servers. All servers are virtualized in KVM. I attached the provider config that is connected at all the consumers. The consumers are cut in 3 groups of 5 servers. Provider: 1,5Go Ram | 2Go swap | olcDbConfig: set_cachesize 0 734003200 0 Consumers: 512Mo | 2Go swap | olcDbConfig: set_cachesize 0 209715200 0 Thanks very much to help me! -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: config.ldif Type: application/octet-stream Size: 64898 bytes Desc: not available URL: From es20490446e at gmail.com Thu May 16 16:01:41 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 16 May 2013 18:01:41 +0200 Subject: Release model Message-ID: <519502E5.7000107@gmail.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5542 bytes Desc: Firma criptográfica S/MIME URL: From brian at ubuntu.com Thu May 16 22:56:22 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 16 May 2013 15:56:22 -0700 Subject: Locker killed to resolve a deadlock In-Reply-To: References: Message-ID: <20130516225622.GY2977@murraytwins.com> On Wed, May 15, 2013 at 04:40:16PM -0500, Francois Gnu wrote: > Hi masters, > Since yesterday, i have that error in my log /var/log/syslog: > > > slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "objectClass" index add failure > slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "objectClass" index add failure > slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure > slapd[861]: <= bdb_equality_candidates: (mail) not indexed > slapd[861]: <= bdb_equality_candidates: (mail) not indexed > slapd[861]: => bdb_idl_insert_key: c_get failed: DB_LOCK_DEADLOCK: Locker > killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure > slapd[861]: => bdb_idl_insert_key: c_put id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryCSN" index add failure > slapd[861]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryCSN" index delete failure > slapd[861]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: > Locker killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryCSN" index delete failure > slapd[861]: => bdb_idl_insert_key: c_get failed: DB_LOCK_DEADLOCK: Locker > killed to resolve a deadlock (-30994) > slapd[861]: conn=-1 op=0: attribute "entryUUID" index add failure > > That, causes the size of logs increases very quickly, 10Mo every minute. > > I used slapindex, but the problem persists. > > I use ubuntu 12.04 with slapd 2.4.28. > I have 15 ldap servers (MMR) and its affects all the 15 servers. > All servers are virtualized in KVM. > > I attached the provider config that is connected at all the consumers. > The consumers are cut in 3 groups of 5 servers. > > Provider: 1,5Go Ram | 2Go swap | olcDbConfig: set_cachesize 0 734003200 0 > Consumers: 512Mo | 2Go swap | olcDbConfig: set_cachesize 0 209715200 0 I don't see any existing bug reports with these error message in the log files. You might check with the Ubuntu server team in #ubuntu-server on freenode. -- 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 gnu699 at gmail.com Fri May 17 01:27:58 2013 From: gnu699 at gmail.com (Francois Gnu) Date: Thu, 16 May 2013 20:27:58 -0500 Subject: segfault at 4 ip b6a201aa sp 9ecf9e30 error 4 in syncprov-2.4.so.2.8.1[b6a1b000+b000] Message-ID: Hello masters, I have that in my /var/log/syslog: slapd[1715]: segfault at 4 ip b6a201aa sp 9ecf9e30 error 4 in syncprov-2.4.so.2.8.1[b6a1b000+b000] and the service slapd stop. uname -a Linux 3.2.0-43-generic-pae #68-Ubuntu SMP Wed May 15 03:55:10 UTC 2013 i686 i686 i386 GNU/Linux It's a bug? Thanks a lot -------------- next part -------------- An HTML attachment was scrubbed... URL: From gnu699 at gmail.com Fri May 17 01:27:59 2013 From: gnu699 at gmail.com (Francois Gnu) Date: Thu, 16 May 2013 20:27:59 -0500 Subject: segfault at b ip b76662c9 sp 9e8f8da0 error 4 in slapd[b7610000+12f000] Message-ID: Hello masters, I have that in my /var/log/syslog: slapd[1814]: segfault at b ip b76662c9 sp 9e8f8da0 error 4 in slapd[b7610000+12f000] and the service slapd stop. uname -a Linux 3.2.0-43-generic-pae #68-Ubuntu SMP Wed May 15 03:55:10 UTC 2013 i686 i686 i386 GNU/Linux It's a bug? Thanks a lot -------------- next part -------------- An HTML attachment was scrubbed... URL: From brian at ubuntu.com Fri May 17 15:02:35 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 17 May 2013 08:02:35 -0700 Subject: adopting the package ubuntu-release-upgrader In-Reply-To: <517A5D3E.2060105@aol.com> References: <517A5D3E.2060105@aol.com> Message-ID: <20130517150234.GB2977@murraytwins.com> On Fri, Apr 26, 2013 at 12:55:58PM +0200, melchiaros wrote: > Hi there, > > you know in the near past I have had some interest in the package > ubuntu-release-upgrader. > > My motivation to this comes from the point to lower the rate of > problems/reports that hit us all on launchpad from the user community. > > Beside this the idee of shortening the relases cycle time with the ideal > of a rolling-release that is really rolling on the bleading edge of > software is a idea I like. This would also circumvent the problmes that > those of us are facing on trying to report upstream on older versions of > software. The most upstream developers are not so happy about reports on > older versions. > > Also the upstream projects by themselfs are boiling down the rate of > errors the software has which they develop. I see the tendece that all > becomes better with release to release. With this it is to expect that a > user community that is in middle more to the latest develoments is a > community that reports lesser bugs (not at whole if the user community > is increasing, but seen on each head). > > The package ubuntu-release-upgrader is a kind of software that plays the > central role for this road of shortening the gab between the latest > software versions and the final releases. > > In respect to this I would like to adopt the package > ubuntu-release-upgrader. > > https://wiki.ubuntu.com/BugSquad/AdoptPackage > > Is there a possibility to get automatic notifications of new reports to > this package? If so could someone give me a workflow or just add me? It is possible to subscribe to the bugs about a particular package using the following steps, using ubuntu-release-upgrader as an example. 1) Visit https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader 2) Click "Subscribe to bug mail" which opens a little dialog 3) Click "are added or changed in anyway" 4) Click "Create" This will of course subscribe you to any changes about bugs that have a task for the ubuntu-release-upgrader package, which can be a fair bit of e-mail. There is a wiki page regarding filtering bug mail at: https://wiki.ubuntu.com/Bugs/HowToFilter > Because I know it: > > Brian, > > refering to > > https://launchpad.net/ubuntu-release-upgrader > > you are the most active developer on ubuntu-release-upgrader. Would it > be o.K to you when I triage arround on this? Yes, it would be okay, however because there is not much documentation regarding triaging ubuntu-release-upgrader bug reports and it can be a complicated process (I'm still learning myself) - I would prefer that we spent some time triaging bugs together in the ubuntu-bugs IRC channel. I'm available weekdays from 1500 UTC to 2359 UTC. Let me know when works for you and I'll be happy to meet you there. Anyone else is welcome to join us! Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From brian at ubuntu.com Fri May 17 16:50:20 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 17 May 2013 09:50:20 -0700 Subject: segfault at b ip b76662c9 sp 9e8f8da0 error 4 in slapd[b7610000+12f000] In-Reply-To: References: Message-ID: <20130517165020.GF2977@murraytwins.com> On Thu, May 16, 2013 at 08:27:59PM -0500, Francois Gnu wrote: > Hello masters, > > > I have that in my /var/log/syslog: > > slapd[1814]: segfault at b ip b76662c9 sp 9e8f8da0 error 4 in > slapd[b7610000+12f000] > > and the service slapd stop. > > uname -a > Linux 3.2.0-43-generic-pae #68-Ubuntu SMP Wed May 15 03:55:10 UTC 2013 i686 > i686 i386 GNU/Linux > > > It's a bug? Yes, any crash like that is a bug. It'd be best to open a bug report on Launchpad about 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 brian at ubuntu.com Mon May 20 19:54:20 2013 From: brian at ubuntu.com (Brian Murray) Date: Mon, 20 May 2013 12:54:20 -0700 Subject: firefox-lp-improvements In-Reply-To: <20130513161314.GR2977@murraytwins.com> References: <20130513161314.GR2977@murraytwins.com> Message-ID: <20130520195420.GO2977@murraytwins.com> On Mon, May 13, 2013 at 09:13:15AM -0700, Brian Murray wrote: > On Mon, May 13, 2013 at 01:36:41AM -0700, Benjamin Kerensa wrote: > > So as many of you are probably aware the firefox-lp-improvements > > add-on has stopped working and I have talked to Brian Murray about it > > and apparently we have hit a roadblock on trying to fix it. Is there > > anyone who might be able to fix it on the mailing list? Perhaps > > someone familiar with making Firefox Add-Ons. > > To be clear, the whole add-on has not stopped working rather the > functionality of reloading the standard responses and tags to add has > stopped working. Additionally, the greasemonkey scripts, of which the > Firefox add-on is a compilation, continues to work. > > > Here is the PPA https://launchpad.net/~gm-dev-launchpad/+archive/ppa > > and source package > > https://launchpad.net/~gm-dev-launchpad/+archive/ppa/+files/firefox-lp-improvements_0.99.93-0ubuntu1%7Eppa1.tar.gz > > I looked at this a bit more just now and as I've already mentioned the > issue is with loading the bug tags or standard responses. (It is still > possible to tag the bugs using the add-on.) You can view the specific > code that does this here: > > http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/view/head:/lp_buttontags.user.js#L76 > > Using the error console, accessible in the Tools menu under Web > Developer, in Firefox I see a message regarding 'syntax > error' and 'undefined'. That wasn't very helpful to me at least. One other idea that occurred to me to fix this issue would be to stop loading the standard replies and bug tags from xml files and putting them back in the scripts themselves. I looked at this briefly and if someone were to work on this they would want to start with the tagging script, lp_button_tags.user.js. In rev 92 of launchpad-gm-scripts[1] you can see how it used to work but I don't think it is as simple as just using that version, I believe there were additional changes to the tagging script since it was switched to loading the tags from an xml file. [1] http://bazaar.launchpad.net/~gm-dev-launchpad/launchpad-gm-scripts/master/files/92 -- 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 brian at ubuntu.com Fri May 24 17:55:22 2013 From: brian at ubuntu.com (Brian Murray) Date: Fri, 24 May 2013 10:55:22 -0700 Subject: Stable Release Update verification Message-ID: <20130524175521.GO2977@murraytwins.com> I've just written a blog post regarding how to participate in the Stable Release Update verification process, this is testing of packages in the -proposed repository so that they can be released to -updates and all Ubuntu users. http://www.murraytwins.com/blog/?p=126 I even left the example bug unverified for someone to do - it's really quite easy! Let's help get these fixed bugs out to all Ubuntu users. Thanks, -- Brian Murray -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From webmaster at ubuntu.com Mon May 27 22:35:26 2013 From: webmaster at ubuntu.com (Help Ubuntu) Date: Mon, 27 May 2013 22:35:26 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_penalvch?= Message-ID: <20130527223526.619.68905@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=231&rev2=232 Comment: High majority of original reports do not keep BIOS updated, or test newest mainline kernel released. Ex. LP# 1101883 Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. Here are a few guiding principles that lead to success in getting bugs fixed: <
><
> - Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). + Before filing any hardware related reports on Launchpad, please '''update''' your BIOS, and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). If your vendor has a newer version of the BIOS on their website, and you have not updated to this, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> 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. 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. + <
><
> + For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, your report is considered [[https://wiki.ubuntu.com/Bugs/Status|Status Incomplete]] whether or not someone toggled the Status of your report. <
><
> Please '''do not solicit non-original reporters to post comments, attachments, etc.''' <
><
> @@ -300, +302 @@ === Linux package bugs === - If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not add attachments to a bug report unless specifically asked of you by a developer or triager. Adding undesired attachments when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via a terminal: + If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not add attachments, to a bug report unless specifically asked of you by a developer or triager. Adding undesired attachments when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via a terminal: {{{ ubuntu-bug linux }}}