fvwm2 error in cygwin

fvwm2 error in cygwin

[wxie]

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/

Re: fvwm2 error in cygwin

[wxie]

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/

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

Re: fvwm2 error in cygwin

[wxie]

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.

--Wei


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


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

Re: fvwm2 error in cygwin

[Jon TURNEY]

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/

how to project startx window to the extended terminal

[wxie]

I have two terminals connect to the laptop running win7. One is the main 
display and the other one is the extended display. When running startx, 
the xwindow always pop-up into the main display. Is it possible to 
configure it such that it directly goes into the extended display?  I 
can certainly drag it there but my two displays have different 
resolution and the xwindow can not fit both terminal at the same time.

Thanks
--Wei

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

RE: how to project startx window to the extended terminal

[JOEL.MOOTS]

> On Behalf Of wxie
> Sent: Thursday, June 09, 2011 7:28 AM

> the xwindow always pop-up into the main display. Is it possible to
> configure it such that it directly goes into the extended display?  I

I asked an similar question a couple months ago and Jon gave this
excellent response:
> From: Jon TURNEY
> Sent: Wednesday, April 13, 2011 9:47 AM
> To place a screen window on the secondary monitor, I'd suggest you
> use the
> syntax '-nodecoration -screen 0 @2'.

-joel

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

Re: how to project startx window to the extended terminal

[Wei Xie]

Thanks for the help but this only works for XWin.exe. I just tried the 
startx which uses xinit and it doesn't work. Further help would be 
appreciated.

--Wei

On 6/9/2011 10:36 AM, JOEL.MOOTS@L-3com.com wrote:
>> On Behalf Of wxie
>> Sent: Thursday, June 09, 2011 7:28 AM
>> the xwindow always pop-up into the main display. Is it possible to
>> configure it such that it directly goes into the extended display?  I
> I asked an similar question a couple months ago and Jon gave this
> excellent response:
>> From: Jon TURNEY
>> Sent: Wednesday, April 13, 2011 9:47 AM
>> To place a screen window on the secondary monitor, I'd suggest you
>> use the
>> syntax '-nodecoration -screen 0 @2'.
> -joel
>
> --
> 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/

Re: how to project startx window to the extended terminal

[wxie]

FYI. I haven't receive any further feedback on the following.

Thanks
--Wei

On 6/9/2011 10:52 AM, Wei Xie wrote:
> Thanks for the help but this only works for XWin.exe. I just tried the 
> startx which uses xinit and it doesn't work. Further help would be 
> appreciated.
>
> --Wei
>
> On 6/9/2011 10:36 AM, JOEL.MOOTS@L-3com.com wrote:
>>> On Behalf Of wxie
>>> Sent: Thursday, June 09, 2011 7:28 AM
>>> the xwindow always pop-up into the main display. Is it possible to
>>> configure it such that it directly goes into the extended display?  I
>> I asked an similar question a couple months ago and Jon gave this
>> excellent response:
>>> From: Jon TURNEY
>>> Sent: Wednesday, April 13, 2011 9:47 AM
>>> To place a screen window on the secondary monitor, I'd suggest you
>>> use the
>>> syntax '-nodecoration -screen 0 @2'.
>> -joel
>>
>> -- 
>> 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/

Re: how to project startx window to the extended terminal

[Marco atzeri]

On 6/10/2011 8:57 PM, wxie wrote:
> FYI. I haven't receive any further feedback on the following.
>

  man startxwin

see the EXAMPLES


> Thanks
> --Wei


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

Re: how to project startx window to the extended terminal

[wxie]

Thanks for the feedback but this is not what I'm referring to.  I can 
run multiple servers but they all show up in the main display.  I can 
make it using XWin -screen 0 @2 but this doesn't work for xinit.

Cheers
--Wei

On 6/10/2011 3:09 PM, Marco atzeri wrote:
> On 6/10/2011 8:57 PM, wxie wrote:
>> FYI. I haven't receive any further feedback on the following.
>>
>
>  man startxwin
>
> see the EXAMPLES
>
>
>> Thanks
>> --Wei
>
>
> -- 
> 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/

