Bug 1151767 - With zukitwo gtk theme xfce4-cpugraph-plugin doesn't show CPU usage bars
Summary: With zukitwo gtk theme xfce4-cpugraph-plugin doesn't show CPU usage bars
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-cpugraph-plugin
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-10-11 17:05 UTC by Artem S. Tashkinov
Modified: 2015-06-29 22:52 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:52:00 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
A problem with Zukitwo theme (4.75 KB, image/png)
2014-10-11 17:05 UTC, Artem S. Tashkinov
no flags Details
Adwaita is OK (6.18 KB, image/png)
2014-10-11 17:05 UTC, Artem S. Tashkinov
no flags Details

Description Artem S. Tashkinov 2014-10-11 17:05:35 UTC
Created attachment 945979 [details]
A problem with Zukitwo theme

Version-Release number of selected component (if applicable): 
xfce4-cpugraph-plugin-1.0.5-4.fc20.x86_64

How reproducible: always


Steps to Reproduce:
1. yum install zukitwo-gtk2-theme zukitwo-gtk3-theme
2. select this theme in XFCE settings
3.

Actual results: xfce4-cpugraph-plugin doesn't show CPU usage bars


Expected results: CPU usage shown


Additional info: screenshots will be attached

Comment 1 Artem S. Tashkinov 2014-10-11 17:05:58 UTC
Created attachment 945980 [details]
Adwaita is OK

Comment 2 Christoph Wickert 2015-02-12 17:13:48 UTC
Sorry for the late response.

Can you reproduce the issue with another theme? If not, it is probably the theme's fault and not the cpu-graph's. Please also try with a different plugin, e.g. the mixer. If this has the same issue, we know it is the theme for sure.

P.S.: Please don't classify this bug as "urgent", because "urgent" is defined as "catastrophic issues which severely impact the mission-critical operations of an organization." This is definitely not the case here, therefor I will reset the urgency accordingly.

Comment 3 Artem S. Tashkinov 2015-02-23 12:41:56 UTC
(In reply to Christoph Wickert from comment #2)

> Can you reproduce the issue with another theme?

No.

> If not, it is probably the theme's fault and not the cpu-graph's.

Probably, but it's not really a consolation.

> Please also try with a different plugin, e.g. the mixer.

The mixer doesn't have any bars, so, nothing to check.

Comment 4 Fedora End Of Life 2015-05-29 13:04:08 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

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 Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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 Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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 Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-06-29 22:52:00 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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


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