From noreply at ubuntu.com Thu Mar 5 21:01:56 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 05 Mar 2015 21:01:56 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Hotkeys/Troubleshooting=22_by_te?= =?utf-8?q?d-m-cox?= Message-ID: <20150305210156.20450.79558@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Hotkeys/Troubleshooting" page has been changed by ted-m-cox: http://wiki.ubuntu.com/Hotkeys/Troubleshooting?action=diff&rev1=41&rev2=42 === Useful Information to Collect in Reports === - /!\ Please do not compress the following, but attach each individually to the report: + /!\ Open a terminal, run each command below, and include the output file in your report. Please do not compress the files, but attach each individually to the report: * `udevadm info --export-db > udev-db.txt` * `dmesg > dmesg.log` * `sudo lsinput > lsinput.log` From noreply at ubuntu.com Thu Mar 5 21:08:10 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 05 Mar 2015 21:08:10 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Hotkeys/Troubleshooting=22_by_te?= =?utf-8?q?d-m-cox?= Message-ID: <20150305210810.20444.91983@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Hotkeys/Troubleshooting" page has been changed by ted-m-cox: http://wiki.ubuntu.com/Hotkeys/Troubleshooting?action=diff&rev1=42&rev2=43 === Useful Information to Collect in Reports === - /!\ Open a terminal, run each command below, and include the output file in your report. Please do not compress the files, but attach each individually to the report: + /!\ Open a terminal, run each command below, and include the output files in your report. Please do not compress the files, but attach each individually to the report: * `udevadm info --export-db > udev-db.txt` * `dmesg > dmesg.log` * `sudo lsinput > lsinput.log` From es20490446e at gmail.com Mon Mar 9 15:30:41 2015 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 09 Mar 2015 16:30:41 +0100 Subject: Please, triage this critical bug // System reboots (from sleep mode) when connecting android (via USB) In-Reply-To: References: Message-ID: <54FDBCA1.4030904@gmail.com> a b: > Please see my comment here: > > http://askubuntu.com/questions/210967/how-to-report-a-system-bug?rq=1#comment827608_243665 > > I'd like to report an apparent bug, but cannot find a way how: I have just answered your question in the page. If after reporting the bug you want me to mark it as critical, send the report URL to me. I will also ask the BugSquad to break the documentation into smaller parts, so it can be well understood. Although some people like to have it in one page, what I think it's a terrible mess! Meanwhile users keeps emailing me about these things. And it's because the one page texty cranky style. But even the real cavemen knew how to do it: Unix Philosophy (1970s): > - Rule of Modularity: Write simple parts connected by clean > interfaces. > > - Rule of Clarity: Clarity is better than cleverness. > > - Rule of Transparency: Design for visibility to make inspection and > debugging easier. > > - Rule of Parsimony: Write a big program only when it is clear by > demonstration that nothing else will do. > > - Rule of Robustness: Robustness is the child of transparency and > simplicity. > Thank you ;-) -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3748 bytes Desc: S/MIME Cryptographic Signature URL: From norman.geist at uni-greifswald.de Mon Mar 16 09:09:11 2015 From: norman.geist at uni-greifswald.de (Norman Geist) Date: Mon, 16 Mar 2015 10:09:11 +0100 Subject: Ubuntu Server LTS 14 Installer MDADM Message-ID: <002001d05fc8$ddd7cdf0$998769d0$@geist@uni-greifswald.de> Hey there, I'd like to report the following problem regarding RAID configuration during Ubuntu Server LTS 14 installation from CD. I have two fake RAID level 1, configured via LSI MegaRaid BIOS utility. Although I've answered both installer question regarding activation of discovered RAID devices with "No", MDADM just activates both of these DDF1 fake raids as software raid. Of course installation on a MDADM RAID doesn't work properly when it comes to write the GRUB boot record. So I had to manually deactivate all the software RAID devices from a shell, activate the fake RAIDs using dmraid, and let the installer redetect the disks. Now I'm finally able to install everything without problems. I think it that it is not the expected behavior for MDADM to jump in without being asked for it, activating fake RAIDs as software RAIDs, making the installation a confusing mess. Cheers Norman Geist -------------- next part -------------- An HTML attachment was scrubbed... URL: From es20490446e at gmail.com Mon Mar 16 09:40:35 2015 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Mon, 16 Mar 2015 10:40:35 +0100 Subject: Ubuntu Server LTS 14 Installer MDADM In-Reply-To: <55069dea.c485460a.0b2f.0245SMTPIN_ADDED_BROKEN@mx.google.com> References: <55069dea.c485460a.0b2f.0245SMTPIN_ADDED_BROKEN@mx.google.com> Message-ID: <5506A513.2050109@gmail.com> Norman Geist: > I’d like to report the following problem. For handling problems we use Launchad. And you can report to it by using the "ubuntu-bug" tool (http://tinyurl.com/kaxuoht). Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3748 bytes Desc: S/MIME Cryptographic Signature URL: From noreply at ubuntu.com Thu Mar 19 05:03:06 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 19 Mar 2015 05:03:06 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Upstream/LXDE=22_by_wxl?= Message-ID: <20150319050306.22206.65415@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Upstream/LXDE" page has been changed by wxl: http://wiki.ubuntu.com/Bugs/Upstream/LXDE?action=diff&rev1=4&rev2=5 Comment: initial commit, keeping it as simple as possible ## page was copied from Bugs/Upstream/Xfce <> - The Xfce bugzilla hosts a range of packages that are upstream to Ubuntu including the standard Xfce desktop and additional components like Thunar, which is the Xubuntu-desktop file manager. + The LXDE bug tracker hosts a range of packages that are upstream to Ubuntu including the standard LXDE desktop and additional components like PCManFM, which is the Lubuntu-desktop file manager. - - {{attachment:xfce-bugzilla.png}} = Packages affected = - Most packages listed in [[https://bugs.launchpad.net/~xubuntu-team/+packagebugs|bug contact packages for the Xubuntu Team]], including: + Most packages listed in [[https://bugs.launchpad.net/~lubuntu-packaging-team/+packagebugs|bug contact packages for the Lubuntu Packaging Team]], including: + * all the lx* packages, e.g. lxsession, lxpanel, etc. + * all the lubuntu* packages, e.g. lubuntu-default-settings, lubuntu-artwork, etc. + * obconf + * pcmanfm - * exo - * ristretto (found in xfce-goodies) - * thunar and thunar-??? - * xfburn - * xfce, xfce-???, xfce4, xfce4-??? - * xfdesktop and xfdesktop4 - * xfmedia and xfmedia-??? - * xfprint - * xfwm4 and xfwm4-??? = Using the bug tracker = - Xfce bugs are tracked upstream at '''[[http://bugzilla.xfce.org/|bugzilla.xfce.org]]'''. Click 'Open a new Bugzilla account' under the login box and enter your email address. + Well, there's more than one. - == Searching == + Most LXDE bugs are tracked upstream at '''[[http://sourceforge.net/projects/lxde/?source=directory|Sourceforge]]'''. You will also find '''[[http://sourceforge.net/projects/pcmanfm/?source=directory|PCManFM]]''' there. - The basic search functionality is the search box which is designed to be really simple to use but still allow you to use some more advanced search features. At the [[http://bugzilla.xfce.org/query.cgi|Search]] page you can search by: + LXQt (the future of LXDE) bugs are tracked upstream at '''[[https://github.com/lxde|GitHub]]''', including obconf and PCManFM.. + Lubuntu-specific packages are tracked on '''[[https://launchpad.net|Launchpad]]'''. - * Bug Numbers - * Phrases - * Target - * Keywords - * etc ... + Note that the window manager openbox is developed independently, as well as all the other apps. - You can also click "Search" on the menu bar under the heading from anywhere in Xfce Bugzilla to get to the search page. - - ## '''Examples:''' - - ## ToDo - - === Advanced === - - There's also functionality that allows you do to advanced searches which you can find at the [[http://bugzilla.xfce.org/query.cgi?format=advanced|Advanced Search]] page. Click on "Give me some help" for more information on search. As you mouse-over each item, a help tip will then appear for it. == Filing new bugs == After searching for possible duplicates you can file a new bug using the guided bug filing. Simply click on "New" in the menu bar under the header. Include a basic description of the problem and link to the original Launchpad report: - For forwarding bugs to the [[http://bugzilla.xfce.org/|Xfce Bugtracker]] (aka Xfce Bugzilla) you should follow these steps: + For forwarding bugs to any of the above trackers you should follow these steps: - * [[http://bugzilla.xfce.org/index.cgi?GoAheadAndLogIn=1|Log in]] or create a [[http://bugzilla.xfce.org/createaccount.cgi|new account]] + * Login (create a new account if you haven't already) - * Check if the bug is already reported with the [[http://bugzilla.xfce.org/query.cgi|search tool]] + * Check if the bug is already reported with the search tool - * ''If it does not already exist'' open a [[http://bugzilla.xfce.org/enter_bug.cgi|new bug]] + * ''If it does not already exist'' open a new bug '''Before submitting a new bug, you need to take care of a few things:''' - * Choose the Xfce and product version, also you need to select a component, almost all the products have a description about their components that is visible when the component is hilighted. - * Choose the [[http://bugzilla.xfce.org/page.cgi?id=fields.html#op_sys|OS]] - in most of the cases Linux, unless the bug affects all OS's. - * Set the correct [[http://bugzilla.xfce.org/page.cgi?id=fields.html#bug_severity|severity]] - * Do not change Priority, Initial_State, Flags, Requestee, Assign_To, or QA Contact - * If you wish to have Xfce notify you of any changes to this bug report, place your email address in CC - * Do not change Alias or URL - * Copy the Summary from the launchpad bug to Summary and add any keywords for later searches + * Copy the Summary from the Launchpad bug to Summary and add any keywords for later searches * Provide a complete description and a link to our bug in Launchpad. It is good to start with {{{ This bug has been reported on Ubuntu Launchpad as: https://bugs.launchpad.net/bugs/BUG_NUMBER }}} - * Check your report over and click on Commit to submit the report + * Check your report over submit the report - - After this follow the steps listed [[https://wiki.ubuntu.com/Bugs/Watches|here]] for linking the report to Launchpad. - - '''Example:''' [[https://bugs.launchpad.net/ubuntu/+source/xfdesktop4/+bug/124739|Launchpad report]] - [[http://bugzilla.xfce.org/show_bug.cgi?id=3461|Upstream report]] - - == Keywords and conventions == - - Since the simple search is based on finding the words in the summary and description, keywords are not used in the Xfce bugzilla. == Launchpad Bug Watch == - After you have forwarded the bug to Xfce's bugzilla you will want to create a "Bug Watch" in Launchpad that links the Ubuntu bug to the Xfce bug. This bug watch will be updated regularly and reflect the status of the upstream bug report. Details on creating one are found at [[Bugs/Watches]]. + After you have forwarded the bug upstream you will want to create a "Bug Watch" in Launchpad that links the Ubuntu bug to the LXDE bug. This bug watch will be updated regularly and reflect the status of the upstream bug report. Details on creating one are found at [[Bugs/Watches]]. - ##== States == - - ##== Following up == ---- CategoryBugSquad From noreply at ubuntu.com Thu Mar 19 05:03:38 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 19 Mar 2015 05:03:38 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Upstream=22_by_wxl?= Message-ID: <20150319050338.22218.46908@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Upstream" page has been changed by wxl: http://wiki.ubuntu.com/Bugs/Upstream?action=diff&rev1=24&rev2=25 Comment: added lxde * [[/GNOME]] * [[/KDE]] * [[/Xfce]] + * [[/LXDE]] * [[/Mozilla]] * [[/kernel]] * [[/Freedesktop]] (includes LibreOffice, X, and others) From zgiltd at gmail.com Wed Mar 25 06:10:10 2015 From: zgiltd at gmail.com (Zgi Ltd) Date: Wed, 25 Mar 2015 06:10:10 +0000 Subject: Connectivity Problem.. Message-ID: Sirs, I use my mobile phone (Vodafone 2G) to access internet on my laptop (Dell Vostro 1015) as i was using Ubuntu 12.4 for long and only now i have upgraded to 14.4.LTS. the problem is i am not able to get connectd thru bluetooth as whenever i am trying to connect thru mobile phone i get message " unable to pair with Ubuntu-0 " so when i am trying to pair thru my laptop i get message Error: connection refused (111) or sometimes the message says; successfully setup new device (my Nokia 6120 classic) and after that it reads.. detecting phone configuration and after a minute or two the following messages appears; Error: timed out detecting phone details. i am not able to get connected as i was earlier so please guide me what to do for getting connected successfully. Thank you. Saiad zgiltd at gmail.com From zgiltd at gmail.com Thu Mar 26 06:40:41 2015 From: zgiltd at gmail.com (Zgi Ltd) Date: Thu, 26 Mar 2015 12:10:41 +0530 Subject: Connectivity Problem after upgrading to Ubuntu 14.4 In-Reply-To: References: Message-ID: Hello.. As subjected above, i am facing connecting problem.. I use my mobile phone (Vodafone 2G) to access internet on my laptop (Dell Vostro 1015) as i was using Ubuntu 12.4 for long and only now i have upgraded to 14.4.LTS. the problem is i am not able to get connectd thru bluetooth as whenever i am trying to connect thru mobile i get message " unable to pair with Ubuntu-0 " so when i am trying to pair thru my laptop i get message Error: connection refused (111) or sometimes the message says; successfully setup new device (my Nokia 6120 classic) and after that it reads.. detecting phone configuration and after a minute or two the following messages appears; Error: timed out detecting phone details. i am not able to get connected as i was earlier so please guide me what to do for getting connected successfully. Thank you. Saiad zgiltd at gmail.com Mobile +8095968985 From es20490446e at gmail.com Thu Mar 26 20:40:34 2015 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Thu, 26 Mar 2015 21:40:34 +0100 Subject: Connectivity Problem after upgrading to Ubuntu 14.4 In-Reply-To: References: Message-ID: <55146EC2.1020408@gmail.com> Zgi Ltd: > i am not able to get connected as i was earlier so please guide me > what to do for getting connected successfully. I have already answered this in a different email. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3748 bytes Desc: S/MIME Cryptographic Signature URL: From es20490446e at gmail.com Fri Mar 27 23:35:32 2015 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 27 Mar 2015 23:35:32 -0000 Subject: [Bug 1407757] Re: multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed References: <20150105182457.24908.12851.malonedeb@wampee.canonical.com> Message-ID: <20150327233532.7626.89300.malone@chaenomeles.canonical.com> @ Ubuntu BugSquad In developers said that the problem is within the front-end , and not with dpkg. Do you know which is the front-end? ** Changed in: dpkg (Ubuntu) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu BugSquad, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1407757 Title: multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/1407757/+subscriptions From es20490446e at gmail.com Fri Mar 27 23:37:39 2015 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Fri, 27 Mar 2015 23:37:39 -0000 Subject: [Bug 1407757] Re: multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed References: <20150105182457.24908.12851.malonedeb@wampee.canonical.com> Message-ID: <20150327233739.23154.97692.malone@wampee.canonical.com> I have just realized that it's apt. ** Package changed: dpkg (Ubuntu) => apt (Ubuntu) ** Also affects: apt Importance: Undecided Status: New ** Changed in: apt (Ubuntu) Assignee: (unassigned) => Alberto Salvia Novella (es20490446e) ** Changed in: apt (Ubuntu) Status: Incomplete => In Progress ** Package changed: apt (Ubuntu) => unattended-upgrades (Ubuntu) ** Changed in: unattended-upgrades (Ubuntu) Assignee: Alberto Salvia Novella (es20490446e) => (unassigned) ** Also affects: unattended-upgrades Importance: Undecided Status: New ** No longer affects: apt ** Package changed: unattended-upgrades (Ubuntu) => aptdaemon (Ubuntu) ** No longer affects: unattended-upgrades ** Also affects: aptdaemon Importance: Undecided Status: New ** Changed in: aptdaemon (Ubuntu) Status: In Progress => Triaged ** Tags added: vivid ** Changed in: aptdaemon Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu BugSquad, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1407757 Title: multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed To manage notifications about this bug go to: https://bugs.launchpad.net/aptdaemon/+bug/1407757/+subscriptions From noreply at ubuntu.com Sun Mar 29 13:17:28 2015 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 29 Mar 2015 13:17:28 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKDE=22_by_penalvch?= Message-ID: <20150329131728.31328.48242@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKDE" page has been changed by penalvch: http://wiki.ubuntu.com/DebuggingKDE?action=diff&rev1=13&rev2=14 Comment: Added support note on missing -dbg symbols when using reporting assistant. 1. Crasher bugs - Log files from the crash incident are required to track down these. Some possible problems with bug reports include: - 1. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help. For KDE, this can be relevant e.g. in configuration dialogs. + 1. Hardware specific bugs - The developers may not have access to the hardware that triggers this bug. Certain log files and command outputs can help. For KDE, this can be relevant e.g. in configuration dialogs. 1. Package selection - [[DebuggingKDE#head-700ed3979b895dbb8fa78c9516ed89c536bea345|Help to find the right package]] = How to file = + See [[Kubuntu/Bugs/Reporting|Reporting Bugs]]. == Choosing the right package == + <> = Upstream = + == bugs.kde.org == + - Most parts of KDE use [[http://bugs.kde.org|KDE's Bug Tracking System]]. If you think a bug is in KDE and not Kubuntu specific, please search for it at [[http://bugs.kde.org|KDE's Bug Tracking System]] and file one there if need be. Link the upstream bug in the Launchpad bug by clicking "Also Effects Project." A bug with an upstream report should usually be "''Confirmed''" (you often shouldn't file it upstream if it's not). These bug reports can do a lot to improve the next version of KDE. + Most parts of KDE use [[http://bugs.kde.org|KDE's Bug Tracking System]]. If you think a bug is in KDE and not Kubuntu specific, please search for it at [[http://bugs.kde.org|KDE's Bug Tracking System]] and file one there if need be. Link the upstream bug in the Launchpad bug by clicking "Also Effects Project." A bug with an upstream report should usually be "''Confirmed''" (you often shouldn't file it upstream if it's not). These bug reports can do a lot to improve the next version of KDE. - == Projects using Launchpad == - === Katapult === = Bug tags = @@ -44, +46 @@ = Debugging procedure = + Every official KDE module has an additional package in the repository, suffixed with -dbg. + + == Debugging a crash == + + Applications by default on Kubuntu will generate useless backtraces when they crash. To get useful backtraces, all debugging symbols for the application need to be installed. + + When utilizing the Crash Reporting Assitant, this should give you the opportunity to install the necessary debug symbol packages. However, if one gets a window noting the following example: {{{ + Missing debug information packages + The packages containing debug information for the following application and libraries are missing: + /usr/bin/plasmashell + /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 + /usr/lib/x86_64-linux-gnu/libQt5Quick.so.5 + /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so + /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 + }}} Then one needs to manually enable the additional debugging symbols by folowing the instructions from [[https://wiki.ubuntu.com/DebuggingProgramCrash|here]]. + - For information on how to debug KDE applications, see: + For additional information on how to debug KDE applications, see: * http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging * http://techbase.kde.org/index.php?title=Development/Tutorials/Debugging/How_to_create_useful_crash_reports * http://techbase.kde.org/index.php?title=Development/FAQs/Debugging_FAQ + = How to Triage = - == Packages with Debugging Symbols == - Applications as installed by default on Kubuntu will generate useless backtraces when they crash. To get useful backtraces, you need to install the package with debugging symbols for the application. - Every official KDE module has an additional package in the repository, suffixed with -dbg. Always install kdelibs-dbg, because all KDE applications use kdelibs. Then you should install a -dbg package for the application which crashed. For example if KOrganizer crashed you should install kdepim-dbg as well. See [[DebuggingKDE#head-700ed3979b895dbb8fa78c9516ed89c536bea345|choosing the right package]] to help figure out what module an application is in. For KDE4 on Hardy, these will be -dbg-kde4. - - = How to Triage = - You can find information on what triaging is and how to do it at [[Bugs/HowToTriage|HowToTriage]]. Here are some pointers as well: + You can find information on what triaging is and how to do it at [[Bugs/HowToTriage|HowToTriage]]. Here are some pointers as well: == What does triaging bugs mean? == + * Responding to new bugs as they are filed. * Reproducing and confirming bug reports. * Asking the reporter to provide missing information. * Searching for duplicates in the bug tracking system. - * Sending bugs to their upstream authors, when applicable. For KDE this is http://bugs.kde.org + * Sending bugs to their upstream authors, when applicable. For KDE this is [[http://bugs.kde.org]]. * Cross-referencing bugs from other distributions. * Classifying bugs by package. * Prioritizing bugs. * Expiring old bugs with missing information and no response. == Suggestions and rules == + * Read the wiki pages: * UbuntuBugDay * HelpingWithBugs @@ -76, +92 @@ * BugSquad * [[Bugs/Responses]] * '''Be polite!''' - * Unconfirmed ("''New''") bugs are a priority. An unconfirmed bug isn't of much use to a developer or to the reporter. It's a waste of developers' time to try to figure out if things are even real bugs, so that's our job. Do your best to reproduce bugs so that you can confirm them. + * Unconfirmed ("''New''") bugs are a priority. An unconfirmed bug isn't of much use to a developer or to the reporter. It's a waste of developers' time to try to figure out if things are even real bugs, so that's our job. Do your best to reproduce bugs so that you can confirm them. - * Bug reports often lack essential information required to fix them or to find out if they are already fixed. This can range from basic information such as what release they are using or even what program the bug is in to slightly more complex things like stack traces for crashes. Ask the reporter for any missing information. Be clear and polite. When you ask questions, mark the bug status as "''Incomplete''" until all the required information is provided. If you can reproduce the bug, provide the information yourself and mark "Confirmed." + * Bug reports often lack essential information required to fix them or to find out if they are already fixed. This can range from basic information such as what release they are using or even what program the bug is in to slightly more complex things like stack traces for crashes. Ask the reporter for any missing information. Be clear and polite. When you ask questions, mark the bug status as "''Incomplete''" until all the required information is provided. If you can reproduce the bug, provide the information yourself and mark "Confirmed." - * Duplicate bug reports are common. When you are looking at a new bug, open up another window and do an advanced search for similar bugs, including ALL bugs -- closed and open. If you are certain a bug report is a duplicate, mark it that way and comment on the bug to inform the reporter. Usual responses for this can be found [[https://wiki.ubuntu.com/Bugs/Responses#head-c9465ec0d0c312bab06eac061dbdc6d2071204d1|here]]. Other than this, avoid commenting on bugs marked as duplicates -- comment on the root bug. + * Duplicate bug reports are common. When you are looking at a new bug, open up another window and do an advanced search for similar bugs, including ALL bugs -- closed and open. If you are certain a bug report is a duplicate, mark it that way and comment on the bug to inform the reporter. Usual responses for this can be found [[https://wiki.ubuntu.com/Bugs/Responses#head-c9465ec0d0c312bab06eac061dbdc6d2071204d1|here]]. Other than this, avoid commenting on bugs marked as duplicates -- comment on the root bug. - * Many bugs have already been fixed. For older bugs that you cannot reproduce, ask if the reporter is sill having the problem. If the problem was fixed with an update that can be identified, you can close the bug as "''Fix Released''". If the problem just magically went away, close the bug as "''Invalid''". + * Many bugs have already been fixed. For older bugs that you cannot reproduce, ask if the reporter is sill having the problem. If the problem was fixed with an update that can be identified, you can close the bug as "''Fix Released''". If the problem just magically went away, close the bug as "''Invalid''". - * Bugs that are marked as "''Incomplete''" for over 3 months with a clear request for information but ''without a response'' that you ''can't reproduce'' aren't particularly useful. They should be closed as "''Invalid''". When closing a bug for this reason, be polite and inform the reporter why you are closing it, and tell them that they can reopen the bug if they still have the problem and can provide the needed information. Some responses for this can be found [[https://wiki.ubuntu.com/Bugs/Responses#head-aa72b6a41481a1304f6cc8dc0b076db1c288ff10|here]]. + * Bugs that are marked as "''Incomplete''" for over 3 months with a clear request for information but ''without a response'' that you ''can't reproduce'' aren't particularly useful. They should be closed as "''Invalid''". When closing a bug for this reason, be polite and inform the reporter why you are closing it, and tell them that they can reopen the bug if they still have the problem and can provide the needed information. Some responses for this can be found [[https://wiki.ubuntu.com/Bugs/Responses#head-aa72b6a41481a1304f6cc8dc0b076db1c288ff10|here]]. - * If you think a bug is in KDE and not Kubuntu specific, please search for it at [[http://bugs.kde.org|KDE's Bug Tracking System]] and file one there if need be. Link the upstream bug in the Launchpad bug by clicking "Also Effects Project." A bug with an upstream report should usually be "''Confirmed''" (you often shouldn't file it upstream if it's not). These bug reports can do a lot to improve the next version of KDE. + * If you think a bug is in KDE and not Kubuntu specific, please search for it at [[http://bugs.kde.org|KDE's Bug Tracking System]] and file one there if need be. Link the upstream bug in the Launchpad bug by clicking "Also Effects Project." A bug with an upstream report should usually be "''Confirmed''" (you often shouldn't file it upstream if it's not). These bug reports can do a lot to improve the next version of KDE. - * Pick an application that you use a lot, and concentrate on it. This helps narrow down the list of bugs you are looking at and makes the work much more manageable. It also helps to be knowledgeable in the program(s) you are doing bug work for. + * Pick an application that you use a lot, and concentrate on it. This helps narrow down the list of bugs you are looking at and makes the work much more manageable. It also helps to be knowledgeable in the program(s) you are doing bug work for. - * If you have some rare configuration, look at bugs relating to it. For example, if you have a dual monitor setup, try to confirm some xinerama/xrandr related bugs. This is particularly helpful since many other people who come across those bugs have no way of doing anything with them. + * If you have some rare configuration, look at bugs relating to it. For example, if you have a dual monitor setup, try to confirm some xinerama/xrandr related bugs. This is particularly helpful since many other people who come across those bugs have no way of doing anything with them. * Keep all this in mind when filing your own bugs. * Don't confirm your own bugs. - * Don't duplicate efforts. If there is already someone working on a bug and asking the right questions, move on to another one. There are plenty to go around. + * Don't duplicate efforts. If there is already someone working on a bug and asking the right questions, move on to another one. There are plenty to go around. * Keep in mind that while closing bugs is important, the key is that the bugs are FIXED. - * DO get on '''#ubuntu-bugs''' and '''#kubuntu-bugs''' if you need help, to discuss bugs, and to watch for incoming bugs. #ubuntu+1 can also be useful to discuss development release problems with other users. Don't use #kubuntu for this. + * DO get on '''#ubuntu-bugs''' and '''#kubuntu-bugs''' if you need help, to discuss bugs, and to watch for incoming bugs. #ubuntu+1 can also be useful to discuss development release problems with other users. Don't use #kubuntu for this. - == Stock Reply == @@ -97, +112 @@ = Known bugs = - TODO: Description of known bug reports that may receive duplicates and how to recognise them. This information should be obtained by looking for bugs tagged as 'metabug'. + == Other useful bug lists == - '''Open''' - || '''Bug''' || '''Subject''' || '''Symptom''' || - || [[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896|#8896]] || The subject from LP || This bug can be identified by ... || - - '''Closed''' - || '''Bug#''' || '''Subject''' || '''Symptom''' || - || [[https://bugs.beta.launchpad.net/ubuntu/+source/synaptic/+bug/8896|#8896]] || The subject from LP || This bug can be identified by ... || - - == Other useful bug lists == Here are the major Kubuntu Desktop packages and their bugs: https://launchpad.net/~kubuntu-team/+packagebugs A [[https://bugs.launchpad.net/ubuntu/?field.searchtext=kde+%7C+kubuntu&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&assignee_option=any&field.assignee=&field.owner=&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_no_package.used=|vague list]] of all the unconfirmed bugs in Kubuntu. - = Non-bugs = + = FAQ = - TODO: How to recognise common issues arising from hardware failures, common feature requests and other invalid bugs for this category. Advice how triage them and stock responses. - - = FAQ = - Why can't I change the importance of bugs? Why can't I set Won't Fix or Triaged status? + Why can't I change the importance of bugs? Why can't I set Won't Fix or Triaged status? - You need to be a member of the ubuntu-bugcontrol team on launchpad to change the importance of bugs. This is mostly so people are responsible and don't raise the importance of their own bugs. Get someone to help you and set it for you, and consider applying for membership once you have some experience. See UbuntuBugControl for more information. + You need to be a member of the ubuntu-bugcontrol team on launchpad to change the importance of bugs. This is mostly so people are responsible and don't raise the importance of their own bugs. Get someone to help you and set it for you, and consider applying for membership once you have some experience. See UbuntuBugControl for more information. = Also see = From 1407757 at bugs.launchpad.net Fri Mar 27 23:29:16 2015 From: 1407757 at bugs.launchpad.net (Launchpad Bug Tracker) Date: Fri, 27 Mar 2015 23:29:16 -0000 Subject: [Bug 1407757] [NEW] multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed References: <20150105182457.24908.12851.malonedeb@wampee.canonical.com> Message-ID: <20150327232916.7387.71457.launchpad@soybean.canonical.com> You have been subscribed to a public bug by Alberto Salvia Novella (es20490446e): HOW TO REPRODUCE: - Install an affected package. EXPECTED BEHAVIOUR: - The package to be installed. REAL BEHAVIOUR: - The package cannot be installed due to dpkg wrongly detecting them as already installed. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libpam-systemd:amd64 204-5ubuntu20.9 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 CrashReports:  640:0:0:1458151:2015-01-05 12:18:11.086621522 -0600:2015-01-05 12:18:12.086621522 -0600:/var/crash/libnss3:amd64.0.crash  600:0:0:217380:2015-01-05 12:17:09.359944581 -0600:2015-01-05 12:17:10.359944581 -0600:/var/crash/libpam-systemd:amd64.0.crash  644:0:0:0:2015-01-05 12:18:13.122599379 -0600:2015-01-05 12:18:13.122599379 -0600:/var/crash/libnss3:amd64.0.upload  600:0:0:217372:2015-01-05 12:17:10.375944347 -0600:2015-01-05 12:17:10.363944604 -0600:/var/crash/libnss3-nssdb.0.crash Date: Mon Jan 5 12:17:10 2015 DuplicateSignature: package:libpam-systemd:amd64:204-5ubuntu20.9:package libpam-systemd:amd64 is already installed and configured ErrorMessage: package libpam-systemd:amd64 is already installed and configured InstallationDate: Installed on 2015-01-04 (1 days ago) InstallationMedia: Mythbuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: dpkg Title: package libpam-systemd:amd64 204-5ubuntu20.9 failed to install/upgrade: package libpam-systemd:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dpkg (Ubuntu) Importance: Critical Status: Triaged ** Tags: already-installed amd64 apport-package asked-to-upstream trusty utopic -- multi-arch packages cannot be installed due to dpkg wrongly detecting them as already installed https://bugs.launchpad.net/bugs/1407757 You received this bug notification because you are a member of Ubuntu BugSquad, which is subscribed to the bug report.