[Bug 56050] Re: Ubiquity crash: RuntimeError: Install failed with exit code 1
Install fails for Hardy 8.04 on HP Pavilion 750c destop. sda - not being used (has winXP and has bad blocks) sdb - install to partition sdb8, with sdb5 used for swap -- Ubiquity crash: RuntimeError: Install failed with exit code 1 https://bugs.launchpad.net/bugs/56050 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 56050] Re: Ubiquity crash: RuntimeError: Install failed with exit code 1
Also, got "install.py crashed with AttributeError in ()" ** Attachment added: "syslog.bak" http://launchpadlibrarian.net/15126458/syslog.bak -- Ubiquity crash: RuntimeError: Install failed with exit code 1 https://bugs.launchpad.net/bugs/56050 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 91128] Re: Files ending with jpg must be renamed jpeg to open
A few notes about this... If you rename the file to .jpeg, double-click on it, it works. (we knew that) If you then rename it back to .jpg, you can now double-click on it and it will open in Image Viewer! A similar problem has been reported for MP3 files: http://ubuntuforums.org/showthread.php?t=617301&highlight=file+type -- Files ending with jpg must be renamed jpeg to open https://bugs.launchpad.net/bugs/91128 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
I am getting the same behavior on an HP Pavillion Desktop except mine is consistent. It will not boot at all. I get this error EVERY time. The only solution has been to revert to the 2.6.17 kernel. Obviously there is nothing wrong with the superblock if I can boot with an older kernel. -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
I will be happy to provide any details possible. This problem is reproducible. On my HP Pavilion 750c Desktop it happens on every boot with the 2.6.20-16-386 kernel. Simply dropping back to the 2.6.17 kernel allows the system to boot. John ** Attachment added: "fsck log" http://launchpadlibrarian.net/8106206/checkfs.txt -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
Here is fstab. Some explanation: hda - old hd with possible bad blocks - not used except to recover data now and then hdb - new Maxtor hd. has copy of Windows XP in hdb1 & hdb2. Ubuntu boots from hdb6. hdb6,7,8 are logical partitions within a container partition ** Attachment added: "contents of fstab" http://launchpadlibrarian.net/8106212/fstab -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 156487] Re: Sudoku Forgets Generated Puzzles and Highscores
On my Gutsy system the directory gnome-sudoku was simply missing. So I created it. Then it complained that the file generated_puzzles was missing. So I created that too. Finally (after getting an EOF error) it seemed to go ahead, but now when it exits it gives the following: Unable to load puzzles: : /usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py:423: Warning: /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1741: instance `0x862a340' has no handler with id `1449' self.timer.disconnect(c) /usr/lib/python2.5/site-packages/gnome_sudoku/gnome_sudoku.py:423: Warning: /build/buildd/glib2.0-2.14.1/gobject/gsignal.c:1741: instance `0x862a340' has no handler with id `1450' self.timer.disconnect(c) -- Sudoku Forgets Generated Puzzles and Highscores https://bugs.launchpad.net/bugs/156487 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99292] Re: fsck tries to check the wrong mapped fs
see also 120285 -- fsck tries to check the wrong mapped fs https://bugs.launchpad.net/bugs/99292 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
output of dmesg (tar.gz format) ** Attachment added: "dmesg.tar.gz" http://launchpadlibrarian.net/8138878/dmesg.tar.gz -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
contents /var/log/udev ** Attachment added: "udev.tar.gz" http://launchpadlibrarian.net/8138881/udev.tar.gz -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
Okay, this is NOT exactly a bug. It may be caused by the use of /dev/hdxx device identifiers in fstab. Evidently this latest kernel no longer recognizes those and the partitions are now identified as /dev/sdxx. The problem in this case is caused by a bug in the upgrade path from Dapper to Edgy. Edgy is supposed to convert the fstab to UUID identifiers, but if there are duplicate UUID's it does not. In fact, if you have duplicate UUIDs you cannot successfully mount all drives using UUID identifiers. I have not yet tried using /dev/sdxx identifiers in the fstab, but if I convert the fstab to use UUID and do not mount any of the duplicate UUID drives it will work with the 2.6.20 kernel. If there is a bug it is this: There is no way (that I am aware of) to change the UUID of an NTFS or FAT32. So if UUID identifiers are required in fstab, there is no way to mount NTFS or FAT32 drives that have been cloned, and thus have duplicate UUID's. -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
Banana - post the output of these two commands: blkid sudo fdisk -lu Also, explain your hd structure. You have sda, sdb, and volume? What are those devices and what's on them. I'm no genius, but maybe I can help (whilst we wait for a techie to look at this) -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
Final suggestion: Start a thread in Installation & Upgrades and ask about proper RAID configuration for Feisty. I assume you are using "software-only RAID 1 using mdadm", correct? I did a little poking around and it's not a simple thing, but you'll get more answers there. -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 120285] Re: Superblock not read at boot
I agree, there is something odd about your fstab. For starters, it lists two swap partitions. If there is some advantage to that I am not aware of it. It may even be bad. Second, couldn't your root partition (/dev/sda1) be paired with the unused partition (/dev/sdb1) in a Raid volume to get improved performance? Or is that not possible with Linux? Lastly, it would appear that /dev/Volume0/lvol0 in fstab is referring to the Raid volume at /dev/sda3 & /dev/sdb3. Exactly how does Raid do that? I would need to read up on Raid. There must be a Raid set-up file somewhere... In short, while there are questions about the use & configuration of Raid, the only oddity in your fstab is the presence of two swap partitions. I would not fool with the entry for /home in fstab until you understand how Raid configures itself. -- Superblock not read at boot https://bugs.launchpad.net/bugs/120285 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955853] Re: Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many a
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955853 Title: Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/955853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955853] [NEW] Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many
Public bug reported: The tracker only allows one colour at a time. Then you must "apply" before moving on to the next one. So what's the point of colour? The previous version worked. You could start one colour, then continue with another, and when you needed to back up you could clear only one colour at a time. This no longer works. Using Sudoku 2.32.1 on Ubuntu 11.04 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-sudoku 1:2.32.1-0ubuntu5 ProcVersionSignature: Ubuntu 2.6.38-13.56-generic-pae 2.6.38.8 Uname: Linux 2.6.38-13-generic-pae i686 Architecture: i386 Date: Thu Mar 15 05:57:40 2012 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429) ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-games UpgradeStatus: Upgraded to natty on 2011-07-07 (251 days ago) ** Affects: gnome-games (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug apport-lpi i386 natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955853 Title: Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/955853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 955853] Re: Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many a
Robert - That's the way it used to work. Now when I click on a different tracker the other color disappears. If I click back on it, then those squares come back. So I only can use one color at a time. What version are you using? If it's SUPPOSED to allow multiple colors simultaneously, it's not working in this version. That would be a bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/955853 Title: Probably not a bug, but the new way tracker works you can only have one color active at a time. I liked the old way much better. You could have several trackers, and back up as many as needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-games/+bug/955853/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
