[kmail2] [Bug 332167] New: KMail is failing to encrypt PGP/Inline for non-signed key

2014-03-14 Thread kolAflash
https://bugs.kde.org/show_bug.cgi?id=332167

Bug ID: 332167
   Summary: KMail is failing to encrypt PGP/Inline for non-signed
key
Classification: Unclassified
   Product: kmail2
   Version: 4.11.5
  Platform: unspecified
OS: Linux
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: crypto
  Assignee: kdepim-bugs@kde.org
  Reporter: kolafl...@kolahilft.de

I can't send an PGP/Inline email to a receiver with an key I didn't sign
before.

If I sign the receivers key before sending OR use PGP/MIME everything's working
fine.

Reproducible: Always

Steps to Reproduce:
1. Create a new email.
2. Encrypt the email and set the encryption-format to PGP/Inline.
3. Click "Send".
Actual Results:  
KMail tells: It was not possible to create a message composer.

Expected Results:  
E-Mail should be encrypted and send using the PGP/Inline format.

I tried to find the bug searching in
messagecomposer/composer/keyresolver.cpp

https://projects.kde.org/projects/kde/kdepim/repository/revisions/6fce5eb967cc02398bcf9032959e48d0a3c64b78/entry/messagecomposer/composer/keyresolver.cpp


Line 547
ValidTrustedOpenPGPEncryptionKey ) != item.keys.end() ) {  // -= trusted?
looks suspicious. I tried replacing it with:
ValidOpenPGPEncryptionKey ) != item.keys.end() ) {

Same for line 1575
NotValidTrustedOpenPGPEncryptionKey ); // -= trusted (see above, too)?
I replaced with
NotValidOpenPGPEncryptionKey );

But both didn't helped. I just got another error telling me, that the key is
corrupt (it definitely isn't - I can use it for PGP/MIME and in Thunderbird it
also works for PGP/Inline).

-- 
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 312608] kmail thread sorting , aggregation - thread leader - most recent message , is not working right

2014-03-14 Thread Arthur Țițeică
https://bugs.kde.org/show_bug.cgi?id=312608

Arthur Țițeică  changed:

   What|Removed |Added

 CC||arthur.tite...@gmail.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


[Akonadi] [Bug 331867] mysql: column 'name' can not be null when migrating PartTable

2014-03-14 Thread tbohaning
https://bugs.kde.org/show_bug.cgi?id=331867

--- Comment #10 from tbohan...@gmail.com ---
That took care of the akonadi issue. Thanks Daniel !!

-- 
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 312608] kmail thread sorting , aggregation - thread leader - most recent message , is not working right

2014-03-14 Thread Andreas Petzold
https://bugs.kde.org/show_bug.cgi?id=312608

Andreas Petzold  changed:

   What|Removed |Added

 CC||andreas.petzold+kdebugs@gma
   ||il.com

--- Comment #1 from Andreas Petzold  ---
This is still broken in kmail 4.12.3. This is really a show stopper for me, as
new replies to older threads are escaping my attention, because they don't show
up on the top of the message list.

-- 
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 331867] mysql: column 'name' can not be null when migrating PartTable

2014-03-14 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=331867

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |CONFIRMED
 Ever confirmed|0   |1

--- Comment #9 from Daniel Vrátil  ---
Ha! We found the culprit. GID is not supposed to be there, it's not a part. It
looks like after an update you started KMail, but did not restart Akonadi, so
KMail was sending the "GID" data, but Akonadi did not know it so it though it's
a part type.

You can run following query in DB Console to get rid of it:

DELETE FROM PartTable WHERE name = 'GID';

This will fix the migration to 1.12 for you. I'll add a check to Akonadi to
prevent this from happening to others.

-- 
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 299224] kontact crash on quit

2014-03-14 Thread auxsvr
https://bugs.kde.org/show_bug.cgi?id=299224

--- Comment #8 from aux...@gmail.com ---
Created attachment 85576
  --> https://bugs.kde.org/attachment.cgi?id=85576&action=edit
New crash information added by DrKonqi

kontact (4.12.3) on KDE Platform 4.12.3 using Qt 4.8.5

- What I was doing when the application crashed:

Kontact was closing when I closed akonadiserver. Then it crashed.

