Bug 528477
Summary: | xine-lib produces lots of CPU wakeups in Amarok while doing nothing | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | RJ <ogldelphi> |
Component: | xine-lib | Assignee: | Rex Dieter <rdieter> |
Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 11 | CC: | fedora, kevin, rdieter, smparrish |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | http://bugs.xine-project.org/show_bug.cgi?id=189 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2009-11-24 20:58:04 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
RJ
2009-10-12 12:47:41 UTC
Thank you for taking the time to report this issue. This is an issue that needs to be addressed by the upstream developers. Please report this at http://bugs.kde.org and then add the upstream report information to this report. We will monitor the upstream report for a resolution to this issue, and will review any bug fixes that become available for consideration in future updates. Setting status to NEEDINFO, and awaiting upstream bug report URL for tracking. Thanks in advance. -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Here it is, https://bugs.kde.org/show_bug.cgi?id=210409 p.s I'm very interested in help fixing wakeup or power consumption bugs. previous bug marked as DUPLICATE of bug 204114 (https://bugs.kde.org/show_bug.cgi?id=204114) sorry not redhat's one but KDE's 204114 I have added it in external bug (didn't see this function before) Amarok developers have discovered that the bug is somewhere in xine-lib. I could not post bug report in xine bugzilla because of 503 error on that server, so I have changed "component" field here. Same bug in xine bugzilla http://bugs.xine-project.org/show_bug.cgi?id=189 OK, let's continue to track it upstream. |