http://bugzilla.opensuse.org/show_bug.cgi?id=1077532 http://bugzilla.opensuse.org/show_bug.cgi?id=1077532#c1 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS CC| |jan.kiszka@web.de, | |msrb@suse.com Assignee|xorg-maintainer-bugs@forge. |msrb@suse.com |provo.novell.com | Flags| |needinfo?(jan.kiszka@web.de | |) --- Comment #1 from Michal Srb --- The latest libxcb update brings fixes for bug 1073996 - it now handles better the situation when hostname changed and the X authority file no longer matches. I can't see what would cause the "No protocol found" message though. The closest one I know is "No protocol specified". This message would be printed and then you would get working application exactly in the case when hostname changes. Can you please provide output of following commands? Must be run inside the graphical session that exhibits the issue.

hostname echo $XAUTHLOCALHOSTNAME echo $DISPLAY xauth list

-- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1077532 http://bugzilla.opensuse.org/show_bug.cgi?id=1077532#c3 Michal Srb changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jan.kiszka@web.de | |) | --- Comment #3 from Michal Srb --- It seems your hostname changed between the time you logged in and now. The XAUTHLOCALHOSTNAME variable is set to the current hostname at log in. Maybe a DHCP server assigned you a new one or something like that. The Xauthority file can be stored in the home directory and so it can be shared between multiple machines and/or multiple X sessions of the same user. The applications use current hostname and display number to identify the cookie for authenticating to the X server. So if the hostname changes, newly started applications could not locate the right cookie anymore. To prevent that, we have the XAUTHLOCALHOSTNAME variable that serves as fallback, if the first attempt with current hostname fails, it retries with the XAUTHLOCALHOSTNAME. Recent changes to this feature caused it to print the warning when the first attempt fails. It is just a cosmetic problem, but should be fixed. -- You are receiving this mail because: You are on the CC list for the bug.