[Akonadi] [Bug 326561] support for recurrence and percentage of completion in google tasks
https://bugs.kde.org/show_bug.cgi?id=326561 --- Comment #2 from Martin Tlustos martin.tlus...@gmail.com --- No problem. But it actually does exactly this already anyway. When kde-specific data is not supported by google, it is written into the notes field, google-specific data is displayed in kaddressbook on the own fields tab. -- 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
[kmail2] [Bug 326865] New: Cannot retrieve emails
https://bugs.kde.org/show_bug.cgi?id=326865
Bug ID: 326865
Summary: Cannot retrieve emails
Classification: Unclassified
Product: kmail2
Version: 4.10.5
Platform: Debian testing
OS: Linux
Status: UNCONFIRMED
Severity: grave
Priority: NOR
Component: general
Assignee: kdepim-bugs@kde.org
Reporter: marcus.ha...@iwr.fzk.de
I cannot retrieve new emails. It worked yesterday, and I know i got new emails.
I stopped kmail2, I killed anything matching on akonadi using
ps aux |grep akonadi |grep -v grep | awk '{ print $2 }' | xargs kill
I restarted kmail2 (which bothers me with some offline tale, asking me to
click something here
The progress bar shows Mail Filter Agent 0%
A big thank you for making me an unvoluntary beta tester!
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 326867] New: Kmail crashed when closed
https://bugs.kde.org/show_bug.cgi?id=326867 Bug ID: 326867 Summary: Kmail crashed when closed Classification: Unclassified Product: kontact Version: 4.10.5 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: paul.mil...@desy.de Application: kontact (4.10.5) KDE Platform Version: 4.10.5 Qt Version: 4.8.6 Operating System: Linux 3.11-1-686-pae i686 Distribution: Debian GNU/Linux unstable (sid) -- Information about the crash: - What I was doing when the application crashed: I closed kmail normally and it crashed. I believe kmail was dormant when I closed it; i.e., I believe it was *not* sync-ing with any of my email accounts at the time I told it to close. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib/i386-linux-gnu/i686/cmov/libthread_db.so.1. [Current thread is 1 (Thread 0xb2580740 (LWP 25060))] Thread 3 (Thread 0xafea1b40 (LWP 25086)): #0 0xb7787424 in __kernel_vsyscall () #1 0xb3c5b7ab in pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_wait.S:187 #2 0xb60e42ac in __pthread_cond_wait (cond=0xb5f8ee30, mutex=0xb5f8ee18) at forward.c:149 #3 0xb5837de9 in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #4 0xb5837e7f in ?? () from /usr/lib/i386-linux-gnu/libQtWebKit.so.4 #5 0xb3c57cf1 in start_thread (arg=0xafea1b40) at pthread_create.c:311 #6 0xb60d708e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 2 (Thread 0xaf580b40 (LWP 25087)): #0 0xb3c59d33 in __GI___pthread_mutex_lock (mutex=0xaec00558) at pthread_mutex_lock.c:95 #1 0xb60e44b4 in pthread_mutex_lock (mutex=0xaec00558) at forward.c:192 #2 0xb3bc2e90 in g_mutex_lock (mutex=mutex@entry=0xaec004e0) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gthread-posix.c:210 #3 0xb3b7fd3d in g_main_context_prepare (context=context@entry=0xaec004e0, priority=priority@entry=0xaf580148) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3330 #4 0xb3b8064f in g_main_context_iterate (context=context@entry=0xaec004e0, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3681 #5 0xb3b80898 in g_main_context_iteration (context=0xaec004e0, may_block=1) at /build/glib2.0-Ot8bbC/glib2.0-2.36.4/./glib/gmain.c:3762 #6 0xb6edd23f in QEventDispatcherGlib::processEvents (this=0xaec00468, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #7 0xb6eac163 in QEventLoop::processEvents (this=this@entry=0xaf580258, flags=...) at kernel/qeventloop.cpp:149 #8 0xb6eac489 in QEventLoop::exec (this=this@entry=0xaf580258, flags=...) at kernel/qeventloop.cpp:204 #9 0xb6d980bd in QThread::exec (this=this@entry=0x85fbe68) at thread/qthread.cpp:537 #10 0xb6d9820b in QThread::run (this=0x85fbe68) at thread/qthread.cpp:604 #11 0xb6d9aa4f in QThreadPrivate::start (arg=0x85fbe68) at thread/qthread_unix.cpp:349 #12 0xb3c57cf1 in start_thread (arg=0xaf580b40) at pthread_create.c:311 #13 0xb60d708e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:131 Thread 1 (Thread 0xb2580740 (LWP 25060)): [KCrash Handler] #7 0x0010 in ?? () #8 0xb75fc1d9 in KWallet::Wallet::openWallet (name=..., w=39846232, ot=ot@entry=KWallet::Wallet::Synchronous) at ../../kdeui/util/kwallet.cpp:496 #9 0xae0c09aa in MailTransport::TransportManager::wallet (this=0x888d498) at ../../mailtransport/transportmanager.cpp:583 #10 0xae0bcae5 in MailTransport::Transport::readPassword (this=0x8a30fa0) at ../../mailtransport/transport.cpp:305 #11 0xae0c1cf0 in MailTransport::TransportManager::loadPasswords (this=0x888d498) at ../../mailtransport/transportmanager.cpp:608 #12 0xae0c1f43 in MailTransport::TransportManager::loadPasswordsAsync (this=0x888d498) at ../../mailtransport/transportmanager.cpp:658 #13 0xae0c523c in MailTransport::TransportManagerPrivate::readConfig (this=this@entry=0x8a14b08) at ../../mailtransport/transportmanager.cpp:467 #14 0xae0c589d in MailTransport::TransportManagerPrivate::slotTransportsChanged (this=0x8a14b08) at ../../mailtransport/transportmanager.cpp:546 #15 0xae0c5a1e in MailTransport::TransportManager::qt_static_metacall (_o=_o@entry=0x888d498, _c=_c@entry=QMetaObject::InvokeMetaMethod, _id=_id@entry=12, _a=_a@entry=0xbfa2744c) at ./moc_transportmanager.cpp:103 #16 0xae0c5dbc in MailTransport::TransportManager::qt_metacall (this=0x888d498, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfa2744c) at ./moc_transportmanager.cpp:147 #17 0xb44cb266 in QDBusConnectionPrivate::deliverCall (this=0x85dfe38, object=object@entry=0x888d498, msg=..., metaTypes=..., slotIdx=16) at qdbusintegrator.cpp:951 #18 0xb44d436d in QDBusCallDeliveryEvent::placeMetaCall (this=0x879b760, object=0x888d498) at qdbusintegrator_p.h:103 #19
[kmail2] [Bug 298277] Can't remove or move folders
https://bugs.kde.org/show_bug.cgi?id=298277 Cédric Bellegarde gnu...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #3 from Cédric Bellegarde gnu...@gmail.com --- Can't reproduce anymore -- 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 326704] akonadi_nepomuk_feeder using large amounts of memory after rebuild of Akonadi database
https://bugs.kde.org/show_bug.cgi?id=326704 --- Comment #4 from Vishesh Handa m...@vhanda.in --- Confirmed. I can reproduce this in a small test case. The leak seems to be in the Akonadi libs. I'll bring this up during the PIM sprint and we can investigate. -- 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 326561] support for recurrence and percentage of completion in google tasks
https://bugs.kde.org/show_bug.cgi?id=326561 --- Comment #3 from Daniel Vrátil dvra...@redhat.com --- Yes, but the contacts API specifies a way how to store custom metadata in contacts (that we then convert into X-KDE-Something key, as specified in vCard standard). The tasks API does not however specify any way to submit custom metadata. -- 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 326867] kontact crashed when closed
https://bugs.kde.org/show_bug.cgi?id=326867 Jekyll Wu adap...@gmail.com changed: What|Removed |Added Summary|Kmail crashed when closed |kontact crashed when closed -- 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 326874] New: Local folder offline
https://bugs.kde.org/show_bug.cgi?id=326874 Bug ID: 326874 Summary: Local folder offline Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: Debian unstable OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: folders Assignee: kdepim-bugs@kde.org Reporter: tipos...@tiscali.it For some reasons, my local folders are offline, as a result it won't send emails (it should send using sendmail locally). It seems already weird to have local folders that went offline (I didn't do that) but I guess it could in some rare cases make sense. However the problem is that it won't go back in online mode, so my outgoing email is not sent. Mutt sends email like a charm, so my server is configured properly. Reproducible: Always Steps to Reproduce: I have no idea how this happened. -- 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 326874] Local folder offline
https://bugs.kde.org/show_bug.cgi?id=326874 --- Comment #1 from Salvo LtWorf Tomaselli tipos...@tiscali.it --- Created attachment 83223 -- https://bugs.kde.org/attachment.cgi?id=83223action=edit Screenshot Screenshot, in case I sound unbelievable. -- 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
[kmail] [Bug 119604] Offline-ness should extend to local folders
https://bugs.kde.org/show_bug.cgi?id=119604 Salvo LtWorf Tomaselli tipos...@tiscali.it changed: What|Removed |Added CC||tipos...@tiscali.it --- Comment #4 from Salvo LtWorf Tomaselli tipos...@tiscali.it --- Could this bug be triaged since that version of kmail doesn't exist anymore? -- 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 323970] kontact summery for korganizer does not include google calendar events
https://bugs.kde.org/show_bug.cgi?id=323970 matzet...@googlemail.com changed: What|Removed |Added CC||matzet...@googlemail.com --- Comment #2 from matzet...@googlemail.com --- Same issue with my installation from the Arch repos. -- 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 326884] New: kmail removes final newline when saving .csv attachment
https://bugs.kde.org/show_bug.cgi?id=326884 Bug ID: 326884 Summary: kmail removes final newline when saving .csv attachment Classification: Unclassified Product: kmail2 Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jwag...@computing.dcu.ie Observed in KDE / Kontact 4.8.5 r2: Saving a .csv attachment produces a file 1 byte smaller than the original. The missing byte is the last newline. While entering the bug, I remember having a virtual machine with KDE 4.11.2 and the bug does not occur there. I submit the bug report anyway so that people know that it may be fixed in a more recent KDE. Reproducible: Always Steps to Reproduce: 1. create a test file, for example echo test test.csv 2. attach test.csv to an e-mail (leaving attachment properties to default: type text/csv, encoding: 7bit) 3. receive e-mail 4. right click on attachment at end of e-mail and choose save, for example as test-v2.csv 5. compare files with diff and cmp Actual Results: diff: No newline at end of file cmp: EOF on test-v2.csv Expected Results: diff: no output (no difference) cmp: no output (no difference) (1) All newlines involved (including newlines in the mbox file if saving the full message) are just 0x0a. No CR LF newlines. (2) Reproduced with a real-world .csv file, head and tail of the latter file and the 1-line echo test test.csv file on 4.8.5 r2. Workaround: echo test-v2.csv after saving adds the missing newline. -- 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 326890] New: kmail eats memory and misbehaves if certificate details dialogue is closed
https://bugs.kde.org/show_bug.cgi?id=326890 Bug ID: 326890 Summary: kmail eats memory and misbehaves if certificate details dialogue is closed Classification: Unclassified Product: kmail2 Version: 4.11.2 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: jwag...@computing.dcu.ie When the SMTP server uses a self-signed certificate, kmail asks whether to trust the certificate. However, if one clicks on Details and leaves the details dialogue with the only button Close, the former dialogue is also gone and the mail dispatcher starts using more and more memory. Within minutes, heavy swap activity starts. Reproducible: Always Steps to Reproduce: 1. Create fresh user and set up kmail (in my test, I first configured a pop3 source) 2. Configure an account for sending with SMTP, TLS and authentication; the outgoing server uses a self-signed certificate in this test 3. Send an e-mail (test body 123) 4. Password dialogue for sending e-mail: enter password and continue 5. Dialogue certificate not signed by trusted authority (actual text is a bit longer) - click Details 6. Click Close (that's the only way forward) Actual Results: The dialogue certificate not signed by trusted authority is missing on the screen and in top on the command line, one can see /usr/bin/akonadi_maildispatcher_agent growing RSS memory allocation. On my virtual machine, memory use grows at approximately 10 MiB per second (30 MiB per top refresh). I started observing this at around 240 MiB and killed the agent when it reached 1 GiB. After killing the process, the password dialogue re-appears in kmail but after completing it again, the certificate dialogue does still not show. Furthermore, the workaround below indicates that the certificate has been stored as trusted permanently. Expected Results: After clicking Close, the dialogue certificate not signed by trusted authority should be on the screen again (it should be behind the details dialogue - sorry didn't check moving the details dialogue to the side to see whether it is there while the other dialogue is shown). Furthermore, the akonadi mail dispatcher agent should not use over 1 GiB of memory as a reaction to some unexpected behavior from the GUI application. Finally, no decision as to whether the certificate can be trusted should be stored since the user did not make any decision (the user only reviewed the details and hit Close). Workaround: After reviewing the certificate, finding it trustworthy and clicking Close, kill the mail dispatcher (you should soon see it as a process using a lot of memory in top or any other system information tool) and restart. Apparently, the certificate has been marked as trust permanently. If there is an issue with the certificate, maybe (I didn't test this) it is not too late if you haven't pressed Close yet. If so, maybe a restart prevents the certificate details from being accepted. -- 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 324807] Sends no UID in UID STORE command
https://bugs.kde.org/show_bug.cgi?id=324807 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||4.11.3 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/498d6678f478bd1bd9bd ||c944bb790f6b16b7ade4 --- Comment #9 from Daniel Vrátil dvra...@redhat.com --- Git commit 498d6678f478bd1bd9bdc944bb790f6b16b7ade4 by Dan Vrátil. Committed on 30/10/2013 at 15:46. Pushed by dvratil into branch 'KDE/4.11'. Wait for changes from resource to be written to Akonadi before marking change as processed This fixes a problem with invalid RIDs after inter-resource moves. When there is an another changeReplay for the just moved item scheduled in the new parent resource, the item will have invalid RID (or rather RID assigned to it by the previous parent resource). It's because the ItemModifyJob dispatched from ResourceBase::changesCommitted() with the new RID is not finished yet when the next task is dispatched, and so the item in resource's EntityCache is not invalidated and the resource will use it instead of the updated one. By waiting for the ItemModifyJob dispatched from changesCommited() to finish before marking the change as processed and dispatching next task we make sure that in case the next task involves the same item the change will be stored in Akonadi and the item will be invalidated in local caches, forcing the resource to fetch the item again from Akonadi before starting the task. This fixes 'Invalid uidset' error reported by IMAP resources after the MailDispatcher agent moves the mail from local Outbox to remote Sent folder and updates it's flags. Related: bug 323762, bug 314964 FIXED-IN: 4.11.3 M +11 -5akonadi/resourcebase.cpp http://commits.kde.org/kdepimlibs/498d6678f478bd1bd9bdc944bb790f6b16b7ade4 -- 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 314964] after deleting large number of email, Invalid uidset errors
https://bugs.kde.org/show_bug.cgi?id=314964 --- Comment #4 from Daniel Vrátil dvra...@redhat.com --- Git commit 498d6678f478bd1bd9bdc944bb790f6b16b7ade4 by Dan Vrátil. Committed on 30/10/2013 at 15:46. Pushed by dvratil into branch 'KDE/4.11'. Wait for changes from resource to be written to Akonadi before marking change as processed This fixes a problem with invalid RIDs after inter-resource moves. When there is an another changeReplay for the just moved item scheduled in the new parent resource, the item will have invalid RID (or rather RID assigned to it by the previous parent resource). It's because the ItemModifyJob dispatched from ResourceBase::changesCommitted() with the new RID is not finished yet when the next task is dispatched, and so the item in resource's EntityCache is not invalidated and the resource will use it instead of the updated one. By waiting for the ItemModifyJob dispatched from changesCommited() to finish before marking the change as processed and dispatching next task we make sure that in case the next task involves the same item the change will be stored in Akonadi and the item will be invalidated in local caches, forcing the resource to fetch the item again from Akonadi before starting the task. This fixes 'Invalid uidset' error reported by IMAP resources after the MailDispatcher agent moves the mail from local Outbox to remote Sent folder and updates it's flags. Related: bug 323762, bug 324807 FIXED-IN: 4.11.3 M +11 -5akonadi/resourcebase.cpp http://commits.kde.org/kdepimlibs/498d6678f478bd1bd9bdc944bb790f6b16b7ade4 -- 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 323762] IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added CC||martin.ruess...@gmx.net --- Comment #8 from Daniel Vrátil dvra...@redhat.com --- *** Bug 324804 has been marked as a duplicate of this bug. *** -- 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 324804] After sending a mail Akonadi gives »A000869 BAD expected DIGIT instead of«
https://bugs.kde.org/show_bug.cgi?id=324804 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||dvra...@redhat.com Resolution|--- |DUPLICATE --- Comment #1 from Daniel Vrátil dvra...@redhat.com --- *** This bug has been marked as a duplicate of bug 323762 *** -- 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 323762] IMAP error every time after sending mail and saving to sent-mail IMAP folder (kde 4.11.0)
https://bugs.kde.org/show_bug.cgi?id=323762 Daniel Vrátil dvra...@redhat.com changed: What|Removed |Added Status|CONFIRMED |RESOLVED Version Fixed In||4.11.3 Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kdep ||imlibs/498d6678f478bd1bd9bd ||c944bb790f6b16b7ade4 --- Comment #7 from Daniel Vrátil dvra...@redhat.com --- Git commit 498d6678f478bd1bd9bdc944bb790f6b16b7ade4 by Dan Vrátil. Committed on 30/10/2013 at 15:46. Pushed by dvratil into branch 'KDE/4.11'. Wait for changes from resource to be written to Akonadi before marking change as processed This fixes a problem with invalid RIDs after inter-resource moves. When there is an another changeReplay for the just moved item scheduled in the new parent resource, the item will have invalid RID (or rather RID assigned to it by the previous parent resource). It's because the ItemModifyJob dispatched from ResourceBase::changesCommitted() with the new RID is not finished yet when the next task is dispatched, and so the item in resource's EntityCache is not invalidated and the resource will use it instead of the updated one. By waiting for the ItemModifyJob dispatched from changesCommited() to finish before marking the change as processed and dispatching next task we make sure that in case the next task involves the same item the change will be stored in Akonadi and the item will be invalidated in local caches, forcing the resource to fetch the item again from Akonadi before starting the task. This fixes 'Invalid uidset' error reported by IMAP resources after the MailDispatcher agent moves the mail from local Outbox to remote Sent folder and updates it's flags. Related: bug 324807, bug 314964 FIXED-IN: 4.11.3 M +11 -5akonadi/resourcebase.cpp http://commits.kde.org/kdepimlibs/498d6678f478bd1bd9bdc944bb790f6b16b7ade4 -- 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
[kmail2] [Bug 323068] Exponential growth of CollectionFetchJobs (infinite loop)
https://bugs.kde.org/show_bug.cgi?id=323068 Martin martin.ruess...@gmx.net changed: What|Removed |Added CC||martin.ruess...@gmx.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
[kmail2] [Bug 326896] New: Execute Command filter inconsistent operation
https://bugs.kde.org/show_bug.cgi?id=326896 Bug ID: 326896 Summary: Execute Command filter inconsistent operation Classification: Unclassified Product: kmail2 Version: unspecified Platform: Mageia RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: misc Assignee: kdepim-bugs@kde.org Reporter: as9902...@gmail.com When Execute Command filter is executed on incoming messages from an IMAP server the body of the message is not fed into the child program. The child program is receiving only message headers. Reproducible: Always Steps to Reproduce: 1. add simple script to filters to execute command everytime a new email message is downloaded 2. let that script just output to file everything it gets from stdin 3. check the file Actual Results: You only get message headers without message body Expected Results: The whole message headers and message body should be passed After the message has been downloaded and you right-click and choose Apply Filters and select your filter with execute command with exact same script it works properly. It puts the whole email message (header+body) into the stdin of a child program. -- 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 326896] Execute Command filter inconsistent operation
https://bugs.kde.org/show_bug.cgi?id=326896 --- Comment #1 from Agron Selimaj as9902...@gmail.com --- Kmail version is 485 -- 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 326899] New: Kontact crashed right after start with heavy IO load
https://bugs.kde.org/show_bug.cgi?id=326899 Bug ID: 326899 Summary: Kontact crashed right after start with heavy IO load Classification: Unclassified Product: kontact Version: 4.11.2 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: devuran...@gmx.net Application: kontact (4.11.2) KDE Platform Version: 4.11.2 Qt Version: 4.8.5 Operating System: Linux 3.11.6-gentoo x86_64 Distribution: Gentoo Base System release 2.2 -- Information about the crash: - What I was doing when the application crashed: Kontact crashed right after the start. The window was grey for a long time (probably due to the IO load making something unresponsive), and when it briefly showed some content, Kontact immediately crashed. - Unusual behavior I noticed: The system was heavily loaded with IO tasks right after startup. (My HDDs are slow, so Nepomuk and Akonadi startup creates very heavy load for a very long time.) -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library /lib64/libthread_db.so.1. [Current thread is 1 (Thread 0x7f6f22713780 (LWP 3209))] Thread 4 (Thread 0x7f6f1d2df700 (LWP 3210)): #0 0x003a0480b8b4 in pthread_cond_wait () from /lib64/libpthread.so.0 #1 0x003d91d39b42 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x003d91d39b79 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x003a04807dff in start_thread () from /lib64/libpthread.so.0 #4 0x003a040e701d in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f6f1c9de700 (LWP 3211)): #0 0x003f7a087adc in ?? () from /usr/lib64/libglib-2.0.so.0 #1 0x003f7a087e09 in g_mutex_unlock () from /usr/lib64/libglib-2.0.so.0 #2 0x003f7a0488d6 in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x003f7a048ad4 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x0033a65aa2ce in QEventDispatcherGlib::processEvents (this=0x7f6f180008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #5 0x0033a657badf in QEventLoop::processEvents (this=this@entry=0x7f6f1c9dde60, flags=...) at kernel/qeventloop.cpp:149 #6 0x0033a657bdcd in QEventLoop::exec (this=this@entry=0x7f6f1c9dde60, flags=...) at kernel/qeventloop.cpp:204 #7 0x0033a6479860 in QThread::exec (this=optimized out) at thread/qthread.cpp:536 #8 0x0033a647c0ff in QThreadPrivate::start (arg=0x1e56ea0) at thread/qthread_unix.cpp:338 #9 0x003a04807dff in start_thread () from /lib64/libpthread.so.0 #10 0x003a040e701d in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f6ecea34700 (LWP 3250)): [KCrash Handler] #6 tcpses_is_read_ready (ses=0x7f6ec001c1a0, to=to@entry=0x7f6ec000bae0) at Dksestcp.c:1024 #7 0x7f6ecf9ca2f5 in service_read (ses=ses@entry=0x7f6ec000ba40, buffer=0x7f6ec000c170 \340\263, req_bytes=req_bytes@entry=32768, need_all=need_all@entry=0) at Dkses2.c:372 #8 0x7f6ecf9ca53a in session_buffered_read (ses=0x7f6ec000ba40, buffer=buffer@entry=0x7f6ecea3355f , req_bytes=req_bytes@entry=1) at Dkses2.c:515 #9 0x7f6ecf9ca5ab in session_buffered_read_char (ses=ses@entry=0x7f6ec000ba40) at Dkses2.c:582 #10 0x7f6ecf9c84cb in scan_session_boxing (session=session@entry=0x7f6ec000ba40) at Dkmarshal.c:769 #11 0x7f6ecf9c86e9 in read_object (session=session@entry=0x7f6ec000ba40) at Dkmarshal.c:296 #12 0x7f6ecf9d2f55 in read_service_request_1t (ses=0x7f6ec000ba40) at Dkernel.c:2277 #13 0x7f6ecf9d3b80 in PrpcFutureNextResult1T (future=0x7f6ec000ac00) at Dkernel.c:4252 #14 PrpcFutureNextResult (future=0x7f6ec000ac00) at Dkernel.c:4084 #15 0x7f6ecf99f711 in stmt_process_result (stmt=stmt@entry=0x7f6ec000acb0, needs_evl=needs_evl@entry=1) at ../../libsrc/Wi/CLIuti.c:719 #16 0x7f6ecf9a36ed in virtodbc__SQLExecDirect (hstmt=0x7f6ec000acb0, szSqlStr=optimized out, cbSqlStr=optimized out) at ../../libsrc/Wi/CLIsql1.c:1530 #17 0x003a02c17002 in ?? () from /usr/lib64/libiodbc.so.2 #18 0x003a02c172be in SQLExecDirect () from /usr/lib64/libiodbc.so.2 #19 0x7f6ed051053a in Soprano::ODBC::Connection::execute (this=this@entry=0x7f6ec000b690, request=..., params=...) at /var/tmp/portage/dev-libs/soprano-2.9.4/work/soprano-2.9.4/backends/virtuoso/odbcconnection.cpp:158 #20 0x7f6ed057 in Soprano::ODBC::Connection::executeQuery (this=this@entry=0x7f6ec000b690, request=...) at /var/tmp/portage/dev-libs/soprano-2.9.4/work/soprano-2.9.4/backends/virtuoso/odbcconnection.cpp:89 #21 0x7f6ed050016c in Soprano::VirtuosoModelPrivate::sqlQuery (this=this@entry=0x235f970, query=...) at /var/tmp/portage/dev-libs/soprano-2.9.4/work/soprano-2.9.4/backends/virtuoso/virtuosomodel.cpp:128 #22 0x7f6ed05002cf in Soprano::VirtuosoModelPrivate::sparqlQuery (this=0x235f970, query=...) at
[kmail2] [Bug 323882] Menu entry is renamed after a few seconds in german translation
https://bugs.kde.org/show_bug.cgi?id=323882 --- Comment #4 from Burkhard Lueck lu...@hube-lueck.de --- (In reply to comment #3) Burkhard, So can this one be resolved ? No, because even in locale en_US and x-test I see a jumping clash after a few seconds like in locale de. But sadly I have no clue what's the reason. -- 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 300898] Tags doesn't work
https://bugs.kde.org/show_bug.cgi?id=300898 --- Comment #5 from luisfe lftab...@yahoo.es --- Created attachment 83234 -- https://bugs.kde.org/attachment.cgi?id=83234action=edit show custom tag icons in the messagelist With this patch (tested against kde 4.11.2) custom assigned icons appear in the messagelist view. -- 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 300898] Tags doesn't work
https://bugs.kde.org/show_bug.cgi?id=300898 Allen Winter win...@kde.org changed: What|Removed |Added CC||win...@kde.org --- Comment #6 from Allen Winter win...@kde.org --- luisfe, Would you be able to post this patch on reviewboard.kde.org please? looks ok to me but I want to make sure the nepomuk experts see it first. -- 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 325372] kmail goes offline, but fails to go back online
https://bugs.kde.org/show_bug.cgi?id=325372 Benoit Leffray benoit.leffray@gmail.com changed: What|Removed |Added CC||benoit.leffray@gmail.co ||m -- 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
[nepomuk] [Bug 326899] Kontact crashed right after start with heavy IO load
https://bugs.kde.org/show_bug.cgi?id=326899 Jekyll Wu adap...@gmail.com changed: What|Removed |Added CC||nepomuk-b...@kde.org Component|general |general Assignee|kdepim-bugs@kde.org |nepomuk-b...@kde.org Product|kontact |nepomuk -- 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 326924] New: Problems when using Postgresql backend database
https://bugs.kde.org/show_bug.cgi?id=326924 Bug ID: 326924 Summary: Problems when using Postgresql backend database Classification: Unclassified Product: Akonadi Version: 4.11 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: server Assignee: kdepim-bugs@kde.org Reporter: aar...@doofus.org I am seeing the following errors when starting up Akonadi when using Postgresql 9.2: DBUpdater: query error: ERROR: function convert_from(text, unknown) does not exist HINT: No function matches the given name and argument types. You might need to add explicit type casts. (42883) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER remoteId TYPE text USING convert_from(remoteId,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER remoteRevision TYPE text USING convert_from(remoteRevision,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER name TYPE text USING convert_from(name,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER cachePolicyLocalParts TYPE text USING convert_from(cachePolicyLocalParts,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER queryString TYPE text USING convert_from(queryString,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE CollectionTable ALTER queryLanguage TYPE text USING convert_from(queryLanguage,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE FlagTable ALTER name TYPE text USING convert_from(name,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE MimeTypeTable ALTER name TYPE text USING convert_from(name,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE PartTable ALTER name TYPE text USING convert_from(name,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE PimItemTable ALTER remoteId TYPE text USING convert_from(remoteId,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE PimItemTable ALTER remoteRevision TYPE text USING convert_from(remoteRevision,'utf8'); Target version was: 24 Mandatory: false DBUpdater: query error: ERROR: current transaction is aborted, commands ignored until end of transaction block (25P02) QPSQL: Unable to create query Query was: ALTER TABLE ResourceTable ALTER name TYPE text USING convert_from(name,'utf8'); Target version was: 24 Mandatory: false Failed to commit transaction for database update Nepomuk Query Server not available Reproducible: Always Steps to Reproduce: 1. Configure to use system postgresql database server (not internal) 2. Start Akonadi 3. Running OpenSUSE 12.3 with Postgres 9.2.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
[Akonadi] [Bug 320911] Google Contacts resource + Akonadi Nepomuk Feeder = Transaction deadlocked.
https://bugs.kde.org/show_bug.cgi?id=320911
Aaron Williams aar...@doofus.org changed:
What|Removed |Added
CC||aar...@doofus.org
--- Comment #1 from Aaron Williams aar...@doofus.org ---
I can confirm that I am seeing the same thing with nepomukindexer 4.11.2
running on OpenSUSE. This happens with certain pdf files.
Here are some PDF files that generate the error:
www.nxp.com/documents/data_sheet/PCA9541.pdf
www.nxp.com/documents/data_sheet/PCA8574_PCA8574A.pdf
www.onfi.org/~/media/ONFI/specs/ONFI_1_0_Gold.pdf
http://www.ti.com/lit/ds/scds178c/scds178c.pdf
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/82599-10-gbe-controller-datasheet.pdf
http://www.ftdichip.com/Support/Documents/AppNotes/AN_107_AdvancedDriverOptions_AN_73.pdf
http://www.ftdichip.com/Support/Documents/AppNotes/AN_135_MPSSE_Basics.pdf
All of these generate the following error:
nepomukindexer(2949)/nepomuk (strigi service): SQLExecDirect failed on query
'sparql insert { graph nepomuk:/ctx/a729a0da-d766-42ad-8491-12c992d2abdb {
nepomuk:/res/708cd4ad-42f8-4d21-8c47-2134ab28521a nie:plainTextContent Open
NAND Flash Interface Specification\nRevision 1.0\n
28-December-2006\n Hynix Semiconductor\nIntel Corporation\n
Micron Technology, Inc.\nPhison Electronics Corp.\n
Sony Corporation\n STMicroelectronics\nThis 1.0 revision of the Open
NAND Flash Interface specification (\Final Specification\) is\navailable for
download at www.onfi.org.\n
...
http://www.w3.org/2001/XMLSchema#string . } }' (iODBC Error:
[OpenLink][Virtuoso iODBC Driver][Virtuoso Server]SR172: Transaction
deadlocked)
--
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
