enso crashes when caps lock + del

[blackdaemon]

What steps will reproduce the problem?
1. Using enso_linux, open the quasimode window (caps lock)
2. Hit the del key
3. enso crashes.

What is the expected output? What do you see instead?

No crash, maybe an output in the terminal I'm running enso from:

INFO:root:Deleting the quasimode window.

What version of the product are you using? On what operating system?

Latest trunk both for enso and enso_linux

Please provide any additional information below.
Traceback (most recent call last):
  File "threading.py", line 460, in __bootstrap
    self.run()
  File "/home/matsubara/devel/enso/trunk/linux/enso_linux/input.py", line
149, in run
    self.__callback (make_event ("quasimodeEnd"))
  File "/home/matsubara/devel/enso/trunk/linux/enso_linux/input.py", line
265, in __keyCallback
    KEYCODE_QUASIMODE_END)
  File "/home/matsubara/devel/enso/trunk/core/enso/events.py", line 283, in
onKeypress
    func( eventType, keyCode )
  File "/home/matsubara/devel/enso/trunk/core/enso/quasimode/__init__.py",
line 199, in onKeyEvent
    self.__quasimodeEnd()
  File "/home/matsubara/devel/enso/trunk/core/enso/quasimode/__init__.py",
line 342, in __quasimodeEnd
    self.__showBadCommandMsg( userText )
  File "/home/matsubara/devel/enso/trunk/core/enso/quasimode/__init__.py",
line 386, in __showBadCommandMsg
    messages.displayMessage( text )
  File "/home/matsubara/devel/enso/trunk/core/enso/messages/__init__.py",
line 432, in displayMessage
    MessageManager.get().newMessage( msg )
  File "/home/matsubara/devel/enso/trunk/core/enso/messages/__init__.py",
line 330, in newMessage
    self.__newPrimaryMessage( msg )
  File "/home/matsubara/devel/enso/trunk/core/enso/messages/__init__.py",
line 406, in __newPrimaryMessage
    self.__primaryMsgWind.setMessage( msg )
  File
"/home/matsubara/devel/enso/trunk/core/enso/messages/primarywindow.py",
line 146, in setMessage
    self.__drawMessage()
  File
"/home/matsubara/devel/enso/trunk/core/enso/messages/primarywindow.py",
line 259, in __drawMessage
    height )
  File
"/home/matsubara/devel/enso/trunk/core/enso/messages/primarywindow.py",
line 330, in __layoutText
    ellipsify = "true",
  File
"/home/matsubara/devel/enso/trunk/core/enso/messages/primarywindow.py",
line 504, in layoutMessageXml
    _tagAliases
  File
"/home/matsubara/devel/enso/trunk/core/enso/graphics/xmltextlayout.py",
line 707, in xmlMarkupToDocument
    xml.sax.parseString( text, xmlMarkupHandler )
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/__init__.py", line
47, in parseString
    parser.parse(inpsrc)
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line
109, in parse
    xmlreader.IncrementalParser.parse(self, source)
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/xmlreader.py", line
123, in parse
    self.feed(buffer)
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/expatreader.py", line
220, in feed
    self._err_handler.fatalError(exc)
  File "/usr/lib/python2.5/site-packages/_xmlplus/sax/handler.py", line 38,
in fatalError
    raise exception
SAXParseException: <unknown>:1:53: reference to invalid character number

[blackdaemon (blackdaemon)]

omment 1 by ebjono, Mar 21, 2008

Added some labels to the ticket. It's a problem in the layout of the message XML, so
it's component-messages, and it's something we need to fix for basic usability on
Linux, so I'm marking it milestone 0.1.