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: wxie@purdue.edu Subject: Re: fvwm2 error in cygwin Date: Mon, 17 Jan 2011 15:48:00 -0000 [thread overview] Message-ID: <4D3464C5.5070001@dronecode.org.uk> (raw) In-Reply-To: <4D30EDF8.90906@purdue.edu> On 15/01/2011 00:44, wxie wrote: > Looking through website, It turns out many people have this problem. The > solution is hidden in one of the e-mail, i.e. rebaseall. Suggest to add this > to the Cygwin/X FAQ. Since this is a problem reported by the cygwin DLL, there's nothing specific to Cygwin/X about this problem, so that FAQ might be better off in the main Cygwin FAQ. Thanks for confirming the problem and solution. I've updated that FAQ [1] as you suggested, and added some more words about other similar problems. [1] http://x.cygwin.com/docs/faq/cygwin-x-faq.html#q-status-access-violation > On 1/14/2011 4:04 PM, wxie wrote: >> I noticed that in the cygwin/X FAQ, this was attributed to the multiple copy >> of cygwin1.dll in the machine. But this doesn't cure the problem shown >> before. Any further input would be appreciated. >> >> --Wei >> >> On 1/13/2011 12:43 PM, wxie wrote: >>> The ".fvwm2rc" can be found at: >>> >>> http://www.physics.purdue.edu/~wxie/tmp/ >>> >>> Thanks >>> --Wei >>> >>> On 1/13/2011 12:17 PM, wxie wrote: >>>> Here is some further information. The X window crashs sometime after >>>> showing the following message: >>>> >>>> 1612977 [main] fvwm2 2984 fork: child -1 - died waiting for longjmp before >>>> initi >>>> alization, retry 0, exit code 0x600, errno 11 >>>> [FVWM][executeModule]: <<ERROR>> Fork failed. waiting for X server to >>>> shut down >>>> >>>> Thanks >>>> --Wei >>>> >>>> On 1/13/2011 11:35 AM, wxie wrote: >>>> I installed the window 7 64-bit in my DELL PRECISION M4300 and installed >>>> cygwin/X without any problem. When running the "startx", the following >>>> message pops up. Helps are greatly appreciated. >>>> >>>> Thanks >>>> --Wei >>>> >>>> [FVWM][scanForPixmap]: <<WARNING>> Couldn't load image from mini.ray.xpm >>>> [FVWM][ChangeMenuStyle]: <<ERROR>> cannot find menu MenuSSaver >>>> 2 [main] fvwm 3276 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 499 [main] fvwm 3276 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 2 [main] fvwm 3684 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 707 [main] fvwm 3684 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 2 [main] fvwm 3660 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 485 [main] fvwm 3660 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 4 [main] fvwm 3296 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 1044 [main] fvwm 3296 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 2 [main] fvwm 3892 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 491 [main] fvwm 3892 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 2 [main] fvwm 3976 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 881 [main] fvwm 3976 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 5 [main] fvwm2 1496 fork: child -1 - died waiting for longjmp before >>>> initi >>>> alization, retry 0, exit code 0x600, errno 11 >>>> [DeskerPanelButtons][FlocaleGetFontSet]: >>>> (-adobe-helvetica-bold-r-*-*-10-*-*-*-* >>>> -*-*-*) Missing font charsets: >>>> ISO8859-5, KOI8-R, ISO8859-7, JISX0208.1983-0, KSC5601.1987-0, >>>> GB2312.1980-0, JI >>>> SX0201.1976-0 >>>> 520848 [main] fvwm 3820 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 521854 [main] fvwm 3820 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 770152 [main] fvwm 3364 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 772199 [main] fvwm 3364 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 1081416 [main] fvwm 3688 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 1082442 [main] fvwm 3688 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump >>>> 1344322 [main] fvwm 3564 exception::handle: Exception: >>>> STATUS_ACCESS_VIOLATION >>>> 1346302 [main] fvwm 3564 open_stackdumpfile: Dumping stack trace to >>>> fvwm.exe.sta >>>> ckdump -- 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-01-17 15:48 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-01-13 17:17 wxie 2011-01-13 17:43 ` wxie 2011-01-14 21:04 ` wxie 2011-01-15 0:44 ` wxie 2011-01-17 15:48 ` Jon TURNEY [this message] 2011-06-09 14:28 ` how to project startx window to the extended terminal wxie 2011-06-09 14:37 ` JOEL.MOOTS 2011-06-09 14:52 ` Wei Xie 2011-06-10 18:57 ` wxie 2011-06-10 19:09 ` Marco atzeri 2011-06-10 19:25 ` wxie 2011-06-10 19:37 ` Marco atzeri 2011-12-03 6:22 ` original cygwin console? wxie 2011-12-03 11:42 ` Christopher Faylor 2011-12-03 14:31 ` Thomas Dickey 2011-12-03 19:12 ` Christopher Faylor 2011-12-03 20:53 ` Thomas Dickey 2012-02-26 23:36 ` cygwin setup download is blocked by OfficeScan wxie 2012-11-20 0:22 ` xinit crashed Wei Xie 2012-11-20 7:36 ` Yaakov (Cygwin/X) 2012-11-20 15:12 ` wxie 2012-11-20 15:55 ` wxie
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=4D3464C5.5070001@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=wxie@purdue.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).