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
--
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
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
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
Also, got install.py crashed with AttributeError in module()
** 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
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
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:
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
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
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
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.
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
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
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.
--
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.
--
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
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
17 matches
Mail list logo
