From noreply at ubuntu.com Sat Oct 1 19:15:11 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 01 Oct 2016 19:15:11 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_statuses=22_by_penalvch?= Message-ID: <20161001191511.4128.35228@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug statuses" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Bug%20statuses?action=diff&rev1=77&rev2=78 Comment: As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/comments/23. * '''Fix Released''': * Ubuntu task: fixed in the latest Ubuntu release, as a standard upgrade. * /!\ If the bug stills affects an older Ubuntu release, please nominate it for that series. Otherwise people won't know it isn't fixed there! - * Indicate which package version the fix was released in. + * It is preferred, although not required, that one indicates which package version the fix was released in. * Upstream task: fix available in a tarball. From noreply at ubuntu.com Sat Oct 1 19:21:07 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 01 Oct 2016 19:21:07 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Bug_statuses=22_by_penalvch?= Message-ID: <20161001192107.4171.89346@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Bug statuses" page has been changed by penalvch: http://wiki.ubuntu.com/Bugs/Bug%20statuses?action=diff&rev1=78&rev2=79 Comment: As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458208/comments/22 some are confused thinking all bugs fixed in the latest release must have series nominated for all prior affected vers. * '''Fix Released''': * Ubuntu task: fixed in the latest Ubuntu release, as a standard upgrade. - * /!\ If the bug stills affects an older Ubuntu release, please nominate it for that series. Otherwise people won't know it isn't fixed there! + * If the bug stills affects an older Ubuntu release, one may nominate it for that series. * It is preferred, although not required, that one indicates which package version the fix was released in. * Upstream task: fix available in a tarball. From mm at ekimia.fr Sun Oct 9 16:11:10 2016 From: mm at ekimia.fr (Michel Memeteau - EKIMIA) Date: Sun, 9 Oct 2016 18:11:10 +0200 Subject: New Meta Bug : Need for a GPU accel browser Message-ID: Hi , After Few years using and selling Ubuntu hardware, i think I needed to open this bug : https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1631763 The fact that today other desktop competitors have out of the box support for GPU accelerated features in their preinstalled browsers is a big advantage on their side for the average consumer. Please give feedback from your experience. Regards. <------------------------------------------------------------------------------------------------------------------> Michel Memeteau - Directeur. Notre Boutique Ordinateurs GNU/Linux : http://shop.ekimia.fr 280 avenue de la malvesine 13720 La Bouilladisse - France. Fixe : +33 (0) 972308334 Mobile : +33(0) 624808051 <------------------------------------------------------------------------------------------------------------------> -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Sun Oct 9 08:30:23 2016 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 09 Oct 2016 08:30:23 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelSuspend=22_by_pen?= =?utf-8?q?alvch?= Message-ID: <20161009083023.14110.11766@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelSuspend" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKernelSuspend?action=diff&rev1=51&rev2=52 Comment: Due to LP#1629197 et. el. adjusted wording as folks think they are only to attach one resume trace. sudo su echo freezer > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo devices > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo platform > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo processors > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo core > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. While booted into the latest [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|non-daily mainline kernel]], execute at a terminal:{{{ sudo su echo none > /sys/power/pm_test exit - }}} Please attach to your report the resume trace mentioned below. <
> + }}} After executing this, please attach to your report the resume trace mentioned below. <
> 1. Please provide the output of the following terminal command: {{{ cat /sys/kernel/debug/suspend_stats }}} 1. If you have a graphics related issue after resume (corruption, display blank, etc.) please [[https://help.ubuntu.com/community/DebuggingSystemCrash#SSH|SSH]] into your machine and capture both /var/log/Xorg.0.log and /var/log/Xorg.0.log.old. Please attach each separately. From kapil.vasisth at gmail.com Wed Oct 12 16:37:52 2016 From: kapil.vasisth at gmail.com (Kapil Vasisth) Date: Wed, 12 Oct 2016 22:07:52 +0530 Subject: Fwd: ERROR WHILE UPGRADING FROM UBUNTU 14.04 TO UBUNTU 16.04 In-Reply-To: References: Message-ID: *Sir/Madam* *Today i have upgraded my ubuntu 14.04 to 16.04 using the “software updater”. But after all the steps it takes me to the black screen tty1. I have searched a lot and run different commnds but nothing works for me after that i had run * *sudo dpkg –configure -a* *sudo apt-get update* *sudo apt-get upgrade -y* *After that my desktop is recovered but many problems are arising after that as mentioned :-* *1. When on my laptop it shows the error as “/dev/sda1: clean, 566253/19349504 files, 28926122/77366272 blocks” it is taking more time to load. Its my biggest problem.* *2. Now my laptop shutdown in between working many times.(Laptop Samsung R-420)* *3.Software updater shows computer is uptodate.* *4. After running some commands the error is shows https://bugzilla.gnome.org/show_bug.cgi?id=709183 * *Some Screenshots are attached.* *Please suggest solutions as early as possible.* -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 20161012_165323.jpg Type: image/jpeg Size: 1925239 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: IMG-20161009-WA0000.jpg Type: image/jpeg Size: 66828 bytes Desc: not available URL: From es20490446e at gmail.com Thu Oct 13 15:50:29 2016 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 13 Oct 2016 17:50:29 +0200 Subject: ERROR WHILE UPGRADING FROM UBUNTU 14.04 TO UBUNTU 16.04 In-Reply-To: References: Message-ID: Kapil Vasisth: > Please suggest solutions. (https://bugs.launchpad.net/ubuntu/+filebug) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4747 bytes Desc: S/MIME Cryptographic Signature URL: From wolfgang.kde at rohdewald.de Mon Oct 17 12:13:37 2016 From: wolfgang.kde at rohdewald.de (Wolfgang Rohdewald) Date: Mon, 17 Oct 2016 14:13:37 +0200 Subject: cannot report a bug about kajongg Message-ID: <5532343.ZXAJeUzXoS@skull> Launchpad does not let me report bugs about kajongg. I can report bugs in other projects. It also says kajongg must be configured in order for Launchpad to forward bugs to the project's developers. What is wrong with launchpad? Please configure it such that bug reports are mailed to me - I am the kajongg developer. kajongg does not work at all with Ubuntu 16.10, see https://bugs.kde.org/show_bug.cgi?id=370998 and the pyqt mailing list as of today. I just committed a workaround as described in the kde bug report. Please consider repackaging kajongg with that workaround. Since kubuntu still comes with the deprecated KDE 16.04 apps, I also committed the fix to the branch Applications/16.04 -- Wolfgang From brian at ubuntu.com Mon Oct 17 12:45:32 2016 From: brian at ubuntu.com (Brian Murray) Date: Mon, 17 Oct 2016 05:45:32 -0700 Subject: cannot report a bug about kajongg In-Reply-To: <5532343.ZXAJeUzXoS@skull> References: <5532343.ZXAJeUzXoS@skull> Message-ID: <20161017124531.GN3849@murraytwins.com> On Mon, Oct 17, 2016 at 02:13:37PM +0200, Wolfgang Rohdewald wrote: > Launchpad does not let me report bugs about kajongg. I can > report bugs in other projects. Launchpad can track bugs for projects and packages for Ubuntu. I think you were at the project and not the Ubuntu package. https://bugs.launchpad.net/ubuntu/+source/kajongg/+bugs > It also says > > kajongg must be configured in order for Launchpad to forward bugs to the > project's developers. > > What is wrong with launchpad? > > Please configure it such that bug reports are mailed to me - I am the > kajongg developer. You can subscribe to bug reports about the kajongg package here: https://bugs.launchpad.net/ubuntu/+source/kajongg/+subscribe -- Brian Murray From wolfgang.kde at rohdewald.de Mon Oct 17 12:56:09 2016 From: wolfgang.kde at rohdewald.de (Wolfgang Rohdewald) Date: Mon, 17 Oct 2016 14:56:09 +0200 Subject: cannot report a bug about kajongg In-Reply-To: <20161017124531.GN3849@murraytwins.com> References: <5532343.ZXAJeUzXoS@skull> <20161017124531.GN3849@murraytwins.com> Message-ID: <1702885.Uq1zBD9cU8@skull> Am Montag, 17. Oktober 2016, 05:45:32 CEST schrieb Brian Murray: > On Mon, Oct 17, 2016 at 02:13:37PM +0200, Wolfgang Rohdewald wrote: > > Launchpad does not let me report bugs about kajongg. I can > > report bugs in other projects. > > Launchpad can track bugs for projects and packages for Ubuntu. I think > you were at the project and not the Ubuntu package. Thank you https://bugs.launchpad.net/ubuntu/+source/kajongg/+bug/1634125 -- Wolfgang From ubuntu at desserud.org Sun Oct 30 20:18:38 2016 From: ubuntu at desserud.org (Hans Joachim Desserud) Date: Sun, 30 Oct 2016 21:18:38 +0100 Subject: Bug pattern and cleanup In-Reply-To: <20160915224905.GX6405@murraytwins.com> References: <20160915224905.GX6405@murraytwins.com> Message-ID: <44400b60cbf679a8fd65acd3bd2f87a6@webmail.domeneshop.no> Den 2016-09-16 00:49, skrev Brian Murray: > I was recently writing an apport bug pattern[1] for a bug report and > discovered a set of bugs (32!) which could use a pattern and some > consolidation. If anybody is interested in learning how to write a bug > pattern let me know or find me on freenode irc (bdmurray). > > [1] > https://code.launchpad.net/~ubuntu-bugcontrol/apport/ubuntu-bugpatterns/ > > -- > Brian Murray > Ubuntu Bug Master Hi all I was inspired by this post, so I recently wrote my first bug pattern [1], which turned out to be easier than I had expected. There's lots of existing patterns in the repository, so it was quite easy to get started. I think I spent roughly two hours to get a working pattern which matched the bugs I wanted. The main reason it took so long was that I was doing things for the first time; reading the README, experimenting with patterns and finding out how to test if bug reports matched. All in all I found it a straight-forward process and it got accepted with only minor changes shortly after I submitted it. [1] https://code.launchpad.net/~hjd/apport/openjdk-9-bugpattern/+merge/309378 --- mvh / best regards Hans Joachim Desserud http://desserud.org