Bug 1284270 - High CPU and not finishing, when "Watch my library for new files" is selected
Summary: High CPU and not finishing, when "Watch my library for new files" is selected
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: rhythmbox
Version: 25
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David King
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-11-22 16:28 UTC by Steve
Modified: 2017-12-12 11:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-12 11:10:14 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Steve 2015-11-22 16:28:10 UTC
Description of problem:
After upgrading to F23 (from F22), Rhythmbox has very high CPU usage and does not finish the "Watch my library for new files", when it is selected. Means, Rhythmbox does not finishing adding new files. When it is deselected, and after killing and restart, everything is fine. The files are on NFS.

Version-Release number of selected component (if applicable):
rhythmbox-3.2.1-3.fc23.x86_64

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Steve 2016-01-12 15:06:39 UTC
This bug is not fixed in version rhythmbox-3.2.1-5.fc23.x86_64

Comment 2 Steve 2016-06-30 06:43:27 UTC
The bug seems not to be fixed in rhythmbox-3.3.1-1.fc23.x86_64.

Comment 3 Steve 2016-06-30 08:18:06 UTC
This bug persists in F24, rhythmbox-3.3.1-1.fc24.x86_64.

Comment 4 Steve 2016-09-14 09:16:24 UTC
No changes in rhythmbox-3.4.1-1.fc24.x86_64.

Comment 5 Fedora Admin XMLRPC Client 2016-09-15 15:17:49 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Admin XMLRPC Client 2016-09-16 07:10:18 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Steve 2016-12-23 04:59:22 UTC
This bug persists in Fedora 25, rhythmbox-3.4.1-1.fc25.x86_64.

Comment 8 Fedora End Of Life 2017-11-16 19:07:14 UTC
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. 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 '25'.

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 25 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 9 gkrithi8 2017-11-18 02:39:44 UTC
If this issue is reproducible, report to rhythmbox upstream at:

https://bugzilla.gnome.org/enter_bug.cgi?product=rhythmbox

Comment 10 Steve 2017-11-27 16:45:15 UTC
Ok.

Comment 11 Fedora End Of Life 2017-12-12 11:10:14 UTC
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.