[Bug 290247] New: Nepomuk email feeder crashed on logout
https://bugs.kde.org/show_bug.cgi?id=290247 Summary: Nepomuk email feeder crashed on logout Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: kdepim-bugs@kde.org ReportedBy: kepl...@cmc.pl CC: vkra...@kde.org Application: akonadi_nepomuk_email_feeder (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-14-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: KMail2 (Nepomuk email feeder) crashed when logging out of a KDE session. -- Backtrace: Application: Obsługa e-maili dla Nepomuka (akonadi_nepomuk_email_feeder), signal: Aborted [KCrash Handler] #7 0x00c32416 in __kernel_vsyscall () #8 0x034d8c8f in raise () from /lib/i386-linux-gnu/libc.so.6 #9 0x034dc2b5 in abort () from /lib/i386-linux-gnu/libc.so.6 #10 0x0350edfc in ?? () from /lib/i386-linux-gnu/libc.so.6 #11 0x03519bc2 in ?? () from /lib/i386-linux-gnu/libc.so.6 #12 0x0351bcf3 in ?? () from /lib/i386-linux-gnu/libc.so.6 #13 0x0351d498 in malloc () from /lib/i386-linux-gnu/libc.so.6 #14 0x08715e0b in qMalloc (size=12) at global/qmalloc.cpp:55 #15 0x0873aa53 in QHashData::allocateNode (this=0x8c44750, nodeAlign=4) at tools/qhash.cpp:175 #16 0x00a7cec4 in createNode (anextNode=optimized out, akey=@0x9c16a34, ah=162677592, this=optimized out, avalue=optimized out) at /usr/include/qt4/QtCore/qhash.h:541 #17 insert (avalue=optimized out, this=0xbf8e6110, akey=@0x9c16a34) at /usr/include/qt4/QtCore/qhash.h:761 #18 insert (value=@0x9c16a34, this=0xbf8e6110) at /usr/include/qt4/QtCore/qset.h:176 #19 QListNepomuk::ResourceData*::toSet (this=0xbf8e610c) at /usr/include/qt4/QtCore/qset.h:309 #20 0x00a7aa8b in Nepomuk::ResourceManagerPrivate::cleanupCache (this=0x8babaf8, num=-1) at ../../nepomuk/core/resourcemanager.cpp:185 #21 0x00a7af3a in Nepomuk::ResourceManager::clearCache (this=0x8b9db90) at ../../nepomuk/core/resourcemanager.cpp:461 #22 0x00a7af68 in Nepomuk::ResourceManager::~ResourceManager (this=0x8b9db90, __in_chrg=optimized out) at ../../nepomuk/core/resourcemanager.cpp:294 #23 0x00a7b062 in Nepomuk::ResourceManager::~ResourceManager (this=0x8b9db90, __in_chrg=optimized out) at ../../nepomuk/core/resourcemanager.cpp:302 #24 0x0882b841 in QObjectPrivate::deleteChildren (this=0x8aa5980) at kernel/qobject.cpp:1955 #25 0x08830439 in QObject::~QObject (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qobject.cpp:946 #26 0x0881a648 in QCoreApplication::~QCoreApplication (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qcoreapplication.cpp:671 #27 0x06797943 in QApplication::~QApplication (this=0xbf8e62e0, __in_chrg=optimized out) at kernel/qapplication.cpp:1093 #28 0x007e4668 in KApplication::~KApplication (this=0xbf8e62e0, __in_chrg=optimized out) at ../../kdeui/kernel/kapplication.cpp:894 #29 0x080553f1 in Akonadi::AgentBase::initAkonadi::NepomukEMailFeeder (argc=3, argv=0xbf8e63b4) at /usr/include/akonadi/agentbase.h:334 #30 0x0805307b in main (argc=3, argv=0xbf8e63b4) at ../../nepomuk_email_feeder/nepomukemailfeeder.cpp:133 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 290249] New: address label printing on sticky labels
https://bugs.kde.org/show_bug.cgi?id=290249 Summary: address label printing on sticky labels Product: kaddressbook Version: unspecified Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: printing AssignedTo: kdepim-bugs@kde.org ReportedBy: s.oosth...@xs4all.nl CC: to...@kde.org Version: unspecified (using KDE 4.7.3) OS:Linux In all the time I've used Linux on the desktop (since 1996) I've sometimes tried to print labels from a linux program and particularly from the kaddressbook database of addresses, but it's always (on the rare occasions I need it) so hard to do it becomes an obstacle and the temptation to use a paper addressbook comes up again. Mostly I have experience with kbarcode to do this, but it's a horror to use! Reproducible: Didn't try Expected Results: I would like kaddressbook (because that's where I keep my addresses) to have an option to print addresses on labels. Apparently this is a feature that is either hard to implement or no developer has ever stumbled upon the need to get this done properly ;-) There are a couple of steps I'd expect: - selecting which addresses to print - a way to select which fields to print and approximately where on the label (order and row in printed form) - a way to describe the layout of the label paper (nr of rows/columns and offsets) (I don't believe in kbarcode's method of choosing from a huge set of predifined label sheets/brands) - perhaps font settings - Optionally repeating one address many times or each address once. I can imagine several ways to implement this, one is to include it into kaddressbook's print feature. Another is to create a separate module for kde/qt to print on labels and kaddressbook to interface with this. This should make it easier to create other programs to print stuff on labels, but perhaps more work? -- 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 288364] Retrieving Folder Contents hanging without showing content
https://bugs.kde.org/show_bug.cgi?id=288364 abrah...@acm.org changed: What|Removed |Added CC||abrah...@acm.org --- Comment #12 from abrahams acm org 2011-12-31 13:06:58 --- Similar problem here with KDE/kmail 4.73 -- according to Synaptic, the latest available for my Kubuntu system. I can clear the Waiting message sometimes by moving to another message in the inbox, but something is clearly very wrong here. A recent update is probably responsible, since I never saw this message until recently. -- 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 290253] New: kMail ignores configured hostname for message id generation
https://bugs.kde.org/show_bug.cgi?id=290253 Summary: kMail ignores configured hostname for message id generation Product: kmail2 Version: 4.7 Platform: Ubuntu Packages OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: kdeb...@customcdrom.de Version: 4.7 (using Devel) OS:Linux The generated message ID uses only my local hostname without any domain part, although I configured a FQDN in the message send settings dialog. Reproducible: Always Steps to Reproduce: Manually configure a FQDN in the SMTP server settings dialog. Actual Results: A message ID containing only the local hostname is generated. Expected Results: A message ID containing the configured FQDN should be generated. -- 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 289295] MySQL errors when creating the akonadi database
https://bugs.kde.org/show_bug.cgi?id=289295 Michael Bach pha...@gmail.com changed: What|Removed |Added CC||pha...@gmail.com --- Comment #3 from Michael Bach phaebz gmail com 2011-12-31 13:39:07 --- I can confirm this. Version: 1.6.2 OS: Arch Linux MySQL: 5.5.19 I was noticing this only yesterday and I think it is due to a MySQL upgrade along the way. I am getting a Warning and another error before the `Native table 'performance_schema'' error: [Warning] Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist [ERROR] Native table 'performance_schema'.'events_waits_current' has the wrong structure [ERROR] Native table 'performance_schema'.'events_waits_history' has the wrong structure I was thinking of fixing the db manually using the tips on the boards, but refrained. -- 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 290259] New: Kontact/KMail crash on filtering messages
https://bugs.kde.org/show_bug.cgi?id=290259 Summary: Kontact/KMail crash on filtering messages Product: kontact Version: unspecified Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general AssignedTo: kdepim-bugs@kde.org ReportedBy: andreas.karrenba...@uni-konstanz.de Application: kontact (4.7.4) KDE Platform Version: 4.7.4 (4.7.4) release 11 Qt Version: 4.7.4 Operating System: Linux 3.1.1-48-desktop x86_64 Distribution: openSUSE 11.4 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I selected about 3500 messages and applied my mail filters on them. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7fd34f32d760 (LWP 2998))] Thread 3 (Thread 0x7fd3372e2700 (LWP 3015)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7fd34bbc0694 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fd3472f6a3f in start_thread (arg=0x7fd3372e2700) at pthread_create.c:297 #3 0x7fd34c8f166d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #4 0x in ?? () Thread 2 (Thread 0x7fd3369c9700 (LWP 3016)): #0 0x7fff651fe8b6 in ?? () #1 0x7fd3369c8b80 in ?? () #2 0x7fd3462362b3 in clock_gettime (clock_id=1, tp=0x7fd3369c8b40) at ../sysdeps/unix/clock_gettime.c:100 #3 0x7fd34dc07cf2 in do_gettime () at tools/qelapsedtimer_unix.cpp:123 #4 qt_gettime () at tools/qelapsedtimer_unix.cpp:140 #5 0x7fd34dccaffd in QTimerInfoList::updateCurrentTime (this=0x648370) at kernel/qeventdispatcher_unix.cpp:339 #6 0x7fd34dccb375 in QTimerInfoList::timerWait (this=0x648370, tm=...) at kernel/qeventdispatcher_unix.cpp:442 #7 0x7fd34dcc9e3c in timerSourcePrepareHelper (src=value optimized out, timeout=0x7fd3369c8c8c) at kernel/qeventdispatcher_glib.cpp:136 #8 0x7fd345f85087 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #9 0x7fd345f85fa9 in ?? () from /lib64/libglib-2.0.so.0 #10 0x7fd345f86650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #11 0x7fd34dcca636 in QEventDispatcherGlib::processEvents (this=0x647850, flags=value optimized out) at kernel/qeventdispatcher_glib.cpp:424 #12 0x7fd34dc9ec22 in QEventLoop::processEvents (this=value optimized out, flags=...) at kernel/qeventloop.cpp:149 #13 0x7fd34dc9ee35 in QEventLoop::exec (this=0x7fd3369c8e20, flags=...) at kernel/qeventloop.cpp:201 #14 0x7fd34dbb3be4 in QThread::exec (this=value optimized out) at thread/qthread.cpp:498 #15 0x7fd34dbb64d5 in QThreadPrivate::start (arg=0x63fcd0) at thread/qthread_unix.cpp:331 #16 0x7fd3472f6a3f in start_thread (arg=0x7fd3369c9700) at pthread_create.c:297 #17 0x7fd34c8f166d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #18 0x in ?? () Thread 1 (Thread 0x7fd34f32d760 (LWP 2998)): [KCrash Handler] #6 count (sender=0xc7d6360, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff6516e100) at ../../src/corelib/tools/qvector.h:246 #7 QMetaObject::activate (sender=0xc7d6360, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff6516e100) at kernel/qobject.cpp:3235 #8 0x7fd34a1dba10 in KPIM::ProgressItem::progressItemProgress (this=value optimized out, _t1=0xc7d6360, _t2=165) at /usr/src/debug/kdepim-4.7.4/build/libkdepim/progressmanager.moc:114 #9 0x7fd2f22e36df in updateProgress (this=0xd2eb80, items=value optimized out) at /usr/src/debug/kdepim-4.7.4/libkdepim/progressmanager.h:158 #10 MailCommon::FilterManager::Private::slotItemsFetchedForFilter (this=0xd2eb80, items=value optimized out) at /usr/src/debug/kdepim-4.7.4/mailcommon/filtermanager.cpp:150 #11 0x7fd2f22e3dc2 in MailCommon::FilterManager::qt_metacall (this=0xe931d0, _c=QMetaObject::InvokeMetaMethod, _id=value optimized out, _a=0x7fff6516e3f0) at /usr/src/debug/kdepim-4.7.4/build/mailcommon/filtermanager.moc:103 #12 0x7fd34dcb3e8f in QMetaObject::activate (sender=0x10444850, m=value optimized out, local_signal_index=value optimized out, argv=0x7fff6516e3f0) at kernel/qobject.cpp:3287 #13 0x7fd3496dd692 in Akonadi::ItemFetchJob::itemsReceived (this=value optimized out, _t1=value optimized out) at /usr/src/debug/kdepimlibs-4.7.4/build/akonadi/itemfetchjob.moc:92 #14 0x7fd34976333b in timeout (this=value optimized out, _c=value optimized out, _id=2, _a=0x7fff6516e4b0) at /usr/src/debug/kdepimlibs-4.7.4/akonadi/itemfetchjob.cpp:71 #15 Akonadi::ItemFetchJob::qt_metacall (this=value optimized out, _c=value optimized out, _id=2, _a=0x7fff6516e4b0) at /usr/src/debug/kdepimlibs-4.7.4/build/akonadi/itemfetchjob.moc:80 #16 0x7fd34dcb3e8f in QMetaObject::activate (sender=0xde8cd70, m=value optimized out,
[Bug 290260] New: Mail filter agent crashed
https://bugs.kde.org/show_bug.cgi?id=290260 Summary: Mail filter agent crashed Product: Akonadi Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Mail Filter Agent AssignedTo: kdepim-bugs@kde.org ReportedBy: szots...@gmail.com Application: akonadi_mailfilter_agent (4.7) KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) release 3 Qt Version: 4.8.0 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - W hat I was doing when the application crashed: I was logging off KDE when the crash dialogue appeared. -- Backtrace: Application: Mail Filter Agent (akonadi_mailfilter_agent), signal: Segmentation fault [KCrash Handler] #6 0x7f4da75e57ca in lockInline (this=0x90c878) at /usr/include/QtCore/qmutex.h:187 #7 QMutexLocker (m=0x90c878, this=synthetic pointer) at /usr/include/QtCore/qmutex.h:109 #8 Soprano::Client::SocketHandler::~SocketHandler (this=0x90fe30, __in_chrg=optimized out) at /usr/src/debug/soprano-2.7.4/client/clientconnection.cpp:58 #9 0x7f4da75e5909 in Soprano::Client::SocketHandler::~SocketHandler (this=0x90fe30, __in_chrg=optimized out) at /usr/src/debug/soprano-2.7.4/client/clientconnection.cpp:61 #10 0x7f4db56d812d in QThreadStorageData::set (this=0x9425e0, p=0x942bb0) at thread/qthreadstorage.cpp:165 #11 0x7f4da75e3290 in qThreadStorage_setLocalDataSoprano::Client::SocketHandler (d=optimized out, t=optimized out) at /usr/include/QtCore/qthreadstorage.h:92 #12 setLocalData (t=0x942bb0, this=optimized out) at /usr/include/QtCore/qthreadstorage.h:155 #13 Soprano::Client::ClientConnection::socketForCurrentThread (this=0x926a40) at /usr/src/debug/soprano-2.7.4/client/clientconnection.cpp:95 #14 0x7f4da75e3309 in Soprano::Client::ClientConnection::connectInCurrentThread (this=optimized out) at /usr/src/debug/soprano-2.7.4/client/clientconnection.cpp:800 #15 0x7f4da75e28ca in Soprano::Client::LocalSocketClient::connect (this=0x734038, name=...) at /usr/src/debug/soprano-2.7.4/client/localsocketclient.cpp:141 #16 0x7f4db11eab41 in init (forced=true, this=0x734010) at /usr/src/debug/kdelibs-4.7.95/nepomuk/core/nepomukmainmodel.cpp:102 #17 Nepomuk::MainModel::init (this=0x733d30) at /usr/src/debug/kdelibs-4.7.95/nepomuk/core/nepomukmainmodel.cpp:176 #18 0x7f4db11e0779 in Nepomuk::ResourceManager::init (this=0x6b70c0) at /usr/src/debug/kdelibs-4.7.95/nepomuk/core/resourcemanager.cpp:331 #19 0x7f4db11e3a85 in Nepomuk::ResourceManagerPrivate::_k_storageServiceInitialized (this=0x872780, success=optimized out) at /usr/src/debug/kdelibs-4.7.95/nepomuk/core/resourcemanager.cpp:221 #20 0x7f4db11e3bdb in Nepomuk::ResourceManager::qt_metacall (this=0x6b70c0, _c=QMetaObject::InvokeMetaMethod, _id=optimized out, _a=0x7fff0a423f80) at /usr/src/debug/kdelibs-4.7.95/build/nepomuk/resourcemanager.moc:107 #21 0x7f4db51e1eab in QDBusConnectionPrivate::deliverCall (this=0x6a98e0, object=0x6b70c0, msg=..., metaTypes=..., slotIdx=9) at qdbusintegrator.cpp:947 #22 0x7f4db57f04f6 in QObject::event (this=0x6b70c0, e=optimized out) at kernel/qobject.cpp:1195 #23 0x7f4db3d58d84 in notify_helper (e=0x941ea0, receiver=0x6b70c0, this=0x649420) at kernel/qapplication.cpp:4550 #24 QApplicationPrivate::notify_helper (this=0x649420, receiver=0x6b70c0, e=0x941ea0) at kernel/qapplication.cpp:4522 #25 0x7f4db3d5dc03 in QApplication::notify (this=0x7fff0a4249c0, receiver=0x6b70c0, e=0x941ea0) at kernel/qapplication.cpp:4411 #26 0x7f4db68fb6f6 in KApplication::notify (this=0x7fff0a4249c0, receiver=0x6b70c0, event=0x941ea0) at /usr/src/debug/kdelibs-4.7.95/kdeui/kernel/kapplication.cpp:311 #27 0x7f4db57d748c in QCoreApplication::notifyInternal (this=0x7fff0a4249c0, receiver=0x6b70c0, event=0x941ea0) at kernel/qcoreapplication.cpp:876 #28 0x7f4db57dad2a in sendEvent (event=0x941ea0, receiver=0x6b70c0) at kernel/qcoreapplication.h:231 #29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x620d70) at kernel/qcoreapplication.cpp:1500 #30 0x7f4db5806093 in sendPostedEvents () at kernel/qcoreapplication.h:236 #31 postEventSourceDispatch (s=optimized out) at kernel/qeventdispatcher_glib.cpp:279 #32 0x7f4dacb7358d in g_main_dispatch (context=0x64d9e0) at gmain.c:2425 #33 g_main_context_dispatch (context=0x64d9e0) at gmain.c:2995 #34 0x7f4dacb73d88 in g_main_context_iterate (context=0x64d9e0, block=optimized out, dispatch=1, self=optimized out) at gmain.c:3073 #35 0x7f4dacb73f59 in g_main_context_iteration (context=0x64d9e0, may_block=1) at gmain.c:3136 #36 0x7f4db58064bf in QEventDispatcherGlib::processEvents (this=0x620620, flags=optimized out) at kernel/qeventdispatcher_glib.cpp:424 #37 0x7f4db3dfbdee in QGuiEventDispatcherGlib::processEvents (this=optimized out, flags=optimized out) at
[Bug 290261] New: Akonadi nepomuk feeder crashed
https://bugs.kde.org/show_bug.cgi?id=290261 Summary: Akonadi nepomuk feeder crashed Product: Akonadi Version: 4.7 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Nepomuk Feeder Agents AssignedTo: kdepim-bugs@kde.org ReportedBy: szots...@gmail.com CC: vkra...@kde.org Application: akonadi_nepomuk_feeder (4.7) KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) release 3 Qt Version: 4.8.0 Operating System: Linux 3.1.0-1.2-desktop x86_64 Distribution: openSUSE 12.1 (x86_64) -- Information about the crash: - What I was doing when the application crashed: I was logging off KDE when the crash dialogue appeared. I'm using Qt 4.8.0 -- Backtrace: Application: Akonadi Nepomuk Feeder (akonadi_nepomuk_feeder), signal: Segmentation fault [KCrash Handler] #6 KSycocaDict::find_string (this=0x909090909090, key=...) at /usr/src/debug/kdelibs-4.7.95/kdecore/sycoca/ksycocadict.cpp:151 #7 0x7fcf4dbaa0b9 in mimeTypeSycocaServiceOffers (mimeType=...) at /usr/src/debug/kdelibs-4.7.95/kdecore/services/kmimetypetrader.cpp:79 #8 KMimeTypeTrader::query (this=optimized out, mimeType=optimized out, genericServiceType=..., constraint=...) at /usr/src/debug/kdelibs-4.7.95/kdecore/services/kmimetypetrader.cpp:147 #9 0x0040bc53 in FeederPluginloader::feederPluginsForMimeType (this=0x6217b0, mimetype=...) at /usr/src/debug/kdepim-runtime-4.7.95/agents/nepomukfeeder/pluginloader.cpp:34 #10 0x004126c5 in NepomukHelpers::addCollectionToNepomuk (collection=...) at /usr/src/debug/kdepim-runtime-4.7.95/agents/nepomukfeeder/nepomukhelpers.cpp:79 #11 0x00408a11 in Akonadi::NepomukFeederAgent::collectionChanged (this=optimized out, collection=..., partIdentifiers=optimized out) at /usr/src/debug/kdepim-runtime-4.7.95/agents/nepomukfeeder/nepomukfeederagent.cpp:163 #12 0x7fcf4d297331 in QMetaObject::activate (sender=0x7bc240, m=optimized out, local_signal_index=optimized out, argv=0x7fffd66337a0) at kernel/qobject.cpp:3547 #13 0x7fcf4d72125a in Akonadi::Monitor::collectionChanged (this=optimized out, _t1=optimized out, _t2=optimized out) at /usr/src/debug/kdepimlibs-4.7.95/build/akonadi/monitor.moc:245 #14 0x7fcf4d724f5c in Akonadi::MonitorPrivate::emitCollectionNotification (this=0x7bf2d0, msg=..., col=optimized out, par=optimized out, dest=optimized out) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/monitor_p.cpp:607 #15 0x7fcf4d726c6a in Akonadi::MonitorPrivate::emitNotification (this=0x7bf2d0, msg=...) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/monitor_p.cpp:285 #16 0x7fcf4d6871a1 in Akonadi::ChangeRecorderPrivate::emitNotification (this=0x7bf2d0, msg=optimized out) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/changerecorder_p.h:60 #17 0x7fcf4d726dd6 in Akonadi::MonitorPrivate::flushPipeline (this=0x7bf2d0) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/monitor_p.cpp:429 #18 0x7fcf4d726e69 in Akonadi::MonitorPrivate::dataAvailable (this=0x7bf2d0) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/monitor_p.cpp:438 #19 0x7fcf4d297331 in QMetaObject::activate (sender=0x7fc5e0, m=optimized out, local_signal_index=optimized out, argv=0x0) at kernel/qobject.cpp:3547 #20 0x7fcf4d68c41d in Akonadi::EntityCacheAkonadi::Collection, Akonadi::CollectionFetchJob, Akonadi::CollectionFetchScope::processResult (this=0x7fc5e0, job=optimized out) at /usr/src/debug/kdepimlibs-4.7.95/akonadi/entitycache_p.h:192 #21 0x7fcf4d297331 in QMetaObject::activate (sender=0x72b430, m=optimized out, local_signal_index=optimized out, argv=0x7fffd6633e60) at kernel/qobject.cpp:3547 #22 0x7fcf4db77322 in KJob::result (this=optimized out, _t1=0x72b430) at /usr/src/debug/kdelibs-4.7.95/build/kdecore/kjob.moc:208 #23 0x7fcf4db77360 in KJob::emitResult (this=0x72b430) at /usr/src/debug/kdelibs-4.7.95/kdecore/jobs/kjob.cpp:318 #24 0x7fcf4d29c4f6 in QObject::event (this=0x72b430, e=optimized out) at kernel/qobject.cpp:1195 #25 0x7fcf4ae92d84 in notify_helper (e=0x7d5c00, receiver=0x72b430, this=0x649de0) at kernel/qapplication.cpp:4550 #26 QApplicationPrivate::notify_helper (this=0x649de0, receiver=0x72b430, e=0x7d5c00) at kernel/qapplication.cpp:4522 #27 0x7fcf4ae97c03 in QApplication::notify (this=0x7fffd6634830, receiver=0x72b430, e=0x7d5c00) at kernel/qapplication.cpp:4411 #28 0x7fcf4e1606f6 in KApplication::notify (this=0x7fffd6634830, receiver=0x72b430, event=0x7d5c00) at /usr/src/debug/kdelibs-4.7.95/kdeui/kernel/kapplication.cpp:311 #29 0x7fcf4d28348c in QCoreApplication::notifyInternal (this=0x7fffd6634830, receiver=0x72b430, event=0x7d5c00) at kernel/qcoreapplication.cpp:876 #30 0x7fcf4d286d2a in sendEvent (event=0x7d5c00, receiver=0x72b430) at kernel/qcoreapplication.h:231 #31 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x627df0) at kernel/qcoreapplication.cpp:1500 #32
[Bug 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 km k...@riseup.net changed: What|Removed |Added CC||k...@riseup.net -- 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 246195] Cannot create Google Contacts akonadi resource [strlen, strdup,extract_and_check_multi, ..., gcal_get_contacts]
https://bugs.kde.org/show_bug.cgi?id=246195 --- Comment #38 from km kmm riseup net 2011-12-31 16:04:37 --- Created an attachment (id=67280) -- (http://bugs.kde.org/attachment.cgi?id=67280) New crash information added by DrKonqi akonadi_googledata_resource (4.7) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0 - What I was doing when the application crashed: I added Google Contacts resource in akonadi configuration and the process aconadi_googledata_resource crashed. Then it starts and crashes again and again, when akonadi tries to sync the resource. -- Backtrace (Reduced): #8 0x7fb012a46403 in extract_and_check_multi (doc=value optimized out, xpath_expression=value optimized out, getContent=0, attr1=0x7fb012a55140 address, attr2=0x7fb012a5513c rel, attr3=0x7fb012a55182 protocol, attr4=0x7fb012a5515e primary, values=0xc13df0, types=0xc13e00, protocols=0xc13df8, pref=0xc13e0c) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:295 #9 0x7fb012a479ae in atom_extract_contact (entry=value optimized out, ptr_entry=0xc13d40) at /usr/src/debug/libgcal-0.9.6/src/atom_parser.c:753 #10 0x7fb012a4e4e6 in extract_all_contacts (doc=value optimized out, data_extract=value optimized out, length=value optimized out) at /usr/src/debug/libgcal-0.9.6/src/gcal_parser.c:434 #11 0x7fb012a524c5 in gcal_get_all_contacts (gcalobj=0x8fc580, length=0x8676d8) at /usr/src/debug/libgcal-0.9.6/src/gcont.c:111 #12 0x7fb012a4f96e in gcal_get_contacts (gcalobj=0x8fc580, contact_array=0x8676d0) at /usr/src/debug/libgcal-0.9.6/src/gcontact.c:155 -- 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 258214] Choosing Completion Order from the context menu of the recipient field crashed kontact
https://bugs.kde.org/show_bug.cgi?id=258214 km k...@riseup.net changed: What|Removed |Added CC||k...@riseup.net -- 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 258214] Choosing Completion Order from the context menu of the recipient field crashed kontact
https://bugs.kde.org/show_bug.cgi?id=258214 --- Comment #1 from km kmm riseup net 2011-12-31 16:38:25 --- Created an attachment (id=67281) -- (http://bugs.kde.org/attachment.cgi?id=67281) New crash information added by DrKonqi kontact (4.7.4) on KDE Platform 4.7.4 (4.7.4) using Qt 4.8.0 - What I was doing when the application crashed: The same as original reporter - I selected completion order from the to field conext menu. I reproduced the crash many times, but not every time. -- Backtrace (Reduced): #7 0x7f47b4910d54 in QObjectPrivate::deleteChildren (this=0x6766e50) at kernel/qobject.cpp:1917 #8 0x7f47b3cc355d in QWidget::~QWidget (this=0x46a4f50, __in_chrg=value optimized out) at kernel/qwidget.cpp:1675 #9 0x7f4758c2337c in ~ComposerLineEdit (this=value optimized out, __in_chrg=value optimized out) at /usr/src/debug/kdepim-4.7.4/messagecomposer/composerlineedit.h:31 #10 ~RecipientLineEdit (this=value optimized out, __in_chrg=value optimized out) at /usr/src/debug/kdepim-4.7.4/messagecomposer/recipientline.h:49 #11 MessageComposer::RecipientLineEdit::~RecipientLineEdit (this=value optimized out, __in_chrg=value optimized out) at /usr/src/debug/kdepim-4.7.4/messagecomposer/recipientline.h:49 -- 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 290272] New: Default value for maximum number of recipients is too small
https://bugs.kde.org/show_bug.cgi?id=290272 Summary: Default value for maximum number of recipients is too small Product: kontact Version: 4.7.2 Platform: openSUSE RPMs OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail AssignedTo: kdepim-bugs@kde.org ReportedBy: br...@clisp.org Version: 4.7.2 (using Devel) OS:Linux Seen in kmail-4.7.4: There is a configuration setting for the maximum number of recipients in a mail reply: Email editor General Maximum number of recipients. It was introduced in https://projects.kde.org/projects/kde/kdepim/repository/revisions/f3476527e4f4c0e269590bf5108cdce211b9c2c7 as a fix to https://bugs.kde.org/show_bug.cgi?id=216351 The problem is that the default value of this maximum number is 1. So, when I reply to all to a mail with 1 To and 2 CC recipients, I get a dialog Truncating recipients list to 1 of 2 entries. And no hint where this problem comes from. Suggestion 1: Set the default value to 100. This would make the problem disappear with normal (not huge) recipient lists. Suggestion 2: Add to the error message (in messagecomposer/recipientseditor.cpp) a hint where to find the configuration setting for the limit. Reproducible: Always Steps to Reproduce: Pick a mail with 1 To and 2 CCs. Do Reply to all Actual Results: A dialog Truncating recipients list to 1 of 2 entries. appears, and some of the expected recipients have been omitted. Expected Results: All Tos and all CCs (except myself) should be listed as recipients. Related bugs: https://bugs.kde.org/show_bug.cgi?id=216351 https://bugs.kde.org/show_bug.cgi?id=287367 -- 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 216351] Opening a draft with more than 200 recipients truncates the recipient list to 200 recipients
https://bugs.kde.org/show_bug.cgi?id=216351 Bruno Haible br...@clisp.org changed: What|Removed |Added CC||br...@clisp.org --- Comment #10 from Bruno Haible bruno clisp org 2011-12-31 17:23:51 --- The maximum number of recipients in a mail can be set through the preferences, but the default is just 1. This is registered as a new bug: https://bugs.kde.org/show_bug.cgi?id=290272 -- 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 287367] Kmail is truncating recipients in reply to all
https://bugs.kde.org/show_bug.cgi?id=287367 Bruno Haible br...@clisp.org changed: What|Removed |Added CC||br...@clisp.org --- Comment #2 from Bruno Haible bruno clisp org 2011-12-31 17:25:02 --- It is indeed possible to configure the maximum number of recipients in a new mail or reply, but the default is still 1. This is registered as a new bug: https://bugs.kde.org/show_bug.cgi?id=290272 -- 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 287394] KMail2 with fetchmail/postfix-fed mbox resource: can't get rid of changed by another program alerts
https://bugs.kde.org/show_bug.cgi?id=287394 Dr. Christoph Pospiech pospi...@de.ibm.com changed: What|Removed |Added CC||pospi...@de.ibm.com --- Comment #1 from Dr. Christoph Pospiech pospiech de ibm com 2011-12-31 20:54:03 --- Hi, I had the same problem and just found a very simple solution (you may call it a work around). Prerequisites - I am using postfix and procmail for mail delivery. Actually, I have a fetchmail type client that funnels incoming mail through procmail. HOWTO implement - step1 * If not already done, add the line mailbox_command = /usr/bin/procmail to /etc/postfix/main.cf and restart postfix. step2 * If ~/.procmailrc doesn't exist, create this file with the following contents. LOGFILE=your_choice_of_logfile_name VERBOSE=yes :0 :your_choice_of_lock_file_name your_$HOME/.local/share/Linux-mail/ !!! And don't forget the '/' after 'Linux-mail' !!! step3 * send a test mail to your account, procmail will create new, cur and tmp sub directories in your_$HOME/.local/share/Linux-mail/ as needed. step4 * Open kmail2, Settings-Konfigure kmail-Accounts-receiving and add a new akonadi resource of type maildir, pointing to your_$HOME/.local/share/Linux-mail step5 * wait some time for akonadi and kmail2 to recognize this new resource. You will find your new mail right there - and NO more changed by another program alerts. Have fun ! Christoph Pospiech -- 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
