https://bugzilla.novell.com/show_bug.cgi?id=465955 Vorname Nachname changed: What |Removed |Added ---------------------------------------------------------------------------- Version|RC 2 |Final -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c2 --- Comment #2 from Vorname Nachname 2009-01-14 06:32:42 MST --- (In reply to comment #1)

How do you start the applicatios (shell, start menu, ...)?

Using the button of kicker, "run command" (alt+f2) or an already running konsole.

It happens also for Firefox!? Then you also get the "kdeinit warning"?

No, when trying to start FF just nothing happens. No error message and no window either. I wrote it a bit unclear. The messagebox appears when trying to start e.g. konsole. When trying to start the screensaver I use the "Miniprogramm" (mini applet in english?) I added to kicker, then there is no message box too, only the screen is not locked.

When it doesn't work next time try a "simple" application like xterm. Does it start?

I will as soon as there is a possibility to. Some other things I noticed today: First: when executing "xhost +localhost" I got a No protocol specified xhost: unable to open display ":0.0" and executing "xauth list" gave xauth: /home/iwtm05/.Xauthority not writeable, changes will be ignored however this file definitely belongs to me and I have both write and read permissions. Some seconds later, after everything worked normal again, "xhost +localhost" worked as it is supposed to (granting localhost access) and "xauth list" did not give any error messages. The homes are distributed over NFS can this be a problem? Second: I wrote a dumb bash script opening and killing a konsole in an endless loop all the time. And within roughly four hours this script was three times unable to launch a konsole because of the reported problem. So it looks like this happens more frequently than I thought, only I did not recognize it in the past. Third: I do not know if this helps, but this error was/is not present up to 10.3 and it was (is?) present in 11.0. (I did not deploy 11.0 widely because of an unusable nscd, glad I am rid of it in 11.1) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 Stephan Binner changed: What |Removed |Added ---------------------------------------------------------------------------- Component|KDE3 |X.Org AssignedTo|kde-maintainers@suse.de |sndirsch@novell.com QAContact|qa@suse.de |xorg-maintainer-bugs@forge. | |provo.novell.com -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c5 --- Comment #5 from Vorname Nachname 2009-01-14 08:14:04 MST --- (In reply to comment #4)

Your ~/.Xauthority appears to be broken - for whatever reasons.

Can this happen during working at the machine? Or would it solve the problem if I delete the .Xauthority and start with a fresh one?

Such issues are very hard to reproduce. I suggest to make a copy when you start a Xsession and copy it back to ~/.Xauthority when this issue occurs.

But exactly here lies the problem. I do not always have a konsole or xterm open. So when I discover that there is something amiss, I will be unable to copy any files (unless I switch to text console, but this would be quite unconvenient).

I'm sorry, that I don't have a better proposal at this point. Hope it helps nevertheless.

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c7 --- Comment #7 from Vorname Nachname 2009-01-19 01:42:30 MST --- (In reply to comment #6) Just wanted to let you know: it happened again. I deleted my .Xauthority (from a console, after login out of KDE) last week, so a new one was created with my login into KDE the next day. Worked for some days without problem, until now. Same symptoms, same error messages in Xorg.0.log. I worked with different versions up to 10.3 without this problem for several years, it definitely started with 11.0 (and it's getting a bit annoying). Could it be some kind of temporary access problems to .Xauthority (home distributed over NFS, user authentication done over LDAP)? At least this would explain some of the messages in comment #2. On my private laptop 11.1 works without problem, biggest difference to my computer at work are those two points: NFS and LDAP. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c9 --- Comment #9 from Volker Barth 2009-01-26 08:04:04 MST --- (In reply to comment #8)

Apparently the file exists, but it is not writable. This is what is tested in source code of xauth right before printing this message. Sounds very likely like an issue related to NFS/LDAP.

