Version: 4.5 (using Devel) OS: Linux Knode crashes when you want to send a reply to a thread via email just after clicking on send and entering the kwallet password for the IMAP / SMTP account. It _SEEMS_ to work as expected (no SEGV) when i get prompted to enter the PSWD for my IMAP account directly (instead of kwallet asking for to access it). Always reproducible. Reproducible: Didn't try Actual Results: gdb) continue Continuing. [New Thread 0x7f316a6c4710 (LWP 5040)] knode(5033)/kio (KIOJob) KIO::TransferJob::slotData: mimeType() not emitted when sending first data!; job URL = KUrl("nntps://snews.gmane.org:563/gmane.linux.redhat.fedora.testers/82416") data size = 35 Object::connect: No such signal KNComposerEditor::sigDragEnterEvent(QDragEnterEvent *) Object::connect: (receiver name: 'composerWindow') Object::connect: No such signal KNComposerEditor::sigDropEvent(QDropEvent *) Object::connect: (receiver name: 'composerWindow') Enchant dict for "en_US" 0x288eaa0 Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) knode(5033)/kdecore (KConfigSkeleton) KCoreConfigSkeleton::writeConfig: [Thread 0x7f316a6c4710 (LWP 5040) exited] Program received signal SIGSEGV, Segmentation fault. QDir::cleanPath (path=<value optimized out>) at io/qdir.cpp:2019 2019 QString name = path; (gdb) thread apply all bt Thread 1 (Thread 0x7f3179290820 (LWP 5033)): #0 QDir::cleanPath (path=<value optimized out>) at io/qdir.cpp:2019 #1 0x0000003054735515 in QFSFileEngine::fileName (this=<value optimized out>, file=QAbstractFileEngine::AbsoluteName) at io/qfsfileengine_unix.cpp:1067 #2 0x00000030547351fa in QFSFileEngine::fileName (this=<value optimized out>, file=QAbstractFileEngine::CanonicalName) at io/qfsfileengine_unix.cpp:1083 #3 0x00000030546f2b6e in QFileInfoPrivate::getFileName (this=0x27c5760, name=QAbstractFileEngine::CanonicalName) at io/qfileinfo.cpp:86 #4 0x00000030546f332b in QFileInfo::canonicalFilePath (this=<value optimized out>) at io/qfileinfo.cpp:510 #5 0x00000030558b1bdd in KConfigIniBackend::setFilePath (this=0x28dc580, file=<value optimized out>) at /usr/src/debug/kdelibs-4.4.92/kdecore/config/kconfigini.cpp:541 #6 0x00000030558b07be in KConfigBackend::create (componentData=<value optimized out>, file=..., sys=<value optimized out>) at /usr/src/debug/kdelibs-4.4.92/kdecore/config/kconfigbackend.cpp:89 #7 0x000000305589e819 in KConfigPrivate::changeFileName (this=0x28e1a90, name=<value optimized out>, type=<value optimized out>) at /usr/src/debug/kdelibs-4.4.92/kdecore/config/kconfig.cpp:434 #8 0x00000030558a27a5 in KConfig::KConfig (this=0x2615990, componentData=..., file=..., mode=<value optimized out>, resourceType=0x305776fa5b "config") at /usr/src/debug/kdelibs-4.4.92/kdecore/config/kconfig.cpp:168 #9 0x00000030558b7828 in KSharedConfig::KSharedConfig (this=0x2615990, componentData=<value optimized out>, fileName=<value optimized out>, flags=<value optimized out>, resType=<value optimized out>) at /usr/src/debug/kdelibs-4.4.92/kdecore/config/ksharedconfig.cpp:64 #10 0x00000030558b7a52 in KSharedConfig::openConfig (componentData=..., fileName=..., flags=<value optimized out>, resType=0x305776fa5b "config") at /usr/src/debug/kdelibs-4.4.92/kdecore/config/ksharedconfig.cpp:56 #11 0x00000030558b7bea in KSharedConfig::openConfig (fileName=..., flags=<value optimized out>, resType=0x305776fa5b "config") at /usr/src/debug/kdelibs-4.4.92/kdecore/config/ksharedconfig.cpp:35 #12 0x00000030576a08a2 in KWallet::Wallet::NetworkWallet () at /usr/src/debug/kdelibs-4.4.92/kdeui/util/kwallet.cpp:92 #13 0x0000003065821ac4 in MailTransport::Transport::readPassword (this=0x2ef50f0) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transport.cpp:283 #14 0x0000003065829807 in MailTransport::TransportManager::loadPasswords (this=0x25de9d0) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transportmanager.cpp:627 #15 0x00000030658212f6 in MailTransport::Transport::password (this=0x2efa250) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transport.cpp:82 #16 0x000000306583a087 in MailTransport::SmtpJob::startSmtpJob (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/smtpjob.cpp:153 #17 0x000000306583b6f2 in MailTransport::SmtpJob::doStart (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/smtpjob.cpp:114 #18 0x0000003065837a24 in MailTransport::TransportJob::start (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transportjob.cpp:129 #19 0x0000003065829890 in MailTransport::TransportManager::loadPasswords (this=0x25de9d0) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transportmanager.cpp:632 #20 0x00000030658212f6 in MailTransport::Transport::password (this=0x2efa250) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transport.cpp:82 #21 0x000000306583a087 in MailTransport::SmtpJob::startSmtpJob (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/smtpjob.cpp:153 #22 0x000000306583b6f2 in MailTransport::SmtpJob::doStart (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/smtpjob.cpp:114 #23 0x0000003065837a24 in MailTransport::TransportJob::start (this=0x2ef1750) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transportjob.cpp:129 #24 0x0000003065829890 in MailTransport::TransportManager::loadPasswords (this=0x25de9d0) at /usr/src/debug/kdepimlibs-4.4.92/mailtransport/transportmanager.cpp:632 Expected Results: NO SEGV :) kdebase-runtime-4.4.92-1.fc14.x86_64 kdepim-4.4.5-1.fc14.x86_64
Looking at the backtrace, I think the bug is an infinite recursion.
It should be noted that DrKonqi fail to "catch" this bug so that's the reason why i used GDB.
kdepimlibs-4.4.92-1.fc14.x86_64
same here ... knode-4.4.5
*** Bug 290663 has been marked as a duplicate of this bug. ***
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kdepim (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.