[Bug 1084798] New: no protocol specified Error: Can't open display:
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 Bug ID: 1084798 Summary: no protocol specified Error: Can't open display: Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: xorg-maintainer-bugs@forge.provo.novell.com Reporter: filippos@dsi.gr QA Contact: xorg-maintainer-bugs@forge.provo.novell.com Found By: --- Blocker: --- Created attachment 763314 --> http://bugzilla.opensuse.org/attachment.cgi?id=763314&action=edit terminal Hi my system is updated on a daily basis. When I start X and work everything is okay, but after some time I cannot execute X programs through terminal! I get the following error. Code: $ xclock No protocol specified No protocol specified Error: Can't open display: :0 DISPLAY=:0 or localhost:0 doesn't work Setting XAUTHORITY doesn't work, too. I also cannot execute from other X opened programs like okular or kate or kwrite though Firefox or Dolphin The error from Dolphin is: KDEInit could not launch '/usr/bin/kwrite' It's like loosing authentication ... Only when I log off/on, everything is fine again! If I reboot the error restarts. See more: https://forums.opensuse.org/showthread.php/530061-No-protocol-specified-Erro... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c1 Michal Srb <msrb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |filippos@filippides.eu, | |msrb@suse.com Assignee|xorg-maintainer-bugs@forge. |msrb@suse.com |provo.novell.com | Flags| |needinfo?(filippos@filippid | |es.eu) --- Comment #1 from Michal Srb <msrb@suse.com> --- Do you use vncserver by any chance? (There is existing issue where xauth started by vncserver overwrites existing Xauthority entries.) When the issue happens, please collect and attach the output of following commands: * echo $DISPLAY * echo $XAUTHORITY * echo $XAUTHLOCALHOSTNAME * hostname * xauth list Note that the advice about "video" group from the forum is wrong. This is about authentication between X application and X server, "video" group has nothing to do with it. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c2 --- Comment #2 from filippos Filippos <filippos@filippides.eu> --- (In reply to Michal Srb from comment #1)
Do you use vncserver by any chance? (There is existing issue where xauth started by vncserver overwrites existing Xauthority entries.)
When the issue happens, please collect and attach the output of following commands: * echo $DISPLAY * echo $XAUTHORITY * echo $XAUTHLOCALHOSTNAME * hostname * xauth list
Note that the advice about "video" group from the forum is wrong. This is about authentication between X application and X server, "video" group has nothing to do with it.
filippos@FOSTW:~/tmp> echo $DISPLAY :0 filippos@FOSTW:~/tmp> echo $XAUTHORITY /tmp/xauth-1000-_0 filippos@FOSTW:~/tmp> echo $XAUTHLOCALHOSTNAME FOSTW filippos@FOSTW:~/tmp> xauth list FOSTW/unix:0 MIT-MAGIC-COOKIE-1 581b477914a05dc6ab34e9585e31d12c filippos@FOSTW:~/tmp> xauth list xauth: file /tmp/xauth-1000-_0 does not exist filippos@FOSTW:~/tmp> echo $DISPLAY :0 filippos@FOSTW:~/tmp> echo $XAUTHORITY /tmp/xauth-1000-_0 filippos@FOSTW:~/tmp> echo $XAUTHLOCALHOSTNAME FOSTW -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c3 --- Comment #3 from Michal Srb <msrb@suse.com> --- (In reply to filippos Filippos from comment #2)
filippos@FOSTW:~/tmp> echo $XAUTHORITY /tmp/xauth-1000-_0
That is unusual place for xauthority file.
filippos@FOSTW:~/tmp> xauth list xauth: file /tmp/xauth-1000-_0 does not exist
Looks like something deleted it meanwhile. Maybe something is cleaning your /tmp/ regularly. Or whatever created it incorrectly determined that it is no longer needed. Which display manager are you using? You can find out using this command: update-alternatives --display default-displaymanager -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c4 --- Comment #4 from filippos Filippos <filippos@filippides.eu> --- default-displaymanager - auto mode link best version is /usr/lib/X11/displaymanagers/sddm link currently points to /usr/lib/X11/displaymanagers/sddm link default-displaymanager is /usr/lib/X11/displaymanagers/default-displaymanager /usr/lib/X11/displaymanagers/console - priority 5 /usr/lib/X11/displaymanagers/kdm - priority 15 /usr/lib/X11/displaymanagers/sddm - priority 25 /usr/lib/X11/displaymanagers/xdm - priority 10 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c5 Michal Srb <msrb@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fvogt@suse.com Flags|needinfo?(filippos@filippid |needinfo?(fvogt@suse.com) |es.eu) | --- Comment #5 from Michal Srb <msrb@suse.com> --- Fabian, any idea why would sddm place XAUTHORITY file into /tmp/xauth-1000-_0? Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c6 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(fvogt@suse.com) | --- Comment #6 from Fabian Vogt <fvogt@suse.com> --- (In reply to Michal Srb from comment #5)
Fabian, any idea why would sddm place XAUTHORITY file into /tmp/xauth-1000-_0? Thanks!
It doesn't - except if explicitly configured to. I just did a search on github for that path and found https://github.com/KDE/kinit/blob/c9688c804d0d76f06062d2b8ab6bd06877510ea0/s... Which seems to be a bad workaround for a bug... kinit (kdeinit5 actually) is the program which spawns various daemons like kded5 and klauncher. The comment in the code seems to be wrong, as as long as the X server is running, there can't be any outdated cookies AFAICT. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c7 --- Comment #7 from filippos Filippos <filippos@filippides.eu> --- In .profile I've changed XAUTHORITY to .Xauthority and everything is okay now. Thanks! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1084798 http://bugzilla.opensuse.org/show_bug.cgi?id=1084798#c8 --- Comment #8 from Fabian Vogt <fvogt@suse.com> --- (In reply to filippos Filippos from comment #7)
In .profile I've changed XAUTHORITY to .Xauthority and everything is okay now. Thanks!
Don't do that, it'll break everything once the fix for this arrives. I made a patch to disable the broken behaviour of kinit for now, but it's not a real solution. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com