From noreply at ubuntu.com Sun Aug 10 02:31:55 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 10 Aug 2014 02:31:55 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Tags=22_by_nathanst?= Message-ID: <20140810023155.20265.81521@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Tags" page has been changed by nathanst: http://wiki.ubuntu.com/Bugs/Tags?action=diff&rev1=193&rev2=194 Comment: disable inclusion of DebuggingNetworkManager tag listing (since the listing has been removed from that page) || '''Tag''' || '''Use case''' || || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-error|`gstreamer-error`]] || Bug is related to bad drivers and not Cheese; ''Switch bug to related package(`linux` for missing/bad drivers)''|| || [[https://launchpad.net/ubuntu/+bugs?field.tag=gstreamer-ok|`gstreamer-ok`]] || Video gstreamer input works fine (drivers seem fine), most likely a Cheese bug || - + g + ##It appears the "Bug Tags" section of the DebuggingNetworkManager page was removed in revision 48, so there's no longer anything to include here... (see https://wiki.ubuntu.com/DebuggingNetworkManager?action=diff&rev1=47&rev2=48 ) - === Network Manager === + ##=== Network Manager === - <> + ##<> === Unity === From noreply at ubuntu.com Sun Aug 10 23:45:00 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 10 Aug 2014 23:45:00 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingModemmanager=22_by_es20?= =?utf-8?q?490446e?= Message-ID: <20140810234500.23144.84796@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingModemmanager" page has been changed by es20490446e: http://wiki.ubuntu.com/DebuggingModemmanager?action=diff&rev1=14&rev2=15 {{{ # get the latest mm-test.py from git - wget http://cgit.freedesktop.org/ModemManager/ModemManager/plain/test/mm-test.py + https://github.com/openshine/ModemManager/blob/master/test/mm-test.py # and run mm-test.py (with modem-manager running) python ./mm-test.py From noreply at ubuntu.com Sun Aug 10 23:55:19 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 10 Aug 2014 23:55:19 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingModemmanager=22_by_es20?= =?utf-8?q?490446e?= Message-ID: <20140810235519.23156.74725@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingModemmanager" page has been changed by es20490446e: http://wiki.ubuntu.com/DebuggingModemmanager?action=diff&rev1=15&rev2=16 {{{ # get the latest mm-test.py from git - https://github.com/openshine/ModemManager/blob/master/test/mm-test.py + https://raw.githubusercontent.com/openshine/ModemManager/master/test/mm-test.py # and run mm-test.py (with modem-manager running) python ./mm-test.py From webmaster at ubuntu.com Fri Aug 15 10:57:27 2014 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 15 Aug 2014 10:57:27 -0000 Subject: =?utf-8?q?=5BCommunity_Help_Wiki=5D_Update_of_=22ReportingBugs=22_by_ivan?= =?utf-8?q?ovm?= Message-ID: <20140815105727.3797.25083@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Help Wiki" for change notification. The "ReportingBugs" page has been changed by ivanovm: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=267&rev2=268 - #title Reporting Bugs - HowTo - #language en + nstallArchives() failed: Selecting previously unselected package synaptic. + (Reading database ... + (Reading database ... 5% + (Reading database ... 10% + (Reading database ... 15% + (Reading database ... 20% + (Reading database ... 25% + (Reading database ... 30% + (Reading database ... 35% + (Reading database ... 40% + (Reading database ... 45% + (Reading database ... 50% + (Reading database ... 55% + (Reading database ... 60% + (Reading database ... 65% + (Reading database ... 70% + (Reading database ... 75% + (Reading database ... 80% + (Reading database ... 85% + (Reading database ... 90% + (Reading database ... 95% + (Reading database ... 100% + (Reading database ... 387382 files and directories currently installed.) + Preparing to unpack .../synaptic_0.81.1ubuntu1_amd64.deb ... + Unpacking synaptic (0.81.1ubuntu1) ... + Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... + Rebuilding /usr/share/applications/bamf-2.index... + Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... + Processing triggers for mime-support (3.54ubuntu1) ... + Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... + Processing triggers for hicolor-icon-theme (0.13-1) ... + Processing triggers for man-db (2.6.7.1-1) ... + Setting up tex-common (4.04) ... + Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! + Running mktexlsr. This may take some time... done. + Running updmap-sys. This may take some time... + updmap-sys failed. Output has been stored in + /tmp/updmap.b3XNDxHN + Please include this file if you report a bug. - <> + Sometimes, not accepting conffile updates in /etc/texmf/updmap.d + causes updmap-sys to fail. Please check for files with extension + .dpkg-dist or .ucf-dist in this directory - ||<>|| + No apport report written because the error message indicates its a followup error from a previous failure. + No apport report written because the error message indicates its a followup error from a previous failure. + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + No apport report written because MaxReports is reached already + dpkg: error processing package tex-common (--configure): + subprocess installed post-installation script returned error exit status 1 + dpkg: dependency problems prevent configuration of latex-sanskrit: + latex-sanskrit depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - = Bug reporting etiquette = + dpkg: error processing package latex-sanskrit (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of lmodern: + lmodern depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + dpkg: error processing package lmodern (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of tex-gyre: + tex-gyre depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. While this is targeted to the new bug reporter, experienced reporters would find these tips invaluable in getting their bugs looked at by a developer and ultimately fixed: - <
><
> - Before filing any linux kernel related reports on Launchpad, please '''update your BIOS''', and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. freezing after lightDM login, intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collateral damage avoidance. For more about BIOS updates, please see [[https://help.ubuntu.com/community/BiosUpdate|here]]. - <
><
> - Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem. - <
><
> - '''Please do not speculate on what you think is or isn't a duplicate report''' (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, if you are the original reporter, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. If you are not the original reporter, it's best to file a new report, so that necessary debugging attachments are reviewed. It is a common misconception that filing a potential duplicate report is wasteful. Filing potential duplicates isn't wasteful, and is actually preferred to ease triaging. - <
><
> - Please '''do not quote Wikipedia''' and other non-primary resource information as fact on [[Launchpad]]. - <
><
> - Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed. - <
><
> - '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox. - <
><
> - For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, you run the strong risk of it not being attended to upstream. - <
><
> - Please '''do not solicit non-original reporters to post comments, attachments, etc.''' - <
><
> - Please '''do not post comments such as “Me too!”, “+1”, “bump”, “same here”, etc.,''' as it is largely unhelpful, produces spammy e-mail traffic to everyone subscribed to the report, and quite often turns out not to be the same root cause. Instead, please follow the below mentioned procedures. - <
><
> - If a triager or developer asks you for some information on reproducing or testing, please do make them dumpster dive by just posting a URL, or saying you already did something in some other report. Instead, put the full reproduction or testing results into the report itself, and if you have to, then post the link. - <
><
> - Please '''do not stack multiple issues into one report'''. For example, jamming suspend and hibernate into one report, reporting multiple [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] problems into one report (ex. Fn+F3 doesn't turn off my laptop WiFi, Fn+Right doesn't turn the brightness on my [[https://wiki.ubuntu.com/Kernel/Debugging/Backlight|backlight]] down, my brightness settings are not remembered after reboot, etc.). Please make one report for each individual problem. - <
><
> - Please '''do not complain''' about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, “I cannot believe it’s not fixed…”, XYZ person(s) do not care about fixing bugs, etc. Especially, if you have not followed the directions mentioned in this article, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your e-mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources. - <
><
> - Please '''keep the bug objective''' as possible. It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large. - <
><
> - Please '''provide all relevant information from [[https://wiki.ubuntu.com/DebuggingProcedures]] when you first report your bug'''. This is one of the top reasons why bugs do not get marked [[https://wiki.ubuntu.com/Bugs/Status|Triaged]], as the minimum requirements for dealing with the problem by a developer are not provided. - <
><
> - If a triager or developer asks you to provide information, please '''avoid arguing''' with them and just provide the information as requested. This is due to how not everyone has access to the hardware you are reporting against, so having you provide the information helps eliminate the difficulty in fixing your bug. If you have a strong disagreement with what a triager or developer is asking of you, please resolve it with them via personal message, instead of turning a bug development report into a “let’s talk about talking about the problem” report. The Ubuntu community takes a favor to objective, technical discourse. - <
><
> - Please '''do not report bugs about software in [[PPA]]s''' on Launchpad. This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag `ppa`. - <
><
> - Please '''do not add project tasks to bug reports that are invalid because they are not supported'''. For example, if you were using the LibreOffice PPA and reported a bug against the package libreoffice (Ubuntu), which would be marked Status Invalid, please do not add the Launchpad Project [[https://launchpad.net/df-libreoffice|df-libreoffice]] to the report, or change the package libreoffice (Ubuntu) to the project df-libreoffice. The purposes of adding the upstream project to a report is to track valid bugs in Ubuntu that are valid upstream, and may have been reported upstream, not to start another upstream bug tracker. - <
><
> - When posting new comments to a report, please do not include every past comment made, as doing so makes it onerous to read a report, and is wasteful. Instead just make your new comment, or just include the relevant portion of a previous comment you are responding to. - <
><
> - '''Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments.''' - - = How to report bugs = - Ubuntu uses [[Launchpad]] to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report. + dpkg: error processing package tex-gyre (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-latex-base: + texlive-latex-base depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - == Create a Launchpad account == + dpkg: error processing package texlive-latex-base (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-generic-recommended: + texlive-generic-recommended depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - If you don’t already have one - you need to [[https://help.launchpad.net/YourAccount/NewAccount|create a Launchpad account]]. This will allow you to file new bugs and comment on existing ones. + dpkg: error processing package texlive-generic-recommended (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-pstricks: + texlive-pstricks depends on texlive-generic-recommended (>= 2013.20130512); however: + Package texlive-generic-recommended is not configured yet. + texlive-pstricks depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - == Determine if the bug is really a bug == + dpkg: error processing package texlive-pstricks (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of asymptote: + asymptote depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + asymptote depends on texlive-pstricks; however: + Package texlive-pstricks is not configured yet. + asymptote depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - You should not file a bug if you are: + dpkg: error processing package asymptote (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-latex-recommended: + texlive-latex-recommended depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. + texlive-latex-recommended depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - * '''Requesting new software:''' you should follow the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages - * '''Requesting support:''' there are a multitude of ways you can get help using Ubuntu, such as the [[https://answers.launchpad.net/ubuntu|Launchpad answer tracker]], the [[http://askubuntu.com/|Ask Ubuntu]] site, the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, and the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list. - * '''Discussing features and existing policy:''' this belongs to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. - * '''Proposing features and ideas:''' you should submit your idea to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. - * '''Filing a bug against a program not provided by an Ubuntu package:''' You should file a bug in that program's bug tracking interface. Instructions are generally available on the program's web site. + dpkg: error processing package texlive-latex-recommended (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of cm-super-minimal: + cm-super-minimal depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + cm-super-minimal depends on texlive-latex-recommended; however: + Package texlive-latex-recommended is not configured yet. - /!\ If you want to file a translation or misspelling bug, follow the instructions [[#translation|here]]. - - == Make sure the bug hasn’t already been reported == + dpkg: error processing package cm-super-minimal (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of cm-super: + cm-super depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + cm-super depends on texlive-latex-recommended; however: + Package texlive-latex-recommended is not configured yet. + cm-super depends on cm-super-minimal (= 0.3.4-9); however: + Package cm-super-minimal is not configured yet. - First, check the release notes for your version of Ubuntu: - * [[http://www.ubuntu.com/getubuntu/releasenotes/1004|Ubuntu 10.04 LTS (Lucid Lynx)]] - * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]] - * [[https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes#Known_issues|Ubuntu 13.10 (Saucy Salamander)]] - * [[https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues|Ubuntu 14.04 (Trusty Tahr)]] + dpkg: error processing package cm-super (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-metapost: + texlive-metapost depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - === Hardware driver bugs (e.g. sound, Linux kernel, X.Org, and Nvidia / AMD proprietary drivers) === + dpkg: error processing package texlive-metapost (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of context: + context depends on texlive-metapost (>= 2013); however: + Package texlive-metapost is not configured yet. + context depends on lmodern (>= 2.004.4); however: + Package lmodern is not configured yet. + context depends on tex-gyre; however: + Package tex-gyre is not configured yet. + context depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - * For hardware driver bugs you are welcome to check for duplicates. However, depending on if you are the original reporter or not, determines what to do next. The following is a list of hardware packages: - * For sound bugs please see [[https://wiki.ubuntu.com/DebuggingSoundProblems]]. - * [[https://launchpad.net/ubuntu/+source/linux|Linux]] kernel (e.g. suspend, hibernate, and other [[https://wiki.ubuntu.com/DebuggingProcedures#Kernel|potential kernel issues]]). - * [[https://launchpad.net/ubuntu/+source/xorg|xorg]] and [[https://launchpad.net/ubuntu/+source/xorg-server|xorg-server]] - * [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]] (e.g. [[https://wiki.ubuntu.com/DebuggingTouchpadDetection|certain Touchpad issues]]). - * [[https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel|xserver-xorg-video-intel]] and other xserver-xorg-video-* like nouveau, radeon, ati, openchrome, geode, etc. - * Nvidia proprietary driver software: [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers|nvidia-graphics-drivers]] , [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173|graphics-drivers-173]] , [[https://launchpad.net/ubuntu/+source/nvidia-settings|nvidia-settings]] , and [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180|nvidia-graphics-drivers-180]] . - * AMD proprietary drivers: [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer|fglrx-installer]] and [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates|fglrx-installer-updates]]. + dpkg: error processing package context (--configure): + dependency problems - leaving unconfigured + Setting up emacsen-common (2.0.7) ... + Install emacsen-common for emacs23 + emacsen-common: Handling install of emacsen flavor emacs23 + Warning: Lisp directory `/usr/local/share/emacs/23.4/site-lisp' does not exist. + Wrote /etc/emacs23/site-start.d/00debian-vars.elc + Wrote /usr/share/emacs23/site-lisp/debian-startup.elc + Install emacsen-common for xemacs21 + emacsen-common: Handling install of emacsen flavor xemacs21 - ==== You are not the original reporter ==== + WARNING: + Couldn't find obvious defaults for: + data-directory + mule-lisp-directory + lisp-directory + Perhaps some directories don't exist, or the XEmacs executable, + /usr/bin/xemacs21 + is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... + Loading 00debian... + Error while loading 00debian: Symbol's function definition is void: loop + Loading 00debian-vars... + Loading 50asymptote... + Loading 50devhelp... + Loading 50dictionaries-common... + Error while loading 50dictionaries-common: No /usr/local/ prefixed paths in load-path + Loading 50gettext... + Loading 50latex-cjk-common... + Error while loading 50latex-cjk-common: Cannot open load file: cjk-enc + Loading 50latex-cjk-thai... + Symbol's function definition is void: dolist + xemacs exiting + . + ERROR: install script from emacsen-common package failed + dpkg: error processing package emacsen-common (--configure): + subprocess installed post-installation script returned error exit status 1 + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of emacs23-common: + emacs23-common depends on emacsen-common (>= 1.4.10); however: + Package emacsen-common is not configured yet. - * Please '''open a new report''' instead of adding debugging information, attachments, apport-collect’ing, or “Me too!” comments on what may appear to be a similar bug. Chances are that your hardware does not match the existing bug’s hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug. - * Please do not assume because you have the same desktop or laptop model line as another original reporter’s bug report, that your problem is the same. Frequently, computer vendors use different parts under the hood within the same model line. - * Regarding peripherals, please do not assume because you have the same peripheral, and similar problems, it is the same bug. Please file a new bug report. + dpkg: error processing package emacs23-common (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of emacs23-bin-common: + emacs23-bin-common depends on emacs23-common (= 23.4+1-4.1ubuntu1); however: + Package emacs23-common is not configured yet. - ==== You are the original reporter ==== + No apport report written because MaxReports is reached already + dpkg: error processing package emacs23-bin-common (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of emacs23: + emacs23 depends on emacs23-bin-common (= 23.4+1-4.1ubuntu1); however: + Package emacs23-bin-common is not configured yet. - If you are the original reporter, here are the ways to maximize the speed with which your bug is fixed: - * Check for the problem in the earliest release that works for your hardware and the latest. Report your testing results in the report. - * Test for this problem in the mainline kernel following [[https://wiki.ubuntu.com/Kernel/MainlineBuilds]]. Report your mainline testing results in the report. - * If your bug is a regression, bisect it following [[https://wiki.ubuntu.com/Kernel/KernelBisection]]. Report your bisect results in the report. - - === Desktop Applications === + dpkg: error processing package emacs23 (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-font-utils: + texlive-font-utils depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - For [[https://wiki.ubuntu.com/DebuggingProcedures#Desktop_Applications|desktop applications]], please make sure it has not already been reported by searching through [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]]. If you find an already reported bug that is exactly like the problem you have, please feel free to add this information to the existing report, rather than opening a new one. However, if you have any doubt as to it being the same or not, please file a separate report. + dpkg: error processing package texlive-font-utils (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-extra-utils: + texlive-extra-utils depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + texlive-extra-utils depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. - [[#Top|Back to top]] + dpkg: error processing package texlive-extra-utils (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of feynmf: + feynmf depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + feynmf depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + feynmf depends on texlive-font-utils; however: + Package texlive-font-utils is not configured yet. + feynmf depends on texlive-extra-utils; however: + Package texlive-extra-utils is not configured yet. - == Reporting an application crash in the development release == + dpkg: error processing package feynmf (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of xemacs21-mule: + xemacs21-mule depends on emacsen-common; however: + Package emacsen-common is not configured yet. - Please report an application crash via the methods outlined below and at [[https://wiki.ubuntu.com/DebuggingProgramCrash]]. + dpkg: error processing package xemacs21-mule (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of xemacs21: + xemacs21 depends on xemacs21-mule (>= 21.4.22-4ubuntu3) | xemacs21-mule-canna-wnn (>= 21.4.22-4ubuntu3) | xemacs21-nomule (>= 21.4.22-4ubuntu3); however: + Package xemacs21-mule is not configured yet. + Package xemacs21-mule-canna-wnn is not installed. + Package xemacs21-nomule is not installed. - If an application crashes, and you're using a development release, Apport will start automatically, raising an appropriate bug report for you to complete in Launchpad. This report is subsequently processed by [[Apport Retracing Service]], in order to provide developers with debugging information that make it easier to fix the problem. + dpkg: error processing package xemacs21 (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of xemacs21-support: + xemacs21-support depends on emacsen-common; however: + Package emacsen-common is not configured yet. + xemacs21-support depends on xemacs21 (= 21.4.22-4ubuntu3); however: + Package xemacs21 is not configured yet. - == Reporting an application crash in the stable release == + dpkg: error processing package xemacs21-support (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of gettext-el: + gettext-el depends on emacs24 | emacs23 | emacsen; however: + Package emacs24 is not installed. + Package emacs23 is not configured yet. + Package emacsen is not installed. + Package xemacs21-mule which provides emacsen is not configured yet. + Package emacs23 which provides emacsen is not configured yet. - Apport may come disabled by default. To enable it, edit the file: - {{{ - /etc/default/apport - }}} + dpkg: error processing package gettext-el (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-fonts-recommended: + texlive-fonts-recommended depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - and change: - {{{ - enabled=0 - }}} + dpkg: error processing package texlive-fonts-recommended (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of tipa: + tipa depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + tipa depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - to: - {{{ - enabled=1 - }}} + dpkg: error processing package tipa (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of jadetex: + jadetex depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + jadetex depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + jadetex depends on texlive-fonts-recommended; however: + Package texlive-fonts-recommended is not configured yet. + jadetex depends on texlive-latex-recommended; however: + Package texlive-latex-recommended is not configured yet. + jadetex depends on texlive-generic-recommended; however: + Package texlive-generic-recommended is not configured yet. + jadetex depends on tipa; however: + Package tipa is not configured yet. + dpkg: error processing package jadetex (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-xcolor: + latex-xcolor depends on texlive-latex-recommended; however: + Package texlive-latex-recommended is not configured yet. + latex-xcolor depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release (see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To file a report on Launchpad anyway, one may open the following file via a command line: {{{ - gksudo gedit /etc/apport/crashdb.conf - }}} and change: {{{ - 'problem_types': ['Bug', 'Package'], - }}} to: {{{ - # 'problem_types': ['Bug', 'Package'], - }}} - Save, close, and try to file the crash report again via: {{{ - ubuntu-bug /var/crash/_my_crash_report.crash - }}} - /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. + dpkg: error processing package latex-xcolor (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-beamer: + latex-beamer depends on tex-common (>= 4); however: + Package tex-common is not configured yet. + latex-beamer depends on latex-xcolor (>= 2.00-1); however: + Package latex-xcolor is not configured yet. + latex-beamer depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. - == Reporting a system crash == + dpkg: error processing package latex-beamer (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-common: + latex-cjk-common depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + latex-cjk-common depends on texlive-font-utils (>= 2007.dfsg.2-1); however: + Package texlive-font-utils is not configured yet. + latex-cjk-common depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - If your system lockups up, freezes, logs you out, etc., then this is not an application crash, but a system crash. Please see below, and consult the following article for these types of problems [[https://help.ubuntu.com/community/DebuggingSystemCrash]]. + dpkg: error processing package latex-cjk-common (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-chinese: + latex-cjk-chinese depends on latex-cjk-common (= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-common is not configured yet. + latex-cjk-chinese depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - == Reporting non-crash hardware and desktop application bugs == + dpkg: error processing package latex-cjk-chinese (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-japanese: + latex-cjk-japanese depends on latex-cjk-common (= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-common is not configured yet. + latex-cjk-japanese depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - The method for reporting bugs in Ubuntu is by using the tool “ubuntu-bug”, otherwise known as '''Apport'''. When reporting a bug, you must tell Apport which program or [[https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?|package]] is at fault. + dpkg: error processing package latex-cjk-japanese (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-korean: + latex-cjk-korean depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-common is not configured yet. + latex-cjk-korean depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - === Collecting information from a specific package === + dpkg: error processing package latex-cjk-korean (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-lang-other: + texlive-lang-other depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - Press Alt+F2 to open the “Run Command” screen: - - ||{{attachment:unity-ubuntu-bug-pkgname.png|Filing a bug with the “Run Command” screen}}|| + dpkg: error processing package texlive-lang-other (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-thai: + latex-cjk-thai depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-common is not configured yet. + latex-cjk-thai depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. + latex-cjk-thai depends on tex-common (>= 4); however: + Package tex-common is not configured yet. + latex-cjk-thai depends on texlive-lang-other (>= 2013.20130523-1); however: + Package texlive-lang-other is not configured yet. - Then, type `ubuntu-bug ` and press Enter. If you’re not sure which package has the problem, refer to the instructions for [[https://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]. + dpkg: error processing package latex-cjk-thai (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of latex-cjk-all: + latex-cjk-all depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-common is not configured yet. + latex-cjk-all depends on latex-cjk-chinese (>= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-chinese is not configured yet. + latex-cjk-all depends on latex-cjk-japanese (>= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-japanese is not configured yet. + latex-cjk-all depends on latex-cjk-korean (= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-korean is not configured yet. + latex-cjk-all depends on latex-cjk-thai (= 4.8.3+git20120914-2ubuntu1); however: + Package latex-cjk-thai is not configured yet. - === Collecting information about a program with a window open === + dpkg: error processing package latex-cjk-all (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of latexmk: + No apport report written because MaxReports is reached already + latexmk depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. - If you want to file a bug about an application but you don't know what that application's package name is, if it has an open window you are in luck. + dpkg: error processing package latexmk (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of m-tx: + m-tx depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - In a terminal execute the command 'ubuntu-bug -w'. + dpkg: error processing package m-tx (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of musixtex: + musixtex depends on tex-common (>= 4); however: + Package tex-common is not configured yet. - ||{{attachment:ubuntu-bug-w.png | terminal with ubuntu-bug -w }}|| + dpkg: error processing package musixtex (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of pmx: + pmx depends on tex-common (>= 4); however: + Package tex-common is not configured yet. + pmx depends on texlive-latex-base; however: + Package texlive-latex-base is not configured yet. - After you close the dialog the next window that you click on will have a problem report created for the package that created the window. + dpkg: error processing package pmx (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of purifyeps: + purifyeps depends on texlive-metapost; however: + Package texlive-metapost is not configured yet. - === Collecting information from a currently running program === + dpkg: error processing package purifyeps (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive: + texlive depends on texlive-latex-recommended (>= 2013.20130512); however: + Package texlive-latex-recommended is not configured yet. + texlive depends on texlive-fonts-recommended (>= 2013.20130512); however: + Package texlive-fonts-recommended is not configured yet. + texlive depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. - To file a bug against a program that is currently running, open the System Monitor application and find the ID of the process. + dpkg: error processing package texlive (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-bibtex-extra: + texlive-bibtex-extra depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + texlive-bibtex-extra depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. - ||{{attachment:system-monitor-id-new.png | System Monitor Processes tab }}|| + dpkg: error processing package texlive-bibtex-extra (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-fonts-extra: + texlive-fonts-extra depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - Then type "ubuntu-bug " followed by the process ID into the “Run Command” screen. + dpkg: error processing package texlive-fonts-extra (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-fonts-extra-doc: + texlive-fonts-extra-doc depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - ||{{attachment:unity-ubuntu-bug-pid.png | Filing a bug with the “Run Command” screen and a process ID}}|| + dpkg: error processing package texlive-fonts-extra-doc (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-fonts-recommended-doc: + texlive-fonts-recommended-doc depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - == Filing a general bug against no particular package == + dpkg: error processing package texlive-fonts-recommended-doc (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-formats-extra: + texlive-formats-extra depends on tex-common (>= 3); however: + Package tex-common is not configured yet. + texlive-formats-extra depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. - If you’re not sure which package is affected by the bug, type `ubuntu-bug` in the “Run Command” screen and press Enter. This will guide you through a series of questions to gather more information about the bug and help you assign it to the appropriate package. + dpkg: error processing package texlive-formats-extra (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-lang-polish: + texlive-lang-polish depends on texlive-latex-base (>= 2013.20130512); however: + Package texlive-latex-base is not configured yet. + texlive-lang-polish depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - [[#Top|Back to top]] + dpkg: error processing package texlive-lang-polish (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-generic-extra: + texlive-generic-extra depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - == Complete the bug report filing process == + dpkg: error processing package texlive-generic-extra (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-lang-indic: + texlive-lang-indic depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - After running one of the above commands, Apport (the Ubuntu bug reporter) will gather information about the bug. + dpkg: error processing package texlive-lang-indic (--configure): + dependency problems - leaving unconfigured + No apport report written because MaxReports is reached already + dpkg: dependency problems prevent configuration of texlive-lang-spanish: + texlive-lang-spanish depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - ||{{attachment:apport-1.png | Apport collecting information about the bug}}|| + dpkg: error processing package texlive-lang-spanish (--configure): + dependency problems - leaving unconfigured + dpkg: too many errors, stopping + No apport report written because MaxReports is reached already + Errors were encountered while processing: + tex-common + latex-sanskrit + lmodern + tex-gyre + texlive-latex-base + texlive-generic-recommended + texlive-pstricks + asymptote + texlive-latex-recommended + cm-super-minimal + cm-super + texlive-metapost + context + emacsen-common + emacs23-common + emacs23-bin-common + emacs23 + texlive-font-utils + texlive-extra-utils + feynmf + xemacs21-mule + xemacs21 + xemacs21-support + gettext-el + texlive-fonts-recommended + tipa + jadetex + latex-xcolor + latex-beamer + latex-cjk-common + latex-cjk-chinese + latex-cjk-japanese + latex-cjk-korean + texlive-lang-other + latex-cjk-thai + latex-cjk-all + latexmk + m-tx + musixtex + pmx + purifyeps + texlive + texlive-bibtex-extra + texlive-fonts-extra + texlive-fonts-extra-doc + texlive-fonts-recommended-doc + texlive-formats-extra + texlive-lang-polish + texlive-generic-extra + texlive-lang-indic + texlive-lang-spanish + Processing was halted because there were too many errors. + Error in function: + Setting up emacsen-common (2.0.7) ... + Install emacsen-common for emacs23 + emacsen-common: Handling install of emacsen flavor emacs23 + Warning: Lisp directory `/usr/local/share/emacs/23.4/site-lisp' does not exist. + Wrote /etc/emacs23/site-start.d/00debian-vars.elc + Wrote /usr/share/emacs23/site-lisp/debian-startup.elc + Install emacsen-common for xemacs21 + emacsen-common: Handling install of emacsen flavor xemacs21 - A window will then pop up, asking you if you want to report the bug. Click "Send Report" if you wish to proceed, or click "Content of the report" if you want to review the information Apport collected. + WARNING: + Couldn't find obvious defaults for: + data-directory + mule-lisp-directory + lisp-directory + Perhaps some directories don't exist, or the XEmacs executable, + /usr/bin/xemacs21 + is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... + Loading 00debian... + Error while loading 00debian: Symbol's function definition is void: loop + Loading 00debian-vars... + Loading 50asymptote... + Loading 50devhelp... + Loading 50dictionaries-common... + Error while loading 50dictionaries-common: No /usr/local/ prefixed paths in load-path + Loading 50gettext... + Loading 50latex-cjk-common... + Error while loading 50latex-cjk-common: Cannot open load file: cjk-enc + Loading 50latex-cjk-thai... + Symbol's function definition is void: dolist + xemacs exiting + . + ERROR: install script from emacsen-common package failed + dpkg: error processing package emacsen-common (--configure): + subprocess installed post-installation script returned error exit status 1 + Setting up synaptic (0.81.1ubuntu1) ... + dpkg: dependency problems prevent configuration of xemacs21-support: + xemacs21-support depends on emacsen-common; however: + Package emacsen-common is not configured yet. - ||{{attachment:apport-problem-report.png | Apport asking you to send the report}}|| + dpkg: error processing package xemacs21-support (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of emacs23-common: + emacs23-common depends on emacsen-common (>= 1.4.10); however: + Package emacsen-common is not configured yet. - Apport will then upload the problem information to Launchpad, and a new browser window will then open to inform you that the bug report is being processed. + dpkg: error processing package emacs23-common (--configure): + dependency problems - leaving unconfigured + Setting up tex-common (4.04) ... + Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! + Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! + Running mktexlsr. This may take some time... done. + Running updmap-sys. This may take some time... + updmap-sys failed. Output has been stored in + /tmp/updmap.zoyOqJD4 + Please include this file if you report a bug. - ||{{attachment:information-upload.png | Apport uploading the problem information}}|| + Sometimes, not accepting conffile updates in /etc/texmf/updmap.d + causes updmap-sys to fail. Please check for files with extension + .dpkg-dist or .ucf-dist in this directory - ||{{attachment:process-data2.png | Launchpad processing the bug report data}}|| + dpkg: error processing package tex-common (--configure): + subprocess installed post-installation script returned error exit status 1 + dpkg: dependency problems prevent configuration of texlive-omega: + texlive-omega depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - After the bug report data has been processed, a new page will open that will ask you for the bug report's title. The bug title will appear in all bug listings so make sure it represents the bug well. When you're done, click "Next". + dpkg: error processing package texlive-omega (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-lang-french: + texlive-lang-french depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - ||{{attachment:bug-title2.png | Launchpad asking for a bug title}}|| + dpkg: error processing package texlive-lang-french (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-lang-other: + texlive-lang-other depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - A search will then occur based on the title you gave to the bug report, and will show potentially similar ones. If one of these seems to be the exact bug you're reporting, click its title, then "Yes, this is the bug I'm trying to report". If not, click "No, I need to report a new bug". + dpkg: error processing package texlive-lang-other (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of xemacs21-mule: + xemacs21-mule depends on xemacs21-support (= 21.4.22-4ubuntu3); however: + Package xemacs21-support is not configured yet. + xemacs21-mule depends on emacsen-common; however: + Package emacsen-common is not configured yet. - ||{{attachment:bug-search.png | Launchpad search results about the bug title}}|| + dpkg: error processing package xemacs21-mule (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-publishers: + texlive-publishers depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - Launchpad will then ask you for further information. It's important that you specify three things: + dpkg: error processing package texlive-publishers (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-lang-cyrillic: + texlive-lang-cyrillic depends on tex-common (>= 3); however: + Package tex-common is not configured yet. - 1. What you expected to happen - 1. What actually happened - 1. If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" + dpkg: error processing package texlive-lang-cyrillic (--configure): + dependency problems - leaving unconfigured + dpkg: dependency problems prevent configuration of texlive-metapost: - Fill in the description field with as much information as you can, it is better to have too much information in the description than not enough. - - ||{{attachment:more-informations2.png | Launchpad asking for further information}}|| - - At then bottom of the page, there are some extra options you can use to make your bug report more complete: - - * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to compromise your security or safety, as well as cause issues such as identity theft or "hi-jacking". - * '''Tags:''' You can add here [[http://wiki.ubuntu.com/Bugs/Tags|tags]] that pertain to your bug report. The predefined values should be left alone. - * '''Include an attachment:''' Using this option, you can add supporting attachments to explain or help others reproduce the bug. This might include a screenshot, a video capture of the problem or a sample document that triggers the fault. If necessary, additional attachments can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. Please check [[https://wiki.ubuntu.com/DebuggingProcedures]] for anything further information to provide. It is vital for developers to get this information, as it contains the minimum requirement information necessary for a developer to begin working on your bug. - * Please note that if one files a bug against the [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel package, you do not need to add as an attachment the terminal command: - {{{ - lspci -vvnn - lspci -vnvn - }}} - - This is due to how [[Launchpad]] automatically generates this as an additional attachment. - - ||{{attachment:extra-options2.png | Launchpad presenting extra options}}|| - - When you're done, click "Submit bug report". - - = Tips and tricks = - - == Filing bugs when off-line == - - In the event that you have an issue with your Internet connection or want to file a bug for another system you can still do this using apport. - - First, on the target system, gather the information in a file: - - * For a bug report about a system crash:<
>`apport-cli -p` ''``'' `--save bug.crash` - * For a bug report about any other issue:<
>`apport-cli -f -p` ''``'' `--save bug.apport` - - You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the `.apport` or `.crash` extension. - - When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:<
> - `ubuntu-bug -c` ''``'' - - /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases (see [[#Stable_release|note about stable releases above]]). - - If this is to be added to an existing bug report, also use the -u option:<
> - `ubuntu-bug -c` ''``'' `-u` ''``'' - - You will need to answer a few questions, and a web browser will be launched to complete the bug report. Please do not attach the `.apport` or `.crash` file to the report, as this is not the same as performing the above mentioned steps. - - == Filing bugs at Launchpad.net == - - If for some reason you cannot file a bug using the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpad's own bug report form]]. When doing so it is best if you have determined which package it should be filed against. Read '[[http://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]' for guidance or use [[ http://launchpad.net/ubuntu/ | Launchpad's package search feature ]]. We don't recommend this method for most bug reports because they will likely be missing crucial information, use ubuntu-bug if you can! - - To file a bug against a specific package you can also use a URL like the following: - - `http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect` - - where PACKAGENAME is the name of the source package about which you want to file the bug report. - - In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the [[ https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu | wiki ]]. - - == Crashes == - - If an application crashes, [[https://wiki.ubuntu.com/Apport|Apport]] will start automatically, raising an appropriate bug report for you to complete in Launchpad. This provides developers with rich debugging information that will make it easier to fix the problem. - - ||{{attachment:apport-1.png}}|| - - == Adding apport-collect information to an existing Launchpad bug == - - First, please do not run apport-collect more than once per release tested. For example, if you originally reported a bug about Precise via Apport, and then could reproduce it in Quantal, only run apport-collect once in Quantal. This minimizes unnecessary E-Mail traffic to those subscribed to your report and keeps the report efficient. - If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not apport-collect to a bug report unless specifically asked of you by a developer or triager. Running apport-collect when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via ubuntu-bug. Otherwise, if you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command: - {{{ - apport-collect bug_number - }}} - via “Run Command” or terminal window. - - Please note that attempting to run `apport-collect bug_number` against a [[https://launchpad.net/ubuntu/+source/linux|linux]] package bug report, while booted into a [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|mainline]] linux kernel will not work. This is due to how Ubuntu does not provide support for mainline kernels. For more on this, please see [[https://wiki.ubuntu.com/Kernel/MainlineBuilds#Kernel.2BAC8-FAQ.2BAC8-DebuggingMainlineBuildsSupport.Does_the_kernel_team_support_the_mainline_kernel_builds.3F]]. - - === Error: The launchpadlib Python module is not installed === - - If one gets the following error while trying to perform apport-collect: {{{ - ERROR: The launchpadlib Python module is not installed. This functionality - is not available. - }}} please install the following package: {{{ - sudo apt-get -y install python-launchpadlib - }}} - - === Package libreoffice not installed and no hook available, ignoring === - - If one attempts to apport-collect and gets the error message: {{{ - Package libreoffice not installed and no hook available, ignoring - }}} one has to install the following package: {{{ - sudo apt-get -y install libreoffice - }}} - - == Adding attachments to an existing Launchpad bug == - - Please ensure you do not use URL links to external posting sites (ex. pastebin.com, paste.ubuntu.com, dropbox.com, etc.) or post external hyperlinks for your attachments. Instead, if as per below you should add an attachment to a report, please post it directly to your bug report. As well, please do not compress attachments (.gz, .zip, etc.) or group mulitiple attachments together (.tar.gz). Attach one uncompressed file at a time. - - === Linux package bugs === - - If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not add attachments, to a bug report unless specifically asked of you by a developer or triager. Adding undesired attachments when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via a terminal: - {{{ - ubuntu-bug linux - }}} - - === Crash reports === - - If your attachment is a crash report (ex. found in directory /var/crash), please do not attach it to an existing report. Instead, file a new report via a terminal so that [[https://help.ubuntu.com/community/ApportRetracingService|Apport Retracing Service]] may process it: - {{{ - ubuntu-bug my_crash_report.crash - }}} - - === Non-crash userspace bugs === - - Sometimes it is useful to take a picture (with a camera or via PrtSc button), or [[https://help.ubuntu.com/community/Screencast|screencast]] of the problem to demonstrate how you reproduced it, what the bug specifically shows, and the impact it has. - - <> - - == Filing a translation bug == - - You should file a translation bug if you are experiencing one of the following issues: - - * Wrong translations or spelling mistakes for languages other than English in applications - * Errors in spellcheckers or language support - * A string from an application not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * An application from the Ubuntu main repository not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * A translation made in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] and not updated in the Ubuntu language packs - * A duplicate translation template (the same application can be translated in two different places) in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - * A template/translation no longer used in Ubuntu and that should be disabled from [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] - In case of doubt, you can always [[http://wiki.ubuntu.com/Translations/Contact|contact the Translations team]]. - - All translation issues should be filed against the [[https://bugs.launchpad.net/ubuntu-translations | Ubuntu Translations project]]. From there the bugs will be triaged and assigned to the right person and package. - - [[#Top|Back to top]] - - = Getting advice = - - Still have doubts about the bug report filing process? You can ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]]. - - [[#Top|Back to top]] - - = Other languages = - - * [[ReportingBugs_es|Español]] - * [[ReportingBugs_ru|Русский]] - * [[ReportingBugs_zh-cn|简体中文（中国）－－ 建设中]] - * [[ReportingBugs_zh-tw|正體中文（台灣）－－ 建置中]] - * [[ReportingBugs-it|Italiano]] - * [[https://help.ubuntu.com/community/ReportingBugs_de|Deutsch]] - [[#Top|Back to top]] - - = See Also = - - * Netiquette Guidelines - [[http://www.ietf.org/rfc/rfc1855.txt]] - * If you use Kubuntu, you are welcome to view the Kubuntu variant of this page [[https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting|here]]. - * [[http://youtu.be/18nsScrDIa0|A screencast on using these tools]] by Jono Bacon - * [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to Report Bugs Effectively]], by Simon Tatham - * [[Ubuntu:DebuggingProcedures|Debugging Procedures]] - From webmaster at ubuntu.com Fri Aug 15 11:44:45 2014 From: webmaster at ubuntu.com (Help Ubuntu) Date: Fri, 15 Aug 2014 11:44:45 -0000 Subject: =?utf-8?q?=5BCommunity_Help_Wiki=5D_Update_of_=22ReportingBugs=22_by_conr?= =?utf-8?q?adoplg?= Message-ID: <20140815114445.12946.42082@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Help Wiki" for change notification. The "ReportingBugs" page has been changed by conradoplg: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=268&rev2=269 Comment: Restored previous version + #title Reporting Bugs - HowTo + #language en - nstallArchives() failed: Selecting previously unselected package synaptic. - (Reading database ... - (Reading database ... 5% - (Reading database ... 10% - (Reading database ... 15% - (Reading database ... 20% - (Reading database ... 25% - (Reading database ... 30% - (Reading database ... 35% - (Reading database ... 40% - (Reading database ... 45% - (Reading database ... 50% - (Reading database ... 55% - (Reading database ... 60% - (Reading database ... 65% - (Reading database ... 70% - (Reading database ... 75% - (Reading database ... 80% - (Reading database ... 85% - (Reading database ... 90% - (Reading database ... 95% - (Reading database ... 100% - (Reading database ... 387382 files and directories currently installed.) - Preparing to unpack .../synaptic_0.81.1ubuntu1_amd64.deb ... - Unpacking synaptic (0.81.1ubuntu1) ... - Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ... - Rebuilding /usr/share/applications/bamf-2.index... - Processing triggers for desktop-file-utils (0.22-1ubuntu1) ... - Processing triggers for mime-support (3.54ubuntu1) ... - Processing triggers for gnome-menus (3.10.1-0ubuntu2) ... - Processing triggers for hicolor-icon-theme (0.13-1) ... - Processing triggers for man-db (2.6.7.1-1) ... - Setting up tex-common (4.04) ... - Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! - Running mktexlsr. This may take some time... done. - Running updmap-sys. This may take some time... - updmap-sys failed. Output has been stored in - /tmp/updmap.b3XNDxHN - Please include this file if you report a bug. + <> - Sometimes, not accepting conffile updates in /etc/texmf/updmap.d - causes updmap-sys to fail. Please check for files with extension - .dpkg-dist or .ucf-dist in this directory + ||<>|| - No apport report written because the error message indicates its a followup error from a previous failure. - No apport report written because the error message indicates its a followup error from a previous failure. - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - No apport report written because MaxReports is reached already - dpkg: error processing package tex-common (--configure): - subprocess installed post-installation script returned error exit status 1 - dpkg: dependency problems prevent configuration of latex-sanskrit: - latex-sanskrit depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + = Bug reporting etiquette = - dpkg: error processing package latex-sanskrit (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of lmodern: - lmodern depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - dpkg: error processing package lmodern (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of tex-gyre: - tex-gyre depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + Thank you for reading this article. This will guide you on how best to present your bug report so that it gets addressed as soon as possible. While this is targeted to the new bug reporter, experienced reporters would find these tips invaluable in getting their bugs looked at by a developer and ultimately fixed: + <
><
> + Before filing any linux kernel related reports on Launchpad, please '''update your BIOS''', and hardware firmware (CF card readers, SSDs, USB 3.0 controllers, DVD/CD drives, etc.) to the newest available from your vendor. Outdated and buggy BIOS and firmware is a common cause of a variety of hardware issues (ex. freezing after lightDM login, intermittent wireless, suspend not working, certain keys on keyboard not working correctly, card readers not working, and kernel panics after plugging USB drive in). Also, please don't make the invalid argument that because it works in Windows, but doesn't in linux, this isn't caused by an outdated BIOS. This is due to how buggy BIOS problems may manifest themselves in linux, but not in Windows. As well, because BIOS vendors typically test to Windows only and make release notes commenting on results to it, it wouldn't advise on if a problem in linux is resolved by it. Hence, one should update anyways, even if your problem isn't specifically mentioned. In addition, BIOS updates are for collateral damage avoidance. For more about BIOS updates, please see [[https://help.ubuntu.com/community/BiosUpdate|here]]. + <
><
> + Please do not claim because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file) you are somehow exempt from providing the information a developer or triager requested. You are being asked for this information so that it would provide more information on how to fix the problem. + <
><
> + '''Please do not speculate on what you think is or isn't a duplicate report''' (ex. I googled around and found bug report...). This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, if you are the original reporter, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. If you are not the original reporter, it's best to file a new report, so that necessary debugging attachments are reviewed. It is a common misconception that filing a potential duplicate report is wasteful. Filing potential duplicates isn't wasteful, and is actually preferred to ease triaging. + <
><
> + Please '''do not quote Wikipedia''' and other non-primary resource information as fact on [[Launchpad]]. + <
><
> + Many [[https://launchpad.net/ubuntu/+source/linux|Linux]] package, hardware, and other non-user space bugs are hardware dependent on both the hardware itself, and what other hardware the problematic hardware is connected to. The rule of thumb is '''''one report, per person, per hardware combination, per bug'''''. For more on this please see [[https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue|here]], and further below in this article. As well, please do not post comments to another person's report, claiming you have the same problem, because you have the same hardware, or same computer model. Instead, please file a separate report, and make comments there. This is because no one can verify if you would have the same problem or not, because your hardware can not be analyzed. + <
><
> + '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox. + <
><
> + For bugs in the [[https://launchpad.net/ubuntu/+source/linux|Linux (Ubuntu)]] package, unless the upstream maintainer or kernel developer notes otherwise, if a new mainline kernel comes out, and you haven't tested with it, you run the strong risk of it not being attended to upstream. + <
><
> + Please '''do not solicit non-original reporters to post comments, attachments, etc.''' + <
><
> + Please '''do not post comments such as “Me too!”, “+1”, “bump”, “same here”, etc.,''' as it is largely unhelpful, produces spammy e-mail traffic to everyone subscribed to the report, and quite often turns out not to be the same root cause. Instead, please follow the below mentioned procedures. + <
><
> + If a triager or developer asks you for some information on reproducing or testing, please do make them dumpster dive by just posting a URL, or saying you already did something in some other report. Instead, put the full reproduction or testing results into the report itself, and if you have to, then post the link. + <
><
> + Please '''do not stack multiple issues into one report'''. For example, jamming suspend and hibernate into one report, reporting multiple [[https://wiki.ubuntu.com/Hotkeys/Troubleshooting|hotkey]] problems into one report (ex. Fn+F3 doesn't turn off my laptop WiFi, Fn+Right doesn't turn the brightness on my [[https://wiki.ubuntu.com/Kernel/Debugging/Backlight|backlight]] down, my brightness settings are not remembered after reboot, etc.). Please make one report for each individual problem. + <
><
> + Please '''do not complain''' about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, “I cannot believe it’s not fixed…”, XYZ person(s) do not care about fixing bugs, etc. Especially, if you have not followed the directions mentioned in this article, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your e-mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources. + <
><
> + Please '''keep the bug objective''' as possible. It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large. + <
><
> + Please '''provide all relevant information from [[https://wiki.ubuntu.com/DebuggingProcedures]] when you first report your bug'''. This is one of the top reasons why bugs do not get marked [[https://wiki.ubuntu.com/Bugs/Status|Triaged]], as the minimum requirements for dealing with the problem by a developer are not provided. + <
><
> + If a triager or developer asks you to provide information, please '''avoid arguing''' with them and just provide the information as requested. This is due to how not everyone has access to the hardware you are reporting against, so having you provide the information helps eliminate the difficulty in fixing your bug. If you have a strong disagreement with what a triager or developer is asking of you, please resolve it with them via personal message, instead of turning a bug development report into a “let’s talk about talking about the problem” report. The Ubuntu community takes a favor to objective, technical discourse. + <
><
> + Please '''do not report bugs about software in [[PPA]]s''' on Launchpad. This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag `ppa`. + <
><
> + Please '''do not add project tasks to bug reports that are invalid because they are not supported'''. For example, if you were using the LibreOffice PPA and reported a bug against the package libreoffice (Ubuntu), which would be marked Status Invalid, please do not add the Launchpad Project [[https://launchpad.net/df-libreoffice|df-libreoffice]] to the report, or change the package libreoffice (Ubuntu) to the project df-libreoffice. The purposes of adding the upstream project to a report is to track valid bugs in Ubuntu that are valid upstream, and may have been reported upstream, not to start another upstream bug tracker. + <
><
> + When posting new comments to a report, please do not include every past comment made, as doing so makes it onerous to read a report, and is wasteful. Instead just make your new comment, or just include the relevant portion of a previous comment you are responding to. + <
><
> + '''Many of the triagers and developers who are providing support to you, are volunteers doing so out of altruism. Please keep this in mind when making your comments.''' + + = How to report bugs = + Ubuntu uses [[Launchpad]] to keep track of bugs and their fixes. This page will guide you through the steps required to file a good and detailed report. - dpkg: error processing package tex-gyre (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-latex-base: - texlive-latex-base depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + == Create a Launchpad account == - dpkg: error processing package texlive-latex-base (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-generic-recommended: - texlive-generic-recommended depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + If you don’t already have one - you need to [[https://help.launchpad.net/YourAccount/NewAccount|create a Launchpad account]]. This will allow you to file new bugs and comment on existing ones. - dpkg: error processing package texlive-generic-recommended (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-pstricks: - texlive-pstricks depends on texlive-generic-recommended (>= 2013.20130512); however: - Package texlive-generic-recommended is not configured yet. - texlive-pstricks depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + == Determine if the bug is really a bug == - dpkg: error processing package texlive-pstricks (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of asymptote: - asymptote depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - asymptote depends on texlive-pstricks; however: - Package texlive-pstricks is not configured yet. - asymptote depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + You should not file a bug if you are: - dpkg: error processing package asymptote (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-latex-recommended: - texlive-latex-recommended depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. - texlive-latex-recommended depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + * '''Requesting new software:''' you should follow the guidelines at https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages + * '''Requesting support:''' there are a multitude of ways you can get help using Ubuntu, such as the [[https://answers.launchpad.net/ubuntu|Launchpad answer tracker]], the [[http://askubuntu.com/|Ask Ubuntu]] site, the [[http://www.ubuntuforums.org/|Ubuntu forums]], the [[irc://irc.freenode.net/#ubuntu|#ubuntu]] channel on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server, and the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-users|ubuntu-users]] mailing list. + * '''Discussing features and existing policy:''' this belongs to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. + * '''Proposing features and ideas:''' you should submit your idea to the [[http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss|ubuntu-devel-discuss]] mailing list. + * '''Filing a bug against a program not provided by an Ubuntu package:''' You should file a bug in that program's bug tracking interface. Instructions are generally available on the program's web site. - dpkg: error processing package texlive-latex-recommended (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of cm-super-minimal: - cm-super-minimal depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - cm-super-minimal depends on texlive-latex-recommended; however: - Package texlive-latex-recommended is not configured yet. + /!\ If you want to file a translation or misspelling bug, follow the instructions [[#translation|here]]. + + == Make sure the bug hasn’t already been reported == - dpkg: error processing package cm-super-minimal (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of cm-super: - cm-super depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - cm-super depends on texlive-latex-recommended; however: - Package texlive-latex-recommended is not configured yet. - cm-super depends on cm-super-minimal (= 0.3.4-9); however: - Package cm-super-minimal is not configured yet. - dpkg: error processing package cm-super (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-metapost: - texlive-metapost depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + First, check the release notes for your version of Ubuntu: + * [[http://www.ubuntu.com/getubuntu/releasenotes/1004|Ubuntu 10.04 LTS (Lucid Lynx)]] + * [[http://www.ubuntu.com/getubuntu/releasenotes/1204|Ubuntu 12.04 LTS (Precise Pangolin)]] + * [[https://wiki.ubuntu.com/SaucySalamander/ReleaseNotes#Known_issues|Ubuntu 13.10 (Saucy Salamander)]] + * [[https://wiki.ubuntu.com/TrustyTahr/ReleaseNotes#Known_issues|Ubuntu 14.04 (Trusty Tahr)]] + === Hardware driver bugs (e.g. sound, Linux kernel, X.Org, and Nvidia / AMD proprietary drivers) === - dpkg: error processing package texlive-metapost (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of context: - context depends on texlive-metapost (>= 2013); however: - Package texlive-metapost is not configured yet. - context depends on lmodern (>= 2.004.4); however: - Package lmodern is not configured yet. - context depends on tex-gyre; however: - Package tex-gyre is not configured yet. - context depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + * For hardware driver bugs you are welcome to check for duplicates. However, depending on if you are the original reporter or not, determines what to do next. The following is a list of hardware packages: + * For sound bugs please see [[https://wiki.ubuntu.com/DebuggingSoundProblems]]. + * [[https://launchpad.net/ubuntu/+source/linux|Linux]] kernel (e.g. suspend, hibernate, and other [[https://wiki.ubuntu.com/DebuggingProcedures#Kernel|potential kernel issues]]). + * [[https://launchpad.net/ubuntu/+source/xorg|xorg]] and [[https://launchpad.net/ubuntu/+source/xorg-server|xorg-server]] + * [[https://launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics|xserver-xorg-input-synaptics]] (e.g. [[https://wiki.ubuntu.com/DebuggingTouchpadDetection|certain Touchpad issues]]). + * [[https://launchpad.net/ubuntu/+source/xserver-xorg-video-intel|xserver-xorg-video-intel]] and other xserver-xorg-video-* like nouveau, radeon, ati, openchrome, geode, etc. + * Nvidia proprietary driver software: [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers|nvidia-graphics-drivers]] , [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-173|graphics-drivers-173]] , [[https://launchpad.net/ubuntu/+source/nvidia-settings|nvidia-settings]] , and [[https://launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180|nvidia-graphics-drivers-180]] . + * AMD proprietary drivers: [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer|fglrx-installer]] and [[https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates|fglrx-installer-updates]]. - dpkg: error processing package context (--configure): - dependency problems - leaving unconfigured - Setting up emacsen-common (2.0.7) ... - Install emacsen-common for emacs23 - emacsen-common: Handling install of emacsen flavor emacs23 - Warning: Lisp directory `/usr/local/share/emacs/23.4/site-lisp' does not exist. - Wrote /etc/emacs23/site-start.d/00debian-vars.elc - Wrote /usr/share/emacs23/site-lisp/debian-startup.elc - Install emacsen-common for xemacs21 - emacsen-common: Handling install of emacsen flavor xemacs21 + ==== You are not the original reporter ==== - WARNING: - Couldn't find obvious defaults for: - data-directory - mule-lisp-directory - lisp-directory - Perhaps some directories don't exist, or the XEmacs executable, - /usr/bin/xemacs21 - is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... - Loading 00debian... - Error while loading 00debian: Symbol's function definition is void: loop - Loading 00debian-vars... - Loading 50asymptote... - Loading 50devhelp... - Loading 50dictionaries-common... - Error while loading 50dictionaries-common: No /usr/local/ prefixed paths in load-path - Loading 50gettext... - Loading 50latex-cjk-common... - Error while loading 50latex-cjk-common: Cannot open load file: cjk-enc - Loading 50latex-cjk-thai... - Symbol's function definition is void: dolist - xemacs exiting - . - ERROR: install script from emacsen-common package failed - dpkg: error processing package emacsen-common (--configure): - subprocess installed post-installation script returned error exit status 1 - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of emacs23-common: - emacs23-common depends on emacsen-common (>= 1.4.10); however: - Package emacsen-common is not configured yet. + * Please '''open a new report''' instead of adding debugging information, attachments, apport-collect’ing, or “Me too!” comments on what may appear to be a similar bug. Chances are that your hardware does not match the existing bug’s hardware, so your bug and comments will not be addressed. As well, unless asked of you by a developer or triager, please do not mark your bug a duplicate of another reporter's bug. + * Please do not assume because you have the same desktop or laptop model line as another original reporter’s bug report, that your problem is the same. Frequently, computer vendors use different parts under the hood within the same model line. + * Regarding peripherals, please do not assume because you have the same peripheral, and similar problems, it is the same bug. Please file a new bug report. - dpkg: error processing package emacs23-common (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of emacs23-bin-common: - emacs23-bin-common depends on emacs23-common (= 23.4+1-4.1ubuntu1); however: - Package emacs23-common is not configured yet. + ==== You are the original reporter ==== - No apport report written because MaxReports is reached already - dpkg: error processing package emacs23-bin-common (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of emacs23: - emacs23 depends on emacs23-bin-common (= 23.4+1-4.1ubuntu1); however: - Package emacs23-bin-common is not configured yet. - dpkg: error processing package emacs23 (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-font-utils: - texlive-font-utils depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + If you are the original reporter, here are the ways to maximize the speed with which your bug is fixed: + * Check for the problem in the earliest release that works for your hardware and the latest. Report your testing results in the report. + * Test for this problem in the mainline kernel following [[https://wiki.ubuntu.com/Kernel/MainlineBuilds]]. Report your mainline testing results in the report. + * If your bug is a regression, bisect it following [[https://wiki.ubuntu.com/Kernel/KernelBisection]]. Report your bisect results in the report. + + === Desktop Applications === + For [[https://wiki.ubuntu.com/DebuggingProcedures#Desktop_Applications|desktop applications]], please make sure it has not already been reported by searching through [[https://launchpad.net/distros/ubuntu/+bugs|existing bugs]]. If you find an already reported bug that is exactly like the problem you have, please feel free to add this information to the existing report, rather than opening a new one. However, if you have any doubt as to it being the same or not, please file a separate report. - dpkg: error processing package texlive-font-utils (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-extra-utils: - texlive-extra-utils depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - texlive-extra-utils depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. + [[#Top|Back to top]] - dpkg: error processing package texlive-extra-utils (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of feynmf: - feynmf depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - feynmf depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - feynmf depends on texlive-font-utils; however: - Package texlive-font-utils is not configured yet. - feynmf depends on texlive-extra-utils; however: - Package texlive-extra-utils is not configured yet. + == Reporting an application crash in the development release == - dpkg: error processing package feynmf (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of xemacs21-mule: - xemacs21-mule depends on emacsen-common; however: - Package emacsen-common is not configured yet. + Please report an application crash via the methods outlined below and at [[https://wiki.ubuntu.com/DebuggingProgramCrash]]. - dpkg: error processing package xemacs21-mule (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of xemacs21: - xemacs21 depends on xemacs21-mule (>= 21.4.22-4ubuntu3) | xemacs21-mule-canna-wnn (>= 21.4.22-4ubuntu3) | xemacs21-nomule (>= 21.4.22-4ubuntu3); however: - Package xemacs21-mule is not configured yet. - Package xemacs21-mule-canna-wnn is not installed. - Package xemacs21-nomule is not installed. + If an application crashes, and you're using a development release, Apport will start automatically, raising an appropriate bug report for you to complete in Launchpad. This report is subsequently processed by [[Apport Retracing Service]], in order to provide developers with debugging information that make it easier to fix the problem. - dpkg: error processing package xemacs21 (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of xemacs21-support: - xemacs21-support depends on emacsen-common; however: - Package emacsen-common is not configured yet. - xemacs21-support depends on xemacs21 (= 21.4.22-4ubuntu3); however: - Package xemacs21 is not configured yet. + == Reporting an application crash in the stable release == - dpkg: error processing package xemacs21-support (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of gettext-el: - gettext-el depends on emacs24 | emacs23 | emacsen; however: - Package emacs24 is not installed. - Package emacs23 is not configured yet. - Package emacsen is not installed. - Package xemacs21-mule which provides emacsen is not configured yet. - Package emacs23 which provides emacsen is not configured yet. + Apport may come disabled by default. To enable it, edit the file: + {{{ + /etc/default/apport + }}} - dpkg: error processing package gettext-el (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-fonts-recommended: - texlive-fonts-recommended depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + and change: + {{{ + enabled=0 + }}} - dpkg: error processing package texlive-fonts-recommended (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of tipa: - tipa depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - tipa depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + to: + {{{ + enabled=1 + }}} - dpkg: error processing package tipa (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of jadetex: - jadetex depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - jadetex depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - jadetex depends on texlive-fonts-recommended; however: - Package texlive-fonts-recommended is not configured yet. - jadetex depends on texlive-latex-recommended; however: - Package texlive-latex-recommended is not configured yet. - jadetex depends on texlive-generic-recommended; however: - Package texlive-generic-recommended is not configured yet. - jadetex depends on tipa; however: - Package tipa is not configured yet. - dpkg: error processing package jadetex (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-xcolor: - latex-xcolor depends on texlive-latex-recommended; however: - Package texlive-latex-recommended is not configured yet. - latex-xcolor depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + /!\ Even when enabled, apport will not upload crash reports to Launchpad for a stable release (see [[https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921|bug #994921]]). Instead, crash reports are uploaded to [[http://errors.ubuntu.com]]. To file a report on Launchpad anyway, one may open the following file via a command line: {{{ + gksudo gedit /etc/apport/crashdb.conf + }}} and change: {{{ + 'problem_types': ['Bug', 'Package'], + }}} to: {{{ + # 'problem_types': ['Bug', 'Package'], + }}} + Save, close, and try to file the crash report again via: {{{ + ubuntu-bug /var/crash/_my_crash_report.crash + }}} + /!\ apport will appear to upload a crash report, but only actually does so if whoopsie is installed. Whoopsie is installed by default for users of ubuntu-desktop, but for users of alternative desktops, or for server users, whoopsie has to be installed manually with ''apt-get install whoopsie''. See [[https://bugs.launchpad.net/ubuntu/+source/xubuntu-meta/+bug/1001630|bug #1001630]] for details. - dpkg: error processing package latex-xcolor (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-beamer: - latex-beamer depends on tex-common (>= 4); however: - Package tex-common is not configured yet. - latex-beamer depends on latex-xcolor (>= 2.00-1); however: - Package latex-xcolor is not configured yet. - latex-beamer depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. + == Reporting a system crash == - dpkg: error processing package latex-beamer (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-common: - latex-cjk-common depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - latex-cjk-common depends on texlive-font-utils (>= 2007.dfsg.2-1); however: - Package texlive-font-utils is not configured yet. - latex-cjk-common depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + If your system lockups up, freezes, logs you out, etc., then this is not an application crash, but a system crash. Please see below, and consult the following article for these types of problems [[https://help.ubuntu.com/community/DebuggingSystemCrash]]. - dpkg: error processing package latex-cjk-common (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-chinese: - latex-cjk-chinese depends on latex-cjk-common (= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-common is not configured yet. - latex-cjk-chinese depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + == Reporting non-crash hardware and desktop application bugs == - dpkg: error processing package latex-cjk-chinese (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-japanese: - latex-cjk-japanese depends on latex-cjk-common (= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-common is not configured yet. - latex-cjk-japanese depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + The method for reporting bugs in Ubuntu is by using the tool “ubuntu-bug”, otherwise known as '''Apport'''. When reporting a bug, you must tell Apport which program or [[https://help.ubuntu.com/community/InstallingSoftware#What%20is%20a%20package?|package]] is at fault. - dpkg: error processing package latex-cjk-japanese (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-korean: - latex-cjk-korean depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-common is not configured yet. - latex-cjk-korean depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + === Collecting information from a specific package === - dpkg: error processing package latex-cjk-korean (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-lang-other: - texlive-lang-other depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + Press Alt+F2 to open the “Run Command” screen: + + ||{{attachment:unity-ubuntu-bug-pkgname.png|Filing a bug with the “Run Command” screen}}|| - dpkg: error processing package texlive-lang-other (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-thai: - latex-cjk-thai depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-common is not configured yet. - latex-cjk-thai depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. - latex-cjk-thai depends on tex-common (>= 4); however: - Package tex-common is not configured yet. - latex-cjk-thai depends on texlive-lang-other (>= 2013.20130523-1); however: - Package texlive-lang-other is not configured yet. + Then, type `ubuntu-bug ` and press Enter. If you’re not sure which package has the problem, refer to the instructions for [[https://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]. - dpkg: error processing package latex-cjk-thai (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of latex-cjk-all: - latex-cjk-all depends on latex-cjk-common (>= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-common is not configured yet. - latex-cjk-all depends on latex-cjk-chinese (>= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-chinese is not configured yet. - latex-cjk-all depends on latex-cjk-japanese (>= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-japanese is not configured yet. - latex-cjk-all depends on latex-cjk-korean (= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-korean is not configured yet. - latex-cjk-all depends on latex-cjk-thai (= 4.8.3+git20120914-2ubuntu1); however: - Package latex-cjk-thai is not configured yet. + === Collecting information about a program with a window open === - dpkg: error processing package latex-cjk-all (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of latexmk: - No apport report written because MaxReports is reached already - latexmk depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. + If you want to file a bug about an application but you don't know what that application's package name is, if it has an open window you are in luck. - dpkg: error processing package latexmk (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of m-tx: - m-tx depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + In a terminal execute the command 'ubuntu-bug -w'. - dpkg: error processing package m-tx (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of musixtex: - musixtex depends on tex-common (>= 4); however: - Package tex-common is not configured yet. + ||{{attachment:ubuntu-bug-w.png | terminal with ubuntu-bug -w }}|| - dpkg: error processing package musixtex (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of pmx: - pmx depends on tex-common (>= 4); however: - Package tex-common is not configured yet. - pmx depends on texlive-latex-base; however: - Package texlive-latex-base is not configured yet. + After you close the dialog the next window that you click on will have a problem report created for the package that created the window. - dpkg: error processing package pmx (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of purifyeps: - purifyeps depends on texlive-metapost; however: - Package texlive-metapost is not configured yet. + === Collecting information from a currently running program === - dpkg: error processing package purifyeps (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive: - texlive depends on texlive-latex-recommended (>= 2013.20130512); however: - Package texlive-latex-recommended is not configured yet. - texlive depends on texlive-fonts-recommended (>= 2013.20130512); however: - Package texlive-fonts-recommended is not configured yet. - texlive depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. + To file a bug against a program that is currently running, open the System Monitor application and find the ID of the process. - dpkg: error processing package texlive (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-bibtex-extra: - texlive-bibtex-extra depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - texlive-bibtex-extra depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. + ||{{attachment:system-monitor-id-new.png | System Monitor Processes tab }}|| - dpkg: error processing package texlive-bibtex-extra (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-fonts-extra: - texlive-fonts-extra depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + Then type "ubuntu-bug " followed by the process ID into the “Run Command” screen. - dpkg: error processing package texlive-fonts-extra (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-fonts-extra-doc: - texlive-fonts-extra-doc depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + ||{{attachment:unity-ubuntu-bug-pid.png | Filing a bug with the “Run Command” screen and a process ID}}|| - dpkg: error processing package texlive-fonts-extra-doc (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-fonts-recommended-doc: - texlive-fonts-recommended-doc depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + == Filing a general bug against no particular package == - dpkg: error processing package texlive-fonts-recommended-doc (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-formats-extra: - texlive-formats-extra depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - texlive-formats-extra depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. + If you’re not sure which package is affected by the bug, type `ubuntu-bug` in the “Run Command” screen and press Enter. This will guide you through a series of questions to gather more information about the bug and help you assign it to the appropriate package. - dpkg: error processing package texlive-formats-extra (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-lang-polish: - texlive-lang-polish depends on texlive-latex-base (>= 2013.20130512); however: - Package texlive-latex-base is not configured yet. - texlive-lang-polish depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + [[#Top|Back to top]] - dpkg: error processing package texlive-lang-polish (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-generic-extra: - texlive-generic-extra depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + == Complete the bug report filing process == - dpkg: error processing package texlive-generic-extra (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-lang-indic: - texlive-lang-indic depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + After running one of the above commands, Apport (the Ubuntu bug reporter) will gather information about the bug. - dpkg: error processing package texlive-lang-indic (--configure): - dependency problems - leaving unconfigured - No apport report written because MaxReports is reached already - dpkg: dependency problems prevent configuration of texlive-lang-spanish: - texlive-lang-spanish depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + ||{{attachment:apport-1.png | Apport collecting information about the bug}}|| - dpkg: error processing package texlive-lang-spanish (--configure): - dependency problems - leaving unconfigured - dpkg: too many errors, stopping - No apport report written because MaxReports is reached already - Errors were encountered while processing: - tex-common - latex-sanskrit - lmodern - tex-gyre - texlive-latex-base - texlive-generic-recommended - texlive-pstricks - asymptote - texlive-latex-recommended - cm-super-minimal - cm-super - texlive-metapost - context - emacsen-common - emacs23-common - emacs23-bin-common - emacs23 - texlive-font-utils - texlive-extra-utils - feynmf - xemacs21-mule - xemacs21 - xemacs21-support - gettext-el - texlive-fonts-recommended - tipa - jadetex - latex-xcolor - latex-beamer - latex-cjk-common - latex-cjk-chinese - latex-cjk-japanese - latex-cjk-korean - texlive-lang-other - latex-cjk-thai - latex-cjk-all - latexmk - m-tx - musixtex - pmx - purifyeps - texlive - texlive-bibtex-extra - texlive-fonts-extra - texlive-fonts-extra-doc - texlive-fonts-recommended-doc - texlive-formats-extra - texlive-lang-polish - texlive-generic-extra - texlive-lang-indic - texlive-lang-spanish - Processing was halted because there were too many errors. - Error in function: - Setting up emacsen-common (2.0.7) ... - Install emacsen-common for emacs23 - emacsen-common: Handling install of emacsen flavor emacs23 - Warning: Lisp directory `/usr/local/share/emacs/23.4/site-lisp' does not exist. - Wrote /etc/emacs23/site-start.d/00debian-vars.elc - Wrote /usr/share/emacs23/site-lisp/debian-startup.elc - Install emacsen-common for xemacs21 - emacsen-common: Handling install of emacsen flavor xemacs21 + A window will then pop up, asking you if you want to report the bug. Click "Send Report" if you wish to proceed, or click "Content of the report" if you want to review the information Apport collected. - WARNING: - Couldn't find obvious defaults for: - data-directory - mule-lisp-directory - lisp-directory - Perhaps some directories don't exist, or the XEmacs executable, - /usr/bin/xemacs21 - is in a strange place?Loading /usr/share/emacs/site-lisp/debian-startup... - Loading 00debian... - Error while loading 00debian: Symbol's function definition is void: loop - Loading 00debian-vars... - Loading 50asymptote... - Loading 50devhelp... - Loading 50dictionaries-common... - Error while loading 50dictionaries-common: No /usr/local/ prefixed paths in load-path - Loading 50gettext... - Loading 50latex-cjk-common... - Error while loading 50latex-cjk-common: Cannot open load file: cjk-enc - Loading 50latex-cjk-thai... - Symbol's function definition is void: dolist - xemacs exiting - . - ERROR: install script from emacsen-common package failed - dpkg: error processing package emacsen-common (--configure): - subprocess installed post-installation script returned error exit status 1 - Setting up synaptic (0.81.1ubuntu1) ... - dpkg: dependency problems prevent configuration of xemacs21-support: - xemacs21-support depends on emacsen-common; however: - Package emacsen-common is not configured yet. + ||{{attachment:apport-problem-report.png | Apport asking you to send the report}}|| - dpkg: error processing package xemacs21-support (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of emacs23-common: - emacs23-common depends on emacsen-common (>= 1.4.10); however: - Package emacsen-common is not configured yet. + Apport will then upload the problem information to Launchpad, and a new browser window will then open to inform you that the bug report is being processed. - dpkg: error processing package emacs23-common (--configure): - dependency problems - leaving unconfigured - Setting up tex-common (4.04) ... - Ignoring /etc/texmf/texmf.d/05TeXMF.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/15Plain.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/45TeXinputs.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/55Fonts.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/65BibTeX.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/75DviPS.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/80DVIPDFMx.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/85Misc.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/90TeXDoc.cnf during generation of texmf.cnf, please remove manually! - Ignoring /etc/texmf/texmf.d/95NonPath.cnf during generation of texmf.cnf, please remove manually! - Running mktexlsr. This may take some time... done. - Running updmap-sys. This may take some time... - updmap-sys failed. Output has been stored in - /tmp/updmap.zoyOqJD4 - Please include this file if you report a bug. + ||{{attachment:information-upload.png | Apport uploading the problem information}}|| - Sometimes, not accepting conffile updates in /etc/texmf/updmap.d - causes updmap-sys to fail. Please check for files with extension - .dpkg-dist or .ucf-dist in this directory + ||{{attachment:process-data2.png | Launchpad processing the bug report data}}|| - dpkg: error processing package tex-common (--configure): - subprocess installed post-installation script returned error exit status 1 - dpkg: dependency problems prevent configuration of texlive-omega: - texlive-omega depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + After the bug report data has been processed, a new page will open that will ask you for the bug report's title. The bug title will appear in all bug listings so make sure it represents the bug well. When you're done, click "Next". - dpkg: error processing package texlive-omega (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-lang-french: - texlive-lang-french depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + ||{{attachment:bug-title2.png | Launchpad asking for a bug title}}|| - dpkg: error processing package texlive-lang-french (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-lang-other: - texlive-lang-other depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + A search will then occur based on the title you gave to the bug report, and will show potentially similar ones. If one of these seems to be the exact bug you're reporting, click its title, then "Yes, this is the bug I'm trying to report". If not, click "No, I need to report a new bug". - dpkg: error processing package texlive-lang-other (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of xemacs21-mule: - xemacs21-mule depends on xemacs21-support (= 21.4.22-4ubuntu3); however: - Package xemacs21-support is not configured yet. - xemacs21-mule depends on emacsen-common; however: - Package emacsen-common is not configured yet. + ||{{attachment:bug-search.png | Launchpad search results about the bug title}}|| - dpkg: error processing package xemacs21-mule (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-publishers: - texlive-publishers depends on tex-common (>= 3); however: - Package tex-common is not configured yet. + Launchpad will then ask you for further information. It's important that you specify three things: - dpkg: error processing package texlive-publishers (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-lang-cyrillic: - texlive-lang-cyrillic depends on tex-common (>= 3); however: - Package tex-common is not configured yet. - dpkg: error processing package texlive-lang-cyrillic (--configure): - dependency problems - leaving unconfigured - dpkg: dependency problems prevent configuration of texlive-metapost: + 1. What you expected to happen + 1. What actually happened + 1. If possible, a minimal series of steps necessary to make it happen, where step 1 is "start the program" + Fill in the description field with as much information as you can, it is better to have too much information in the description than not enough. + + ||{{attachment:more-informations2.png | Launchpad asking for further information}}|| + + At then bottom of the page, there are some extra options you can use to make your bug report more complete: + + * '''This bug is a security vulnerability:''' Please check this '''''only''''' if your bug report describes a behaviour that could be exploited to compromise your security or safety, as well as cause issues such as identity theft or "hi-jacking". + * '''Tags:''' You can add here [[http://wiki.ubuntu.com/Bugs/Tags|tags]] that pertain to your bug report. The predefined values should be left alone. + * '''Include an attachment:''' Using this option, you can add supporting attachments to explain or help others reproduce the bug. This might include a screenshot, a video capture of the problem or a sample document that triggers the fault. If necessary, additional attachments can be added after the bug is reported via '''Add a comment/attachment''' at the bottom of the page. Please check [[https://wiki.ubuntu.com/DebuggingProcedures]] for anything further information to provide. It is vital for developers to get this information, as it contains the minimum requirement information necessary for a developer to begin working on your bug. + * Please note that if one files a bug against the [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel package, you do not need to add as an attachment the terminal command: + {{{ + lspci -vvnn + lspci -vnvn + }}} + + This is due to how [[Launchpad]] automatically generates this as an additional attachment. + + ||{{attachment:extra-options2.png | Launchpad presenting extra options}}|| + + When you're done, click "Submit bug report". + + = Tips and tricks = + + == Filing bugs when off-line == + + In the event that you have an issue with your Internet connection or want to file a bug for another system you can still do this using apport. + + First, on the target system, gather the information in a file: + + * For a bug report about a system crash:<
>`apport-cli -p` ''``'' `--save bug.crash` + * For a bug report about any other issue:<
>`apport-cli -f -p` ''``'' `--save bug.apport` + + You will need to answer a few questions, which will vary depending on which package the bug report is about. Relevant system information, including the package name, is then saved on the target system, in the current directory. The extension indicates if it is a crash report or another kind of report. If you decide to rename the report file, please keep the `.apport` or `.crash` extension. + + When the file is ready, copy it to the system you intend to use for filing the report. There you can then file the report:<
> + `ubuntu-bug -c` ''``'' + + /!\ 'ubuntu-bug -c x.crash' does not work for crash reports from stable Ubuntu releases (see [[#Stable_release|note about stable releases above]]). + + If this is to be added to an existing bug report, also use the -u option:<
> + `ubuntu-bug -c` ''``'' `-u` ''``'' + + You will need to answer a few questions, and a web browser will be launched to complete the bug report. Please do not attach the `.apport` or `.crash` file to the report, as this is not the same as performing the above mentioned steps. + + == Filing bugs at Launchpad.net == + + If for some reason you cannot file a bug using the ''Apport'' tool you can file one via [[https://bugs.launchpad.net/ubuntu/+filebug/?no-redirect | Launchpad's own bug report form]]. When doing so it is best if you have determined which package it should be filed against. Read '[[http://wiki.ubuntu.com/Bugs/FindRightPackage|finding the right package]]' for guidance or use [[ http://launchpad.net/ubuntu/ | Launchpad's package search feature ]]. We don't recommend this method for most bug reports because they will likely be missing crucial information, use ubuntu-bug if you can! + + To file a bug against a specific package you can also use a URL like the following: + + `http://bugs.launchpad.net/ubuntu/+source/PACKAGENAME/+filebug?no-redirect` + + where PACKAGENAME is the name of the source package about which you want to file the bug report. + + In the event that you want to request a piece of software be packaged for Ubuntu please follow the instructions in the [[ https://wiki.ubuntu.com/UbuntuDevelopment/NewPackages#Requesting%20a%20new%20package%20for%20Ubuntu | wiki ]]. + + == Crashes == + + If an application crashes, [[https://wiki.ubuntu.com/Apport|Apport]] will start automatically, raising an appropriate bug report for you to complete in Launchpad. This provides developers with rich debugging information that will make it easier to fix the problem. + + ||{{attachment:apport-1.png}}|| + + == Adding apport-collect information to an existing Launchpad bug == + + First, please do not run apport-collect more than once per release tested. For example, if you originally reported a bug about Precise via Apport, and then could reproduce it in Quantal, only run apport-collect once in Quantal. This minimizes unnecessary E-Mail traffic to those subscribed to your report and keeps the report efficient. + If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not apport-collect to a bug report unless specifically asked of you by a developer or triager. Running apport-collect when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via ubuntu-bug. Otherwise, if you have already reported a bug directly via Launchpad, but want to add additional debugging information via ''Apport'' to the bug report, you can do this by running the command: + {{{ + apport-collect bug_number + }}} + via “Run Command” or terminal window. + + Please note that attempting to run `apport-collect bug_number` against a [[https://launchpad.net/ubuntu/+source/linux|linux]] package bug report, while booted into a [[https://wiki.ubuntu.com/Kernel/MainlineBuilds|mainline]] linux kernel will not work. This is due to how Ubuntu does not provide support for mainline kernels. For more on this, please see [[https://wiki.ubuntu.com/Kernel/MainlineBuilds#Kernel.2BAC8-FAQ.2BAC8-DebuggingMainlineBuildsSupport.Does_the_kernel_team_support_the_mainline_kernel_builds.3F]]. + + === Error: The launchpadlib Python module is not installed === + + If one gets the following error while trying to perform apport-collect: {{{ + ERROR: The launchpadlib Python module is not installed. This functionality + is not available. + }}} please install the following package: {{{ + sudo apt-get -y install python-launchpadlib + }}} + + === Package libreoffice not installed and no hook available, ignoring === + + If one attempts to apport-collect and gets the error message: {{{ + Package libreoffice not installed and no hook available, ignoring + }}} one has to install the following package: {{{ + sudo apt-get -y install libreoffice + }}} + + == Adding attachments to an existing Launchpad bug == + + Please ensure you do not use URL links to external posting sites (ex. pastebin.com, paste.ubuntu.com, dropbox.com, etc.) or post external hyperlinks for your attachments. Instead, if as per below you should add an attachment to a report, please post it directly to your bug report. As well, please do not compress attachments (.gz, .zip, etc.) or group mulitiple attachments together (.tar.gz). Attach one uncompressed file at a time. + + === Linux package bugs === + + If your problem is in the [[https://launchpad.net/ubuntu/+source/linux|linux]] package, and you are not the original reporter, please do not add attachments, to a bug report unless specifically asked of you by a developer or triager. Adding undesired attachments when not asked creates spammy E-Mail traffic for those subscribed, clutters up the bug report with undesired attachments, and hinders the bug getting addressed quickly. As well, your attachments are subject to deletion at the discretion of developers and triagers. Instead, please open a new report via a terminal: + {{{ + ubuntu-bug linux + }}} + + === Crash reports === + + If your attachment is a crash report (ex. found in directory /var/crash), please do not attach it to an existing report. Instead, file a new report via a terminal so that [[https://help.ubuntu.com/community/ApportRetracingService|Apport Retracing Service]] may process it: + {{{ + ubuntu-bug my_crash_report.crash + }}} + + === Non-crash userspace bugs === + + Sometimes it is useful to take a picture (with a camera or via PrtSc button), or [[https://help.ubuntu.com/community/Screencast|screencast]] of the problem to demonstrate how you reproduced it, what the bug specifically shows, and the impact it has. + + <> + + == Filing a translation bug == + + You should file a translation bug if you are experiencing one of the following issues: + + * Wrong translations or spelling mistakes for languages other than English in applications + * Errors in spellcheckers or language support + * A string from an application not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * An application from the Ubuntu main repository not available for translation in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * A translation made in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] and not updated in the Ubuntu language packs + * A duplicate translation template (the same application can be translated in two different places) in [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + * A template/translation no longer used in Ubuntu and that should be disabled from [[http://translations.launchpad.net/ubuntu|Launchpad Translations]] + In case of doubt, you can always [[http://wiki.ubuntu.com/Translations/Contact|contact the Translations team]]. + + All translation issues should be filed against the [[https://bugs.launchpad.net/ubuntu-translations | Ubuntu Translations project]]. From there the bugs will be triaged and assigned to the right person and package. + + [[#Top|Back to top]] + + = Getting advice = + + Still have doubts about the bug report filing process? You can ask someone on [[irc://irc.freenode.net/#ubuntu-bugs|#ubuntu-bugs]] on the [[https://help.ubuntu.com/community/InternetRelayChat|Freenode IRC]] server or on the [[https://lists.ubuntu.com/mailman/listinfo/Ubuntu-bugsquad|bugsquad mailing list]]. + + [[#Top|Back to top]] + + = Other languages = + + * [[ReportingBugs_es|Español]] + * [[ReportingBugs_ru|Русский]] + * [[ReportingBugs_zh-cn|简体中文（中国）－－ 建设中]] + * [[ReportingBugs_zh-tw|正體中文（台灣）－－ 建置中]] + * [[ReportingBugs-it|Italiano]] + * [[https://help.ubuntu.com/community/ReportingBugs_de|Deutsch]] + [[#Top|Back to top]] + + = See Also = + + * Netiquette Guidelines - [[http://www.ietf.org/rfc/rfc1855.txt]] + * If you use Kubuntu, you are welcome to view the Kubuntu variant of this page [[https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting|here]]. + * [[http://youtu.be/18nsScrDIa0|A screencast on using these tools]] by Jono Bacon + * [[http://www.chiark.greenend.org.uk/~sgtatham/bugs.html|How to Report Bugs Effectively]], by Simon Tatham + * [[Ubuntu:DebuggingProcedures|Debugging Procedures]] + From zgiltd at gmail.com Sat Aug 16 20:26:42 2014 From: zgiltd at gmail.com (Zgi Ltd) Date: Sun, 17 Aug 2014 01:56:42 +0530 Subject: Fwd: HAVING PROBLEM IN STARTUP : SAIAD In-Reply-To: References: <53EB19E1.3010804@gmail.com> Message-ID: Hello I have problem (as detailed below) as this happened when i was trying to updgrade from 12.04 to 14.04 as almost half of the packages have been dowwnloaded and hald to be done. i had disconnected in between since late evening and it was showing it will take another 8 hours to complete downloading. The next day when i was trying to start the system is not funtional at all.. although i can sign in, i cannot have access to Ubuntu. as advise i tried to open terminal with Ctrl+Alt+F2 .. i got as follows.. Ubuntu 14.04 LTS Saiad tty2 Saiad Login: Hence, i need to know what commands to be entreed to gain access to my account and complete the balance downloanding of ubuntu 14.04 I am using live CD 12.04 for time being... please advise soon so as to fix this problem. Thanks. Saiad ---------- Forwarded message ---------- From: Zgi Ltd Date: Wed, 13 Aug 2014 14:40:45 +0530 Subject: Re: Fwd: HAVING PROBLEM IN STARTUP : SAIAD To: Jkhatri I AM USING WITH UBUNTU 12.04 LIVE CD TO WORK TEMPORARILY IN THE SAME LAPTOP I AM USING AT MY HOME. PLEASE ASK ANY QUESTIONS IN THIS REGARD.. AS I HAVE DOWNLOADED 50% OF THE LATEST UPGRADE 14.04 AND THAN CLOSED IT LAST NIGHT. SINCE THAN I AM NOT ABLE TO GAIN ACCESS TO MY UBUNTU ACCOUNT.. EVEN THOUGH I CAN SIGN IN BUT THE DESTOP IS NOT OPENING. HOPE THIS HELPS. SAIAD On 8/13/14, Zgi Ltd wrote: > JATIN, > > I SAID EVER AFTER SIGNING SUCCESSFULLY I AM NOT ABLE TO ACCES TO > DESKTOP ITSELF SO HOW CAN I CAN GO OPEN TERMINAL..? > > SAIAD > > On Wednesday 13 August 2014 01:19 PM, Zgi Ltd wrote: > >> PLEASRE TREAT THIS AS URGENT >> >> >> ---------- Forwarded message ---------- >> From: Zulkhar Nain >> Date: Wed, 13 Aug 2014 08:42:46 +0530 >> Subject: HAVING PROBLEM IN STARTUP : SAIAD >> To: khatri.jatin at gmail.com >> Cc: "zgiltd at gmail.com" >> >> Good morning Jatin! >> >> As i was upgrading from my old version of Ubuntu 12.04 to 14.04 and >> since i did not complete the downloading completely (out of about 1800 >> packages i have downloaded around 800 already) and switched of due to >> late evening. I had in starting up although i can sign in to my >> account.. immediaely it comes back to the signing page .. as it is not >> opening the desktop page. pls advise what to do next...? >> >> thanks >> >> Saiad >> +9986388797 >> +8095968985 >> > do the same thing... as i said in previous mail ( as given below) > cd /var/lib/apt > sudo mv list list.old > sudo mkdir -p list.partial > sudo apt-get update > > > */ > > Jatin Khatri > > RHCSA RHCE CCNA > > www.fedoraproject.org/wiki/Jatin > > Phone (+91) 98250 20393 > > Save Paper, Save Environment.** > (Plant at least one tree in your life and nurture it !!!) > > On 8/13/14, Jkhatri wrote: >> On Wednesday 13 August 2014 01:19 PM, Zgi Ltd wrote: >>> PLEASRE TREAT THIS AS URGENT >>> >>> >>> ---------- Forwarded message ---------- >>> From: Zulkhar Nain >>> Date: Wed, 13 Aug 2014 08:42:46 +0530 >>> Subject: HAVING PROBLEM IN STARTUP : SAIAD >>> To: khatri.jatin at gmail.com >>> Cc: "zgiltd at gmail.com" >>> >>> Good morning Jatin! >>> >>> As i was upgrading from my old version of Ubuntu 12.04 to 14.04 and >>> since i did not complete the downloading completely (out of about 1800 >>> packages i have downloaded around 800 already) and switched of due to >>> late evening. I had in starting up although i can sign in to my >>> account.. immediaely it comes back to the signing page .. as it is not >>> opening the desktop page. pls advise what to do next...? >>> >>> thanks >>> >>> Saiad >>> +9986388797 >>> +8095968985 >>> >> do the same thing... as i said in previous mail >> >> -- >> >> */ >> >> Jatin Khatri >> >> RHCSA RHCE CCNA >> >> www.fedoraproject.org/wiki/Jatin >> >> >> Phone (+91) 98250 20393 >> >> Save Paper, Save Environment.** >> /*(Plant at least one tree in your life and nurture it !!!)*/ >> From es20490446e at gmail.com Sun Aug 17 16:23:17 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sun, 17 Aug 2014 18:23:17 +0200 Subject: Having problems with start-up In-Reply-To: References: <53EB19E1.3010804@gmail.com> Message-ID: <53F0D6F5.6000509@gmail.com> Zgi Ltd: > I have problem (as detailed below) For technical support, please refer to . From noreply at ubuntu.com Sat Aug 16 09:46:36 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 16 Aug 2014 09:46:36 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?pascal-devuyst?= Message-ID: <20140816094636.15967.71337@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 pascal-devuyst: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=91&rev2=92 Comment: Remove cupsys, releases that support it are EOL = Reporting Bugs = + Bugs about printing problems should be assigned to the '''cups''' package if you don't know which package they belong to. To report printing bugs preferably use 'ubuntu-bug cups' from a terminal window which will gather useful information about your system related to printing like the version of Ubuntu you use, configured printers and the versions of important printing packages installed and automatically attach them to your bug report. You can also add the information after the bug is reported by executing 'apport-collect -p cups BUGNUMBER' where BUGNUMBER is the bug report you want to add information to. - Beginning with 9.04, Jaunty Jackalope, to report printing bugs use 'ubuntu-bug cups' which will gather useful information about your system related to printing like the version of Ubuntu you use, configured printers and the versions of important printing packages installed and automatically attach them to your bug report. You can also add the information after the bug is reported by executing 'apport-collect -p cups BUGNUMBER' where BUGNUMBER is the bug report you want to add information to. - - Starting with Intrepid the '''cupsys''' package has been renamed to '''cups'''. Subsequently, bugs about Intrepid (8.10) and newer releases should be assigned to the '''cups''' package and bug reports about previous releases should be assigned to '''cupsys'''. = Printer detection = @@ -92, +90 @@ 1. In Ubuntu Gutsy or newer, select "System" -> "Administration" -> "Printing" in the main menu of your desktop and in Oneiric or newer with Unity desktop click the gear icon at the upper right (the one also used to log out) and in the menu showing up then, click "Printer". The printer setup tool system-config-printer will open. Select "Server Settings" in the list on the left or in newer versions with the printers showing as icons choose "Server" in the main menu and then "Settings". Note that the main menu will be in the bar at the top of the screen if Oneiric (or newer) with Unity is used. There it only appears if you move the mouse into the top bar. Then check the checkbox "Save debugging information for troubleshooting" and click "Apply". 2. In all Ubuntu flavors (also Kubuntu and server editions) you can run <
> {{{$ cupsctl LogLevel=debug}}} <
> to activate debug logging. 3. In Karmic and later (CUPS 1.4.x) there is an automatic debug logging only for failed print jobs. So if you problem was a failed print job, the error_log can already contain the desired information. Unfortunately, only 200 debug message lines get logged per failed job. Run the command <
> {{{$ cupsctl LogDebugHistory=999999}}} <
> for practically unlimited logging of failed jobs. - 4. In older versions of all flavors, where there is not yet a "cupsctl" command, edit the file {{{/etc/cups/cupsd.conf}}}, find the line '''Log``Level ...''' and change it to '''Log``Level debug''', save the file. Then restart CUPS: <
> {{{$ sudo /etc/init.d/cupsys restart}}} + 4. In older versions of all flavors, where there is not yet a "cupsctl" command, edit the file {{{/etc/cups/cupsd.conf}}}, find the line '''Log``Level ...''' and change it to '''Log``Level debug''', save the file. Then restart CUPS: <
> {{{$ sudo /etc/init.d/cups restart}}} 5. Clear the queue from any stuck jobs by deleting the jobs in the job viewer or running the "{{{cancel -a}}}" command. 6. Try to print something. Wait until the job disappears from the queue or turns into "Stopped" state, independent whether something gets out of the printer. If the job never reaches "Stopped" state after the printer not showing any reaction for a longer time you also can go on to the next step. 7. Scan or photograph the printout if it is not correct and attach the images to the bug report. @@ -107, +105 @@ If a print job fails, a job viewer with the failed job ("Stopped" state) and pop-up window telling that the job has problems will appear. If you click the "Diagnose" button, the troubleshooting wizard will open. Do not delete the job before having completed the wizard. Take care to choose the printer with which the problem occured. In the "Test Page" step you do not need to print anything, nor to wait. Mark the stopped job in the integrated job viewer, click "No" at the question and then "Forward". After that save the file and attach it to the bug report. = AppArmor Protection of the printing system = - From Gutsy on the security of the CUPS printing system is improved by using App``Armor. Unfortunately, the configuration is not perfect yet, especially if third-party printer drivers are used. If you have any problems with printing, try deactivating the App``Armor protection with {{{sudo aa-complain cupsd}}}. If this helps, look for messages containing '''audit''' in the {{{/var/log/messages}}} file. These show which components are accessed by the printing system for which there is no explicit permission given in {{{/etc/apparmor.d/usr.sbin.cupsd}}}. You can re-activate App``Armor via {{{sudo aa-enforce cupsd}}}. Report a bug, about the package '''cups''' ('''cupsys''' on 8.04 and older), so that we can correct the default configuration of App``Armor. + From Gutsy on the security of the CUPS printing system is improved by using App``Armor. Unfortunately, the configuration is not perfect yet, especially if third-party printer drivers are used. If you have any problems with printing, try deactivating the App``Armor protection with {{{sudo aa-complain cupsd}}}. If this helps, look for messages containing '''audit''' in the {{{/var/log/messages}}} file. These show which components are accessed by the printing system for which there is no explicit permission given in {{{/etc/apparmor.d/usr.sbin.cupsd}}}. You can re-activate App``Armor via {{{sudo aa-enforce cupsd}}}. Report a bug to the package '''cups''', so that we can correct the default configuration of App``Armor. = Capturing print job data = Often it is needed to find out what actually got sent to the printer in order to determine whether the problem is caused by the application or by the printing subsystem. For that it is the easiest way to capture the job data from the application so that it can analyzed whether it is already broken or not. To do so, follow these steps: <
> From es20490446e at gmail.com Sat Aug 23 13:30:41 2014 From: es20490446e at gmail.com (Alberto Salvia Novella) Date: Sat, 23 Aug 2014 15:30:41 +0200 Subject: Wanted to apologise Message-ID: <53F89781.1060804@gmail.com> I wanted to apologise. I believe I have mistreating some people here with my comments, and I want to say sorry. I'll drop passing judgements on how you do your work. Instead I'll support you. I feel I had been taking myself too seriously for some months, and I'm leaving the space of it for making things real. 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 Fri Aug 22 07:41:51 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 22 Aug 2014 07:41:51 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/FindRightPackage=22_by_mpt?= Message-ID: <20140822074151.30139.19138@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 mpt: http://wiki.ubuntu.com/Bugs/FindRightPackage?action=diff&rev1=132&rev2=133 Comment: Bug Squad header -> QA Team header - <> + <> ||<>|| To ensure that the right people see a bug report, every report should identify the software [[Package|package]] related to the bug. When running `ubuntu-bug` (see [[https://help.ubuntu.com/community/ReportingBugs | ReportingBugs]]), one must sometimes specify the package manually. This page contains information to help identify the related package. From noreply at ubuntu.com Sat Aug 30 11:41:20 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 30 Aug 2014 11:41:20 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingPrintingProblems=22_by_?= =?utf-8?q?pascal-devuyst?= Message-ID: <20140830114120.14633.3231@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 pascal-devuyst: http://wiki.ubuntu.com/DebuggingPrintingProblems?action=diff&rev1=92&rev2=93 Comment: printout > appout 2. Disable the print queue with which you have the problem. Use system-config-printer (System -> Administration -> Printing in GNOME classic, Gear icon at the upper right of the screen -> Printers in Unity), right-click the appropriate printer icon, and click "Enabled" in the pop-up menu, so that the check mark disappears or run the command <
> {{{$ cupsdisable }}} <
> in a terminal window (Replace "" by the name of the print queue). This makes jobs staying in the queue so that you can capture them. 3. Now print the job from your application. When the application has finished sending the job, check via the job viewer or the command <
> {{{$ lpstat -o}}} <
> whether it is in the queue. 4. Display the content of CUPS' spool directory using the command <
> {{{$ sudo ls -1 /var/spool/cups}}} <
> (Enter your password when getting asked). - 5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <
> {{{$ sudo cp /var/spool/cups/d... ~/printout}}} <
> {{{$ sudo chmod 777 ~/printout}}} + 5. There should be exactly one file beginning with a "d". Copy this file to your home directory: <
> {{{$ sudo cp /var/spool/cups/d... ~/appout}}} <
> {{{$ sudo chmod 777 ~/appout}}} 6. Re-enable the print queue: <
> {{{$ cupsenable }}} <
> 7. If the file gets correctly printed now, try the above procedure with another file, we need a file where the problem occurs. - 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. + 8. Check via the command <
> {{{$ file ~/appout}}} <
> 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. + 9. Attach the original file of your application and the ~/appout file to your bug report. = Getting the data which would go to the printer = From noreply at ubuntu.com Sat Aug 30 21:12:42 2014 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sat, 30 Aug 2014 21:12:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Triage=22_by_ian-weisser?= Message-ID: <20140830211242.15617.44382@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Triage" page has been changed by ian-weisser: http://wiki.ubuntu.com/Bugs/Triage?action=diff&rev1=163&rev2=164 Comment: Removed references to Ubuntu Brainstorm (closed in 2012) Bugs requesting a feature concerning upstream projects should be forwarded upstream. Forwarding upstream is explained at [[Bugs/HowToTriage#Forwarding_upstream|Forwarding Bugs Upstream]]. - However, if the request is abstract and/or suggesting a large change the bug should be closed as 'Invalid' while posting a message pointing the user to [[http://brainstorm.ubuntu.com/|Ubuntu Brainstorm]]. + However, if the request is abstract and/or suggesting a large change the bug should be closed as 'Invalid' while posting a message pointing the user to the appropriate upstream or to the user forums. A canned response you can use is: - || Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu, you are invited to post your idea in Ubuntu Brainstorm at http://brainstorm.ubuntu.com/ where it can be discussed, voted on by the community, and reviewed by developers. Thanks for taking the time to share your opinion!|| + || Thank you for taking the time to make Ubuntu better. Since what you submitted is not really a bug, or a problem, but rather an idea to improve Ubuntu, you are invited discuss the idea with other Ubuntu community members in the many public forums. Public discussion of ideas improves the likelihood of adoption. Thanks for taking the time to share your opinion!|| === Regressions ===