I think I finally found a solution for the NFS/ssh problem on the web: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269954 One modification is needed for openSuSE, hence I get the following (no problems opening windows since over a week). adding in .bashrc: --- snip --- if [ -n "$SSH_CLIENT" ] ; then export XAUTHORITY=$HOME/.Xauthority-$HOSTNAME fi --- snap --- adding in .ssh/rc: --- snip --- if [ -n "$DISPLAY" ] ; then if read proto cookie ; then case "$DISPLAY" in localhost:*) /usr/X11R6/bin/xauth -f $HOME/.Xauthority-$HOSTNAME add unix:$(echo $DISPLAY | cut -c11-) $proto $cookie ;; *) /usr/X11R6/bin/xauth -f $HOME/.Xauthority-$HOSTNAME add $DISPLAY $proto $cookie ;; esac fi fi --- snap --- -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |eich@novell.com, | |lverhaegen@novell.com, | |mfabian@novell.com, | |mhopf@novell.com, | |sndirsch@novell.com Component|X.Org |Other AssignedTo|sndirsch@novell.com |anicka@novell.com QAContact|xorg-maintainer-bugs@forge. |qa@suse.de |provo.novell.com | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User eich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c12 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |NEEDINFO Info Provider| |volker.barth@ltm.uni-erlang | |en.de --- Comment #12 from Egbert Eich 2009-01-27 08:47:59 MST --- OK, so the workaround described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/269954 works. Volker, do you see any of the other symptoms described in this report? Can you verify that it is NFS that breaks the access to your .Xauthority file? You can dump the content with 'xauth -list'. What changes when you do this after access breaks? Please try this from the home directory mounted to the machine where things break. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|volker.barth@ltm.uni-erlang | |en.de | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User bernet@physik.unizh.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c15 Roland Bernet changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bernet@physik.unizh.ch --- Comment #15 from Roland Bernet 2009-01-28 05:26:40 MST --- This bug is also present in openSUSE 11.0. Having your home directory on NFS and logging in on other machines with ssh -X with the same home directory, you suddenly cannot anymore start any X applications: Error: Can't open display: :0.0 and a ls -l ~/.Xauthority gives sometimes ls: cannot access .Xauthority: Stale NFS file handle A second ls -l ~/.Xauthority usually resolves the problem. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c17 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tiwai@novell.com --- Comment #17 from Stefan Dirsch 2009-01-28 06:05:28 MST --- Takashi (cc'ed) just told me that he's using a special nfs mount option to avoid exactly this problem. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c19 --- Comment #19 from Volker Barth 2009-01-28 06:44:52 MST --- (In reply to comment #18)

In my case, the nfs server (not mount) option "subtree_check" helped. Add it in /etc/exports appropriately. For example, my config looks like: /home @myhosts(rw,async,no_root_squash,subtree_check)

But "man exports" states: As a general guide, a home directory filesystem, which is normally exported at the root and may see lots of file renames, should be exported with subtree checking disabled. A filesystem which is mostly read-only, and at least doesn't see many file renames (e.g. /usr or /var) and for which subdirectories may be exported, should probably be exported with subtree checks enabled. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sndirsch@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c21 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|anicka@novell.com |sjayaraman@novell.com --- Comment #21 from Stefan Dirsch 2009-01-28 08:20:38 MST --- Reassigning to Suresh. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c23 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #23 from Suresh Jayaraman 2009-01-29 03:43:43 MST --- subtree_check might help workaround the problem. But, there could much deeper issue. Could you try to get a packet capture which I think should provide more clues? Something like: #tcpdump -s0 -wnfs-pkts.cap port 2049 and attach nfs-pkts.cap (currently focusing on other high priority issues, will come to this in a while) -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User bernet@physik.unizh.ch added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c25 --- Comment #25 from Roland Bernet 2009-01-30 02:19:36 MST --- Ups, comment got lost ... Created a packet capture file (see attachment) with #tcpdump -s0 -wnfs-pkts.cap port 2049 on a openSUSE 11.0 system with NFS home directories. I executed the command xterm, which failed:

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

-- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c27 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |volker.barth@ltm.uni-erlang | |en.de --- Comment #27 from Suresh Jayaraman 2009-02-16 00:18:48 MST --- Does setting "X11UseLocalhost no" in /etc/ssh/sshd_config and restarting sshd help? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c29 --- Comment #29 from Volker Barth 2009-02-16 02:15:32 MST --- (In reply to comment #27)

