Summary: | kmail2 doesn't remember SMTP password | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Christopher Heiny <christopherheiny> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bruno, christiandehne, montel, wstephenson |
Priority: | NOR | ||
Version: | 4.7 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christopher Heiny
2012-03-22 16:20:49 UTC
you store it in kwallet ? Presumably that is the case. kmail2 or some related service does ask for access to the wallet, sometimes with annoying frequency, and sometimes on a completely different display than it is running on. Where should I check to confirm this? look at in kwalletmanager if you have mailtransport entry for example It shows mailtransports(5). Also kmail(4). I'm unable to look inside those folders, though. And I think that you have just "one" smtp ? It just happened again. I was able to capture the kmail output (unfortunately intermixed with some other stuff), appended below. Not sure if it's useful in any way. continuing request for item 65285 succeeded Enchant dict for "en_US" 0x300bdb0 Enchant dict for "en_US" 0x333b560 Could not contact query service. QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! Could not contact query service. QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! Could not contact query service. QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! Could not contact query service. QStringList Akonadi::NepomukSearch::search(const QString&) Calling blockingQuery() failed! kwalletd(2890)/kdeui (Wallet) KWalletD::setupDialog: Application ' "Mail Dispatcher Agent" ' using kwallet without parent window! QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QObject::connect: Cannot connect (null)::destroyed() to QHostInfoLookupManager::waitForThreadPoolDone() QSystemTrayIcon::setVisible: No Icon set Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No space left on device QFileSystemWatcher: failed to add paths: /etc/mtab QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No space left on device QFileSystemWatcher: failed to add paths: /etc/fstab "And I think that you have just "one" smtp ?" ? Sorry - thought I'd answered that question. My apologies... Yes, I have several SMTPs. However, I use only one - the others are for travel purposes, and haven't been used since the upgrade to Fedora 16. I have the same problem, that kmail sometimes forgets the smtp-password (using kwallet). I have several SMTPs which I all use. Same here I've 3 differents smtp out account. The sometimes seems more reproductable with clearing all kde cache you could find in /var/tmp/kde* (but could be a coincidence) Then the first time you want to send a message the ask password appear. This bug might be related a duplicate of bug 295010 which claims that the password is always forgotten after a reboot. In my case, it doesn't seem to be related to reboot. It just randomly (as far as I can tell) asks for the SMTP password. Also, I've updated to 4.8.1 (Fedora 16 RPMSs) and still observe the same issue. Still on 4.8.1 (should I update the version field in this bug?). This morning kmail2 not only forgot the SMTP password and required it to be re-entered, it also got confused as to the security settings on the SMTP server. After redoing "auto-detect" (which resulted in no change in the selected settings in the UI), sending worked OK. Happen to me on 4.8.2 just this morning. So updating the version seems a good idea This morning I send (the first mail) with signed openPGP ( which trigger the passphrase for unlocking the openGPG key), and just after the password for smtp was asked. *** This bug has been marked as a duplicate of bug 293271 *** |