Bug 892155

Summary: when unbound is not started, KDE system tray shows two icons & claims success
Product: [Fedora] Fedora Reporter: Alan Jenkins <alan.christopher.jenkins>
Component: dnssec-system-trayAssignee: Wes Hardaker <wjhns174>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: wjhns174
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-01-05 14:41:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot: KDE system tray shows two anchor icons none

Description Alan Jenkins 2013-01-05 14:29:17 UTC
Created attachment 672854 [details]
Screenshot: KDE system tray shows two anchor icons

Description of problem:

When unbound is not started, the KDE system tray shows two identical anchor icons (instead of the usual one icon).  There are no error messages in the probe results dialogue.

Version-Release number of selected component (if applicable):

Name        : dnssec-system-tray
Arch        : x86_64
Version     : 1.12
Release     : 1.fc17

How reproducible: Always

Steps to Reproduce:
1. Add 'interface: 1.1.1.1' to /etc/unbound.conf, so that unbound will fail to start (because the system does not have the IP address 1.1.1.1).
2. Reboot & log in to KDE

Actual results:

Two anchor icons appear in the system tray.  Right clicking on either of them shows a context menu.  I tried clicking the "probe results" menu item... I've had the results come up for both icons (as two separate windows).  There are no error messages in the probe results.

Expected results:

There should only be one anchor icon in the system tray.

Ideally, the probe report would not end in "DNSSEC results fetched from (DHCP) cache(s)".  It sounds a bit too satisfied, for something that doesn't know whether unbound is running or not :).  To put it another way - it sounds more like a report from a component in the DNS resolution path, i.e. unbound.

Maybe a message in future tense message would be less likely to confuse.  I.e. "DNSSEC results _will be_ fetched ...".

Comment 1 Alan Jenkins 2013-01-05 14:41:14 UTC
Argh, now I can't reproduce it as described.

I've had it happen a couple of times now.  It might be associated with me manually restarting dnssec-triggerd (which was probably a bit of a pointless thing to do).  I also wonder whether there's some interaction with the KDE session manager.  (By default, this restores the previous session's applications).