interpret search function is not able to treat name fragments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
rhythmbox (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
After clicking in the Interpret list, it is possible to start the search function with simple tipping in.
The problem is that the search function is not very performant.
Searching for e.g "Justing Cronin" with the search term "Cronin" do not do(the name is mannually checked in the list).
The search is only able to find exact matches.
Steps to reproduce:
1. Have some Interpret names in the list.
2.Start a search a describted above with a fragment.
3.See that rhythmbox is not able to find simplest request. Only exact matches are working. No search with the second part of a name is possible.
Expected: A user has not always the full name of a Interpret in mind. Search with simple parts of the name should be possible.
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: rhythmbox 2.98-0ubuntu5
ProcVersionSign
Uname: Linux 3.8.0-26-generic x86_64
NonfreeKernelMo
ApportVersion: 2.9.2-0ubuntu8.2
Architecture: amd64
Date: Sat Jul 6 18:17:04 2013
ExecutablePath: /usr/bin/rhythmbox
InstallationDate: Installed on 2013-01-13 (174 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
LogAlsaMixer:
Simple mixer control 'IEC958',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
MarkForUpload: True
SourcePackage: rhythmbox
UpgradeStatus: Upgraded to raring on 2013-04-18 (78 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect <bug #> and any other logs that are relevant for this particular issue.