[Python-apps-team] Bug#678402: closed by أحمد المحمودي <aelmahmoudy at sabily.org> (Use --xvfb switch)
Michal Suchanek
michal.suchanek at ruk.cuni.cz
Tue Jul 10 09:01:18 UTC 2012
Excerpts from Debian Bug Tracking System's message of Fri Jun 29 11:21:19 +0200 2012:
> This is an automatic notification regarding your Bug report
> which was filed against the xpra package:
>
> #678402: xpra: does not run X startup scripts on start
>
> It has been closed by Ø£ØÙ
د اÙÙ
ØÙ
Ùد٠<aelmahmoudy at sabily.org>.
>
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ø£ØÙ
د اÙÙ
ØÙ
Ùد٠<aelmahmoudy at sabily.org> by
> replying to this email.
>
> tag 678402 +wontfix
> quit
> .
>
> Upstream responded to the bug as follows:
>
> It is not the role of xpra to deal with starting up the full X
> environment, that is what tools like winswitch
> (http://winswitch.org/about) are for.
Of course, this is not work of xpra.
Where is winswitch packaged in debian, though?
>
> If you must do it with xpra, you can always point --xvfb to a script
> of your choosing that starts whatever you require (dbus, etc).
As for that the Debian X session script that starts Xsession.d scripts,
~/.xsessionrc, and possibly some other undocumented scripts I don't even
know of it cannot be used with xpra because it insists on starting a window
manager. Patching in a 'dummy' session in addition to 'failsafe' should
not be hard but that mode is afaik not available.
Thanks
Michal
More information about the Python-apps-team
mailing list