Re: how to project startx window to the extended terminal

[Marco atzeri]

On 6/10/2011 9:24 PM, wxie wrote:
> Thanks for the feedback but this is not what I'm referring to. I can run
> multiple servers but they all show up in the main display. I can make it
> using XWin -screen 0 @2 but this doesn't work for xinit.

on these mailing lists we use to comment after,
not before the message...

>
> Cheers
> --Wei
>
> On 6/10/2011 3:09 PM, Marco atzeri wrote:
>> On 6/10/2011 8:57 PM, wxie wrote:
>>> FYI. I haven't receive any further feedback on the following.
>>>
>>
>> man startxwin
>>
>> see the EXAMPLES
>>
>>
>>> Thanks
>>> --Wei
>>

man xinit

xinit -- -screen 0 @2
or
xinit -- Xwin -screen 0 @2

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

original cygwin console?

[wxie]

The new cygwin console use mintty. Is it still possible to change back 
to the orignal console?

Thanks
--Wei


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

Re: original cygwin console?

[Christopher Faylor]

On Fri, Dec 02, 2011 at 09:30:06PM -0500, wxie wrote:
>The new cygwin console use mintty. Is it still possible to change back 
>to the orignal console?

Wrong mailing list but, there was no "cygwin console".  That's just a
standard Windows console running bash.

cgf

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

Re: original cygwin console?

[Thomas Dickey]

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

On Sat, Dec 03, 2011 at 01:44:59AM -0500, Christopher Faylor wrote:
> On Fri, Dec 02, 2011 at 09:30:06PM -0500, wxie wrote:
> >The new cygwin console use mintty. Is it still possible to change back 
> >to the orignal console?
> 
> Wrong mailing list but, there was no "cygwin console".  That's just a
> standard Windows console running bash.

agree "wrong mailing list"

disagree on the followup comment: a standard Windows console provides
a way to implement a simple terminal emulator, but the functionality which
wxie appears to refer to was the implementation provided by Cygwin.

-- 
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: original cygwin console?

[Christopher Faylor]

On Sat, Dec 03, 2011 at 09:23:38AM -0500, Thomas Dickey wrote:
>On Sat, Dec 03, 2011 at 01:44:59AM -0500, Christopher Faylor wrote:
>> On Fri, Dec 02, 2011 at 09:30:06PM -0500, wxie wrote:
>> >The new cygwin console use mintty. Is it still possible to change back 
>> >to the orignal console?
>> 
>> Wrong mailing list but, there was no "cygwin console".  That's just a
>> standard Windows console running bash.
>
>agree "wrong mailing list"
>
>disagree on the followup comment: a standard Windows console provides a
>way to implement a simple terminal emulator, but the functionality
>which wxie appears to refer to was the implementation provided by
>Cygwin.

There is no "implementation" beyond running bash, i.e.:

c:\cygwin\bin\bash --login -i

Put that in a shortcut or, if you need to set some environment
variables, create a .bat file.

Many people seem to think that what they got when they clicked on the
Cygwin icon was some sort of "Cygwin terminal" because they were
apparently unfamilar with the Windows console as seen in good-old
"CMD.EXE".  They apparently had never seen that white-on-black box on
their screen before and thought that Cygwin created it.

cgf

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

Re: original cygwin console?

[Thomas Dickey]

