Bug 809801 - Disabling IPV6 in network settings, ssh X11-Forwarding fails
Summary: Disabling IPV6 in network settings, ssh X11-Forwarding fails
Status: VERIFIED DUPLICATE of bug 686477
Alias: None
Product: openSUSE 12.3
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: x86-64 SUSE Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-16 14:29 UTC by David North
Modified: 2013-04-07 07:33 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David North 2013-03-16 14:29:11 UTC
User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 Firefox/19.0

Yast2(graphical):Network_Settings:Global_Options:IPv6_Protocol_Settings
Contains a checkbox 'Enable IPV6'.

Un-setting the checkbox and rebooting resulted in X11 forwarding failing.

sshd emits a message to /var/log/messages upon an attempt to login with 'ssh -X':
   sshd[11290]: error: Failed to allocate internet-domain X11 display socket.

This is manually correctable by editing /etc/ssh/sshd_config, enabling option
'AddressFamily inet' instead of 'any' and restarting sshd.


Reproducible: Always

Steps to Reproduce:
1.Disable IPV6 in yast2 network settings
2.Reboot
3.use 'ssh -X' to login from a remote system and run xclock (or similar)
Actual Results:  
X11-forward fails : tested by attempting to run xclock
Client receives message saying 'Error: Can't open display:'
$DISPLAY is not present
/var/log/messages contains error message from sshd:
    sshd[11290]: error: Failed to allocate internet-domain X11 display socket.

Expected Results:  
xclock should run normally

Corrected by manually updating /etc/ssh/sshd_config to contain
'AddressFamily inet' and restarting sshd.
Comment 1 Lance Wang 2013-04-07 07:33:30 UTC
It is a duplicate of bnc#686477. Just close it.

*** This bug has been marked as a duplicate of bug 686477 ***