From brian at ubuntu.com Wed Feb 1 17:08:04 2012 From: brian at ubuntu.com (Brian Murray) Date: Wed, 1 Feb 2012 09:08:04 -0800 Subject: Bugs regarding update status Message-ID: <20120201170804.GU8364@murraytwins.com> When running unity in the "Log Out" menu there is information about package updates, your system's status and whether or not you need to reboot. There is at least one bug about this[1] regarding indicator-session which provides that functionality. However, I suspect that these bugs may be incorrectly filed about update-manager and or update-notifier. If you happen to run across one please mark it as a duplicate. [1] https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/852181 Thanks, -- Brian Murray Ubuntu Bug Master -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 198 bytes Desc: Digital signature URL: From noreply at ubuntu.com Thu Feb 2 17:47:35 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 02 Feb 2012 17:47:35 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_brian-mu?= =?utf-8?q?rray?= Message-ID: <20120202174735.22180.84@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=44&rev2=45 Certain hardware failures can often be reported as installer bugs. This includes faulty CDs, CD drives hard drives and memory. - = Installer hangs = + = Notes = - (just asking: how to debug if the installer doesn't crash, but "just" hangs? Could you add some basic hints for that here? Thanks) + The 'kernel command line' line of the syslog file contains information about the boot parameters used. + * Images created by unetbootin contain 'initrd=/ubninit' and / or 'BOOT_IMAGE=/ubnkern' ------ '''Also see:''' From noreply at ubuntu.com Tue Feb 7 12:31:42 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 07 Feb 2012 12:31:42 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingKernelBoot=22_by_herton?= Message-ID: <20120207123142.15335.73368@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingKernelBoot" page has been changed by herton: http://wiki.ubuntu.com/DebuggingKernelBoot?action=diff&rev1=14&rev2=15 1. During the BIOS screen, press the shift key and hold it down. You should see the GRUB menu after the BIOS loads. 1. Navigate to the kernel entry you want to boot, and press 'e'. 1. Then remove the '''quiet''' and '''splash''' keywords (found in the line starting with linux) - 1. If running Natty (Ubuntu 11.04) also remove the parameter '''vt.handoff=7''', and on the line that reads '''set gfxpayload=$linux_gfx_mode''', replace with '''set gfxpayload=text''' + 1. Starting with Natty (Ubuntu 11.04), also remove the parameter '''vt.handoff=7''', and on the line that reads '''set gfxpayload=$linux_gfx_mode''', replace with '''set gfxpayload=text''' 1. Press 'Ctrl+x' to boot. It's best if you can attach a log file which may have captured any messages you see. If you are unable to capture a log file, a digital photo will work just as well. As a last resort you can even copy messages down by hand. From noreply at ubuntu.com Tue Feb 7 21:29:39 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 07 Feb 2012 21:29:39 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_brian-mu?= =?utf-8?q?rray?= Message-ID: <20120207212939.16501.91110@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=45&rev2=46 The 'kernel command line' line of the syslog file contains information about the boot parameters used. * Images created by unetbootin contain 'initrd=/ubninit' and / or 'BOOT_IMAGE=/ubnkern' + Bugs should be tagged indicating the step where the issue occurred if possible. The possible steps are: + + * ubi-console-setup + * ubi-language + * ubi-migrationassistant + * ubi-network + * ubi-partman + * ubi-prepare + * ubi-tasks + * ubi-timezone + * ubi-usersetp - "Who are you?" + * ubi-webcam + * ubi-wireless + ------ '''Also see:''' From costamagnagianfranco at yahoo.it Mon Feb 13 10:28:40 2012 From: costamagnagianfranco at yahoo.it (Gianfranco Costamagna) Date: Mon, 13 Feb 2012 10:28:40 +0000 (GMT) Subject: Libpng & ubuntu Message-ID: <1329128920.73197.YahooMailNeo@web171212.mail.ir2.yahoo.com> Just a stupid question, why libpng in ubuntu isn't the latest one? https://launchpad.net/ubuntu/precise/+source/libpng ubuntu is at 1.2 but the latest is 1.5 in debian too (libpng15-15 in experimental) could anybody please sinc this new package in precise?  thanks Gianfranco -------------- next part -------------- An HTML attachment was scrubbed... URL: From roignac at gmail.com Mon Feb 13 16:33:13 2012 From: roignac at gmail.com (Vadim Rutkovsky) Date: Mon, 13 Feb 2012 18:33:13 +0200 Subject: Libpng & ubuntu In-Reply-To: <1329128920.73197.YahooMailNeo@web171212.mail.ir2.yahoo.com> References: <1329128920.73197.YahooMailNeo@web171212.mail.ir2.yahoo.com> Message-ID: Hi Gianfranco, Ubuntu is synced with Debian unstable, so as soon as libpng15 will be promoted to unstable, this version will appear in next Ubuntu release. I hope, this solves your question. 2012/2/13 Gianfranco Costamagna : > Just a stupid question, why libpng in ubuntu isn't the latest one? > https://launchpad.net/ubuntu/precise/+source/libpng > ubuntu is at 1.2 but the latest is 1.5 in debian too (libpng15-15 in > experimental) > > could anybody please sinc this new package in precise? >  thanks > Gianfranco > > -- > Ubuntu-bugsquad mailing list > Ubuntu-bugsquad at lists.ubuntu.com > https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad > -- Vadim Rutkovsky From noreply at ubuntu.com Wed Feb 15 10:17:53 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Wed, 15 Feb 2012 10:17:53 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Responses=22_by_veger?= Message-ID: <20120215101753.12552.9310@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Responses" page has been changed by veger: http://wiki.ubuntu.com/Bugs/Responses?action=diff&rev1=341&rev2=342 Comment: Updated link for requesting backports The bug's state should become '''Fix Released''' and if the package does not qualify for a SRU because it is considered a minor bug and the package can be backported: - || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Precise Pangolin.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#request-new-packages || + || Thank you for taking the time to report this bug and helping to make Ubuntu better. However, I am closing it because the bug has been fixed in the latest development version of Ubuntu - Precise Pangolin.<
><
> If you need a fix for the bug in previous versions of Ubuntu, please follow the instructions for "How to request new packages" at https://help.ubuntu.com/community/UbuntuBackports#Requesting_New_Backports || The bug's state should become '''Fix Released''' and if the package can not be backported: From noreply at ubuntu.com Thu Feb 16 04:08:31 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 16 Feb 2012 04:08:31 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/Status=22_by_mfisch?= Message-ID: <20120216040831.9603.7332@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/Status" page has been changed by mfisch: http://wiki.ubuntu.com/Bugs/Status?action=diff&rev1=58&rev2=59 * If you have to ask the reporter questions, set the bug to {{{Incomplete}}} * Ask the submitter to provide any necessary information in a comment, and make sure you subscribe yourself to the bug report so you will get any updates to the bug via e-mail. * <> + * If anyone, including you, comments on the bug, the 60 day expiration clock is reset. * '''Opinion''': * The status 'opinion' means there is a difference of opinion around a particular bug and people are free to continue the discussion, but the project or package maintainers need to move to other work and are considering the issue closed. The idea is that bugs can be marked closed, so developers aren't wasting time on them, but discussion can still be on-going. * This status 'opinion' is considered an experiment, and will be closely monitored. From noreply at ubuntu.com Thu Feb 16 22:49:18 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 16 Feb 2012 22:49:18 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/DisconnectedTasks=22_by_bri?= =?utf-8?q?an-murray?= Message-ID: <20120216224918.1468.95219@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/DisconnectedTasks" page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/DisconnectedTasks New page: This is a page for recording bug tasks about a bug that are disconnected, or out of sync, in some way. || Date || Bug || Task || How is it not in sync? || || 2012-02-16 || bug:876626 || upstart (Ubuntu) (Oneiric) || The precise task has an importance but the oneiric one doesn't. || From noreply at ubuntu.com Thu Feb 16 22:50:38 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Thu, 16 Feb 2012 22:50:38 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22Bugs/DisconnectedTasks=22_by_bri?= =?utf-8?q?an-murray?= Message-ID: <20120216225038.1468.57635@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "Bugs/DisconnectedTasks" page has been changed by brian-murray: http://wiki.ubuntu.com/Bugs/DisconnectedTasks?action=diff&rev1=1&rev2=2 This is a page for recording bug tasks about a bug that are disconnected, or out of sync, in some way. - || Date || Bug || Task || How is it not in sync? || + || '''Date''' || '''Bug''' || '''Task''' || '''How is it not in sync?''' || - || 2012-02-16 || bug:876626 || upstart (Ubuntu) (Oneiric) || The precise task has an importance but the oneiric one doesn't. || + || 2012-02-16 || bug876626 || upstart (Ubuntu) (Oneiric) || The precise task has an importance but the oneiric one doesn't. || From rhhyatt at hotmail.com Sun Feb 19 09:29:39 2012 From: rhhyatt at hotmail.com (Robert Hyatt) Date: Sun, 19 Feb 2012 09:29:39 +0000 Subject: Help and Advice, please - VLC and other video players fail in 12.04LTS Message-ID: Sirs, I was 'hit' by the recent problem of accessing the libraries during a 'normal' update of my PC, at that time using Ubuntu 11.10 without issues. It appears that the ' internet pipe' into your libraries was restricted and some of the requests for downloads were successful and others failed due to internet access failures (Including the infamous HTTP 404 error). The problem was furthur compounded when the incomplete set of software that was retrieved was installed. This meant some dependencies were not satisfied... The result is my PC would not boot after the 'normal update' that failed. I tried reinstalling 11.10 from the DVD, which seemed to work, but again, the PC would not boot. >From another PC with Ubuntu, I downloaded the dvd for 12.04 Precise (even though it is in beta testing) and made sure to NOT do a normal update on that PC. I then installed Ubuntu 12.04 LTS from the DVD on or about Feb 7th. As I was telling the BIOS to boot from the DVD, when I noticed the hard drives had been 'switched'. e.g. what was supposed to be the C: drive for booting, etc purposes was now the 2nd drive on the list. I fixed this and did the installation. In my installations I pointed the install programmer at the correct drive, but the boot was going to another drive. So SAD. The installation went ok, until it started downloading 92 packages. The whole reason I downloaded the DVD was to STOP this annoying delay in getting work done. The internet speed I have during the daylight and evening hours in the Philippines is very slow and this downloading of packages takes a very long time. I have been using Ubuntu 12.04 for a couple of weeks now and have had some aborts, which usually Apport noted and reported. In looking at the bugs and errors reports, the one that killed my system was the 'partial updates', for which it was advised to NOT accept this option. ---- Video Player aborts I am having some issues, and in particular NO VIDEO Playing software will run correctly. Worse, the manner in which they fail means that Apport never has the chance to report the issue. I have installed about 6 of the video players and they all failed in the same manner. When I click on a video file, the splash screen for that program will appear, then the screen goes a way for a moment, and I am back at the initial logon screen when powering up. No Error message. No Apport process collecting data. VLC, Movie Player, MPlayer, Gnome Media Player, and a few more all did what I just described. Without an error message, etc I cannot determine how to fix. === About me... I am a retired programmer, systems analyst, dba, systems architect, project architect, and a whole bunch more titles. I worked from 1970 until retirement in 2007. I used more than 3 dozen programming languages in my career. I worked on 72-bit computer hardware system (Honeywell and Sperry Univac), plus the usual IBM 32 and 64 bit hardware systems. I have worked on different database architectures and some complicated file systems. The last 15 years I spent being the systems architect, data architect, project architect, Project mgr, and other titles related to EDI (Electronic Data Interchange) sometimes known as e-Commerce. I first 'tried' Linux in 1995, for 3 years on my own systems at home. I decided they were 'not ready for prime time' and went back to Windows. I used Suse and RedHat as my test software. In 2002 I had reason to 'appreciate' my little adventure in Linux as I began working on Unix computers, in addition to the mainframes that was my primary responsibility. In November 2011, I finally got rid of M S Windows in my home and switched to Edubuntu and Ubuntu. My Netbook has Win XP and it looks like it will remain thus for some time to come. I am not looking for another 'job', but I might be of service. Unfortunately the issue I am reporting does NOT fit into the "Apport" box you normally want for bug reports. ===== Help Please?? A. Video Player Fix and 'partial updates' process? Please point me to where I could find instructions to allow me to successfully do 'partial updates', and to fix the Video Player issue. B. O S backup and restore? Thanks to my habit of backing up my data, I lost no data files. I did lose all my program settings, etc. So, I would like to be pointed to where I could do a complete OS backup (not my data) and if I should ever have the need, the process to use that backup to restore. C. Install without download? I would like to 'find' or 'have built' a boot dvd containing what I need to do a successful installation without even ONE download! I especially find the 'Language' packages annoying as the downloads for them take a very long time to complete. This would likely require a 'scan' of my system to determine what packages should be on the install dvd. Since the 'scan' process is well known, I don't see this as a big challenge. D. I would like to specify an option for 'normal' updates that says: Do NO updating unless ALL downloads have been successful. My problem that started me on this merry go round was started because of an incomplete update. e.g. some parts were downloaded, and installed, while other parts only got a partial set of the required files - yet still tried to do the installation. I want to tell the updater to ONLY do updates if each and every file has been successfully downloaded to my PC. Any failures stop any installation. Next, I want the downloader to know that some files have previously been downloaded. It is very annoying to try to do the same update and see the exact same files downloaded as a few minutes ago, when I am attempting to get only those that failed the prior attempt. E. Some errors I get cannot be reported by Apport as some bit of software is missing. Whenever they specify the package, I do the Terminal window process to get them and to install, but I am unable to do this in all cases. e.g. I have aborts or 'bad behavior' and no way to report it. Best regards, Bob Hyatt -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at ubuntu.com Fri Feb 24 16:24:27 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 24 Feb 2012 16:24:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_jibel?= Message-ID: <20120224162427.898.79510@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by jibel: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=46&rev2=47 = Known bugs = + Before filing new bugs, check that it is not already [[https://bugs.launchpad.net/ubuntu/+source/ubiquity|listed in Launchpad]] - == Fixed == - * '''[fixed in dapper-updates and Edgy]''' Crash if /boot is on XFS: [[https://launchpad.net/bugs/47848|Bug 47848]] - - This can be recognised by grub-installer exiting 10 or 30, and /var/log/partman or /var/log/installer/syslog (look for "mountpoints:" in the latter) indicating that / is on XFS and there is no non-XFS /boot filesystem. Feel free to mark such bugs as duplicates of #47848, with text such as: {{{ - Thanks for your report. Due to some reliability problems with GRUB and XFS, you need to use a non-XFS root filesystem or create a non-XFS /boot filesystem. The fact that the partitioner doesn't warn you about this up-front is also bug 47848, and is fixed in 6.06.1. - }}} - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash if system partitions are not reformatted: [[https://launchpad.net/bugs/47046|Bug 47046]] - - This can be recognised by an OS``Error exception being thrown from the `copy_all` function, usually "File exists" or similar, and a "mountpoints:" line in /var/log/installer/syslog that includes a tuple with a standard filesystem (e.g. /, /boot, /usr, or /var; not /home or /media/*) as the first item and False as the second item. Feel free to mark such bugs as duplicates of #47046, with text such as: {{{ - Thanks for your report. At present, you must reformat system partitions (e.g. /, /boot, /usr, or /var) during installation; the fact that the partitioner doesn't warn you about this is also bug 47046, and is fixed in 6.06.1. If you are upgrading an existing installation, then please see http://wiki.ubuntu.com/DapperUpgrades rather than using this installer. - }}} - - * '''[fixed in dapper-updates and Edgy]''' Crash if some packages on running live session are unconfigured: [[https://launchpad.net/bugs/47859|Bug 47859]] - - This can be recognised by a dpkg error in /var/log/installer/syslog while installing language packs, and a crash in the `install_language_packs` function. Feel free to mark such bugs as duplicates of #47859, with text such as: {{{ - Thanks for your report. This is also bug 47859, and can be worked around by not installing [substitute the package that broke here] in the live session before running the installer. This is fixed in 6.06.1. - }}} If one of the packages that broke was `ntp`, then use the following text: {{{ - Thanks for your report. This is also bug 47859, and can be worked around by not choosing to install NTP support while running the installer. It can be installed after rebooting into the newly-installed system by right-clicking on the date/time applet and selecting "Adjust Date & Time". This is fixed in 6.06.1. - }}} - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash when installing in Chinese but with a non-Chinese-speaking country: [[https://launchpad.net/bugs/47687|Bug 47687]] - - This can be recognised by Chinese characters scattered through /var/log/installer/syslog and: {{{ - ubiquity: ['sh', '-c', '/usr/lib/ubiquity/localechooser/post-base-installer && /usr/lib/ubiquity/localechooser/prebaseconfig'] exited with code 1 - }}} Feel free to mark such bugs as duplicates of #47687, with text such as: {{{ - Thanks for your report. This is also bug 47687, and occurs when you select a Chinese language (either Simplified or Traditional) but then select a non-Chinese-speaking country on the timezone/country selection page. This is fixed in 6.06.1, so you can work around it by upgrading all packages with 'ubiquity' in their names on the running live CD before starting the installer. - }}} - - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash with certain kinds of disk attached: [[https://launchpad.net/bugs/48732|Bug 48732]] - - This can be recognised by the following at the end of the traceback (ignoring line and byte number differences): {{{ - File "/usr/lib/python2.4/site-packages/ubiquity/components/partman.py", line 214, in run - if not self.frontend.set_disk_choices(self.choices(question), - File "/usr/lib/python2.4/site-packages/ubiquity/filteredcommand.py", line 189, in choices - choices = unicode(self.db.metaget(question, 'choices'), 'utf-8') - UnicodeDecodeError: 'utf8' codec can't decode bytes in position 204-205: invalid data - }}} Feel free to mark such bugs as duplicates of #48732, with text such as: {{{ - Thanks for your report. This is also bug 48732, and occurs due to strange model names on certain disks. This is fixed in 6.06.1, so you can work around it by upgrading all packages with 'ubiquity' in their names on the running live CD before starting the installer. - }}} - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash when gparted crashes: [[https://launchpad.net/bugs/48856|Bug 48856]] - - This can be recognised by the following at the end of the traceback: {{{ - print >>self.gparted_subp.stdin, "apply" - AttributeError: 'NoneType' object has no attribute 'stdin' - }}} Feel free to mark such bugs as duplicates of #48856, with text such as: {{{ - Thanks for your report, which is also bug 48856. The program used for advanced partitioning, gparted, appears to have crashed. The version of the installer present in Ubuntu/Edubuntu/Xubuntu 6.06.1 deals with this more gracefully. If you can reproduce the gparted crash by running it directly from the System -> Administration menu, then please file a separate bug against gparted. - }}} - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash when qtparted crashes: [[https://launchpad.net/bugs/47194|Bug 47194]] - - This can be recognised by the following at the end of the traceback: {{{ - print >>self.qtparted_subp.stdin, "apply" - AttributeError: 'NoneType' object has no attribute 'stdin' - }}} Feel free to mark such bugs as duplicates of #47194, with text such as: {{{ - Thanks for your report, which is also bug 47194. The program used for advanced partitioning, qtparted, appears to have crashed. The version of the installer present in Kubuntu 6.06.1 deals with this more gracefully. If you can reproduce the qtparted crash by running it directly from K Menu -> System, then please file a separate bug against qtparted. - }}} - - * '''[fixed in dapper-updates and Edgy Knot 1]''' Crash when hw-detect fails to load a module: [[https://launchpad.net/bugs/48524|Bug 48524]] - - This can be recognised by the following in `/var/log/installer/syslog` just before the traceback: {{{ - ubiquity: ['/bin/hw-detect'] exited with code 1 - }}} (AND ONLY THAT EXIT CODE!) and the following as the last message about `hw-detect` in `/var/log/syslog`: {{{ - Aug 24 18:02:10 ubuntu hw-detect: Detecting hardware... - }}} Feel free to mark such bugs as duplicates of #48524, with text such as: {{{ - Thanks for your report. This is also bug 48524, and occurs due to a failure to handle module load errors on certain hardware. This is fixed in 6.06.1, so you can work around it by upgrading all packages with 'ubiquity' in their names on the running live CD before starting the installer. - }}} - - * '''[fixed in Feisty Herd 2]''' Crash if language packs are uninstallable in certain ways: [[https://launchpad.net/bugs/61912|Bug 61912]] - - This can be recognised by the following traceback from `install.py` (in 6.06, you'll need to look in `/var/log/installer/syslog`): {{{ - File "/usr/share/ubiquity/install.py", line 1347, in ? - install.run() - File "/usr/share/ubiquity/install.py", line 335, in run - self.install_language_packs() - File "/usr/share/ubiquity/install.py", line 807, in install_language_packs - self.mark_install(cache, lp) - File "/usr/share/ubiquity/install.py", line 734, in mark_install - assert cache._depcache.BrokenCount == 0 - AssertionError - }}} If `self.mark_install` is not present in the traceback, then it is a different bug. Otherwise, feel free to mark such bugs as duplicates of #61912, with text such as: {{{ - Thanks for your report. This is also bug 61912, and occurs due to a failure to handle uninstallable language packs. You can typically work around this by installing in English or by disconnecting from the network during installation. - }}} - - * '''[fixed in Hardy Heron]''' Crash when autopartitioning and disk is too small: [[https://launchpad.net/bugs/48355|Bug 48355]] - - This can be recognised by {{{IOError: [Errno 28] No space left on device}}} being thrown inside the `copy_all` function, and `stepPartAdvanced` not appearing in /var/log/installer/syslog; also check the end of /var/log/partman to make sure that the size of the disk is smaller than about 2.5GB (I'm not sure of the exact figure). Feel free to mark such bugs as duplicates of #48355, with text such as: {{{ - Thanks for your report. I'm afraid that one of your partitions seems to be too small to complete an Ubuntu desktop installation successfully. Bug 48355 notes that the partitioner should have warned you about this. This has been fixed in Hardy Heron. - }}} - - * '''[fixed in Hardy Heron - ubiquity version 1.7.9]''' Ubiquity dialogs too large for 800x600 display: [[https://launchpad.net/bugs/38442|Bug 38442]] - - The timezone map used in ubiquity was a static size and larger than 800x600 so it was challenging to use ubiquity with hardware that would use a display resolution lower than that. It is possible that some duplicate bug reports still exist and they should be marked as a duplicate of 38442 with text such as: {{{ - Thanks for taking the time to report this bug and helping to make Ubuntu better. This bug is a duplicate of bug 38442 and is being marked as such. Incidentally, this issue is resolved in Hardy Heron as the timezone map can scale down to 674x434. - }}} - - * '''[fixed in Hardy Heron ]''' Login sound plays while installing from the Live CD [[https://launchpad.net/bugs/178057|Bug 178057]] - - During the installation process the login sound was being played multiple times. This was not strictly a ubiquity bug but rather a bug in debian-installer-utils. However, most of the bug reports about it will be filed about ubiquity. = Non-bugs = From noreply at ubuntu.com Fri Feb 24 16:29:48 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Fri, 24 Feb 2012 16:29:48 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_jibel?= Message-ID: <20120224162948.861.2560@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by jibel: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=47&rev2=48 Certain hardware failures can often be reported as installer bugs. This includes faulty CDs, CD drives hard drives and memory. + You can check if your hardware is faulty from kernel's error message in /var/log/syslog or the output of the command '''dmesg''' + + You'll find messages such as: + {{{ + Feb 18 22:01:41 ubuntu kernel: [ 1976.481211] ata3.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 + Feb 18 22:01:41 ubuntu kernel: [ 1976.481230] ata3.00: irq_stat 0x40000008 + Feb 18 22:01:41 ubuntu kernel: [ 1976.481257] ata3.00: failed command: READ FPDMA QUEUED + Feb 18 22:01:41 ubuntu kernel: [ 1976.481281] ata3.00: cmd 60/08:00:58:5c:0c/00:00:00:00:00/40 tag 0 ncq 4096 in + Feb 18 22:01:41 ubuntu kernel: [ 1976.481286] res 51/40:08:58:5c:0c/00:00:00:00:00/40 Emask 0x409 (media error) + Feb 18 22:01:41 ubuntu kernel: [ 1976.481296] ata3.00: status: { DRDY ERR } + Feb 18 22:01:41 ubuntu kernel: [ 1976.481304] ata3.00: error: { UNC } + Feb 18 22:01:41 ubuntu kernel: [ 1976.484953] ata3.00: configured for UDMA/133 + Feb 18 22:01:41 ubuntu kernel: [ 1976.485000] sd 3:0:0:0: [sda] Unhandled sense code + Feb 18 22:01:41 ubuntu kernel: [ 1976.485012] sd 3:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE + Feb 18 22:01:41 ubuntu kernel: [ 1976.485029] sd 3:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor] + Feb 18 22:01:41 ubuntu kernel: [ 1976.485048] Descriptor sense data with sense descriptors (in hex): + Feb 18 22:01:41 ubuntu kernel: [ 1976.485058] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 + Feb 18 22:01:41 ubuntu kernel: [ 1976.485106] 00 0c 5c 58 + Feb 18 22:01:41 ubuntu kernel: [ 1976.485121] sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed + Feb 18 22:01:41 ubuntu kernel: [ 1976.485137] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 00 0c 5c 58 00 00 08 00 + Feb 18 22:01:41 ubuntu kernel: [ 1976.485165] end_request: I/O error, dev sda, sector 810072 + Feb 18 22:01:41 ubuntu kernel: [ 1976.485225] ata3: EH complete + }}} + = Notes = The 'kernel command line' line of the syslog file contains information about the boot parameters used. From noreply at ubuntu.com Sun Feb 26 04:34:15 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Sun, 26 Feb 2012 04:34:15 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUpdateManager=22_by_nat?= =?utf-8?q?hanst?= Message-ID: <20120226043415.17719.29297@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUpdateManager" page has been changed by nathanst: http://wiki.ubuntu.com/DebuggingUpdateManager?action=diff&rev1=44&rev2=45 = Bug Tags = || '''Tag''' || '''Use case''' || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=lucid2precise|`lucid2precise`]] || Bugs related to upgrades from Lucid Lynx (10.04) to Precise Pangolin (12.04) || + || [[https://launchpad.net/ubuntu/+bugs?field.tag=oneiric2precise |`oneiric2precise`]] || Bugs related to upgrades from Oneiric Ocelot (11.10) to Precise Pangolin (12.04) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=natty2oneiric |`natty2oneiric`]] || Bugs related to upgrades from Natty Narwhal (11.04) to Oneiric Ocelot (11.10) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=maverick2natty |`maverick2natty`]] || Bugs related to upgrades from Maverick Meerkat (10.10) to Natty Narwhal (11.04) || || [[https://launchpad.net/ubuntu/+bugs?field.tag=lucid2maverick |`lucid2maverick`]] || Bugs related to upgrades from Lucid Lynx (10.04) to Maverick Meerkat (10.10) || From noreply at ubuntu.com Mon Feb 27 10:08:27 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Mon, 27 Feb 2012 10:08:27 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_jibel?= Message-ID: <20120227100827.13351.52187@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by jibel: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=48&rev2=49 = Crash report handling = - Many Ubiquity bugs arrive in the form of cut-and-pastes from its crash helper dialog. In simple cases, these are often enough to completely diagnose the bug and allow a developer to fix it, which is why the crash dialog exists. However, if the crash occurs in `install.py` (the component of Ubiquity that actually constructs and configures the newly-installed system), then in Dapper a combination of technical awkwardness and lack of developer time means that the traceback from the crash dialog often ends like this: + If you're running the development release, most Ubiquity bugs are reported by apport and the right log files are attached to the bug report. + + If the log files are not attached and want to analyze them locally logs are: + + * During installation or from a Live Session: + {{{ + /var/log/syslog + /var/log/partman + /var/log/installer + }}} + + * After installation from running system installer log files are stored in the directory ```/var/log/installer/``` + + These are often enough to completely diagnose the bug and allow a developer to fix it. + + Sometimes, the developer will need more information than what is actually in the log files. In this case, if you know and can reproduce the defect you can run Ubiquity in '''debug mode'''. To run Ubiquity in debug mode, from a Live Session, open a terminal (On Unity Press to display the dash then enter '''terminal''' in the search field then ) and start Ubiquity with: {{{ - RuntimeError: Install failed with exit code 1; see /var/log/installer/syslog and /var/log/syslog + $ ubiquity -d }}} - (Edgy installations will produce a more verbose traceback.) - - This traceback is moderately useless on its own, and you must not mark bugs as duplicates on the basis that they both contain a traceback such as this. In Dapper, the real error is hidden in /var/log/installer/syslog, so if the reporter didn't attach that, ask for it, and for /var/log/syslog and /var/log/partman as well for good measure. Look for the traceback from the crash dialog in /var/log/installer/syslog and then trace up a little bit; the real error should be there, often in the form of a subprocess exiting non-zero. - - Standard text for asking for log files in Dapper: {{{ - Could you please attach /var/log/installer/syslog, /var/log/syslog, and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance. - }}} - - Standard text for asking for log files in >= Edgy: {{{ - Could you please attach /var/log/syslog and /var/log/partman to this bug, following the directions in http://wiki.ubuntu.com/DebuggingUbiquity/AttachingLogs? Thanks in advance. - }}} - - Don't ask for `/var/log/installer/syslog` if the version of ubiquity in the log is `1.1.12` or greater (Edgy or later). Those versions of ubiquity send all log messages apart from certain detailed partitioning log messages to `/var/log/syslog`, and `/var/log/installer/syslog` no longer exists. Please do not assign ubiquity bugs to anyone unless you're a ubiquity developer or you manage a ubiquity developer. Please don't reject ubiquity bugs unless you're a ubiquity developer. In general, please try to refrain from causing unnecessary extra bug mail noise for ubiquity developers or from taking items off their to-do lists without consulting them first. From webmaster at ubuntu.com Tue Feb 28 16:55:02 2012 From: webmaster at ubuntu.com (Help Ubuntu) Date: Tue, 28 Feb 2012 16:55:02 -0000 Subject: =?utf-8?q?=5BCommunity_Ubuntu_Documentation=5D_Update_of_=22ReportingBugs?= =?utf-8?q?=22_by_dholbach?= Message-ID: <20120228165502.20169.4903@jostaberry.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Community Ubuntu Documentation" for change notification. The "ReportingBugs" page has been changed by dholbach: http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=162&rev2=163 = See Also = - * [[http://screencasts.ubuntu.com/2009/09/16/Reporting_Bugs|A screencast on using these tools]] by Daniel Holbach + * [[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 noreply at ubuntu.com Tue Feb 28 16:45:44 2012 From: noreply at ubuntu.com (Ubuntu Wiki) Date: Tue, 28 Feb 2012 16:45:44 -0000 Subject: =?utf-8?q?=5BUbuntu_Wiki=5D_Update_of_=22DebuggingUbiquity=22_by_brian-mu?= =?utf-8?q?rray?= Message-ID: <20120228164544.23317.48391@mangaba.canonical.com> Dear Wiki user, You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification. The "DebuggingUbiquity" page has been changed by brian-murray: http://wiki.ubuntu.com/DebuggingUbiquity?action=diff&rev1=49&rev2=50 Feb 18 22:01:41 ubuntu kernel: [ 1976.485225] ata3: EH complete }}} + These messages indicate an error with sda, which is likely the disk you to which you are installing Ubuntu. Hardware errors with the CD / DVD drives would also contain "I/O error" but with "dev sr0". + = Notes = The 'kernel command line' line of the syslog file contains information about the boot parameters used. @@ -80, +82 @@ * ubi-webcam * ubi-wireless + Additionally, if you are using OEM setup the bug should be tagged '''oem-config'''. + ------ '''Also see:'''