Bug 805220 - Misleading string in calendar/tasks alarm settings
Summary: Misleading string in calendar/tasks alarm settings
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution
Version: 6.3
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: beta
: 6.4
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-20 16:54 UTC by David Jaša
Modified: 2012-03-21 10:23 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 10:23:07 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 672486 0 None None None Never

Description David Jaša 2012-03-20 16:54:07 UTC
Description of problem:
In the alarm settings, there is the checkbox that states "Display alarms in
notification area *only*" (emphasis mine). However, in my experience, when
unchecked, *no* notifications are shown.

Please correct the string to show the real underlying functionality.

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

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Milan Crha 2012-03-21 10:05:35 UTC
It is supposed to open a window with list of alarm notification directly, like when you click the icon in the notification area, with the check turned off. It will be better to track down why you do not see the notification, rather than "fixing" the string, because the string is correct.

Does it work with local reminders? If it does, then it's just yours bug #805239 and bug #805228 can be closed.

Comment 2 David Jaša 2012-03-21 10:22:20 UTC
It does work with local reminders, so I'm closing this one and bug #805228

Comment 3 David Jaša 2012-03-21 10:23:07 UTC
(In reply to comment #2)
> It does work with local reminders, so I'm closing this one and bug #805228


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