This is a major bug which basically destroys all documents that are
opened, modified and then saved. This problem is also documented in [1]
and [2].
It practically makes Draw not only unsuable but is a real threat to
existing document based. This is definitely not fixed in 4.1.2 rc3
(saucy) and is
And [3].
[3] https://bugs.freedesktop.org/show_bug.cgi?id=70210
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1244890
Title:
REGRESSION: Draw connector skew is lost on opening
To manage notificati
The issue is still present (Thinkpad T420s) with 3.8.5
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1180513
Title:
lid close actions are ignored laptop always suspends
To manage notifications abou
Great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054948
Title:
dmraid broken for large drives
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug
If co-existence of dmraid and mdadm would be just an incremental step
for later versions, exclusive-or would at least a step forward for mdadm
and I would be happy to test that (isms root + shutdown).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
But wouldn't that simply only imply that dmraid and mdadm are not supposed to
co-exist? I'm a bit puzzled about this change. As far as I understand this, the
auto-assemble rules have been removed just to guarantee the function of dmraid
- temporarily or not.
Automated installation procedure asi
Just for reference, #957494 is an incomplete fix for the readonly issue
mentioned above. mdmon is still missing in the initrd which leads to
read-only arrays. Inclusion of mdmon into the image fixes this. However,
system shutdown is still broken in this case.
--
You received this bug notification
Just for reference, with disable auto-assembly you mean the changes in mdadm
3.2.5-1ubuntu0.2 (#1030292)?
Would one be required to set up custom udev rules or which package version
contains rules for mdadm auto-assembly?
--
You received this bug notification because you are a member of Ubuntu
For new installations, mdadm should be the default. Migration is not
necessary, dmraid could be post-installed. As dmraid isn't under
development anymore and drive capacities and the kind of platform won't
go away, this will sooner rather than later become a widespread critical
issue.
--
You rece
Public bug reported:
Attempting to set up a fresh Quantal system on a system with Intel 'fakeraid'
(imsm, 1.3) and 3TB SATA RAID1. When running the live CD, dmraid identifies the
drives as being of size 746GB (Same effect with a Windows 7 setup without
loading the corresponding Intel drivers pr
dmraid is essentially broken for large drives (unable to set up an imsm raid1
array on 3TB, 'fakeraid'), there is no way around mdadm. Simply disabling mdadm
is not a fix. See also #957494 and #957494.
Since the mdadm package is currently severly broken when the system root is
part of an array
But maybe related/duplicate of #1030292
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054773
Title:
mdadm: support external metadata arrays correctly (from debian)
To manage notifications about th
And it is not a duplicate of #957494
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054773
Title:
mdadm: support external metadata arrays correctly (from debian)
To manage notifications about this
Also [1].
[1] http://comments.gmane.org/gmane.linux.raid/36900
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054773
Title:
mdadm: support external metadata arrays correctly (from debian)
To manag
Also related to this is [1].
[1] http://comments.gmane.org/gmane.linux.raid/36852
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054773
Title:
mdadm: support external metadata arrays correctly (fro
I should add that this is a problem only if the system / is part of the
array itself and therefore must be setup in initrd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1054773
Title:
mdadm: suppor
It is critical to replace dmraid with mdadm as dmraid is unable to deal
with large disk sizes. For a 3TB imsm raid1 dual-boot ('fakeraid') in my
case the disks were shown as ~746GB sized and dmraid -an would not
release them. So the only way was to boot the live cd with nodmraid and
manually instal
Public bug reported:
The mdadm package is currently seriously broken for Intel
IMSM/"fakeraid" setups since mdmon is not part of the initrd (tested on
quantal alpha3) and therefore only sets up a read-only array which
breaks the boot process. If booted from a live cd and entered via a jail
root, m
18 matches
Mail list logo
