Bug 190401 - kmail crashed during first use wizard when told to store password in the configuration file and not kwallet
Summary: kmail crashed during first use wizard when told to store password in the conf...
Status: RESOLVED DUPLICATE of bug 184324
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.11.1
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-23 05:31 UTC by Bill Rosmus
Modified: 2009-08-23 18:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Rosmus 2009-04-23 05:31:12 UTC
Version:           1.11.1 (using KDE 4.1.2)
Compiler:          fedora binary distribution 
OS:                Linux
Installed from:    Fedora RPMs

1) Started Kmail for the first time since installing fedora 10 distro
2) Wizard to set up account started, filled out the user name pop server smtp server yadda yadda yadda
3) Entered password for mail server
4) System asked if I would like to store my password in Kwallet. Since kwallet is a pain in the ass I said no (from my previous experience I don't want to log into something so that I can log into something, especially email since my password is sent to the mail server in clear text anyway).
5) The system popped up an essentially 'are you sure' dialog saying it would store in an encrypted form in the configuration file but it was easy to crack if someone were to gain access to my machine. (why not just use really strong encryption on that instead of a pain in the ass kwallet?).
ANYWAY, I clicked on no I still don't want kwallet store it in the configuration (and stop bugging me about it... I wish that were part of the message I could send with the button).
6) When I clicked on the button saying I still didn't want to use kwallet, Kmail crashed and burned.
7) The KDE crash handler came up and I copied the stack trace and posted it below here.

Application: KMail (kmail), signal SIGSEGV
0x00000036014a7f81 in nanosleep () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f8f0de0e810 (LWP 12644))]

Thread 2 (Thread 0x7f8f01d00950 (LWP 12653)):
#0  0x000000360200b309 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x0000003c6d45a839 in QWaitCondition::wait () from /usr/lib64/libQtCore.so.4
#2  0x0000003c6da72eac in ?? () from /usr/lib64/libQtNetwork.so.4
#3  0x0000003c6d459852 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00000036020073da in start_thread () from /lib64/libpthread.so.0
#5  0x00000036014e62bd in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f8f0de0e810 (LWP 12644)):
[KCrash Handler]
#5  0x0000003c6d454834 in QMutex::lock () from /usr/lib64/libQtCore.so.4
#6  0x0000003c6d55697a in QMetaObject::activate () from /usr/lib64/libQtCore.so.4
#7  0x0000003c6da87bf1 in QAbstractSocket::error () from /usr/lib64/libQtNetwork.so.4
#8  0x0000003c6da8948f in ?? () from /usr/lib64/libQtNetwork.so.4
#9  0x0000003c6da89649 in ?? () from /usr/lib64/libQtNetwork.so.4
#10 0x0000003c6da8ad75 in ?? () from /usr/lib64/libQtNetwork.so.4
#11 0x0000003c6da7c571 in ?? () from /usr/lib64/libQtNetwork.so.4
#12 0x0000003b7f3828dd in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4
#13 0x0000003b7f38a68a in QApplication::notify () from /usr/lib64/libQtGui.so.4
#14 0x0000003b80604f3b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#15 0x0000003c6d542391 in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4
#16 0x0000003c6d56aa19 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x0000003602c3779b in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#18 0x0000003602c3af6d in ?? () from /lib64/libglib-2.0.so.0
#19 0x0000003602c3b12b in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#20 0x0000003c6d56a79f in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4
#21 0x0000003b7f41328f in ?? () from /usr/lib64/libQtGui.so.4
#22 0x0000003c6d540cb2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4
#23 0x0000003c6d540e3d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#24 0x0000003b7f79a915 in QDialog::exec () from /usr/lib64/libQtGui.so.4
#25 0x0000003b87658456 in ?? () from /usr/lib64/libkmailprivate.so.4
#26 0x0000003b8730a95e in ?? () from /usr/lib64/libkmailprivate.so.4
#27 0x0000003b874c0a1f in KMKernel::openReader () from /usr/lib64/libkmailprivate.so.4
#28 0x0000003b874ce438 in KMKernel::action () from /usr/lib64/libkmailprivate.so.4
#29 0x0000003b874cf968 in KMKernel::handleCommandLine () from /usr/lib64/libkmailprivate.so.4
#30 0x0000000000401ff8 in _start ()



 Evolution installed nicely and works... but I don't like the interface. I use it because I can't stand the kwallet thing. It is intrusive and pisses me off. Imagine how I feel now that something involving that extraneous piece of paranoia massager not only is more annoying than being poked in the eye with an ice pick, it also crashes the application.

Have a nice day... hope you fix it. By fix it I mean get rid of kwallet.
Comment 1 Jaime Torres 2009-08-05 12:34:58 UTC
Strong encryption for storing/retrieving passwords is an old computing problem quite difficult to solve (where and how do you store the crypto key for the encryption engine?). kwallet solves this problem for all kde applications.

Kwallet will be there. There is also a gnome equivalent, and both will share the same programming interface.

Please, check the kwallet configuration to allow kmail to open the wallet without asking you a password (if this is your problem with kwallet).
Comment 2 Christophe Marin 2009-08-23 18:49:47 UTC

*** This bug has been marked as a duplicate of bug 184324 ***