From noreply at ubuntu.com Mon Apr 1 14:59:25 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 01 Apr 2013 14:59:25 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130401145925.27841.25860@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=76&rev2=77 8. Check via the command <
> {{{$ file ~/printout}}} <
> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package. 9. Attach the original file of your application and the ~/printout file to your bug report. + = USB printer does not print or prints garbage = + + There are some USB printers who do not work when the standard communication through the USB is applied. For these exception rules need to get implemented in the USB backend of CUPS. + + If your printer is connected via USB try the following steps to find out whether such exception rules could solve your problem: + + 1. Does your printer also allow to be connected via network? Or does your router have a USB port which can be used to make a network printer out of a USB printer? Try out these connection methods. If your printer works with them, continue with the following steps. Continue also with the following steps if you do not have possibilities to use your printer as a network printer. Otherwise, your printer has a problem which does not fall into this class. + + 2. Make sure your printer is connected via USB again. Run the following command in a terminal window <
> {{{$ cancel -a}}} <
> {{{$ lpadmin -p -o usb-unidir-default=true}}} <
> with being the print queue name of the printer with problems. Now your computer does purely uni-directional USB communication with your printer. Does printing work correctly now? Run <
> {{{$ lpadmin -p -R usb-unidir-default}}} <
> to remove this change. + + 3. Run <
> {{{$ cancel -a}}} <
> {{{$ lpadmin -p -o usb-no-reattach-default=true}}} <
to make the USB backend not re-attach the usblp kernel module after the communication with the printer. Does printing work correctly for you now? Undo this change via <
> {{{$ lpadmin -p -R usb-no-reattach-default}}}. + + Please report a bug on the package "cups", preferably by running the command <
> {{{$ ubuntu-bug cups]]] <
>, reporting your results of the tests above and pasting in the output of the <
> {{{$ lsusb}}} <
command. + = Problems installing the CUPS package = Most problems of installing the CUPS package are due to the CUPS daemon not starting after the installation or update of the package and this often happens when something is not OK with the configuration settings in '''/etc/cups/cupsd.conf'''. From noreply at ubuntu.com Mon Apr 1 15:05:53 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 01 Apr 2013 15:05:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130401150553.1457.94544@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=78&rev2=79 3. Run <
> {{{$ cancel -a}}} <
> {{{$ lpadmin -p -o usb-no-reattach-default=true}}} <
> to make the USB backend not re-attach the usblp kernel module after the communication with the printer. Does printing work correctly for you now? Undo this change via <
> {{{$ lpadmin -p -R usb-no-reattach-default}}} - Please report a bug on the package "cups", preferably by running the command <
> {{{$ ubuntu-bug cups}}} <
>, reporting your results of the tests above and pasting in the output of the <
> {{{$ lsusb}}} <
command. + Please report a bug on the package "cups", preferably by running the command <
> {{{$ ubuntu-bug cups}}} <
> Report your results of the tests above and paste in the output of the <
> {{{$ lsusb}}} <
> command. = Problems installing the CUPS package = From noreply at ubuntu.com Fri Apr 5 15:54:05 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 05 Apr 2013 15:54:05 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130405155405.28470.88250@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=79&rev2=80 8. Check via the command <
> {{{$ file ~/printout}}} <
> what format the file is. It is usually PDF or PostScript. Display the file on the screen to see whether the problem already occurs (error message, missing characters, wrong colors, ...). If you see the problem already, the application is the culprit, assign your bug report to the application's package, otherwise assign it to the "cups" package. 9. Attach the original file of your application and the ~/printout file to your bug report. + = Getting the data which would go to the printer = + + Another important piece of data for debugging printing problems is the data which is supposed to be sent to the printer. In the previous section we captured what the application has sent to CUPS. CUPS applies several filters to this data to convert it into the prionter's native language. This result of the filter work we capture here. + + 1. Activate printing into a file by adding a line containing "FileDevice yes" to /etc/cups/cups-files.conf and restarting CUPS by the command <
> {{{$ sudo restart cups}}} + 2. Clone the queue of the printer with problems. The clone should print into a file and not to the actual printer, but the driver should the same, so that the same filters get applied. Use the command: <
> {{{$ lpadmin -p test -E -v file:/tmp/printout -P /etc/cups/ppd/.ppd}}} <
>Replace "" by the name of the queue with the problem. The clone has also exactly the same default settings as the original queue. + 3. Print the job which failed to the new print queue "test". If you have selected options in the print dialog, use the same options as you used when you encountered the problem. Wait until the job finishes (disappears in the job viewer). You will have a non-empty file named /tmp/printout then. Copy this file to your home directory: <
> {{{$ sudo cp /tmp/printout ~}}} <
> {{{$ sudo chmod 777 ~/printout}}} + 4. Attach this file to your bug report and/or examine it. + = USB printer does not print or prints garbage = There are some USB printers who do not work when the standard communication through the USB is applied. For these exception rules need to get implemented in the USB backend of CUPS. From es20490446e at gmail.com Mon Apr 8 16:20:27 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 08 Apr 2013 18:20:27 +0200 Subject: Application for joining Ubuntu BugControl In-Reply-To: <514BE394.5040708@gmail.com> References: <50EB5BFE.7060704@gmail.com> <2061598.D0So4SbAHO@xango3> <514BE394.5040708@gmail.com> Message-ID: <5162EE4B.2000106@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 marconifabio at hotmail.it Mon Apr 8 16:34:14 2013 From: marconifabio at hotmail.it (Fabio Marconi) Date: Mon, 8 Apr 2013 18:34:14 +0200 Subject: Application for joining Ubuntu BugControl In-Reply-To: <5162EE4B.2000106@gmail.com> References: <50EB5BFE.7060704@gmail.com> <2061598.D0So4SbAHO@xango3> <514BE394.5040708@gmail.com> <5162EE4B.2000106@gmail.com> Message-ID: On 08/04/2013 18:20, Alberto Salvia Novella wrote: > El 22/03/13 05:52, Alberto Salvia Novella escribió: >> Here is my application: >> >> 1. Do you promise to be polite to bug reporters even if they are rude >> to you or Ubuntu? Have you signed the Ubuntu Code of Conduct? >> >> Yes, I promise: I signed Ubuntu Code of Conduct years ago, and >> read it recently. >> >> 2. Have you read Bugs/HowToTriage >> , Bugs/Assignment >> , Bugs/Status >> and Bugs/Importance >> ? Do you have any questions >> about that documentation? >> >> I have been an active member of Launchpad since 2007 and, since >> then, the only operating system I have used in my computers has >> been Ubuntu. In this period I read these wiki-pages many times, >> and from start to end before writing this application. >> >> 3. What sensitive data should you look for in a private Apport crash >> report bug before making it public? See Bugs/HowToTriage >> for more information. >> >> - I should look for "CoreDump.gz" and remove it if the stack >> trace provides enough details. >> >> - I should check into "Stacktrace.txt" and "ThreadStacktrace.txt" >> for any sensitive information like passwords, bank account >> numbers, CSS keys, user names or server names. >> >> 4. Is there a particular package or group of packages that you are >> interested in helping out with? >> >> There isn't. My objective is Ubuntu to be perceived stable as a >> hole, by working on bugs that are more obvious and making them to >> be triaged as fast as possible. >> >> 5. Please list five or more bug reports which you have triaged and >> include an explanation of your decisions. Please note that these bugs >> should be representative of your very best work and they should >> demonstrate your understanding of the triage process and how to >> properly handle bugs. For *all* the bugs in the list, please indicate >> what importance you would give it *and* explain the reasoning. >> /Please use urls in your list of bugs./ >> >> Bandwidth limit is not correctly enforced: Transmission delays >> are inserted between data chunk writes (of arbitrary sizes) >> >> - I change the hole bug description to be as clear as possible. >> Also the original one didn't have proper steps to reproduce it. >> - I deeply investigated the origin of the bug and how to >> workaround it. I provided the tools to test it by the users >> themselves. >> - I would give it an importance of "high", since it has a >> moderate impact on a large portion of Ubuntu users. >> >> Misinformation when intending to download the 64-bit edition >> >> - I completely rewrote the hole bug, since it didn't reflect the >> scope of the hole long discussion hold. >> - I would give it an importance of "low", since it's usability >> issue that does not limit the functionality of Ubuntu but rather >> creates a probable non-ideal configurations scenario. >> >> Unable to upgrade "commercial/binary-i386/Packages" >> >> >> - I change the hole bug description to be as clear as possible. >> - I asked the user to add the missing log files as separate >> attachments, in order to have them automatically available. Also >> marked the bug as incomplete. >> - Also asked to gather information using apport, since it was missed. >> - I would give it an importance of "low", since the program >> itself suggest the origin of the problem is a misconfiguration. >> >> upgrade issues 12.04=>12.10 >> >> - I transformed this but to a question, since the user made a >> cross-dependency issue himself by using an experimental ppa for >> xorg. So it wasn't a bug but a support request. >> - Since it is not longer a bug, its importance cannot be set. >> However is would give it an importance of "low", since it's hoped >> the user to be the only one affected. >> >> When selected partition is not focused, it becomes invisible >> >> - I attached an screen-cast which clearly showed the problem, but >> now I think screen-casts are useless when the bug description is >> clear. >> - I would give it an importance of "low", since it's an usability >> issue that does not limit the functionality of the application. >> - I assigned the bug to the "Paper Cuts Ninja" project, since of >> its low importance in a application provided in the default >> installation. >> >> Or have a look at any other bug from the bunch I have here >> , although they aren't the >> most impressive in the world. But happy birthday to me: I recently >> got my twenty-fives and also got at the same time my hundred bugs >> worked in. And if you notice any errata in this application there >> will be no problem in asking me to improve it. >> >> Regards, >> Alberto Salvia Novella (es20490446e) >> >> >> >> El 08/01/13 15:10, C de-Avillez escribió: >>> On Tuesday, January 08, 2013 00:36:30 Alberto Salvia Novella wrote: >>>> Please, accept me to join Ubuntu BugSquad and BugControl in Launchpad >>>> and I will show you what Raring is going to be. If you need more info >>>> about me and how familiar I am with the triaging process, you can have a >>>> look at my profile in Launchpad . >>> My fault there regarding the Ubuntu-BugSquad. I have added you in (and >>> processed all other pending requests). >>> >>> For Ubuntu BugControl the process is different. You must show you understand >>> how we use status and importance, and you must show bugs you triaged. This >>> process is explained in [1]. >>> >>> Cheers, >>> >>> ..C.. >>> >>> >>> [1] https://wiki.ubuntu.com/UbuntuBugControl >>> >>> >> > So? > > And mine ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Tue Apr 9 09:41:47 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 09 Apr 2013 09:41:47 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130409094147.5226.19543@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=80&rev2=81 3. Print the job which failed to the new print queue "test". If you have selected options in the print dialog, use the same options as you used when you encountered the problem. Wait until the job finishes (disappears in the job viewer). You will have a non-empty file named /tmp/printout then. Copy this file to your home directory: <
> {{{$ sudo cp /tmp/printout ~}}} <
> {{{$ sudo chmod 777 ~/printout}}} 4. Attach this file to your bug report and/or examine it. + = Sending a file to the printer unfiltered = + + If you print a file from an application or to + + = PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu = + + Unfortunately, the PostScript (or PDF) interpreters in many printers have bugs, letting them print garbage or nothing at all, or even crash/get stuck when receiving a valid PostScript (or PDF) file. + + If you have a PostScript or PDF printer and it does not print correctly from Ubuntu, please report a bug and proceed as follows, telling all your results in your bug report and staying tuned for further instructions of the developers: + + 1. Tell us the exact Ubuntu version which you are using. + 2. Tell us the exact printer model. + 3. Attach the input file which you tried to print and tell us with which application you tried to print it. + 4. Attach the data which CUPS receives from the application (section "Capturing print job data" on this page). + 5. Attach the data which the printer receives (section "Getting the data which would go to the printer" on this page) + 6. Examine the file obtained in the previous step by running the command <
> {{{$ file printout}}} <
> If it is PostScript or PDF, subscribe "cliddell" (Chris Liddell, Ghostscript upstream developer) to the bug report and also try to display the file on the screen with "evince" and "gs". + 7. + = USB printer does not print or prints garbage = There are some USB printers who do not work when the standard communication through the USB is applied. For these exception rules need to get implemented in the USB backend of CUPS. From noreply at ubuntu.com Tue Apr 9 09:59:39 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 09 Apr 2013 09:59:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130409095939.5312.64748@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=81&rev2=82 = Sending a file to the printer unfiltered = - If you print a file from an application or to + If you print a file from an application or via the "lp" or "lpr" commands, the data usually goes through several filters to convert it into a format which the printer understands and to apply page management options, like 2 pages per sheet, only page 1, 3, and 9, ... to it. For debugging it can be useful to bypass all these filters and let the data go directly to the printer, without any changes or conversions. + + Do not send arbitrary files unfiltered to the printer now hoping that will solve any problems. Please use this mainly if you are asked for doing so in bug reports or after asking a support question. + + In most cases you will have to print the data obtained from the section "Getting the data which would go to the printer" this way, often after editing it. + + 1. Independent how your printer is connected, you can print unfiltered by using the "lp" or "lpr" commands with the "-oraw" argument: <
> {{{$ lp -d -oraw }}} <
> {{{$ lpr -P -oraw }}} <
> Replace by the name of your print queue and by the name of the file you want to print. This does not work around bugs in CUPS backends (the modules which CUPS uses to communicate with printer hardware), see the next steps for such cases. + 2. If the printer id connected via USB or parallel port, you can send the job directly to the printer's device file: <
> {{{$ sudo -s}}} <
> {{{# cat file > /dev/lp0}}} <
> {{{# cat file > /dev/usb/lp0}}} <
> {{{# cat file > /dev/usb/lp1}}} <
> {{{# exit}}} <
> The numbers in the device file names can vary. + 3. If the printer is connected via the network (both ethernet or WLAN), you can use = PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu = From noreply at ubuntu.com Tue Apr 9 11:07:56 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 09 Apr 2013 11:07:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130409110756.23892.42963@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=82&rev2=83 In most cases you will have to print the data obtained from the section "Getting the data which would go to the printer" this way, often after editing it. 1. Independent how your printer is connected, you can print unfiltered by using the "lp" or "lpr" commands with the "-oraw" argument: <
> {{{$ lp -d -oraw }}} <
> {{{$ lpr -P -oraw }}} <
> Replace by the name of your print queue and by the name of the file you want to print. This does not work around bugs in CUPS backends (the modules which CUPS uses to communicate with printer hardware), see the next steps for such cases. - 2. If the printer id connected via USB or parallel port, you can send the job directly to the printer's device file: <
> {{{$ sudo -s}}} <
> {{{# cat file > /dev/lp0}}} <
> {{{# cat file > /dev/usb/lp0}}} <
> {{{# cat file > /dev/usb/lp1}}} <
> {{{# exit}}} <
> The numbers in the device file names can vary. + 2. If the printer id connected via USB or parallel port, you can send the job directly to the printer's device file: <
> {{{$ sudo -s}}} <
> {{{# cat file > /dev/lp0}}} <
> {{{# cat file > /dev/usb/lp0}}} <
> {{{# cat file > /dev/usb/lp1}}} <
> {{{# exit}}} <
> The numbers in the device file names can vary (sse also sections "USB Printer" and "Parallel printer" above). - 3. If the printer is connected via the network (both ethernet or WLAN), you can use + 3. If the printer is connected via the network (both ethernet or WLAN), you can use "nc" ("netcat", part of the netcat-openbsd and netcat-traditional packages, install one of them if needed) to send unfiltered data: <
>{{{$ nc -w1 9100 < }}}<
> Replace by the host name or IP address of your printer and by the name of the file you want to send. If the printer refuses the job, check in the printer's web configuration interface whether JetDirect/AppSocket/9100 printing is enabled (see also the section "Network printer" above. = PostScript (PDF) printer chokes on the PostScript (PDF) coming from Ubuntu = From noreply at ubuntu.com Tue Apr 9 11:37:28 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 09 Apr 2013 11:37:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?till-kamppeter?= Message-ID: <20130409113728.7493.37962@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingPrintingProblems" page has been changed by till-kamppeter: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=85&rev2=86 3. Attach the input file which you tried to print and tell us with which application you tried to print it. 4. Attach the data which CUPS receives from the application (section "Capturing print job data" on this page). 5. Attach the data which the printer receives (section "Getting the data which would go to the printer" on this page) + 6. Examine the file obtained in the previous step by running the command <
> {{{$ file printout}}} <
> - 6. Examine the file obtained in the previous step by running the command <
> {{{$ file printout}}} <
> If it is PostScript or PDF, subscribe "cliddell" (Chris Liddell, Ghostscript upstream developer) to the bug report and also try to display the file on the screen with "evince" and "gs". + 7. If the file is PostScript or PDF, subscribe "cliddell" (Chris Liddell, Ghostscript upstream developer) to the bug report and also try to display the file on the screen with "evince" and "gs". - 7. + 8. Send the file unfiltered to the printer (as described in the section "Sending a file to the printer unfiltered". You should get the same problem, if you get a different (correct or incorrect) result, there is a problem with the CUPS backend (program which CUPS uses to communicate with the printer hardware). + 9. If the file is PostScript, try to send uncompressed PostScript. To do so print the file obtained in step (4) with one of the commands <
> {{{$lpr -P -o psdebug }}} <
> {{{$ lp -d -o psdebug }}} <
> Repeat the steps (5) - (8) printing this way. See also the file /usr/share/doc/cups-filters/README.gz, section "POSTSCRIPT PRINTING DEBUG MODE". + 10. As a workaround for the time being you can switch to an alternative program for generating the PostScript which is sent to the printer. Run <
> {{{$ lpadmin -p -o pdftops-renderer-default=pdftops}}} <
> to switch over and <
> {{{$ lpadmin -p -R pdftops-renderer-default}}} <
> to switch back. Make sure that you switch back if you follow further instructions from the developers in your bug report, or create a separate print queue for the workaround. See also the file /usr/share/doc/cups-filters/README.gz, section "POSTSCRIPT PRINTING RENDERER AND RESOLUTION SELECTION". = USB printer does not print or prints garbage = From es20490446e at gmail.com Wed Apr 10 14:17:20 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Wed, 10 Apr 2013 16:17:20 +0200 Subject: Where to find proper bugs Message-ID: <51657470.9030909@gmail.com> Dear BugSquad, I'm looking to apply for Ubuntu BugControl, but most bugs from the hundred I worked on seem too easy to consider me proficient on managing them. Do you know how I could find bugs where I will be able to clearly demonstrate I'm capable of doing it properly? because I'm finding discovering proper bugs somehow much harder for me than actually triaging them. Thank you, Logo/Alberto Salvia Novella/ -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Rasterizado.png Type: image/png Size: 79386 bytes Desc: not available 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 chilicuil at ubuntu.com Wed Apr 10 22:38:14 2013 From: chilicuil at ubuntu.com (Javier P.L.) Date: Wed, 10 Apr 2013 17:38:14 -0500 Subject: Where to find proper bugs In-Reply-To: <51657470.9030909@gmail.com> References: <51657470.9030909@gmail.com> Message-ID: <20130410223812.GC18387@sup.lan> On 10/04/13 at 04:17pm, Alberto Salvia Novella wrote: > Dear BugSquad, > > I'm looking to apply for Ubuntu BugControl, but most bugs from the > hundred I worked on seem too easy to consider me proficient on > managing them. Do you know how I could find bugs where I will be > able to clearly demonstrate I'm capable of doing it properly? > because I'm finding discovering proper bugs somehow much harder for > me than actually triaging them. > > Thank you, > > > Logo/Alberto Salvia Novella/ Hello, Whenever I want do triaging I look at these lists: http://tinyurl.com/5uxg9a Bugs with no package assigned http://tinyurl.com/ydwayom New bugs http://tinyurl.com/c7wok2e New security bugs http://feeds.launchpad.net/ubuntu/latest-bugs.atom latests bugs Or you could adopt a package you feel comfortable with and triage those bugs as soon as they get reported > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad From robert.park at canonical.com Thu Apr 11 01:19:26 2013 From: robert.park at canonical.com (Robert Bruce Park) Date: Wed, 10 Apr 2013 18:19:26 -0700 Subject: Where to find proper bugs In-Reply-To: <20130410223812.GC18387@sup.lan> References: <51657470.9030909@gmail.com> <20130410223812.GC18387@sup.lan> Message-ID: <20130411011925.GG24645@rouge> On Wed, Apr 10, 2013 at 05:38:14PM -0500, Javier P.L. wrote: > Whenever I want do triaging I look at these lists: > > http://tinyurl.com/5uxg9a Bugs with no package assigned > http://tinyurl.com/ydwayom New bugs > http://tinyurl.com/c7wok2e New security bugs Those are really good links, thanks! I have just bookmarked them. Here's another really good one to keep an eye on: http://tinyurl.com/bqqgc9b That link shows NEW *or* CONFIRMED bugs (remember, 'confirmed' just means that more than one person is affected; it still needs triaging), sorted by oldest first, because it's kind of embarrassing how old some of these untriaged bugs are... Come on, guys! Only 97,706 untriaged bugs left to go! We can do it! ;-) From matthew.fischer at canonical.com Thu Apr 11 03:41:11 2013 From: matthew.fischer at canonical.com (Matt Fischer) Date: Wed, 10 Apr 2013 21:41:11 -0600 Subject: Where to find proper bugs In-Reply-To: <20130411011925.GG24645@rouge> References: <51657470.9030909@gmail.com> <20130410223812.GC18387@sup.lan> <20130411011925.GG24645@rouge> Message-ID: <516630D7.4020807@canonical.com> On 04/10/2013 07:19 PM, Robert Bruce Park wrote: > On Wed, Apr 10, 2013 at 05:38:14PM -0500, Javier P.L. wrote: >> Whenever I want do triaging I look at these lists: >> >> http://tinyurl.com/5uxg9a Bugs with no package assigned >> http://tinyurl.com/ydwayom New bugs >> http://tinyurl.com/c7wok2e New security bugs > Those are really good links, thanks! I have just bookmarked them. > > Here's another really good one to keep an eye on: > > http://tinyurl.com/bqqgc9b > > That link shows NEW *or* CONFIRMED bugs (remember, 'confirmed' just > means that more than one person is affected; it still needs triaging), > sorted by oldest first, because it's kind of embarrassing how old some > of these untriaged bugs are... > > Come on, guys! Only 97,706 untriaged bugs left to go! We can do it! ;-) > Sometimes I find that the new/no-package bugs are not so easy to isolate to a package, so when I really want to make progress and try to get that number down below 97700, I take a slightly different approach. Maybe you can consider this option too: I pick packages that I am familiar with, use a lot, or have an interest in. I try to clean up the new bug list first, confirming, duping, and triaging if possible. After a few passes through the list you can usually make a dent in dupes and unconfirmed bugs. I'll then spend some time on older bugs, seeing if they've been fixed upstream or need more info. Good luck! -- Matthew (Matt) Fischer LP: http://launchpad.net/~mfisch IRC: mfisch From brian at ubuntu.com Thu Apr 11 20:07:46 2013 From: brian at ubuntu.com (Brian Murray) Date: Thu, 11 Apr 2013 13:07:46 -0700 Subject: Where to find proper bugs In-Reply-To: <51657470.9030909@gmail.com> References: <51657470.9030909@gmail.com> Message-ID: <20130411200746.GC29575@murraytwins.com> On Wed, Apr 10, 2013 at 04:17:20PM +0200, Alberto Salvia Novella wrote: > Dear BugSquad, > > I'm looking to apply for Ubuntu BugControl, but most bugs from the > hundred I worked on seem too easy to consider me proficient on > managing them. Do you know how I could find bugs where I will be > able to clearly demonstrate I'm capable of doing it properly? > because I'm finding discovering proper bugs somehow much harder for > me than actually triaging them. In my experience bugs that have more details are more likely to be successfully triaged and bugs reported via apport have lots of system information added to them. Additionally, apport automatically tags bug reports when they are reported some of these tags include apport-bug, apport-package, and apport-crash. Subsequently, I would either search for bugs with this tag or customize Launchpad's bug listing to show tags. Thanks and good luck! -- Brian Murray Ubuntu Bug Master From okg853 at lavabit.com Tue Apr 16 11:31:50 2013 From: okg853 at lavabit.com (okg853 at lavabit.com) Date: Tue, 16 Apr 2013 07:31:50 -0400 (EDT) Subject: Ubuntu 13.04 // Lenovo B590 MBX29GE/627429G // WLAN and ACPI Issues/Bugs!? Message-ID: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> Dear community, I've got the notebook mentioned above. I've installed Ubuntu 13.04 (latest updates, kernel 3.8.0-18) on this machine and got several issues: 1.) The most anyoing one (Broadcom BMC 43142): I can't work on console due to the spamming of the following message all two seconds: ERROR @wl_cfg80211_get_station : Could not get rssi (-1) ERROR @wl_cfg80211_get_station : Could not get rate (-1) I don't know if it's a known bug in this combination. The issue is common known on other hardware configs. dmesg | grep broadcom [ 2.170370] usb 1-1.4: Manufacturer: Broadcom Corp [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.20.155.1 (r326264) --> Wrong Chip WLAN is working ... But not in fullspeed and the datarate is a bit weak/random. lspci -nvv 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) Subsystem: Broadcom Corporation Device [14e4:0608] Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at f0500000 (64-bit, non-prefetchable) [size=16K] Capabilities: [40] Power Management version 3 Capabilities: [58] Vendor Specific Information: Len=78 Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [d0] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [13c] Virtual Channel Capabilities: [160] Device Serial Number 00-00-3d-ff-ff-de-c0-14 Capabilities: [16c] Power Budgeting Kernel driver in use: wl 2. Several ACPI errors (parts of dmesg): [ 0.134252] ACPI: bus type pci registered [ 0.134310] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) [ 0.134312] PCI: not using MMCONFIG [ 0.134313] PCI: Using configuration type 1 for base access [ 0.135048] bio: create slab at 0 [ 0.135116] ACPI: Added _OSI(Module Device) [ 0.135118] ACPI: Added _OSI(Processor Device) [ 0.135119] ACPI: Added _OSI(3.0 _SCP Extensions) [ 0.135122] ACPI: Added _OSI(Processor Aggregator Device) [ 0.136797] ACPI: EC: Look up EC in DSDT [ 0.136929] ACPI Error: No handler for Region [ECOR] (ffff88021285acf0) [EmbeddedControl] (20121018/evregion-376) [ 0.136933] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20121018/exfldio-305) [ 0.136936] ACPI Error: Method parse/execution failed [\_SB_.PCI0.LPCB.H_EC._REG] (Node ffff880212868d48), AE_NOT_EXIST (20121018/psparse-537) [ 0.138135] ACPI: Executed 1 blocks of module-level executable AML code [ 0.142156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 0.142812] ACPI: SSDT 00000000dae3e018 0083B (v01 PmRef Cpu0Cst 00003001 INTL 20061109) [ 0.143236] ACPI: Dynamic OEM Table Load: [ 0.143237] ACPI: SSDT (null) 0083B (v01 PmRef Cpu0Cst 00003001 INTL 20061109) [ 0.143493] ACPI: SSDT 00000000dae3fa98 00303 (v01 PmRef ApIst 00003000 INTL 20061109) [ 0.143941] ACPI: Dynamic OEM Table Load: [ 0.143943] ACPI: SSDT (null) 00303 (v01 PmRef ApIst 00003000 INTL 20061109) [ 0.144063] ACPI: SSDT 00000000dae3dd98 00119 (v01 PmRef ApCst 00003000 INTL 20061109) [ 0.144483] ACPI: Dynamic OEM Table Load: [ 0.144485] ACPI: SSDT (null) 00119 (v01 PmRef ApCst 00003000 INTL 20061109) [ 0.561205] ACPI: Interpreter enabled [ 0.561208] ACPI: (supports S0 S3 S4 S5) [ 0.561229] ACPI: Using IOAPIC for interrupt routing [ 0.561248] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem 0xf8000000-0xfbffffff] (base 0xf8000000) [ 0.561757] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in ACPI motherboard resources [ 0.571926] ACPI: Power Resource [PUBS] (off) [ 0.577232] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62 [ 0.577364] ACPI: No dock devices found. [ 0.577367] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [ 0.577478] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) [ 0.577480] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ 0.577613] \_SB_.PCI0:_OSC invalid UUID [ 0.577614] _OSC request data:1 8 1f [ 0.577655] \_SB_.PCI0:_OSC invalid UUID [ 0.577656] _OSC request data:1 1f 1f [ 0.577659] pci_root PNP0A08:00: ACPI _OSC support notification failed, disabling PCIe ASPM [ 0.577661] pci_root PNP0A08:00: Unable to request _OSC control (_OSC support mask: 0x08) [ 1.099434] efifb: mode is 1366x768x32, linelength=5504, pages=1 [ 1.099435] efifb: scrolling: redraw [ 1.099437] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 1.102464] Console: switching to colour frame buffer device 170x48 [ 1.105323] fb0: EFI VGA frame buffer device [ 1.105327] intel_idle: MWAIT substates: 0x21120 [ 1.105328] intel_idle: v0.4 model 0x3A [ 1.105329] intel_idle: lapic_timer_reliable_states 0xffffffff [ 1.105522] ACPI: AC Adapter [ADP1] (on-line) [ 1.105619] input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 [ 1.105762] ACPI: Lid Switch [LID0] [ 1.105796] input: Sleep Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 [ 1.105799] ACPI: Sleep Button [SLPB] [ 1.105823] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [ 1.105825] ACPI: Power Button [PWRF] [ 1.105896] ACPI: Requesting acpi_cpufreq [ 1.109262] ACPI Error: No handler for Region [ECRM] (ffff880212b7d5e8) [EmbeddedControl] (20121018/evregion-376) [ 1.109266] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20121018/exfldio-305) [ 1.109269] ACPI Error: Method parse/execution failed [\_TZ_.MDEC] (Node ffff88021286b9b0), AE_NOT_EXIST (20121018/psparse-537) [ 1.109275] ACPI Error: Method parse/execution failed [\_TZ_.TZS0._SCP] (Node ffff88021286ba50), AE_NOT_EXIST (20121018/psparse-537) [ 1.109351] thermal LNXTHERM:00: registered as thermal_zone0 [ 1.109353] ACPI: Thermal Zone [TZS0] (44 C) [ 1.109492] thermal LNXTHERM:01: registered as thermal_zone1 [ 1.109493] ACPI: Thermal Zone [TZS1] (31 C) [ 1.109517] GHES: HEST is not enabled! [ 1.109581] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ 1.110384] ACPI: Battery Slot [BAT0] (battery present) [ 1.110905] Linux agpgart interface v0.103 [ 1.111813] brd: module loaded [ 1.112343] loop: module loaded [ 1.112564] libphy: Fixed MDIO Bus: probed [ 23.044977] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 23.199826] udevd[645]: starting version 175 [ 24.106469] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x12 [ 24.260832] Non-volatile memory driver v1.3 [ 24.279032] ACPI Warning: 0x0000000000000428-0x000000000000042f SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251) [ 24.279040] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 24.279045] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) [ 24.279049] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20121018/utaddress-251) [ 24.279053] ACPI Warning: 0x0000000000000530-0x000000000000053f SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 (20121018/utaddress-251) [ 24.279057] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 24.279059] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) [ 24.279063] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 (20121018/utaddress-251) [ 24.279066] ACPI Warning: 0x0000000000000500-0x000000000000052f SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 (20121018/utaddress-251) [ 24.279070] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 24.279072] lpc_ich: Resource conflict(s) found affecting gpio_ich [ 24.284425] cfg80211: Calling CRDA to update world regulatory domain [ 24.348682] mei 0000:00:16.0: setting latency timer to 64 [ 24.348743] mei 0000:00:16.0: irq 44 for MSI/MSI-X [ 24.370936] Bluetooth: Core ver 2.16 [ 24.370953] NET: Registered protocol family 31 [ 24.370955] Bluetooth: HCI device and connection manager initialized [ 24.370963] Bluetooth: HCI socket layer initialized [ 24.370966] Bluetooth: L2CAP socket layer initialized [ 24.370972] Bluetooth: SCO socket layer initialized [ 24.387322] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X [ 24.487908] lib80211: common routines for IEEE802.11 drivers [ 24.487912] lib80211_crypt: registered algorithm 'NULL' [ 24.509595] cfg80211: World regulatory domain updated: [ 24.509599] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 24.509600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 24.509602] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 24.509603] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm) [ 24.509604] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 24.509606] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) [ 24.761841] Bluetooth: can't load firmware, may not work correctly [ 24.801105] wl: module license 'MIXED/Proprietary' taints kernel. [ 24.810628] thinkpad_acpi: ThinkPad ACPI Extras v0.24 [ 24.810631] thinkpad_acpi: http://ibm-acpi.sf.net/ [ 24.810633] thinkpad_acpi: ThinkPad BIOS H1ET63WW (1.06 ), EC unknown [ 24.810634] thinkpad_acpi: Lenovo Lenovo B590, model 627429G [ 24.811941] thinkpad_acpi: detected a 8-level brightness capable ThinkPad [ 24.811986] thinkpad_acpi: This ThinkPad has standard ACPI backlight brightness control, supported by the ACPI video driver [ 24.811988] thinkpad_acpi: Disabling thinkpad-acpi brightness events by default... [ 24.815661] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [ 24.816095] thinkpad_acpi: Standard ACPI backlight interface available, not loading native one [ 24.816232] thinkpad_acpi: Console audio control enabled, mode: monitor (read only) [ 24.817780] input: ThinkPad Extra Buttons as /devices/platform/thinkpad_acpi/input/input8 [ 24.835558] INFO @wl_cfg80211_attach : Registered CFG80211 phy [ 24.843006] type=1400 audit(1366106007.209:2): apparmor="STATUS" operation="profile_load" name="/sbin/dhclient" pid=849 comm="apparmor_parser" [ 24.843014] type=1400 audit(1366106007.209:3): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=850 comm="apparmor_parser" [ 24.843356] type=1400 audit(1366106007.209:4): apparmor="STATUS" operation="profile_load" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 comm="apparmor_parser" [ 24.843363] type=1400 audit(1366106007.209:5): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=850 comm="apparmor_parser" [ 24.843546] type=1400 audit(1366106007.209:6): apparmor="STATUS" operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" pid=849 comm="apparmor_parser" [ 24.843554] type=1400 audit(1366106007.209:7): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=850 comm="apparmor_parser" [ 24.854831] lib80211_crypt: registered algorithm 'TKIP' [ 24.991554] Linux video capture interface: v2.00 [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller 6.20.155.1 (r326264) [ 25.210570] uvcvideo: Found UVC 1.00 device Integrated Camera (04f2:b2fa) [ 25.211869] input: Integrated Camera as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 [ 25.211942] usbcore: registered new interface driver uvcvideo [ 25.211944] USB Video Class driver (1.1.1) [ 25.316148] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: 0x1e0b1, caps: 0xf00073/0x240000/0xa2400, board id: 2060, fw id: 1040538 [ 25.349946] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input10 [ 26.673431] btrfs: disk space caching is enabled [ 26.802960] device fsid 040341e4-f437-42c5-890b-8639d5046bf1 devid 1 transid 96 /dev/sda4 [ 26.803657] btrfs: disk space caching is enabled [ 27.158579] device fsid 5683cbcc-e616-4535-a393-b7108562cf60 devid 1 transid 962 /dev/mapper/linroot_crypt [ 29.429897] init: failsafe main process (1206) killed by TERM signal [ 30.331389] type=1400 audit(1366106012.705:8): apparmor="STATUS" operation="profile_replace" name="/sbin/dhclient" pid=1281 comm="apparmor_parser" [ 30.331760] type=1400 audit(1366106012.705:9): apparmor="STATUS" operation="profile_replace" name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1281 comm="apparmor_parser" [ 30.331953] type=1400 audit(1366106012.705:10): apparmor="STATUS" operation="profile_replace" name="/usr/lib/connman/scripts/dhclient-script" pid=1281 comm="apparmor_parser" [ 30.382097] type=1400 audit(1366106012.757:11): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" pid=1280 comm="apparmor_parser" [ 30.382367] type=1400 audit(1366106012.757:12): apparmor="STATUS" operation="profile_load" name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" pid=1280 comm="apparmor_parser" [ 30.395833] type=1400 audit(1366106012.769:13): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/mission-control-5" pid=1283 comm="apparmor_parser" [ 30.396254] type=1400 audit(1366106012.769:14): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=1283 comm="apparmor_parser" [ 30.396915] type=1400 audit(1366106012.773:15): apparmor="STATUS" operation="profile_load" name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=1283 comm="apparmor_parser" [ 30.402793] type=1400 audit(1366106012.777:16): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1279 comm="apparmor_parser" [ 30.403059] type=1400 audit(1366106012.777:17): apparmor="STATUS" operation="profile_load" name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" pid=1279 comm="apparmor_parser" [ 30.859995] Bluetooth: RFCOMM TTY layer initialized [ 30.860004] Bluetooth: RFCOMM socket layer initialized [ 30.860005] Bluetooth: RFCOMM ver 1.11 [ 30.893034] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 30.893038] Bluetooth: BNEP filters: protocol multicast [ 30.893046] Bluetooth: BNEP socket layer initialized [ 31.481429] init: avahi-cups-reload main process (1363) terminated with status 1 I hope anyone can help me to identify if it's a bug or not. Kind regards From joseph.salisbury at canonical.com Tue Apr 16 15:54:11 2013 From: joseph.salisbury at canonical.com (Joseph Salisbury) Date: Tue, 16 Apr 2013 11:54:11 -0400 Subject: Ubuntu 13.04 // Lenovo B590 MBX29GE/627429G // WLAN and ACPI Issues/Bugs!? In-Reply-To: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> References: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> Message-ID: <516D7423.4040802@canonical.com> On 04/16/2013 07:31 AM, okg853 at lavabit.com wrote: > Dear community, > > I've got the notebook mentioned above. I've installed Ubuntu 13.04 (latest > updates, kernel 3.8.0-18) on this machine and got several issues: > > > 1.) The most anyoing one (Broadcom BMC 43142): > > I can't work on console due to the spamming of the following message all > two seconds: > > ERROR @wl_cfg80211_get_station : Could not get rssi (-1) > ERROR @wl_cfg80211_get_station : Could not get rate (-1) > > I don't know if it's a known bug in this combination. The issue is common > known on other hardware configs. > > dmesg | grep broadcom > > [ 2.170370] usb 1-1.4: Manufacturer: Broadcom Corp > [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller > 6.20.155.1 (r326264) > > --> Wrong Chip > > WLAN is working ... But not in fullspeed and the datarate is a bit > weak/random. > > > lspci -nvv > > 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 > 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) > Subsystem: Broadcom Corporation Device [14e4:0608] > Flags: bus master, fast devsel, latency 0, IRQ 17 > Memory at f0500000 (64-bit, non-prefetchable) [size=16K] > Capabilities: [40] Power Management version 3 > Capabilities: [58] Vendor Specific Information: Len=78 > Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ > Capabilities: [d0] Express Endpoint, MSI 00 > Capabilities: [100] Advanced Error Reporting > Capabilities: [13c] Virtual Channel > Capabilities: [160] Device Serial Number 00-00-3d-ff-ff-de-c0-14 > Capabilities: [16c] Power Budgeting > Kernel driver in use: wl > > > > 2. Several ACPI errors (parts of dmesg): > > > [ 0.134252] ACPI: bus type pci registered > [ 0.134310] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem > 0xf8000000-0xfbffffff] (base 0xf8000000) > [ 0.134312] PCI: not using MMCONFIG > [ 0.134313] PCI: Using configuration type 1 for base access > [ 0.135048] bio: create slab at 0 > [ 0.135116] ACPI: Added _OSI(Module Device) > [ 0.135118] ACPI: Added _OSI(Processor Device) > [ 0.135119] ACPI: Added _OSI(3.0 _SCP Extensions) > [ 0.135122] ACPI: Added _OSI(Processor Aggregator Device) > [ 0.136797] ACPI: EC: Look up EC in DSDT > [ 0.136929] ACPI Error: No handler for Region [ECOR] (ffff88021285acf0) > [EmbeddedControl] (20121018/evregion-376) > [ 0.136933] ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20121018/exfldio-305) > [ 0.136936] ACPI Error: Method parse/execution failed > [\_SB_.PCI0.LPCB.H_EC._REG] (Node ffff880212868d48), AE_NOT_EXIST > (20121018/psparse-537) > [ 0.138135] ACPI: Executed 1 blocks of module-level executable AML code > [ 0.142156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ > 0.142812] ACPI: SSDT 00000000dae3e018 0083B (v01 PmRef Cpu0Cst 00003001 > INTL 20061109) > [ 0.143236] ACPI: Dynamic OEM Table Load: > [ 0.143237] ACPI: SSDT (null) 0083B (v01 PmRef Cpu0Cst > 00003001 INTL 20061109) > [ 0.143493] ACPI: SSDT 00000000dae3fa98 00303 (v01 PmRef ApIst > 00003000 INTL 20061109) > [ 0.143941] ACPI: Dynamic OEM Table Load: > [ 0.143943] ACPI: SSDT (null) 00303 (v01 PmRef ApIst > 00003000 INTL 20061109) > [ 0.144063] ACPI: SSDT 00000000dae3dd98 00119 (v01 PmRef ApCst > 00003000 INTL 20061109) > [ 0.144483] ACPI: Dynamic OEM Table Load: > [ 0.144485] ACPI: SSDT (null) 00119 (v01 PmRef ApCst > 00003000 INTL 20061109) > [ 0.561205] ACPI: Interpreter enabled > [ 0.561208] ACPI: (supports S0 S3 S4 S5) > [ 0.561229] ACPI: Using IOAPIC for interrupt routing > [ 0.561248] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem > 0xf8000000-0xfbffffff] (base 0xf8000000) > [ 0.561757] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in > ACPI motherboard resources > [ 0.571926] ACPI: Power Resource [PUBS] (off) > [ 0.577232] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62 > [ 0.577364] ACPI: No dock devices found. > [ 0.577367] PCI: Using host bridge windows from ACPI; if necessary, use > "pci=nocrs" and report a bug > [ 0.577478] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) [ > 0.577480] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ > 0.577613] \_SB_.PCI0:_OSC invalid UUID > [ 0.577614] _OSC request data:1 8 1f > [ 0.577655] \_SB_.PCI0:_OSC invalid UUID > [ 0.577656] _OSC request data:1 1f 1f > [ 0.577659] pci_root PNP0A08:00: ACPI _OSC support notification failed, > disabling PCIe ASPM > [ 0.577661] pci_root PNP0A08:00: Unable to request _OSC control (_OSC > support mask: 0x08) > > > [ 1.099434] efifb: mode is 1366x768x32, linelength=5504, pages=1 [ > 1.099435] efifb: scrolling: redraw > [ 1.099437] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 > [ 1.102464] Console: switching to colour frame buffer device 170x48 [ > 1.105323] fb0: EFI VGA frame buffer device > [ 1.105327] intel_idle: MWAIT substates: 0x21120 > [ 1.105328] intel_idle: v0.4 model 0x3A > [ 1.105329] intel_idle: lapic_timer_reliable_states 0xffffffff > [ 1.105522] ACPI: AC Adapter [ADP1] (on-line) > [ 1.105619] input: Lid Switch as > /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 > [ 1.105762] ACPI: Lid Switch [LID0] > [ 1.105796] input: Sleep Button as > /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 > [ 1.105799] ACPI: Sleep Button [SLPB] > [ 1.105823] input: Power Button as > /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 > [ 1.105825] ACPI: Power Button [PWRF] > [ 1.105896] ACPI: Requesting acpi_cpufreq > [ 1.109262] ACPI Error: No handler for Region [ECRM] (ffff880212b7d5e8) > [EmbeddedControl] (20121018/evregion-376) > [ 1.109266] ACPI Error: Region EmbeddedControl (ID=3) has no handler > (20121018/exfldio-305) > [ 1.109269] ACPI Error: Method parse/execution failed [\_TZ_.MDEC] > (Node ffff88021286b9b0), AE_NOT_EXIST (20121018/psparse-537) > [ 1.109275] ACPI Error: Method parse/execution failed [\_TZ_.TZS0._SCP] > (Node ffff88021286ba50), AE_NOT_EXIST (20121018/psparse-537) > [ 1.109351] thermal LNXTHERM:00: registered as thermal_zone0 > [ 1.109353] ACPI: Thermal Zone [TZS0] (44 C) > [ 1.109492] thermal LNXTHERM:01: registered as thermal_zone1 > [ 1.109493] ACPI: Thermal Zone [TZS1] (31 C) > [ 1.109517] GHES: HEST is not enabled! > [ 1.109581] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled [ > 1.110384] ACPI: Battery Slot [BAT0] (battery present) > [ 1.110905] Linux agpgart interface v0.103 > [ 1.111813] brd: module loaded > [ 1.112343] loop: module loaded > [ 1.112564] libphy: Fixed MDIO Bus: probed > > > [ 23.044977] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready > [ 23.199826] udevd[645]: starting version 175 > [ 24.106469] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x12 [ > 24.260832] Non-volatile memory driver v1.3 > [ 24.279032] ACPI Warning: 0x0000000000000428-0x000000000000042f > SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251) > [ 24.279040] ACPI: If an ACPI driver is available for this device, you > should use it instead of the native driver > [ 24.279045] ACPI Warning: 0x0000000000000530-0x000000000000053f > SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) > [ 24.279049] ACPI Warning: 0x0000000000000530-0x000000000000053f > SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 > (20121018/utaddress-251) > [ 24.279053] ACPI Warning: 0x0000000000000530-0x000000000000053f > SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 > (20121018/utaddress-251) > [ 24.279057] ACPI: If an ACPI driver is available for this device, you > should use it instead of the native driver > [ 24.279059] ACPI Warning: 0x0000000000000500-0x000000000000052f > SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) > [ 24.279063] ACPI Warning: 0x0000000000000500-0x000000000000052f > SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 > (20121018/utaddress-251) > [ 24.279066] ACPI Warning: 0x0000000000000500-0x000000000000052f > SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 > (20121018/utaddress-251) > [ 24.279070] ACPI: If an ACPI driver is available for this device, you > should use it instead of the native driver > [ 24.279072] lpc_ich: Resource conflict(s) found affecting gpio_ich [ > 24.284425] cfg80211: Calling CRDA to update world regulatory domain [ > 24.348682] mei 0000:00:16.0: setting latency timer to 64 > [ 24.348743] mei 0000:00:16.0: irq 44 for MSI/MSI-X > [ 24.370936] Bluetooth: Core ver 2.16 > [ 24.370953] NET: Registered protocol family 31 > [ 24.370955] Bluetooth: HCI device and connection manager initialized [ > 24.370963] Bluetooth: HCI socket layer initialized > [ 24.370966] Bluetooth: L2CAP socket layer initialized > [ 24.370972] Bluetooth: SCO socket layer initialized > [ 24.387322] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X > [ 24.487908] lib80211: common routines for IEEE802.11 drivers > [ 24.487912] lib80211_crypt: registered algorithm 'NULL' > [ 24.509595] cfg80211: World regulatory domain updated: > [ 24.509599] cfg80211: (start_freq - end_freq @ bandwidth), > (max_antenna_gain, max_eirp) > [ 24.509600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 > mBi, 2000 mBm) > [ 24.509602] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 > mBi, 2000 mBm) > [ 24.509603] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 > mBi, 2000 mBm) > [ 24.509604] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 > mBi, 2000 mBm) > [ 24.509606] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 > mBi, 2000 mBm) > > > [ 24.761841] Bluetooth: can't load firmware, may not work correctly [ > 24.801105] wl: module license 'MIXED/Proprietary' taints kernel. [ > 24.810628] thinkpad_acpi: ThinkPad ACPI Extras v0.24 > [ 24.810631] thinkpad_acpi: http://ibm-acpi.sf.net/ > [ 24.810633] thinkpad_acpi: ThinkPad BIOS H1ET63WW (1.06 ), EC unknown [ > 24.810634] thinkpad_acpi: Lenovo Lenovo B590, model 627429G > [ 24.811941] thinkpad_acpi: detected a 8-level brightness capable ThinkPad > [ 24.811986] thinkpad_acpi: This ThinkPad has standard ACPI backlight > brightness control, supported by the ACPI video driver > [ 24.811988] thinkpad_acpi: Disabling thinkpad-acpi brightness events by > default... > [ 24.815661] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is > unblocked > [ 24.816095] thinkpad_acpi: Standard ACPI backlight interface available, > not loading native one > [ 24.816232] thinkpad_acpi: Console audio control enabled, mode: monitor > (read only) > [ 24.817780] input: ThinkPad Extra Buttons as > /devices/platform/thinkpad_acpi/input/input8 > [ 24.835558] INFO @wl_cfg80211_attach : Registered CFG80211 phy > [ 24.843006] type=1400 audit(1366106007.209:2): apparmor="STATUS" > operation="profile_load" name="/sbin/dhclient" pid=849 > comm="apparmor_parser" > [ 24.843014] type=1400 audit(1366106007.209:3): apparmor="STATUS" > operation="profile_replace" name="/sbin/dhclient" pid=850 > comm="apparmor_parser" > [ 24.843356] type=1400 audit(1366106007.209:4): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 > comm="apparmor_parser" > [ 24.843363] type=1400 audit(1366106007.209:5): apparmor="STATUS" > operation="profile_replace" > name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=850 > comm="apparmor_parser" > [ 24.843546] type=1400 audit(1366106007.209:6): apparmor="STATUS" > operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" > pid=849 comm="apparmor_parser" > [ 24.843554] type=1400 audit(1366106007.209:7): apparmor="STATUS" > operation="profile_replace" > name="/usr/lib/connman/scripts/dhclient-script" pid=850 > comm="apparmor_parser" > [ 24.854831] lib80211_crypt: registered algorithm 'TKIP' > [ 24.991554] Linux video capture interface: v2.00 > [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller > 6.20.155.1 (r326264) > [ 25.210570] uvcvideo: Found UVC 1.00 device Integrated Camera > (04f2:b2fa) > [ 25.211869] input: Integrated Camera as > /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 [ > 25.211942] usbcore: registered new interface driver uvcvideo > [ 25.211944] USB Video Class driver (1.1.1) > [ 25.316148] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, id: > 0x1e0b1, caps: 0xf00073/0x240000/0xa2400, board id: 2060, fw id: 1040538 [ > 25.349946] input: SynPS/2 Synaptics TouchPad as > /devices/platform/i8042/serio1/input/input10 > [ 26.673431] btrfs: disk space caching is enabled > [ 26.802960] device fsid 040341e4-f437-42c5-890b-8639d5046bf1 devid 1 > transid 96 /dev/sda4 > [ 26.803657] btrfs: disk space caching is enabled > [ 27.158579] device fsid 5683cbcc-e616-4535-a393-b7108562cf60 devid 1 > transid 962 /dev/mapper/linroot_crypt > [ 29.429897] init: failsafe main process (1206) killed by TERM signal [ > 30.331389] type=1400 audit(1366106012.705:8): apparmor="STATUS" > operation="profile_replace" name="/sbin/dhclient" pid=1281 > comm="apparmor_parser" > [ 30.331760] type=1400 audit(1366106012.705:9): apparmor="STATUS" > operation="profile_replace" > name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1281 > comm="apparmor_parser" > [ 30.331953] type=1400 audit(1366106012.705:10): apparmor="STATUS" > operation="profile_replace" > name="/usr/lib/connman/scripts/dhclient-script" pid=1281 > comm="apparmor_parser" > [ 30.382097] type=1400 audit(1366106012.757:11): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" > pid=1280 comm="apparmor_parser" > [ 30.382367] type=1400 audit(1366106012.757:12): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" > pid=1280 comm="apparmor_parser" > [ 30.395833] type=1400 audit(1366106012.769:13): apparmor="STATUS" > operation="profile_load" name="/usr/lib/telepathy/mission-control-5" > pid=1283 comm="apparmor_parser" > [ 30.396254] type=1400 audit(1366106012.769:14): apparmor="STATUS" > operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=1283 > comm="apparmor_parser" > [ 30.396915] type=1400 audit(1366106012.773:15): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=1283 > comm="apparmor_parser" > [ 30.402793] type=1400 audit(1366106012.777:16): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1279 > comm="apparmor_parser" > [ 30.403059] type=1400 audit(1366106012.777:17): apparmor="STATUS" > operation="profile_load" > name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" > pid=1279 comm="apparmor_parser" > [ 30.859995] Bluetooth: RFCOMM TTY layer initialized > [ 30.860004] Bluetooth: RFCOMM socket layer initialized > [ 30.860005] Bluetooth: RFCOMM ver 1.11 > [ 30.893034] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 > [ 30.893038] Bluetooth: BNEP filters: protocol multicast > [ 30.893046] Bluetooth: BNEP socket layer initialized > [ 31.481429] init: avahi-cups-reload main process (1363) terminated with > status 1 > > > I hope anyone can help me to identify if it's a bug or not. > > Kind regards > > > > Please open a bug in Launchpad by running the following from a terminal: ubuntu-bug linux That will allow us to review all your logs, config info, etc. It will also allow others to search for your bug if they are having similar issues. Thanks, Joe From okg853 at lavabit.com Tue Apr 16 17:31:58 2013 From: okg853 at lavabit.com (okg853 at lavabit.com) Date: Tue, 16 Apr 2013 13:31:58 -0400 (EDT) Subject: Ubuntu 13.04 // Lenovo B590 MBX29GE/627429G // WLAN and ACPI Issues/Bugs!? In-Reply-To: <516D7423.4040802@canonical.com> References: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> <516D7423.4040802@canonical.com> Message-ID: <15706.84.150.143.143.1366133518.squirrel@lavabit.com> > On 04/16/2013 07:31 AM, okg853 at lavabit.com wrote: >> Dear community, >> >> I've got the notebook mentioned above. I've installed Ubuntu 13.04 >> (latest >> updates, kernel 3.8.0-18) on this machine and got several issues: >> >> >> 1.) The most anyoing one (Broadcom BMC 43142): >> >> I can't work on console due to the spamming of the following message all >> two seconds: >> >> ERROR @wl_cfg80211_get_station : Could not get rssi (-1) >> ERROR @wl_cfg80211_get_station : Could not get rate (-1) >> >> I don't know if it's a known bug in this combination. The issue is >> common >> known on other hardware configs. >> >> dmesg | grep broadcom >> >> [ 2.170370] usb 1-1.4: Manufacturer: Broadcom Corp >> [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller >> 6.20.155.1 (r326264) >> >> --> Wrong Chip >> >> WLAN is working ... But not in fullspeed and the datarate is a bit >> weak/random. >> >> >> lspci -nvv >> >> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 >> 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) >> Subsystem: Broadcom Corporation Device [14e4:0608] >> Flags: bus master, fast devsel, latency 0, IRQ 17 >> Memory at f0500000 (64-bit, non-prefetchable) [size=16K] >> Capabilities: [40] Power Management version 3 >> Capabilities: [58] Vendor Specific Information: Len=78 >> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ >> Capabilities: [d0] Express Endpoint, MSI 00 >> Capabilities: [100] Advanced Error Reporting >> Capabilities: [13c] Virtual Channel >> Capabilities: [160] Device Serial Number >> 00-00-3d-ff-ff-de-c0-14 >> Capabilities: [16c] Power Budgeting >> Kernel driver in use: wl >> >> >> >> 2. Several ACPI errors (parts of dmesg): >> >> >> [ 0.134252] ACPI: bus type pci registered >> [ 0.134310] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem >> 0xf8000000-0xfbffffff] (base 0xf8000000) >> [ 0.134312] PCI: not using MMCONFIG >> [ 0.134313] PCI: Using configuration type 1 for base access >> [ 0.135048] bio: create slab at 0 >> [ 0.135116] ACPI: Added _OSI(Module Device) >> [ 0.135118] ACPI: Added _OSI(Processor Device) >> [ 0.135119] ACPI: Added _OSI(3.0 _SCP Extensions) >> [ 0.135122] ACPI: Added _OSI(Processor Aggregator Device) >> [ 0.136797] ACPI: EC: Look up EC in DSDT >> [ 0.136929] ACPI Error: No handler for Region [ECOR] >> (ffff88021285acf0) >> [EmbeddedControl] (20121018/evregion-376) >> [ 0.136933] ACPI Error: Region EmbeddedControl (ID=3) has no handler >> (20121018/exfldio-305) >> [ 0.136936] ACPI Error: Method parse/execution failed >> [\_SB_.PCI0.LPCB.H_EC._REG] (Node ffff880212868d48), AE_NOT_EXIST >> (20121018/psparse-537) >> [ 0.138135] ACPI: Executed 1 blocks of module-level executable AML >> code >> [ 0.142156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ >> 0.142812] ACPI: SSDT 00000000dae3e018 0083B (v01 PmRef Cpu0Cst >> 00003001 >> INTL 20061109) >> [ 0.143236] ACPI: Dynamic OEM Table Load: >> [ 0.143237] ACPI: SSDT (null) 0083B (v01 PmRef Cpu0Cst >> 00003001 INTL 20061109) >> [ 0.143493] ACPI: SSDT 00000000dae3fa98 00303 (v01 PmRef ApIst >> 00003000 INTL 20061109) >> [ 0.143941] ACPI: Dynamic OEM Table Load: >> [ 0.143943] ACPI: SSDT (null) 00303 (v01 PmRef ApIst >> 00003000 INTL 20061109) >> [ 0.144063] ACPI: SSDT 00000000dae3dd98 00119 (v01 PmRef ApCst >> 00003000 INTL 20061109) >> [ 0.144483] ACPI: Dynamic OEM Table Load: >> [ 0.144485] ACPI: SSDT (null) 00119 (v01 PmRef ApCst >> 00003000 INTL 20061109) >> [ 0.561205] ACPI: Interpreter enabled >> [ 0.561208] ACPI: (supports S0 S3 S4 S5) >> [ 0.561229] ACPI: Using IOAPIC for interrupt routing >> [ 0.561248] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem >> 0xf8000000-0xfbffffff] (base 0xf8000000) >> [ 0.561757] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in >> ACPI motherboard resources >> [ 0.571926] ACPI: Power Resource [PUBS] (off) >> [ 0.577232] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = >> 0x62 >> [ 0.577364] ACPI: No dock devices found. >> [ 0.577367] PCI: Using host bridge windows from ACPI; if necessary, >> use >> "pci=nocrs" and report a bug >> [ 0.577478] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) [ >> 0.577480] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ >> 0.577613] \_SB_.PCI0:_OSC invalid UUID >> [ 0.577614] _OSC request data:1 8 1f >> [ 0.577655] \_SB_.PCI0:_OSC invalid UUID >> [ 0.577656] _OSC request data:1 1f 1f >> [ 0.577659] pci_root PNP0A08:00: ACPI _OSC support notification >> failed, >> disabling PCIe ASPM >> [ 0.577661] pci_root PNP0A08:00: Unable to request _OSC control (_OSC >> support mask: 0x08) >> >> >> [ 1.099434] efifb: mode is 1366x768x32, linelength=5504, pages=1 [ >> 1.099435] efifb: scrolling: redraw >> [ 1.099437] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 >> [ 1.102464] Console: switching to colour frame buffer device 170x48 [ >> 1.105323] fb0: EFI VGA frame buffer device >> [ 1.105327] intel_idle: MWAIT substates: 0x21120 >> [ 1.105328] intel_idle: v0.4 model 0x3A >> [ 1.105329] intel_idle: lapic_timer_reliable_states 0xffffffff >> [ 1.105522] ACPI: AC Adapter [ADP1] (on-line) >> [ 1.105619] input: Lid Switch as >> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 >> [ 1.105762] ACPI: Lid Switch [LID0] >> [ 1.105796] input: Sleep Button as >> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 >> [ 1.105799] ACPI: Sleep Button [SLPB] >> [ 1.105823] input: Power Button as >> /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 >> [ 1.105825] ACPI: Power Button [PWRF] >> [ 1.105896] ACPI: Requesting acpi_cpufreq >> [ 1.109262] ACPI Error: No handler for Region [ECRM] >> (ffff880212b7d5e8) >> [EmbeddedControl] (20121018/evregion-376) >> [ 1.109266] ACPI Error: Region EmbeddedControl (ID=3) has no handler >> (20121018/exfldio-305) >> [ 1.109269] ACPI Error: Method parse/execution failed [\_TZ_.MDEC] >> (Node ffff88021286b9b0), AE_NOT_EXIST (20121018/psparse-537) >> [ 1.109275] ACPI Error: Method parse/execution failed >> [\_TZ_.TZS0._SCP] >> (Node ffff88021286ba50), AE_NOT_EXIST (20121018/psparse-537) >> [ 1.109351] thermal LNXTHERM:00: registered as thermal_zone0 >> [ 1.109353] ACPI: Thermal Zone [TZS0] (44 C) >> [ 1.109492] thermal LNXTHERM:01: registered as thermal_zone1 >> [ 1.109493] ACPI: Thermal Zone [TZS1] (31 C) >> [ 1.109517] GHES: HEST is not enabled! >> [ 1.109581] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled >> [ >> 1.110384] ACPI: Battery Slot [BAT0] (battery present) >> [ 1.110905] Linux agpgart interface v0.103 >> [ 1.111813] brd: module loaded >> [ 1.112343] loop: module loaded >> [ 1.112564] libphy: Fixed MDIO Bus: probed >> >> >> [ 23.044977] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready >> [ 23.199826] udevd[645]: starting version 175 >> [ 24.106469] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x12 [ >> 24.260832] Non-volatile memory driver v1.3 >> [ 24.279032] ACPI Warning: 0x0000000000000428-0x000000000000042f >> SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251) >> [ 24.279040] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279045] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) >> [ 24.279049] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 >> (20121018/utaddress-251) >> [ 24.279053] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 >> (20121018/utaddress-251) >> [ 24.279057] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279059] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) >> [ 24.279063] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 >> (20121018/utaddress-251) >> [ 24.279066] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 >> (20121018/utaddress-251) >> [ 24.279070] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279072] lpc_ich: Resource conflict(s) found affecting gpio_ich [ >> 24.284425] cfg80211: Calling CRDA to update world regulatory domain [ >> 24.348682] mei 0000:00:16.0: setting latency timer to 64 >> [ 24.348743] mei 0000:00:16.0: irq 44 for MSI/MSI-X >> [ 24.370936] Bluetooth: Core ver 2.16 >> [ 24.370953] NET: Registered protocol family 31 >> [ 24.370955] Bluetooth: HCI device and connection manager initialized >> [ >> 24.370963] Bluetooth: HCI socket layer initialized >> [ 24.370966] Bluetooth: L2CAP socket layer initialized >> [ 24.370972] Bluetooth: SCO socket layer initialized >> [ 24.387322] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X >> [ 24.487908] lib80211: common routines for IEEE802.11 drivers >> [ 24.487912] lib80211_crypt: registered algorithm 'NULL' >> [ 24.509595] cfg80211: World regulatory domain updated: >> [ 24.509599] cfg80211: (start_freq - end_freq @ bandwidth), >> (max_antenna_gain, max_eirp) >> [ 24.509600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509602] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509603] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509604] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509606] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> >> >> [ 24.761841] Bluetooth: can't load firmware, may not work correctly [ >> 24.801105] wl: module license 'MIXED/Proprietary' taints kernel. [ >> 24.810628] thinkpad_acpi: ThinkPad ACPI Extras v0.24 >> [ 24.810631] thinkpad_acpi: http://ibm-acpi.sf.net/ >> [ 24.810633] thinkpad_acpi: ThinkPad BIOS H1ET63WW (1.06 ), EC unknown >> [ >> 24.810634] thinkpad_acpi: Lenovo Lenovo B590, model 627429G >> [ 24.811941] thinkpad_acpi: detected a 8-level brightness capable >> ThinkPad >> [ 24.811986] thinkpad_acpi: This ThinkPad has standard ACPI backlight >> brightness control, supported by the ACPI video driver >> [ 24.811988] thinkpad_acpi: Disabling thinkpad-acpi brightness events >> by >> default... >> [ 24.815661] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio >> is >> unblocked >> [ 24.816095] thinkpad_acpi: Standard ACPI backlight interface >> available, >> not loading native one >> [ 24.816232] thinkpad_acpi: Console audio control enabled, mode: >> monitor >> (read only) >> [ 24.817780] input: ThinkPad Extra Buttons as >> /devices/platform/thinkpad_acpi/input/input8 >> [ 24.835558] INFO @wl_cfg80211_attach : Registered CFG80211 phy >> [ 24.843006] type=1400 audit(1366106007.209:2): apparmor="STATUS" >> operation="profile_load" name="/sbin/dhclient" pid=849 >> comm="apparmor_parser" >> [ 24.843014] type=1400 audit(1366106007.209:3): apparmor="STATUS" >> operation="profile_replace" name="/sbin/dhclient" pid=850 >> comm="apparmor_parser" >> [ 24.843356] type=1400 audit(1366106007.209:4): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 >> comm="apparmor_parser" >> [ 24.843363] type=1400 audit(1366106007.209:5): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=850 >> comm="apparmor_parser" >> [ 24.843546] type=1400 audit(1366106007.209:6): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" >> pid=849 comm="apparmor_parser" >> [ 24.843554] type=1400 audit(1366106007.209:7): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/connman/scripts/dhclient-script" pid=850 >> comm="apparmor_parser" >> [ 24.854831] lib80211_crypt: registered algorithm 'TKIP' >> [ 24.991554] Linux video capture interface: v2.00 >> [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller >> 6.20.155.1 (r326264) >> [ 25.210570] uvcvideo: Found UVC 1.00 device Integrated Camera >> (04f2:b2fa) >> [ 25.211869] input: Integrated Camera as >> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 [ >> 25.211942] usbcore: registered new interface driver uvcvideo >> [ 25.211944] USB Video Class driver (1.1.1) >> [ 25.316148] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, >> id: >> 0x1e0b1, caps: 0xf00073/0x240000/0xa2400, board id: 2060, fw id: 1040538 >> [ >> 25.349946] input: SynPS/2 Synaptics TouchPad as >> /devices/platform/i8042/serio1/input/input10 >> [ 26.673431] btrfs: disk space caching is enabled >> [ 26.802960] device fsid 040341e4-f437-42c5-890b-8639d5046bf1 devid 1 >> transid 96 /dev/sda4 >> [ 26.803657] btrfs: disk space caching is enabled >> [ 27.158579] device fsid 5683cbcc-e616-4535-a393-b7108562cf60 devid 1 >> transid 962 /dev/mapper/linroot_crypt >> [ 29.429897] init: failsafe main process (1206) killed by TERM signal >> [ >> 30.331389] type=1400 audit(1366106012.705:8): apparmor="STATUS" >> operation="profile_replace" name="/sbin/dhclient" pid=1281 >> comm="apparmor_parser" >> [ 30.331760] type=1400 audit(1366106012.705:9): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1281 >> comm="apparmor_parser" >> [ 30.331953] type=1400 audit(1366106012.705:10): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/connman/scripts/dhclient-script" pid=1281 >> comm="apparmor_parser" >> [ 30.382097] type=1400 audit(1366106012.757:11): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" >> pid=1280 comm="apparmor_parser" >> [ 30.382367] type=1400 audit(1366106012.757:12): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" >> pid=1280 comm="apparmor_parser" >> [ 30.395833] type=1400 audit(1366106012.769:13): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/telepathy/mission-control-5" >> pid=1283 comm="apparmor_parser" >> [ 30.396254] type=1400 audit(1366106012.769:14): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=1283 >> comm="apparmor_parser" >> [ 30.396915] type=1400 audit(1366106012.773:15): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=1283 >> comm="apparmor_parser" >> [ 30.402793] type=1400 audit(1366106012.777:16): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1279 >> comm="apparmor_parser" >> [ 30.403059] type=1400 audit(1366106012.777:17): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" >> pid=1279 comm="apparmor_parser" >> [ 30.859995] Bluetooth: RFCOMM TTY layer initialized >> [ 30.860004] Bluetooth: RFCOMM socket layer initialized >> [ 30.860005] Bluetooth: RFCOMM ver 1.11 >> [ 30.893034] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 >> [ 30.893038] Bluetooth: BNEP filters: protocol multicast >> [ 30.893046] Bluetooth: BNEP socket layer initialized >> [ 31.481429] init: avahi-cups-reload main process (1363) terminated >> with >> status 1 >> >> >> I hope anyone can help me to identify if it's a bug or not. >> >> Kind regards >> >> >> >> > Please open a bug in Launchpad by running the following from a terminal: > > ubuntu-bug linux > > That will allow us to review all your logs, config info, etc. It will > also allow others to search for your bug if they are having similar > issues. > > Thanks, > > Joe > > > > ____________________________________________________________________________________ > Your personal email. Anytime, anywhere. > Ridiculously affordable at $19.95. No contracts. > http://www.getpeek.com/lavabit.html > ____________________________________________________________________________________ > From okg853 at lavabit.com Tue Apr 16 17:35:50 2013 From: okg853 at lavabit.com (okg853 at lavabit.com) Date: Tue, 16 Apr 2013 13:35:50 -0400 (EDT) Subject: Ubuntu 13.04 // Lenovo B590 MBX29GE/627429G // WLAN and ACPI Issues/Bugs!? In-Reply-To: <516D7423.4040802@canonical.com> References: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> <516D7423.4040802@canonical.com> Message-ID: <46872.84.150.143.143.1366133750.squirrel@lavabit.com> > On 04/16/2013 07:31 AM, okg853 at lavabit.com wrote: >> Dear community, >> >> I've got the notebook mentioned above. I've installed Ubuntu 13.04 >> (latest >> updates, kernel 3.8.0-18) on this machine and got several issues: >> >> >> 1.) The most anyoing one (Broadcom BMC 43142): >> >> I can't work on console due to the spamming of the following message all >> two seconds: >> >> ERROR @wl_cfg80211_get_station : Could not get rssi (-1) >> ERROR @wl_cfg80211_get_station : Could not get rate (-1) >> >> I don't know if it's a known bug in this combination. The issue is >> common >> known on other hardware configs. >> >> dmesg | grep broadcom >> >> [ 2.170370] usb 1-1.4: Manufacturer: Broadcom Corp >> [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller >> 6.20.155.1 (r326264) >> >> --> Wrong Chip >> >> WLAN is working ... But not in fullspeed and the datarate is a bit >> weak/random. >> >> >> lspci -nvv >> >> 02:00.0 Network controller [0280]: Broadcom Corporation BCM4313 >> 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01) >> Subsystem: Broadcom Corporation Device [14e4:0608] >> Flags: bus master, fast devsel, latency 0, IRQ 17 >> Memory at f0500000 (64-bit, non-prefetchable) [size=16K] >> Capabilities: [40] Power Management version 3 >> Capabilities: [58] Vendor Specific Information: Len=78 >> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+ >> Capabilities: [d0] Express Endpoint, MSI 00 >> Capabilities: [100] Advanced Error Reporting >> Capabilities: [13c] Virtual Channel >> Capabilities: [160] Device Serial Number >> 00-00-3d-ff-ff-de-c0-14 >> Capabilities: [16c] Power Budgeting >> Kernel driver in use: wl >> >> >> >> 2. Several ACPI errors (parts of dmesg): >> >> >> [ 0.134252] ACPI: bus type pci registered >> [ 0.134310] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem >> 0xf8000000-0xfbffffff] (base 0xf8000000) >> [ 0.134312] PCI: not using MMCONFIG >> [ 0.134313] PCI: Using configuration type 1 for base access >> [ 0.135048] bio: create slab at 0 >> [ 0.135116] ACPI: Added _OSI(Module Device) >> [ 0.135118] ACPI: Added _OSI(Processor Device) >> [ 0.135119] ACPI: Added _OSI(3.0 _SCP Extensions) >> [ 0.135122] ACPI: Added _OSI(Processor Aggregator Device) >> [ 0.136797] ACPI: EC: Look up EC in DSDT >> [ 0.136929] ACPI Error: No handler for Region [ECOR] >> (ffff88021285acf0) >> [EmbeddedControl] (20121018/evregion-376) >> [ 0.136933] ACPI Error: Region EmbeddedControl (ID=3) has no handler >> (20121018/exfldio-305) >> [ 0.136936] ACPI Error: Method parse/execution failed >> [\_SB_.PCI0.LPCB.H_EC._REG] (Node ffff880212868d48), AE_NOT_EXIST >> (20121018/psparse-537) >> [ 0.138135] ACPI: Executed 1 blocks of module-level executable AML >> code >> [ 0.142156] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ >> 0.142812] ACPI: SSDT 00000000dae3e018 0083B (v01 PmRef Cpu0Cst >> 00003001 >> INTL 20061109) >> [ 0.143236] ACPI: Dynamic OEM Table Load: >> [ 0.143237] ACPI: SSDT (null) 0083B (v01 PmRef Cpu0Cst >> 00003001 INTL 20061109) >> [ 0.143493] ACPI: SSDT 00000000dae3fa98 00303 (v01 PmRef ApIst >> 00003000 INTL 20061109) >> [ 0.143941] ACPI: Dynamic OEM Table Load: >> [ 0.143943] ACPI: SSDT (null) 00303 (v01 PmRef ApIst >> 00003000 INTL 20061109) >> [ 0.144063] ACPI: SSDT 00000000dae3dd98 00119 (v01 PmRef ApCst >> 00003000 INTL 20061109) >> [ 0.144483] ACPI: Dynamic OEM Table Load: >> [ 0.144485] ACPI: SSDT (null) 00119 (v01 PmRef ApCst >> 00003000 INTL 20061109) >> [ 0.561205] ACPI: Interpreter enabled >> [ 0.561208] ACPI: (supports S0 S3 S4 S5) >> [ 0.561229] ACPI: Using IOAPIC for interrupt routing >> [ 0.561248] PCI: MMCONFIG for domain 0000 [bus 00-3f] at [mem >> 0xf8000000-0xfbffffff] (base 0xf8000000) >> [ 0.561757] PCI: MMCONFIG at [mem 0xf8000000-0xfbffffff] reserved in >> ACPI motherboard resources >> [ 0.571926] ACPI: Power Resource [PUBS] (off) >> [ 0.577232] ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = >> 0x62 >> [ 0.577364] ACPI: No dock devices found. >> [ 0.577367] PCI: Using host bridge windows from ACPI; if necessary, >> use >> "pci=nocrs" and report a bug >> [ 0.577478] ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-3e]) [ >> 0.577480] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [ >> 0.577613] \_SB_.PCI0:_OSC invalid UUID >> [ 0.577614] _OSC request data:1 8 1f >> [ 0.577655] \_SB_.PCI0:_OSC invalid UUID >> [ 0.577656] _OSC request data:1 1f 1f >> [ 0.577659] pci_root PNP0A08:00: ACPI _OSC support notification >> failed, >> disabling PCIe ASPM >> [ 0.577661] pci_root PNP0A08:00: Unable to request _OSC control (_OSC >> support mask: 0x08) >> >> >> [ 1.099434] efifb: mode is 1366x768x32, linelength=5504, pages=1 [ >> 1.099435] efifb: scrolling: redraw >> [ 1.099437] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 >> [ 1.102464] Console: switching to colour frame buffer device 170x48 [ >> 1.105323] fb0: EFI VGA frame buffer device >> [ 1.105327] intel_idle: MWAIT substates: 0x21120 >> [ 1.105328] intel_idle: v0.4 model 0x3A >> [ 1.105329] intel_idle: lapic_timer_reliable_states 0xffffffff >> [ 1.105522] ACPI: AC Adapter [ADP1] (on-line) >> [ 1.105619] input: Lid Switch as >> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 >> [ 1.105762] ACPI: Lid Switch [LID0] >> [ 1.105796] input: Sleep Button as >> /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 >> [ 1.105799] ACPI: Sleep Button [SLPB] >> [ 1.105823] input: Power Button as >> /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 >> [ 1.105825] ACPI: Power Button [PWRF] >> [ 1.105896] ACPI: Requesting acpi_cpufreq >> [ 1.109262] ACPI Error: No handler for Region [ECRM] >> (ffff880212b7d5e8) >> [EmbeddedControl] (20121018/evregion-376) >> [ 1.109266] ACPI Error: Region EmbeddedControl (ID=3) has no handler >> (20121018/exfldio-305) >> [ 1.109269] ACPI Error: Method parse/execution failed [\_TZ_.MDEC] >> (Node ffff88021286b9b0), AE_NOT_EXIST (20121018/psparse-537) >> [ 1.109275] ACPI Error: Method parse/execution failed >> [\_TZ_.TZS0._SCP] >> (Node ffff88021286ba50), AE_NOT_EXIST (20121018/psparse-537) >> [ 1.109351] thermal LNXTHERM:00: registered as thermal_zone0 >> [ 1.109353] ACPI: Thermal Zone [TZS0] (44 C) >> [ 1.109492] thermal LNXTHERM:01: registered as thermal_zone1 >> [ 1.109493] ACPI: Thermal Zone [TZS1] (31 C) >> [ 1.109517] GHES: HEST is not enabled! >> [ 1.109581] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled >> [ >> 1.110384] ACPI: Battery Slot [BAT0] (battery present) >> [ 1.110905] Linux agpgart interface v0.103 >> [ 1.111813] brd: module loaded >> [ 1.112343] loop: module loaded >> [ 1.112564] libphy: Fixed MDIO Bus: probed >> >> >> [ 23.044977] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready >> [ 23.199826] udevd[645]: starting version 175 >> [ 24.106469] microcode: CPU0 sig=0x306a9, pf=0x10, revision=0x12 [ >> 24.260832] Non-volatile memory driver v1.3 >> [ 24.279032] ACPI Warning: 0x0000000000000428-0x000000000000042f >> SystemIO conflicts with Region \PMIO 1 (20121018/utaddress-251) >> [ 24.279040] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279045] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) >> [ 24.279049] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 >> (20121018/utaddress-251) >> [ 24.279053] ACPI Warning: 0x0000000000000530-0x000000000000053f >> SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 >> (20121018/utaddress-251) >> [ 24.279057] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279059] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \GPIO 1 (20121018/utaddress-251) >> [ 24.279063] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \_SB_.PCI0.PEG0.PEGP.GPIO 2 >> (20121018/utaddress-251) >> [ 24.279066] ACPI Warning: 0x0000000000000500-0x000000000000052f >> SystemIO conflicts with Region \_SB_.PCI0.LPCB.LPIO 3 >> (20121018/utaddress-251) >> [ 24.279070] ACPI: If an ACPI driver is available for this device, you >> should use it instead of the native driver >> [ 24.279072] lpc_ich: Resource conflict(s) found affecting gpio_ich [ >> 24.284425] cfg80211: Calling CRDA to update world regulatory domain [ >> 24.348682] mei 0000:00:16.0: setting latency timer to 64 >> [ 24.348743] mei 0000:00:16.0: irq 44 for MSI/MSI-X >> [ 24.370936] Bluetooth: Core ver 2.16 >> [ 24.370953] NET: Registered protocol family 31 >> [ 24.370955] Bluetooth: HCI device and connection manager initialized >> [ >> 24.370963] Bluetooth: HCI socket layer initialized >> [ 24.370966] Bluetooth: L2CAP socket layer initialized >> [ 24.370972] Bluetooth: SCO socket layer initialized >> [ 24.387322] snd_hda_intel 0000:00:1b.0: irq 45 for MSI/MSI-X >> [ 24.487908] lib80211: common routines for IEEE802.11 drivers >> [ 24.487912] lib80211_crypt: registered algorithm 'NULL' >> [ 24.509595] cfg80211: World regulatory domain updated: >> [ 24.509599] cfg80211: (start_freq - end_freq @ bandwidth), >> (max_antenna_gain, max_eirp) >> [ 24.509600] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509602] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509603] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509604] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> [ 24.509606] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 >> mBi, 2000 mBm) >> >> >> [ 24.761841] Bluetooth: can't load firmware, may not work correctly [ >> 24.801105] wl: module license 'MIXED/Proprietary' taints kernel. [ >> 24.810628] thinkpad_acpi: ThinkPad ACPI Extras v0.24 >> [ 24.810631] thinkpad_acpi: http://ibm-acpi.sf.net/ >> [ 24.810633] thinkpad_acpi: ThinkPad BIOS H1ET63WW (1.06 ), EC unknown >> [ >> 24.810634] thinkpad_acpi: Lenovo Lenovo B590, model 627429G >> [ 24.811941] thinkpad_acpi: detected a 8-level brightness capable >> ThinkPad >> [ 24.811986] thinkpad_acpi: This ThinkPad has standard ACPI backlight >> brightness control, supported by the ACPI video driver >> [ 24.811988] thinkpad_acpi: Disabling thinkpad-acpi brightness events >> by >> default... >> [ 24.815661] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio >> is >> unblocked >> [ 24.816095] thinkpad_acpi: Standard ACPI backlight interface >> available, >> not loading native one >> [ 24.816232] thinkpad_acpi: Console audio control enabled, mode: >> monitor >> (read only) >> [ 24.817780] input: ThinkPad Extra Buttons as >> /devices/platform/thinkpad_acpi/input/input8 >> [ 24.835558] INFO @wl_cfg80211_attach : Registered CFG80211 phy >> [ 24.843006] type=1400 audit(1366106007.209:2): apparmor="STATUS" >> operation="profile_load" name="/sbin/dhclient" pid=849 >> comm="apparmor_parser" >> [ 24.843014] type=1400 audit(1366106007.209:3): apparmor="STATUS" >> operation="profile_replace" name="/sbin/dhclient" pid=850 >> comm="apparmor_parser" >> [ 24.843356] type=1400 audit(1366106007.209:4): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=849 >> comm="apparmor_parser" >> [ 24.843363] type=1400 audit(1366106007.209:5): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=850 >> comm="apparmor_parser" >> [ 24.843546] type=1400 audit(1366106007.209:6): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/connman/scripts/dhclient-script" >> pid=849 comm="apparmor_parser" >> [ 24.843554] type=1400 audit(1366106007.209:7): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/connman/scripts/dhclient-script" pid=850 >> comm="apparmor_parser" >> [ 24.854831] lib80211_crypt: registered algorithm 'TKIP' >> [ 24.991554] Linux video capture interface: v2.00 >> [ 25.102896] eth1: Broadcom BCM4727 802.11 Hybrid Wireless Controller >> 6.20.155.1 (r326264) >> [ 25.210570] uvcvideo: Found UVC 1.00 device Integrated Camera >> (04f2:b2fa) >> [ 25.211869] input: Integrated Camera as >> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/input/input9 [ >> 25.211942] usbcore: registered new interface driver uvcvideo >> [ 25.211944] USB Video Class driver (1.1.1) >> [ 25.316148] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.5, >> id: >> 0x1e0b1, caps: 0xf00073/0x240000/0xa2400, board id: 2060, fw id: 1040538 >> [ >> 25.349946] input: SynPS/2 Synaptics TouchPad as >> /devices/platform/i8042/serio1/input/input10 >> [ 26.673431] btrfs: disk space caching is enabled >> [ 26.802960] device fsid 040341e4-f437-42c5-890b-8639d5046bf1 devid 1 >> transid 96 /dev/sda4 >> [ 26.803657] btrfs: disk space caching is enabled >> [ 27.158579] device fsid 5683cbcc-e616-4535-a393-b7108562cf60 devid 1 >> transid 962 /dev/mapper/linroot_crypt >> [ 29.429897] init: failsafe main process (1206) killed by TERM signal >> [ >> 30.331389] type=1400 audit(1366106012.705:8): apparmor="STATUS" >> operation="profile_replace" name="/sbin/dhclient" pid=1281 >> comm="apparmor_parser" >> [ 30.331760] type=1400 audit(1366106012.705:9): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/NetworkManager/nm-dhcp-client.action" pid=1281 >> comm="apparmor_parser" >> [ 30.331953] type=1400 audit(1366106012.705:10): apparmor="STATUS" >> operation="profile_replace" >> name="/usr/lib/connman/scripts/dhclient-script" pid=1281 >> comm="apparmor_parser" >> [ 30.382097] type=1400 audit(1366106012.757:11): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" >> pid=1280 comm="apparmor_parser" >> [ 30.382367] type=1400 audit(1366106012.757:12): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" >> pid=1280 comm="apparmor_parser" >> [ 30.395833] type=1400 audit(1366106012.769:13): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/telepathy/mission-control-5" >> pid=1283 comm="apparmor_parser" >> [ 30.396254] type=1400 audit(1366106012.769:14): apparmor="STATUS" >> operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=1283 >> comm="apparmor_parser" >> [ 30.396915] type=1400 audit(1366106012.773:15): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/telepathy/telepathy-*//sanitized_helper" pid=1283 >> comm="apparmor_parser" >> [ 30.402793] type=1400 audit(1366106012.777:16): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1279 >> comm="apparmor_parser" >> [ 30.403059] type=1400 audit(1366106012.777:17): apparmor="STATUS" >> operation="profile_load" >> name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" >> pid=1279 comm="apparmor_parser" >> [ 30.859995] Bluetooth: RFCOMM TTY layer initialized >> [ 30.860004] Bluetooth: RFCOMM socket layer initialized >> [ 30.860005] Bluetooth: RFCOMM ver 1.11 >> [ 30.893034] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 >> [ 30.893038] Bluetooth: BNEP filters: protocol multicast >> [ 30.893046] Bluetooth: BNEP socket layer initialized >> [ 31.481429] init: avahi-cups-reload main process (1363) terminated >> with >> status 1 >> >> >> I hope anyone can help me to identify if it's a bug or not. >> >> Kind regards >> >> >> >> > Please open a bug in Launchpad by running the following from a terminal: > > ubuntu-bug linux > > That will allow us to review all your logs, config info, etc. It will > also allow others to search for your bug if they are having similar > issues. > > Thanks, > > Joe > > > > ____________________________________________________________________________________ > Your personal email. Anytime, anywhere. > Ridiculously affordable at $19.95. No contracts. > http://www.getpeek.com/lavabit.html > ____________________________________________________________________________________ > Hi Joe, thank you for you quick reply! I've done what you suggested. Bug #1169653 // https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1169653 Kind regards From noreply at ubuntu.com Wed Apr 17 09:37:39 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 17 Apr 2013 09:37:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_shan?= =?utf-8?q?kao?= Message-ID: <20130417093739.30699.54925@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=125&rev2=126 Some packages have changed names through versions of ubuntu and others need special care while reporting. This section lists these caveats. + == Filesystem problems == + + Usual suspects are the kernel, gvfs and mountall. + === Kernel === The correct package for bugs about the kernel is `linux`. From hggdh2 at ubuntu.com Sat Apr 20 17:06:28 2013 From: hggdh2 at ubuntu.com (C de-Avillez) Date: Sat, 20 Apr 2013 17:06:28 +0000 Subject: Ubuntu 13.04 // Lenovo B590 MBX29GE/627429G // WLAN and ACPI Issues/Bugs!? In-Reply-To: <516D7423.4040802@canonical.com> References: <22394.80.254.76.178.1366111910.squirrel@lavabit.com> <516D7423.4040802@canonical.com> Message-ID: <20130420170628.6f6b3a45@xango3> On Tue, 16 Apr 2013 11:54:11 -0400 Joseph Salisbury wrote: > On 04/16/2013 07:31 AM, okg853 at lavabit.com wrote: > > Dear community, > > > > I've got the notebook mentioned above. I've installed Ubuntu 13.04 > > (latest updates, kernel 3.8.0-18) on this machine and got several > > issues: > > > > > > 1.) The most anyoing one (Broadcom BMC 43142): > > > > I can't work on console due to the spamming of the following > > message all two seconds: > > > > ERROR @wl_cfg80211_get_station : Could not get rssi (-1) > > ERROR @wl_cfg80211_get_station : Could not get rate (-1) > Please open a bug in Launchpad by running the following from a > terminal: > > ubuntu-bug linux > > That will allow us to review all your logs, config info, etc. It > will also allow others to search for your bug if they are having > similar issues. This is https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1107155; I am certain there are others about the same issue. Since this is kernel-related, opening a new bug is still important, due to potentially different hardware. ..C.. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: From noreply at ubuntu.com Mon Apr 22 18:08:56 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 22 Apr 2013 18:08:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingDBus=22_by_grawity?= Message-ID: <20130422180856.11617.23939@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingDBus" page has been changed by grawity: http://wiki.kubuntu.org/DebuggingDBus?action=diff&rev1=5&rev2=6 Comment: Update for a stricter policy This is trickier, because D-Bus policy typically prevents anything but signals from being viewable by dbus-monitor. But we can change that. - 1. Make a backup of /etc/dbus-1/system.conf: + 1. Create a file /etc/dbus-1/system.d/99-eavesdrop.conf, with these contents: {{{ + + + - sudo cp /etc/dbus-1/system.conf /etc/dbus-1/system.conf~ - }}} - 1. Edit /etc/dbus-1/system.conf - {{{ - sudo editor /etc/dbus-1/system.conf - }}} - 1. Find the section and replace it with the following block. This block opens up the system bus to viewing by anyone. - - '''This is not a safe policy! You should revert this change after you are done debugging.''' - {{{ - - - - - + - - - + - + + - }}} - 1. Then comment out or delete the nearby line. This line will include individual policies for specific services. But we don't want those individual policies to further restrict the bus. So we force our above lax policy by not including sub-policies. - {{{ - - }}} - 1. Reboot to get a fresh dbus daemon using this new policy. - {{{ - sudo reboot }}} 1. Now run dbus-monitor as root. You should be able to see all signals, method calls, and method replies. {{{ sudo dbus-monitor --system }}} - 1. When done debugging, remember to go back to your previous, secure policy: + 1. When done debugging, it is wise to remove the policy snippet: {{{ + sudo rm /etc/dbus-1/system.d/99-eavesdrop.conf - sudo cp /etc/dbus-1/system.conf~ /etc/dbus-1/system.conf - sudo reboot }}} = Filtering all the noise = If there is just too much information on the bus, pass a match rule like so: {{{ - dbus-monitor "type='signal',sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'" + dbus-monitor "type=signal,sender='org.gnome.TypingMonitor',interface='org.gnome.TypingMonitor'" }}} - Multiple rules can be specified. If a message matches any of the rules, the message will be printed. Like so: + Multiple rules can be specified. If a message matches ''any'' of the rules, the message will be printed. Like so: {{{ - dbus-monitor 'type=error' 'sender=org.freedesktop.SystemToolsBackends' + dbus-monitor "type=error" "sender=org.freedesktop.SystemToolsBackends" + }}} + {{{ + dbus-monitor "type=method_call" "type=method_return" "type=error" }}} See the [[http://dbus.freedesktop.org/doc/dbus-specification.html|D-Bus documentation]] for more information on match rule syntax. From melchiaros at aol.com Fri Apr 26 10:55:58 2013 From: melchiaros at aol.com (melchiaros) Date: Fri, 26 Apr 2013 12:55:58 +0200 Subject: adopting the package ubuntu-release-upgrader Message-ID: <517A5D3E.2060105@aol.com> 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? 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? greetings melchiaros (aka Sasa Paporovic) https://launchpad.net/~melchiaros From es20490446e at gmail.com Fri Apr 26 14:14:31 2013 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 26 Apr 2013 16:14:31 +0200 Subject: Where to find proper bugs Message-ID: <517A8BC7.9000503@gmail.com> I wanted to thank Al Snow, Javier P.L., Robert Bruce Park, Matt Fischer and Brian Murray for your suggestion about how to find proper bugs to apply for Ubuntu BugControl. I found them very useful. -------------- 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 Apr 30 17:24:08 2013 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 30 Apr 2013 17:24:08 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_logan?= Message-ID: <20130430172408.310.9733@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by logan: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=365&rev2=366 Comment: change all instances of "Raring Ringtail" to "Saucy Salamander" Before using this, ''please'' check "rmadison " to see if the package version has changed between when the bug was reported and the current development release. If it has not changed, there is no need to ask. If it has changed, check the changelog (via aptitude changelog $PKGNAME) to see if this issue has been specifically addressed. - || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Raring Ringtail. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Saucy Salamander. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.|| == Missing a crash report or having a .crash attachment == @@ -208, +208 @@ ## Also we are actively promoting testing the development release of Ubuntu so something like this could be added: - ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Raring Ringtail. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || + ## || The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Saucy Salamander. It would help us greatly if you could test with it so we can work on getting it fixed in the actively developed release. You can find out more about the development release at http://www.ubuntu.com/testing/ || == Packages not provided by Ubuntu == @@ -221, +221 @@ The bug's state should become '''Fix Released''' and if the package qualifies for a [[https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|Stable Release Update (SRU)]]: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.<
><
> This is a significant bug in Ubuntu. If you need a fix for the bug in previous versions of Ubuntu, please do steps 1 and 2 of the SRU Procedure [1] to bring the need to a developer's attention.<
><
>[1]: https://wiki.ubuntu.com/StableReleaseUpdates#Procedure|| The bug's state should become '''Fix Released''' and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "Requesting a Backport" at https://wiki.ubuntu.com/UbuntuBackports#Requesting_a_Backport || The bug's state should become '''Fix Released''' and if the package can not be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Raring Ringtail. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information. || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Saucy Salamander. It won't be fixed in previous versions of Ubuntu because the package doesn't fit the requirements for backporting. See https://wiki.ubuntu.com/UbuntuBackports for more information. || == Reported by someone not respecting the Code of Conduct ==