"this occurs for all semantically empty scripts." In fact the bug is more extensive.
The critical error message occurs for every file it reads unless each file contains one and ONLY one valid s-expression. As observed, empty files or files with commented out expressions produce it, as do files which contain more than one s-expression. I discovered the latter by trying to put two valid rules in one file and wondered why I was getting all these "critical" messages. So even wanting to go into debug mode means putting debug into its own debug.ds file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1190888 Title: CRITICAL **: e_sexp_eval: assertion `f->tree != NULL' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/devilspie/+bug/1190888/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
