Version: 1.10.1 (using 4.1.1 (KDE 4.1.1), Debian packages) Compiler: cc OS: Linux (i686) release 2.6.25-2-686 When i create new message and insert any text (for example "kde4") from clipboard by ctrl+v of menu->paste, kmail crash. Dont any error message or bugreport master. Debian Sid/Experimental, i386, KDE 4.1.1
Does Konqueror crash as well when you do this? Please paste a backtrace here, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports.
kmail in konsole write: kmail --nofork kmail(9797) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kmail(9797) KWallet::Wallet::openWallet: Pass a valid window to KWallet::Wallet::openWallet(). kmail(9797) <unnamed>::UrlHandler::UrlHandler: UrlHandler() (iCalendar) kmail(9797) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_aspell.desktop" kmail(9797) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_hspell.desktop" kmail(9797) Sonnet::Loader::loadPlugin: Successfully loaded plugin: "kspell_enchant.desktop" Enchant dict for "ru_RU" 0xa078e98 Enchant dict for "ru" 0xa9105e8 Enchant dict for "ru" 0xa9105e8 Enchant dict for "ru_RU" 0xa078e98 kmail(9797) Sonnet::Highlighter::slotRehighlight: Highlighter::slotRehighlight() kmail: symbol lookup error: /usr/lib/libkmailprivate.so.4: undefined symbol: _ZN4KPIM8KMeditor18insertFromMimeDataEPK9QMimeData gdb write on crash: (gdb) continue Continuing. Program exited with code 0177. (gdb) thread apply all backtrace No registers. (gdb) No registers. valgrind: valgrind --log-file=/home/alexs/sdf kmail --nofork or valgrind --log-file=/home/alexs/sdf kmail kmail window not shown :(
> kmail: symbol lookup error: /usr/lib/libkmailprivate.so.4: undefined symbol: _ZN4KPIM8KMeditor18insertFromMimeDataEPK9QMimeData This is a problem with your distribution, report the bug there. You seem to be mixing invalid combinations of KMail and libkdepim packages.
*** Bug 170707 has been marked as a duplicate of this bug. ***
*** Bug 171217 has been marked as a duplicate of this bug. ***
Thanks. I've submitted a Debian bug report about this.