Bug 180834

Summary:	Dragon player causes many wakeups (powertop) while idle
Product:	[Applications] dragonplayer	Reporter:	Alberto Gonzalez <luis6674>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	rakuco, sitter, sts
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alberto Gonzalez 2009-01-15 16:48:23 UTC

Version:           2.0 (using Devel)
Compiler:          gcc 4.3.2 
OS:                Linux
Installed from:    Compiled sources

Using Xine as a phonon backend, if I open Dragon Player and leave it there idle (not playing any media) it causes more than 100 wakeups per second as reported by Powertop.

Switching to gstreamer backend solves the problem completely, so it might be a xine issue (in fact xine-ui also suffers this problem). However, KDE-4.1 had this problem (knotify) and it's been solved in 4.2 (I'm using 4.1.96). So maybe it is possible to also fix it in Dragon independently of xine? Amarok using also phonon-xine doesn't have this problem.

Thanks.

Comment 1 Raphael Kubo da Costa 2009-07-13 23:32:46 UTC

For now, I'm marking it as NEW - dragon is shown in the first place in the top causes for wakeups. I'm just not sure if this is Dragon's fault, though.

Comment 2 Harald Sitter 2012-05-31 22:54:06 UTC

still a problem with an actually working phonon backend?

if so a callgrind and cachegrind log would be cool.

Comment 3 Andrew Crouthamel 2018-09-23 02:40:26 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 4 Andrew Crouthamel 2018-10-27 02:29:37 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!