fvwm2 error in cygwin

[wxie]

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
>>
>> -- 
>> 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/
>>
>
>
> -- 
> 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/
>


--
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/