After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 619036 - Words get switched around when typed into the Search bar
Words get switched around when typed into the Search bar
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: User Interface
1.7.0
Other Linux
: High major
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
: 620457 627329 628911 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-05-18 22:08 UTC by mxyzptlk
Modified: 2010-09-06 18:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mxyzptlk 2010-05-18 22:08:13 UTC
Overview: 
When typing a phrase into the search bar, the first word regularly appears after the second word. 


Steps to Reproduce: 
Start typing something into the search bar, like the name of a podcast, but it has to be more than one word -- eg. Ninja Tune Podcast, or The Linux Action Show!


Actual Results: 
Often -- not always -- your search would end up like:

 - Tune Ninja Podcast
 - Linux The Action Show!


Expected Results: 
It should register the phrase as typed.


Build Date & Platform: 
1.7.0-1~hyper1~lucid released on 2010-05-08 on Ubuntu Lucid. 


Additional Builds and Platforms: 
I also noticed this happening in the Ubuntu Lucid default 1.6.0-1 build.  


Additional Information:
I can't say for certain because I haven't had time to test it enough, but I think this is only happening on my laptop installation, and not on my desktop installation. I don't notice anything different about the installed files, but when I tested the search function on my desktop, it worked. But it rarely works on my laptop -- maybe 50% of the time.
Comment 1 Albert K 2010-05-20 05:29:30 UTC
Hi mxyzptlk
Could you run banshee --debug and try to reproduce the error? The debug log might provide some useful information about this issue.
Comment 2 mannheim89 2010-05-27 13:34:10 UTC
I can reproduce something that might be the same bug as this, using the backspace key in the search field, like so:

1. Type "aaaa bbbb" (without the quotes)
2. Hit the backspace key exactly four times.

Expected result: the search field shows "aaaa |" (where the bar indicates the cursor)

Actual result: the search field shows "|aaaa"

So the cursor jumps to the beginning of the search field whenever the cursor encounters a space, and the trailing space is deleted. This is 100% reproducible on my machine. 

So, if I type "Julian Bream" but make a typing error during "Bream" and correct it with the backspace key, I end up with "BreamJulian"
Comment 3 Aaron Bockover 2010-05-27 17:38:00 UTC
Confirmed - I see this as well.
Comment 4 Aaron Bockover 2010-05-27 17:38:45 UTC
It's an issue in the stable branch as well.
Comment 5 Alexander Kojevnikov 2010-06-03 10:36:12 UTC
*** Bug 620457 has been marked as a duplicate of this bug. ***
Comment 6 Chow Loong Jin 2010-07-10 15:20:10 UTC
I have bisected the regression down to the following commit:
commit dea6a184f9de4baf938f394db89b2e8b91b6f7bf
Author: Gabriel Burt <gabriel.burt@gmail.com>
Date:   Tue May 4 11:11:34 2010 -0700

    [MeeGo] Keep the search entries synced
    
    Keep the MeeGo panel search entry and the Nereid entry in sync with each
    other, so if you enter a query in one and switch to the other, it'll be
    there.

The corresponding commit in stable-1.6 is 781c691924ecde1dd9d372a825c5cab71d59a150.
Comment 7 Gabriel Burt 2010-07-11 20:25:04 UTC
Thanks a lot for tracking it down, hyperair!  Great sleuthing
Comment 8 Michael Monreal 2010-08-03 15:34:51 UTC
Severity "normal" does not really indicates that this completely destroys the search experience in banshee :(
Comment 9 Gabriel Burt 2010-08-10 23:22:06 UTC
Fixed
Comment 10 Alexander Kojevnikov 2010-08-19 04:23:25 UTC
*** Bug 627329 has been marked as a duplicate of this bug. ***
Comment 11 Michael Martin-Smucker 2010-09-06 18:22:46 UTC
*** Bug 628911 has been marked as a duplicate of this bug. ***