public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net> To: cygwin-xfree@cygwin.com Subject: Re: X server crash when running texworks Date: Thu, 29 Mar 2012 20:21:00 -0000 [thread overview] Message-ID: <4F74C42A.9050707@users.sourceforge.net> (raw) In-Reply-To: <4F74BF22.3020109@cornell.edu> On 2012-03-29 14:59, Ken Brown wrote: > OK, I'm running it now and have attached gdb to it. The good news is > that I've been running it for a couple hours with no crash, and I've > used texworks and have opened many tex files and pdf files in it without > a problem. The bad news is that texworks becomes unresponsive and has to > be killed whenever I try to compile a tex file. I have no idea whether > this is due to an X server problem or something completely different. fork() errors? Are there any messages on the console? > In case you want to try to reproduce the current problem, start > texworks, open a tex file (such as the file test1.tex whose contents I > listed at the beginning of this thread), and click on the icon at the > left end of the toolbar (brown triangle on a green background). This is > supposed to cause test1.tex to get compiled, but for me it just causes > texworks to become unresponsive. This was working properly with the > previous version of the X server (until the server crashed). > > After I kill texworks, `ps' shows a dbus-daemon process and a > dbus-launch process that weren't there before I started texworks, but > maybe that's to be expected. texworks uses QtDBus, so it needs a DBus session bus. If one isn't present (which nowadays you need for just about anything), it will start its own instance. If you are using multiwindow with startxwin, I strongly recommend adding the following to the beginning of your ~/.startxwinrc: eval `dbus-launch --sh-syntax` Yaakov -- 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-03-29 20:21 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-03-24 19:48 Ken Brown 2012-03-26 19:47 ` Ken Brown 2012-03-26 20:07 ` Jon TURNEY 2012-03-26 20:33 ` Ken Brown 2012-03-28 11:16 ` Jon TURNEY 2012-03-28 12:28 ` Ken Brown 2012-03-28 12:46 ` Ken Brown 2012-03-29 12:14 ` Jon TURNEY 2012-03-29 20:00 ` Ken Brown 2012-03-29 20:21 ` Yaakov (Cygwin/X) [this message] 2012-03-29 21:01 ` Ken Brown 2012-03-30 11:36 ` Jon TURNEY 2012-03-31 10:29 ` Jon TURNEY 2012-03-31 15:27 ` Ken Brown 2012-04-01 6:07 ` Jim Reisert AD1C 2012-04-01 13:36 ` Jon TURNEY 2012-04-02 12:05 ` Ken Brown 2012-04-02 16:06 ` Jim Reisert AD1C 2012-04-02 21:14 ` Ken Brown 2012-04-02 22:50 ` Yaakov (Cygwin/X) 2012-04-01 13:40 ` Jon TURNEY 2012-03-28 9:35 ` Yaakov (Cygwin/X)
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=4F74C42A.9050707@users.sourceforge.net \ --to=yselkowitz@users.sourceforge.net \ --cc=cygwin-xfree@cygwin.com \ /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).