Bug 892155 - when unbound is not started, KDE system tray shows two icons & claims success
Summary: when unbound is not started, KDE system tray shows two icons & claims success
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: dnssec-system-tray
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Wes Hardaker
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-05 14:29 UTC by Alan Jenkins
Modified: 2013-01-05 14:41 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-05 14:41:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Screenshot: KDE system tray shows two anchor icons (6.42 KB, image/png)
2013-01-05 14:29 UTC, Alan Jenkins
no flags Details

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


Note You need to log in before you can comment on or make changes to this bug.