New subject: [Bug 484026] X11 applications do not start anymore; error message "No protocol specified" and "Can't open display: :0.0"

10 Mar 2009

      https://bugzilla.novell.com/show_bug.cgi?id=484026

           Summary: X11 applications do not start anymore; error message
                    "No protocol specified" and "Can't open display: :0.0"
    Classification: openSUSE
           Product: openSUSE 11.1
           Version: Final
          Platform: i686
        OS/Version: openSUSE 11.1
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: X.Org
        AssignedTo: bnc-team-xorg-bugs@forge.provo.novell.com
        ReportedBy: mail@Franosch.org
         QAContact: xorg-maintainer-bugs@forge.provo.novell.com
          Found By: ---

User-Agent:       Mozilla/5.0 (compatible; Konqueror/3.5; Linux) KHTML/3.5.10
(like Gecko) SUSE

When working under KDE3, after some time (hours, days) no X11 applications
start anymore. When trying to start xterm in a (already open) konsole shell by

xterm

the following error is displayed:

No protocol specified
xterm Xt error: Can't open display: :0.0

When trying to start X11 applications via the "Run command" dialog (Alt-F2,
xterm) the application will not open a window.

This is bug because using the Alt-F2 dialog or the menu, it should always be
possible to start new applications.

I currently know no method to reproduce the bug. It seems to simply occur after
having been logged in for a relatively long time (hours, days). It does not
seem to be triggered by special programs or activities although I am not sure
about this.

You can "cure" the bug by logging out and logging in again.
Or you can cure it by doing "su" in a konsole shell and then log out of this
shell again. After this procedure "xterm" can be started again in the konsole
shell where you did "su". But not only there. It is now again possible to start
xterm in every konsole shell and also by the Alt-F2 dialog. If you just open  a
new konsole shell (without doing su before), then you will not be able to start
xterm in the new shell. So just opening a new shell does not cure the bug.

For an ordinary user, there is no obvious way to work around the bug, it just
appears as a system hang or crash. Therefore, it should be fixed.

How can I debug this further, when the bug occurs?

Thank you very much.

Reproducible: Sometimes

Steps to Reproduce:
It is hard to reproduce. It seems just to occur after some login time or by
chance.

The home directory is mounted by NFS. The server runs Suse Linux 10.2.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

[Bug 484026] New: X11 applications do not start anymore; error message "No protocol specified" and "Can't open display: :0.0"

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

bugzilla_noreply＠novell.com

tags

participants (1)