[kmail2] [Bug 315617] New: kmail asks to resize images when there aren't any
https://bugs.kde.org/show_bug.cgi?id=315617 Bug ID: 315617 Summary: kmail asks to resize images when there aren't any Classification: Unclassified Product: kmail2 Version: 4.10.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: composer Assignee: kdepim-bugs@kde.org Reporter: nqn1...@gmail.com kmail asks to resize images when trying to send an empty email Reproducible: Always -- 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
[kontact] [Bug 315612] New: Kontact crashed after starup
https://bugs.kde.org/show_bug.cgi?id=315612 Bug ID: 315612 Summary: Kontact crashed after starup Classification: Unclassified Product: kontact Version: 4.10 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: filipobece...@gmail.com Application: kontact (4.10) KDE Platform Version: 4.10.00 Qt Version: 4.8.3 Operating System: Linux 3.5.0-24-generic x86_64 Distribution: Ubuntu 12.10 -- Information about the crash: - What I was doing when the application crashed: I was adding email accounts in kmail for first time. Kontact broke while i trying to update the inbox folder in one of the accounts. - Custom settings of the application: The crash can be reproduced some of the time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2efe9777c0 (LWP 14367))] Thread 4 (Thread 0x7f2ef6ca7700 (LWP 14368)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162 #1 0x7f2f101e4b2d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x7f2f101e4c39 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x7f2f0b31be9a in start_thread (arg=0x7f2ef6ca7700) at pthread_create.c:308 #4 0x7f2f10f0fcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #5 0x in ?? () Thread 3 (Thread 0x7f2ef63a6700 (LWP 14369)): #0 0x7f2f0aa91ba0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f2f0aa91e19 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2f0aa54623 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2f0aa54cab in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2f0aa54ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2f12331c46 in QEventDispatcherGlib::processEvents (this=0x7f2ef8c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f2f123022ef in QEventLoop::processEvents (this=this@entry=0x7f2ef63a5dc0, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f2f12302578 in QEventLoop::exec (this=0x7f2ef63a5dc0, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f2f12203b40 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f2f12206b1c in QThreadPrivate::start (arg=0x1c611b0) at thread/qthread_unix.cpp:338 #10 0x7f2f0b31be9a in start_thread (arg=0x7f2ef63a6700) at pthread_create.c:308 #11 0x7f2f10f0fcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #12 0x in ?? () Thread 2 (Thread 0x7f2ea8d1c700 (LWP 14373)): #0 0x7f2f10f028bd in read () at ../sysdeps/unix/syscall-template.S:82 #1 0x7f2f0aa9115f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f2f0aa54914 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f2f0aa54d22 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f2f0aa54ea4 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f2f12331c46 in QEventDispatcherGlib::processEvents (this=0x7f2ea40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x7f2f123022ef in QEventLoop::processEvents (this=this@entry=0x7f2ea8d1bd90, flags=...) at kernel/qeventloop.cpp:149 #7 0x7f2f12302578 in QEventLoop::exec (this=0x7f2ea8d1bd90, flags=...) at kernel/qeventloop.cpp:204 #8 0x7f2f12203b40 in QThread::exec (this=) at thread/qthread.cpp:501 #9 0x7f2f122e29df in QInotifyFileSystemWatcherEngine::run (this=0x22792d0) at io/qfilesystemwatcher_inotify.cpp:248 #10 0x7f2f12206b1c in QThreadPrivate::start (arg=0x22792d0) at thread/qthread_unix.cpp:338 #11 0x7f2f0b31be9a in start_thread (arg=0x7f2ea8d1c700) at pthread_create.c:308 #12 0x7f2f10f0fcbd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #13 0x in ?? () Thread 1 (Thread 0x7f2efe9777c0 (LWP 14367)): [KCrash Handler] #6 ref (this=0x0) at /usr/include/qt4/QtCore/qatomic_x86_64.h:121 #7 QString (other=..., this=0x7fff829786a0) at /usr/include/qt4/QtCore/qstring.h:726 #8 KontactInterface::Plugin::identifier (this=0x1f3f700) at ../../kontactinterface/plugin.cpp:102 #9 0x7f2f135a3d46 in activateInitialPluginModule (this=0x1c50c90) at ../../../kontact/src/mainwindow.cpp:325 #10 Kontact::MainWindow::activateInitialPluginModule (this=0x1c50c90) at ../../../kontact/src/mainwindow.cpp:320 #11 0x00403d9a in KontactApp::newInstance (this=0x7fff82979890) at ../../../kontact/src/main.cpp:148 #12 0x7f2f12d478e2 in KUniqueApplicationAdaptor::newInstance (this=0x1c2ead0, asn_id=..., args=...) at ../../kdeui/kernel/kuniqueapplication.cpp:442 #13 0x7f2f12d47964 in
[knotes] [Bug 203982] bullet points not saved when application is closed
https://bugs.kde.org/show_bug.cgi?id=203982 --- Comment #7 from Peter --- I think the problem was that notes forces the "-"s into bullet points and then refuses to save them unless rich text is enabled. For instance, I don't want Rich Text enabled. -- 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
[kmail2] [Bug 293271] KMail doesn't remember the SMTP password
https://bugs.kde.org/show_bug.cgi?id=293271 Kamil Dudka changed: What|Removed |Added CC||kdu...@redhat.com -- 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
[kontact] [Bug 315601] New: Kmail crashed when exited.
https://bugs.kde.org/show_bug.cgi?id=315601 Bug ID: 315601 Summary: Kmail crashed when exited. Classification: Unclassified Product: kontact Version: 4.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: petriel...@ornl.gov Application: kontact (4.9.5) KDE Platform Version: 4.9.5 Qt Version: 4.8.4 Operating System: Linux 3.7.6-102.fc17.x86_64 x86_64 Distribution: "Fedora release 17 (Beefy Miracle)" -- Information about the crash: - What I was doing when the application crashed: I was closing kmail, preparing to logoff. It has been behaving inconsistently, sometimes not showing the folder list, or not showing any contacts. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". 82T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS) [Current thread is 1 (Thread 0x7f23cc366880 (LWP 5527))] Thread 4 (Thread 0x7f23c0ccf700 (LWP 5618)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:166 #1 0x0037fb416a5d in WTF::TCMalloc_PageHeap::scavengerThread (this=0x37fbe00ce0) at wtf/FastMalloc.cpp:2495 #2 0x0037fb416b69 in WTF::TCMalloc_PageHeap::runScavengerThread (context=) at wtf/FastMalloc.cpp:1618 #3 0x00351d207d14 in start_thread (arg=0x7f23c0ccf700) at pthread_create.c:309 #4 0x00351c6f168d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 3 (Thread 0x7f23b8bb6700 (LWP 5619)): #0 0x00351c6e8bdf in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x003ca0247af4 in g_main_context_poll (n_fds=1, fds=0x7f23ac0029c0, timeout=7652, context=0x7f23ac0009a0, priority=) at gmain.c:3440 #2 g_main_context_iterate (context=context@entry=0x7f23ac0009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at gmain.c:3141 #3 0x003ca0247c14 in g_main_context_iteration (context=0x7f23ac0009a0, may_block=1) at gmain.c:3207 #4 0x003eb33a5fe6 in QEventDispatcherGlib::processEvents (this=0x7f23ac0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x003eb33766ef in QEventLoop::processEvents (this=this@entry=0x7f23b8bb5d00, flags=...) at kernel/qeventloop.cpp:149 #6 0x003eb3376978 in QEventLoop::exec (this=0x7f23b8bb5d00, flags=...) at kernel/qeventloop.cpp:204 #7 0x003eb3278940 in QThread::exec (this=) at thread/qthread.cpp:542 #8 0x003eb327b91c in QThreadPrivate::start (arg=0x2843f40) at thread/qthread_unix.cpp:338 #9 0x00351d207d14 in start_thread (arg=0x7f23b8bb6700) at pthread_create.c:309 #10 0x00351c6f168d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 2 (Thread 0x7f234bfff700 (LWP 17472)): #0 pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:218 #1 0x003eb327bdd7 in wait (time=3, this=0x35469a0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x3533c58, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x003eb326f65f in QThreadPoolThread::run (this=0x28d12c0) at concurrent/qthreadpool.cpp:141 #4 0x003eb327b91c in QThreadPrivate::start (arg=0x28d12c0) at thread/qthread_unix.cpp:338 #5 0x00351d207d14 in start_thread (arg=0x7f234bfff700) at pthread_create.c:309 #6 0x00351c6f168d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115 Thread 1 (Thread 0x7f23cc366880 (LWP 5527)): [KCrash Handler] #6 isEmpty (this=this@entry=0xb1) at ../../src/corelib/tools/qhash.h:297 #7 QHash::remove (this=this@entry=0xb1, akey=...) at ../../src/corelib/tools/qhash.h:786 #8 0x003eb3372308 in QAbstractItemModelPrivate::removePersistentIndexData (this=0x21, data=data@entry=0x3847710) at kernel/qabstractitemmodel.cpp:542 #9 0x003eb3372559 in QPersistentModelIndexData::destroy (data=0x3847710) at kernel/qabstractitemmodel.cpp:83 #10 0x003eb337268f in QPersistentModelIndex::~QPersistentModelIndex (this=0x43c3970, __in_chrg=) at kernel/qabstractitemmodel.cpp:155 #11 0x0037f32db17d in ~QItemSelectionRange (this=0x43c3970, __in_chrg=) at ../../src/gui/itemviews/qitemselectionmodel.h:58 #12 node_destruct (to=0x45a2cf0, from=0x45a2ce8, this=) at ../../src/corelib/tools/qlist.h:431 #13 free (data=0x45a2cd0, this=) at ../../src/corelib/tools/qlist.h:757 #14 QList::~QList (this=, __in_chrg=) at ../../src/corelib/tools/qlist.h:732 #15 0x0037f332ac1b in ~QItemSelection (this=0x3514b90, __in_chrg=) at itemviews/qitemselectionmodel.h:231 #16 ~QItemSelectionModelPrivate (this=0x3514b00, __in_chrg=) at ../../src/gui/itemviews/qitemselectionmodel_p.h:61 #17 QItemSelectionModelPrivate::~QItemSelectionModelPrivate (this=0x3514b00, __in_chrg=) at ../../src/gui/itemviews/qitemselectionmodel_p.h:61 #18 0x003eb33
[Akonadi] [Bug 284527] Error when changing an imap folder's identity (Unknown command SETANNOTATION)
https://bugs.kde.org/show_bug.cgi?id=284527 Christux changed: What|Removed |Added CC||c.schwarzgruber...@gmail.co ||m --- Comment #10 from Christux --- Same for me using KDE 4.10 on openSuSe 12.3 RC1! -- 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
[kontact] [Bug 315597] New: Kontact nicht bedienbar / Reagiert nicht
https://bugs.kde.org/show_bug.cgi?id=315597 Bug ID: 315597 Summary: Kontact nicht bedienbar / Reagiert nicht Classification: Unclassified Product: kontact Version: 4.10 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: gt4ra...@gmx.de Application: kontact (4.10) KDE Platform Version: 4.10.00 "release 550" Qt Version: 4.8.4 Operating System: Linux 3.4.28-2.20-desktop i686 Distribution: "openSUSE 12.2 (i586)" -- Information about the crash: - What I was doing when the application crashed: Kontact gestartet. Egal auf welchen Ordner ich klicke, das Symbol davor fängt an sich zu drehen, aber nicht passiert. Es werden keine Mails angezeigt, abgerufen oder können gelöscht werden. - Unusual behavior I noticed: The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0xb22fb740 (LWP 26315))] Thread 3 (Thread 0xb1094b40 (LWP 26316)): #0 0xb7707424 in __kernel_vsyscall () #1 0xb3ab0a4c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb600211c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libc.so.6 #3 0xb571230d in ?? () from /usr/lib/libQtWebKit.so.4 #4 0xb571233f in ?? () from /usr/lib/libQtWebKit.so.4 #5 0xb3aace32 in start_thread () from /lib/libpthread.so.0 #6 0xb5ff47ee in clone () from /lib/libc.so.6 Thread 2 (Thread 0xb076bb40 (LWP 26317)): #0 0xb772145b in __x86.get_pc_thunk.bx () from /lib/ld-linux.so.2 #1 0xb771a416 in ___tls_get_addr_internal () from /lib/ld-linux.so.2 #2 0xb6cebb1f in get_thread_data () at thread/qthread_unix.cpp:182 #3 QThreadData::current () at thread/qthread_unix.cpp:208 #4 0xb6e30eff in postEventSourcePrepare (s=0xafe00da8, timeout=0xb076b0cc) at kernel/qeventdispatcher_glib.cpp:256 #5 0xb395d2a2 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0 #6 0xb395d9ef in ?? () from /usr/lib/libglib-2.0.so.0 #7 0xb395dc51 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #8 0xb6e3164f in QEventDispatcherGlib::processEvents (this=0xafe00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #9 0xb6dfe12c in QEventLoop::processEvents (this=this@entry=0xb076b258, flags=...) at kernel/qeventloop.cpp:149 #10 0xb6dfe421 in QEventLoop::exec (this=0xb076b258, flags=...) at kernel/qeventloop.cpp:204 #11 0xb6ce9b3c in QThread::exec (this=this@entry=0x8a60440) at thread/qthread.cpp:542 #12 0xb6ce9c9b in QThread::run (this=0x8a60440) at thread/qthread.cpp:609 #13 0xb6cecf48 in QThreadPrivate::start (arg=0x8a60440) at thread/qthread_unix.cpp:338 #14 0xb3aace32 in start_thread () from /lib/libpthread.so.0 #15 0xb5ff47ee in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb22fb740 (LWP 26315)): [KCrash Handler] #7 0xaf02b2c7 in MailCommon::FolderTreeWidget::folderTreeView() const () from /usr/lib/libmailcommon.so.4 #8 0xaf19ca9c in folderTreeView (this=) at /usr/src/debug/kdepim-4.10.0/kmail/kmmainwidget.h:139 #9 KMKernel::treeviewModelSelection (this=0x8cedec8) at /usr/src/debug/kdepim-4.10.0/kmail/kmkernel.cpp:1938 #10 0xaf18f66f in KMail::KMSystemTray::slotContextMenuAboutToShow (this=0x8e7be38) at /usr/src/debug/kdepim-4.10.0/kmail/kmsystemtray.cpp:279 #11 0xb6e179b2 in QMetaObject::activate (sender=0x8e91570, m=0xb6c65bb4 , local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3548 #12 0xb6795255 in QMenu::aboutToShow (this=this@entry=0x8e91570) at .moc/release-shared/moc_qmenu.cpp:165 #13 0xb679bdf8 in qt_static_metacall (_a=0xbf9d92b4, _id=0, _o=0x8e91570, _c=) at .moc/release-shared/moc_qmenu.cpp:74 #14 QMenu::qt_static_metacall (_o=0x8e91570, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf9d92b4) at .moc/release-shared/moc_qmenu.cpp:68 #15 0xb6e0801d in QMetaMethod::invoke (this=0xbf9d93e4, object=0x8e91570, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1664 #16 0xb6e0a699 in QMetaObject::invokeMethod (obj=0x8e91570, member=0xb3b0fc68 "aboutToShow", type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1179 #17 0xb3af93c1 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., member=, obj=) at /usr/include/QtCore/qobjectdefs.h:434 #18 DBusMenuExporterDBus::AboutToShow (this=0x0, id=0) at /usr/src/debug/libdbusmenu-qt-0.9.2/src/dbusmenuexporterdbus_p.cpp:156 #19 0xb3afc0b8 in DBusMenuExporterDBus::qt_static_metacall (_o=_o@entry=0x8e5c5f8, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=7, _a=_a@entry=0xbf9d98cc) at /usr/src/debug/libdbusmenu-qt-0.9.2/build/sr
[Akonadi] [Bug 292497] kmail 4.8.0 doesn't filter the incoming messages
https://bugs.kde.org/show_bug.cgi?id=292497 Diego Calleja Garcia changed: What|Removed |Added CC||dieg...@teleline.es --- Comment #28 from Diego Calleja Garcia --- I have been hitting this problem (POP3 account) over more than a year, still happens with the latest version. -- 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
[kmail2] [Bug 292418] Kmail can't create IMAP top level folders
https://bugs.kde.org/show_bug.cgi?id=292418 Tom Chiverton changed: What|Removed |Added CC||bugs.kde@falkensweb.com --- Comment #24 from Tom Chiverton --- Same here as #23: Fully updated KDE 4.8.5 on Ubuntu 12/04. The folder is created and accessible fine by other clients, but the popup appears every few minutes. The resource id is higher, might be an internal number. Starting from the command line reveals nothing of insight about what might actually be wrong. -- 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
[Akonadi] [Bug 315584] New: Crash when trying to retrieve email on spotty network
https://bugs.kde.org/show_bug.cgi?id=315584 Bug ID: 315584 Summary: Crash when trying to retrieve email on spotty network Classification: Unclassified Product: Akonadi Version: 4.7 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: christian.winterst...@googlemail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.7) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-31-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: During the IMAP synchronization the internet connection got lost. Then I clicked on File -> Offline Mode. Then happened the crash. -- Backtrace: Application: Web.de of type IMAP-E-Mail-Server (akonadi_imap_resource), signal: Segmentation fault [Current thread is 1 (Thread 0x7fdc54b67780 (LWP 2102))] Thread 2 (Thread 0x7fdc40937700 (LWP 15579)): #0 0x7fdc5058be63 in __GI___poll (fds=, nfds=, timeout=) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x7fdc4eed9f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fdc4eeda429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fdc53fd8f3e in QEventDispatcherGlib::processEvents (this=0x24fb430, flags=) at kernel/qeventdispatcher_glib.cpp:424 #4 0x7fdc53faccf2 in QEventLoop::processEvents (this=, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fdc53facef7 in QEventLoop::exec (this=0x7fdc40936de0, flags=...) at kernel/qeventloop.cpp:201 #6 0x7fdc53ec427f in QThread::exec (this=) at thread/qthread.cpp:498 #7 0x7fdc52beac13 in ?? () from /usr/lib/libkimap.so.4 #8 0x7fdc53ec6d05 in QThreadPrivate::start (arg=0x2526510) at thread/qthread_unix.cpp:331 #9 0x7fdc4fe43efc in start_thread (arg=0x7fdc40937700) at pthread_create.c:304 #10 0x7fdc50597f8d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x in ?? () Thread 1 (Thread 0x7fdc54b67780 (LWP 2102)): [KCrash Handler] #6 0x0098 in ?? () #7 0x7fdc53fc0714 in QObject::disconnect (sender=0x236b400, signal=0x2352699 "connectionLost()", receiver=0x2306480, method=0x23aa4b9 "onEarlyConnectionLost()") at kernel/qobject.cpp:2728 #8 0x00453931 in SessionPool::killSession (this=0x2306480, session=0x236b400, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:177 #9 0x00453ef5 in SessionPool::disconnect (this=0x2306480, termination=SessionPool::LogoutSession) at ../../../resources/imap/sessionpool.cpp:119 #10 0x004168c3 in ImapResource::doSetOnline (this=0x231bc10, online=false) at ../../../resources/imap/imapresource.cpp:421 #11 0x7fdc545d8ee8 in Akonadi::AgentBase::setOnline(bool) () from /usr/lib/libakonadi-kde.so.4 #12 0x7fdc5470e9c0 in ?? () from /usr/lib/libakonadi-kde.so.4 #13 0x7fdc543050e9 in QDBusConnectionPrivate::deliverCall (this=0x2247860, object=0x22e27b0, msg=..., metaTypes=..., slotIdx=12) at qdbusintegrator.cpp:942 #14 0x7fdc5430625c in QDBusConnectionPrivate::activateCall (this=0x2247860, object=0x22e27b0, flags=273, msg=...) at qdbusintegrator.cpp:852 #15 0x7fdc54306b22 in QDBusConnectionPrivate::activateObject (this=0x2247860, node=..., msg=..., pathStartPos=) at qdbusintegrator.cpp:1410 #16 0x7fdc54306bf8 in QDBusActivateObjectEvent::placeMetaCall (this=0x2594a50) at qdbusintegrator.cpp:1524 #17 0x7fdc53fc4a5e in QObject::event (this=0x231bc10, e=) at kernel/qobject.cpp:1217 #18 0x7fdc5335d474 in notify_helper (e=0x2594a50, receiver=0x231bc10, this=0x21be640) at kernel/qapplication.cpp:4486 #19 QApplicationPrivate::notify_helper (this=0x21be640, receiver=0x231bc10, e=0x2594a50) at kernel/qapplication.cpp:4458 #20 0x7fdc533622e1 in QApplication::notify (this=0x7fffe30d2f10, receiver=0x231bc10, e=0x2594a50) at kernel/qapplication.cpp:4365 #21 0x7fdc51474466 in KApplication::notify (this=0x7fffe30d2f10, receiver=0x231bc10, event=0x2594a50) at ../../kdeui/kernel/kapplication.cpp:311 #22 0x7fdc53fadafc in QCoreApplication::notifyInternal (this=0x7fffe30d2f10, receiver=0x231bc10, event=0x2594a50) at kernel/qcoreapplication.cpp:787 #23 0x7fdc53fb151f in sendEvent (event=0x2594a50, receiver=0x231bc10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #24 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x2195800) at kernel/qcoreapplication.cpp:1428 #25 0x7fdc53fd8a73 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #26 postEventSourceDispatch (s=) at kernel/qeventdispatcher_glib.cpp:277 #27 0x7fdc4eed9a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2
[akregator] [Bug 158272] in Delete article dialog switching options with arrows highlights text
https://bugs.kde.org/show_bug.cgi?id=158272 Maarten De Meyer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||de.meyer.maar...@gmail.com Resolution|--- |WORKSFORME --- Comment #2 from Maarten De Meyer --- (In reply to comment #1) > I can not reproduce this bug with akregator 1.6.5 kde 4.6.2 kubuntu 10.10 > and kdepim master compiled from sources Thanks. Closing. -- 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
[akregator] [Bug 315554] [USABILITY] Akregator should switch keryboard focus to the browser window once a tab is selected
https://bugs.kde.org/show_bug.cgi?id=315554 Maarten De Meyer changed: What|Removed |Added CC||de.meyer.maar...@gmail.com --- Comment #1 from Maarten De Meyer --- I can confirm left and right bring you back to the feed list. But I can use up and down without problem when switching to a tab. Is up and down disabled for every feed? -- 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
[akregator] [Bug 315555] [USABILITY-KEYBOARD] WISH: Switch between tabs with the + or arrows ala Konsole
https://bugs.kde.org/show_bug.cgi?id=31 Maarten De Meyer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||de.meyer.maar...@gmail.com Resolution|--- |WORKSFORME --- Comment #1 from Maarten De Meyer --- The tabbar in akregator uses the stock KDE shortcuts for switching. Konsole is the exception. (because some commandline programs can use these default shortcuts) Most apps from the KDE community: + for next tab. ++ for previous tab. You can change these shortcuts if you want. In akregator: Settings -> Configure Shortcuts For all applications: System Settings -> Shortcuts and Gestures -> Standard Keyboard Shortcuts Please use the forums or irc if you have further questions. Thanks -- 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
[kmail2] [Bug 315568] New: kmail crash on startup
https://bugs.kde.org/show_bug.cgi?id=315568 Bug ID: 315568 Summary: kmail crash on startup Classification: Unclassified Product: kmail2 Version: 4.10 Platform: openSUSE RPMs OS: Linux Status: CONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: kol...@aon.at Application: kmail (4.10) KDE Platform Version: 4.10.00 "release 546" Qt Version: 4.8.4 Operating System: Linux 3.4.28-2.20-desktop x86_64 Distribution: "openSUSE 12.2 (x86_64)" -- Information about the crash: - What I was doing when the application crashed: As I had a mail in my inbox (from a POP account) where kmail did not show any content, I thought let's stop kmail and restart akonadi. So I stopped kmail, opened a konsole and shut down akonadi with akonadictl stop Then after no more akonadi processes were running, I tried to start kmail again, but this lead to this crash. -- Backtrace: Application: KMail (kmail), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe18273b780 (LWP 29174))] Thread 5 (Thread 0x7fe162c16700 (LWP 29200)): #0 0x7fe17d8c68f4 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe17306e437 in ?? () from /usr/lib64/libQtWebKit.so.4 #2 0x7fe17306e469 in ?? () from /usr/lib64/libQtWebKit.so.4 #3 0x7fe17d8c2e0e in start_thread () from /lib64/libpthread.so.0 #4 0x7fe17fa912cd in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fe1622fd700 (LWP 29201)): #0 0x7fe17fa8914f in poll () from /lib64/libc.so.6 #1 0x7fe177d26684 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7fe177d267a4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x7fe18041c136 in QEventDispatcherGlib::processEvents (this=0x7fe1540008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #4 0x7fe1803ec94f in QEventLoop::processEvents (this=this@entry=0x7fe1622fce00, flags=...) at kernel/qeventloop.cpp:149 #5 0x7fe1803ecbd8 in QEventLoop::exec (this=0x7fe1622fce00, flags=...) at kernel/qeventloop.cpp:204 #6 0x7fe1802ef0b0 in QThread::exec (this=) at thread/qthread.cpp:542 #7 0x7fe1802f208c in QThreadPrivate::start (arg=0xed8210) at thread/qthread_unix.cpp:338 #8 0x7fe17d8c2e0e in start_thread () from /lib64/libpthread.so.0 #9 0x7fe17fa912cd in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7fe159916700 (LWP 20342)): #0 0x7fe177d26795 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #1 0x7fe18041c136 in QEventDispatcherGlib::processEvents (this=0x7fe12d30, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #2 0x7fe1803ec94f in QEventLoop::processEvents (this=this@entry=0x7fe159915dd0, flags=...) at kernel/qeventloop.cpp:149 #3 0x7fe1803ecbd8 in QEventLoop::exec (this=0x7fe159915dd0, flags=...) at kernel/qeventloop.cpp:204 #4 0x7fe1802ef0b0 in QThread::exec (this=) at thread/qthread.cpp:542 #5 0x7fe1803cd0bf in QInotifyFileSystemWatcherEngine::run (this=0x7191100) at io/qfilesystemwatcher_inotify.cpp:256 #6 0x7fe1802f208c in QThreadPrivate::start (arg=0x7191100) at thread/qthread_unix.cpp:338 #7 0x7fe17d8c2e0e in start_thread () from /lib64/libpthread.so.0 #8 0x7fe17fa912cd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fe15bfff700 (LWP 16512)): #0 0x7fe17d8c6c61 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fe1802f2547 in wait (time=3, this=0x41f4340) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=, mutex=0x1185198, time=3) at thread/qwaitcondition_unix.cpp:158 #3 0x7fe1802e5d4f in QThreadPoolThread::run (this=0xb62cde0) at concurrent/qthreadpool.cpp:141 #4 0x7fe1802f208c in QThreadPrivate::start (arg=0xb62cde0) at thread/qthread_unix.cpp:338 #5 0x7fe17d8c2e0e in start_thread () from /lib64/libpthread.so.0 #6 0x7fe17fa912cd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fe18273b780 (LWP 29174)): [KCrash Handler] #6 QMetaObject::indexOfEnumerator (this=, name=0x7fe1822d5b5f "ItemStatus") at kernel/qmetaobject.cpp:717 #7 0x7fe18226e4fc in KStatusNotifierItem::setStatus (this=0x1531160, status=KStatusNotifierItem::Passive) at /usr/src/debug/kdelibs-4.10.0/kdeui/notifications/kstatusnotifieritem.cpp:161 #8 0x7fe1814e6486 in KMail::KMSystemTray::setMode (this=0x1531160, newMode=1) at /usr/src/debug/kdepim-4.10.0/kmail/kmsystemtray.cpp:164 #9 0x7fe1814f4126 in KMKernel::toggleSystemTray (this=0x7fff90786f80) at /usr/src/debug/kdepim-4.10.0/kmail/kmkernel.cpp:2057 #10 0x7fe1815459d7 in KMMainWidget::readConfig (this=this@entry=0xb6a7ea0) at /usr/src/debug/kdepim-4.10.0/kmail/kmmainwidget.cpp:979 #11 0x7fe181545ee1 in KMMainWidget::KMMainWidget (this=0xb6a7ea0, parent=, aGUIClient=0x179ebb0, actionCollection=, config
[kmail2] [Bug 315559] New: kmail sometimes does not empty trash
https://bugs.kde.org/show_bug.cgi?id=315559 Bug ID: 315559 Summary: kmail sometimes does not empty trash Classification: Unclassified Product: kmail2 Version: 4.10.0 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: dron...@gmail.com the bug introduced in IMAP mode for me, but POP3 may be also affected (not checked) if Thash folder is active and empty, the newly arrived trash cannot be deleted because menu item used to empty trash is disabeld. move to home and return to trash is a workaround ) Reproducible: Always Steps to Reproduce: 1. Empty trash folder and make it active 2. Wait for new emails in trash 3. Unable to empty trash again -- 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
