[kontact] [Bug 342139] KDE 4.14.3 - Kontact when opening the first time shows only half the side bar in summary.
https://bugs.kde.org/show_bug.cgi?id=342139 Tim Ruffing changed: What|Removed |Added CC||k...@davidedmudnson.co.uk, ||pub...@timruffing.de --- Comment #2 from Tim Ruffing --- The same happens if the scaling factor of the new high DPI settings is set to 1.5. (see http://blog.davidedmundson.co.uk/blog/high_dpi_again) I guess the reason is that this scaling factor just changes the font DPI? The sidebar works fine with an integer scaling factor; I tried 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
[Akonadi] [Bug 338570] Akonadi Dav Resource: Missing Conflict Resolution
https://bugs.kde.org/show_bug.cgi?id=338570 Tim Ruffing changed: What|Removed |Added CC||pub...@timruffing.de --- Comment #3 from Tim Ruffing --- I think bug #343152 is a duplicate of this one. -- 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 343152] CardDav not syncing client changes with server
https://bugs.kde.org/show_bug.cgi?id=343152 --- Comment #2 from Tim Ruffing --- I think this is a duplicate of bug #338570. -- 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 343152] CardDav not syncing client changes with server
https://bugs.kde.org/show_bug.cgi?id=343152 Tim Ruffing changed: What|Removed |Added CC||pub...@timruffing.de -- 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 343133] New: printing should fail if decryption fails
https://bugs.kde.org/show_bug.cgi?id=343133 Bug ID: 343133 Summary: printing should fail if decryption fails Product: kmail2 Version: 4.14.3 Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: crypto Assignee: kdepim-bugs@kde.org Reporter: pub...@timruffing.de 1. Open an encrypted email but do not decrypt it 2. Try to print it (or print preview) 3. If decryption fails (e.g., due to clicking "Cancel"), the print dialog is shown unexpectedly 4. Continuing will print an error message "Could not decrypt the data." -- 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 339384] New akonadi_kolab_resource crashing (Signal: Aborted) on start up
https://bugs.kde.org/show_bug.cgi?id=339384
--- Comment #3 from Tim Ruffing ---
qDebug was not enabled for akonadi_kolab_resource. If I enable it, I get one
more line (marked with >>>)
akonadi_kolab_resource_1(10790)/kdepimlibs (kimap)
KIMAP::LoginJob::handleResponse: "Login" "A02"
akonadi_kolab_resource_1(10790)/kdepimlibs (kimap) KIMAP::LoginJob::~LoginJob:
KIMAP::LoginJob(0x11df050)
akonadi_kolab_resource_1(10790) ImapResourceBase::doSetOnline: online= true
akonadi_kolab_resource_1(10790)/libakonadi Akonadi::EntityListCache::processResult: "Item query returned empty result set"
>>> akonadi_kolab_resource_1(10790) KolabHelpers::translateToImap: converted
>>> event
Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
---
This happens in line 219 in kolabhelpers.cpp (v4.14.3). In a debug build, the
"Q_ASSERT(item.hasPayload());" (line 218) fires. So
the expection is thrown while trying to access the payload afterwards.
The reason is that a non-existing item is processed here.
Query Debugger says:
21587: SELECT PimItemTable.id, PimItemTable.remoteId, MimeTypeTable.name,
PimItemTable.rev, PimItemTable.remoteRevision, PimItemTable.size,
PimItemTable.collectionId FROM PimItemTable INNER JOIN MimeTypeTable ON (
PimItemTable.mimeTypeId = MimeTypeTable.id ) WHERE ( ( PimItemTable.id = 86977
) ) ORDER BY PimItemTable.id DESC
Success: Query took 1 msecs
Fetched 0 results
Using debug output, I have confirmed that 86977 is the id of the item that
fails in the assert.
I just don't know where this id comes from, i.e., why this id should be
accessed at all. It is possible that I created an item with this id (it's a
"recent" id) locally, and deleted it afterwards, while I was offline. I could
imagine that now it's still in some jon cache or similar for whatever reason,
and the resource tries to send it to the kolab server. But I could not find the
id anywhere in a table. (I don't know about caches.)
As a workaround, I replaced the assert by
if (!item.hasPayload()) {
ok = false;
return Akonadi::Item();
}
Using this modification, I could avoid the crash. Then akonadi_kolab_resource
could start and sort things out. Afterwards, I reverted to the original version
of akonadi_kolab_resource (that crashed beforehand). Now the problems seems to
be solved for me.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 341513] New: wrong contact photo shown
https://bugs.kde.org/show_bug.cgi?id=341513 Bug ID: 341513 Summary: wrong contact photo shown Product: kontact Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: mail Assignee: kdepim-bugs@kde.org Reporter: pub...@timruffing.de I regularly get emails from "post+exam...@example.de", where I substituted "EXAMPLE" for privacy reasons. I don't have this email address in my address book. Still, a contact photo is displayed when I read mails from this address. The photo belongs to an unrelated contact with "p...@anotherexample.de". If I remove the email address from the contact, kontact displays the photo of yet another contact with "p...@yetanotherexample.de". I guess the plus sign in the email address is the problem. 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 339384] New akonadi_kolab_resource crashing (Signal: Aborted) on start up
https://bugs.kde.org/show_bug.cgi?id=339384 --- Comment #2 from Tim Ruffing --- forgot to add: This is KDE 4.14.3 on Arch Linux (x86_64). -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[Akonadi] [Bug 339384] New akonadi_kolab_resource crashing (Signal: Aborted) on start up
https://bugs.kde.org/show_bug.cgi?id=339384 Tim Ruffing changed: What|Removed |Added CC||pub...@timruffing.de --- Comment #1 from Tim Ruffing --- For me the problem did not show up immediately after switching to the new Kolab ressource. The new ressource worked for some weeks... Now it crashes reliably. the output is: [...] akonadi_kolab_resource_1(8051)/kdepimlibs (kimap) KIMAP::LoginJob::handleResponse: "Login" "A02" akonadi_kolab_resource_1(8051)/kdepimlibs (kimap) KIMAP::LoginJob::~LoginJob: KIMAP::LoginJob(0x1121f80) akonadi_kolab_resource_1(8051)/libakonadi Akonadi::EntityListCache::processResult: "Item query returned empty result set" Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'Akonadi::PayloadException' what(): Akonadi::PayloadException: No payload set KCrash: Application 'akonadi_kolab_resource' crashing... KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit KCrash: Connect sock_file=/home/tim/.kde4/socket-calzone/kdeinit4__0 Unregistering search instance "akonadi_kolab_resource_1" Lost connection to resource "org.freedesktop.Akonadi.Resource.akonadi_kolab_resource_1" , discarding cached interface void Akonadi::Server::NotificationSource::serviceUnregistered(const QString&) Notification --- Application: [...] of type Kolab Groupware Server (akonadi_kolab_resource), signal: Aborted Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0b7aa587c0 (LWP 8051))] Thread 2 (Thread 0x7f0b63539700 (LWP 8053)): #0 0x7f0b758747bd in poll () from /usr/lib/libc.so.6 #1 0x7f0b747f7c94 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x7f0b747f7dac in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x7f0b7a094397 in QEventDispatcherGlib::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #4 0x7f0b7a063de1 in QEventLoop::processEvents(QFlags) () from /usr/lib/libQtCore.so.4 #5 0x7f0b7a064145 in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #6 0x7f0b79f587f9 in QThread::exec() () from /usr/lib/libQtCore.so.4 #7 0x7f0b79f5b05f in ?? () from /usr/lib/libQtCore.so.4 #8 0x7f0b74edd314 in start_thread () from /usr/lib/libpthread.so.0 #9 0x7f0b7587d5bd in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f0b7aa587c0 (LWP 8051)): [KCrash Handler] #5 0x7f0b757c8a97 in raise () from /usr/lib/libc.so.6 #6 0x7f0b757c9e6a in abort () from /usr/lib/libc.so.6 #7 0x7f0b75daefcd in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/libstdc++.so.6 #8 0x7f0b75dace56 in __cxxabiv1::__terminate(void (*)()) () from /usr/lib/libstdc++.so.6 #9 0x7f0b75dacea1 in std::terminate() () from /usr/lib/libstdc++.so.6 #10 0x7f0b75dad106 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #11 0x7f0b7a06434b in QEventLoop::exec(QFlags) () from /usr/lib/libQtCore.so.4 #12 0x7f0b7a0696e9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #13 0x7f0b7a56006c in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4 #14 0x004314fe in _start () -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs
[kontact] [Bug 309981] Kontact crashed after returning from sleep
https://bugs.kde.org/show_bug.cgi?id=309981 Tim Ruffing changed: What|Removed |Added CC||pub...@timruffing.de -- 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
[kleopatra] [Bug 341293] Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1
https://bugs.kde.org/show_bug.cgi?id=341293 --- Comment #1 from Tim Ruffing --- This is one concrete instance of bug 340677. Bug 340676 is a similar issue in KGPG. -- 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
[kleopatra] [Bug 341293] New: Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1
https://bugs.kde.org/show_bug.cgi?id=341293 Bug ID: 341293 Summary: Kleopatra self-test should not expect gpg-agent to be running for GnuPG >= 2.1 Product: kleopatra Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: general Assignee: kdepim-bugs@kde.org Reporter: pub...@timruffing.de CC: m...@kde.org GnuPG 2.1 autostarts the gpg-agent on demand. Thus the self-test in kleopatra should not fail if it cannot connect to gpg-agent. Additionally, the text that explains the failure is wrong, because it refers to GPG_AGENT_INFO, which is not used anymore. Reproducible: Always Steps to Reproduce: 1. Make sure gpg-agent is not running 2. Run kleopatra self-test Actual Results: The test "Gpg-Agent Connectivity" fails. Expected Results: The test should succeed. There is no problem, because gpg-agent will be started on demand. -- 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
