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 608415 - [OS X] Pango font rendering issue 'fi'
[OS X] Pango font rendering issue 'fi'
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: User Interface
1.5.4
Other Mac OS
: High normal
: 1.6
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-29 06:25 UTC by Tom Byrne
Modified: 2010-03-23 22:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Tom Byrne 2010-01-29 06:25:28 UTC 
Just downloaded the repacked 1.5.3 w/Mono and removed the system Mono. It starts right up no errors but I am getting an odd issue. It seems the string 'fi' is replaced by another character. See link below.

http://imgur.com/nBWsW

This error is not present in the track listing section, all the filenames are correct. Only in the Preferences pane.

Also, when i enter text into the search field 'f' for instance it goes fullscreen or if 'n' is entered it goes to the next song. It seems like it doesn't know where the focus is. Only characters that aren't binded to shortcuts appear in the search box. 

NOTE: Neither of these issues are present on 1.4.3 w/ MonoFramework 2.2.
Comment 1 Aaron Bockover 2010-01-29 06:47:15 UTC 
These are all known issues due to [possible] Pango regressions. We are looking into fixes. Banshee for OS X will track any efforts of Mono and MonoDevelop for OS X.
Comment 2 Aaron Bockover 2010-03-04 00:10:12 UTC 
The keyboard input issues are fixed in 1.5.4...

As these are two separate bugs, there should have been two separate bug reports, so the input issue could have been closed.

Reducing severity since the "fi" issue is not critical, just annoying.

For future record, if you find yourself saying "Also..." and describing something different, that's a good indicator that a separate bug report would be appreciated :)

Thanks
Comment 3 Tom Byrne 2010-03-15 06:31:45 UTC 
Any progress on this issue in the OS X build for 1.5.5?
Comment 4 Aaron Bockover 2010-03-23 22:25:29 UTC 
This is fixed. A 1.5.7 build for OS X will be available later today.