Hi there!
This is a known issue with amnThis is a known issue with using katapult
and amarok.
Unfortunately, there isn't a "fix" as of such, as amarok is always going
to be slow for us to access it's databaase.
However, there is a way to temporarily fix this issue.
If you load the configure Katapult menu, and look at the section
startingh "Amarok Catalog" then you should be able to set the number of
characters before it searches the amarok collection. If you set this to
a higher numnber than 1, then the amarok collection will not be searched
till after you have typed that amount of characters. I have mine set to
3, which I find useful
In 0.4, however, we do have catalogs running in their own threads, so
this will solve this issue then.
for now, I will create a patch to make katapult use 5 chars before
searching the amarok catalog by default.
Regards,
Martin Meredith
** Also affects: katapult (upstream)
Importance: Undecided
Status: Unconfirmed
** Changed in: katapult (upstream)
Importance: Undecided => Low
Assignee: (unassigned) => Martin Meredith
Status: Unconfirmed => Confirmed
Target: None => 0.4
** Changed in: katapult (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Martin Meredith
Target: None => ubuntu-6.10
--
Katapult slows down to a near crawl when amarok is open
https://launchpad.net/bugs/49901
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
