pkg/33034: xfce4 doesn't start unless you tweak things

[smb%cs.columbia.edu@localhost]

>Number:         33034
>Category:       pkg
>Synopsis:       xfce4 doesn't start unless you tweak things in /tmp
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    pkg-manager
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Mar 08 19:05:00 +0000 2006
>Originator:     Steven M. Bellovin
>Release:        NetBSD 3.99.16
>Organization:
Department of Computer Science, Columbia University
>Environment:
        
        
System: NetBSD berkshire.machshav.com 3.99.16 NetBSD 3.99.16 (BERKSHIRE) #0: 
Wed Mar 8 08:25:28 EST 2006 
smb%berkshire.machshav.com@localhost:/usr/BUILD/obj/sys/arch/i386/compile/BERKSHIRE
 i386
Architecture: i386
Machine: i386
>Description:
        Run 'startxfce4', exactly as the xfce.org web page says.  It won't
        start; it complains about /tmp/.ICE-unix not existing or having
        the wrong modes.  
>How-To-Repeat:
        Build and install xfce4 from pkgsrc, log in on a command line (and
        not via xdm, gdm, or kdm -- I haven't tried those) and type
        'startxfce4', exactly as the xfce.org web page says.
>Fix:
        You have to create a few directories first as root.  See
        
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2005-03/3277.html
        for details.  I think there should be a MESSAGE in the xfce4
        package and and rc.d script to create those directories.  (I
        confess that since I don't know what those directories do, I don't
        know if there are any security implications to them.  What happens
        if, say, someone creates their own symlinks sockets before the
        proper ones are built?  Are there race condition attacks?  Denial
        of service attacks?)

>Unformatted: