Bugzilla – Bug 12465
Keyboard text entry remains blank
Last modified: 2009-10-06 09:22:34 UTC
r6189. The cursor moves, but no characters are echoed. Looks like the artwork is hosed as well.
*** Bug 12506 has been marked as a duplicate of this bug. ***
Apparently the characters are now black and the background on the inside of the text box is transparent. This can be seen if you change the wallpaper, then do something like add an alarm, where you use the keyboard. During setup, with an all black wallpaper, this gives the net effect of seeing no characters echoed.
*** Bug 12573 has been marked as a duplicate of this bug. ***
This is a build issue with the graphic asset. Some extra chars are being appended on to the filename so the skin is not finding the image: the file that should be named text_entry_titlebar_box.png is named text_entry_titlebar_box.png0000644 it looks like the umask is being appended to the filename. very strange. this bug is seen in two other images in the skin directory, but neither of those are being used right now so it's only apparent with this one. important to figure out the root cause of the file naming problem so it doesn't happen again.
Incorrectly targetted. Fab4 MP has already happened
This error does not happen on MP r5969 firmware, only on POST MP firmware
This is sometimes frustrating for testing.
the immediate workaround is to use a light colored wallpaper. It's black text on a transparent background...if your wallpaper is dark it's going to be unreadable, but if it's light you won't have any trouble.
That doesn't help at all during initial setup, where the background is black. Anyone who has been through setup recently and had to blindly key in a 30 or 40 character wireless passphrase is going to be very reluctant to do it again. I would have thought that something so fundamental to setup would have been given a much higher priority.
I agree. This needs to fixed sooner rather than later. It's currently crazy hard testing setup issues with it in this state.
fix attempt r6561 is checked into a separate branch and will be merged back later this week. No way to confirm the fix yet because this is an issue with the build server, not with code on my side. Tried the brute force approach of deleting the existing one from the repository and checking it back in under a different file name.
*** Bug 12864 has been marked as a duplicate of this bug. ***
This bug has been fixed in the latest release of MySqueezebox.com (formally known as SqueezeNetwork)! If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.