X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=PK Tu2vgX5mZd3I9T17NZJ+Frm6OJOLvRyGNXuR7BkmdM32DaoVP6icMZXd6eBXy5LU PG7+upi/JIBQIKS0/v1xdGyZspnBucybK/pg40H3hdim57nFrMUvfX1jUNyXiWom cV/KEb8bAshBsCauJdBlaWHigeqyjtcgFa6ICqn7U= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=CQbHMHwy wFbr3dkOBCad7U39uzM=; b=goRBAgwHdG4bzFILH2/7rkabZsRp9lio4FsHgqtM 8Vek2HCIxRjfz9g/y9gakttm6q28aYt0U5/CU1301wKQ/+lEA+vOD1CVaHmETBT+ 1WsPBnlMLRjCQa2V7P4wga7Wg0sFXl2Op7XJlHqFUjElZ0ToZWLQE6rF4X8n/U+P TPw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.1 required=5.0 tests=AWL,BAYES_50,KAM_INFOUSMEBIZ,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: alum-mailsec-scanner-4.mit.edu MIME-Version: 1.0 X-Received: by 10.107.128.28 with SMTP id b28mr22787208iod.84.1437746516061; Fri, 24 Jul 2015 07:01:56 -0700 (PDT) In-Reply-To: <55B23255.7010504@dronecode.org.uk> References: <55B23255 DOT 7010504 AT dronecode DOT org DOT uk> Date: Fri, 24 Jul 2015 08:01:56 -0600 Message-ID: Subject: Re: Applications no longer launching from xdg From: Jim Reisert AD1C To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes On Fri, Jul 24, 2015 at 6:40 AM, Jon TURNEY wrote: > If you can reproduce this problem, you could always examine the > ~/.xsession-errors file directly. Here it is. There "Can't create dir" messages have been there all along. The ones regarding "Failed to connect to socket" may be the problem. Could not change to root directory: Permission denied Failed to start message bus: Could not chdir() to root directory EOF reading PID from bus daemon Can't create dir /cygdrive/D/Home/Desktop Can't create dir /cygdrive/D/Home/Downloads Can't create dir /cygdrive/D/Home/Templates Can't create dir /cygdrive/D/Home/Public Can't create dir /cygdrive/D/Home/Documents Can't create dir /cygdrive/D/Home/Music Can't create dir /cygdrive/D/Home/Pictures Can't create dir /cygdrive/D/Home/Videos Failed to connect to socket /tmp/fam-Jim Reisert/fam- (process:10328): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 Failed to connect to socket /tmp/fam-Jim Reisert/fam- (process:10328): GLib-GIO-WARNING **: FAMOpen failed, FAMErrno=3 I went in and cleaned out the entire /tmp directory, no change. This is what's in there now: drwxrwxrwt+ 1 Jim Reisert None 0 Jul 24 07:59 . drw-rwx---+ 1 Jim Reisert None 0 Jul 22 21:20 .. -r-----r-- 1 Jim Reisert Jim Reisert 11 Jul 24 07:58 .X0-lock drwx---rwt+ 1 Jim Reisert Jim Reisert 0 Jul 24 07:58 .X11-unix -- Jim Reisert AD1C, , http://www.ad1c.us -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple