[kmail2] [Bug 378189] kmail often stuck in "Retrieving Folder Contents"
https://bugs.kde.org/show_bug.cgi?id=378189 Brallan Aguilar <apcomp...@gmail.com> changed: What|Removed |Added CC||apcomp...@gmail.com --- Comment #15 from Brallan Aguilar <apcomp...@gmail.com> --- Everyday I must restart Akonadi and KMail to use my email properly :( Using Kontact 5.5.1 -- You are receiving this mail because: You are the assignee for the bug.
[kmail2] [Bug 344459] New: Email as attachment are not loaded in ToDo
https://bugs.kde.org/show_bug.cgi?id=344459 Bug ID: 344459 Summary: Email as attachment are not loaded in ToDo Product: kmail2 Version: 4.14.4 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: apcomp...@gmail.com I'm using Kontact. In Mail section, I select an email and in Main Toolbar (kmmainwin) I press Create To-Do, then appears a panel in the bottom, select Open editor and appears the To-Do window. I select Attachments tab and can see the email. Right click and Open don't show the 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 332991] Wrong remaining time in Summary
https://bugs.kde.org/show_bug.cgi?id=332991 --- Comment #2 from Brallan Aguilar apcomp...@gmail.com --- Still present in KDE 4.14.1 -- 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 338739] Kontact crashes when open a Task from Summary
https://bugs.kde.org/show_bug.cgi?id=338739 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #1 from Brallan Aguilar apcomp...@gmail.com --- After update FEDORA-2014-9920, I have not see this bug. -- 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 338739] New: Kontact crashes when open a Task from Summary
https://bugs.kde.org/show_bug.cgi?id=338739 Bug ID: 338739 Summary: Kontact crashes when open a Task from Summary Product: kontact Version: unspecified Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: apcomp...@gmail.com Application: kontact (4.13.3) KDE Platform Version: 4.13.3 Qt Version: 4.8.6 Operating System: Linux 3.15.10-201.fc20.i686 i686 Distribution: Fedora release 20 (Heisenbug) -- Information about the crash: - What I was doing when the application crashed: 1. Open Kontact (a fresh update, KDE 4.13.3 from fedora-updates repository) 2. Click over a Task on Summary 3. Kontact crashes 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 0xb7634840 (LWP 1923))] Thread 3 (Thread 0xb4d68b40 (LWP 1924)): #0 0xb77edb1c in __kernel_vsyscall () #1 0x4284979c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:187 #2 0x490f1c44 in WTF::ThreadCondition::wait (this=this@entry=0x83097ec, mutex=...) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:379 #3 0x48db88dc in JSC::BlockAllocator::blockFreeingThreadMain (this=0x8309760) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128 #4 0x490d4139 in WTF::threadEntryPoint (contextData=0x822fae8) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/Threading.cpp:69 #5 0x490f156a in WTF::wtfThreadEntryPoint (param=0x8277f20) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196 #6 0x42845d7c in start_thread (arg=0xb4d68b40) at pthread_create.c:309 #7 0x4276f7ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 2 (Thread 0xb2736b40 (LWP 1927)): #0 0xb77edb1c in __kernel_vsyscall () #1 0x427631bb in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x42a30f9c in poll (__timeout=__timeout@entry=4270, __nfds=__nfds@entry=1, __fds=__fds@entry=0xb1d02160) at /usr/include/bits/poll2.h:46 #3 g_poll (fds=fds@entry=0xb1d02160, nfds=nfds@entry=1, timeout=timeout@entry=4270) at gpoll.c:132 #4 0x42a218a0 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0xb1d02160, timeout=4270, context=0xb1d004e0) at gmain.c:4007 #5 g_main_context_iterate (context=context@entry=0xb1d004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3708 #6 0x42a219e9 in g_main_context_iteration (context=0xb1d004e0, may_block=1) at gmain.c:3774 #7 0x43414dcf in QEventDispatcherGlib::processEvents (this=0xb1d00468, flags=...) at kernel/qeventdispatcher_glib.cpp:452 #8 0x433e1ac0 in QEventLoop::processEvents (this=this@entry=0xb2736194, flags=...) at kernel/qeventloop.cpp:149 #9 0x433e1e51 in QEventLoop::exec (this=this@entry=0xb2736194, flags=...) at kernel/qeventloop.cpp:204 #10 0x432c30d5 in QThread::exec (this=this@entry=0x8429068) at thread/qthread.cpp:538 #11 0x432c323c in QThread::run (this=0x8429068) at thread/qthread.cpp:605 #12 0x432c5bdb in QThreadPrivate::start (arg=0x8429068) at thread/qthread_unix.cpp:349 #13 0x42845d7c in start_thread (arg=0xb2736b40) at pthread_create.c:309 #14 0x4276f7ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129 Thread 1 (Thread 0xb7634840 (LWP 1923)): [KCrash Handler] #7 QApplication::notify (this=0xbfe689b4, receiver=0x98525b0, e=e@entry=0xbfe68414) at kernel/qapplication.cpp:4092 #8 0x44e4ea30 in KApplication::notify (this=0xbfe689b4, receiver=0x98525b0, event=0xbfe68414) at /usr/src/debug/kdelibs-4.13.3/kdeui/kernel/kapplication.cpp:311 #9 0x433e3226 in QCoreApplication::notifyInternal (this=0xbfe689b4, receiver=receiver@entry=0x98525b0, event=event@entry=0xbfe68414) at kernel/qcoreapplication.cpp:953 #10 0x43794262 in sendEvent (event=optimized out, receiver=optimized out) at ../../src/corelib/kernel/qcoreapplication.h:231 #11 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x98525b0, event=0xbfe68414, alienWidget=0x98525b0, nativeWidget=0x969d130, buttonDown=buttonDown@entry=0x441493e4 qt_button_down, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173 #12 0x43819cb8 in QETWidget::translateMouseEvent (this=0x969d130, event=event@entry=0xbfe6862c) at kernel/qapplication_x11.cpp:4540 #13 0x438183a3 in QApplication::x11ProcessEvent (this=0xbfe689b4, event=event@entry=0xbfe6862c) at kernel/qapplication_x11.cpp:3663 #14 0x4384409b in x11EventSourceDispatch (s=s@entry=0x80ba840, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148 #15 0x42a21556 in g_main_dispatch (context=0x80b9488) at gmain.c:3066 #16 g_main_context_dispatch (context=context@entry=0x80b9488) at gmain.c:3642 #17
[kontact] [Bug 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #11 from Brallan Aguilar apcomp...@gmail.com --- It continues in KDE 4.13.3 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Version|4.13.1 |4.13.2 -- 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 332991] Wrong remaining time in Summary
https://bugs.kde.org/show_bug.cgi?id=332991 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Version|4.12.3 |4.13.2 --- Comment #1 from Brallan Aguilar apcomp...@gmail.com --- Still present in KDE 4.13.3 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Version|4.12.4 |4.13.1 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #9 from Brallan Aguilar apcomp...@gmail.com --- The problem persists in KDE 4.12.5 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=330420 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #6 from Brallan Aguilar apcomp...@gmail.com --- Created attachment 86360 -- https://bugs.kde.org/attachment.cgi?id=86360action=edit Upcoming Events Summary Setup in Kontact -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #7 from Brallan Aguilar apcomp...@gmail.com --- Created attachment 86361 -- https://bugs.kde.org/attachment.cgi?id=86361action=edit Existence of an event in the calendar -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #8 from Brallan Aguilar apcomp...@gmail.com --- Created attachment 86362 -- https://bugs.kde.org/attachment.cgi?id=86362action=edit Kontact Summary showing no events -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Version|4.12.3 |4.12.4 --- Comment #5 from Brallan Aguilar apcomp...@gmail.com --- Still present in KDE 4.12.4 -- 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 332991] New: Wrong remaining time in Summary
https://bugs.kde.org/show_bug.cgi?id=332991 Bug ID: 332991 Summary: Wrong remaining time in Summary Classification: Unclassified Product: kontact Version: 4.12.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: apcomp...@gmail.com In Upcoming Events is shown in the second column the time remaining for every event. The problem is that when an event ends, you still see now. For example, I had an activity from 9:00 to 10:00 and it's 19:00 and still appears that the event is occurring now. Reproducible: Always Expected Results: The finished events must disappear from Upcoming Events. -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added Version|4.11.3 |4.12.3 Severity|minor |normal -- 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 330420] kontact, 2 events but 0 event displayed in the list
https://bugs.kde.org/show_bug.cgi?id=330420 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added CC||apcomp...@gmail.com --- Comment #5 from Brallan Aguilar apcomp...@gmail.com --- May be related with https://bugs.kde.org/show_bug.cgi?id=327256 -- 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 327256] Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 --- Comment #4 from Brallan Aguilar apcomp...@gmail.com --- It's present on KDE 4.12.3 ;( -- 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 331621] New: Kontact crashed while starting
https://bugs.kde.org/show_bug.cgi?id=331621
Bug ID: 331621
Summary: Kontact crashed while starting
Classification: Unclassified
Product: kontact
Version: 4.12.2
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: apcomp...@gmail.com
Application: kontact (4.12.2)
KDE Platform Version: 4.12.2
Qt Version: 4.8.5
Operating System: Linux 3.13.4-200.fc20.i686 i686
Distribution: Fedora release 20 (Heisenbug)
-- Information about the crash:
- What I was doing when the application crashed:
I was running Kontact on background, suddenly it closed. I executed it again
and crashed.
The crash does not seem to be reproducible.
-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
Using host libthread_db library /lib/libthread_db.so.1.
[Current thread is 1 (Thread 0xb77abac0 (LWP 1783))]
Thread 4 (Thread 0xb5016b40 (LWP 1808)):
#0 0xb77fa424 in __kernel_vsyscall ()
#1 0x4a08d7ac in pthread_cond_wait@@GLIBC_2.3.2 () at
../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:187
#2 0x44c3ae34 in WTF::ThreadCondition::wait (this=this@entry=0x8961e74,
mutex=...) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:379
#3 0x44901acc in JSC::BlockAllocator::blockFreeingThreadMain (this=0x8961de8)
at
/usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128
#4 0x44c1d329 in WTF::threadEntryPoint (contextData=0x88abeb0) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/Threading.cpp:69
#5 0x44c3a75a in WTF::wtfThreadEntryPoint (param=0x88ef760) at
/usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196
#6 0x4a089d8a in start_thread (arg=0xb5016b40) at pthread_create.c:309
#7 0x49fb3a0e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:129
Thread 3 (Thread 0xb23ffb40 (LWP 1937)):
[KCrash Handler]
#7 0xb2dea249 in stmt_process_result (stmt=stmt@entry=0x8da6450,
needs_evl=needs_evl@entry=1) at ../../libsrc/Wi/CLIuti.c:721
#8 0xb2dee5e8 in virtodbc__SQLExecDirect (hstmt=hstmt@entry=0x8da6450,
szSqlStr=szSqlStr@entry=0x8f4f768 sparql DEFINE input:inference
nepomukinference select distinct ?r ?o where { { ?r
http://www.semanticdesktop.org/ontologies/2007/01/19/nie#url
akonadi:?item=-1 . FILTER(?r!=akonadi:?item=-1) ,
cbSqlStr=cbSqlStr@entry=249) at ../../libsrc/Wi/CLIsql1.c:1530
#9 0xb2dee7c4 in SQLExecDirect (hstmt=0x8da6450, wszSqlStr=0x8f4f768 sparql
DEFINE input:inference nepomukinference select distinct ?r ?o where { { ?r
http://www.semanticdesktop.org/ontologies/2007/01/19/nie#url
akonadi:?item=-1 . FILTER(?r!=akonadi:?item=-1) , cbSqlStr=249) at
../../libsrc/Wi/CLIsql1.c:1556
#10 0xb38b1fdc in SQLExecDirect_Internal (hstmt=hstmt@entry=0x8da6388,
szSqlStr=szSqlStr@entry=0x8f4f768, cbSqlStr=cbSqlStr@entry=249,
waMode=waMode@entry=65 'A') at execute.c:549
#11 0xb38b22f4 in SQLExecDirect (hstmt=0x8da6388, szSqlStr=0x8f4f768 sparql
DEFINE input:inference nepomukinference select distinct ?r ?o where { { ?r
http://www.semanticdesktop.org/ontologies/2007/01/19/nie#url
akonadi:?item=-1 . FILTER(?r!=akonadi:?item=-1) , cbSqlStr=249) at
execute.c:631
#12 0xb390d45c in Soprano::ODBC::Connection::execute
(this=this@entry=0x8f2d7d0, request=..., params=...) at
/usr/src/debug/soprano-2.9.4/backends/virtuoso/odbcconnection.cpp:158
#13 0xb390e07b in Soprano::ODBC::Connection::executeQuery
(this=this@entry=0x8f2d7d0, request=...) at
/usr/src/debug/soprano-2.9.4/backends/virtuoso/odbcconnection.cpp:89
#14 0xb38fbb5f in Soprano::VirtuosoModelPrivate::sqlQuery
(this=this@entry=0x8d48500, query=...) at
/usr/src/debug/soprano-2.9.4/backends/virtuoso/virtuosomodel.cpp:128
#15 0xb38fbd00 in Soprano::VirtuosoModelPrivate::sparqlQuery (this=0x8d48500,
query=...) at
/usr/src/debug/soprano-2.9.4/backends/virtuoso/virtuosomodel.cpp:148
#16 0xb38fbf2a in Soprano::VirtuosoModel::executeQuery (this=0x8defa88,
query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...)
at /usr/src/debug/soprano-2.9.4/backends/virtuoso/virtuosomodel.cpp:485
#17 0x4da496c2 in Nepomuk2::MainModel::executeQuery (this=0x8de5148, query=...,
language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at
/usr/src/debug/nepomuk-core-4.12.2/libnepomukcore/resource/nepomukmainmodel.cpp:191
#18 0x4da3e526 in Nepomuk2::ResourceData::determineUri
(this=this@entry=0x8f230a8) at
/usr/src/debug/nepomuk-core-4.12.2/libnepomukcore/resource/resourcedata.cpp:638
#19 0x4da4a892 in Nepomuk2::Resource::determineFinalResourceData
(this=0xb23ff1d0) at
/usr/src/debug/nepomuk-core-4.12.2/libnepomukcore/resource/resource.cpp:760
#20 0x4da4b802 in Nepomuk2::Resource::setWatchEnabled
(this=this@entry=0xb23ff1d0, status=status@entry=false) at
[kontact] [Bug 329900] New: Kontact Summary no updates new Popup Notes
https://bugs.kde.org/show_bug.cgi?id=329900 Bug ID: 329900 Summary: Kontact Summary no updates new Popup Notes Classification: Unclassified Product: kontact Version: 4.11.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: apcomp...@gmail.com If I create a new Popup Note in Kontact, it should be appear immediately in Summary, but it doesn't until I restart Kontact. 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
[Akonadi] [Bug 301182] Mail dispatcher agent stops working
https://bugs.kde.org/show_bug.cgi?id=301182 Brallan Aguilar apcomp...@gmail.com changed: What|Removed |Added CC||apcomp...@gmail.com --- Comment #10 from Brallan Aguilar apcomp...@gmail.com --- I have the same bug. I'm using KDE 4.11.3 :s -- 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 327256] New: Summary doesn't show upcoming events
https://bugs.kde.org/show_bug.cgi?id=327256 Bug ID: 327256 Summary: Summary doesn't show upcoming events Classification: Unclassified Product: kontact Version: 4.11.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: summary Assignee: kdepim-bugs@kde.org Reporter: apcomp...@gmail.com I have some events in my calendar. The problem is showing upcoming events in Kontact/Summary. If there are a birthday, anniversary within period specified in settings or at least one event today , these ones are showed in Upcoming events, only these cases. So, if there is at least one event (excluding birthdays or anniversaries) within the same period, this one aren't showed by Upcoming events. Reproducible: Always Steps to Reproduce: 1. Add a new event (neither birthdays nor anniversaries, within specified period in Kontact settings to show events) Actual Results: The event doesn't appear in Upcoming events Expected Results: All events within valid period must be showed in Upcoming events I added new calendars (I'm using iCal files) and put new events, but exhibit same behavior. -- 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 323883] New: Akonadi IMAP resource crashed while I shutdown PC
https://bugs.kde.org/show_bug.cgi?id=323883 Bug ID: 323883 Summary: Akonadi IMAP resource crashed while I shutdown PC Classification: Unclassified Product: Akonadi Version: 4.10 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: apcomp...@gmail.com CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.10) KDE Platform Version: 4.10.5 Qt Version: 4.8.5 Operating System: Linux 3.10.7-200.fc19.i686.PAE i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I simply shutdown my pc and the error appeared. Before that, Kontact was opened. I closed it, but possibly it wasn't correctly -- Backtrace: Application: Personal of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/libthread_db.so.1. [Current thread is 1 (Thread 0xb65bd7c0 (LWP 1620))] Thread 3 (Thread 0xb47ffb40 (LWP 29901)): #0 __pthread_mutex_unlock_usercnt (decr=1, mutex=0xb34016e0) at pthread_mutex_unlock.c:69 #1 __GI___pthread_mutex_unlock (mutex=0xb34016e0) at pthread_mutex_unlock.c:297 #2 0x4149c301 in g_mutex_unlock (mutex=mutex@entry=0xb3401668) at gthread-posix.c:229 #3 0x41457e12 in g_main_context_check (context=context@entry=0xb3401668, max_priority=2147483647, fds=fds@entry=0xb340bd28, n_fds=n_fds@entry=1) at gmain.c:3543 #4 0x414583ba in g_main_context_iterate (context=context@entry=0xb3401668, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at gmain.c:3698 #5 0x41458569 in g_main_context_iteration (context=0xb3401668, may_block=1) at gmain.c:3762 #6 0x41d39b7f in QEventDispatcherGlib::processEvents (this=0xb3405460, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #7 0x41d08444 in QEventLoop::processEvents (this=this@entry=0xb47ff1f8, flags=...) at kernel/qeventloop.cpp:149 #8 0x41d08781 in QEventLoop::exec (this=this@entry=0xb47ff1f8, flags=...) at kernel/qeventloop.cpp:204 #9 0x41bf3a9d in QThread::exec (this=this@entry=0x9423da8) at thread/qthread.cpp:536 #10 0xb74a80f4 in KIMAP::SessionThread::run (this=0x9423da8) at /usr/src/debug/kdepimlibs-4.10.5/kimap/sessionthread.cpp:188 #11 0x41bf6450 in QThreadPrivate::start (arg=0x9423da8) at thread/qthread_unix.cpp:338 #12 0x45ee09da in start_thread (arg=0xb47ffb40) at pthread_create.c:308 #13 0x45e1192e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xb538ab40 (LWP 30246)): #0 0xb7759424 in __kernel_vsyscall () #1 0x45ee71db in write () at ../sysdeps/unix/syscall-template.S:81 #2 0x4149b496 in g_wakeup_signal (wakeup=0x9383898) at gwakeup.c:238 #3 0x41458f8f in g_main_context_wakeup (context=optimized out) at gmain.c:4317 #4 0x41d39d6c in QEventDispatcherGlib::wakeUp (this=0x9385d90) at kernel/qeventdispatcher_glib.cpp:581 #5 0x41d0d66d in QCoreApplication::postEvent (receiver=receiver@entry=0x9504d80, event=event@entry=0xb483fbd0, priority=priority@entry=0) at kernel/qcoreapplication.cpp:1395 #6 0x41d0d76c in QCoreApplication::postEvent (receiver=0x9504d80, event=event@entry=0xb483fbd0) at kernel/qcoreapplication.cpp:1307 #7 0x41d1eed6 in queued_activate (argv=optimized out, c=0xb484, signal=optimized out, sender=optimized out) at kernel/qobject.cpp:3427 #8 QMetaObject::activate (sender=sender@entry=0x9592338, m=m@entry=0xb74dfa9c KIMAP::SessionThread::staticMetaObject, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0xb5389c48) at kernel/qobject.cpp:3503 #9 0xb74a90c9 in responseReceived (_t1=..., this=0x9592338) at /usr/src/debug/kdepimlibs-4.10.5/i686-redhat-linux-gnu/kimap/moc_sessionthread_p.cpp:133 #10 KIMAP::SessionThread::readMessage (this=0x9592338) at /usr/src/debug/kdepimlibs-4.10.5/kimap/sessionthread.cpp:124 #11 0xb74a9fc0 in KIMAP::SessionThread::qt_static_metacall (_o=0xfe00, _id=8, _a=0xb485b9a0, _c=optimized out) at /usr/src/debug/kdepimlibs-4.10.5/i686-redhat-linux-gnu/kimap/moc_sessionthread_p.cpp:78 #12 0x41d1b32b in QMetaCallEvent::placeMetaCall (this=0xb485b9c0, object=0x9592338) at kernel/qobject.cpp:524 #13 0x41d2330b in QObject::event (this=0x9592338, e=0xb485b9c0) at kernel/qobject.cpp:1194 #14 0x47424174 in QApplicationPrivate::notify_helper (this=0x93a9cd0, receiver=0x9592338, e=0xb485b9c0) at kernel/qapplication.cpp:4562 #15 0x4742ac89 in QApplication::notify (this=0xbfa305c4, receiver=receiver@entry=0x9592338, e=e@entry=0xb485b9c0) at kernel/qapplication.cpp:4348 #16 0xb6d352f5 in KApplication::notify (this=0xbfa305c4, receiver=0x9592338, event=0xb485b9c0) at /usr/src/debug/kdelibs-4.10.5/kdeui/kernel/kapplication.cpp:311 #17 0x41d09a3a in QCoreApplication::notifyInternal (this=0xbfa305c4, receiver=receiver@entry=0x9592338,
[kontact] [Bug 320449] New: Kontact crashes on second start up
https://bugs.kde.org/show_bug.cgi?id=320449 Bug ID: 320449 Summary: Kontact crashes on second start up Classification: Unclassified Product: kontact Version: 4.10.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: brallanagui...@riseup.net Application: kontact (4.10.3) KDE Platform Version: 4.10.3 Qt Version: 4.8.4 Operating System: Linux 3.9.4-200.fc18.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I started Kontact normally, then I closed it (worked well all the time). After that, I opened again and an error had appeared. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/libthread_db.so.1. [Current thread is 1 (Thread 0xb761c780 (LWP 1989))] Thread 4 (Thread 0xb62ebb40 (LWP 1990)): #0 0xb77a3424 in __kernel_vsyscall () #1 0x4749018c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:171 #2 0x44fd6f05 in WTF::TCMalloc_PageHeap::scavengerThread (this=this@entry=0x458086c0 WTF::pageheap_memory) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:2571 #3 0x44fd6f40 in WTF::TCMalloc_PageHeap::runScavengerThread (context=0x458086c0 WTF::pageheap_memory) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/FastMalloc.cpp:1767 #4 0x4748caff in start_thread (arg=0xb62ebb40) at pthread_create.c:308 #5 0x473c30be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 3 (Thread 0xb59b9b40 (LWP 1992)): #0 0xb77a3424 in __kernel_vsyscall () #1 0x4749018c in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i486/pthread_cond_wait.S:171 #2 0x45006a44 in WTF::ThreadCondition::wait (this=0xb5a307dc, mutex=...) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:379 #3 0x44d0c2c3 in JSC::BlockAllocator::blockFreeingThreadMain (this=0xb5a30750) at /usr/src/debug/webkit-qtwebkit-23/Source/JavaScriptCore/heap/BlockAllocator.cpp:128 #4 0x44fec8a5 in WTF::threadEntryPoint (contextData=0xb59e4be0) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/Threading.cpp:69 #5 0x450065b3 in WTF::wtfThreadEntryPoint (param=0x9a495b8) at /usr/src/debug/webkit-qtwebkit-23/Source/WTF/wtf/ThreadingPthreads.cpp:196 #6 0x4748caff in start_thread (arg=0xb59b9b40) at pthread_create.c:308 #7 0x473c30be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 2 (Thread 0xb2884b40 (LWP 2080)): #0 0xb77a3424 in __kernel_vsyscall () #1 0x473b8bab in poll () at ../sysdeps/unix/syscall-template.S:81 #2 0x4767332c in g_poll () from /lib/libglib-2.0.so.0 #3 0x47664480 in g_main_context_iterate.isra.22 () from /lib/libglib-2.0.so.0 #4 0x476645e2 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x47cbaadf in QEventDispatcherGlib::processEvents (this=0xb1f00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x47c86a6d in QEventLoop::processEvents (this=this@entry=0xb2884218, flags=...) at kernel/qeventloop.cpp:149 #7 0x47c86d69 in QEventLoop::exec (this=0xb2884218, flags=...) at kernel/qeventloop.cpp:204 #8 0x47b6f0dc in QThread::exec (this=this@entry=0x9c9e098) at thread/qthread.cpp:542 #9 0x47b6f23c in QThread::run (this=0x9c9e098) at thread/qthread.cpp:609 #10 0x47b7256a in QThreadPrivate::start (arg=0x9c9e098) at thread/qthread_unix.cpp:338 #11 0x4748caff in start_thread (arg=0xb2884b40) at pthread_create.c:308 #12 0x473c30be in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 1 (Thread 0xb761c780 (LWP 1989)): [KCrash Handler] #7 0x46f41eab in QString (other=..., this=0xbfd60da8) at /usr/include/QtCore/qstring.h:725 #8 KontactInterface::Plugin::identifier (this=0x9d0b650) at /usr/src/debug/kdepimlibs-4.10.3/kontactinterface/plugin.cpp:102 #9 0x45873ef1 in activateInitialPluginModule (this=0x45873fd6 Kontact::MainWindow::setInitialActivePluginModule(QString const)+54) at /usr/src/debug/kdepim-4.10.3/kontact/src/mainwindow.cpp:325 #10 Kontact::MainWindow::activateInitialPluginModule (this=0x45873fd6 Kontact::MainWindow::setInitialActivePluginModule(QString const)+54) at /usr/src/debug/kdepim-4.10.3/kontact/src/mainwindow.cpp:320 #11 0xbfd6103c in ?? () Backtrace stopped: previous frame inner to this frame (corrupt stack?) Possible duplicates by query: bug 315612, bug 313028, bug 306003, bug 304391, bug 302939. Reported using DrKonqi -- 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 318477] New: Kmail is slow to adjunct a file
https://bugs.kde.org/show_bug.cgi?id=318477 Bug ID: 318477 Summary: Kmail is slow to adjunct a file Classification: Unclassified Product: kmail2 Version: 4.10.2 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-bugs@kde.org Reporter: brallanagui...@riseup.net I create a new message. When I want to adjunct a file, I select de Adjunct... menu. Appear a dialog window to select the file, but when I want to scroll it, is very slow and when finally it scroll (lasts several seconds) I select the file and lasts several seconds again to choose. Reproducible: Always Steps to Reproduce: 1. Create a new email 2. Adjunct a file 3. Actual Results: I select the file to attach, but it lasts a long time. Kmail doesn't crashes. Expected Results: Do not get stuck while moving the scrollbar or select a file. Moving the scrollbar or selecting a file consumes a lot of processor. -- 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 309728] Akonadi IMAP resource crashes when I shutdown or reboot my system
https://bugs.kde.org/show_bug.cgi?id=309728 --- Comment #5 from Brallan Aguilar brallanagui...@riseup.net --- Created attachment 78564 -- https://bugs.kde.org/attachment.cgi?id=78564action=edit New crash information added by DrKonqi akonadi_imap_resource (4.10) on KDE Platform 4.10.1 using Qt 4.8.4 - What I was doing when the application crashed: I had opened Kontact when I restart my PC and the error appeared. -- Backtrace (Reduced): #8 QSharedDataPointer (o=..., this=0xbf8f33ec) at /usr/include/QtCore/qshareddata.h:93 #9 assignEntityPrivate (one=..., other=...) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/entity.cpp:49 #10 0x45ff0440 in Akonadi::Entity::Entity (this=0xbf8f34ac, other=...) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/entity.cpp:56 #11 0x460246d4 in Akonadi::Collection::Collection (this=0xbf8f34ac, other=...) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/collection.cpp:72 #12 0x460e3925 in Task (this=0xbf8f34a0) at /usr/src/debug/kdepimlibs-4.10.1/akonadi/resourcescheduler_p.h:67 -- 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
[Akonadi] [Bug 315492] New: Akonadi crashes when I restart my PC
https://bugs.kde.org/show_bug.cgi?id=315492 Bug ID: 315492 Summary: Akonadi crashes when I restart my PC Classification: Unclassified Product: Akonadi Version: 4.9 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: IMAP resource Assignee: er...@kde.org Reporter: brallanagui...@riseup.net CC: kdepim-bugs@kde.org, vkra...@kde.org Application: akonadi_imap_resource (4.9) KDE Platform Version: 4.9.5 Qt Version: 4.8.4 Operating System: Linux 3.7.8-202.fc18.i686 i686 Distribution (Platform): Fedora RPMs -- Information about the crash: - What I was doing when the application crashed: I've opened KMail when I decided to restart my computer. When it was logout, the error appeared -- Backtrace: Application: Personal of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault Using host libthread_db library /lib/libthread_db.so.1. [Current thread is 1 (Thread 0xb76fb780 (LWP 1662))] Thread 4 (Thread 0xb65b3b40 (LWP 1711)): #0 0x4ba37e1a in g_source_iter_next () from /lib/libglib-2.0.so.0 #1 0x4ba39ebd in g_main_context_check () from /lib/libglib-2.0.so.0 #2 0x4ba3a412 in g_main_context_iterate.isra.22 () from /lib/libglib-2.0.so.0 #3 0x4ba3a5e2 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #4 0x41757aef in QEventDispatcherGlib::processEvents (this=0xb5c00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #5 0x41723b2d in QEventLoop::processEvents (this=this@entry=0xb65b31f8, flags=...) at kernel/qeventloop.cpp:149 #6 0x41723e29 in QEventLoop::exec (this=0xb65b31f8, flags=...) at kernel/qeventloop.cpp:204 #7 0x4160c0ac in QThread::exec (this=0x9c03570) at thread/qthread.cpp:542 #8 0x46ca6034 in KIMAP::SessionThread::run (this=0x9c03570) at /usr/src/debug/kdepimlibs-4.9.5/kimap/sessionthread.cpp:182 #9 0x4160f53a in QThreadPrivate::start (arg=0x9c03570) at thread/qthread_unix.cpp:338 #10 0x4b8aaaff in start_thread (arg=0xb65b3b40) at pthread_create.c:308 #11 0x4b7e109e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 3 (Thread 0xb4dffb40 (LWP 3278)): #0 0xb7731424 in __kernel_vsyscall () #1 0x4b8b11db in read () at ../sysdeps/unix/syscall-template.S:81 #2 0x4ba7bbc6 in g_wakeup_acknowledge () from /lib/libglib-2.0.so.0 #3 0x4ba39fab in g_main_context_check () from /lib/libglib-2.0.so.0 #4 0x4ba3a412 in g_main_context_iterate.isra.22 () from /lib/libglib-2.0.so.0 #5 0x4ba3a5e2 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #6 0x41757aef in QEventDispatcherGlib::processEvents (this=0xb4f00468, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #7 0x41723b2d in QEventLoop::processEvents (this=this@entry=0xb4dff1f8, flags=...) at kernel/qeventloop.cpp:149 #8 0x41723e29 in QEventLoop::exec (this=0xb4dff1f8, flags=...) at kernel/qeventloop.cpp:204 #9 0x4160c0ac in QThread::exec (this=0x9bc7920) at thread/qthread.cpp:542 #10 0x46ca6034 in KIMAP::SessionThread::run (this=0x9bc7920) at /usr/src/debug/kdepimlibs-4.9.5/kimap/sessionthread.cpp:182 #11 0x4160f53a in QThreadPrivate::start (arg=0x9bc7920) at thread/qthread_unix.cpp:338 #12 0x4b8aaaff in start_thread (arg=0xb4dffb40) at pthread_create.c:308 #13 0x4b7e109e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 2 (Thread 0xb59ffb40 (LWP 3336)): #0 0x4b8ac900 in __GI___pthread_mutex_lock (mutex=0xb5005070) at pthread_mutex_lock.c:95 #1 0x4ba7c961 in g_mutex_lock () from /lib/libglib-2.0.so.0 #2 0x4ba39686 in g_main_context_acquire () from /lib/libglib-2.0.so.0 #3 0x4ba3a329 in g_main_context_iterate.isra.22 () from /lib/libglib-2.0.so.0 #4 0x4ba3a5e2 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #5 0x41757aef in QEventDispatcherGlib::processEvents (this=0xb5006878, flags=...) at kernel/qeventdispatcher_glib.cpp:426 #6 0x41723b2d in QEventLoop::processEvents (this=this@entry=0xb59ff1f8, flags=...) at kernel/qeventloop.cpp:149 #7 0x41723e29 in QEventLoop::exec (this=0xb59ff1f8, flags=...) at kernel/qeventloop.cpp:204 #8 0x4160c0ac in QThread::exec (this=0x9afe488) at thread/qthread.cpp:542 #9 0x46ca6034 in KIMAP::SessionThread::run (this=0x9afe488) at /usr/src/debug/kdepimlibs-4.9.5/kimap/sessionthread.cpp:182 #10 0x4160f53a in QThreadPrivate::start (arg=0x9afe488) at thread/qthread_unix.cpp:338 #11 0x4b8aaaff in start_thread (arg=0xb59ffb40) at pthread_create.c:308 #12 0x4b7e109e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:132 Thread 1 (Thread 0xb76fb780 (LWP 1662)): [KCrash Handler] #7 ref (this=0x70706124) at /usr/include/QtCore/qatomic_i386.h:120 #8 QSharedDataPointer (o=..., this=0xbfeccb2c) at /usr/include/QtCore/qshareddata.h:93 #9 assignEntityPrivate (one=..., other=...) at /usr/src/debug/kdepimlibs-4.9.5/akonadi/entity.cpp:49 #10 0x46457070 in Akonadi::Entity::Entity (this=0xbfeccbec, other=...) at
[Bug 265498] kontact crash on quit
https://bugs.kde.org/show_bug.cgi?id=265498 Brallan Aguilar brallanagui...@riseup.net changed: What|Removed |Added CC||brallanagui...@riseup.net -- 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 265498] kontact crash on quit
https://bugs.kde.org/show_bug.cgi?id=265498 --- Comment #6 from Brallan Aguilar brallanagui...@riseup.net --- Created attachment 74276 -- https://bugs.kde.org/attachment.cgi?id=74276action=edit New crash information added by DrKonqi kontact (4.9.1) on KDE Platform 4.9.1 using Qt 4.8.2 - What I was doing when the application crashed: Simply I pressed CTRL + Q to close the app, finally it crashed. -- Backtrace (Reduced): #8 0x41a06d73 in KWallet::Wallet::openWallet (name=..., w=33554450, ot=KWallet::Wallet::Synchronous) at /usr/src/debug/kdelibs-4.9.1/kdeui/util/kwallet.cpp:496 #9 0x459da71e in MailTransport::TransportManager::wallet (this=0x97bfb28) at /usr/src/debug/kdepimlibs-4.9.1/mailtransport/transportmanager.cpp:606 #10 0x459d183d in MailTransport::Transport::readPassword (this=0x9bc2268) at /usr/src/debug/kdepimlibs-4.9.1/mailtransport/transport.cpp:314 #11 0x459d220c in qt_static_metacall (_id=0, _o=0x9bc2268, _c=optimized out, _a=optimized out) at /usr/src/debug/kdepimlibs-4.9.1/i686-redhat-linux-gnu/mailtransport/transport.moc:48 #12 MailTransport::Transport::qt_static_metacall (_o=0x9bc2268, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xb5e8868) at /usr/src/debug/kdepimlibs-4.9.1/i686-redhat-linux-gnu/mailtransport/transport.moc:42 -- 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
