On Wed, Feb 4, 2009 at 8:13 PM, Antoine Martin <[email protected]> wrote: > Nathaniel Smith wrote: >> Are you hoping to run parti, or xpra? > Either, I was just toying with this.
Ah, gotcha. >>> File "wimpiggy.lowlevel.bindings.pyx", line 423, in >>> wimpiggy.lowlevel.bindings.XGetWindowProperty >>> TypeError: exceptions must be strings, classes, or instances, not type >> >> That's... weird. The code itself appears correct. >> >> What version of Python and Pyrex are you using? > pyrex-0.9.4.1 > python-2.5.2-r7 It looks like the problem is that if you're using Python 2.5, then Pyrex versions before 0.9.6 have totally broken exception support: http://osdir.com/ml/python.pyrex/2008-04/msg00062.html So try uprading Pyrex, and let me know if that helps? > xpra just would not start using > install/bin/xpra start :13 > > I eventually found some info in ~/.xpra/\:13.log > "File not found" error (but not telling you which one;) > The source told me it was xmodmap... And after installing it, xpra/Xvfb > is now working fine. Thanks for the report! This is a bit tricky, actually... the problem is that by the time the call to xmodmap fails, the server has already gone into daemon mode, and no longer has the ability to write stuff back to the console. But we can't spawn Xfvb until we're in daemon mode... So now: - 'xpra start' prints the location of the log file just before daemonizing - subprocess spawns should all write informative messages to the log if they fail Good luck, -- Nathaniel _______________________________________________ Parti-discuss mailing list [email protected] http://lists.partiwm.org/cgi-bin/mailman/listinfo/parti-discuss
