Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at

Bug 1199754

Summary: Please apply the upstream patch (Polish translation, time format)
Product: [Fedora] Fedora Reporter: Rafal Luzynski <digitalfreak>
Component: mate-screensaverAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, digitalfreak, fedora, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: mate-screensaver-1.8.1-3.el7 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-18 10:27:16 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:
Bug Depends On:    
Bug Blocks: 484497    

Description Rafal Luzynski 2015-03-07 23:26:20 UTC
Description of problem:

Bad time format in Polish translation in the unlock dialog box of the screensaver.

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


How reproducible:


Steps to Reproduce:
1. Select Polish language and MATE desktop environment.
2. Lock the screen or wait until the screensaver locks it.
3. Try to unlock, watch the unlock dialog.

Actual results:

The dialog shows the current date, time, etc. The time is always displayed like "11:M" because of the missing '%' sign in the time format ("%k:M", should be "%k:%M").

Expected results:

The correct time should be displayed, e.g., "11:23".

Additional info:

This bug affects only Polish speaking MATE users but the bad time format looks ugly. This bug has already been fixed upstream but is still present as long as you deliver MATE screensaver 1.8 for Fedora 20 and 21. Please apply this one-line fix unless you are going to provide 1.9 for Fedora 20/21.

Upstream bug report (closed):

Diff of the affected file:

Pull request:

Comment 1 Wolfgang Ulbrich 2015-03-08 02:58:37 UTC
Please test

Comment 2 Rafal Luzynski 2015-03-09 22:42:22 UTC
(In reply to Wolfgang Ulbrich from comment #1)
> Please test

Works correctly, hour:minute is displayed correctly and even updated as the time passes. Thank you for your quick update!

To be honest and precise, I have tested x86_64 version but I believe it works the same on all architectures.

Comment 3 Fedora Update System 2015-03-10 00:10:43 UTC
mate-screensaver-1.8.1-3.el7 has been submitted as an update for Fedora EPEL 7.

Comment 4 Fedora Update System 2015-03-10 00:11:53 UTC
mate-screensaver-1.8.1-3.fc21 has been submitted as an update for Fedora 21.

Comment 5 Fedora Update System 2015-03-10 00:11:57 UTC
mate-screensaver-1.8.1-3.fc20 has been submitted as an update for Fedora 20.

Comment 6 Fedora Update System 2015-03-10 16:04:04 UTC
Package mate-screensaver-1.8.1-3.el7:
* should fix your issue,
* was pushed to the Fedora EPEL 7 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing mate-screensaver-1.8.1-3.el7'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2015-03-18 10:27:16 UTC
mate-screensaver-1.8.1-3.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Fedora Update System 2015-03-21 04:59:12 UTC
mate-screensaver-1.8.1-3.fc20 has been pushed to the Fedora 20 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-03-25 19:56:22 UTC
mate-screensaver-1.8.1-3.el7 has been pushed to the Fedora EPEL 7 stable repository.  If problems still persist, please make note of it in this bug report.