Bug 1408717 - labels on calendar are overlaps each other
Summary: labels on calendar are overlaps each other
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: gnome-shell
Version: 7.3
Hardware: All
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Florian Müllner
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: gnome-shell-rebase
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-26 16:01 UTC by ilya
Modified: 2017-08-01 22:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-08-01 22:44:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
liik at top calendar (99.19 KB, image/png)
2016-12-26 16:01 UTC, ilya 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2098 0 normal SHIPPED_LIVE gnome-shell-extensions, gnome-shell, mutter bug fix and enhancement update 2017-08-01 19:36:42 UTC

Description ilya 2016-12-26 16:01:42 UTC 
Created attachment 1235410 [details]
liik at top calendar

Description of problem:
labels on calendar are overlaps each other

Version-Release number of selected component (if applicable):
rhel 7.3,gnome-calendar

How reproducible:


Steps to Reproduce:
1.click to watch in top bar
2.
3.

Actual results:
labels in right panel are overlapping each other

Expected results:
labels are looking good

Additional info:
maybe reoroducible only in russian translattion
Comment 2 Florian Müllner 2017-01-19 17:50:04 UTC 
Since version 3.16, calendar events use separate lines for the time and description labels, so the desktop rebase in RHEL 7.4 will fix this issue.
Comment 4 errata-xmlrpc 2017-08-01 22:44:12 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:2098
Note You need to log in before you can comment on or make changes to this bug.