finaly found that cryptsetup isLuks is actually used in
scripts/local-top/cryptroot line 236:
if /sbin/cryptsetup isLuks $cryptsource /dev/null 21; then
Please remember to have the bootscripts output messages about what they
are doing and their results to the (hidden) text console. Not
** Summary changed:
- User Privileges ignored
+ user:group privileges ignored
** Summary changed:
- user:group privileges ignored
+ policykit breaking unix user/group privileges
--
policykit introduction broke unix user/group privileges
https://bugs.launchpad.net/bugs/326135
You received
** Description changed:
I have set up a number of user accounts. On one of these accounts I
adjusted the user privileges (System-Administration-Users and
Groups-Properties-User Privileges). For one particular user I de-
selected the two options:
- * Connect to Internet using a
Lets think some more of signature rules.
Crypt vs Container
- any crypt should be lower then other containers (not fs) because whaterver
is in it wouldn't be visible or is random.
Crypt vs FS
- old fs signatuers may have remained.
RAID vs LVM-LV
- LVs never reside on RAIDs directly (always
** Description changed:
Binary package hint: util-linux
After the member is opened as luks device it is booted instead of the md
device, while the raid remains inactive.
I first noticed /proc/mdstat reported the root raid as inactive
(although the system seemed to run fine!).
My current conception: (WARNING)
Both blkid and cryptsetup isLuks misreport a raid_member as luks when
checking devices, but blkid correctly reports RAID if the device is set
up (mounted/active) in the system as intended (after
install/update/recover).
On boot what happens depends on the order
Cool, that I didn't know from the thread my search turned up about
blkid. (increases the bug weight though)
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I think on hotplug systems mdadm.conf should generally not contain any
specific ARRAY references, maybe it should explicity mention any like
this:?
DEVICE any
HOMEHOST any
ARRAY any
This whole bussiness of locking down array assembly (homehost,ARRAY) may
just be due to the historical
** Summary changed:
- [karmic] mdadm, initramfs missing ARRAY lines
+ [karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
--
[karmic] mdadm.conf w/o ARRAY lines but udev/mdadm not assembling arrays.
https://bugs.launchpad.net/bugs/136252
You received this bug
This is a bug with mdadm --incremental not doing hotplug, because it looks for
permission to do so in mdadm.conf.
On hotplug systems mdadm.conf should not have contain any specific references,
maybe it should explicity mention any like this:?
DEVICE any
HOMEHOST any
ARRAY any
This whole
** Summary changed:
- boot from manually constructed raid1 root fails because of missing hostname
in initramfs
+ boot fails: mdadm not looking for UUIDs but hostname in superblocks
--
boot fails: mdadm not looking for UUIDs but hostname in superblocks
https://bugs.launchpad.net/bugs/226484
[cryptsetup] waits for the physical device to be available, decrypts it
as needed, then mounts it. No other event handling is required or
appropriate.
Think of the following example.
As far as I can see cryptsetup in initramfs is not called on the event
that a crypt device appears. It seems
copying this conclusion from #531240 as it rather belongs here
As far as I can see cryptsetup in initramfs is not called on the event that a
crypt device appears. It seems cryptsetup in initramfs is currently rather
linear script driven: the cryptsetup script has its own while loop
** Changed in: mdadm (Ubuntu)
Status: Invalid = Confirmed
--
boot fails: mdadm not looking for UUIDs but hostname in superblocks
https://bugs.launchpad.net/bugs/226484
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Summary changed:
- boot impossible due to missing initramfs failure hook integration
+ boot impossible due to missing initramfs failure hook / event driven initramfs
--
boot impossible due to missing initramfs failure hook / event driven initramfs
https://bugs.launchpad.net/bugs/251164
You
Scott, I put you on here because from your upstart/mountall experience you may
well spot flaws and benefits in the design.
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/251164/comments/15
--
boot impossible due to missing initramfs failure hook / event driven initramfs
Err, it happened again, reduncancy in the system is destroyed,
cryptsetup opened a raid member and it got mounted leaving the raid
incomplet/inactive:
md3 : inactive sda7[0](S)
blkid (now again) returns TYPE=crypto_LUKS for the raid member.
When I run su cryptsetup isLuks on raid members or
Public bug reported:
Binary package hint: mdadm
Anybody who cares about redundancy to use mdadm probably cares enough
about redundancy to want being informed if redundancy is degraded.
Debian systems do have at least local mail enabled and package mdadm
asks for a mail address to notify during
it's still a bug in blkid. It's blkid that wrongly detects the LUKS
UUID on a device that's a RAID member.
Yes, your of course right, and if cryptsetup isLuks is itself scanning
for a luks signature (without giving RAID precedence) it got the same
bug. Can you rule that out / know for sure that
Thank you Paul, for spreading that. I am backing up the ubuntu md raid
systems now though, and switching them to a distro that does less hectic
transitions and leaving things like raid or boot up unreliable in the
process.
--
mountall and cryptsetup will fight for the console when not using
cryptsetup is event-driven in lucid.
good news!
including in initramfs?
can you tell if cryptsetup isLuks correctly reports false for luks on
raid members?
(or with what test command can I tell? This gives me nothing:
r...@localhost:~# cryptsetup isLuks /dev/hda7
r...@localhost:~#
)
--
** Summary changed:
- mdadm degrades all arrays (from initramfs) instead of just those required to
boot
+ initramfs' mdadm degrades all arrays (not just those required to boot)
--
initramfs' mdadm degrades all arrays (not just those required to boot)
https://bugs.launchpad.net/bugs/497186
You
** Description changed:
Binary package hint: mdadm
-
- It is said that the intrepid fix to Bug #120375 added support to mdadm and
initramfs-tools for configurable booting degraded RAIDs, but a systems with
/home on a degraded array doesn't come up.
+ It is said that the intrepid fix to
On https://wiki.ubuntu.com/ReliableRaid See: How would you decide what
device is needed?
Only raids required for the rootfs should be started degraded if they
haven't come up for a while.
(Within the ubuntu hotplug-scheme /usr/share/initramfs-
tools/hooks/cryptroot contains code that may be
** Description changed:
Binary package hint: mdadm
+ after a timeout mdadm in initrams degrades all arrays instead of just
+ those required for the rootfs.
- The dependencies are not checked, it looks into /proc/mdstat and uses mdadm
--assemble --scan --run.
+ The dependencies are not
** Summary changed:
- mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents
hotplug autodetection
+ mdadm.conf created with explicit ARRAY statements, and HOMEHOST !=any
prevents hotplug autodetection
--
mdadm.conf created with explicit ARRAY statements, and HOMEHOST !=any
@SoulWax: Did you follow and use the manual fix of the ubuntuforums link
on https://wiki.ubuntu.com/ReliableRaid ?
Sounds like bug #252345
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a member of Ubuntu
Bugs, which
This behaviour actually not only breaks the autodetection of (complete)
hot plugged md arrays from another systems, but breaks every array newly
created on ubuntu systems (as ubuntu uses the hotplug scheme) .
For instructions on updating the initramfs refer to:
** Changed in: mdadm (Ubuntu)
Status: Incomplete = Fix Released
--
udev not using mdadm incremental
https://bugs.launchpad.net/bugs/157981
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- mdadm.conf with explicit ARRAY statements, and HOMEHOST !=any prevents
hotplug setup
+ raid setup fails due to mdadm.conf with explicit ARRAY statements and
HOMEHOST !=any
--
raid setups fail due to mdadm.conf with explicit ARRAY statements and HOMEHOST
!=any
** Description changed:
Binary package hint: debian-installer
On systems that are set up statically mdadm.conf is often used to list
the md devices that should be set up and the startup script just calls
mdadm --assemble --scan.
But on systems oriented towards hotplug ability this
The following will recreate a static mdadm.conf (a workaround) but is not a fix
to the issue (disfunctional hotpluging):
# /usr/share/mdadm/mkconf force-generate /etc/mdadm/mdadm.conf
# update-initramfs -k all -u
--
raid setups fail due to mdadm.conf with explicit ARRAY statements and
...we should also ship PolicyKit config files that make use of these
groups.
You're tres right, Milan. But you showed already twice a desktop guy
that actually learned/understands the *nix systems before not breaking
them but hooking in to them :) Kudos!
--
User Privileges ignored
New observation: When booting the alternate CD into rescue-mode in a
luks on raid system, it asks passphrases for the raid members instead of
the md device.
Problem: cryptsetup (not beeing udev but boot script driven, and looking
for luks headers on its own?) really needs to be hooked into the
** Summary changed:
- blkid reports root raid_member (on usb) as luks, which is booted while raid
remains inactive
+ breaking raid: root raid_member opened as luks
--
breaking raid: root raid_member opened as luks
https://bugs.launchpad.net/bugs/531240
You received this bug notification
** Description changed:
Binary package hint: util-linux
- I noticed /proc/mdstat reported the root raid as inactive (although the
- system seemed to run fine!).
+ After the member is opened as luks device it is booted instead of the md
+ device, while the raid remains inactive.
+
+ I first
debian init script has been removed but no upstart job has been created
to start/run necessary regular (non-rootfs) arrays degraded.
--
non-root raids fail to run degraded on boot
https://bugs.launchpad.net/bugs/259145
You received this bug notification because you are a member of Ubuntu
Bugs,
Public bug reported:
Binary package hint: util-linux
I noticed /proc/mdstat reported the root raid as inactive (although the
system seemed to run fine!).
Looking further it seemed like during boot the system has unlocked and mounted
the rootfs using (only) one raid_member located on an
Scott wrote:
Since moving to util-linux, we set the blkid cache to a path under /dev so
it's wiped after each reboot
Has that been reverted?
On my 9.10 /etc/blkid.tab was present, outdated (nov 09) and wrong.
--
Wrong type in blkid cache causes fsck on boot to fail
Ah, I have found /dev/.blkid.tab recent but still wrong (#531240).
--
Wrong type in blkid cache causes fsck on boot to fail
https://bugs.launchpad.net/bugs/316322
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
---
util-linux (2.16-1ubuntu5) karmic; urgency=low
* Always return encrypted block devices as the first detected encryption
system (ie. LUKS, since that's the only one) rather than probing for
additional metadata and returning an ambivalent result. LP: #428435.
might that
A (more or less wild) guess why this misreporting may not have surfaced
with any bad effects before:
After booting manually and reassembling the array manually I noticed the
usb disk did fail after a while and was dropped from the array, so it
has become unreliably.
So maybe it is this condition
Nahsei, do you use lines like client http accept dst
archive.ubuntu.com and the domain names are being resolved and firehol
started correctly on boot?
--
firehol not started on boot (with START_FIREHOL=yes)
https://bugs.launchpad.net/bugs/490317
You received this bug notification because you are
The directories of user2 aren't group writeable.
Well then they really should show with a lock symbol (read-only). Looks
like this may be a (different) bug that you are experiencing. (and since
you are only shown one emblem per icon don't see any difference to the
list view icons either)
For my
** Description changed:
Binary package hint: nautilus
9.10: Nautilus 2.28.1
- A file/directory without write permissions shows a lock emblem even
- though you can access it.
+ In the list view the difference in permissions does not result in
+ appropriate icon differences. (only one
Actually the lock emblem (read-only) you are not seeing is bogus when
one does not have any read permissions. Maybe you are using a newer
version that recognizes this? (and avoids showing multiple emblems)
Are there any other emblem combinations used that may get messed up in
list view?
--
in
** Changed in: ubuntu
Status: Incomplete = Confirmed
** Changed in: ubuntu
Status: Confirmed = Incomplete
--
Inaccessible directory has same emblem as read-only directory
https://bugs.launchpad.net/bugs/489977
You received this bug notification because you are a member of Ubuntu
Hm, do your user2's directories have the same permissions as mine?
Or are your directories of user2 group writeable? It would be OK for
them not to have a lock emblem then, if you are browsing as user1 and
member in the user2 group.
Further details on the issue I observe:
* The theme used in
Thank you for helping out here. I am using the humanity theme though,
and seeing this.
I checked back, and can more precisely add that I see this after:
I added a second user user2 to the machine and added user1 to the user2
group. After newly logging in as user1 and browsing to
/home/user2
Thanks for the pointer!
--
LD_LIBRARY_PATH settings in /etc/profile lost
https://bugs.launchpad.net/bugs/367814
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
Public bug reported:
Binary package hint: user-setup
/home/user/.Private gets currenty mounted as /home/user with
permissions set to rwx-- by default.
This is changing the default to have homedirs readable among users and
for example breaks sharing files and having ~/public_html work.
We
Fedora's sandbox -X seems to be made for this.
** Summary changed:
- wrong ownership of .Xauthority and /tmp/libgksu-xxx
+ run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
--
run as different user fails (wrong ownership of .Xauthority and
/tmp/libgksu-xxx)
Good choice I think. Cutting down the settings forced with g-s-t GUI
profiles is probably also a good measure for supporting the adduser
profiles (or any other system wide profiles).
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You
** Summary changed:
- Ship adduser with user profiles to unify their handling by different tools
+ Ship adduser.conf as symlink to user profiles to unify their handling by
different tools
** Description changed:
Binary package hint: adduser
+ Default profiles could be shiped for
** Summary changed:
- Ship adduser.conf as symlink to user profiles to unify their handling by
different tools
+ Ship adduser.conf as symlink to a profile (provides switchable profile
feature for all frontends)
** Summary changed:
- Ship adduser.conf as symlink to a profile (provides
If policykit broke the desktop and unprivileged profiles this is a bug
with policykit not being set up to honor those unix groups.
I don't see user profiles only with respect to g-s-t. It seems usefull
also for admins not using g-s-t. As adduser is supposed to be thesystem
wide tool, even the
If policykit broke the desktop and unprivileged profiles this is a bug
with policykit not being set up to honor those unix groups.
It seems to merely match all users in admin group to root.
** Also affects: policykit-1 (Ubuntu)
Importance: Undecided
Status: New
** Also affects:
Phil, thank you for pointing me to the xorg.conf. (your help worked out
great :)
** Description changed:
Binary package hint: xorg
There is reproducable corruption of the screen when using a Sapphire
- Radeon 4770 card with the open source radeon drivers.
+ Radeon 4770 card with the open
Hmm, seems like adduser wants to ensure UID == UPG-GID?
Maybe g-s-t could offer to choose the next possible ID available, or
optionally override the GID and possibly mess up the system?
--
users-admin should leave adduser handle main group creation
https://bugs.launchpad.net/bugs/488158
You
Thank you for the hints Peter. Which vnc packages did you install?
So regading the fix for running apps as different user, it should
probably make use of xnest or Xephyr?
--
wrong ownership of .Xauthority and /tmp/libgksu-xxx
https://bugs.launchpad.net/bugs/275304
You received this bug
** Summary changed:
- error: Running 'grub-install --no-floppy /dev/md0' failed.
+ 'grub-install --no-floppy /dev/md0' fails
--
'grub-install --no-floppy /dev/md0' fails
https://bugs.launchpad.net/bugs/462171
You received this bug notification because you are a member of Ubuntu
Bugs, which
There is again the same error message in 9.10 when installing grub to md
device. - Bug #462171
--
error: Running 'grub-install --no-floppy /dev/md0' failed.
https://bugs.launchpad.net/bugs/457687
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Confirming:
# grub-install /dev/md1
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR.
This is a BAD idea.
grub-setup: error: Embedding is not possible, but this is required when the
root device is on a RAID array or LVM volume.
# cat /proc/mdstat
Personalities
# fdisk -l /dev/sda
Platte /dev/sda: 82.3 GByte, 82348277760 Byte
255 Köpfe, 63 Sektoren/Spuren, 10011 Zylinder
Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes
Disk identifier: 0x0009d720
Gerät boot. AnfangEnde Blöcke Id System
/dev/sda1 2 24
** Description changed:
Binary package hint: xorg
- There is occasional corruption of the screen when using a Sapphire
- Radeon 4770 card with the open source radeon drivers. The takes the form
- of a chequered effect, looking a bit like a chequer board. This is
- most noticeable when the
Logging into kde the errors are all over the place.
--
Occasional screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Summary changed:
- Occasional screen corruption with Radeon 4770
+ screen corruption with Radeon 4770
--
screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Looks like they had the same prob, but I don't understand their solutions:
http://www.phoronix.com/forums/showthread.php?t=18687
--
screen corruption with Radeon 4770
https://bugs.launchpad.net/bugs/440544
You received this bug notification because you are a member of Ubuntu
Bugs, which is
crased on me in 9.10
** Changed in: fast-user-switch-applet (Ubuntu)
Status: Incomplete = Confirmed
--
fast-user-switch-applet crashes system on usage
https://bugs.launchpad.net/bugs/352056
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This is confirmed many times by now.
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** This bug is no longer a duplicate of bug 408432
[i915] 'xrandr' with no arguments garbles screen
--
intel graphics laptop crashes with external monitor
https://bugs.launchpad.net/bugs/465318
*** This bug is a duplicate of bug 489474 ***
https://bugs.launchpad.net/bugs/489474
Thank you. All good with that LucidBootRecovery spec.
--
mountall can not be unblocked
https://bugs.launchpad.net/bugs/498636
You received this bug notification because you are a member of Ubuntu
Bugs,
As mountall already has the waiting for device functionality,
linking this to https://wiki.ubuntu.com/ReliableRaid that was updated
with email discussion and made to match a SpecTemplate.
** Changed in: mountall (Ubuntu)
Status: Invalid = New
--
mounts fail because degraded raid is not
Could someone give me a hint how/what I have to do, in order to install
aqbanking from lucid (version 4.1.8) in 9.10?
The package search turns out many .debs.
--
Online-Actions not working in GnuCash
https://bugs.launchpad.net/bugs/453895
You received this bug notification because you are a
Ok, thought of checking it in somewhere.
-blueprints?
--
mounts fail because degraded raid is not beeing started
https://bugs.launchpad.net/bugs/496461
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
dowload and dpkg -i * of aqbanking-tools plus 5x libaqbanking and 1x
libaqhbci seem to do it.
--
Online-Actions not working in GnuCash
https://bugs.launchpad.net/bugs/453895
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
* If /boot files are copied to rescue partition manually, the UUID in
the search lines in grub.cfg will not match the UUID of the rescue
partition. A --grub-root-directory option for grub-mkconfig would fix
this.
* grubenv seems to get written to (root)/grub while it is installed in
Architecture: i386
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: cisco_ipsec
Package: linux-image-2.6.31-16-generic 2.6.31-16.53
PackageArchitecture: i386
ProcEnviron:
SHELL=/bin/bash
LANG=de_DE.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
Uname: Linux 2.6.31-16-generic i686
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/36968589/Dependencies.txt
--
rejected 1 configuration due to insufficient available bus power
https://bugs.launchpad.net/bugs/203473
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: XsessionErrors.txt
http://launchpadlibrarian.net/36968590/XsessionErrors.txt
** Changed in: linux (Ubuntu)
Status: Incomplete = New
** Tags added: apport-collected
--
rejected 1 configuration due to insufficient available bus power
I am not sure if devicekit is right.
If not please change to the package that provides the device detection
UI.
** Also affects: devicekit (Ubuntu)
Importance: Undecided
Status: New
--
rejected 1 configuration due to insufficient available bus power
with 9.10
Same Hub here:
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
lsusb shows the flash drive (after a while), but nothing more happens.
/var/log/messages however says:
usb 1-2.3: rejected 1 configuration due to insufficient available bus power
--
usb device
Public bug reported:
Binary package hint: grub2
9.10
The following example used to work with grub1 to create separate rescue
boot media:
* Plugged in the USB Stick which contains a dedicated grup partition and
chainloads other (rescue) boot partitions for several installations that are on
I did actually copy to /media/label/boot/
(But I have tried it as written above with same result.)
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
One error I noticed now:
grub-mkconfig is always writing to /boot/grub/device.map not honoring
the path given with for grub.cfg with -o
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of
Hi, thanks for that quick response. Is there any workaround for Cannot read
`/grub/core.img'?
normally). - Grub2 needed grub-install /dev/sda5 to work again.
Should never happen if both the directory given with --root-directory is
the drive/partition you want and also the device you give
grub-mkconfig always uses /boot.
It doestn't have at all any support for something like --root-directory=
of grub-install.
Hm, I took the option -o, --output=FILE output generated config to
FILE for it.
Also all /etc/grub.d/* files only look in /boot/ for the kernels etc.
That might not
Ah, right, I probably just don't need to grub-mkconfig at all if /boot
is copied.
--
failures on grub-install to create rescue boot media
https://bugs.launchpad.net/bugs/498533
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
you can use grub-install with --grub-setup=/bin/true
Thanks for this, and your help!
Way cleaner than copying to the rescue partition, over-mounting it to /boot and
than doing update-grub/grub-install.
--
failures on grub-install to create rescue boot media
Public bug reported:
9.10 ubuntu desktop CD iso put on usb stick (live-usb) and booted:
Update using synaptic failed and got reported by apport.
ProblemType: Package
Architecture: i386
ArecordDevices:
List of CAPTURE Hardware Devices
card 0: SB [HDA ATI SB], device 0: ALC883 Analog
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/36978175/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/36978176/AplayDevices.txt
** Attachment added: AptOrdering.txt
http://launchpadlibrarian.net/36978177/AptOrdering.txt
**
--grub-setup=/bin/true worked nice! Nailed it down to two issues now.
1)
When I used grub-mkconfig (at that time with -o
/media/label/boot/grub/grub.cfg but shouldn't matter) it did create a faulty
grub.cfg however. It probably looked in /boot/grub for the device.map (as it
does not support
Public bug reported:
Binary package hint: mountall
When booting from a rescue boot device, mountall prevented a successful
boot.
It was waiting for the UUID of the (potentially destroyed) /boot
partition. (different form the boot media used)
While ESC did get me a shell, I could not disable
Public bug reported:
Binary package hint: mountall
separate bug originally posted as comment
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/456274/comments/34
by Andreas Lieser on 2009-12-06:
I did a fresh Karmic install 2 weeks ago, too, and I still got this bug.
I have two
Public bug reported:
Binary package hint: mountall
reporting as another bug as summuarized by
Steve Langasek in
https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/456274/comments/39
on the second prompt (for /home) ... it should be reported as a
separate bug
it's ... known that
Thanks for sorting it out.
The issue Andreas Lieser an I commented on can't enter a password for
my encrypted home directory is now Bug #497682
and mountall and cryptsetup will fight for the console when not using
usplash is now Bug #497684
--
mountall 0.2.5 and cryptsetup fail to boot when
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
--
mountall and cryptsetup will fight for the console when not using usplash
** Also affects: cryptsetup (Ubuntu)
Importance: Undecided
Status: New
** Changed in: cryptsetup (Ubuntu)
Status: New = Confirmed
** Changed in: mountall (Ubuntu)
Status: New = Confirmed
--
can't enter a password for my encrypted home directory
Now the only thing left for laptop-mode-tools:
* remove the lines sourcing /etc/default/acpi-support (search the
package source)
--
remove laptop-mode settings from /etc/default/acpi-support
https://bugs.launchpad.net/bugs/244838
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 497738 ***
https://bugs.launchpad.net/bugs/497738
** This bug has been marked a duplicate of bug 497738
error in platform restricted installation of config files
--
/etc/power/ directory and files (used on powerpc) get installed on all platforms
Public bug reported:
Binary package hint: laptop-mode-tools
Instead of installing the /etc/power files only on the powerpc platform,
/etc/default/laptop-mode gets only installed on the powerpc.
Consequently laptop-mode-tools is in many cases installed without its
config file.
/etc/power/
701 - 800 of 1115 matches
Mail list logo