[-- Attachment #1: Type: text/plain, Size: 1252 bytes --]

On Sat, Dec 03, 2011 at 01:30:23PM -0500, Christopher Faylor wrote:
> On Sat, Dec 03, 2011 at 09:23:38AM -0500, Thomas Dickey wrote:
> >On Sat, Dec 03, 2011 at 01:44:59AM -0500, Christopher Faylor wrote:
> >> On Fri, Dec 02, 2011 at 09:30:06PM -0500, wxie wrote:
> >> >The new cygwin console use mintty. Is it still possible to change back 
> >> >to the orignal console?
> >> 
> >> Wrong mailing list but, there was no "cygwin console".  That's just a
> >> standard Windows console running bash.
> >
> >agree "wrong mailing list"
> >
> >disagree on the followup comment: a standard Windows console provides a
> >way to implement a simple terminal emulator, but the functionality
> >which wxie appears to refer to was the implementation provided by
> >Cygwin.
> 
> There is no "implementation" beyond running bash, i.e.:

...and the cygwin dll.  Taking a quick look at the source, it seems
that one of the places of interest is fhandler_console.cc

there's no disagreement that it's running in a Windows console window,
but the point that cygwin provides the terminal emulation behavior
seems to be dismissed - awai

-- 
Thomas E. Dickey <dickey@invisible-island.net>
http://invisible-island.net
ftp://invisible-island.net

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

cygwin setup download is blocked by OfficeScan

[wxie]

It said "it detect a web security policy violation" when I click the 
"setup" link.

Cheers
--Wei

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

xinit crashed

[Wei Xie]

This happened after I did the updated a couple of days ago.
Thanks for any help
--Wei

xinit: XFree86_VT property unexpectedly has 0 items instead of 1
/usr/bin/fvwm.exe: error while loading shared libraries: 
cygfribidi-0.dll: canno
t open shared object file: No such file or directory
xinit: connection to X server lost

waiting for X server to shut down


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

Re: xinit crashed

[Yaakov (Cygwin/X)]

On Mon, 2012-11-19 at 19:22 -0500, Wei Xie wrote:
> /usr/bin/fvwm.exe: error while loading shared libraries: 
> cygfribidi-0.dll: cannot open shared object file: No such file or directory

This means you failed to install dependencies when you
installed/upgraded fvwm.  You need to rerun setup.exe, this time
choosing to install dependencies on the "Resolving Dependencies" page.
If that does not help, then please follow precisely the directions here:
http://cygwin.com/problems.html


Yaakov
Cygwin/X



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

Re: xinit crashed

[wxie]

It doesn't help. When installing fvwm, the fribidi package was not 
picked up automatically. I manually installed it and reinstalled fvwm 
but still got the same problem. Will try to reinstall cygwin from 
scratch which probably faster.

--Wei

On 11/20/2012 2:36 AM, Yaakov (Cygwin/X) wrote:
> On Mon, 2012-11-19 at 19:22 -0500, Wei Xie wrote:
>> /usr/bin/fvwm.exe: error while loading shared libraries:
>> cygfribidi-0.dll: cannot open shared object file: No such file or directory
> This means you failed to install dependencies when you
> installed/upgraded fvwm.  You need to rerun setup.exe, this time
> choosing to install dependencies on the "Resolving Dependencies" page.
> If that does not help, then please follow precisely the directions here:
> http://cygwin.com/problems.html
>
>
> Yaakov
> Cygwin/X
>
>
>
> --
> 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/

Re: xinit crashed

[wxie]

Just as a follow-up. re-installation from scratch solve the problem.

--Wei

On 11/20/2012 10:12 AM, wxie wrote:
> It doesn't help. When installing fvwm, the fribidi package was not 
> picked up automatically. I manually installed it and reinstalled fvwm 
> but still got the same problem. Will try to reinstall cygwin from 
> scratch which probably faster.
>
> --Wei
>
> On 11/20/2012 2:36 AM, Yaakov (Cygwin/X) wrote:
>> On Mon, 2012-11-19 at 19:22 -0500, Wei Xie wrote:
>>> /usr/bin/fvwm.exe: error while loading shared libraries:
>>> cygfribidi-0.dll: cannot open shared object file: No such file or 
>>> directory
>> This means you failed to install dependencies when you
>> installed/upgraded fvwm.  You need to rerun setup.exe, this time
>> choosing to install dependencies on the "Resolving Dependencies" page.
>> If that does not help, then please follow precisely the directions here:
>> http://cygwin.com/problems.html
>>
>>
>> Yaakov
>> Cygwin/X
>>
>>
>>
>> -- 
>> 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/