[Expired for rhythmbox (Ubuntu) because there has been no activity for
60 days.]
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/29
Rhythmbox-metadata still uses 100% cpu when files are changing
continuously, but it seems to close down fine in 10.10.
Maybe there should be some kind of back-off mechanism? I remember
similar bugs filed with the nautilus thumbnailer some time ago. Not
sure how or even if those were resolved.
-
Could we have another confirmation from you rfugger if the issue is
happening with rhythmbox in Ubuntu-10.10 so that we could send this bug
report to the people writing the software.
** Changed in: rhythmbox (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned)
--
You receiv
I know what's causing the bug. It's when I'm downloading many video
files simultaneously into a subdirectory of my rhythmbox library
directory when I have rhythmbox set to "watch my library for new
files". As the downloading files are continually being updated,
rhythmbox continually tries to inde
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
rhythmbox-metadata process uses 100% cpu, even after closing app
https://bugs.launchpad.net/bugs/291813
You received this bug noti
It's not hanged -- it still works fine. It is obviously continually
trying to index all the constantly-changing video files that I'm
downloading.
--
rhythmbox-metadata process uses 100% cpu, even after closing app
https://bugs.launchpad.net/bugs/291813
You received this bug notification because
Could you attach gdb to that process to see why it's using alot of cpu?
it's probably hanged, please read
https://wiki.ubuntu.com/Backtrace#Already%20running%20programs
** Changed in: rhythmbox (Ubuntu)
Status: New => Incomplete
--
rhythmbox-metadata process uses 100% cpu, even after clos
Cannot provide a backtrace on program crash because there is no program
crash, just inappropriate program behaviour. I will be happy to provide
any other information you ask for to help remedy this problem.
** Changed in: rhythmbox (Ubuntu)
Status: Invalid => New
--
rhythmbox-metadata pr
Closing this bug report as no further information has been provided.
Please feel free to reopen this bug if you can provide the information
asked for. Thanks!.
** Changed in: rhythmbox (Ubuntu)
Status: Incomplete => Invalid
--
rhythmbox-metadata process uses 100% cpu, even after closing a
There is no program crash. This is a problem of using 100% cpu while
the program is running. The "even after closing app" part turned out
to be invalid, as I wrote above.
--
rhythmbox-metadata process uses 100% cpu, even after closing app
https://bugs.launchpad.net/bugs/291813
You received thi
Thanks for your bug report. Please try to obtain a backtrace
http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
bug report. This will greatly help us in tracking down your problem.
** Changed in: rhythmbox (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned)
Please note that 100% cpu behaviour still persists while app is
running... Just in case that wasn't clear.
--
rhythmbox-metadata process uses 100% cpu, even after closing app
https://bugs.launchpad.net/bugs/291813
You received this bug notification because you are a member of Ubuntu
Bugs, which
After further investigation, I am unable to replicate the 100% cpu
behaviour after closing the app. Possibly the app was just minimized to
the notification area and I didn't realize. Sorry.
--
rhythmbox-metadata process uses 100% cpu, even after closing app
https://bugs.launchpad.net/bugs/29181
Turns out the rhythmbox app main process was still active after I closed
the app, probably related to another bug I just filed
(https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/291810) where
my Sansa Clip player fails to show up in rhythmbox under intrepid. The
rhythmbox process was launch
14 matches
Mail list logo
