http://bugzilla.suse.com/show_bug.cgi?id=910920 Ancor Gonzalez Sosa <ancor@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|YaST2 |KDE4 Workspace Assignee|ancor@suse.com |kde-maintainers@suse.de QA Contact|jsrain@suse.com |qa-bugs@suse.de Flags|needinfo?(epistemepromeneur | |@free.fr) | --- Comment #4 from Ancor Gonzalez Sosa <ancor@suse.com> --- I've looked through the YaST logs. I can see how YaST adds the key to the zypp Keyring and imports it every few days. 2014-12-20: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-16: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-17: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-18: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-19: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-13: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-13: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-12: User wants to trust key 8E5578B7233AB63D Emulators OBS Project 2014-12-11: User wants to trust key 8E5578B7233AB63D Emulators OBS Project But I see nothing removing or disabling it. I can be wrong, but my theory is that another software (and not YaST) is actually removing the key in the meantime. Since the main suspect would be the KDE systray application, I'm reassigning the bug to KDE workspace. -- You are receiving this mail because: You are on the CC list for the bug.