Nice to see that at last some sanity finally got in. I am a bit late
here, but I have another suggestion below. Skip to the end to avoid the
rant.
Context: FYI, yesterday I had to patch (live) the bootblock of a Debian
squeeze system that stopped to boot a few updates ago. It was a pain
There is no way to resolve such conflicts automatically.
In some cases (such as the case above), there is.
We would risk serious data loss.
The very worst that could eventually happen here is that the swap is
mounted unencrypted. The only possible data loss is that LUKS key slots
would be
Sorry, nothing to prove here. You totally miss the point. Fix your
broken metadata.
That's already done, mind you.
Now PROVE that my suggestion to expose the LUKS UUID could actually
cause bad things. Go.
--
udev fails to identify crypt_LUKS swap partition by uuid
You self-identified an apparent defect in a particular software package,
when in fact that package was working normally and as designed.
Fact: it worked before jaunty, with jaunty it's broken.
It's often better to *not* jump directly to the source as you did; had
you filed a more generic
Public bug reported:
Binary package hint: udev
Description:Ubuntu 9.04
Release:9.04
udev:
Installed: 141-1
Symptoms:
My laptop fails to boot since I upgraded from Intrepid to Jaunty. Before
Jaunty, the system asked for cryptsetup luks passphrases twice, a first time
for the root
** Attachment added: result of udevadm --export-db
http://launchpadlibrarian.net/25532310/udevadm_db
--
udev fails to identify crypt_LUKS swap partition by uuid
https://bugs.launchpad.net/bugs/362315
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hey, this was setup using the standard ubuntu tools some releases ago.
It used to work until Jaunty. Now it doesn't work. THAT'S A DEFECT
period. Reopening. Someone influent told in some report of some other
package that libvolid folks are not willing to fix bugs, it looks like
this is true
By the way, about multiple metadata is not supported, there are already
multiple links for the same block device in /dev/disk/by-id, e.g.
ata-HTS721060G9AT00_MPC3B2Y3GK0S3E-part1 - sda1
scsi-SATA_HTS721060G9AT00_MPC3B2Y3GK0S3E-part1 - sda1
Why not just do that in /dev/disk/by-uuid when you are
Reopening again. Please don't make bugs as invalid without first making
sure that you understand the problem, and that the bug report is
actually invalid. Because in this case it is not. Thanks.
Yes, devmapper exposes the unencrypted partition ... once the partition
is unlocked. At boot time it
Won't fix is less bad than plain invalid but still not appropriate
IMO. This is the cow-boy way of fixing problems: shoot them first, if
they survive shoot them again, then eventally think about them.
With your packages:
$ sudo ./blkid -p /dev/sda3
/dev/sda3:
A better way to remove a stale swap signature than zeroing the whole thing:
dd if=/dev/zero of=/dev/sdXXX bs=1024 seek=1 count=3
--
udev fails to identify crypt_LUKS swap partition by uuid
https://bugs.launchpad.net/bugs/362315
You received this bug notification because you are a member of
Marking as invalid in e2fsprogs. As written above, it is a problem in
init scripts and/or udev.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Invalid
--
fsck dies on boot with USB drives
https://bugs.launchpad.net/bugs/276045
You received this bug notification because you are a member
Marking as confirmed in Ubuntu:
- implement or remove the write option -w (upstream)
- fix issue with MD devices (upstream)
** Changed in: e2fsprogs (Ubuntu)
Status: New = Confirmed
--
Wrong type in blkid cache causes fsck on boot to fail
https://bugs.launchpad.net/bugs/316322
You
Marking as invalid (won't fix).
First, this is not a problem concerning e2fsprogs. Should have been
filed in ntp, sysv-rc or util-linux. Please also file issues with
your local politicians, because actually the best way to fix this would
be to stop that twice-a-year-time-change insanity,
Marking invalid. Not related to e2fsprogs.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Invalid
--
libqt4-dev fails to install in Intrepid due to dependency problems (libaa1-dev,
comerr-dev)
https://bugs.launchpad.net/bugs/318539
You received this bug notification because you are a
Marking invalid. The disk check is finished when you get your problem;
could be a hardware, configuration or X driver issue.
If you still have the problem please check if ctrl-alt-delete or ctrl-
alt-backspace can restart the X server. If you can, also check if your
machine responds to ping. If
Fix released in 1.41.4-1ubuntu1.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Fix Released
--
bug in tune2fs/e2label
https://bugs.launchpad.net/bugs/319262
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
Marking invalid. Not a problem with e2fsprogs.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Invalid
--
package comerr-dev 2.1-1.41.3-1ubuntu1 failed to install/upgrade: subprocess
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/330049
You
Marking as incomplete. The attached VarLog...gz is empty.
Do you still have the problem with 141-1? If so can you please provide
the actual error message? Thanks.
** Changed in: udev (Ubuntu)
Status: New = Incomplete
--
package udev 139-1 failed to install/upgrade: (Jaunty)
fidel,
ldap-auth-config exists and is even installed on your system.
Please follow the instructions at:
https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html#openldap-auth-config
that is, run:
sudo dpkg-reconfigure ldap-auth-config
not just:
sudo ldap-auth-config
Thanks.
Marking as
This has nothing to do with libuuid specifically.
There is a UID_MIN parameter in /etc/login.defs. Login applications
could use that parameter to find out automatically which accounts are
system accounts.
If some reason cause the actual system/user UID threshold on your setup
to be another value
Marking as invalid. Configuration / system administration issue.
** Changed in: ubiquity (Ubuntu)
Status: New = Invalid
--
libuuid user created with uid 500
https://bugs.launchpad.net/bugs/207040
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hesitated between Invalid (can't reproduce) and Fixed. There was
certainly a real problem here (probably belonging to libuuid rather than
subversion), but I could not find in which release it was fixed. Anyway
it's gone.
** Changed in: subversion (Ubuntu)
Status: New = Fix Released
--
Marking the bug as incomplete.
unetbootin is packed with UPX, this is why it appears as a static
binary. Before trying ldd and objdump -x it should be first expanded
with ucl -d (from the package upx-ucl).
After some fighting with upx to make it compile with lzma, I found that there
is no
Marking as invalid in compiz:
- see #237209 in wine for the desktop effects / wine issue
- follow this bug in xserver-xorg-video-ati for the probable driver issue
** Changed in: compiz (Ubuntu)
Status: New = Invalid
--
wine screen updates faulty in Jaunty
fidel,
ldap-auth-config exists and is even installed on your system.
Please follow the instructions at:
https://help.ubuntu.com/8.10/serverguide/C/openldap-server.html#openldap-auth-config
that is, run:
sudo dpkg-reconfigure ldap-auth-config
not just:
sudo ldap-auth-config
Thanks.
Marking as
It looks like a stack / memory corruption problem. The place where the
program finally crashes is probably not the place where the problem is.
Maybe (probably) related to that specific codec (that looks
proprietary).
Marking as incomplete. Please tell us if:
- the problem does not happen anymore
You have a point somewhere. But unfortunately there is no good way for
libuuid to get a list of opened FDs and close them all except its own
sockets when launching uuidd.
What you should do instead: create your own sockets with O_CLOEXEC (or
use fcntl F_SETFD to set that flag on your open
Marking as incomplete. Please send the actual output of blkid and
contents of /etc/fstab. Thanks.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Incomplete
--
filesystem check fails on boot, but filesystem isn't bad
https://bugs.launchpad.net/bugs/48563
You received this bug
Fix released in 1.41.2-1ubuntu1.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Fix Released
--
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 subscribed to Ubuntu.
--
Mount count: 4
Next check after: Tue Jan 8 16:52:30 2008
So yes, the history is actually updated. Marking invalid.
As you suggested, your problem may be time initialization on your
system. It's probably better for you to completely disable checking
intervals using tune2fs, and then remember to
Changing status to confirmed; apparently everyone agrees that something
should be done.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Confirmed
--
tools should use libvolume-id instead of libblkid
https://bugs.launchpad.net/bugs/235165
You received this bug notification because you
Fix released in 1.41.2-1ubuntu1.
** Changed in: e2fsprogs (Ubuntu)
Status: In Progress = Fix Released
--
e2fsck outputs translation header to terminal
https://bugs.launchpad.net/bugs/246892
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Looks like a hardware problem to me too.
You could try to isolate one of the servers that has the problem fairly
often, make it run on just one disk for some time (e.g. off office
hours, after the backup). Power off, remove a disk, power on and run
fsck, reboot, simulate some load for some,
Fix released in 1.41.2-1ubuntu1.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Fix Released
--
blkid library detects JFS partition as FAT32
https://bugs.launchpad.net/bugs/255255
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Marking incomplete; waiting for details with valgrind.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Incomplete
--
e2fsck crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/257048
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Marking as incomplete; waiting for either results of test with sparse
image or bzip2 archive of sparse image.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Incomplete
--
e2fsck keeps reporting new block bitmap differences and illegal blocks after
re-run
Fix released in 1.41.4-1ubuntu1.
** Changed in: e2fsprogs (Ubuntu)
Status: New = Fix Released
--
tune2fs -I 256 extremly slow
https://bugs.launchpad.net/bugs/298343
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
** Summary changed:
- Please sync openswan 1:2.6.20+dfsg-3 (universe) from Debian unstable (main)
+ Please sync openswan 1:2.6.20+dfsg-4 (universe) from Debian unstable (main)
--
Please sync openswan 1:2.6.20+dfsg-4 (universe) from Debian unstable (main)
https://bugs.launchpad.net/bugs/334596
The new version is already available in Debian unstable:
http://packages.debian.org/sid/openswan
1:2.6.20+dfsg-1
--
update to upstream release 2.6.20
https://bugs.launchpad.net/bugs/334596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I got a reply on 2009-02-28 from Rene Mayrhofer (package maintainer for Debian):
Updated my own subversion tree using svn-buildpackage and fixed a few
errors/warnings. Testing now and will upload rather soon to unstable.
--
update to upstream release 2.6.20
YoBoY:
What I have submitted is not just an idea to improve Ubuntu. It solves actual
bugs and problems. I could as well have written Openswan 2.4.x is bugged and
outdated in the title.
Daniel:
It is probably better to wait past alpha 5 release to push this. This is the
kind of package that
Public bug reported:
Binary package hint: openswan
The newest openswan 2.6.X releases fix several important bugs that
caused a lof of trouble when establishing tunnels.
Attached is a source package that seems to work for our needs, but a
careful review is certainly a good idea.
** Affects:
** Attachment added: source package 1 of 4
http://launchpadlibrarian.net/23132078/openswan_2.6.20%2Bdfsg.orig.tar.gz
--
update to upstream release 2.6.20
https://bugs.launchpad.net/bugs/334596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: source package 2 of 4
http://launchpadlibrarian.net/23132114/openswan_2.6.20%2Bdfsg-1.diff.gz
--
update to upstream release 2.6.20
https://bugs.launchpad.net/bugs/334596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: source package 3 of 4
http://launchpadlibrarian.net/23132117/openswan_2.6.20%2Bdfsg-1.dsc
--
update to upstream release 2.6.20
https://bugs.launchpad.net/bugs/334596
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: source package 4 of 4
http://launchpadlibrarian.net/23132121/openswan_2.6.20%2Bdfsg-1_source.changes
--
update to upstream release 2.6.20
https://bugs.launchpad.net/bugs/334596
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Bug fixed (patch accepted) upstream.
--
USB touchscreen is disabled when switching virtual console back to X
https://bugs.launchpad.net/bugs/322946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Public bug reported:
Binary package hint: xserver-xorg-input-evdev
Also reported upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=19819
Problem located in evdev.c / EvdevCacheCompare()
Symptom: USB touchscreen no longer works when switching from X to another
virtual console and then back
** Attachment added: patch evdev.c
http://launchpadlibrarian.net/21785946/patch
--
USB touchscreen is disabled when switching virtual console back to X
https://bugs.launchpad.net/bugs/322946
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
50 matches
Mail list logo
