public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: kbrown@cornell.edu Subject: Re: dbus-launch --exit-with-session fails when run from .startxwinrc Date: Wed, 25 Apr 2012 16:22:00 -0000 [thread overview] Message-ID: <4F98249E.8010103@dronecode.org.uk> (raw) In-Reply-To: <4F96AFA3.8060704@cornell.edu> On 24/04/2012 14:50, Ken Brown wrote: > On 4/16/2012 9:50 AM, Ken Brown wrote: >> On 4/16/2012 9:44 AM, Ken Brown wrote: >>> The following problem occurs on my 64-bit Windows 7 system but not on my >>> XP system. >>> >>> I start the X server using the Start Menu shortcut [modified to add >>> -emulate3buttons] and a .startxwinrc with the following contents: >>> >>> eval `dbus-launch --sh-syntax --exit-with-session` >>> xterm >>> >>> Running ps in the resulting xterm window shows no dbus-launch or >>> dbus-daemon process. But I can give the same dbus-launch command in the >>> xterm window, and the processes start as expected. I'm attaching >>> cygcheck output and the XWin log. >>> >>> My hope in reporting this is that the problem I'm seeing (and the >>> difference between XP and Win7) is somehow related to the emacs problem >>> I've been trying to solve: >>> >>> http://cygwin.com/ml/cygwin-xfree/2012-04/msg00048.html >>> >>> Ken >>> >>> P.S. You'll see in the cygcheck output that I'm running a Cygwin >>> snapshot; but nothing changes if I revert to cygwin-1.7.13-1. >> >> I forgot to say that if I remove "--exit-with-session" from the command >> line in my .startxwinrc, then a dbus-daemon process does start. > > I tried modifying the X server shortcut to read > > C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c '/usr/bin/startxwin.exe >>> /var/log/xwin/startxwin.log 2>&1' > > as suggested in a different thread, but that provides no information. The > resulting startxwin.log is virtually identical (with minor differences) to > XWin.0.log. > > In particular, there's no indication of what's happening when .startxwinrc is > processed. There's no output because ~/.startxwinrc generates no output. > For starters, it would really be helpful if someone could try to reproduce my > problem on a 64-bit Windows 7 system. At the moment, I don't even know if > there is a bug somewhere or simply a problem with my own system. Here's the > recipe: > > 1. Create a .startxwinrc file with the following contents: > > eval `dbus-launch --sh-syntax --exit-with-session` > xterm > > 2. Start the X server using the Start Menu shortcut. > > 3. In the resulting xterm window, give the "ps" command. If things are > working right, the output from ps should show a dbus-launch process and a > dbus-daemon process. > > These processes do appear on my XP system but not on my Windows 7 system. FWIW, it works on XP for me as well. I tried with the following ~/.startxwinrc: eval `dbus-launch --sh-syntax --exit-with-session | tee /dev/stderr` xterm ... which at least lets you see the pid of the dbus-daemon that is started. I'm not sure if --exit-with-session is correct with startxwin, since the startxwin process will not linger after it has started ~/.startxwinrc, and I don't know if stdin will remain open after it (and the process tree above it waiting for it) exits. I have this vague recollection that 'run' has to do different things on XP and W7, which might account for the different behaviour? -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next prev parent reply other threads:[~2012-04-25 16:22 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-04-16 13:46 Ken Brown 2012-04-16 13:50 ` Ken Brown 2012-04-24 13:51 ` Ken Brown 2012-04-25 16:22 ` Jon TURNEY [this message] 2012-04-25 17:18 ` Ken Brown
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4F98249E.8010103@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=kbrown@cornell.edu \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).