Does setting "X11UseLocalhost no" in /etc/ssh/sshd_config and restarting sshd help?

I'll test and report back. (In reply to comment #28)

Irrespective of the previous comment, got a clue just now. Check if the export has "root_squash". If so, the filesystem is exported in a way the causes 'root' accesses to be treated as accessed by 'nobody'. So if you try to access a setuid binary then you might be seeing this error. Changing the export option to "no_root_squash" can fix this.

The server exports the home indeed with the option "root_squash". We set this option with purpose, so that only root on the server has root rights and root from a remote machine cannot access the home folder with root rights (thus preventing damage to the home folder out out carelessness or a hijacked remote machine). Changing it would open a kind of a security leak. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c31 --- Comment #31 from Volker Barth 2009-02-16 03:54:06 MST --- (In reply to comment #27)

Does setting "X11UseLocalhost no" in /etc/ssh/sshd_config and restarting sshd help?

No. Changed the mentioned setting on a remote machine, failed starting X apps after a while at the known point. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c33 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |volker.barth@ltm.uni-erlang | |en.de --- Comment #33 from Suresh Jayaraman 2009-02-20 00:02:42 MST --- When you're seeing the issue, can you please nfs client side debugging by doing(as root): dmesg -c #clear ring buffer rpcdebug -m nfs -s vfs pagecache # enable nfs debugging start xterm (hit the issue) dmesg > nfs-debug.log and attach nfs-debug.log? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c35 Suresh Jayaraman changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |volker.barth@ltm.uni-erlang | |en.de --- Comment #35 from Suresh Jayaraman 2009-02-24 23:04:25 MST --- Sorry, I missed asking you to enable lookupcache.. I also could not reproduce it myself (run for 4 hrs now). Could you please enable lookupcache also by doing this: dmesg -c #clear ring buffer rpcdebug -m nfs -s vfs pagecache lookupcache# enable nfs debugging start xterm (hit the issue) dmesg > nfs-debug.log for both the error case and non-error case and attach? I think this should give definite hints. Thanks! -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c37 --- Comment #37 from Volker Barth 2009-02-25 01:50:49 MST --- Created an attachment (id=275254) --> (https://bugzilla.novell.com/attachment.cgi?id=275254) capture as described in comment #35; workaround from comment #9 inactive -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c39 --- Comment #39 from Volker Barth 2009-02-25 01:52:39 MST --- (From update of attachment 275254) starting xterm does not work -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c41 --- Comment #41 from Suresh Jayaraman 2009-02-25 05:41:36 MST --- Created an attachment (id=275325) --> (https://bugzilla.novell.com/attachment.cgi?id=275325) Proposed patch Could you please apply this patch and see whether it fixes the issue for you? Also, if possible see whether the reproducer that I mentioned in the above comment helps you reproduce the problem for you always and update. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User volker.barth@ltm.uni-erlangen.de added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c43 --- Comment #43 from Volker Barth 2009-02-25 09:13:12 MST --- (In reply to comment #42)

(In reply to comment #41)

...

Created an attachment (id=275325) --> (https://bugzilla.novell.com/attachment.cgi?id=275325) [details] [details] Proposed patch

Could you please apply this patch and see whether it fixes the issue for you?

still compiling, I'll report back as soon as I have the new kernel running.

...

Also, if possible see whether the reproducer that I mentioned in the above comment helps you reproduce the problem for you always and update.

Yes, following the steps listed in comment #40 the problem is reproducible under 11.1, too.

Finally have the patched kernel running. Looks promising. Using the steps in comment #40 I am no longer able to trigger the problem; still able to open new windows. I will work on with the patched kernel and report back in some days with longer time experience. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c45 --- Comment #45 from Suresh Jayaraman 2009-03-06 05:51:01 MST --- Did this problem go away? Or It still occurs? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=465955 User sjayaraman@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=465955#c47 --- Comment #47 from Suresh Jayaraman 2009-03-06 06:08:15 MST --- Excellent! I'll ping upstream folks to get this merged soon. -- 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.