[Bug 322946] [NEW] USB touchscreen is disabled when switching virtual console back to X
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 to X. Sample log message: (EE) Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface: Device has changed - disabling. (WW) Elo TouchSystems, Inc. Elo TouchSystems 2700 IntelliTouch(r) USB Touchmonitor Interface: Release failed (Invalid argument) Cause: EvdevCacheCompare fails because it also compares all values of input_absinfo structure, which include the last tapped position of the touchscreen (.value field). This is never updated in the cache, and anyway it could change anytime if the screen is touched while away from the X virtual console. Solution: Exclude .value from comparison. One-liner patch attached. ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322946] Re: USB touchscreen is disabled when switching virtual console back to X
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
> 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 overwritten. That is, if the partition is exposed as "swap". But that's not what I suggest. I suggest that when there is a valid LUKS header, the partition is always exposed as LUKS. There is no possible data loss here: if there is no valid key, the partition cannot be used at all. > Be happy, that the system did not recognize one of your data partitions as swap and corrupted it. It's not a data partition that has a swap signature, it's an actual swap partition (but encrypted with LUKS), with type 0x83 "swap". And it worked that way for about two years (the UUID that was exposed in /dev/disks/by-uuid was the one of the swap header, not the LUKS header). And nothing bad happened, until Jaunty, where I could not boot at all. Proven fact: your position, on this particular issue, breaks things. Still not proven: my suggestion would break things. To do: - prove that my suggestion to expose the LUKS UUID could actually cause bad things OR - recognize that this is an acceptable way to deal with that particular issue (way better IMO than to actually write things on block devices without knowing too well if you should do that, think of the users). -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
> 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 https://bugs.launchpad.net/bugs/362315 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] [NEW] update to upstream release 2.6.20
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: openswan (Ubuntu) Importance: Undecided Status: New -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
** 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 Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: 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 requires some length of time for reviewing, testing and adjusting. I submitted the package to the Debian maintainers via e-mail, I did not file a bug there yet. I am waiting for their feedback. -- 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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 322946] Re: USB touchscreen is disabled when switching virtual console back to X
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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
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 https://bugs.launchpad.net/bugs/334596 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: update to upstream release 2.6.20
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 334596] Re: Please sync openswan 1:2.6.20+dfsg-4 (universe) from Debian unstable (main)
** 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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207040] Re: libuuid user created with uid >500
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 (such as 500), please correct your /etc/login.defs as the UID_MIN value is used to create new users. Automatically created system users should then be below the threshold. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 207040] Re: libuuid user created with uid >500
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 258973] Re: subversion link problem with libuuid.so.1
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 -- subversion link problem with libuuid.so.1 https://bugs.launchpad.net/bugs/258973 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 306101] Re: libuuid version number
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 direct dependency on libuuid. unetbootin depends on libSM (/usr/lib/libSM.so.6) which depends on /lib/libuuid.so.1. By the way unetbooting is a 32 bit binary, and there is no separate file for 32 and 64 bits versions of libuuid in arch amd64: (result of objdump -x) libuuid.so.1.2: file format elf64-x86-64 architecture: i386:x86-64, flags 0x0150: You system would probably be mostly unusable if libSM did not work at all. Please tell us if you still have the problem. Thanks. ** Changed in: e2fsprogs (Ubuntu) Status: New => Incomplete -- libuuid version number https://bugs.launchpad.net/bugs/306101 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 314205] Re: wine screen updates faulty in Jaunty
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 https://bugs.launchpad.net/bugs/314205 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 333460] Re: [Hardy][LDAP]client authentication broken
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 incomplete. ** Changed in: libpam-ldap (Ubuntu) Status: New => Incomplete -- [Hardy][LDAP]client authentication broken https://bugs.launchpad.net/bugs/333460 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 324658] Re: totem-xine-video-thumbnailer crashed with SIGSEGV in xine_list_get_value()
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 - it happens with a different file format than RAX - you can find a pattern and a file that reproduce the problem fairly often. Thanks. ** Changed in: xine-lib (Ubuntu) Status: New => Incomplete -- totem-xine-video-thumbnailer crashed with SIGSEGV in xine_list_get_value() https://bugs.launchpad.net/bugs/324658 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 305057] Re: uuidd does not close sockets on launch
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 descriptors). Available since linux 2.6.23; see open(2) man page for details. Your sockets will then be closed automatically in the child process when it will execute uuidd. Marking invalid "wontfix". ** Changed in: e2fsprogs (Ubuntu) Status: New => Invalid -- uuidd does not close sockets on launch https://bugs.launchpad.net/bugs/305057 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 48563] Re: filesystem check fails on boot, but filesystem isn't bad
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 notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99292] Re: fsck tries to check the wrong mapped fs
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 125106] Re: fsck not updating clean history
> 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 check once in a while. ** Changed in: e2fsprogs (Ubuntu) Status: New => Invalid -- fsck not updating clean history https://bugs.launchpad.net/bugs/125106 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 235165] Re: tools should use libvolume-id instead of libblkid
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 246892] Re: e2fsck outputs translation header to terminal
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 to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 247318] Re: Dapper lvm over software raid kills ext3
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, reboot, fsck, check if there are problems. Yes? not related to raid. Power off, Re-add the disk you removed to the raid. Power on, boot knoppix, wait for your disk to be in sync (hours). Fsck. Problems that were not there just before power-off => probably bad hardware. Then reboot, simulate some load, fsck again. No problem now? Your raid was out of sync. This is not an e2fsprogs problem though. Either hardware, kernel or both. Waiting for more info to redispatch. ** Changed in: e2fsprogs (Ubuntu) Status: New => Incomplete -- Dapper lvm over software raid kills ext3 https://bugs.launchpad.net/bugs/247318 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 255255] Re: blkid library detects JFS partition as FAT32
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. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 257048] Re: e2fsck crashed with SIGSEGV in strlen()
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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 270231] Re: e2fsck keeps reporting new block bitmap differences and illegal blocks after re-run
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 https://bugs.launchpad.net/bugs/270231 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 298343] Re: "tune2fs -I 256" extremly slow
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276045] Re: fsck dies on boot with USB drives
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 of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 316322] Re: Wrong type in blkid cache causes fsck on boot to fail
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 107098] Re: Superblock Last write time was in the future
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, seriously. It is not possible to run ntpdate before fsck, because networking can only be enabled after fsck. I am not redirecting the bug because there is no good way to fix your issue. If you were not running XP you would set your CMOS clock to UTC, problem solved. But if your CMOS is set to local time, including temporary political time shifts, there is no flag in CMOS telling the system that time correction has been applied (or telling in which time zone the CMOS clock is). Maybe hwclock could try to implement some clever, optional and not-enabled-by-default-unless-you-dual-boot-windows heuristics to guess whether the time should be considered summer or winter (and then there is one hour in the year where you just can't know), but it is not worth the extra complexity and problems in my opinion. ** Changed in: e2fsprogs (Ubuntu) Status: New => Invalid -- Superblock Last write time was in the future https://bugs.launchpad.net/bugs/107098 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318539] Re: libqt4-dev fails to install in Intrepid due to dependency problems (libaa1-dev, comerr-dev)
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 member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 318069] Re: Ubuntu hangs after routine disk check
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 not, reboot on a CD, mount your root partition, check /var/log/kern.log and /var/log/Xorg.0.log, then file a bug in the appropriate package (maybe xserver-xorg-video-ati or linux kernel). Thanks. ** Changed in: e2fsprogs (Ubuntu) Status: New => Invalid -- Ubuntu hangs after routine disk check https://bugs.launchpad.net/bugs/318069 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 319262] Re: bug in tune2fs/e2label
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 330049] Re: package comerr-dev 2.1-1.41.3-1ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
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 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 335738] Re: package udev 139-1 failed to install/upgrade: (Jaunty)
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) https://bugs.launchpad.net/bugs/335738 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] [NEW] udev fails to identify crypt_LUKS swap partition by uuid
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 partition (sda3 on my system) and a second time for the swap partion (sda4). Since Jaunty it asks for the root cryptsetup passphrase, unlocks the slot, waits a long time then drops to a shell, saying that the device /dev/disks/by-uuid/ (id of sda4 partition) was not found. I have to manually create the link in /dev/disks/by-uuid every time for the system to boot. What's actually wrong: running udevadm info --export-db do not report any uuid for sda4, while sda3 is correct. See attached file. More wrongness: # vol_id /dev/sda4 unknown or non-unique volume type (--probe-all lists possibly conflicting types) # vol_id --probe-all /dev/sda4 swap crypto_LUKS ## I could not find a way to make vol_id spit out the uuid of the luks header of the partition. For information, blkid has a different kind of wrongness. Out of the box it will report a wrong uuid (that is, the uuid that was used in intrepid and before), probably because it parses the luks data as swap area. But then it is possible to edit /etc/blkid.tab and say that sda4 is of type crypt_LUKS, then blkid will find the right UUID and remember it. ** Affects: udev (Ubuntu) Importance: Undecided Status: New -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
** 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
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 unfortunately. There is no multiple medatadata on this block device, it's supposed to be only LUKS. If tools detect another metadata that's a bug. And "multiple metadata is not supported" does not make this bug invalid. It makes the design choice not to support multiple metadata invalid. Change that. Thanks. ** Changed in: udev (Ubuntu) Status: Invalid => New -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
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 not sure about the type and UUID of a block device? -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
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 is not unlocked. In order to unlock it, the init scripts wait for sda4 (that is, a LUKS block device) to appear with a UUID in /dev/disks/by-uuid. This happened in the past (with a wrong UUID, but at least it appeared to work), and does not happen anymore. It is not possible to use the UUID of the unencrypted device before it is unencrypted. Init scripts need the UUID of the LUKS device in order to unlock it. Also note that this already correctly works for sda3, which is the root device. It fails for sda4, which is the swap/hibernate partition. ** Changed in: udev (Ubuntu) Status: Invalid => Confirmed -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
"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: UUID="4d3ba41a-1fb4-474b-a59e-4285e4768bdd" VERSION="256" TYPE="crypto_LUKS" USAGE="crypto" $ sudo ./blkid -p /dev/sda4 /dev/sda4: ambivalent result (probably more filesystems on the device) Correct detection should stop as soon as a LUKS header is detected, and report the LUKS UUID. Why? Because if this was an actual swap partition, the LUKS header would have been deleted by mkswap (see zap_bootbits). What's actually on /dev/sda4: 4c 55 4b 53 ba be 00 01 61 65 73 00 00 00 00 00 |LUKSaes.| (...) 0400 01 00 00 00 25 72 07 00 00 00 00 00 e6 78 04 bd |%r...x..| (...) 0ff0 00 00 00 00 00 00 53 57 41 50 53 50 41 43 45 32 |..SWAPSPACE2| So yes there is a stale swap signature, probably coming from a previous distro before I switched to ubuntu. As far as I know it's not cryptsetup's job to erase what's there. It is recommanded to fill the disk with random bits before running cryptsetup; the ubuntu tool at that time did not do this (nor did they erase the swap signature). If you leave this as "Won't fix", it actually means that migrating from previous Ubuntu releases with encrypted swap partitions is not supported. Also probably means that installing Ubuntu Jaunty with a LUKS swap over over existing partitions is not supported, and going to fail. Please document this in release notes. Thanks. Nevertheless, not reporting any UUID is the worst possible behaviour and break things, as demonstrated. What is so hard about marking this bug as "confirmed" so 1. others have a better chance to know about it, and 2. it gets a better chance to be fixed someday? -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: udev fails to identify crypt_LUKS swap partition by uuid
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 Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 362315] Re: 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 bug, our QA team would have been able to triage > it far more effectively and identify the real problem. You are just denying what the real problem is. > Right, so blkid behaves the same. THIS version of blkid behaves the same broken way as vol_id. Previous versions of blkid reported a UUID. > For every person that authoratively asserts, as you just did, that X is > always preferred over Y - I can find you somebody who asserts the exact > opposite. Yeah, I've read that one before. The perfect excuse for never fixing anything. BULLSHIT. I _demonstrated_ that if you have both a LUKS header and a swap header on a partition, it means that cryptsetup was run after mkswap. So that partition is _supposed_ to be a LUKS partition. An in fact it is way more likely to be a LUKS partition than a swap partition. If it were a swap partition with a stale LUKS signature it would mean that the owner of the system took unusual steps (e.g. running cryptsetup, reverting to regular swap but not running mkswap again). Now find me someone that will assert and demonstrate the reverse. > The better solution is to ensure that there is never a case of > conflicting meta-data on a block device. That's correct, but that's another problem. Yes you can use migration scripts to remove the stale signature. It's going to be more complicated to implement and test than just FIXING udev to report ANY UUID (as blkid used to do before). > Because it isn't a bug. Yes it is. > The software is working exactly as designed. Probably not. Even then, if there is a design goal that states "when there are two possible UUID do not report ANY" that design goal is plain wrong and must go. > If you'd like to complain about the design of the software, upstream is > a far better place to do that - we're just a distro. I am going to do that too. But in the interim, or if upstream fails to understand that, that can, and should, be patched at the distro level. --- Now some words about the way YOU, Mr. Scott James Remnant, handled the issue: - failed to realize that this is a migration problem that is going to impact actual users - marked bug as "invalid" two times before thinking about it, suggesting an alternative (cryptsetup), and marked as "won't fix" even before evaluating the effort in the alternative vs. the effort in udev - still fails to realize that the easiest short-term solution for the distro is to fix udev. And this is how a sensible bug supervisor (like most supervisors actually are) would have done it: - ask for details (mark bug "new", "incomplete" or "triaged") ; are there actually two signatures on the partition? how did that happen? - add "cryptsetup" to the bug so they can think about erasing some known signatures (esp. swap) when initalizing a LUKS partition - mark the bug as "confirmed" because not reporting any UUID in this case is just nonsense. - eventually report the problem upstream (or ask the reporter do do so), and wait for upstream reaction before taking a decision (implement upstream fix, won't fix, patch in distro). Think about it. And please improve your own way of dealing with bugs. Thanks. -- 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 subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 428435] Re: luks encrypted partition not detected
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 diagnosing that one, because it was installed "cleanly" from scratch (I thought), and blkid on the live system reported both partitions: /dev/hda1 root ext3, and /dev/hda5 swap. In the initramfs, only swap was detected. Side note: usually on a PC I like my MBR being a regular PC MBR (or debian's enhanced MBR that allows you to choose the partition), and my GRUB being on the boot block of the "boot" (if any) or "root" partition. Telling users that GRUB should be on the MBR is, IMHO, asking for trouble. But for the system above I decided to go by the book and just follow what the install CD told me to do next, next, next. Context again: Finding what was wrong was a pain. First, I had to figure out that blkid used a cache, which explained why the root partition was shown on the live system but not at boot time. Using "-c /dev/null" the same problem was visible on the live system. Deleted the cache, hacked grub.conf, lazily waited a few weeks for the fix to come (or not) because my last experience of sending blkid bug reports left me with the impression that the only sane thing to do would be to fork the package and took it off the hands of its current maintainers. Context continued: Somehow the ext3 partition managed to get back in blkid's cache over these weeks. Thought it was solved, tried "-c /dev/null", nope, deleted cache, nope. Then finally decided to take a few hours solving that "perfectly-legit-installed-by-the-book-no-longed- detected-ext3-partition" mystery. Played around with blkid options but could not get anything useful of it, excepted that "probably more filesystems" message (option -p) that did not tell which other signatures it found. Downloaded source, activated all debug flags in libblkid, tried again. Could finally see that libblkid detected a vfat and an ext3 signature. vfat?!? Then FINALLY I checked hda1's boot block, and found out that nothing erased the vfat boot block when I installed the Debian system on it, following the regular procedure. That old box used to have a W2K system on it... Of course, there are failures on multiple levels here, just like in this bug report. Now the suggestion for blkid: Implement an option (e.g. -a for "all") that will use blkid_do_probe and a loop instead of blkid_do_safeprobe, and report all detected signatures. I guess that it should make everybody happy, because scripts can now try the "safe" (aka your system is so safe it won't boot anymore) version first, then -a, then handle special cases at script level or issue warning or error messages as needed. But the system will boot. Alternative: a second run of blkid_do_probe in the error message of lowprobe_device so the poor user can get an idea of which signatures are confusing blkid. -- luks encrypted partition not detected https://bugs.launchpad.net/bugs/428435 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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