-- Backtrace (Reduced):
#7  data (this=0x5) at ../../src/corelib/tools/qscopedpointer.h:135
[...]
#10 QItemSelectionModel::selectedIndexes (this=0x1) at
itemviews/qitemselectionmodel.cpp:1432
#11 0xac840638 in MailCommon::FolderTreeWidget::selectedCollections
(this=0x8f6e7c8) at
/usr/src/debug/kdepim-4.12.3/mailcommon/folder/foldertreewidget.cpp:244
#12 0xaca11b88 in KMMainWidget::updateFolderMenu (this=this@entry=0x8f70eb8) at
/usr/src/debug/kdepim-4.12.3/kmail/kmmainwidget.cpp:4133
#13 0xaca126b8 in KMMainWidget::slotUpdateActionsAfterMailChecking
(this=this@entry=0x8f70eb8) at
/usr/src/debug/kdepim-4.12.3/kmail/kmmainwidget.cpp:431

-- 
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 331867] mysql: column 'name' can not be null when migrating PartTable

2014-03-14 Thread tbohaning
https://bugs.kde.org/show_bug.cgi?id=331867

--- Comment #8 from tbohan...@gmail.com ---
Daniel - As you requested

ATR:AddressAttribute
ATR:DispatchModeAttribute
ATR:MDNStateAttribute
ATR:ScamAttribute
ATR:SentActionAttribute
ATR:SentBehaviourAttribute
ATR:TransportAttribute
ATR:contactmetadata
ATR:pop3resourceattribute
GID
PLD:ENVELOPE
PLD:HEAD
PLD:RFC822

-- 
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 258157] akonadi self-test doesn't find nepomuk dbus search service at startup

2014-03-14 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=258157

Daniel Vrátil  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||dvra...@redhat.com
  Component|server  |libakonadi
   Version Fixed In||4.13
 Resolution|--- |FIXED
  Latest Commit||http://commits.kde.org/kdep
   ||imlibs/4b3e3fa8692f2701e146
   ||db2ea8c364ae8d7372a9

--- Comment #6 from Daniel Vrátil  ---
We don't check for Nepomuk anymore in KDE 4.13.

-- 
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 331867] mysql: column 'name' can not be null when migrating PartTable

2014-03-14 Thread Daniel Vrátil
https://bugs.kde.org/show_bug.cgi?id=331867

--- Comment #7 from Daniel Vrátil  ---
If you still run the stable database (from Akonadi 1.11) that you tried to
update to 1.12, could any of you please open Akonadi Console, go to DB Console
tab and run following query:

SELECT DISTINCT(name) FROM PartTable;


and post it's output here? The problem you ran into can only happen when some
of they part names don't have NAMESPACE:NAME format, which should not happen,
but it's possible that there are some legacy names I missed.

-- 
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 306807] akonadi 4.8.5 states that Nepomuk query server is not available, but there is no further information

2014-03-14 Thread Jon Randoem
https://bugs.kde.org/show_bug.cgi?id=306807

Jon Randoem  changed:

   What|Removed |Added

 CC||cont...@jonrandoem.com

--- Comment #10 from Jon Randoem  ---
On Fedora 19, I managed to get rid of that bug with the following:

- install of the package mysql-connector-odbc
- restart akonadi

Note that I obviously use MySQL (actually MariaDB) as backend for Akonadi.
KDE 4.11.5
Virtuoso 6.1.6

Hope this will be useful.

-- 
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 332129] New: Open-ended to-dos not shown in Summary

2014-03-14 Thread Adriano Fantini
https://bugs.kde.org/show_bug.cgi?id=332129

Bug ID: 332129
   Summary: Open-ended to-dos not shown in Summary
Classification: Unclassified
   Product: kontact
   Version: 4.12.3
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: summary
  Assignee: kdepim-bugs@kde.org
  Reporter: adr.fant...@gmail.com

Open-ended to-dos are not shown in Summary even though they are not hidden in
the Pending To-dos Summary Setup

Reproducible: Always

Steps to Reproduce:
1. Create new to-do with no start and no due date
2. To-do is not shown in Summary
3.
Actual Results:  
Open-ended to-dos are not shown in Summary

Expected Results:  
Open-ended to-dos should always be shown in Summary except when the start date
is far in the future (further than the Show To-dos Due limit)

-- 
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