xpra icon
Bug tracker and wiki

Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#1127 closed defect (fixed)

xpra starts x11-server with xorg log in ~/.xpra but does not create it

Reported by: urzds Owned by: urzds
Priority: major Milestone: 0.17
Component: server Version: trunk
Keywords: Cc:

Description

When setting XPRA_LOG_DIR and --log-dir to /tmp, Xpra will not create ~/.xpra, but still starts instructs the X11 server to log there:

+ ls -la /home/xpra
total 20
drwx------ 2 xpra xpra 4096 Feb 18 18:09 .
drwxr-xr-x 3 root root 4096 Feb 18 18:09 ..
-rw-r--r-- 1 xpra xpra   18 Aug 18  2015 .bash_logout
-rw-r--r-- 1 xpra xpra  193 Aug 18  2015 .bash_profile
-rw-r--r-- 1 xpra xpra  231 Aug 18  2015 .bashrc
+ xpra start :100 --daemon=no --log-dir=/tmp --socket-dir=/tmp --bind-tcp=0.0.0.0:30000 --start-child=xterm
2016-02-18 18:09:12,376 Warning: failed to load the mdns avahi publisher: No module named avahi
2016-02-18 18:09:12,376  either fix your installation or use the 'mdns=no' option
(EE) 
Fatal server error:
(EE) Cannot open log file "/home/xpra/.xpra/Xorg.:100.log"
(EE) 
(EE) 
Please consult the Fedora Project support 
         at http://wiki.x.org
 for help. 
(EE) 
could not connect to X server on display ':100' after 3 seconds
2016-02-18 18:09:15,385 closing tcp socket 0.0.0.0:30000
2016-02-18 18:09:15,386 removing socket /tmp/62fc0769750c-100
+ ls -la /home/xpra
total 24
drwx------ 2 xpra xpra 4096 Feb 18 18:09 .
drwxr-xr-x 4 root root 4096 Feb 18 18:09 ..
-rw------- 1 xpra xpra   59 Feb 18 18:09 .Xauthority
-rw-r--r-- 1 xpra xpra   18 Aug 18  2015 .bash_logout
-rw-r--r-- 1 xpra xpra  193 Aug 18  2015 .bash_profile

It should probably respect --log-dir also for the location of the xorg.log.

I am using the Fedora rawhide package of Xpra 0.16.1.

Change History (4)

comment:1 Changed 4 years ago by Antoine Martin

Owner: changed from Antoine Martin to urzds

This overlaps with #1129.
As of version 0.17, we place the Xorg log file in /run/user/$UID/xpra on Fedora:

xvfb=xpra_Xdummy -noreset -nolisten tcp +extension GLX +extension RANDR +extension RENDER \
    -auth $XAUTHORITY -logfile /run/user/$UID/xpra/Xorg.${DISPLAY}.log \
    -configdir ${HOME}/.xpra/xorg.conf.d -config /etc/xpra/xorg.conf

I'm not sure how we would ensure the directory exists since we don't really know in advance what it is going to be set to. (I wouldn't want to parse that string)
I would gladly accept a patch to the man page to add warning there.
Any other ideas?

Last edited 4 years ago by Antoine Martin (previous) (diff)

comment:2 Changed 4 years ago by Antoine Martin

Looking into it, I found that we did already parse the logfile argument to support automatic display selection.
So r11990 fixes this and uses 0700 permissions for the directory it creates.

@urzds: if that works for you, please close.

Last edited 4 years ago by Antoine Martin (previous) (diff)

comment:3 Changed 4 years ago by Antoine Martin

Resolution: fixed
Status: newclosed

Not heard back, closing.

comment:4 Changed 4 years ago by urzds

@urzds: if that works for you, please close.

This appears to work and I make use of it by setting XDG_RUNTIME_DIR=~/.xpra as described in ticket:1129#comment:19

Note: See TracTickets for help on using tickets.