I have just installed the 9.1 Pro upgrade this morning. Most things seem to be working right, but my old buddy "sux" no longer gives the root user access to the display. After doing "sux -", I do become the root user, but running any X application gives me errors like: michaeln@seahunt:~> sux - Password: seahunt:~ # id uid=0(root) gid=0(root) groups=0(root) seahunt:~ # xclock Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server Error: Can't open display: :0 seahunt:~ # I have been using sux for so long now I forgot how to solve this. It's always just worked in the past. There doesn't seem to be a man page for sux, and sux --help just gives a usage message that isn't particularly helpful. Has anyone else seen this? Thanks Michael
I don't think it's very safe, but I always use: xhost + which allows su (or anyone for that matter) to connect to X. Michael Nelson wrote:
I have just installed the 9.1 Pro upgrade this morning. Most things seem to be working right, but my old buddy "sux" no longer gives the root user access to the display. After doing "sux -", I do become the root user, but running any X application gives me errors like:
michaeln@seahunt:~> sux - Password: seahunt:~ # id uid=0(root) gid=0(root) groups=0(root) seahunt:~ # xclock Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Error: Can't open display: :0 seahunt:~ #
I have been using sux for so long now I forgot how to solve this. It's always just worked in the past. There doesn't seem to be a man page for sux, and sux --help just gives a usage message that isn't particularly helpful.
Has anyone else seen this?
Thanks Michael
On Wed, 5 May 2004, Michael Nelson wrote:
I have just installed the 9.1 Pro upgrade this morning. Most things seem to be working right, but my old buddy "sux" no longer gives the root user access to the display. After doing "sux -", I do become the root user, but running any X application gives me errors like:
michaeln@seahunt:~> sux - Password: seahunt:~ # id uid=0(root) gid=0(root) groups=0(root) seahunt:~ # xclock Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Error: Can't open display: :0 seahunt:~ #
I have been using sux for so long now I forgot how to solve this. It's always just worked in the past. There doesn't seem to be a man page for sux, and sux --help just gives a usage message that isn't particularly helpful.
Has anyone else seen this?
While still waiting for my 9.1 to show up, let me offer this observation on previous SuSE versions: If your security configuration is too tight it won't let you connect to the local X server. IIRC it is the settings of file permissions that will screw things up. I would check those first via YaST ---> Security and Users ---> Security Settings, and relax them in case you have them pre-set to too secure. HTH, Alex.
On Thursday 06 May 2004 01.05, Michael Nelson wrote:
I have just installed the 9.1 Pro upgrade this morning. Most things seem to be working right, but my old buddy "sux" no longer gives the root user access to the display. After doing "sux -", I do become the root user, but running any X application gives me errors like:
michaeln@seahunt:~> sux - Password: seahunt:~ # id uid=0(root) gid=0(root) groups=0(root) seahunt:~ # xclock Xlib: connection to ":0.0" refused by server Xlib: Protocol not supported by server
Error: Can't open display: :0 seahunt:~ #
I have been using sux for so long now I forgot how to solve this. It's always just worked in the past. There doesn't seem to be a man page for sux, and sux --help just gives a usage message that isn't particularly helpful.
Has anyone else seen this?
Usually it's solved by su rm /root/.Xauthority exit sux
Am Donnerstag, 6. Mai 2004 06:17 schrieb Anders Johansson:
su rm /root/.Xauthority exit sux And: danam@twiddle:~> sux - hostname: Unbekannter Rechner /usr/X11R6/bin/sux: line 143: /home/danam/.Xauthority: Datei oder Verzeichnis nicht gefunden cat: /home/danam/.Xauthority: Datei oder Verzeichnis nicht gefunden Password: sux: Missing id or cookie or DISPLAY
...errr ... well...in the first place it complained about "protocol version not supported. Meanwhile "ssh -X localhost" is the workaround... Regards Dan -- buddha 2.6.4-54.3-default 11:06am up 1:18, 1 user,
On Thursday 06 May 2004 11.09, Dan Am wrote:
Am Donnerstag, 6. Mai 2004 06:17 schrieb Anders Johansson:
su rm /root/.Xauthority exit sux
And: danam@twiddle:~> sux - hostname: Unbekannter Rechner /usr/X11R6/bin/sux: line 143: /home/danam/.Xauthority: Datei oder Verzeichnis nicht gefunden
I said "rm /root/.Xauthority", not delete your own. If you delete your own Xauthority file you won't even be able to run graphical programs as yourself, let alone as root
In a previous message, Michael Nelson
my old buddy "sux" no longer gives the root user access to the display.
I've had this in the past and (IIRC) the solution was to remove /root/.Xauthority HTH John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!
participants (6)
-
Alex Angerhofer -
Anders Johansson -
Dan Am -
John Pettigrew -
Michael Nelson -
Mike Evans