Bug 6507

Summary: rpmdrake and MageiaUpdate do not honor KDE color scheme for several elements
Product: Mageia Reporter: R B <ralf09.05>
Component: RPM PackagesAssignee: Thierry Vignaud <thierry.vignaud>
Status: RESOLVED OLD QA Contact:
Severity: minor    
Priority: Low CC: stormi-mageia
Version: 2Keywords: Triaged
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: rpmdrake CVE:
Status comment:

Description R B 2012-06-19 04:06:18 CEST
Description of problem:

When a non-default color theme is chosen in System Settings, rpmdrake only partially uses the selected colors.  It always forces light/white backgrounds for the two drop-down menus to select type of package and installed/not-installed filter, the software-type tree on the left, and the package list pane at top right.  Using a theme with light text on a dark background makes these four elements difficult or impossible to read.

Other elements, such as the package-detail pane at lower right, Select-All/Apply/Quit buttons and search field all properly use the active theme's colors.


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

How reproducible:

Steps to Reproduce:
1.  Open System Settings, go to Application Appearance | Colors, and select a dark theme such as Obsidian Coast, Wonton Soup, or Zion(Reversed).
2. Apply the theme
3. Run rpmdrake
R B 2012-06-19 04:07:21 CEST

Priority: Normal => Low
Hardware: i586 => x86_64

Comment 1 R B 2012-06-24 19:37:42 CEST
MageiaUpdate has the same problem of white/light-gray background in the package list pane.  Presumably the problem is in the Perl GTK2 bindings, so I changed the RPM package field above.

Summary: rpmdrake does not honor KDE color scheme for several elements => rpmdrake and MageiaUpdate do not honor KDE color scheme for several elements
Source RPM: rpmdrake-5.34-1.mga2 => perl-Gtk2 1.242.0-2.mga2

Comment 2 Samuel Verschelde 2013-09-05 15:04:49 CEST
Well, MageiaUpdate and rpmdrake are almost the same program, so I'll put the RPM field back to rpmdrake and the maintainer can correct me it that was a mistake.

Keywords: (none) => Triaged
CC: (none) => stormi
Assignee: bugsquad => thierry.vignaud
Source RPM: perl-Gtk2 1.242.0-2.mga2 => rpmdrake

Comment 3 Manuel Hiebel 2013-10-22 12:10:33 CEST
This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad
Comment 4 Manuel Hiebel 2013-11-23 16:14:00 CET
Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD