Bug 277697 - Impossible to set "owner trust"
Summary: Impossible to set "owner trust"
Status: RESOLVED FIXED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: 2.0.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-13 14:35 UTC by S. Burmeister
Modified: 2012-05-09 04:58 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.8.4

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description S. Burmeister 2011-07-13 14:35:10 UTC 
Version:           2.0.0 (using Devel) 
OS:                Linux

I got a certificate from a person. I want to attach it to his kaddressbook entry which does not work - I guess because I did not trust it.

So I open kleopatra > other certificates and right click the certificate in question > change owner trust. A new window opens with some radio buttons yet whatever I pick the "ok" stays inactive, i.e. I cannot change the owner trust.

Reproducible: Always

Steps to Reproduce:
Import a certificate and try to change the owner trust

Actual Results:  
not possible

Expected Results:  
possibel
Comment 1 kuhlmann-michael 2011-08-02 07:38:01 UTC 
same here on kubuntu using kde 4.7

When I open kleopatra from the konsole i get this error mesage:

Object::connect: No such slot QWidget::slotTrustLevelChanged()
Object::connect:  (sender name:   'unknownRB')
Object::connect:  (receiver name: 'OwnerTrustDialog')
Object::connect: No such slot QWidget::slotTrustLevelChanged()
Object::connect:  (sender name:   'neverRB')
Object::connect:  (receiver name: 'OwnerTrustDialog')
Object::connect: No such slot QWidget::slotTrustLevelChanged()
Object::connect:  (sender name:   'marginalRB')
Object::connect:  (receiver name: 'OwnerTrustDialog')
Object::connect: No such slot QWidget::slotTrustLevelChanged()
Object::connect:  (sender name:   'fullRB')
Object::connect:  (receiver name: 'OwnerTrustDialog')
Object::connect: No such slot QWidget::slotTrustLevelChanged()
Object::connect:  (sender name:   'ultimateRB')
Object::connect:  (receiver name: 'OwnerTrustDialog')
Comment 2 Martin Samek 2011-08-15 20:16:58 UTC 
I can confirm this. Running version 2.1.1 of Kleopatra. OK button is still disabled.
Comment 3 Robby Engelmann 2011-12-05 22:52:16 UTC 
I can confirm that using:
Kleopatra
Version 2.1.1
Using KDE Development Platform 4.7.3 (4.7.3)
Comment 4 Alexander Görtz 2012-01-10 10:11:55 UTC 
I have the same Problem here. KMail shows me "The signature is valid, but the key's validity is unknown." for my own key!

So I opened up Kleopatra and tryed to change the trust of my own key and the OK button just keeps beeing gray. Hope there will be a fix soon.
Comment 5 Blackpaw 2012-05-05 07:49:24 UTC 
(In reply to comment #1)
> same here on kubuntu using kde 4.7
> 
> When I open kleopatra from the konsole i get this error mesage:
> 
> Object::connect: No such slot QWidget::slotTrustLevelChanged()
> Object::connect:  (sender name:   'unknownRB')
> Object::connect:  (receiver name: 'OwnerTrustDialog')
> Object::connect: No such slot QWidget::slotTrustLevelChanged()
> Object::connect:  (sender name:   'neverRB')
> Object::connect:  (receiver name: 'OwnerTrustDialog')
> Object::connect: No such slot QWidget::slotTrustLevelChanged()
> Object::connect:  (sender name:   'marginalRB')
> Object::connect:  (receiver name: 'OwnerTrustDialog')
> Object::connect: No such slot QWidget::slotTrustLevelChanged()
> Object::connect:  (sender name:   'fullRB')
> Object::connect:  (receiver name: 'OwnerTrustDialog')
> Object::connect: No such slot QWidget::slotTrustLevelChanged()
> Object::connect:  (sender name:   'ultimateRB')
> Object::connect:  (receiver name: 'OwnerTrustDialog')



Same problem here. KDE 4.8.2
Comment 6 Allen Winter 2012-05-09 00:04:40 UTC 
I just committed a fix for this one.

Will be in KDE SC Release 4.8.4 and above
Comment 7 S. Burmeister 2012-05-09 04:10:36 UTC 
Thanks!
Comment 8 Blackpaw 2012-05-09 04:58:11 UTC 
Replicated then tested with new fixes. Definitely fixed.

Thanks!