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: stephen.more@gmail.com Subject: Re: [ANNOUNCEMENT] Updated: xorg-server-1.10.2-1 Date: Wed, 29 Jun 2011 11:06:00 -0000 [thread overview] Message-ID: <4E0B0711.90403@dronecode.org.uk> (raw) In-Reply-To: <BANLkTi=jwnenQ6ZGd9QydQ+aSdA7=yOC9g@mail.gmail.com> On 29/06/2011 12:00, Stephen More wrote: > After installing service pack 1 to System 7 I got the "Failed to > activate core devices." so I updated to xorg-server-1.10.2-1. > > I no longer am getting the Xwin modal error window, but Xwin is still > not starting. Thanks for the report. Can you attach the /var/log/xwin/XWin.0.log, please > On Tue, Jun 28, 2011 at 9:48 AM, Jon TURNEY <jon.turney@dronecode.org.uk> wrote: >> The following packages have been updated in the Cygwin distribution: >> >> *** xorg-server-1.10.2-1 >> *** xorg-server-dmx-1.10.2-1 >> >> These packages contain XWin and the other X.Org X11 servers. >> >> In addition to upstream fixes [1], the following cygwin-specific changes >> have been made since 1.10.1-1: >> >> * Use system() rather than pipe() & fork() to invoke xkbcomp. This should >> work around the X server being unable to startup with "Failed to activate >> core devices" error when cygwin's fork() emulation is unable to work >> successfully. (Launching applications from the tray menu still uses fork() >> and might still fail on problem systems, and other cygwin programs might >> still fail to fork(), but hopefully this will prevent these problems from >> being reported as an X server issue quite as much). (This should make >> Cygwin/X FAQ 9.15 obsolete) >> * Automatically activate the -nolock option if /tmp is on a FAT filesystem. >> (This should make Cygwin/X FAQ 2.3 obsolete) >> * Automatically activate the -emulate3buttons option if less than 3 mouse >> buttons are reported. Add -noemulate3buttons option so this can be >> reversed. >> * To facilitate testing of llvmpipe/softpipe, if the GALLIUM_DRIVER env var >> is set, load the swrastg rather than swrast rasterizer. >> * In -wgl mode, create a new dispatch table, rather than modifying the >> existing one to avoid a GLX crash. >> >> 9ea8c1f306aff9cd32542ee9f47af400 *xorg-server-1.10.2-1.tar.bz2 >> 974750046285c50f8c91244120af5d41 *xorg-server-dmx-1.10.2-1.tar.bz2 >> b525dda038b3b91b347699aa3de0966a *xorg-server-1.10.2-1-src.tar.bz2 >> >> [1] http://lists.freedesktop.org/archives/xorg-announce/2011-May/001675.html >> > Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple > Problem reports: http://cygwin.com/problems.html Please read :-) > Documentation: http://x.cygwin.com/docs/ > FAQ: http://x.cygwin.com/docs/faq/ -- 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:[~2011-06-29 11:06 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-28 14:06 Jon TURNEY 2011-06-29 11:01 ` Stephen More 2011-06-29 11:06 ` Jon TURNEY [this message] 2011-06-29 11:22 ` Stephen More 2011-06-29 11:27 ` Stephen More
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=4E0B0711.90403@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=stephen.more@gmail.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).