... and it's back on later upgrade. Not sure the circumstances but for
a bit at least it *was* good.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040885
Title:
gnome-terminal auto-restores its si
seems resolved for me after recent update/upgrade on 6-Nov-2012
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1040885
Title:
gnome-terminal auto-restores its size
To manage notifications about this
Not an installation media error. I just spun it on independent hardware
on that's running Natty and VirtualBox; under VirtualVox the media check
found no problems. The drive on the original hardware appears to work
as expected.
Given Lucid's not tip any more, I'm willing to have the bug closed a
There's further traffic on bug 573220 that I posted but can't properly
file as a dupe of this one because of some internal launchpad silliness
as near as I can tell.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/188976
You received this bug notification because yo
note 4 about bug 548691 not real helpful as it's a private bug and I
can't get to it.
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/573220
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
this needs to dupe bug 188976, but presently unable :-(
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/573220
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.
wrong bug status change
** Changed in: ubiquity (Ubuntu)
Status: New => Invalid
** Changed in: ubiquity (Ubuntu)
Status: Invalid => Confirmed
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/573220
You received this bug notification because you are a
changed status to 'Fix Released' since Lucid counts in my book :-)
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
just installed Lucid Lynx from release cd and the disks are back, hooray
** Tags removed: needs-upstream-testing
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Released
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received thi
depending on what the first "this" means, this bug is potentially still
viable as of 10.4 release / Lucid Lynx
I just logged bug 573220 (which I can't flag as dupe right now because
of it's dupe bug 573218 that's a result of impatient clicking and is
unable to be accessed (with OOPS-1582B2194 )).
>From bug 188976
comment 6: the second level of /usr/local was preformatted and thus
possibly leading to error: (see previous comment this bug about
/usr/local/man)
comment 30: it appears as if I was destined for pain by having "tree-
partitioning" wherein I wanted to mount not only /usr/local bu
repeatable.
"OSError: [Errno 21] Is a directory: /target/usr/local/man"
I have that as a directory already since I have a /usr/local partition
I'm trying to reuse ... will retry without that partition (or the other
/usr/local/* partitions I have -- don't ask) and see if the install
succeeds
--
** Visibility changed to: Public
--
ubiquity crashed with OSError in copy_all()
https://bugs.launchpad.net/bugs/573220
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://list
it's been all quiet :-(
On the bright side, it appears as if I can see my disks again via Lucid
Lynx Beta 1, so I'm hopeful for the final release
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a mem
Have posted further files at the behest of the linux-ide mailing list.
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
** Attachment added: "/var/log/syslog from karmic release live session"
http://launchpadlibrarian.net/37373869/karmic-live-syslog
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ubuntu
** Attachment added: "/var/log/kern.log from karmic release live session"
http://launchpadlibrarian.net/37373856/karmic-live-kern.log
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ub
** Attachment added: "/var/log/dmesg from karmic release live session"
http://launchpadlibrarian.net/37373836/karmic-live-dmesg
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ubuntu
B
I'm out of ideas but am willing to chase ... if someone provides a hint
on which way to go.
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
lspci seems the same, excepting a bit more output as I ran it as root
rather than a user. Truncating to the "interesting" device [note
"Capablities" section now filled out]
00:10.0 Mass storage controller: Promise Technology, Inc. PDC20265 (FastTrak100
Lite/Ultra100) (rev 02)
Subsystem:
Running gparted from the karmic-live release cd, it recognizes the drives
(albeit with different "letters" (eg: sda vs sdc)) and presents a little
warning triangle, which, when double clicked says:
--
e2label: No such file or directory while trying to open /dev/sda1
Couldn't find a valid filesyst
changed tag from kernel-jaunty to kernel-karmic because the bug is in
karmic, not jaunty, so if kernel-{release} is valid as a tag, it's a
karmic issue, not jaunty. Although the files attached to date are from
jaunty.
** Tags added: kernel-karmic
** Tags removed: kernel-jaunty
--
unable to reco
if I rebooted and attached files similar to note 1 for karmic-live,
would that help diagnose the problem? Or at least get some constructive
hinting going on?
TIA
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
You received this bug notification beca
Attachments are from a viable Jaunty install.
--
unable to recognize some disks on upgrade to Karmic
https://bugs.launchpad.net/bugs/489685
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.ub
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/36206452/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/36206453/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/36206454/Dependencies.txt
** A
Public bug reported:
I have a Gigabyte GA-7DXR motherboard with an onboard RAID controller:
Promise 20265. It's running in unraided mode right now with two drives
hung off of one IDE port. In all installations of ubuntu on this
hardware prior to Karmic, the partitioning has not been an issue. A
26 matches
Mail list logo
