Re: [arch-general] Warning: dbmail is broken
At Tue, 13 Oct 2009 13:49:06 +0800, Ng Oon-Ee wrote: On Tue, 2009-10-13 at 09:17 +0400, Sergej Pupykin wrote: It is not problem. I do not think that someone have installed dbmail and gnome on the same computer. Please don't top-post. What you're suggesting WILL affect all gnome users, even if they don't have dbmail installed. Simple stop-gap is for dbmail's depends to be on that particular version of gmime. Or put that version in community. Why all? I do not suggest to downgrade gmime in repos. I just warn users who use dbmail to prevent upgrading of gmime package. I work on dbmail and I think it will be done soon.
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
i am beginning to think there really is a problem. i have a luks encrypted partition that i automatically mount at boot via /etc/crypttab with a *keyfile* so this has never failed and it can't fail except if the keyfile is damaged. and today the luks partition failed to be opened for the *first* time *ever* by cryptsetup because of a password problem. once i rebooted it worked. so the keyfile is not wrong. and i double check it with my backup keyfile this looks like your problem Hussam. it sometimes fails sometimes works.
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
solsTiCe d'Hiver schrieb: i am beginning to think there really is a problem. i have a luks encrypted partition that i automatically mount at boot via /etc/crypttab with a *keyfile* so this has never failed and it can't fail except if the keyfile is damaged. and today the luks partition failed to be opened for the *first* time *ever* by cryptsetup because of a password problem. once i rebooted it worked. so the keyfile is not wrong. and i double check it with my backup keyfile this looks like your problem Hussam. it sometimes fails sometimes works. When did any of you guys upgrade to cryptsetup 1.0.7? Can you grep this from pacman.log please? signature.asc Description: OpenPGP digital signature
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
solsTiCe d'Hiver schrieb: it has been sometime ago # grep cryptsetup /var/log/pacman.log [2008-07-16 11:03] upgraded cryptsetup (1.0.6-1 - 1.0.6-1) [2008-10-08 14:29] upgraded cryptsetup (1.0.6-1 - 1.0.6-2) [2009-06-19 21:52] upgraded cryptsetup (1.0.6-2 - 1.0.6-3) [2009-08-10 14:52] upgraded cryptsetup (1.0.6-3 - 1.0.7-1) So that's not it. 1.0.7 should be working better anyway. Sadly, a viable debug option has only been introduced in 1.1.0rc1 afaik, 1.0.7 doesn't have anything that will help here. We need to find out where exactly it fails. Maybe I could write an email to Milan Broz about this, because I am out of ideas. signature.asc Description: OpenPGP digital signature
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
solsTiCe d'Hiver schrieb: i am beginning to think there really is a problem. i have a luks encrypted partition that i automatically mount at boot via /etc/crypttab with a *keyfile* so this has never failed and it can't fail except if the keyfile is damaged. and today the luks partition failed to be opened for the *first* time *ever* by cryptsetup because of a password problem. once i rebooted it worked. so the keyfile is not wrong. and i double check it with my backup keyfile this looks like your problem Hussam. it sometimes fails sometimes works. When did any of you guys upgrade to cryptsetup 1.0.7? Can you grep this from pacman.log please? [2009-07-25 20:43] upgraded cryptsetup (1.0.6-3 - 1.0.7-1)
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
On Tue, 2009-10-13 at 20:10 +0200, Thomas Bächler wrote: solsTiCe d'Hiver schrieb: it has been sometime ago # grep cryptsetup /var/log/pacman.log [2008-07-16 11:03] upgraded cryptsetup (1.0.6-1 - 1.0.6-1) [2008-10-08 14:29] upgraded cryptsetup (1.0.6-1 - 1.0.6-2) [2009-06-19 21:52] upgraded cryptsetup (1.0.6-2 - 1.0.6-3) [2009-08-10 14:52] upgraded cryptsetup (1.0.6-3 - 1.0.7-1) So that's not it. 1.0.7 should be working better anyway. Sadly, a viable debug option has only been introduced in 1.1.0rc1 afaik, 1.0.7 doesn't have anything that will help here. We need to find out where exactly it fails. Maybe I could write an email to Milan Broz about this, because I am out of ideas. I compiled 1.1.0rc2 then copied cryptsetup libcryptsetup.so libcryptsetup.so.1 libcryptsetup.so.1.0.0 to /tmp/testfolder then cd /tmp/testfolder then LD_LIBRARY_PATH=./ ./cryptsetup --debug luksOpen /dev/sdb1 home and it unlocks it correctly everytime!
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
On Tue, Oct 13, 2009 at 11:04 PM, Hussam Al-Tayeb ht990...@gmail.com wrote: Nice. I suggest you upgrade to 1.1.0rc2 then (changes to the PKGBUILD should be trivial). I hope it won't break anything for you further. If the problem stays away with 1.1.0, that is solution enough for me. If it returns, we need to really find out what's wrong. Done! I updated to 1.1.0-rc2 then I also upgraded to kernel 2.6.31.4 After rebooting, things are still fine. /dev/sdb1 unlocked correctly :) Could you check the upstream issues to find if one matches your case ? http://code.google.com/p/cryptsetup/issues/list?can=1q=colspec=ID+Type+Status+Priority+Milestone+Owner+Summarycells=tiles It seems there are a few issues related to udev and some locking or racing conditions : http://code.google.com/p/cryptsetup/issues/list?can=1q=udevcolspec=ID+Type+Status+Priority+Milestone+Owner+Summarycells=tiles I looked at all your mails, and it seems you never showed exactly what the output of cryptsetup was when it failed. It's good to know it's fixed in 1.1.0-rc2 but it would be better to know why.
Re: [arch-general] can't unlock a luks encrypted partition. (urgent).
On Tue, 2009-10-13 at 23:27 +0200, Xavier wrote: On Tue, Oct 13, 2009 at 11:04 PM, Hussam Al-Tayeb ht990...@gmail.com wrote: Nice. I suggest you upgrade to 1.1.0rc2 then (changes to the PKGBUILD should be trivial). I hope it won't break anything for you further. If the problem stays away with 1.1.0, that is solution enough for me. If it returns, we need to really find out what's wrong. Done! I updated to 1.1.0-rc2 then I also upgraded to kernel 2.6.31.4 After rebooting, things are still fine. /dev/sdb1 unlocked correctly :) Could you check the upstream issues to find if one matches your case ? http://code.google.com/p/cryptsetup/issues/list?can=1q=colspec=ID+Type+Status+Priority+Milestone+Owner+Summarycells=tiles It seems there are a few issues related to udev and some locking or racing conditions : http://code.google.com/p/cryptsetup/issues/list?can=1q=udevcolspec=ID+Type+Status+Priority+Milestone+Owner+Summarycells=tiles I looked at all your mails, and it seems you never showed exactly what the output of cryptsetup was when it failed. It's good to know it's fixed in 1.1.0-rc2 but it would be better to know why. It just didn't accept the passphrase as if I entered it correctly.
[arch-general] Xorg 7.5 hits testing
I've built the new Xorg 7.5 based on xorg-server 1.7.1rc1 and Mesa 7.6. Some very old drivers have been dropped because they are no more developed and won't build anymore. I hope I have updated all essential parts. Some Xorg fonts related packages still need a bump. Mesa 7.6 is built right now plain upstream. This means Gallium 3d stack for Nouveau and Intel. For Intel we might go back to old way DRI when we can't solve some existing issues. Radeon is built the old DRI way. Let's pray the update goes smooth. So far only Jan has played with Intel drivers. We will probably need some time until all important regressions and bugs have been solved. Good luck. -Andy
