Re: Latest upgrade broke Aegyptan
On Wed 07 Jan 2004 8:07 pm, Bob Underwood wrote: > On Wednesday 07 January 2004 8:53 pm, Doug Holland wrote: > > I had kmail working fine with Aegyptan until the last KDE update, > > now when I try to send a signed message, It briefly shows the > > enter-your-passphrase dialog, but that quickly disappears and is > > replaced with an error message saying > > > > "This message could not be signed! > > The Crypto Plug-In '/usr/lib/cryptplug/gpgme-openpgp.so' reported > > the following details: > > #19 : No Passphrase > > Your configuration might be invalid or the Plug-In damaged. > > Please contact your system administrator." > > > > How do I get Aegyptan's kmail integration working again? > > My 3.1.4 KMail has a click box for either the plug-in or the "Inline > OpenGPG (built in)" Using the built in works for me. > > I can confirm that the plug-in doesn't work for me. > > bob Yeah, but the built-in GPG functionality has always been half broken (WHY HASN'T IT BEEN FIXED?) so I'd rather use Aegyptan if at all possible.
Re: Packagers: What should we recommend about KDE 2 -> 3 upgrades?
On Wednesday 07 of January 2004 19:35, Ross Boylan wrote: > I would like to raise an issue for the Debian KDE package maintainers: > will someone who has been running woody KDE 2.2 run into troubles if > they upgrade to 3.x? And if so, what should we do about this? Probably, the safest way is to remove (not purge!) whole KDE from the computer and the install KDE 3.* again. I did this with transfer from KDE which is part of woody to 3.1.4 and I do not see any substantial problems with that. Matej -- Matej Cepl, http://www.ceplovi.cz/matej GPG Finger: 89EF 4BC6 288A BF43 1BAB 25C3 E09F EF25 D964 84AC 138 Highland Ave. #10, Somerville, Ma 02143, (617) 623-1488 He can compress the most words into the smallest idea of any man I know. -- Abraham Lincoln
Re: Latest upgrade broke Aegyptan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 07 January 2004 8:53 pm, Doug Holland wrote: > I had kmail working fine with Aegyptan until the last KDE update, > now when I try to send a signed message, It briefly shows the > enter-your-passphrase dialog, but that quickly disappears and is > replaced with an error message saying > > "This message could not be signed! > The Crypto Plug-In '/usr/lib/cryptplug/gpgme-openpgp.so' reported > the following details: > #19 : No Passphrase > Your configuration might be invalid or the Plug-In damaged. > Please contact your system administrator." > > How do I get Aegyptan's kmail integration working again? My 3.1.4 KMail has a click box for either the plug-in or the "Inline OpenGPG (built in)" Using the built in works for me. I can confirm that the plug-in doesn't work for me. bob -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQE//Ml9D1FnKkrNf0URAk91AJ4nCwGDKhV9FJxTCX09qHq3j9vnyQCg7yj4 tLzcPA5nUz8qCKP9R82NWKI= =lTzE -END PGP SIGNATURE-
Latest upgrade broke Aegyptan
I had kmail working fine with Aegyptan until the last KDE update, now when I try to send a signed message, It briefly shows the enter-your-passphrase dialog, but that quickly disappears and is replaced with an error message saying "This message could not be signed! The Crypto Plug-In '/usr/lib/cryptplug/gpgme-openpgp.so' reported the following details: #19 : No Passphrase Your configuration might be invalid or the Plug-In damaged. Please contact your system administrator." How do I get Aegyptan's kmail integration working again?
Source Code
I would like to apt-get source code and projects that can be loaded into KDevelop so I can learn KDE programming. Can anyone help a young (sic), budding programmer? -- Comments are appreciated, Bob
Packagers: What should we recommend about KDE 2 -> 3 upgrades?
I would like to raise an issue for the Debian KDE package maintainers: will someone who has been running woody KDE 2.2 run into troubles if they upgrade to 3.x? And if so, what should we do about this? I asked about this earlier, but want to raise it a bit more forcefully now, because subsequent conversations have reinforced my belief that the upgrade path will not work smoothly because of changes in the interpretation of configuration files, especially ~/.kde, between the two versions. If that's the case, I think it would be a huge mistake to make it easy for many users to run into this problem. I note that at least one Debian KDE FAQ explicitly recommends upgrading to 3 right over 2.2: http://davidpashley.com/debian-kde/faq.html#id2801637 (I realize the FAQ is a bit dated; I'm not sure if it's supposed to apply currently, but clearly people may run into it). And even without a recommendation, it's the "natural" thing to do. My guess is the safest route would be to compile KDE 3 to use a different directory, such as ~/.kde3. Possibly there could be some conversion scripts available. Certainly there will then be "I lost my settings" complaints otherwise (but see below: KDE may already do the conversion). Alternately, it might be possible to deal with this entirely at install time, or via some script magic that affects each user on their first start of the new package (again, maybe KDE does this already). The least attractive alternative, still better than nothing, is a warning in the appropriate packages, during installs, and somewhere in a README. I would be delighted to find such precautions are not necessary, but I'm concerned that they are. The information available on KDE's site seems to imply even major version upgrades should work, but notes that there have been reports of problems. It also seems to imply that your .kde tree is automatically migrated (http://www.kde.org/documentation/faq/install.html, esp 4.16 at http://www.kde.org/documentation/faq/install.html#id2910419 and 4.7 at http://www.kde.org/documentation/faq/install.html#id2909163). However, note 4.17 says "Normally (i.e. when not upgrading between KDE versions) it's quite safe to leave these files [a bunch of run-time communication files in ~/.kde] intact, ..." So perhaps upgrading KDE while running KDE is risky... well for other reasons too--you'll be uninstalling the KDE that you are running! P.S. Since I'm not a maintainer, and assume the maintainers read this list, I'm posting to debian-kde rather than debian-qt-kde.
