Bug: Inputing text displays the Red Box of Doom in latest Pharo on Windows
Windows build is broken to the degree of becoming completely unusable . Trying to type in any tool, workspace , system browser etc. it displays the Red Box with the yellow X displaying MNU: FixedFaceFont >> glyphInforOf: into: Went into settings, to change the standard font in case its a font problem. It could not find my system fonts but it so I choose the one that was available with force all. Did not solve the problem. That means I can't input code in any way. Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ? -- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-late... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
I can't reproduce the problem on Ubuntu. Works fine on my Ubuntu amd64 13.04. Can someone else confirm the problem on Windows ? I use Windows 7 64 bit. kilon wrote
Windows build is broken to the degree of becoming completely unusable . Trying to type in any tool, workspace , system browser etc. it displays the Red Box with the yellow X displaying MNU: FixedFaceFont >> glyphInforOf: into:
Went into settings, to change the standard font in case its a font problem. It could not find my system fonts but it so I choose the one that was available with force all. Did not solve the problem.
That means I can't input code in any way.
Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ?
-- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-late... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ?
Because nobody on windows reviewed the slice. Your issue is not that easy to detect automatically, and testing a slice under 3 platform manually is just overkill... So If you want to contribute, write some UI tests ;) and help fixing the CI project: http://smalltalkhub.com/#!/~Pharo/ci You found the bug, that's what counts.
fair enough , I will be testing latest builds in all 3 OSes from now on. So consider me as your "happy to test" bot for now on Writing UI tests sounds reasonable to me. Sure will give it a try . Will also take a look at CI. Camillo Bruni-3 wrote
Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ?
Because nobody on windows reviewed the slice.
Your issue is not that easy to detect automatically, and testing a slice under 3 platform manually is just overkill...
So If you want to contribute, write some UI tests ;) and help fixing the CI project: http://smalltalkhub.com/#!/~Pharo/ci
You found the bug, that's what counts.
signature.asc (457 bytes) <http://forum.world.st/attachment/4714286/0/signature.asc>;
-- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-late... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
I have the same bug on Pharo 3.0 on Ubuntu 13.10 64bits. Changed the font, and then all text with an utf8 character got this MNU (but on LogicalFont). Unable to change it back: the font dialog is now showing only one font instead of the 50+ the system has. Thierry Le 14/10/2013 11:22, kilon a écrit :
Windows build is broken to the degree of becoming completely unusable . Trying to type in any tool, workspace , system browser etc. it displays the Red Box with the yellow X displaying MNU: FixedFaceFont >> glyphInforOf: into:
Went into settings, to change the standard font in case its a font problem. It could not find my system fonts but it so I choose the one that was available with force all. Did not solve the problem.
That means I can't input code in any way.
Question : why such fundamental and very easy to find out problem went into the build process ? Are you not checking the build on win / mac and linux before committing it ? I know Pharo 3.0 is alpha and I most certainly expect to find a fair share of bugs in it. But this is just to obvious and easily avoided. Am I missing something here ?
-- View this message in context: http://forum.world.st/Bug-Inputing-text-displays-the-Red-Box-of-Doom-in-late... Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
-- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
On Oct 14, 2013, at 12:44 PM, Goubier Thierry <thierry.goubier@cea.fr> wrote:
I have the same bug on Pharo 3.0 on Ubuntu 13.10 64bits.
Changed the font, and then all text with an utf8 character got this MNU (but on LogicalFont). Unable to change it back: the font dialog is now showing only one font instead of the 50+ the system has.
Yes, there was something wrong with the font related update last week⦠normally it should have set new fonts but it does not. Marcus
participants (4)
-
Camillo Bruni -
Goubier Thierry -
kilon -
Marcus Denker