[Python-apps-team] Bug#681051: xpra: menus pop up off-screen

Antoine Martin antoine at nagafix.co.uk
Sun Aug 5 18:14:14 UTC 2012


On 07/13/2012 08:43 PM, Michal Suchanek wrote:
> Excerpts from Antoine Martin's message of Thu Jul 12 16:00:48 +0200 2012:
>>>>> Perhaps some sample script in documentation, or perhaps even a
>>>>> xorg.conf.dummy and a script in /usr/bin using it could be installed
>>>>> with xpra so that everyone does not have to figure out how the hell is
>>>>> that thing supposed to work.
>>>>>
>>>
>>>>> A sample script using xorg.conf.dummy could look like this:
>>>>>
>>>>> xpra --xvfb="Xorg -nolisten tcp -config xorg.conf.dummy -noreset +extension GLX +extension RANDR +extension RENDER -logfile ~/.xpra/xserver-$DISPLAY.log" --start-child="/etc/X11/Xsession true" start :$DISPLAY
>>>>>
>>>>> It is sad that you can't know what display xpra picks when starting it
>>>>> but without actually patching xpra you can't do more than that.
>>>> I think the config file option above is the easiest way to improve
>>>> things quickly?
>>>
>>> It requires that the xorg.conf linked on the wiki is installed at
>>> /etc/X11/xorg.conf.dummy
>>> Otherwise full path to the file is required.
>> Sure, I was thinking of putting it in:
>> /etc/xpra/xorg.conf.dummy
>> Next to xpra's config. Saves potential clashes with Xorg paths/packages
>> and keeps it more self-contained. But your suggested location also
>> works. Are there any guidelines on things like this?
>
> I guess it would be better to get the file into xserver-xorg-video-dummy
> package in this case.
Until that happens, current xpra trunk (what will become the 0.5.0 
release) now uses a default per-install config file in:
/etc/xpra/xpra.conf
which can be overriden with a per-user ~/.xpra/xpra.conf or via the 
command line. It also ships with a:
/etx/xpra/xorg.conf
Which is the dummy config Xorg needs.

Then at build time, one can use:
./setup.py --enable-Xdummy install
To make it install the default xpra.conf with Xdummy support.
If the "--enable-Xdummy" flag is not specified, it will try to run "Xorg 
-version" to figure out if support can be enabled (v>=1.12).
If that fails (for whatever reason), it will use the standard config 
file with "Xvfb", as before.

The beta packages I have just made depend on Xvfb for distros with old 
versions of Xorg (squeeze, precise, etc) and build with Xdummy 
dependencies and config file for the newer ones (wheezy, sid, quantal)
https://www.xpra.org/beta/

So, as far as I am concerned (barring any bugs or packaging issues I've 
missed), this issue is closed.

Cheers
Antoine

>
> Thanks
>
> Michal
>



More information about the Python-apps-team mailing list