|
|
| Reporter | legrandewen | Assigned To | | |
|---|
| Priority | immediate | Severity | block | Reproducibility | random |
|---|
| Status | closed | Resolution | no change required | |
|---|
| Platform | Armv7 | OS | CentOS Linux release 7.6.1810 | OS Version | 7.6.1810 |
|---|
|
|
| Summary | 0017433: .Xauthority-c and .Xauthority-l lock files generated after using startx command |
|---|
| Description | At boot, our web application is launched by the command startx ( The startx(1) script is a front-end for xinit(1). The xinit program allows a user to manually start an Xorg display server.) and is displayed on the screen.
But sometimes, we get an error just after a reboot : " timeout in locking authority file /home/prescom/.Xauthority " and the web application can't start anymore (even after few reboot). If we manually launch the web application using startx, we get the error "no protocol specified".
After analysis, two lock file are present in the /home/user folder : .Xauthority-c and .Xauthority-l
Those files are lock files for .Xauthority, so simply removing them resolves the issue.
We need to know Why and how the lock files are generated ?
Thank you for your support,
Ewen Legrand
Research engineer,
Tel : +33 (0) 7 71 92 75 55 / 02 96 05 76 06
ewen.legrand@prescom.fr
PRESCOM
Rue de Broglie , 22300 LANNION , FRANCE
www.prescom.fr
NB : the xinit command executed is as follows : " xinit /home/prescom/.xinitrc -- -auth /home/prescom/.server.xxxx /usr/bin/X :2 -nocursor "
|
|---|
| Steps To Reproduce | random |
|---|
| Additional Information | NB : the xinit command executed is as follows : " xinit /home/prescom/.xinitrc -- -auth /home/prescom/.server.xxxx /usr/bin/X :2 -nocursor "
Link forum solution : https://unix.stackexchange.com/questions/215558/why-am-i-getting-this-message-from-xauth-timeout-in-locking-authority-file-ho |
|---|
| Tags | #Centos7, armv7, centos7, serverx, startx, xauthority, xinit, Xorg |
|---|
|
|
| abrt_hash | |
|---|
| URL | |
|---|
|
|
