** Description changed:
Binary package hint: ding
-
- The agrep package needs to be installed so number of allowed errors menue in
not greyed out and approximate matches can be found.
+ The agrep package needs to be installed, otherwise the number of
+ allowed errors menu item is greyed
@Surbhi
With natty (mdadm capable of hotplugging) the hostname should probably
not be exposed in the the initramfs (boot may stay unencrypted). Are you
applying that patch in 11.04?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Duplicity as backend uses rdiff-backup and would bring network support
but also space efficient incremental diffs and encryption features
http://duplicity.nongnu.org/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Lorenzo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/549172
Title:
pam config: not yet including common-session modules
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
The UUID of the filesystem created on a raid mirror is of course present
and identical on any member devices of the raid mirror mirror.
The raid member device (superblocks) are probably also all taged with
(another) UUID of the raid device they assemble, plus the device ID.
Mdadm seems to handle
** Description changed:
Binary package hint: debian-installer
Following is a little informative text for the set up users and
passwords stage:
---
- It is easy for multiple users to collaborate on a debian/ubuntu system.
- Just keep in mind that access to files always depends on
Sharing a hotplug raid array to two sync two machines is a very nice use
case iMac, thanks for sharing your experience. I did only intentionally
segment an array prior to performing updates so far.
A place where information experience with the topic is shared and your
workarounds would fit in
should be specified and added *as a new feature*. Since the current
documentation and implementation do not define any behavior for this
diverged RAID1 scenario
You could build upon this thread:
http://comments.gmane.org/gmane.linux.raid/27822
(but leave out the parts that was caused by naming
Surbhi you're very welcome. I am glad if some of our analysing and
comments turned out to be helpful for you, and you are actually about to
get ubuntu's raid setup into shape. https://wiki.ubuntu.com/ReliableRaid
I think with adopting the upstream version and mechanisms you're already
clearing the
Setting the hostname in initramfs is probably a good workaround for
older versions.
New mdadm versions may need an option to not check the hostname, and
only go by the UUIDs of md devices and filesystems for proper
hot/coldplug support.
--
[-UUIDudev] HOMEHOST system does not work inside initrd
Guys, make sure what you are seeing is not your machine saving your from
data loss. Bug #531240 (root raid_members opened as luks). Especialy if
you are only seeing this occasionally/with not all member devices
present.
The check to only open /dev/mapper/ is your last hold in preventing data
loss
I don't think there is anything practical that could be changed in md or
mdadm to make it possible to catch this behaviour and refuse the assemble the
array...
The original topic of the linux-raid discussion
http://comments.gmane.org/gmane.linux.raid/27822 suggested the idea to
detect
Surbhi, you actually have an ubuntu system on raid installed and the mapfile is
carried over?
Then please state the exact version and details and say it works for you.
If not please leave the bug filed as it was, documenting a bug in the ubuntu
mdadm package.
** Changed in: mdadm (Ubuntu)
@Surbhi
when you go around changing many bug statuses you chould probably subscribe to
mdadm bug mail in general and be careful with changes.
--
[-UUIDudev] mdadm fails to assemble raid during boot
https://bugs.launchpad.net/bugs/541058
You received this bug notification because you are a
*** This bug is a duplicate of bug 495370 ***
https://bugs.launchpad.net/bugs/495370
** This bug has been marked a duplicate of bug 495370
Please upgrade to a non-outdated version
--
Please merge mdadm 2.7.1.1 (main) from Debian unstable (main)
https://bugs.launchpad.net/bugs/603582
You
*** This bug is a duplicate of bug 495370 ***
https://bugs.launchpad.net/bugs/495370
** This bug has been marked a duplicate of bug 495370
Please upgrade to a non-outdated version
--
mdadm needs update to 3.1.2
https://bugs.launchpad.net/bugs/606210
You received this bug notification
I got sick of unplugging a hard drive and then waiting for the entire
array to rebuild.
Maybe try mdadm's --monitor --test option to generate test messages.
(Or have your arrays --grow a bitmaps to speed up resync.)
--
mdadm monitor feature broken, email notification not set up, nor using
See https://wiki.ubuntu.com/ReliableRaid
and the bugs with [-UUIDudev].
You may well find the reason and workaround of your md devices that are
gone after reboot in one of the other bugs filed against the mdadm
package that is distributed with ubuntu, but has not seen any
maintenance for years.
Just booted a 10.04 machine with root on lvm on on luks on raid with
an incomplete array.
It failed to degrade the array and boot of course because the mdadm
package is broken and unmaintained since years in ubuntu, but what is
relevant here is the cryptsetup prompt that showed before failing
** Description changed:
Binary package hint: ubuntu-docs
+ As long as we do not provide a reliable raid setup,
+ https://wiki.ubuntu.com/ReliableRaid:
- As long as we do not provide a reliable raid setup,
- https://wiki.ubuntu.com/ReliableRaid
+ (Package mdadm has not been synced for
May this be related? (500GB disk): Bug #599515 mdadm misdetects disks
instead of partition
--
mount: mounting /dev/md0 on /root/ failed: Invalid argument
https://bugs.launchpad.net/bugs/569900
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
md_dx stuff: Bug #551719 Bug #469574, Bug #532960, ...
They have workarounds and even some fixes in stable upstream for years but who
cares.
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug notification because you are a member of Ubuntu
Thanks dino, that does not seem to be lucid then, every case where
stable means no bugfix for core parts is unfortunate.
--
Current grub-pc takes several minutes to show menu
https://bugs.launchpad.net/bugs/420933
You received this bug notification because you are a member of Ubuntu
Bugs, which
May this be Bug #469574 or Bug #532960 ? They have workarounds.
--
non-partitionable array become partitionable after reboot
https://bugs.launchpad.net/bugs/598771
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
May this be Bug #469574 or Bug #532960 ? They have workarounds.
--
mdadm cannot assemble array
https://bugs.launchpad.net/bugs/599135
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
What latest 2 updates? Have those come to current buggy production
lucid?
There are unfortunately still minutes to wait each day due to grub with
Raid1 Bug #577369
--
Current grub-pc takes several minutes to show menu
https://bugs.launchpad.net/bugs/420933
You received this bug notification
Use gedit with the snippet plug-in installed, tools-snippets and import
the file from http://mga.tiny.googlepages.com/openerp.tar.gz (or bzr
branch lp:openobject-gedit) to the python snippets. See screencast at:
http://openerp.tv/display.php?rnd=NzA=
** Changed in: gedit (Ubuntu)
Status:
The workaround generates a mdadm.conf describing active arrays and
updates the initramfs for all kernels, so they will contain the new
file.
--
[-UUIDudev] new array not assembled correctly after reboot
https://bugs.launchpad.net/bugs/469574
You received this bug notification because you are a
Bug #469574: The workaround generates a mdadm.conf describing active
arrays and updates the initramfs for all kernels, so they will contain
the new file.
--
if array is given a name, a strange inactive md device appears instead of the
one created upon reboot
Proposed package seems to work fine here, didn't crash again.
--
[MASTER] Lucid 2.6.32-16 crashed to login screen - miCopyRegion
https://bugs.launchpad.net/bugs/539772
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
May this be Bug #469574 or Bug #532960 ? They have workarounds.
--
if array is given a name, a strange inactive md device appears instead of the
one created upon reboot
https://bugs.launchpad.net/bugs/576147
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Michel, I don't understand how that could explain why some users are not
notified with the download all in background option.
The boxes that show pending security updates when manually opening
update-manager even though install security updates without
confirmation has been configured actually do
Micheal of course, sorry.
I can confirm the lucid behavior of no update notification with auto
security updates enabled on a fresh install.
That looks like a separate issue, though.
--
security updates not installed daily as configured
https://bugs.launchpad.net/bugs/549217
You received this
** Description changed:
Original Report (also confirmed with 9.10 and 10.04 beta1):
On a freshly installed ubuntu-7.10-alternate, with latest apt-get
update.
When the 'mdadm' package is installed, the system fails to boot
successfully, and ends up at the initrd '(busybox)' prompt.
You could check #158918 and mark this a duplicate if appropriate.
--
Installing mdadm renders lucid desktop unbootable
https://bugs.launchpad.net/bugs/591696
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
There doesn't seem anything special to be necessary to reproduce.
Maybe it's the usage pattern. The computers are usually not running for
more then 2-3 hours at at time, then shut down until next boot.
Konstantin does not get any out of the box notifications of security updates.
Original
The boot loader really needs provide some more verbose output to give
any hints of what it's trying to do and may go wrong.
** Summary changed:
- Grub loading. takes very long
+ Grub loading. raid1 rootfs takes very long
--
Grub loading. raid1 rootfs takes very long
The impotance is serious. (please adjust)
Have confirmed this behavior on another machine.
Security updates are available but don't get installed automatically as
the configuration option claims, nor are updates signaled to the user.
--
security updates not installed daily as configured
Something is wrong with the non-existing maintenance of a basic system
component like mdadm in ubuntu. Not even the updated debian packages get
synced.
** Summary changed:
- Please upgrade to 3.1.x for lucid
+ Please upgrade to a non-outdated version
--
Please upgrade to a non-outdated version
10.04
Opening update-manager manually showed it hasn't run since 25 days!!!
(Contrary to the setting to check for updates daily, and the computer is
used several times each day.)
And after manually checking for updates: Contrary to the setting to
install security updates automatically, no
** Summary changed:
- Update manager not showing notification of daily updates
+ security updates not installed daily as configured
--
security updates not installed daily as configured
https://bugs.launchpad.net/bugs/549217
You received this bug notification because you are a member of Ubuntu
What's your business messing with bug status? Please explain.
** Changed in: mdadm (Ubuntu)
Assignee: vingslagsvisvid...@gmail.com (bjerry) = (unassigned)
--
mdadm : boot failed sometimes, no devices found
https://bugs.launchpad.net/bugs/120504
You received this bug notification because
Please get the PPA fix for this crash bug into the lucid release.
--
[MASTER] Lucid 2.6.32-16 crashed to login screen - miCopyRegion
https://bugs.launchpad.net/bugs/539772
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Coz: So other distros dont't take ages to detect your disks?
Maybe the boot option raid=noautodetect helps in you case? Bug #551719
--
disk detection is real slow with some hardware (timout shell drops)
https://bugs.launchpad.net/bugs/278176
You received this bug notification because you are a
** Summary changed:
- enabled kernel raid autodetection disturbs udev/mdadm (initramfs later)
+ boot delay and udev/mdadm disturbance (obsolete kernel raid autodetection)
--
boot delay and udev/mdadm disturbance (obsolete kernel raid autodetection)
https://bugs.launchpad.net/bugs/551719
You
** Changed in: adduser (Ubuntu)
Status: Incomplete = New
** Summary changed:
- adduser silently removes users from groups
+ adduser user group removes all other ldap users from group
--
adduser user group removes all other ldap users from group
https://bugs.launchpad.net/bugs/260086
You
Did you follow README.debian and issued the following to create the user?:
#su - postgres -c createuser --createdb --no-createrole --pwprompt openerp
However #327998 says NOT to createdb ! What to do?
Did you edit /etc/openerp-server.conf and added the password you chose
to the db_password =
The README.debian seems in fact to miss point 2. Save the chosen
openerp database user password to /etc/openerp-server.conf (it goes 0.
1. 3. 4.)
** Description changed:
Binary package hint: openerp-server
- When starting the openerp-server, it is not working.
- I guess it there is a
Debconf may, during install,
if /etc/openerp-server.conf is not present already,
ask for the name, server and password for the openerp database,
create the user if its a local database and user does not exist, and
and save the details to /etc/openerp-server.conf.
--
server can not
Public bug reported:
Binary package hint: openerp-server
README.debian says:
* openerp-server in the upstreams configuration listens by default to *all*
interfaces. For security reasons, we do restrict it in the Debian packages
to listen only on localhost. If you need to change this,
** Summary changed:
- server can not start after install
+ server can not start after package is installed
--
server can not start after package is installed
https://bugs.launchpad.net/bugs/528006
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The createuser line mentioned in README.debian (and any debconf
configuration should probably also contain --no-superuser, to not make
crateuser prompt for that decision. (The openerp user does not need to
be able to mess with the whole postgres setup.)
--
server can not start after package is
Public bug reported:
Binary package hint: openerp-server
README.debian advices to create an openerp database user like this:
#su - postgres -c createuser --createdb --no-createrole --pwprompt
openerp
However this advice (and any debconf postinst configuration should
probably also contain the
Beware of old superblocks, getting available again when (re-)creating
partitions. Superblocks stay on the disks if you don't mdadm --zero-
superblock the partition, prior to deleting the partition from the
partition table.
--
Mdadm array fails to assemble on boot.
Since we have to consider mdadm/raid as not maintained in ubuntu, maybe
check other bug reports to see if their workarounds may help for this
case.
--
Mdadm array fails to assemble on boot.
https://bugs.launchpad.net/bugs/573477
You received this bug notification because you are a member of
This is simpy an unneeded and adverse option enabled in the default
kernel configuration. Not much to to with upstream.
** Tags added: kernel-config
** Tags removed: kernel-series-unknown kj-triage needs-kernel-logs
needs-upstream-testing
--
enabled kernel raid autodetection disturbs
** Description changed:
+ Ubuntu still uses the kernel option
+ CONFIG_MD_AUTODETECT=y
+ thus enables the kernel's RAID autodetection during boot.
- Ubuntu's current kernel option
- CONFIG_MD_AUTODETECT=y
- enables the kernel's RAID autodetection during boot.
-
- Aside from causing a delay
You searched the wiki for offline update?
--
Ubuntu should provide update packages for download and use for offline users
https://bugs.launchpad.net/bugs/572776
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: grub2
The Grub loading. message only shows if the shift key was held down,
otherwise only a blank screen with a blinking cursor is shown.
It takes over 60 seconds before boot continues / menu is shown.
/boot is on raid1 (md0)
and the root fs is a
Ext2 for the root fs has definitely been misdetected during grub install, it is
ext4.
Manually changing this in grub.cfg made no difference, though.
--
Grub loading. takes very long
https://bugs.launchpad.net/bugs/577369
You received this bug notification because you are a member of Ubuntu
I've #commented out all things related to set root='(vg0-root)', but
that did not have an effect on the delay either.
--
Grub loading. takes very long
https://bugs.launchpad.net/bugs/577369
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Summary changed:
- The default ~/Private name is not very clear
+ The default ~/Private name is confusing (general permissions) but not crypt
specific
--
The default ~/Private name is confusing (general permissions) but not crypt
specific
https://bugs.launchpad.net/bugs/575096
You received
** Description changed:
Binary package hint: ecryptfs-utils
What ecryptfs does with ~/Private really is (on-disk) encrpytion.
Private in terms of permissions is a different thing. Using another
- default, more like ~/Encrypted would avoid misconceptions, and avoid
- conflicting with
Specifying the UID on creation is not the only advanced option missing.
Generally see it quite troublesome when gnome apps are cutting
functionality away, not uncluttering or easing or explaining advanced
options in the UI but actually delivering regressions. GDM just did the
same, it used to
OK, hopefully system users can be shown for anybody to see in a next
version.
--
[users-admin] No option to show system users
https://bugs.launchpad.net/bugs/574379
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
Public bug reported:
Binary package hint: ding
The agrep package needs to be installed so number of allowed errors menue in
not greyed out and approximate matches can be found.
The 'Recommends' field should list packages that would be found
together with this one in all but unusual
I don't see any change in the CONFIG_MD_AUTODETECT setting.
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Changed in: linux (Ubuntu)
Status: New = Confirmed
--
enabled kernel raid autodetection disturbs udev/mdadm (initramfs later)
Just meant the option to show system users.
--
[users-admin] No option to show system users
https://bugs.launchpad.net/bugs/574379
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
I guess it's what I expect from a GUI.
I expect it to be of help for new users not yet familiar with things and
it to suggest appropriate actions the user may not be aware of but might
likely be interested in.
I.e. now, you have to be aware that users are made members to a couple
of groups and
On a fresh install of 10.04 there was now an option to save the
default.keyring password to the login.keyring. And it works (as long as
autologin is disabled). So I'd consider my issue solved. Thanks!
** Changed in: seahorse (Ubuntu)
Status: New = Fix Released
** Changed in: gksu (Ubuntu)
But that bug's duplicate claims to be fixed!?
--
System won't boot after upgrade to 10.04
https://bugs.launchpad.net/bugs/573272
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
Thanks, that is very good you already implemented the path to be
configurable.
The issue here is more about the particular default, though.
People using the user private group scheme (used and advocated for
user collaboration in debian/ubuntu system, but still broken due to some
minor bugs) use
I see, thank your the message.
Indeed, Private makes a nice contrast with Public, but to keeping
something Private within a filesystem isn't necessarily much connected
with on-disk-encryption at all, or would you think otherwise?
I do understand we're not going to change the default crypt-dir
I mean Private does make good sense for a subdirectory provided to
users to keep files private from other users of the system, regardless
if it is (on-disk) encrypted or not.
--
The default ~/Private name is not very clear
https://bugs.launchpad.net/bugs/575096
You received this bug notification
** Summary changed:
- common-session pam configuration not included
+ pam config: not yet including common-session modules
--
pam config: not yet including common-session modules
https://bugs.launchpad.net/bugs/549172
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
- Binary package hint: sudo
+ A simple package configuration issue.
- The pam configuration seems to be incomplete in the sense that no
- common-session modules are included in sudo's pam config.
+ PAM modules like pam_umask, limits and pam_env don't work with sudo
+
Cofirming it works here, too.
** Changed in: gksu (Ubuntu)
Status: Confirmed = Fix Released
--
gksu breaks X apps when /etc/sudoers has NOPASSWORD:
https://bugs.launchpad.net/bugs/66328
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Summary changed:
- pam_umask.so missing in common-account
+ pam_umask.so not called in /etc/pam.d/common-session{,-noninteractive}
--
pam_umask.so not called in /etc/pam.d/common-session{,-noninteractive}
https://bugs.launchpad.net/bugs/253096
You received this bug notification because you
The issue that sudo's pam config is not including the common-session
configuration is now tracked separately Bug #549172
and the /etc/pam.d/common-session{,-noninteractive} patch would be the right
seed to call pam_umask.
--
pam_umask.so not called in
** Description changed:
A simple package configuration issue.
PAM modules like pam_umask, limits and pam_env don't work with sudo
because no common-session modules are included in sudo's pam config
file.
/etc/pam.d/sudo should be shipped containing
@include
** Patch added: include-common-session.patc
http://launchpadlibrarian.net/47786643/include-common-session.patch
--
pam config: not yet including common-session modules
https://bugs.launchpad.net/bugs/549172
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The following wikipage contains valuable information about working with
different user accounts
https://wiki.ubuntu.com/MultiUserManagement
--
run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
https://bugs.launchpad.net/bugs/275304
You received this bug
*** This bug is a duplicate of bug 275304 ***
https://bugs.launchpad.net/bugs/275304
** This bug has been marked a duplicate of bug 275304
run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
--
gksu to regular users broken
Public bug reported:
Binary package hint: ecryptfs-utils
What ecryptfs does with ~/Private really is (on-disk) encrpytion.
Private in terms of permissions is a different thing. Using another
default, more like ~/Encrypted would avoid misconceptions, and avoid
conflicting with ~/priv or
Public bug reported:
Binary package hint: gnome-system-tools
When creating a new user, there is no (advanced tab/button) option to
specify those options for the new user.
Since gdm does not support to display only selected or unselected users
in the user list, you need to create users that
** Description changed:
Binary package hint: gnome-system-tools
- When creating a new user, there is no (advanced tab/button) option to
- specify those options for the new user.
+ When creating a new user in 10.04, there is no (advanced tab/button)
+ option to specify those options for the
Will g-s-t also adjust the ownership of files in the filesystem upon
changing a user's ID, or would that be a different issue?
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Is gst using usermod? Its manpage says:
-u The ownership of files outside of the users home directory must be
fixed manually.
--
[users-admin] Changing UID doesn't work
https://bugs.launchpad.net/bugs/542183
You received this bug notification because you are a member of Ubuntu
Bugs,
Mind you that I'd consider any device-kit privilege escalation
implementation that isn't configured to support/use (be itself easily
configurable by) standard unix user group memberships as a regression.
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
Instead pulling users from the audio group etc. to make user switching
work, device-kit configuration needs to take user groups into account.
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
https://bugs.launchpad.net/bugs/433654
You received this bug notification
Public bug reported:
Binary package hint: gnome-system-tools
The advanced option rightly allows to set G/UIDs below the standard rage (i.e.
within the range of dynamically allocated system users, in debian: 100-999
created by adduser --system)
But since the option to show those dynamically
** Also affects: consolekit (Ubuntu)
Importance: Undecided
Status: New
--
[Karmic][Lucid] Only one user has sound; no hw shows in Sound Preferences
https://bugs.launchpad.net/bugs/433654
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+ Sound does not work for different users if they belong to the audio
+ group.
+
+ A workaround is to remove the users from the audio group. With this
+ however simply managing individual device access based on standard group
+ memberships stops working (regression).
+
+
Public bug reported:
Binary package hint: mozilla-noscript
Lucid branch exists but no packages.
No explanation is available of why this popular security add-on has
apparently been dropped.
https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel
/extension-list
** Affects:
Found explanation:
https://wiki.ubuntu.com/DesktopTeam/Specs/Lucid/FirefoxNewSupportModel
Please link to this from the package overview pages instead of the drop-
list.
--
no package available/build in lucid
https://bugs.launchpad.net/bugs/572923
You received this bug notification because you
Besides: Allready installed packages should really get uninstalled when
you drop the package. Otherwise they sit around possibly dirsturbing
manually installed add-ons, while they won't work in lucid and later
anyway.
--
no package available/build in lucid
https://bugs.launchpad.net/bugs/572923
Public bug reported:
Binary package hint: update-manager
10.04
http://www.ubuntu.com/getubuntu/upgrading
But upgrade from alternate CD downloads *all* packages again. Not only
some updated packages.
** Affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
** Also affects: update-manager
Importance: Undecided
Status: New
** Also affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- boot failure with LVM on RAID
+ dist-upgrade LVM on RAID: boot failure
--
dist-upgrade LVM on RAID: boot failure
Public bug reported:
9.10 - 10.04 update crashed
needed to reboot into rescue mode, select dpkg repair and reboot to be
able to log in.
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: libggz2 0.0.14.1-1build2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/46720096/Dependencies.txt
** Attachment added: VarLogDistupgradeAptlog.gz
http://launchpadlibrarian.net/46720097/VarLogDistupgradeAptlog.gz
** Attachment added: VarLogDistupgradeApttermlog.gz
201 - 300 of 1115 matches
Mail list logo
