[Bug 249298] New: kontact crashed on startup
https://bugs.kde.org/show_bug.cgi?id=249298 Summary: kontact crashed on startup Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: klaus.la...@gmx.de Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-24-generic i686 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: Kontact crashed on startup when waiting in the background for a password from kwallet -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [KCrash Handler] #6 0xb43f46f7 in QList::operator= (this=0x9a62930, folder=0x0, recurse=true) at /usr/include/qt4/QtCore/qlist.h:410 #7 operator= (this=0x9a62930, folder=0x0, recurse=true) at /usr/include/qt4/QtCore/qstringlist.h:67 #8 KMFolderCachedImap::setNamespacesToList (this=0x9a62930, folder=0x0, recurse=true) at ../../kmail/kmfoldercachedimap.h:380 #9 KMAcctCachedImap::processNewMail (this=0x9a62930, folder=0x0, recurse=true) at ../../kmail/kmacctcachedimap.cpp:246 #10 0xb43f49a2 in KMAcctCachedImap::processNewMail (this=0x9a62930) at ../../kmail/kmacctcachedimap.cpp:209 #11 0xb436db41 in KMail::AccountManager::processNextCheck (this=0x9720368, _newMail=false) at ../../kmail/accountmanager.cpp:230 #12 0xb436e300 in KMail::AccountManager::singleCheckMail (this=0x9720368, account=0x120a3f4, interactive=false) at ../../kmail/accountmanager.cpp:157 #13 0xb42def02 in KMAccount::mailCheck (this=0x9a62930) at ../../kmail/kmaccount.cpp:447 #14 0xb42df43b in KMAccount::qt_metacall (this=0x9a62930, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff47c5c) at ./kmaccount.moc:159 #15 0xb43d46d2 in KMail::NetworkAccount::qt_metacall (this=0x9a62930, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff47c5c) at ./networkaccount.moc:64 #16 0xb43e901a in KMail::ImapAccountBase::qt_metacall (this=0x9a62930, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff47c5c) at ./imapaccountbase.moc:119 #17 0xb43f324a in KMAcctCachedImap::qt_metacall (this=0x9a62930, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff47c5c) at ./kmacctcachedimap.moc:84 #18 0x010fac9a in QMetaObject::metacall (object=0x9a62930, cl=153018216, idx=6, argv=0xbff47c5c) at kernel/qmetaobject.cpp:237 #19 0x011093d5 in QMetaObject::activate (sender=0x9758a68, m=0x12095a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293 #20 0x0115aaa7 in QTimer::timeout (this=0x9758a68) at .moc/release-shared/moc_qtimer.cpp:134 #21 0x060e in QTimer::timerEvent (this=0x9758a68, e=0xbff48190) at kernel/qtimer.cpp:271 #22 0x01106254 in QObject::event (this=0x9758a68, e=0x0) at kernel/qobject.cpp:1212 #23 0x02ea14dc in QApplicationPrivate::notify_helper (this=0x91acda8, receiver=0x9758a68, e=0xbff48190) at kernel/qapplication.cpp:4300 #24 0x02ea805e in QApplication::notify (this=0xbff49ff4, receiver=0x9758a68, e=0xbff48190) at kernel/qapplication.cpp:3704 #25 0x009b7f2a in KApplication::notify (this=0xbff49ff4, receiver=0x9758a68, event=0xbff48190) at ../../kdeui/kernel/kapplication.cpp:302 #26 0x010f5a3b in QCoreApplication::notifyInternal (this=0xbff49ff4, receiver=0x9758a68, event=0xbff48190) at kernel/qcoreapplication.cpp:704 #27 0x01124d66 in QCoreApplication::sendEvent (this=0x91b7a74) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #28 QTimerInfoList::activateTimers (this=0x91b7a74) at kernel/qeventdispatcher_unix.cpp:603 #29 0x011218e4 in timerSourceDispatch (source=0x91b7a40) at kernel/qeventdispatcher_glib.cpp:184 #30 0x0219d5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #31 0x021a12d8 in ?? () from /lib/libglib-2.0.so.0 #32 0x021a14b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #33 0x011215d5 in QEventDispatcherGlib::processEvents (this=0x9187070, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #34 0x02f61135 in QGuiEventDispatcherGlib::processEvents (this=0x9187070, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #35 0x010f4059 in QEventLoop::processEvents (this=0xbff48534, flags=) at kernel/qeventloop.cpp:149 #36 0x010f44aa in QEventLoop::exec (this=0xbff48534, flags=...) at kernel/qeventloop.cpp:201 #37 0x00a5876f in KWallet::Wallet::openWallet (name=..., w=0, ot=KWallet::Wallet::Synchronous) at ../../kdeui/util/kwallet.cpp:260 #38 0xb4455c7e in KMKernel::wallet (this=0x96596c8) at ../../kmail/kmkernel.cpp:2498 #39 0xb43d6fdd in KMail::NetworkAccount::readPassword (this=0x9a62930) at ../../kmail/networkaccount.cpp:328 #40 0xb43d79c1 in KMail::NetworkAccount::readConfig (this=0x9a62930, config=...) at ../../kmail/networkaccount.cpp:170 #41 0xb43e765f in KMail::ImapAccountBase::readConfig (this=0x9a62930, config=...) at ../../kmail/imapaccountbase.cpp:207 #42 0xb43f3b16 in KMAcctCachedImap::readConfig (this=0x9a62930, config=...) at ../../kmail/
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #153 from Ian 2010-08-28 04:18:33 --- I paid for the original HTML capabilities some years ago, to be implemented. As I've written previously, I'm willing to "donate" toward getting this bug resolved and will commit $40.00 as well. Problem I have though is that I had expected based on my understanding on what I was paying for originally, was that this bug wouldn't have even been necessary. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 235481] all dimap data / receiving mail accounts deleted
https://bugs.kde.org/show_bug.cgi?id=235481 --- Comment #5 from Kaleb Pederson 2010-08-27 23:44:15 --- Note, I'm currently running KMail version 1.13.5 on KDE 4.4.5 on 64-bit Gentoo. Although after the fact, the following found no files for which I did not have read-write access: $ find . ! -perm -600 -print -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 235481] all dimap data / receiving mail accounts deleted
https://bugs.kde.org/show_bug.cgi?id=235481 --- Comment #4 from Kaleb Pederson 2010-08-27 23:35:01 --- Created an attachment (id=51039) --> (http://bugs.kde.org/attachment.cgi?id=51039) strace log showing dimap files being deleted -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 235481] all dimap data / receiving mail accounts deleted
https://bugs.kde.org/show_bug.cgi?id=235481 --- Comment #3 from Kaleb Pederson 2010-08-27 23:34:04 --- Created an attachment (id=51038) --> (http://bugs.kde.org/attachment.cgi?id=51038) New accounts dialog I was greeted with. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 235481] all dimap data / receiving mail accounts deleted
https://bugs.kde.org/show_bug.cgi?id=235481 --- Comment #2 from Kaleb Pederson 2010-08-27 23:33:26 --- Created an attachment (id=51037) --> (http://bugs.kde.org/attachment.cgi?id=51037) one of 47 dialogs displaying a uid cache file error -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 235481] all dimap data / receiving mail accounts deleted
https://bugs.kde.org/show_bug.cgi?id=235481
--- Comment #1 from Kaleb Pederson 2010-08-27
23:31:32 ---
This just happened again. Upon restarting my system and logging in I started
kmail. It didn't appear right away. Remembering what happened before, I ran
strace:
[***ki...@kibab ~***]$ ps aux | grep [k]mail
kibab19634 3.5 0.4 475692 37216 ?D14:05 0:02 /usr/bin/kmail
-caption KMail
[***ki...@kibab ~***]$ strace -o strace.log -f -ff -s1024 -p 19634
Process 19634 attached - interrupt to quit
^CProcess 19634 detached
The strace log shows that it was indeed deleting all my files. Here's a small
excerpt:
stat("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272262518.17914.pEJzl:2,S",
{st_mode=S_IFREG|0644, st_size=3345, ...}) = 0
lstat("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272262518.17914.pEJzl:2,S",
{st_mode=S_IFREG|0644, st_size=3345, ...}) = 0
getdents(16, /* 0 entries */, 32768)= 0
close(16) = 0
stat("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272262518.17914.UT4E3:2,S",
{st_mode=S_IFREG|0644, st_size=2240, ...}) = 0
lstat("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272262518.17914.UT4E3:2,S",
{st_mode=S_IFREG|0644, st_size=2240, ...}) = 0
brk(0x14f1000) = 0x14f1000
brk(0x1512000) = 0x1512000
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261978.17914.QbIQK:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261978.17914.riLCe:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261978.17914.yejcA:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261979.17914.382pG:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261979.17914.CnuoW:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261979.17914.rxmbp:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261980.17914.avpv7:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261980.17914.NXR67:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261981.17914.7BMzz:2,S")
= 0
unlink("/home/kibab/.kde4/share/apps/kmail/dimap/.1948823749.directory/qt/cur/1272261981.17914.TJhkk:2,S")
= 0
I'll attach the full log, which I probably should have let run longer to help
in debugging.
When kmail finally came up I was greeted with 47 dialogs like
kmail_permissions_error.png (attached). The error message read:
The UID cache file for folder 2046725245/[Gmail]/Trash could not be written.
There could be a problem with file system permissions.
Once I closed down all the error dialogs, I was once again greeted with the new
accounts dialog (kmail_new_accounts.png, attached).
As last time, this resulted in both of my dimap accounts being completely
deleted. My account settings were also deleted although my POP-based e-mail was
still present.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #10 from Louis-Philippe 2010-08-27 22:40:32 --- For me, to reproduce the problem, I only have to launch Kmail, kwallet popup asking for password, I open the wallet, akonadi shows a error report saying that, among other errors, it is not registered with D-Bus, and I close the error report. Kmail works fine until I create a new email and click send... Until I click send, I did not experience any other problems. Kalendar is working fine, The contacts are not accessible (because of akonadi not started) and thats about it. I can receive emails w/o problems. All that time, no akonadi instance in the processes list. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249273] New: Kontact crash when opening Kontact config window
https://bugs.kde.org/show_bug.cgi?id=249273 Summary: Kontact crash when opening Kontact config window Product: kontact Version: 4.4.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: tim.klas...@gmail.com Application: kontact (4.4.5) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.7.0 Operating System: Linux 2.6.32-24-generic x86_64 Distribution: KXStudio 10.04 LTS -- Information about the crash: - What I was doing when the application crashed: clicked on configure kontact button in menu settings and kontact immediately crashed. This occurs repeatedly without any way of opening the kontact config window. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7faa2b2e7780 (LWP 21474))] Thread 2 (Thread 0x7faa0c631710 (LWP 21475)): #0 IA__g_main_context_acquire (context=0x159e6e0) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2049 #1 0x7faa21015295 in g_main_context_iterate (context=0x159e6e0, block=0, dispatch=207821376, self=0x1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2535 #2 0x7faa210158fc in IA__g_main_context_iteration (context=0x159e6e0, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654 #3 0x7faa28a44bd6 in QEventDispatcherGlib::processEvents (this=0x14c8880, flags=) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7faa28a177b2 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7faa28a17b9c in QEventLoop::exec (this=0x7faa0c630d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7faa2892323d in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7faa289f76d8 in QInotifyFileSystemWatcherEngine::run (this=0x15d6a80) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7faa289261be in QThreadPrivate::start (arg=0x15d6a80) at thread/qthread_unix.cpp:266 #9 0x7faa233a29ca in start_thread (arg=) at pthread_create.c:300 #10 0x7faa282fa6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7faa2b2e7780 (LWP 21474)): [KCrash Handler] #6 0x7faa050f0e14 in ?? () from /usr/lib/libkmailprivate.so.4 #7 0x7faa050f in MiscPage::MiscPage(KComponentData const&, QWidget*) () from /usr/lib/libkmailprivate.so.4 #8 0x7faa05937fe7 in create_kmail_config_misc () from /usr/lib/kde4/kcm_kmail.so #9 0x7faa271f5829 in KCModuleLoader::loadModule (mod=..., report=, parent=, args=) at ../../kutils/kcmoduleloader.cpp:111 #10 0x7faa271f9cc9 in KCModuleProxyPrivate::loadModule (this=0x28deae0) at ../../kutils/kcmoduleproxy.cpp:106 #11 0x7faa271fa7f5 in KCModuleProxy::realModule (this=) at ../../kutils/kcmoduleproxy.cpp:83 #12 0x7faa271fa869 in KCModuleProxy::useRootOnlyMessage (this=0x7faa28592e40) at ../../kutils/kcmoduleproxy.cpp:315 #13 0x7faa271f6dce in KCMultiDialog::addModule (this=0x2349630, moduleInfo=..., parentItem=, args=) at ../../kutils/kcmultidialog.cpp:339 #14 0x7faa2720eca4 in KSettings::DialogPrivate::createDialogFromServices (this=0x2687240) at ../../kutils/ksettings/dialog.cpp:358 #15 0x7faa2720fca0 in KSettings::Dialog::showEvent (this=) at ../../kutils/ksettings/dialog.cpp:127 #16 0x7faa2943d2c9 in QWidget::event (this=0x2349630, event=0x7fff4ce72470) at kernel/qwidget.cpp:8364 #17 0x7faa293e7cdc in QApplicationPrivate::notify_helper (this=0x10a3410, receiver=0x2349630, e=0x7fff4ce72470) at kernel/qapplication.cpp:4389 #18 0x7faa293ed7cd in QApplication::notify (this=0x7fff4ce740f0, receiver=0x2349630, e=0x7fff4ce72470) at kernel/qapplication.cpp:4270 #19 0x7faa2a13ceb6 in KApplication::notify (this=0x7fff4ce740f0, receiver=0x2349630, event=0x7fff4ce72470) at ../../kdeui/kernel/kapplication.cpp:310 #20 0x7faa28a18a8c in QCoreApplication::notifyInternal (this=0x7fff4ce740f0, receiver=0x2349630, event=0x7fff4ce72470) at kernel/qcoreapplication.cpp:732 #21 0x7faa2944156a in QCoreApplication::sendEvent (this=0x277a4b0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 QWidgetPrivate::show_helper (this=0x277a4b0) at kernel/qwidget.cpp:7337 #23 0x7faa29442dba in QWidget::setVisible (this=0x2349630, visible=) at kernel/qwidget.cpp:7559 #24 0x7faa298d484c in QDialog::setVisible (this=0x2349630, visible=) at dialogs/qdialog.cpp:733 #25 0x7faa2af10e18 in Kontact::MainWindow::slotPreferences() () from /usr/lib/libkontactprivate.so.4 #26 0x7faa2af153fe in Kontact::MainWindow::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkontactprivate.so.4 #27 0x7faa28a307a7 in QMetaObject::activate (sender=0x15e2750, m=, local_signal_index=, argv=0x13d60) at kernel/qobject.cpp:3280 #28 0x7faa293e0622 in QAction::triggered (this=0x7faa28592e40, _t1=fal
[Bug 245379] akonadi_kolabproxy_resource not available prevents creation of an addressbook
https://bugs.kde.org/show_bug.cgi?id=245379 --- Comment #1 from Sabine Faure 2010-08-27 22:16:20 --- Could not retest since 'Accounts' functionality from 'Actions' tab not implemented. I will retest later. Note: the bug description has changed due to a kab-mobile layout modification: - Launch kab-mobile - Open the 'Actions' tab - Click on Accounts - Fill in the account information N900, 4:4.5~20100827.1168874-1maemo1.1168783 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249272] New: Kontact crashes after re-opening
https://bugs.kde.org/show_bug.cgi?id=249272 Summary: Kontact crashes after re-opening Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: ferdom...@hotmail.com Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-24-generic x86_64 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: After closing kontact, crashes in re-opening. The first closing, throw an error of akonadi -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7fcb11b05780 (LWP 1762))] Thread 2 (Thread 0x7fcaecb91710 (LWP 1853)): #0 0x7fcb0ebd4f83 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fcb077094a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7fcb077098fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7fcb0ffc0566 in QEventDispatcherGlib::processEvents (this=0x7fcae8082b20, flags=) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7fcb0ff95992 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7fcb0ff95d6c in QEventLoop::exec (this=0x7fcaecb90d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7fcb0fe9fd59 in QThread::exec (this=) at thread/qthread.cpp:487 #7 0x7fcb0ff76178 in QInotifyFileSystemWatcherEngine::run (this=0x2491680) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7fcb0fea2775 in QThreadPrivate::start (arg=0x2491680) at thread/qthread_unix.cpp:248 #9 0x7fcb09c809ca in start_thread (arg=) at pthread_create.c:300 #10 0x7fcb0ebe16fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fcb11b05780 (LWP 1762)): [KCrash Handler] #5 Kontact::MainWindow::activateInitialPluginModule (this=0x1a7d640) at ../../../kontact/src/mainwindow.cpp:289 #6 0x00404722 in KontactApp::newInstance (this=0x7fff31b6cb20) at ../../../kontact/src/main.cpp:149 #7 0x7fcb109866b6 in KUniqueApplicationAdaptor::newInstance (this=0x19d1540, asn_id=, args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:454 #8 0x7fcb10986cf6 in KUniqueApplicationAdaptor::qt_metacall (this=0x19d1540, _c=QMetaObject::InvokeMetaMethod, _id=31337840, _a=0x7fff31b6bce0) at ./kuniqueapplication_p.moc:81 #9 0x7fcb0d3e2486 in QDBusConnectionPrivate::deliverCall (this=, object=, msg=, metaTypes=..., slotIdx=) at qdbusintegrator.cpp:904 #10 0x7fcb0d3e374b in QDBusConnectionPrivate::activateCall (this=, object=0x19d1540, flags=337, msg=...) at qdbusintegrator.cpp:816 #11 0x7fcb0d3e41cd in QDBusConnectionPrivate::activateObject (this=, node=, msg=..., pathStartPos=) at qdbusintegrator.cpp:1364 #12 0x7fcb0d3e4468 in QDBusActivateObjectEvent::placeMetaCall (this=0x43beb70) at qdbusintegrator.cpp:1477 #13 0x7fcb0ffa6d49 in QObject::event (this=0x7fff31b6cb20, e=0x43beb70) at kernel/qobject.cpp:1248 #14 0x7fcb0f35459d in QApplication::event (this=0x7fff31b6cb20, e=0x43beb70) at kernel/qapplication.cpp:2353 #15 0x7fcb0f35022c in QApplicationPrivate::notify_helper (this=0x19123e0, receiver=0x7fff31b6cb20, e=0x43beb70) at kernel/qapplication.cpp:4300 #16 0x7fcb0f3566fb in QApplication::notify (this=0x7fff31b6cb20, receiver=0x7fff31b6cb20, e=0x43beb70) at kernel/qapplication.cpp:4183 #17 0x7fcb1097f526 in KApplication::notify (this=0x7fff31b6cb20, receiver=0x7fff31b6cb20, event=0x43beb70) at ../../kdeui/kernel/kapplication.cpp:302 #18 0x7fcb0ff9706c in QCoreApplication::notifyInternal (this=0x7fff31b6cb20, receiver=0x7fff31b6cb20, event=0x43beb70) at kernel/qcoreapplication.cpp:704 #19 0x7fcb0ff997e7 in QCoreApplication::sendEvent (receiver=0x0, event_type=, data=0x18e4620) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=, data=0x18e4620) at kernel/qcoreapplication.cpp:1345 #21 0x7fcb0ffc09d3 in QCoreApplication::sendPostedEvents (s=) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #22 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:276 #23 0x7fcb077058c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #24 0x7fcb07709748 in ?? () from /lib/libglib-2.0.so.0 #25 0x7fcb077098fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #26 0x7fcb0ffc0513 in QEventDispatcherGlib::processEvents (this=0x18e3d70, flags=) at kernel/qeventdispatcher_glib.cpp:412 #27 0x7fcb0f40046e in QGuiEventDispatcherGlib::processEvents (this=0x1a7d640, flags=) at kernel/qguieventdispatcher_glib.cpp:204 #28 0x7fcb0ff95992 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #29 0x7fcb0ff95d6c in QEven
[Bug 242808] No address book created by default
https://bugs.kde.org/show_bug.cgi?id=242808 Sabine Faure changed: What|Removed |Added Status|RESOLVED|VERIFIED -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 246519] Issues that need improvements in order to make n900 kdepim-mobile usable (aka "beta")
https://bugs.kde.org/show_bug.cgi?id=246519 Bug 246519 depends on bug 242808, which changed state. Bug 242808 Summary: No address book created by default http://bugs.kde.org/show_bug.cgi?id=242808 What|Old Value |New Value Status|NEW |RESOLVED Resolution||FIXED -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 242808] No address book created by default
https://bugs.kde.org/show_bug.cgi?id=242808 Sabine Faure changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Comment #5 from Sabine Faure 2010-08-27 22:07:01 --- It is corrected now. N900, 4:4.5~20100827.1168874-1maemo1.1168783 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249036] Configure account button not implemented
https://bugs.kde.org/show_bug.cgi?id=249036 Sabine Faure changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #2 from Sabine Faure 2010-08-27 21:59:54 --- It is corrected now. The 'Configure account' button has been removed and it is possible instead to go to the Actions tab - Account - Edit account to get the configure account dialogue now. N900, 4:4.5~20100827.1168874-1maemo1.1168783 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 248554] Regression: Imap folder changes are not displayed (no longer synchronized?)
https://bugs.kde.org/show_bug.cgi?id=248554 Sabine Faure changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED | --- Comment #13 from Sabine Faure 2010-08-27 21:53:12 --- I retested this today and it still does not sync unfortunately. I get the same info as in comment #11 in the terminal (see above) so I am reopening this bug. N900,4:4.5~20100827.1168874-1maemo1.1168783 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 231377] 'Use as Default Calendar' functionality does not seem to work
https://bugs.kde.org/show_bug.cgi?id=231377 Sabine Faure changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME | --- Comment #4 from Sabine Faure 2010-08-27 21:32:18 --- I retested this today and it is nearly corrected. The calendar set as default is displayed correctly in the New event dialogue as long as it is a local calendar. However, when selecting a kolab calendar as a default one (ex: Calendar) then another one, (a local calendar) is displayed instead, when the new event dialogue opens. Because of this I am reopening this bug. Trunk, Svn Rev 1168877 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Pascal changed: What|Removed |Added CC||pascal.hasko.bernh...@googl ||email.com --- Comment #152 from Pascal 2010-08-27 21:06:17 --- My $40 are also on the table. I do not want to enter into the debate about the merits and perils of using HTML in emails, nor do I know much about its security issues. I can live without HTML reply enabled in Kmail, but some recipients expect my replies in this format. Even developers who do not like HTML in messages might have an interest in seing this feature implemented, as this would make Kmail more attractive for end-users thus increasing usage and popularity of the mail programme. Why not setting no HTML as default and giving notice to users who activate the feature? I have read someplace that te current version of Thunderbird has found a solution to the security problems, so that seems possible after all. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249269] Kmail crashes on launch (Nepomuk pb)
https://bugs.kde.org/show_bug.cgi?id=249269 David Faure changed: What|Removed |Added CC||fa...@kde.org AssignedTo|kdepim-bugs@kde.org |sebast...@trueg.de --- Comment #1 from David Faure 2010-08-27 20:57:54 --- valgrind log: ==2709== Invalid read of size 4 ==2709==at 0x76160B4: QBasicAtomicInt::ref() (qatomic_x86_64.h:121) ==2709==by 0x76643DC: QExplicitlySharedDataPointer::QExplicitlySharedDataPointer(QExplicitlySharedDataPointer const&) (qshareddata.h:162) ==2709==by 0x7663D7F: Nepomuk::Types::EntityManager::getClass(QUrl const&) (entitymanager.cpp:42) ==2709==by 0x765625C: Nepomuk::Types::Class::Class(QUrl const&) (class.cpp:286) ==2709==by 0x7623216: Nepomuk::ResourceData::constHasType(QUrl const&) const (resourcedata.cpp:224) ==2709==by 0x76231D6: Nepomuk::ResourceData::hasType(QUrl const&) (resourcedata.cpp:215) ==2709==by 0x762484E: Nepomuk::ResourceData::load() (resourcedata.cpp:393) ==2709==by 0x762333B: Nepomuk::ResourceData::property(QUrl const&) (resourcedata.cpp:239) ==2709==by 0x7635259: Nepomuk::Resource::property(QUrl const&) const (resource.cpp:271) ==2709==by 0x7637429: Nepomuk::Resource::label() const (resource.cpp:771) ==2709==by 0x6020141: KMFilterActionAddTag::KMFilterActionAddTag() (kmfilteraction.cpp:912) ==2709==by 0x601FD16: KMFilterActionAddTag::newAction() (kmfilteraction.cpp:905) ==2709==by 0x602A1AC: KMFilterActionDict::insert(KMFilterAction* (*)()) (kmfilteraction.cpp:2212) ==2709==by 0x6029F76: KMFilterActionDict::init() (kmfilteraction.cpp:2186) ==2709==by 0x602A14A: KMFilterActionDict::KMFilterActionDict() (kmfilteraction.cpp:2207) ==2709==by 0x6060B79: KMKernel::init() (kmkernel.cpp:1159) This is with kdesupport trunk, kdelibs-4.5, kdepimlibs+kdepim trunk. Is this an unsupported combination? Also on KDE startup, nepomukservicestub crashes with a similar backtrace. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249269] Kmail crashes on launch (Nepomuk pb)
https://bugs.kde.org/show_bug.cgi?id=249269 Sabine Faure changed: What|Removed |Added Component|general |general Version|2.0.89 |unspecified Product|KMail 2 |nepomuk -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249269] New: Kmail crashes on launch (Nepomuk pb)
https://bugs.kde.org/show_bug.cgi?id=249269 Summary: Kmail crashes on launch (Nepomuk pb) Product: KMail 2 Version: 2.0.89 Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: sab...@kdab.net Application: kmail (2.0.89) KDE Platform Version: 4.5.1 (KDE 4.5.1) (Compiled from sources) Qt Version: 4.6.2 Operating System: Linux 2.6.32-19-generic x86_64 Distribution: Ubuntu lucid (development branch) -- Information about the crash: - What I was doing when the application crashed: - Go to menu K - Type in 'Kmail' - Click on 'Kmail' entry from the K menu Kmail crashes Trunk, Svn Rev 1168877 The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault [KCrash Handler] #6 0x7f4ba64a40b4 in QBasicAtomicInt::ref (this=0x40008) at /d/qt/4/kde-qt/include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:121 #7 0x7f4ba64f23d9 in QExplicitlySharedDataPointer (this=0x7fffd4d94b40, o=...) at /d/qt/4/kde-qt/include/QtCore/../../src/corelib/tools/qshareddata.h:162 #8 0x7f4ba64f1d7c in Nepomuk::Types::EntityManager::getClass (this=0xbf1d10, uri=...) at /d/kde/src/t/kdelibs/nepomuk/types/entitymanager.cpp:42 #9 0x7f4ba64e4259 in Class (this=0x7fffd4d94b80, uri=...) at /d/kde/src/t/kdelibs/nepomuk/types/class.cpp:286 #10 0x7f4ba64b1217 in Nepomuk::ResourceData::constHasType (this=0xbf1950, uri=...) at /d/kde/src/t/kdelibs/nepomuk/core/resourcedata.cpp:224 #11 0x7f4ba64b11d7 in Nepomuk::ResourceData::hasType (this=0xbf1950, uri=...) at /d/kde/src/t/kdelibs/nepomuk/core/resourcedata.cpp:215 #12 0x7f4ba64b284f in Nepomuk::ResourceData::load (this=0xbf1950) at /d/kde/src/t/kdelibs/nepomuk/core/resourcedata.cpp:393 #13 0x7f4ba64b133c in Nepomuk::ResourceData::property (this=0xbf1950, uri=...) at /d/kde/src/t/kdelibs/nepomuk/core/resourcedata.cpp:239 #14 0x7f4ba64c3256 in Nepomuk::Resource::property (this=0xbfac90, uri=...) at /d/kde/src/t/kdelibs/nepomuk/core/resource.cpp:271 #15 0x7f4ba64c5426 in Nepomuk::Resource::label (this=0xbfac90) at /d/kde/src/t/kdelibs/nepomuk/core/resource.cpp:771 #16 0x7f4ba79f1142 in KMFilterActionAddTag (this=0xbebc30) at /d/kde/src/t/kdepim/kmail/kmfilteraction.cpp:912 #17 0x7f4ba79f0d17 in KMFilterActionAddTag::newAction () at /d/kde/src/t/kdepim/kmail/kmfilteraction.cpp:905 #18 0x7f4ba79fb1ad in KMFilterActionDict::insert (this=0x1014840, aNewFunc=0x7f4ba79f0cf2 ) at /d/kde/src/t/kdepim/kmail/kmfilteraction.cpp:2212 #19 0x7f4ba79faf77 in KMFilterActionDict::init (this=0x1014840) at /d/kde/src/t/kdepim/kmail/kmfilteraction.cpp:2186 #20 0x7f4ba79fb14b in KMFilterActionDict (this=0x1014840) at /d/kde/src/t/kdepim/kmail/kmfilteraction.cpp:2207 #21 0x7f4ba7a31b7a in KMKernel::init (this=0x7fffd4d951f0) at /d/kde/src/t/kdepim/kmail/kmkernel.cpp:1159 #22 0x00403814 in main (argc=3, argv=0x7fffd4d95488) at /d/kde/src/t/kdepim/kmail/main.cpp:129 Reported using DrKonqi -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249106] Check what server supports
https://bugs.kde.org/show_bug.cgi?id=249106 Michal Wazgird changed: What|Removed |Added CC||cyry...@gmail.com --- Comment #2 from Michal Wazgird 2010-08-27 20:06:15 --- It's wrong library linking. See here: http://www.pclinuxos.com/forum/index.php/topic,78088.msg645442.html#msg645442 Snippet of backtrace in my case: #7 0xb3386234 in EVP_MD_CTX_md () from /usr/lib/libcrypto.so.0.9.8 #8 0xabe2ac66 in tls1_enc () from /usr/lib/libssl.so.1.0.0 And problem solved by symlinking libcrypto.so.0.9.8 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249109] KMail will not receive email
https://bugs.kde.org/show_bug.cgi?id=249109 Michal Wazgird changed: What|Removed |Added CC||cyry...@gmail.com --- Comment #2 from Michal Wazgird 2010-08-27 19:55:28 --- For me it was two versions of openssl installed (0.9.8 and 1.0.0) and wrong linking. Symlinking libcrypto.so.0.9.8 to libcrypto.so.1.0.0 solved the problem. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249249] Kontact crashes when logging out of/shutting down KDE.
https://bugs.kde.org/show_bug.cgi?id=249249 Pino Toscano changed: What|Removed |Added Component|general |general Version|4.4.5 |unspecified AssignedTo|kdepim-bugs@kde.org |akregator-de...@lists.sourc ||eforge.net Product|kontact |akregator -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249249] New: Kontact crashes when logging out of/shutting down KDE.
https://bugs.kde.org/show_bug.cgi?id=249249 Summary: Kontact crashes when logging out of/shutting down KDE. Product: kontact Version: 4.4.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: lnx...@westlot.net Version: 4.4.5 (using KDE 4.5.0) OS:Linux First, this is not a duplicate of Bug 199530, as everything runs fine up until logout/shutdown. Nor is is a duplicate of Bug 225860, as Kontact shuts down normally from the menu (File-Quit). This may be related to Bug 116482, but is not a duplicate as *I* am not invoking Akregator. I am aware of this bug, so am not using Akregator until it is resolved (although Akregator is, temptingly, sitting in the sidebar). What happens is, when I leave KDE either by shutting down or logging out, I notice in the system tray the Akregator icon appears for an instance, then disappears. The screen clears as if a normal shutdown is happening then I get a message that Kontact has crashed. After this happens, I get Bug 185544 upon startup, but if I quit Kontact via the menu before shutting down, I do not. It seems to me that, for some reason, when KDE sends the shutdown signal to Kontact, it tries to read the Akregator feeds, where it does not when exited from the menu. Reproducible: Always Steps to Reproduce: Leave Kontact running and log out of KDE or shutdown the system. Actual Results: Kontact crashes. Expected Results: Kontact does not crash. I saved this backtrace on the last instance: Application: kontact (4.4.5) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.7.0 Operating System: Linux 2.6.32-24-generic x86_64 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f9965617780 (LWP 3423))] Thread 2 (Thread 0x7f993f81a710 (LWP 3445)): #0 0x7f9962612f83 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f995b33a4a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x7f995b33a8fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x7f9962d69bd6 in QEventDispatcherGlib::processEvents (this=0x2eb6d10, flags=) at kernel/qeventdispatcher_glib.cpp:414 #4 0x7f9962d3c7b2 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #5 0x7f9962d3cb9c in QEventLoop::exec (this=0x7f993f819d90, flags=) at kernel/qeventloop.cpp:201 #6 0x7f9962c4823d in QThread::exec (this=) at thread/qthread.cpp:490 #7 0x7f9962d1c6d8 in QInotifyFileSystemWatcherEngine::run (this=0x2eae850) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x7f9962c4b1be in QThreadPrivate::start (arg=0x2eae850) at thread/qthread_unix.cpp:266 #9 0x7f995d6c79ca in start_thread (arg=) at pthread_create.c:300 #10 0x7f996261f6fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7f9965617780 (LWP 3423)): [KCrash Handler] #6 memcpy () at ../sysdeps/x86_64/memcpy.S:267 #7 0x7f9939d476cb in c4_Column::CopyData (this=0x2e576f8, to_=, from_=, count_=3298) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:305 #8 0x7f9939d4809f in c4_Column::Grow (this=0x2e576f8, off_=, diff_=103) at ../../../../akregator/plugins/mk4storage/metakit/src/column.cpp:556 #9 0x7f9939d52455 in c4_FormatB::SetOne (this=0x2e576e0, index_=126, xbuf_=, ignoreMemos_=) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:608 #10 0x7f9939d525c8 in c4_FormatS::Set (this=0x416a550, index_=8, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/format.cpp:863 #11 0x7f9939d61110 in c4_Sequence::Set (this=0x305ef50, index_=126, prop_=..., buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:335 #12 0x7f9939d59e58 in c4_HashViewer::SetItem (this=0x3206b10, row_=126, col_=6, buf_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/remap.cpp:366 #13 0x7f9939d61565 in c4_Sequence::SetAt (this=0x2eaca30, index_=126, newElem_=...) at ../../../../akregator/plugins/mk4storage/metakit/src/viewx.cpp:104 #14 0x7f9939d629a5 in c4_View::SetAt (this=0x2f94df0, guid=, link=...) at ../../../../akregator/plugins/mk4storage/metakit/include/mk4.inl:89 #15 Akregator::Backend::FeedStorageMK4Impl::setLink (this=0x2f94df0, guid=, link=...) at ../../../../akregator/plugins/mk4storage/feedstoragemk4impl.cpp:451 #16 0x7f993a68a233 in Private (this=0x40bb890, article=..., feed_=, archive_=) at ../../../akregator/src/article.cpp:182 #17 0x7f993a68aff5 in Article (this=0x7fffb809cd80, article=..., feed=0x39a9260) at ../../../akregator/src/article.cpp:245 #18 0x7f993a697580 in Akregator::Feed::appendArticles (this=0x39a9260, feed
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #151 from John A. Sullivan III 2010-08-27 19:01:45 --- On Fri, 2010-08-27 at 10:59 +0200, Jakub Benda wrote: > https://bugs.kde.org/show_bug.cgi?id=86423 > > > Jakub Benda changed: > >What|Removed |Added > > CC||alban...@atlas.cz > > > > > --- Comment #148 from Jakub Benda 2010-08-27 10:59:19 --- > I am missing this feature, too. And I would happily join with my $40 as well > if > there was a chance it would change something. > I have asked Tim Pearson of the Trinity project (http://trinity.pearsoncomputing.net) if he is interested in doing this work and how much it would cost. I've not yet heard back from him - John -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 193514] Crash when activating plugin [[Kontact::Plugin::identifier], Kontact::MainWindow::activatePluginModule, Kontact::MainWindow::setActivePluginModule, KontactApp::newInstance]
https://bugs.kde.org/show_bug.cgi?id=193514 Frédéric COIFFIER changed: What|Removed |Added CC||frederic.coiff...@free.fr -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249109] KMail will not receive email
https://bugs.kde.org/show_bug.cgi?id=249109 Macedonio Fernandez changed: What|Removed |Added CC||muso...@yahoo.com.ar --- Comment #1 from Macedonio Fernandez 2010-08-27 17:12:51 --- Kmail is not able to send mails either. (I'm using gmail for smtp). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249231] New: kontact crashes when kmail is opened
https://bugs.kde.org/show_bug.cgi?id=249231 Summary: kontact crashes when kmail is opened Product: kontact Version: 4.4.2 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: kdeb...@ringle.org Application: kontact (4.4.2) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-24-generic-pae i686 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: First time I tried opening kmail, kontact crashed. A subsequent attempt to open kmail resulted in no crash. The crash does not seem to be reproducible. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0xb35de990 (LWP 26797))] Thread 2 (Thread 0xae63eb70 (LWP 26865)): #0 0xb410d79f in g_main_context_check () from /lib/libglib-2.0.so.0 #1 0xb410e0ce in ?? () from /lib/libglib-2.0.so.0 #2 0xb410e4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0xb6cbf60f in QEventDispatcherGlib::processEvents (this=0xadd00468, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #4 0xb6c92059 in QEventLoop::processEvents (this=0xae63e270, flags=) at kernel/qeventloop.cpp:149 #5 0xb6c924aa in QEventLoop::exec (this=0xae63e270, flags=...) at kernel/qeventloop.cpp:201 #6 0xb6b8e5a8 in QThread::exec (this=0xa1c2fd0) at thread/qthread.cpp:487 #7 0xb6c71c1b in QInotifyFileSystemWatcherEngine::run (this=0xa1c2fd0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0xb6b9132e in QThreadPrivate::start (arg=0xa1c2fd0) at thread/qthread_unix.cpp:248 #9 0xb43fb96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #10 0xb5f10a4e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb35de990 (LWP 26797)): [KCrash Handler] #6 0xb7579b50 in KontactInterface::Plugin::part (this=0xa0dfd90) at ../../kontactinterface/plugin.cpp:190 #7 0xafe0ba7d in KMailUniqueAppHandler::newInstance (this=0xa0f8c20) at ../../../../kontact/plugins/kmail/kmail_plugin.cpp:216 #8 0xb757b7e9 in KontactInterface::UniqueAppHandler::newInstance (this=0xa0f8c20, asn_id=..., args=...) at ../../kontactinterface/uniqueapphandler.cpp:129 #9 0xb757b874 in KontactInterface::UniqueAppHandler::qt_metacall (this=0xa0f8c20, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfe697ec) at ./uniqueapphandler.moc:79 #10 0xb5471b34 in QDBusConnectionPrivate::deliverCall (this=0x9d61d60, object=0xa0f8c20, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:904 #11 0xb5472ddf in QDBusConnectionPrivate::activateCall (this=0x9d61d60, object=0xa0f8c20, flags=272, msg=...) at qdbusintegrator.cpp:809 #12 0xb54735ac in QDBusConnectionPrivate::activateObject (this=0x9d61d60, node=..., msg=..., pathStartPos=21) at qdbusintegrator.cpp:1383 #13 0xb5473b1a in QDBusActivateObjectEvent::placeMetaCall (this=0x9ecb4b0) at qdbusintegrator.cpp:1477 #14 0xb6ca43fe in QObject::event (this=0xa0f8c20, e=0x9ecb4b0) at kernel/qobject.cpp:1248 #15 0xb61e34dc in QApplicationPrivate::notify_helper (this=0x9d6ad90, receiver=0xa0f8c20, e=0x9ecb4b0) at kernel/qapplication.cpp:4300 #16 0xb61ea05e in QApplication::notify (this=0xbfe6a204, receiver=0xa0f8c20, e=0x9ecb4b0) at kernel/qapplication.cpp:3704 #17 0xb71e4f2a in KApplication::notify (this=0xbfe6a204, receiver=0xa0f8c20, event=0x9ecb4b0) at ../../kdeui/kernel/kapplication.cpp:302 #18 0xb6c93a3b in QCoreApplication::notifyInternal (this=0xbfe6a204, receiver=0xa0f8c20, event=0x9ecb4b0) at kernel/qcoreapplication.cpp:704 #19 0xb6c96473 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9d4a4e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9d4a4e0) at kernel/qcoreapplication.cpp:1345 #21 0xb6c965dd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1238 #22 0xb6cbfadf in QCoreApplication::sendPostedEvents (s=0x9d70710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #23 postEventSourceDispatch (s=0x9d70710) at kernel/qeventdispatcher_glib.cpp:276 #24 0xb410a5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #25 0xb410e2d8 in ?? () from /lib/libglib-2.0.so.0 #26 0xb410e4b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #27 0xb6cbf5d5 in QEventDispatcherGlib::processEvents (this=0x9d4a070, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #28 0xb62a3135 in QGuiEventDispatcherGlib::processEvents (this=0x9d4a070, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #29 0xb6c92059 in QEventLoop::processEvents (this=0xbfe6a164, flags=) at kernel/qeventloop.cpp:149 #30 0xb6c924aa in QEventLoop::exec (this=0xbfe6a164, flags=...) at kernel/qeventloop.cpp:201 #31 0xb6c9669f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #32 0xb61e3577 in QAppli
[Bug 249229] messagelist previews are not updated after creating a new akonadi db
https://bugs.kde.org/show_bug.cgi?id=249229 --- Comment #1 from Christophe Giboudeaux 2010-08-27 15:10:50 --- Created an attachment (id=51021) --> (http://bugs.kde.org/attachment.cgi?id=51021) Akonadiconsole rdf tab for the same message -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249229] New: messagelist previews are not updated after creating a new akonadi db
https://bugs.kde.org/show_bug.cgi?id=249229 Summary: messagelist previews are not updated after creating a new akonadi db Product: Akonadi Version: unspecified Platform: Compiled Sources OS/Version: Linux Status: NEW Severity: normal Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: to...@kde.org ReportedBy: cgiboude...@gmail.com CC: vkra...@kde.org, kdepim-bugs@kde.org Created an attachment (id=51019) --> (http://bugs.kde.org/attachment.cgi?id=51019) Bugged KMail preview. Using trunk. Testcase: - Start Akonadi from scratch, add a mail account, let akonadi download and index the messages, - Stop Akonadi, wipe the db and settings, - Create a new akonadi db - Add a different mail account and let Akonadi download the messages. Here's the issue: The messages preview in KMail (or the RDF tab in akonadiconsole) show the preview from the previous Akonadi data. See the attached screenshot. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 248554] Regression: Imap folder changes are not displayed (no longer synchronized?)
https://bugs.kde.org/show_bug.cgi?id=248554 Volker Krause changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution||FIXED --- Comment #12 from Volker Krause 2010-08-27 15:05:33 --- SVN commit 1168799 by vkrause: Disable conflict detection in ItemSync for now. We currently have no way yet to handle LR conflicts, and there are cases where this can actually dead-lock the ItemSync/TransactionSequence combination. BUG: 248554 M +1 -0 itemsync.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1168799 -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 --- Comment #150 from Edwin Schepers 2010-08-27 15:02:05 --- Last time, it was april when I picked up this issue again. Compiling the kde modules was impossible to me then because my system crashed because of it (https://bugzilla.redhat.com/show_bug.cgi?id=580208). When I find the time, I'll install a new fedora and give it another try. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 226527] Reply does not open composer window over NX connections
https://bugs.kde.org/show_bug.cgi?id=226527 Tristan Miller changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #4 from Tristan Miller 2010-08-27 12:39:21 --- Can no longer reproduce with KDE 4.5.0 and nxclient 3.4.0. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86629] commandline option --attach should look for files in actual directory
https://bugs.kde.org/show_bug.cgi?id=86629 Tristan Miller changed: What|Removed |Added CC||psychon...@nothingisreal.co ||m --- Comment #2 from Tristan Miller 2010-08-27 12:45:01 --- Confirming bug still exists with KMail 1.13.5 (KDE 4.5.0). -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 190824] Can't launch Configure Kontact dialog more than once
https://bugs.kde.org/show_bug.cgi?id=190824 Tristan Miller changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #7 from Tristan Miller 2010-08-27 12:40:28 --- Can no longer reproduce with KDE 4.5.0 and nxclient 3.4.0. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Denis Prost changed: What|Removed |Added CC||denis.pr...@wanadoo.fr --- Comment #149 from Denis Prost 2010-08-27 11:02:03 --- me too -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 86423] Ability To Reply To HTML Email With Same HTML Format As It Was Received
https://bugs.kde.org/show_bug.cgi?id=86423 Jakub Benda changed: What|Removed |Added CC||alban...@atlas.cz --- Comment #148 from Jakub Benda 2010-08-27 10:59:19 --- I am missing this feature, too. And I would happily join with my $40 as well if there was a chance it would change something. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249162] KDE PIM std.ics on computer 1 crashed when edited from computer 2
https://bugs.kde.org/show_bug.cgi?id=249162 Pino Toscano changed: What|Removed |Added Component|general |general AssignedTo|kdepim-bugs@kde.org |korganizer-de...@kde.org Product|kontact |korganizer -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249201] New: won't send if key isn't fully trusted
https://bugs.kde.org/show_bug.cgi?id=249201 Summary: won't send if key isn't fully trusted Product: kmail Version: 1.13.5 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: tipos...@tiscali.it Version: 1.13.5 (using KDE 4.4.5) OS:Linux Kmail won't send email if a not fully trusted encryption key is selected. I can (could) approve the warning, but not sending the email at all is just annoying and brings to mark all the keys to trusted, just to be able to send emails to their owners. Yes, after the warning asking if i want to continue, even if i continue the email won't be send anyway. Reproducible: Didn't try OS: Linux (x86_64) release 2.6.34.5-galatea Compiler: cc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249198] After initial installation, "write new mail" dialog accessible, although no account available
https://bugs.kde.org/show_bug.cgi?id=249198 --- Comment #1 from Felix Wolfsteller 2010-08-27 10:23:06 --- It seemed to me that an account wizard popped up after closing kmail via "Quit" in flap. It might however also just have taken so long to start it in the first place. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249198] New: After initial installation, "write new mail" dialog accessible, although no account available
https://bugs.kde.org/show_bug.cgi?id=249198
Summary: After initial installation, "write new mail" dialog
accessible, although no account available
Product: KMail Mobile
Version: unspecified
Platform: Maemo 5
OS/Version: Linux
Status: NEW
Keywords: komo3
Severity: minor
Priority: NOR
Component: general
AssignedTo: kdepim-bugs@kde.org
ReportedBy: felix.wolfstel...@intevation.de
After a fresh install of Version 4:4.5~20100820.1165966-1maemo1.1167016 , KMail
Mobile offers "Write new Mail", although I have not yet created an account
("Identity").
The "selected" account in the "New mail" dialog appears as "Unknown".
Possible solutions:
- Disable the button when none account yet specified.
- Notify that the identity lacks information when attempting to send the mail.
- Force identity definition on initial startup.
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 248381] Spellcheck while typing does not work
https://bugs.kde.org/show_bug.cgi?id=248381 Rainer Merz changed: What|Removed |Added CC||rainer.m...@ipe.uni-stuttga ||rt.de --- Comment #1 from Rainer Merz 2010-08-27 10:14:58 --- I have absolutely the same problem, if there is an solution it would help very mutch -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249197] New: attachment not saved
https://bugs.kde.org/show_bug.cgi?id=249197 Summary: attachment not saved Product: kmail Version: 1.13.5 Platform: Unlisted Binaries OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: tipos...@tiscali.it Version: 1.13.5 (using KDE 4.4.5) OS:Linux I got an email and tried to view and save it's attachment. The view window was EMPTY and the saved file had 0 size. This is the email (removed almost all the headers) Date: Fri, 27 Aug 2010 10:01:45 + User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.7) Gecko/20100813 Thunderbird/3.1.1 MIME-Version: 1.0 Subject: Re: wifi X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="030906030202060509050501" X-Length: 6651 X-UID: 5218 This is a multi-part message in MIME format. --030906030202060509050501 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Il 26/08/2010 08:54, Salvo 'LtWorf' Tomaselli ha scritto: non si puo' aprire ne questo e quello dopo --030906030202060509050501 Content-Type: application/pgp-keys; name="0x598DC43C.asc" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="0x598DC43C.asc" -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2.0.15 (GNU/Linux) mQSuBExhyn4RDACE3OaOWv6jftN9tXmYceo1K2LwtqFOkHJfTFUtpoqYYIuPn8kK ieUP2uvBsMRS45+TSaFtFX1IU7Ki3Yu2Suo8b2kKnZIIeBcopaWtMoo/SNf/wpGv zq8f3V9Sl6iTtbd+2c4BBRop3YYRojYTfjD0IA+aE9Gozk46CVdYi63qUa95EKdJ CELoYG+pKkSNrlmq9wzla7huBLCxpm9ujIsz6J6rhxRxsUyr0Pg5nIyRXbZ4ZNO3 K56oyMeAKug0k6mCtseChS1Y9rjZc24dRNwhrTdLqgpKb+MPDMREE0h5P03OMULN bSLJ3cx5VVtKe3OAwOEAVqSWbMNIK2zXNpm6kM+Qa0uQBS8FU7BSdWcM4YglNTQs i9aFz9qv93phh0C+kYWoECbcKvrGKsZ9CMN6LX92e03LMg70xIunXRNGZUo2gX70 Z7wP1Tm9dc1CVsCK9PXTIAo10Wc5lh7HYxUvxJ/+sKZ0w+iAg6VhXRKXN6+0zXmi egR0CWN4u4DwJQcBAPRhI9kHX/8Yh9aewd+KE3VAD0ssnJXz7HoMmdX72ld9C/4r EuMw91KbLE/RepRdMT8HbSFOiLMmTzqRYU9z1H0FTBlqJb951ffBKjcoXZM3NZNX 8yrQTRliRwzHWMLsm+jm9jNKI16gwu7nNnF+AWLtxLCiyW/pO5edNZgarqZneIfY 3l7S1tqV+al62rSzeTD1VzHRAyMz8/9JQPX/bShNKcS4CzKIIcOvyICm0efafgsF KzsT8jyCcx2aNzlXm2AT1ATuxaIitnN61Xa/xakbFr9qDv7i6q54kbIEpVW/Vwoy zgQ6LTjGsAs1xv6s+0Y5xy1Qc+3fWNn1ZnfBELAVvz9ayAQElpvTJMC2yVKp97mV b5Y5vvqZoIqy84TlmcM6qAFEJ+WZpgR+6H7rd0MSP4o1xUSADTJi+Ep1O3TZ+40S P4hhAZNDVULbw1BTFhs/gkNxRfUnKDZN6KYCYgCkF0i7jVAr8K/6ja7wfiK0DWUs 7bDDOzwMn2+zFLKanOYDnb9UG/lJPR09caygSYNkv4XDV8VeHSjg4qBRzbpJCrYL /jzNvR8gUk+3EFwT7HnDlpPWX2M+QlDnkurnpq4yaYl8h42sek+hQASLctx/DvdQ cBn5HaFZS88/H8f/ho+s6CBiJILuWAw3OXI7gfd+JNx9zuIp9hoSVJ0uV8D5YmHV jrxy9aEOBYcCzkhHuz/lkLsUOGUF1eorfd/uPU54DhvoH3mZPZ7tsLDOIqFOKCpk RteACCb03rwHUb1R5YWeCgjklvFNIQC0U08I7TOTeQz20AysedcmE4wtxNe4z0xT NrNduajWhCAS6ZZAWgQVemO/J7JyACW0lCvebg9NQr9n6wB9N+I3RA3eRB2lHpIi LZPAnsW8dO1DAf+2X4bWhVPpZ+k1m5HvgvQRNIjfA1+y4sHx4gH3JTmlHQRHpkzZ Lre4b6LW91H6EiU8SuU3v3piNAnwqiwpNCorTmXVTTEc4HZDh8WAC0m3EquVB7ux bkadmj/Qhk17FXAD+aqKnDyxuLbRD16RSG6SEMqDUx66EwI90tzoNigp9kf2l+XT bbQ0UmhvZyBGZXJuYW5kbyAoUmlnaHQgSGFuZCBvZiBHb2QpIDxyaG9nMDlAZ21h aWwuY29tPoh9BBMRCAAlAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAUCTGHn wgIZAQAKCRCheVeBWY3EPKqCAQC7VQfWhbOSOANQDNOEyewZLrx84jXzz6PZA8hO bLAR8QEAuCUmebmi4Z4GlxE+W4m8WFgb2hM6WqQUtk0PW4CeVHO5Aw0ETGHKfhAM AM30FHn1bZd8o54nHO8RxEVAoGwVTLtexz/DN8NnIKrwJEMDfbSyFsxmeianU7a2 /y/CIyTgnJcGGRhhAjnVCyPgoW9Zkr8RiK5EI1+2rqKcyGdDYyM/8//2Lf0Mxgpf 0Bs4BvxxfQGVRAxaorwaRAHQ7Q2JEHXp7d3Jq+CHVoe1j/dNjojNwj1XGop3idwC NWl9qK2z73HCFobhrSFPBhAYqRhbhgrD5TKd19gcxind87gWBF8Ny8ubP+rCfNXd +FKOQDWykh9xBexLVIkZm/PYLBh4fQVY1uBWTdZE88mk507ncr2vLFQOX63+iCuJ 6axcD16uprJPxlFYdCOG3HyQG4IQ5ZgUASruw7Zxz3LA5bEi8oeMMPADc72VDSiw Tqu9HciXbxTFfq/KjczB+IZuC9HszAvgaMijhvr3BYeM8AEne2uAUYz949T/TH0N JtlgoLXiKn1btWiEPUDqZhF2YZOEvkc5p8+F01g2HcFtAlMcy/oqSEGWH0VwJhh7 hwAFEwwArW0ELHYA8Owf9tVwegvJZYbwidejIVpEBA2NFdWPXBHokQ1H89Pk7384 rDrdLZ0/2sIMMa67AFW5ynbD42TJc3KyyuAtGGykvuGkYEbq1b6MyCIuHkT7mQXY 7cqtnmS3a2Db57Pqxi87HXRr+avXLHdZMCb2DZZgvCfHauCaFEn+Gj+GpanYpD8n o7uDow27DWVJTuT0kzSjB61Bo2lsq5cFHWg3HfnPYZCa+c/DPfm0/oGT4dgCD87s zO91bwfJZNJRx35xenlXGWPot7fqWwgXO3+Ti3RwJRLedO7phAKtSNqxgevgLeKr AKBkNkCTASXNqFwBLDMZACJVic2ZreflYNjKpL9jTOGJ9ft+F3ZtOy4Bbg1Vi4fQ 9c9yeYuNuqJYAWcyJwAu6yRjU23u0PQn07oFe4egPCiLnUbgQ8i5FeJOUiLN1Ceg YIrhnvvYzy4sKqP0kimnZpRyxzCApqx2Qy0OF2DQapZb+H7bNFnI0fMJuGApPSgX pc1qKRMmiGEEGBEIAAkFAkxhyn4CGwwACgkQoXlXgVmNxDxXXwEAieSOJWOiUXCT 6RJeYjMkOWg9uUxoGlst4ux82+nVg3gA/ivhByI040Nq4FO4ZpRSg/UYpqA7wWCU 7sjyp7U0PZcG =4BNv -END PGP PUBLIC KEY BLOCK- --030906030202060509050501-- Reproducible: Didn't try OS: Linux (x86_64) release 2.6.34.5-galatea Compiler: cc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo
[Bug 249195] New: Kmail crash when viewing mail
https://bugs.kde.org/show_bug.cgi?id=249195 Summary: Kmail crash when viewing mail Product: kontact Version: 4.4.5 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: dre...@iem.uni-due.de Application: kontact (4.4.5) KDE Platform Version: 4.4.5 (KDE 4.4.5) Qt Version: 4.6.3 Operating System: Linux 2.6.32-24-generic x86_64 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: Kmail crashed when clicking on a mail in a lokal mbox folder. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 1 (Thread 0x7f6d1c632780 (LWP 8069))] Thread 2 (Thread 0x7f6cf3fff710 (LWP 8088)): #0 0x7f6d19704f83 in *__GI___poll (fds=, nfds=, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7f6d122334a9 in g_main_context_poll (context=0x7f6cf4000ed0, block=, dispatch=, self=) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2904 #2 g_main_context_iterate (context=0x7f6cf4000ed0, block=, dispatch=, self=) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2586 #3 0x7f6d122338fc in IA__g_main_context_iteration (context=0x7f6cf4000ed0, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654 #4 0x7f6d1aaf0406 in QEventDispatcherGlib::processEvents (this=0x2683f40, flags=) at kernel/qeventdispatcher_glib.cpp:414 #5 0x7f6d1aac56c2 in QEventLoop::processEvents (this=, flags=) at kernel/qeventloop.cpp:149 #6 0x7f6d1aac5a9c in QEventLoop::exec (this=0x7f6cf3ffed90, flags=) at kernel/qeventloop.cpp:201 #7 0x7f6d1a9d48db in QThread::exec (this=) at thread/qthread.cpp:487 #8 0x7f6d1aaa5dd8 in QInotifyFileSystemWatcherEngine::run (this=0x2683e60) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x7f6d1a9d6f95 in QThreadPrivate::start (arg=0x2683e60) at thread/qthread_unix.cpp:248 #10 0x7f6d147aa9ca in start_thread (arg=) at pthread_create.c:300 #11 0x7f6d197116fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 1 (Thread 0x7f6d1c632780 (LWP 8069)): [KCrash Handler] #5 QBasicAtomicInt::deref (this=0x539fad0, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:133 #6 QString::operator= (this=0x539fad0, other=...) at tools/qstring.cpp:1281 #7 0x7f6d1bf7b44d in KPIM::ProgressItem::setStatus (this=0x539fab0, v=...) at ../../libkdepim/progressmanager.cpp:118 #8 0x7f6d027cde21 in KMail::BackupJob::finish (this=0x539d030) at ../../kmail/backupjob.cpp:172 #9 0x7f6d027cfee5 in KMail::BackupJob::archiveNextFolder (this=0x539fad0) at ../../kmail/backupjob.cpp:388 #10 0x7f6d027ced76 in KMail::BackupJob::archiveNextMessage (this=0x539d030) at ../../kmail/backupjob.cpp:208 #11 0x7f6d027d0d84 in KMail::BackupJob::processCurrentMessage (this=0x539d030) at ../../kmail/backupjob.cpp:341 #12 0x7f6d027d194c in KMail::BackupJob::qt_metacall (this=0x539d030, _c=QMetaObject::InvokeMetaMethod, _id=, _a=0x7fff87465f00) at ./backupjob.moc:80 #13 0x7f6d1aada036 in QMetaObject::activate (sender=0x39afee0, m=, local_signal_index=, argv=0x1) at kernel/qobject.cpp:3295 #14 0x7f6d1aae14ef in QSingleShotTimer::timerEvent (this=0x39afee0) at kernel/qtimer.cpp:308 #15 0x7f6d1aad6893 in QObject::event (this=0x39afee0, e=0x7fff8740) at kernel/qobject.cpp:1212 #16 0x7f6d19e80c0c in QApplicationPrivate::notify_helper (this=0x15aae30, receiver=0x39afee0, e=0x7fff8740) at kernel/qapplication.cpp:4302 #17 0x7f6d19e870eb in QApplication::notify (this=0x7fff874669c0, receiver=0x39afee0, e=0x7fff8740) at kernel/qapplication.cpp:4185 #18 0x7f6d1b4b0a16 in KApplication::notify (this=0x7fff874669c0, receiver=0x39afee0, event=0x7fff8740) at ../../kdeui/kernel/kapplication.cpp:302 #19 0x7f6d1aac6d9c in QCoreApplication::notifyInternal (this=0x7fff874669c0, receiver=0x39afee0, event=0x7fff8740) at kernel/qcoreapplication.cpp:726 #20 0x7f6d1aaf3ba2 in QCoreApplication::sendEvent (this=0x159ec60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #21 QTimerInfoList::activateTimers (this=0x159ec60) at kernel/qeventdispatcher_unix.cpp:603 #22 0x7f6d1aaf06c4 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:184 #23 0x7f6d1222f8c2 in g_main_dispatch (context=0x1595480) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:1960 #24 IA__g_main_context_dispatch (context=0x1595480) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2513 #25 0x7f6d12233748 in g_main_context_iterate (context=0x1595480, block=, dispatch=, self=) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2591 #26 0x7f6d122338fc in IA__g_main_context_iteration (context=0x1595480, may_block=1) at /build/buildd/glib2.0-2.24.1/glib/gmain.c:2654 #27 0x7f6d1aaf03b3 in QEventDispatcherGlib::processEvents (this=0x1568d70, fl
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #8 from Marcus Hardt 2010-08-27 09:58:52 --- Created an attachment (id=51009) --> (http://bugs.kde.org/attachment.cgi?id=51009) Processes after ssh connection from pc to notebook was terminated -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #9 from Marcus Hardt 2010-08-27 09:59:13 --- Good news: I did manage to reproduce the problem. 01: start kmail on notebook 02: ssh into notebook from pc 03: run "killall kmail" in ssh session, killing ssh on notebook. (Processes see attached 01*.txt) 04: start kmail in ssh session (Processes see attached 01*.txt) 05: check mail => invokes kwallet on the pc (!) 06: unlock wallet 07: check mail, send mail works fine now 08: terminate kmail (using c-q) 09: process that are running now on notebook see attached 03*.txt Most noteworthy: Akonadi processes are still there 10: back at the notebook's desktop: start kmail 11: send an email: still works 12: terminate the ssh session (and also the wallet) 13: sending emails will freeze kmail from now on -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #7 from Marcus Hardt 2010-08-27 09:57:56 --- Created an attachment (id=51008) --> (http://bugs.kde.org/attachment.cgi?id=51008) processes running on notebook after kmail was terminated -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #6 from Marcus Hardt 2010-08-27 09:57:10 --- Created an attachment (id=51007) --> (http://bugs.kde.org/attachment.cgi?id=51007) Processes running on notebook after kmail was started on pc -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 241081] KMail freezes when trying to send email
https://bugs.kde.org/show_bug.cgi?id=241081 --- Comment #5 from Marcus Hardt 2010-08-27 09:56:11 --- Created an attachment (id=51005) --> (http://bugs.kde.org/attachment.cgi?id=51005) Processes after kmail was killed within ssh session initiated from pc to notebook -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 246889] sending mails failed
https://bugs.kde.org/show_bug.cgi?id=246889 --- Comment #10 from Bernhard E. Reiter 2010-08-27 09:39:22 --- Sabine, oh, you are right about the tag number, I somehow overlooked it. Sorry. :( Did you see the reason meanwhile why your emails were not transported? -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Bug 249100] akonadi kolab/imap: double entry after edit
https://bugs.kde.org/show_bug.cgi?id=249100 --- Comment #1 from Raimar Sandner 2010-08-27 08:57:13 --- I have to add that in some rare events this bug is not triggered and the edit is handled correctly. -- Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
