Date: Fri, 26 Dec 2008 14:25:10 GMT From: Kyryll A Mirnenko <mirya@zoc.com.ua> To: freebsd-gnats-submit@FreeBSD.org Subject: misc/129951: wine 1.1.11 fails to start: problems with temporary files Message-ID: <200812261425.mBQEPA7w029852@www.freebsd.org> Resent-Message-ID: <200812261430.mBQEU1vk077735@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 129951 >Category: misc >Synopsis: wine 1.1.11 fails to start: problems with temporary files >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 26 14:30:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Kyryll A Mirnenko >Release: RELENG_7_1 >Organization: >Environment: FreeBSD miryanote 7.1-RC2 FreeBSD 7.1-RC2 #15: Tue Dec 23 12:31:18 EET 2008 mirya@miryanote:/usr/src/sys/i386/compile/MY-LITE i386 >Description: Any wine problem fails to start due to wineserver initialization failure: $ winecfg wineserver: /tmp/.wine-1005 must not be accessible by other users For some reason the temporary files are created with broken permissions, like /tmp/.wine-1005: d-wxr-xr-- 2 mirya wheel 512 26 гру 16:11 .wine-1005 umask is 0022, and /tmp has standart rwxrwxrwt permissions. It's possible to make it start at last by setting /tmp/.wine-1005 and subdirs permissions to -rwx------ manually, but then any application trying temporary files creation fill fail, probably due to the same reason. The described behavior was not observed with wine-1.1.10, same machine >How-To-Repeat: 1) update to wine-1.1.11 / RELENG_7_1 2) run some simple app, like winecfg 3) expected: fails to start with the message like wineserver: /tmp/.wine-1005 must not be accessible by other users >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200812261425.mBQEPA7w029852>