Bug 199316 - Logout dialog align in wrong direction in RTL mode
Summary: Logout dialog align in wrong direction in RTL mode
Status: RESOLVED FIXED
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: ui (show other bugs)
Version: 4.9.1
Platform: Compiled Sources Unspecified
: NOR normal
Target Milestone: ---
Assignee: Lubos Lunak
URL:
Keywords: rtl
Depends on:
Blocks:
 
Reported: 2009-07-07 18:31 UTC by Zayed Al-Saidi
Modified: 2018-11-10 18:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
the screenshot of logout dialog in RTL mode (9.53 KB, image/jpeg)
2009-07-07 18:32 UTC, Zayed Al-Saidi 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Zayed Al-Saidi 2009-07-07 18:31:29 UTC 
Version:            (using KDE 4.2.90)
Installed from:    Compiled From Sources

Please see the attached screen shot. Notice that the text is align to right instead to the left. Therefore there is overlap. In RTL mode the text of the logout button and Cancel button should align to the left.
Comment 1 Zayed Al-Saidi 2009-07-07 18:32:43 UTC 
Created attachment 35129 [details]
the screenshot of logout dialog in RTL mode
Comment 2 Zayed Al-Saidi 2010-05-22 19:02:43 UTC 
The overlap between the label and the icon is still there.
Comment 3 Myriam Schweingruber 2012-09-08 12:35:06 UTC 
I assume this is still valid for KDE 4.9.x? Please set the version field.
Comment 4 Jekyll Wu 2012-09-08 18:55:36 UTC 
updating status
Comment 5 Andrew Crouthamel 2018-11-09 01:09:36 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Zayed Al-Saidi 2018-11-10 18:22:34 UTC 
This UI for logout doesn't exist since version 5. Therefore, we can close this bug.