xpra icon
Bug tracker and wiki

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#179 closed defect (fixed)

no Xdummy support out of the box.

Reported by: onlyjob Owned by: Antoine Martin
Priority: major Milestone: 0.5
Component: core Version: trunk
Keywords: Cc:

Description

Xdummy support doesn't work "out of the box" in just released 0.5.0 probably because xpra is ignoring 'xvfb=' option in /etc/xpra/*/xpra.conf.

I built xpra using '--enable-Xdummy' and correct xdummy 'xorg.conf' was installed to /etc/xpra.

'xpra start :8' started with xvfb.

I uncommented

xvfb=/usr/bin/Xorg -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg.${DISPLAY}.log -config /etc/xpra/xorg.conf

in /etc/xpra/Xvfb/xpra.conf but it didn't help.
(in /etc/xpra/Xdummy/xpra.conf 'xvfb=' is already uncommented)

The very same configuration line given as argument to xpra worked but applications were starting with big fonts so a had to add '-dpi 96' which produced the following argument:

--xvfb="/usr/bin/Xorg -dpi 96 -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER -logfile ${HOME}/.xpra/Xorg.8.log -config /etc/xpra/xorg.conf"

that successfully started Xdummy.

I tried this all on Debian Wheezy with xserver-xorg-video-dummy/1:0.3.5-2+b1

Also xdummy's xorg.conf have the following lines:

  #The following modeline is invalid (calculator overflowed):
  #Modeline "32000x32000@0" -38917.43 32000 32032 -115848 -115816 32000 32775 32826 33601

You probably used http://xtiming.sourceforge.net/cgi-bin/xtiming.pl aren't you? ;)

Calculator 'cvt' provided by package 'xserver-xorg-core' produced the following Modeline:

# 32000x32000 10.00 Hz (CVT) hsync: 321.80 kHz; pclk: 14514.25 MHz
Modeline "32000x32000_10.00"  14514.25  32000 34952 38552 45104  32000 32003 32013 32180 -hsync +vsync

Similar Modeline was generated by http://www.arachnoid.com/modelines/

# 32000x32000 @ 10.00 Hz (GTF) hsync: 321.78 kHz; pclk: 14518.71 MHz
Modeline "32000x32000_10.00" 14518.71 32000 34952 38560 45120 32000 32001 32004 32178 -HSync +Vsync

Thank you.

Change History (3)

comment:1 Changed 8 years ago by Antoine Martin

Status: newaccepted

Installing the correct /etc/xpra/xpra.conf is a packaging issue (..).

The distutils setup.py tries to detect if the version of Xorg is recent enough - unless one uses --enable-Xdummy which is useful when the build machine does not have Xorg installed.

I've just checked again and the packages that I made do have the correct configuration for both squeeze and wheezy.
Also, I do not understand why you have those directories in /etc, this is all you should have (and what is in the packages I made):

/etc/xpra/xpra.conf
/etc/xpra/xorg.conf

Nothing else... Can you confirm how you installed it? Something seems to have gone wrong there.
The reason why uncommenting that line did not do anything is because that file is not meant to exist and is not used for anything (see above).


About the dpi: I will probably add 96dpi as default since it is sensible, but the dpi should already be correct if you connect your client before starting the app.


As for the modelines, I will also try those - not that there is any urgency as I don't think many people use 32kx32k resolutions. Also, this requires more memory to be allocated to the dummy driver, and there are still bugs with toolkits and applications above 16kx16k (irrc)

comment:2 in reply to:  1 ; Changed 8 years ago by onlyjob

Resolution: fixed
Status: acceptedclosed

Replying to antoine:

Installing the correct /etc/xpra/xpra.conf is a packaging issue (..).


Of course that's the case, how embarrassing. :)
If .conf files are installed to correct location (/etc/xpra) there is no problem whatsoever.

Thank you.

The distutils setup.py tries to detect if the version of Xorg is recent enough - unless one uses --enable-Xdummy which is useful when the build machine does not have Xorg installed.


Yes, I've noticed this from reading setup.py.

I've just checked again and the packages that I made do have the correct configuration for both squeeze and wheezy.


Thank you for checking and sorry for troubles.

Also, I do not understand why you have those directories in /etc, this is all you should have (and what is in the packages I made):

/etc/xpra/xpra.conf
/etc/xpra/xorg.conf


My mistake, sorry.

Nothing else... Can you confirm how you installed it? Something seems to have gone wrong there.


I was using incorrect line in xpra.install -- packaging issue, as you've said.

About the dpi: I will probably add 96dpi as default since it is sensible, but the dpi should already be correct if you connect your client before starting the app.


This is very interesting, perhaps worth mentioning somewhere in README. I will add a note to Debian packaging.

As for the modelines, I will also try those - not that there is any urgency as I don't think many people use 32kx32k resolutions. Also, this requires more memory to be allocated to the dummy driver, and there are still bugs with toolkits and applications above 16kx16k (irrc)


Thanks, of course there is no urgency, I just noticed and let you know.

Thank you.

comment:3 in reply to:  2 Changed 8 years ago by Antoine Martin

(...)

About the dpi: I will probably add 96dpi as default since it is sensible, but the dpi should already be correct if you connect your client before starting the app.

This is very interesting, perhaps worth mentioning somewhere in README. I will add a note to Debian packaging.

OK, trunk now has "-dpi 96" as of r1341. I will apply this to the 0.5.x branch after further testing.


As for the modelines, I will also try those - not that there is any urgency as I don't think many people use 32kx32k resolutions. Also, this requires more memory to be allocated to the dummy driver, and there are still bugs with toolkits and applications above 16kx16k (irrc)


Thanks, of course there is no urgency, I just noticed and let you know.

I've committed the new modelines in r1340, the file now includes a note explaining how to get those to work (bump ram). The current highest resolution supported with the 256M allocated to the dummy video card is 8192x4096. (which should take 128M at 4 bytes per pixel - seems about right)

Note: See TracTickets for help on using tickets.