You are not logged in.

#1 2013-10-03 16:16:09

Torxed
Member
Registered: 2013-01-10
Posts: 125

[SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Running xpra causes some headaches.
The application builds fine and installs just perfectly, the troubles comes from the default Xorg configuration is no longer stored in /etc/X11/xorg.conf, it's now stored and read from numerous files under /etc/X11/xorg.conf.d/ where just so happen to be my 5-nvidia.conf.

Starting xpra via:

xpra start :100

Causes:

X.Org X Server 1.14.3
Release Date: 2013-09-12
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.11.0-1-ARCH x86_64 
Current Operating System: Linux archie 3.11.2-1-ARCH #1 SMP PREEMPT Fri Sep 27 07:35:36 CEST 2013 x86_64
Kernel command line: root=/dev/sda1 rw initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux 
Build Date: 13 September 2013  01:28:59PM
 
Current version of pixman: 0.30.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(++) Log file: "/home/torxed/.xpra/Xorg.:100.log", Time: Thu Oct  3 19:56:30 2013
(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"
setversion 1.4 failed
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension SECURITY
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(EE) 
Fatal server error:
(EE) xf86OpenConsole: Cannot open /dev/tty0 (No such file or directory)
(EE) 
(EE) 
Please consult the The X.Org Foundation support 
         at http://wiki.x.org
 for help. 
(EE) Please also check the log file at "/home/torxed/.xpra/Xorg.:100.log" for additional information.
(EE) 
(EE) Server terminated with error (1). Closing log file.
2013-10-03 19:56:30,893 
2013-10-03 19:56:30,893 Xvfb command has terminated! xpra cannot continue
2013-10-03 19:56:30,894 
2013-10-03 19:56:30,895 removing socket /home/torxed/.xpra/archie-100

tl;dr: 5-nvidia.conf is trying to get loaded after xf86-video-dummy is loaded (which is the default for xpra).


Now to the question: What's the best practice because there's no information about this issue, and i can't be the only one who's run in to this since the xorg.conf was removed. At the moment I move all my nvidia configs out of the way, start xpra and move them back in. This works for the better part as long as i execute xpra with my own scripts.

But is there a better way (which doesn't perhaps include recreating xorg.conf since that appears to be something you should walk away from)?

Last edited by Torxed (2013-10-04 10:29:35)

Offline

#2 2013-10-03 17:36:07

Raynman
Member
Registered: 2011-10-22
Posts: 1,154

Re: [SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Xorg (like other apps) has options to direct it to a config file/dir other than the default. The lines

(++) Using config file: "/etc/xpra/xorg.conf"
(==) Using config directory: "/etc/X11/xorg.conf.d"

indicate that xpra (whatever it is) passes -config, but not -configdir. If you can get it to include that option when starting X, you should be fine.

Offline

#3 2013-10-04 10:12:25

Torxed
Member
Registered: 2013-01-10
Posts: 125

Re: [SOLVED]xpra + winswitch - best practice due to /etc/X11/xorg.conf.d/*

Good thinking! (xpra is basically just screen but for x, or a X11 tunnel via SSH).

After a really quick poking around and remembering that xpra really just uses xorg-server-xvfb and at the very bottom of /etc/xpra/xpra.conf there's a line that says:

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

Appending -configdir appears to be working.

Here are the full steps:

[torxed@archie ~]$ sudo cp -r /etc/X11/xorg.conf.d /etc/xpra/
[torxed@archie ~]$ sudo rm /etc/xpra/xorg.conf.d/*nvidia*
[torxed@archie ~]$ sudo sed -i '$s/$/ -configdir \/etc\/xpra\/xpra.conf.d/' /etc/xpra/xpra.conf

*nvidia* would have to match your graphic-driver-config that would cause xorg-server-xvbf to crash.


I'll update the wiki and put a mention on the package about it because this either has to be standard or well known from the start because it really just breaks the package all together.

Last edited by Torxed (2013-10-04 10:29:09)

Offline

Board footer

Powered by FluxBB